draft-ietf-softwire-ds-lite-tunnel-option-01.txt   draft-ietf-softwire-ds-lite-tunnel-option-02.txt 
Dynamic Host Configuration Working D. Hankins Softwires D. Hankins
Group ISC Internet-Draft ISC
Internet-Draft T. Mrugalski Intended status: Standards Track T. Mrugalski
Intended status: Standards Track Gdansk University of Technology Expires: September 3, 2010 Gdansk University of Technology
Expires: July 9, 2010 January 5, 2010 March 2, 2010
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Options for Dual- Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Options for Dual-
Stack Lite Stack Lite
draft-ietf-softwire-ds-lite-tunnel-option-01 draft-ietf-softwire-ds-lite-tunnel-option-02
Abstract Abstract
This document specifies two DHCPv6 Options which are meant to be used This document specifies two DHCPv6 options which are meant to be used
by Softwire Initiator (SI) to retrieve its attached DS-Lite AFTR by a Dual-Stack Lite client (Basic Bridging BroadBand element, B4) to
(Address Family Transition Router). discover its Address Family Transition Router (AFTR) address.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 July 9, 2010. This Internet-Draft will expire on September 3, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the BSD License.
Table of Contents Table of Contents
1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DHCPv6 Options . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The Dual-Stack Lite Address DHCPv6 Option . . . . . . . . . . . 3
3.1. The Dual-Stack Lite Softwire Concentrator Address 4. The Dual-Stack Lite Name DHCPv6 Option . . . . . . . . . . . . 4
DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . . . 3 5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 6
3.2. The Dual-Stack Lite Softwire Concentrator Name DHCPv6 6. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 7
Option . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
5. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 7 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 10. Normative References . . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
9. Normative References . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Requirements Language 1. Requirements Language
In this document, the key words "MAY", "MUST", "MUST NOT", In this document, the key words "MAY", "MUST", "MUST NOT",
"OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be "OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be
interpreted as described in BCP 14, RFC 2119 [RFC2119]. interpreted as described in BCP 14, RFC 2119 [RFC2119].
2. Introduction 2. Introduction
Dual-Stack Lite [draft-ietf-softwire-dual-stack-lite-02] is a Dual-Stack Lite [I-D.softwire-ds-lite-03] is a solution to offer both
solution to offer both IPv4 and IPv6 connectivity to customers which IPv4 and IPv6 connectivity to customers which are addressed only with
are addressed only with an IPv6 prefix (no IPv4 address is assigned an IPv6 prefix (no IPv4 address is assigned to the attachment
to the attachment device). One of its key components is an IPv4- device). One of its key components is an IPv4-over-IPv6 tunnel,
over-IPv6 tunnel, commonly referred to as a Softwire, but a DS-Lite commonly referred to as a Softwire, but a DS-Lite Basic Bridging
Basic Bridging BroadBand (B4) will not know if the network it is BroadBand (B4) will not know if the network it is attached to offers
attached to offers Dual-Stack Lite support, and if it did would not Dual-Stack Lite support, and if it did would not know the remote end
know the remote end of the tunnel to establish a connection. of the tunnel to establish a connection.
To inform the B4 of the Address Family Transition Router's (AFTR) To inform the B4 of the AFTR's location, either an IPv6 address or
location, either an IPv6 address or Fully Qualified Domain Name Fully Qualified Domain Name (FQDN) may be used. Once this
(FQDN) may be used. Once this information is conveyed, the presence information is conveyed, the presence of the configuration indicating
of the configuration indicating the AFTR's location also informs a the AFTR's location also informs a host to initiate Dual-Stack Lite
host to initiate Dual-Stack Lite (DS-Lite) service and become a (DS-Lite) service and become a Softwire Initiator.
Softwire Initiator.
To provide the conveyance of the configuration information, two To provide the conveyance of the configuration information, two
DHCPv6 [RFC3315] Options are used; one in the case where the host DHCPv6 [RFC3315] options are used; one in the case where the host
receives an IPv6 address, and one in the case where the host receives receives an IPv6 address, and one in the case where the host receives
an FQDN in order to derive an IPv6 address. an FQDN in order to derive an IPv6 address.
This document assumes that the SI is provided with appropriate The details of how the B4 establishes an IPv4-in-IPv6 tunnel to the
instructions for the activation of an IPv4-in-IPv6 scheme which is AFTR are out of scope for this document.
supposed to be supported in both B4 and AFTR. Consequently, this
memo does not precise the IPv4-in-IPv6 encapsulation scheme to be
used by B4.
3. DHCPv6 Options
Following sub-sections define two new DHCPv6 Options, conformant with
requirements specified in DHCPv6 [RFC3315] Section 22.1.
3.1. The Dual-Stack Lite Softwire Concentrator Address DHCPv6 Option 3. The Dual-Stack Lite Address DHCPv6 Option
The Dual-Stack Lite Softwire Concentrator Address Option consists of The Dual-Stack Lite Address option consists of option-code and
option-code and option-len fields (common for all DHCPv6 Options), option-len fields (common for all DHCPv6 options), and a 128 bit
and a 128 bit tunnel-endpoint-addr field, containing one IPv6 tunnel-endpoint-addr field, containing one IPv6 address. The tunnel-
address. The tunnel-endpoint-addr specifies the location of the endpoint-addr specifies the location of the remote tunnel endpoint,
remote tunnel endpoint, expected to be located at an AFTR (DS-Lite expected to be located at an AFTR.
Address Family Transition Router element).
The DS-Lite Address DHCPv6 Option MAY appear in the root scope of a The DS-Lite Address option MAY appear in the root scope of a DHCPv6
DHCPv6 packet. It MUST NOT appear inside any IA_NA, IA_TA, IA_PD, packet. It MUST NOT appear inside any IA_NA, IA_TA, IA_PD, IAADDR,
IAADDR, or similar. or similar.
The DS-Lite Address DHCPv6 Option MUST NOT appear more than once in a The DS-Lite Address option MUST NOT appear more than once in a
message. message.
The format of the Dual-Stack Lite Softwire Concentrator Addr DHCPv6 The format of the Dual-Stack Lite Address option is shown in the
Option is shown in the following figure: following figure:
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
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| OPTION_DS_LITE_ADDR (TBD) | option-len: 16 | | OPTION_DS_LITE_ADDR (TBD) | option-len: 16 |
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| | | |
| tunnel-endpoint-addr (IPv6 Address) | | tunnel-endpoint-addr (IPv6 Address) |
| | | |
| | | |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
DS Lite IPv6 Address DHCPv6 Option format. option-code: OPTION_DS_LITE_ADDR (TBD)
Figure 1
Below is provided the description of the enclosed fields:
option-code: OPTION_DS_LITE_ADDR (TBD) option-len: Length of the tunnel-endpoint-addr field,
which is precisely 16 octets.
option-len: Length of the tunnel-endpoint-addr field, which is tunnel-endpoint-addr: A single IPv6 address in binary
currently defined to be precisely 16 octets. representation of the remote tunnel
endpoint, located at the DS-Lite AFTR.
tunnel-endpoint-addr: This field contains a single IPv6 address in Figure 1: DS-Lite IPv6 Address DHCPv6 Option Format
binary representation of the remote tunnel endpoint, located at
the DS-Lite AFTR. It is precisely 16 octets in length.
The client validates the DS-Lite Address DHCPv6 Option by confirming The client validates the DS-Lite Address option by confirming the
the option is of 16 octets in length or greater. The client MUST option is of 16 octets in length or greater. The client MUST ignore
ignore tunnel-endpoint-addr shorter than 16 octets. In the event the any tunnel-endpoint-addr shorter than 16 octets. In the event the
option is greater than 16 octets in length, only the first 16 octets option is greater than 16 octets in length, only the first 16 octets
are interpreted. are interpreted.
Because this option conveys the tunnel-endpoint-addr value, no Because this option conveys the tunnel-endpoint-addr value, no
further processing is required of the client. further processing is required of the client.
The definition of this option is simple and encloses only a single This option conveys a single IPv6 address, as the Dual-Stack Lite
IPv6 address. It is temping to define a flexible option which may specification [I-D.softwire-ds-lite-03] defines only one Softwire
convey several IPv6 addresses (for robustness and service connection between a B4 and any AFTR. Multiple connections or
availability reasons), but for the sake of simplicity and consistency endpoints are undefined. For more information, see Section 7.2 "High
it is recommended to use a FQDN Option instead of conveying several Availability" of [I-D.softwire-ds-lite-03].
IPv6 addresses.
3.2. The Dual-Stack Lite Softwire Concentrator Name DHCPv6 Option 4. The Dual-Stack Lite Name DHCPv6 Option
The Dual-Stack Lite Softwire Concentrator Name Option consists of The Dual-Stack Lite Name option consists of option-code and option-
option-code and option-len fields (common for all DHCPv6 Options), len fields (common for all DHCPv6 options), and a variable length
and a variable length tunnel-endpoint-name field, containing a Fully tunnel-endpoint-name field, containing a Fully Qualified Domain Name
Qualified Domain Name that refers to the AFTR the client is requested that refers to the AFTR the client is requested to establish a
to establish a connection with. connection with.
The DS-Lite Name option MAY appear in the root scope of a DHCPv6 The DS-Lite Name option MAY appear in the root scope of a DHCPv6
packet. It MUST NOT appear inside any IA_NA, IA_TA, IA_PD, IAADDR, packet. It MUST NOT appear inside any IA_NA, IA_TA, IA_PD, IAADDR,
or similar. or similar.
The DS-Lite Name DHCPv6 Option MUST NOT appear more than once in a The DS-Lite Name option MUST NOT appear more than once in a message.
message.
The format of the Dual-Stack Lite Softwire Concentrator Name DHCPv6 The format of the Dual-Stack Lite Name option is shown in the
Option is shown in th following figure: following figure:
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
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| OPTION_DS_LITE_NAME (TBD) | option-len | | OPTION_DS_LITE_NAME (TBD) | option-len |
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| tunnel-endpoint-name (FQDN) | | tunnel-endpoint-name (FQDN) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
DS-Lite FQDN DHCPv6 Option format. option-code: OPTION_DS_LITE_NAME (TBD)
Figure 2
Below is provided the description of the enclosed fields:
option-code: OPTION_DS_LITE_NAME (TBD) option-len: Length in octets of the tunnel-endpoint-
name field.
option-len: Length in octets of the tunnel-endpoint-name field. tunnel-endpoint-name: A single Fully Qualified Domain Name of the
remote tunnel endpoint, located at the
DS-Lite AFTR.
tunnel-endpoint-name: This field contains a single Fully Qualified Figure 2: DS-Lite Name DHCPv6 Option Format
Domain Name of the remote tunnel endpoint, located at the DS-Lite
AFTR.
The tunnel-endpoint-name field is formatted as required in DHCPv6 The tunnel-endpoint-name field is formatted as required in DHCPv6
[RFC3315] Section 8 ("Representation and Use of Domain Names"). [RFC3315] Section 8 ("Representation and Use of Domain Names").
Briefly, the format described is using a single octet noting the Briefly, the format described is using a single octet noting the
length of one DNS label (limited to at most 64 octets), followed by length of one DNS label (limited to at most 64 octets), followed by
the label. This repeats until all labels in the FQDN are exhausted. the label. This repeats until all labels in the FQDN are exhausted.
The root label (or the end of the FQDN) is denoted as a zero length The root label (or the end of the FQDN) is denoted as a zero length
label. An example FQDN format for this option is shown in Figure 3. label. An example FQDN format for this option is shown in Figure 3.
+------+------+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+------+------+
| 0x07 | e | x | a | m | p | l | e | 0x03 | | 0x07 | e | x | a | m | p | l | e | 0x03 |
+------+------+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+------+------+
skipping to change at page 6, line 18 skipping to change at page 5, line 47
the label. This repeats until all labels in the FQDN are exhausted. the label. This repeats until all labels in the FQDN are exhausted.
The root label (or the end of the FQDN) is denoted as a zero length The root label (or the end of the FQDN) is denoted as a zero length
label. An example FQDN format for this option is shown in Figure 3. label. An example FQDN format for this option is shown in Figure 3.
+------+------+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+------+------+
| 0x07 | e | x | a | m | p | l | e | 0x03 | | 0x07 | e | x | a | m | p | l | e | 0x03 |
+------+------+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+------+------+
| i | s | c | 0x03 | o | r | g | 0x00 | | i | s | c | 0x03 | o | r | g | 0x00 |
+------+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+------+
Example tunnel-endpoint-name. Figure 3: Example tunnel-endpoint-name.
Figure 3
Note that in the specific case of the example tunnel-endpoint-name, Note that in the specific case of the example tunnel-endpoint-name,
(Figure 3) the length of the option is 17 octets, and so an option- (Figure 3) the length of the option is 17 octets, and so an option-
len field value of 17 would be used. len field value of 17 would be used.
The client (B4) validates the option in this format by first The client (B4) validates the option in this format by first
confirming that the option length is greater than 3, that the option confirming that the option length is greater than 3, that the option
data can be contained by the option length (that the option length data can be contained by the option length (that the option length
does not run off the end of the packet), and that the tunnel- does not run off the end of the packet), and that the tunnel-
endpoint-name is of valid format as described in DHCPv6 Section 8 endpoint-name is of valid format as described in DHCPv6 Section 8
[RFC3315]; there are no compression tags, there is at least one label [RFC3315]; there are no compression tags, there is at least one label
of nonzero length. of nonzero length.
The client (B4) determines a value for the tunnel-endpoint-addr from The client (B4) determines a value for the tunnel-endpoint-addr from
the tunnel-endpoint-name using standard DNS resolution, as defined in the tunnel-endpoint-name using standard DNS resolution, as defined in
[RFC3596]. If the DNS response contains more than one IPv6 address, [RFC3596]. If the DNS response contains more than one IPv6 address,
the client picks only one IPv6 address and uses it as a remote tunnel the client picks only one IPv6 address and uses it as a remote tunnel
endpoint. The client MUST NOT establish more than one DS Lite tunnel endpoint. The client MUST NOT establish more than one DS-Lite tunnel
at the same time. For a redundancy and high availability discussion, at the same time. For a redundancy and high availability discussion,
see Section 7.2 "High availability" of see Section 7.2 "High availability" of [I-D.softwire-ds-lite-03].
[draft-ietf-softwire-dual-stack-lite-02].
4. DHCPv6 Server Behavior 5. DHCPv6 Server Behavior
DHCP servers must translate user input from their own specific and DHCP servers must translate user input from their own specific and
unique operator's interfaces into configuration state for the client. unique operator's interfaces into configuration state for the client.
The server MUST provide a way to configure the OPTION_DS_LITE_ADDR, The server MUST provide a way to configure the OPTION_DS_LITE_ADDR,
and SHOULD allow the operator to enter a Fully Qualified Domain Name, and SHOULD allow the operator to enter a Fully Qualified Domain Name,
upon which the server performs DNS Resolution to assemble its upon which the server performs DNS Resolution to assemble its
OPTION_DS_LITE_ADDR contents. The server MAY either provide the same OPTION_DS_LITE_ADDR contents. The server MAY either provide the same
Fully Qualified Domain Name as OPTION_DS_LITE_NAME contents, or Fully Qualified Domain Name as OPTION_DS_LITE_NAME contents, or
simply provide a distinct method of configuring it. simply provide a distinct method of configuring it.
If configured with values, DHCPv6 servers will include the DS Lite If configured with values, DHCPv6 servers will include the DS-Lite
Address and/or Name Options if either or both appear on the client's Address and/or Name options if either or both appear on the client's
Option Request Option (OPTION_ORO). RFC 3315 Section 17.2.2 Option Request Option (OPTION_ORO). RFC 3315 Section 17.2.2
[RFC3315] describes how a DHCPv6 client and server negotiate [RFC3315] describes how a DHCPv6 client and server negotiate
configuration values using the ORO. configuration values using the ORO.
A DHCPv6 server MAY NOT send either Option if it has not been A DHCPv6 server MUST NOT send either option if it has not been
explicitly requested by the client. explicitly requested by the client.
If the server is configured with an FQDN as the tunnel endpoint If the server is configured with an FQDN as the tunnel endpoint
locator, the configured FDQN value MUST contain a resolvable Fully locator, the configured FQDN value MUST contain a resolvable Fully
Qualified Domain Name, having appropriate delegations from the root, Qualified Domain Name, having appropriate delegations from the root,
and having a AAAA record locating the Softwire Concentrator. and having a AAAA record locating the Softwire Concentrator.
If OPTION_DS_LITE_NAME is being configured, the server MUST be If OPTION_DS_LITE_NAME is being configured, the server MUST be
configured to provide OPTION_DNS_SERVERS defined in [RFC3646] configured to provide OPTION_DNS_SERVERS defined in [RFC3646]
together with the DS Lite option, so that clients will be able to ask together with the DS-Lite Name option, so that clients will be able
for DNS servers locations to resolve the domain name provided in the to ask for DNS servers locations to resolve the domain name provided
DS-Lite Name DHCPv6 option. in the DS-Lite Name option.
5. DHCPv6 Client Behavior 6. DHCPv6 Client Behavior
A client that supports B4 functionality of the DS-Lite (defined in A client that supports B4 functionality of DS-Lite (defined in
[draft-ietf-softwire-dual-stack-lite-02]) MUST include [I-D.softwire-ds-lite-03]) MUST include OPTION_DS_LITE_ADDR on its
OPTION_DS_LITE_ADDR on its OPTION_ORO, and MAY include OPTION_ORO, and MAY include OPTION_DS_LITE_NAME at its option and
OPTION_DS_LITE_NAME at its option and ability. ability.
If requesting the OPTION_DS_LITE_NAME DHCPv6 Option, the client also If requesting the OPTION_DS_LITE_NAME option, the client also SHOULD
SHOULD request OPTION_DNS_SERVERS defined in [RFC3646] to be able to request OPTION_DNS_SERVERS defined in [RFC3646] to be able to resolve
resolve any received domain name. any received domain name.
If the client receives either DS-Lite Option, it MUST verify the If the client receives either DS-Lite option, it MUST verify the
option contents as described in Section 3.1 and Section 3.2. The option contents as described in Section 3 and Section 4. The client
client (B4) SHOULD establish a softwire tunnel to the tunnel- (B4) SHOULD establish a softwire tunnel to the tunnel-endpoint-addr
endpoint-addr IPv6 address it determines from either of these IPv6 address it determines from either of these options.
options.
If the client requests and receives both the OPTION_DS_LITE_ADDR and If the client requests and receives both the OPTION_DS_LITE_ADDR and
the OPTION_DS_LITE_NAME, it MUST proceed with resolving the the OPTION_DS_LITE_NAME options, it MUST proceed with resolving the
OPTION_DS_LITE_NAME. OPTION_DS_LITE_NAME.
6. Security Considerations 7. Security Considerations
This document does not present any new security issues, but as with This document does not present any new security issues, but as with
all DHCPv6-derived configuration state, it is completely possible all DHCPv6-derived configuration state, it is completely possible
that the configuration is being delivered by a third party (Man In that the configuration is being delivered by a third party (Man In
The Middle). As such, there is no basis to trust that the access the The Middle). As such, there is no basis to trust that the access the
DS-Lite Softwire connection represents can be trusted, and it should DS-Lite Softwire connection represents can be trusted, and it should
not therefore bypass any security mechanisms such as IP firewalls. not therefore bypass any security mechanisms such as IP firewalls.
RFC 3315 [RFC3315] discusses DHCPv6-related security issues. RFC 3315 [RFC3315] discusses DHCPv6-related security issues.
[draft-ietf-softwire-dual-stack-lite-02] discusses DS Lite related [I-D.softwire-ds-lite-03] discusses DS-Lite related security issues.
security issues.
7. IANA Considerations 8. IANA Considerations
IANA is requested to allocate two DHCPv6 Option codes referencing IANA is requested to allocate two DHCPv6 option codes referencing
this document. One delineating OPTION_DS_LITE_ADDR, and one this document. One delineating OPTION_DS_LITE_ADDR, and one
delineating OPTION_DS_LITE_NAME. delineating OPTION_DS_LITE_NAME.
8. Acknowledgements 9. Acknowledgements
Authors would like to thank Alain Durand, Rob Austein and Dave Thaler Authors would like to thank Alain Durand, Rob Austein, Dave Thaler
for their valuable feedback and suggestions. and Paul Selkirk for their valuable feedback and suggestions.
9. Normative References 10. Normative References
[I-D.softwire-ds-lite-03]
Durand, A., Ed., "Dual-stack lite broadband deployments
post IPv4 exhaustion",
draft-ietf-softwire-dual-stack-lite-03 (work in progress),
February 2010.
[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.
[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.
[RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
"DNS Extensions to Support IP Version 6", RFC 3596, "DNS Extensions to Support IP Version 6", RFC 3596,
October 2003. October 2003.
[RFC3646] Droms, R., "DNS Configuration options for Dynamic Host [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
December 2003. December 2003.
[draft-ietf-softwire-dual-stack-lite-02]
Durand, A., Ed., "Dual-stack lite broadband deployments
post IPv4 exhaustion", October 2009.
Authors' Addresses Authors' Addresses
David W. Hankins David W. Hankins
Internet Systems Consortium, Inc. Internet Systems Consortium, Inc.
950 Charter Street 950 Charter Street
Redwood City, CA 94063 Redwood City, CA 94063
US US
Phone: +1 650 423 1307 Phone: +1 650 423 1307
Email: David_Hankins@isc.org Email: David_Hankins@isc.org
 End of changes. 51 change blocks. 
143 lines changed or deleted 117 lines changed or added

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