draft-ietf-dhc-dhcpv6-opt-netboot-01.txt   draft-ietf-dhc-dhcpv6-opt-netboot-02.txt 
DHC T. Huth DHC T. Huth
Internet-Draft J. Freimann Internet-Draft J. Freimann
Intended status: Standards Track IBM Deutschland Research & Intended status: Standards Track IBM Deutschland Research &
Expires: April 17, 2009 Development GmbH Expires: May 22, 2009 Development GmbH
October 14, 2008 November 18, 2008
DHCPv6 option for network boot DHCPv6 option for network boot
draft-ietf-dhc-dhcpv6-opt-netboot-01 draft-ietf-dhc-dhcpv6-opt-netboot-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 17, 2009. This Internet-Draft will expire on May 22, 2009.
Abstract Abstract
The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a
framework for passing configuration information to nodes on a framework for passing configuration information to nodes on a
network. This document describes a new option for DHCPv6 to convey network. This document describes a new option for DHCPv6 to convey
information, required for network booting, to the nodes. information, required for network booting, to the nodes.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Netboot option format . . . . . . . . . . . . . . . . . . . . 3 3. Netboot option format . . . . . . . . . . . . . . . . . . . . 3
4. Suboption: Boot file Uniform Resource Locator (URL) . . . . . 4 4. Suboptions . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Suboption: Vendor class extension . . . . . . . . . . . . . . 6 4.1. Suboption: Boot file Uniform Resource Locator (URL) . . . 4
6. Appearance of these options . . . . . . . . . . . . . . . . . 7 4.2. Suboption: Vendor class extension . . . . . . . . . . . . 6
7. Boot protocol considerations . . . . . . . . . . . . . . . . . 7 5. Appearance of the Netboot option . . . . . . . . . . . . . . . 7
8. IANA considerations . . . . . . . . . . . . . . . . . . . . . 7 6. Boot protocol considerations . . . . . . . . . . . . . . . . . 8
9. Security considerations . . . . . . . . . . . . . . . . . . . 8 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 8. Security considerations . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 12
1. Introduction 1. Introduction
Network booting means that a node which should be booted fetches the Network booting means that a node which should be booted fetches the
files required for booting via its network device from a server. files required for booting via its network device from a server.
Network booting is, for example, very useful in environments where Network booting is, for example, very useful in environments where
the administrators have to maintain a large number of nodes. Since the administrators have to maintain a large number of nodes. Since
all boot and configuration files are stored on a central server, the all boot and configuration files are stored on a central server, the
maintenance of all nodes can be kept simple this way. maintenance of all nodes can be kept simple this way.
skipping to change at page 3, line 25 skipping to change at page 3, line 25
or a boot loader program. To be able to download such a file, the or a boot loader program. To be able to download such a file, the
firmware (BIOS) running on the client node must be provided with firmware (BIOS) running on the client node must be provided with
information such as: the server on which the boot files can be found, information such as: the server on which the boot files can be found,
the protocol to be used for the download (for example TFTP [RFC1350]) the protocol to be used for the download (for example TFTP [RFC1350])
and the name of the boot file. Since some kernels or boot loaders and the name of the boot file. Since some kernels or boot loaders
need to be provided with additional parameters, there should also be need to be provided with additional parameters, there should also be
the possibility to pass additional parameters along with the server the possibility to pass additional parameters along with the server
address, the protocol and the file name. address, the protocol and the file name.
DHCPv6 allows client nodes to ask a DHCPv6 server for configuration DHCPv6 allows client nodes to ask a DHCPv6 server for configuration
parameters. Contrary to its IPv4 predecessor, DHCPv6 does not define parameters. Contrary to its IPv4 predecessor, DHCPv6 does not yet
a way to query network boot options such as the IPv6 address of a define a way to query network boot options such as the IPv6 address
boot file server and boot file names. Therefore this document of a boot file server and boot file names. Therefore this document
defines a new DHCPv6 option which is required for network booting defines a new DHCPv6 option which is required for network booting
clients. clients.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Terminology specific to IPv6 and DHCPv6 are used in the same way as Terminology specific to IPv6 and DHCPv6 are used in the same way as
skipping to change at page 4, line 23 skipping to change at page 4, line 23
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. <multiple suboptions> . . <multiple suboptions> .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-code n | suboption-len | | suboption-code n | suboption-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| subopt-data n (variable length) | | subopt-data n (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPT_NET_BOOT (tbd). option-code OPT_NET_BOOT (TBD1).
option-len Length of the netboot option in octets (not including option-len Length of the netboot option in octets (not
the size of the option-code and option-len fields). including the size of the option-code and option-
len fields).
suboption-code, suboption-len and subopt-data together comprise a
suboption for the netboot option. The 16-bit
unsigned suboption-code values are drawn from a
private namespace of the netboot option managed by
IANA (cf. Section 8). The 16-bit unsigned
suboption-len values indicate the length of the
subopt-data field in octets.
Multiple occurences of each suboption-type can occur within a netboot Multiple occurences of each suboption-type can occur within a netboot
option (for example when more than one boot server is available). option (for example when more than one boot server is available).
Clients MUST process the suboptions in the order in which they appear Clients MUST process the suboptions in the order in which they appear
in the message sent by the server. in the message sent by the server.
So far, only the suboptions in the following chapters have been So far, only the suboptions in the following chapters have been
defined. Other suboptions might be defined in future RFCs. defined. Other suboptions might be defined in future RFCs.
4. Suboption: Boot file Uniform Resource Locator (URL) 4. Suboptions
This suboption consists of multiple null-terminated strings. It is 4.1. Suboption: Boot file Uniform Resource Locator (URL)
used to convey an URL to a boot file together with additional
parameters for the boot file (e.g. parameters for the kernel or boot
loader program).
Since multiple occurrences of SUBOPT_BOOTFILE_URL can be present in a This suboption consists of multiple ASCII strings. It is used to
single OPT_NETBOOT message, clients MUST process them in the order in convey an URL to a boot file together with additional parameters for
which they appear within the message. For example in the case of a the boot file (e.g. parameters for the kernel or boot loader
boot file URL the first file should be downloaded and executed. In program).
case of a failure the process should continue with the second one and
so on.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SUBOPT_BOOTFILE_URL | suboption-len | | SUBOPT_BOOTFILE_URL | suboption-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bootfile-url | | bootfile-len | bootfile-url |
. (variable) . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (variable length) .
| | '\0' | . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| parameter 1 | | param-len 1 | parameter 1 |
. (variable) . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (variable length) .
| | '\0' | . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. <multiple Parameters> . . <multiple Parameters> .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| parameter n | | param-len n | parameter n |
. (variable) . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (variable length) .
| | '\0' | . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Format description: Format description:
suboption-code SUBOPT_BOOTFILE_URL (tbd). suboption-code SUBOPT_BOOTFILE_URL (1).
suboption-len Length of the bootfile suboption in octets (not suboption-len Length of the bootfile suboption in octets (not
including the size of the suboption-code and including the size of the suboption-code and
suboption-len fields). suboption-len fields).
bootfile-url This NULL-terminated ASCII string is the URL bootfile-len 16-bit integer that specifies the length of the
(conforming to [RFC2396]) to a boot file. This bootfile-url in octets (not including the bootfile-
string starts with the protocol which is used for length field).
downloading. Separated by '://', the hostname or
IPv6 address of the server hosting the boot file
(see also the note below), the path, file name and
query parts of the URL follow.
parameters 1...n These NULL-terminated ASCII strings are parameters bootfile-url This ASCII string is the URL (conforming to
needed for booting, e.g. kernel parameters. In [RFC3986]) for a boot file. This string starts
cases where no parameters are needed, everything with the protocol which is used for downloading.
but the boot file URL can be omitted. Parameters Separated by "://", the hostname or IPv6 address of
following the boot file name should be directly the server hosting the boot file (see also the note
related to the boot file (kernel) itself. below) follows, and then the path, file name and
query parts of the URL. The string is not null-
terminated.
param-len 1...n This is a 16-bit integer which specifies the length
of the following parameter in octets (not including
the parameter-length field).
parameters 1...n These ASCII strings are parameters needed for
booting, e.g. kernel parameters. The strings are
not null-terminated. The firmware should pass
these parameters in the order they appear in the
SUBOPT_BOOTFILE_URL suboption to the boot file
which has been specified in the bootfile-url field.
In cases where no parameters are needed, everything
but the boot file URL (including its length field)
can be omitted.
Note about the bootfile-url: This string can either contain a Note about the bootfile-url: This string can either contain a
hostname or an IPv6 address to specify the server where the boot file hostname or a literal IPv6 address to specify the server where the
should be downloaded from. All clients which implement support for boot file should be downloaded from. All clients which implement the
the SUBOPT_BOOTFILE_URL suboption MUST be able to handle IPv6 SUBOPT_BOOTFILE_URL suboption MUST be able to handle IPv6 addresses
addresses here. The IPv6 address in the URL then MUST be enclosed in here and SHOULD also be able to handle a hostname in the URL. The
"[" and "]" characters, conforming to [RFC2732]. Clients SHOULD also IPv6 address in the URL then MUST be enclosed in "[" and "]"
be able to handle hostnames in the URLs. However, in this case the characters, conforming to [RFC3986]. Clients SHOULD also be able to
firmware implementation on the client machine must support DNS, too. handle hostnames in the URLs. However, in this case the firmware
Due to size limitations, this might not be possible in all firmware implementation on the client machine must support DNS, too. Due to
size limitations, this might not be possible in all firmware
implementations, so support for hostnames in the URLs is only implementations, so support for hostnames in the URLs is only
optional. optional.
5. Suboption: Vendor class extension Since multiple occurrences of SUBOPT_BOOTFILE_URL can be present in a
single OPT_NETBOOT message, clients MUST process them in the order in
which they appear within the message. For example in the case of a
boot file URL the first file should be downloaded and executed. In
case of a failure the process should continue with the second one and
so on.
4.2. Suboption: Vendor class extension
With this suboption, vendors can define their own netboot suboptions: With this suboption, vendors can define their own netboot suboptions:
It can be used by clients and servers to exchange vendor-specific It can be used by clients and servers to exchange vendor-specific
information which is related to network booting. information which is related to network booting.
This suboption can occur multiple times within a OPT_NET_BOOT option This suboption can occur multiple times within a OPT_NET_BOOT option
(also with different enterprise-numbers in case a server and client (also with different enterprise-numbers in case a server and client
implementation supports different vendor extensions). Clients MUST implementation supports different vendor extensions). Clients MUST
process them in the order in which they appear within the message. process them in the order in which they appear within the message.
Unsupported vendor extensions MUST be ignored. Unsupported vendor extensions MUST be ignored.
skipping to change at page 6, line 40 skipping to change at page 7, line 20
| enterprise-number | | enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. vendor-class-data . . vendor-class-data .
. (variable length) . . (variable length) .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Format description: Format description:
suboption-code SUBOPT_NETBOOT_VENDOR (tbd). suboption-code SUBOPT_NETBOOT_VENDOR (2).
suboption-len Length of the vendor class suboption in octets suboption-len Length of the vendor class suboption in octets
(not including the size of the suboption-code and (not including the size of the suboption-code and
suboption-len fields). suboption-len fields).
enterprise-number The enterprise number of the vendor as registered enterprise-number The enterprise number of the vendor as registered
with IANA (see [VENDORIDS]). with IANA (see [VENDORIDS]).
vendor-class-data Vendor-specific information. The meaning is vendor-class-data Vendor-specific information. The meaning is
defined by the vendor identified by the defined by the vendor identified by the
enterprise-number. enterprise-number. It is suggested that the
vendor-class-data SHOULD be composed of a series
of separate items with a two-octets length field
at the beginning of each item, as it is described
for the vendor class option in chapter 22.16 of
[RFC3315].
6. Appearance of these options 5. Appearance of the Netboot option
The netboot option MUST NOT appear in DHCPv6 messages other than the The netboot option MUST NOT appear in DHCPv6 messages other than the
types Solicit, Advertise, Request, Renew, Rebind, Information-Request types Solicit, Advertise, Request, Renew, Rebind, Information-Request
and Reply. and Reply.
The number of the netboot option MAY appear in the Option Request The option-code of the netboot option MAY appear in the Option
Option in the DHCPv6 message types Solicit, Request, Renew, Rebind, Request Option in the DHCPv6 message types Solicit, Request, Renew,
Information-Request and Reconfigure. Rebind, Information-Request and Reconfigure.
The suboptions MUST appear only in the netboot option. The suboptions MUST appear only in the netboot option.
7. Boot protocol considerations 6. Boot protocol considerations
RFC 906 [RFC906] suggests to use TFTP for bootstrap loading. Because RFC 906 [RFC906] suggests to use TFTP for bootstrap loading. Because
it is easy to implement this protocol in firmware (where one has to it is easy to implement this protocol in firmware (where one has to
deal with size and complexity constraints), this is still the deal with size and complexity constraints), this is still the
recommended protocol for network booting. Every firmware recommended protocol for network booting. Every firmware
implementation SHOULD at least support this protocol. The boot file implementation SHOULD at least support this protocol. The boot file
URLs then must be specified according to RFC 3617 [RFC3617]. URLs then must be specified according to RFC 3617 [RFC3617].
An alternative approach to TFTP network booting is to bootstrap the An alternative approach to TFTP network booting is to bootstrap the
system with iSCSI. In this case, the URL in the SUBOPT_BOOTFILE_URL system with iSCSI. In this case, the URL in the SUBOPT_BOOTFILE_URL
skipping to change at page 7, line 47 skipping to change at page 8, line 31
anymore. So for IPv6 iSCSI booting, the "iscsi:" string MUST be anymore. So for IPv6 iSCSI booting, the "iscsi:" string MUST be
specified as URL in the SUBOPT_BOOTFILE_URL suboption instead. specified as URL in the SUBOPT_BOOTFILE_URL suboption instead.
In some different scenarios, it might also be useful to use other In some different scenarios, it might also be useful to use other
protocols like FTP or HTTP for network booting, so a firmware protocols like FTP or HTTP for network booting, so a firmware
implementation can support these protocols, too. Then it is up to implementation can support these protocols, too. Then it is up to
the network administrator to choose the appropriate boot protocol for the network administrator to choose the appropriate boot protocol for
the network, and to specify the right boot file URLs in the DHCPv6 the network, and to specify the right boot file URLs in the DHCPv6
server configuration file. server configuration file.
8. IANA considerations 7. IANA considerations
The following option needs to be assigned by the IANA from the option The following option needs to be assigned by the IANA from the option
number space defined in the chapter 22 of the DHCPv6 RFC [RFC3315]. number space defined in the chapter 22 of the DHCPv6 RFC [RFC3315].
+--------------+-------+--------------+ +--------------+-------+--------------+
| Option name | Value | Specified in | | Option name | Value | Specified in |
+--------------+-------+--------------+ +--------------+-------+--------------+
| OPT_NET_BOOT | tbd | Section 3 | | OPT_NET_BOOT | TBD1 | Section 3 |
+--------------+-------+--------------+ +--------------+-------+--------------+
The netboot suboptions numbers form a new name space to be defined by The OPT_NET_BOOT option also defines a new 16-bit integer suboption
the IANA: field, for which IANA is to create and maintain a new sub-registry
entitled "Netboot Suboptions" under the OPT_NET_BOOT option. Initial
values for the Netboot Suboptions registry are given below; future
assignments are to be made through IETF Review (see [RFC5226]).
Assignments consist of a suboption name and its associated value.
+-----------------------+-------+--------------+ +-----------------------+-------+--------------+
| Suboption name | Value | Specified in | | Suboption name | Value | Specified in |
+-----------------------+-------+--------------+ +-----------------------+-------+--------------+
| SUBOPT_BOOTFILE_URL | tbd | Section 4 | | SUBOPT_BOOTFILE_URL | 1 | Section 4.1 |
| SUBOPT_NETBOOT_VENDOR | tbd | Section 5 | | SUBOPT_NETBOOT_VENDOR | 2 | Section 4.2 |
+-----------------------+-------+--------------+ +-----------------------+-------+--------------+
9. Security considerations 8. Security considerations
The new DHCPv6 option described in this document could be sent in The new DHCPv6 option described in this document could be sent in
untrusted networks by malicious people with a fake DHCPv6 server to untrusted networks by malicious people with a fake DHCPv6 server to
confuse the booting clients. The clients could be provided with a confuse the booting clients. The clients could be provided with a
wrong URL so that the boot either fails, or even worse, the client wrong URL so that the boot either fails, or even worse, the client
boots the wrong operating system which has been provided by a boots the wrong operating system which has been provided by a
malicious file server. To prevent this kind of attack, clients malicious file server. To prevent this kind of attack, clients
SHOULD use authentication of DHCPv6 messages (see chapter 21. in RFC SHOULD use authentication of DHCPv6 messages (see chapter 21. in RFC
3315 [RFC3315]). 3315 [RFC3315]).
Note also that DHCPv6 messages are sent unencrypted by default. So Note also that DHCPv6 messages are sent unencrypted by default. So
the boot file URL options are sent unencrypted over the network, too. the boot file URL options are sent unencrypted over the network, too.
This can become a security risk since the URLs can contain sensitive This can become a security risk since the URLs can contain sensitive
information like user names and passwords (for example a URL like information like user names and passwords (for example a URL like
"ftp://username:password@servername/path/file"). At the current "ftp://username:password@servername/path/file"). At the current
point in time, there is no possibility to send encrypted DHCPv6 point in time, there is no possibility to send encrypted DHCPv6
messages, so it is strongly recommended not to use sensitive messages, so it is strongly recommended not to use sensitive
information in the URLs in untrusted networks. information in the URLs in untrusted networks.
10. Acknowledgements 9. Acknowledgements
The authors would like to thank Ketan P. Pancholi for corrections and The authors would like to thank Ketan P. Pancholi and Alfred Hoenes
suggestions. for corrections and suggestions.
Vijayabhaskar Kalusivalingam and Senthil Balasubramanian published a Vijayabhaskar Kalusivalingam and Senthil Balasubramanian published a
similar draft for IPv6 network booting some years ago (available at similar draft for IPv6 network booting some years ago (available at
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-opt-rboot-00), which http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-opt-rboot-00), which
however was abandoned for unknown reasons. however was abandoned for unknown reasons.
11. References 10. References
11.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998.
[RFC2732] Hinden, R., Carpenter, B., and L. Masinter, "Format for
Literal IPv6 Addresses in URL's", RFC 2732, December 1999.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3617] Lear, E., "Uniform Resource Identifier (URI) Scheme and [RFC3617] Lear, E., "Uniform Resource Identifier (URI) Scheme and
Applicability Statement for the Trivial File Transfer Applicability Statement for the Trivial File Transfer
Protocol (TFTP)", RFC 3617, October 2003. Protocol (TFTP)", RFC 3617, October 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[RFC4173] Sarkar, P., Missimer, D., and C. Sapuntzakis, [RFC4173] Sarkar, P., Missimer, D., and C. Sapuntzakis,
"Bootstrapping Clients using the Internet Small Computer "Bootstrapping Clients using the Internet Small Computer
System Interface (iSCSI) Protocol", RFC 4173, System Interface (iSCSI) Protocol", RFC 4173,
September 2005. September 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[VENDORIDS] [VENDORIDS]
IANA, "Private Enterprise Numbers", IANA, "Private Enterprise Numbers",
<http://www.iana.org/assignments/enterprise-numbers>. <http://www.iana.org/assignments/enterprise-numbers>.
11.2. Informative References 10.2. Informative References
[RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, [RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33,
RFC 1350, July 1992. RFC 1350, July 1992.
[RFC906] Finlayson, R., "Bootstrap Loading using TFTP", RFC 906, [RFC906] Finlayson, R., "Bootstrap Loading using TFTP", RFC 906,
June 1984. June 1984.
Authors' Addresses Authors' Addresses
Thomas H. Huth Thomas H. Huth
 End of changes. 36 change blocks. 
92 lines changed or deleted 127 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/