draft-ietf-v6ops-6204bis-07.txt   draft-ietf-v6ops-6204bis-08.txt 
Network Working Group H. Singh Network Working Group H. Singh
Internet-Draft W. Beebee Internet-Draft W. Beebee
Obsoletes: 6204 (if approved) Cisco Systems, Inc. Obsoletes: 6204 (if approved) Cisco Systems, Inc.
Intended status: Informational C. Donley Intended status: Informational C. Donley
Expires: September 9, 2012 CableLabs Expires: October 8, 2012 CableLabs
B. Stark B. Stark
AT&T AT&T
O. Troan, Ed. O. Troan, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
March 8, 2012 April 6, 2012
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-6204bis-07 draft-ietf-v6ops-6204bis-08
Abstract Abstract
This document specifies requirements for an IPv6 Customer Edge (CE) This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. The document also covers IP transition of IPv6 hosts attached to it. The document also covers IP transition
technologies. Two transition technologies in RFC 5969's 6rd and RFC technologies. Two transition technologies in RFC 5969's 6rd and RFC
6333's DS-Lite. are covered in the document. The document obsoletes 6333's DS-Lite are covered in the document. The document obsoletes
RFC 6204, if approved. RFC 6204, if approved.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on September 9, 2012. This Internet-Draft will expire on October 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 2, line 29 skipping to change at page 2, line 29
3.1. Current IPv4 End-User Network Architecture . . . . . . . . 4 3.1. Current IPv4 End-User Network Architecture . . . . . . . . 4
3.2. IPv6 End-User Network Architecture . . . . . . . . . . . . 5 3.2. IPv6 End-User Network Architecture . . . . . . . . . . . . 5
3.2.1. Local Communication . . . . . . . . . . . . . . . . . 6 3.2.1. Local Communication . . . . . . . . . . . . . . . . . 6
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7 4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7
4.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . . 7 4.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . . 7
4.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . . 11 4.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . . 11
4.4. Transition Technologies Support . . . . . . . . . . . . . 13 4.4. Transition Technologies Support . . . . . . . . . . . . . 13
4.4.1. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.4.1. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 14 4.4.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 14
4.5. Security Considerations . . . . . . . . . . . . . . . . . 14 4.5. Security Considerations . . . . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 8.1. Normative References . . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 19 Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document defines basic IPv6 features for a residential or small- This document defines basic IPv6 features for a residential or small-
office router, referred to as an IPv6 CE router. Typically, these office router, referred to as an IPv6 CE router. Typically, these
routers also support IPv4. routers also support IPv4.
Mixed environments of dual-stack hosts and IPv6-only hosts (behind Mixed environments of dual-stack hosts and IPv6-only hosts (behind
skipping to change at page 3, line 28 skipping to change at page 3, line 28
of its LAN interfaces, and fetches other configuration information of its LAN interfaces, and fetches other configuration information
from the service provider network. Automatic provisioning of more from the service provider network. Automatic provisioning of more
complex topology than a single router with multiple LAN interfaces is complex topology than a single router with multiple LAN interfaces is
out of scope for this document. out of scope for this document.
See [RFC4779] for a discussion of options available for deploying See [RFC4779] for a discussion of options available for deploying
IPv6 in service provider access networks. IPv6 in service provider access networks.
The document also covers IP transition technologies. Two transition The document also covers IP transition technologies. Two transition
technologies in 6rd [RFC5969] and DS-Lite [RFC6333] are covered in technologies in 6rd [RFC5969] and DS-Lite [RFC6333] are covered in
the document. At the time of writing this document these were the the document.
only two transition technologies available in RFC form to be included
in this document.
1.1. Requirements Language 1.1. Requirements Language
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].
2. Terminology 2. Terminology
End-User Network one or more links attached to the IPv6 CE End-User Network one or more links attached to the IPv6 CE
skipping to change at page 4, line 28 skipping to change at page 4, line 24
provider specifically offers Internet provider specifically offers Internet
access using IPv6, and may also offer IPv4 access using IPv6, and may also offer IPv4
Internet access. The service provider can Internet access. The service provider can
provide such access over a variety of provide such access over a variety of
different transport methods such as DSL, different transport methods such as DSL,
cable, wireless, and others. cable, wireless, and others.
WAN Interface an IPv6 CE router's attachment to a link WAN Interface an IPv6 CE router's attachment to a link
used to provide connectivity to the service used to provide connectivity to the service
provider network; example link technologies provider network; example link technologies
include Ethernets (simple or bridged), PPP include Ethernet (simple or bridged), PPP
links, Frame Relay, or ATM networks, as links, Frame Relay, or ATM networks, as
well as Internet-layer (or higher-layer) well as Internet-layer (or higher-layer)
"tunnels", such as tunnels over IPv4 or "tunnels", such as tunnels over IPv4 or
IPv6 itself. IPv6 itself.
3. Architecture 3. Architecture
3.1. Current IPv4 End-User Network Architecture 3.1. Current IPv4 End-User Network Architecture
An end-user network will likely support both IPv4 and IPv6. It is An end-user network will likely support both IPv4 and IPv6. It is
skipping to change at page 8, line 34 skipping to change at page 8, line 34
default router(s) and install default route(s) in its routing default router(s) and install default route(s) in its routing
table with the discovered router's address as the next hop. table with the discovered router's address as the next hop.
W-4: The router MUST act as a requesting router for the purposes of W-4: The router MUST act as a requesting router for the purposes of
DHCPv6 prefix delegation ([RFC3633]). DHCPv6 prefix delegation ([RFC3633]).
W-5: The IPv6 CE router MUST use a persistent DHCP Unique Identifier W-5: The IPv6 CE router MUST use a persistent DHCP Unique Identifier
(DUID) for DHCPv6 messages. The DUID MUST NOT change between (DUID) for DHCPv6 messages. The DUID MUST NOT change between
network interface resets or IPv6 CE router reboots. network interface resets or IPv6 CE router reboots.
W-6: The WAN interface of the CE router SHOULD support an IPv4 PCP W-6: The WAN interface of the CE router SHOULD support a PCP client
client as specified in [I-D.ietf-pcp-base] for use by as specified in [I-D.ietf-pcp-base] for use by applications on
applications on the CE Router. This document takes no position the CE Router. The PCP client SHOULD follow the procedure
on whether such functionality is enabled by default or specified in Section 8.1 of [I-D.ietf-pcp-base] to discover its
mechanisms by which users would configure the functionality. PCP server. This document takes no position on whether such
functionality is enabled by default or mechanisms by which
users would configure the functionality. Handling PCP requests
from PCP clients in the LAN side of the CE Router is out of
scope.
Link-layer requirements: Link-layer requirements:
WLL-1: If the WAN interface supports Ethernet encapsulation, then WLL-1: If the WAN interface supports Ethernet encapsulation, then
the IPv6 CE router MUST support IPv6 over Ethernet [RFC2464]. the IPv6 CE router MUST support IPv6 over Ethernet [RFC2464].
WLL-2: If the WAN interface supports PPP encapsulation, the IPv6 CE WLL-2: If the WAN interface supports PPP encapsulation, the IPv6 CE
router MUST support IPv6 over PPP [RFC5072]. router MUST support IPv6 over PPP [RFC5072].
WLL-3: If the WAN interface supports PPP encapsulation, in a dual- WLL-3: If the WAN interface supports PPP encapsulation, in a dual-
stack environment with IPCP and IPV6CP running over one PPP stack environment with IPCP and IPV6CP running over one PPP
logical channel, the Network Control Protocols (NCP's) MUST logical channel, the Network Control Protocols (NCP's) MUST
be treated as independent of each other and start and be treated as independent of each other and start and
terminate independently. terminate independently.
Address assignment requirements: Address assignment requirements:
WAA-1: The IPv6 CE router MUST support Stateless Address WAA-1: The IPv6 CE router MUST support Stateless Address
Autoconfiguration (SLAAC) [RFC4862]. Autoconfiguration (SLAAC) [RFC4862].
WAA-2: The IPv6 CE router MUST follow the recommendations in Section WAA-2: The IPv6 CE router MUST follow the recommendations in
4 of [RFC5942], and in particular the handling of the L flag Section 4 of [RFC5942], and in particular the handling of
in the Router Advertisement Prefix Information option. the L flag in the Router Advertisement Prefix Information
option.
WAA-3: The IPv6 CE router MUST support DHCPv6 [RFC3315] client WAA-3: The IPv6 CE router MUST support DHCPv6 [RFC3315] client
behavior. behavior.
WAA-4: The IPv6 CE router MUST be able to support the following WAA-4: The IPv6 CE router MUST be able to support the following
DHCPv6 options: IA_NA, Reconfigure Accept [RFC3315], and DHCPv6 options: IA_NA, Reconfigure Accept [RFC3315], and
DNS_SERVERS [RFC3646]. The IPv6 CE router SHOULD be able to DNS_SERVERS [RFC3646]. The IPv6 CE router SHOULD be able to
support the DNS Search List DNSSL option as specified in support the DNS Search List DNSSL option as specified in
[RFC3646]. [RFC3646].
WAA-5: The IPv6 CE router SHOULD support the DHCPv6 Simple Network WAA-5: The IPv6 CE router SHOULD implement the Simple Network Time
Time Protocol (SNTP) option [RFC4075] and the Information Protocol (SNTP) as specified in [RFC2030]. If the CE router
Refresh Time option [RFC4242]. implements SNTP, it requests the SNTP option [RFC4075] and
uses the received list of servers as primary time reference,
unless explicitly configured otherwise.
WAA-6: If the IPv6 CE router receives a Router Advertisement message WAA-6: If the IPv6 CE router receives a Router Advertisement
(described in [RFC4861]) with the M flag set to 1, the IPv6 message (described in [RFC4861]) with the M flag set to 1,
CE router MUST do DHCPv6 address assignment (request an IA_NA the IPv6 CE router MUST do DHCPv6 address assignment
option). (request an IA_NA option).
WAA-7: If the IPv6 CE router does not acquire global IPv6 WAA-7: If the IPv6 CE router does not acquire global IPv6
address(es) from either SLAAC or DHCPv6, then it MUST create address(es) from either SLAAC or DHCPv6, then it MUST create
global IPv6 address(es) from its delegated prefix(es) and global IPv6 address(es) from its delegated prefix(es) and
configure those on one of its internal virtual network configure those on one of its internal virtual network
interfaces, unless configured to require a global IPv6 interfaces, unless configured to require a global IPv6
address on the WAN interface. address on the WAN interface.
WAA-8: The CE Router MUST support the DHCPv6 SOL_MAX_RT option WAA-8: The CE Router MUST support the DHCPv6 SOL_MAX_RT option
[I-D.droms-dhc-dhcpv6-maxsolrt-update] in a received DHCPv6 [I-D.droms-dhc-dhcpv6-maxsolrt-update] in a received DHCPv6
Advertise or Reply message and set its internal SOL_MAX_RT Advertise or Reply message and set its internal SOL_MAX_RT
parameter to the value contained in the SOL_MAX_RT option. parameter to the value contained in the SOL_MAX_RT option.
WAA-9: As a router, the IPv6 CE router MUST follow the weak host WAA-9: As a router, the IPv6 CE router MUST follow the weak host
(Weak ES) model [RFC1122]. When originating packets from an (Weak ES) model [RFC1122]. When originating packets from an
interface, it will use a source address from another one of interface, it will use a source address from another one of
its interfaces if the outgoing interface does not have an its interfaces if the outgoing interface does not have an
address of suitable scope. address of suitable scope.
WAA-10: The IPv6 CE router SHOULD implement the Information Refresh
Time option and associated client behavior as specified in
[RFC4242].
Prefix delegation requirements: Prefix delegation requirements:
WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation
requesting router behavior as specified in [RFC3633] (IA_PD requesting router behavior as specified in [RFC3633] (IA_PD
option). The IPv6 CE Router SHOULD support the option).
[I-D.ietf-dhc-pd-exclude] PD-Exclude option.
WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating
router the size of the prefix it requires. If so, it MUST router the size of the prefix it requires. If so, it MUST
ask for a prefix large enough to assign one /64 for each of ask for a prefix large enough to assign one /64 for each of
its interfaces, rounded up to the nearest nibble, and SHOULD its interfaces, rounded up to the nearest nibble, and SHOULD
be configurable to ask for more. be configurable to ask for more.
WPD-3: The IPv6 CE router MUST be prepared to accept a delegated WPD-3: The IPv6 CE router MUST be prepared to accept a delegated
prefix size different from what is given in the hint. If the prefix size different from what is given in the hint. If the
delegated prefix is too small to address all of its delegated prefix is too small to address all of its
interfaces, the IPv6 CE router SHOULD log a system management interfaces, the IPv6 CE router SHOULD log a system management
error. error. [RFC6177] covers the recommendations for service
providers for prefix allocation sizes.
WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix
delegation when either the M or O flags are set to 1 in a delegation when either the M or O flags are set to 1 in a
received Router Advertisement message. received Router Advertisement message.
WPD-5: If the delegated prefix(es) are aggregate route(s) of WPD-5: If the delegated prefix(es) are aggregate route(s) of
multiple, more-specific routes, the IPv6 CE router MUST multiple, more-specific routes, the IPv6 CE router MUST
discard packets that match the aggregate route(s), but not discard packets that match the aggregate route(s), but not
any of the more-specific routes. In other words, the next any of the more-specific routes. In other words, the next
hop for the aggregate route(s) should be the null hop for the aggregate route(s) should be the null
skipping to change at page 10, line 44 skipping to change at page 11, line 14
(a) The IPv6 CE router SHOULD send an ICMPv6 Destination (a) The IPv6 CE router SHOULD send an ICMPv6 Destination
Unreachable message in accordance with Section 3.1 of Unreachable message in accordance with Section 3.1 of
[RFC4443] back to the source of the packet, if the [RFC4443] back to the source of the packet, if the
packet is to be dropped due to this rule. packet is to be dropped due to this rule.
WPD-6: If the IPv6 CE router requests both an IA_NA and an IA_PD WPD-6: If the IPv6 CE router requests both an IA_NA and an IA_PD
option in DHCPv6, it MUST accept an IA_PD option in DHCPv6 option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
Advertise/Reply messages, even if the message does not Advertise/Reply messages, even if the message does not
contain any addresses, unless configured to only obtain its contain any addresses, unless configured to only obtain its
WAN IPv6 address via DHCPv6. WAN IPv6 address via DHCPv6. See
[I-D.troan-dhc-dhcpv6-stateful-issues]
WPD-7: By default, an IPv6 CE router MUST NOT initiate any dynamic WPD-7: By default, an IPv6 CE router MUST NOT initiate any dynamic
routing protocol on its WAN interface. routing protocol on its WAN interface.
WPD-8: The IPv6 CE Router SHOULD support the
[I-D.ietf-dhc-pd-exclude] PD-Exclude option.
4.3. LAN-Side Configuration 4.3. LAN-Side Configuration
The IPv6 CE router distributes configuration information obtained The IPv6 CE router distributes configuration information obtained
during WAN interface provisioning to IPv6 hosts and assists IPv6 during WAN interface provisioning to IPv6 hosts and assists IPv6
hosts in obtaining IPv6 addresses. It also supports connectivity of hosts in obtaining IPv6 addresses. It also supports connectivity of
these devices in the absence of any working WAN interface. these devices in the absence of any working WAN interface.
An IPv6 CE router is expected to support an IPv6 end-user network and An IPv6 CE router is expected to support an IPv6 end-user network and
IPv6 hosts that exhibit the following characteristics: IPv6 hosts that exhibit the following characteristics:
skipping to change at page 13, line 36 skipping to change at page 14, line 7
delegation to sites, stateless operation, simple provisioning, and delegation to sites, stateless operation, simple provisioning, and
service that is equivalent to native IPv6 at the sites that are service that is equivalent to native IPv6 at the sites that are
served by the mechanism. It is expected that such traffic is served by the mechanism. It is expected that such traffic is
forwarded over the CE Router's native IPv4 WAN interface, and not forwarded over the CE Router's native IPv4 WAN interface, and not
encapsulated in another tunnel. encapsulated in another tunnel.
The CE Router SHOULD support 6rd functionality. If 6rd is supported, The CE Router SHOULD support 6rd functionality. If 6rd is supported,
it MUST be implemented according to [RFC5969]. The following CE it MUST be implemented according to [RFC5969]. The following CE
Requirements also apply: Requirements also apply:
.
6rd requirements: 6rd requirements:
6RD-1: The IPv6 CE router MUST support 6rd configuration via the 6rd 6RD-1: The IPv6 CE router MUST support 6rd configuration via the 6rd
DHCPv4 Option (212). If the CE router has obtained an IPv4 DHCPv4 Option (212). If the CE router has obtained an IPv4
network address through some other means such PPP, it SHOULD network address through some other means such as PPP, it
use the DHCPINFORM request message [RFC2131] to request the SHOULD use the DHCPINFORM request message [RFC2131] to
6rd DHCPv4 Option. The IPv6 CE router MAY use other request the 6rd DHCPv4 Option. The IPv6 CE router MAY use
mechanisms to configure 6rd parameters. Such mechanisms are other mechanisms to configure 6rd parameters. Such
outside the scope of this document. mechanisms are outside the scope of this document.
6RD-2: If the IPv6 CE router is capable of automated configuration 6RD-2: If the IPv6 CE router is capable of automated configuration
of IPv4 through IPCP (i.e., over a PPP connection), it MUST of IPv4 through IPCP (i.e., over a PPP connection), it MUST
support user-entered configuration of 6rd. support user-entered configuration of 6rd.
6RD-3: If the CE router supports configuration mechanisms other than 6RD-3: If the CE router supports configuration mechanisms other than
the 6rd DHCPv4 Option 212 (user-entered, TR-69, etc.), the CE the 6rd DHCPv4 Option 212 (user-entered, TR-69, etc.), the CE
router MUST support 6rd in "hub and spoke" mode. 6rd in "hub router MUST support 6rd in "hub and spoke" mode. 6rd in "hub
and spoke" requires all IPv6 traffic to go to the 6rd Border and spoke" requires all IPv6 traffic to go to the 6rd Border
Relay. In effect, this requirement removes the "direct Relay. In effect, this requirement removes the "direct
connect to 6rd" route defined in Section 7.1.1 of [RFC5969]. connect to 6rd" route defined in Section 7.1.1 of [RFC5969].
6RD-4: Per [RFC3704], Section 4.3, the CE router MUST send traffic
using a prefix learned via 6rd over the 6rd tunnel.
6RD-5: The IPv6 CE router MUST support two operational modes:
different prefixes on 6rd and native interfaces or identical
prefixes on 6rd and native interfaces.
6RD-6: By default, the IPv6 CE router MUST prefer a native IPv6
interface over a 6rd virtual interface.
6RD-7: The IPv6 CE router SHOULD support independent WAN interface
configuration for 6rd and native IPv6.
4.4.2. Dual-Stack Lite (DS-Lite) 4.4.2. Dual-Stack Lite (DS-Lite)
Dual-Stack Lite [RFC6333] enables both continued support for IPv4 Dual-Stack Lite [RFC6333] enables both continued support for IPv4
services and incentives for the deployment of IPv6. It also de- services and incentives for the deployment of IPv6. It also de-
couples IPv6 deployment in the Service Provider network from the rest couples IPv6 deployment in the Service Provider network from the rest
of the Internet, making incremental deployment easier. Dual-Stack of the Internet, making incremental deployment easier. Dual-Stack
Lite enables a broadband service provider to share IPv4 addresses Lite enables a broadband service provider to share IPv4 addresses
among customers by combining two well-known technologies: IP in IP among customers by combining two well-known technologies: IP in IP
(IPv4-in-IPv6) and Network Address Translation (NAT). It is expected (IPv4-in-IPv6) and Network Address Translation (NAT). It is expected
that DS-Lite traffic is forwarded over the CE Router's native IPv6 that DS-Lite traffic is forwarded over the CE Router's native IPv6
WAN interface, and not encapsulated in another tunnel. WAN interface, and not encapsulated in another tunnel.
The IPv6 CE Router SHOULD implement DS-Lite functionality. If DS- The IPv6 CE Router SHOULD implement DS-Lite functionality. If DS-
Lite is supported, it MUST be implemented according to [RFC6333]. Lite is supported, it MUST be implemented according to [RFC6333].
The following CE Router requirements also apply: This document takes no position on simultaneous operation of Dual-
Stack Lite and native IPv4. The following CE Router requirements
also apply:
WAN requirements: WAN requirements:
DLW-1: The CE Router MUST support DS-Lite via the DS-Lite DHCPv6 DLW-1: The CE Router MUST support DS-Lite via the DS-Lite DHCPv6
option [RFC6334]. The IPv6 CE Router MAY use other option [RFC6334]. The IPv6 CE Router MAY use other
mechanisms to configure DS-Lite parameters. Such mechanisms mechanisms to configure DS-Lite parameters. Such mechanisms
are outside the scope of this document. are outside the scope of this document.
DLW-2: IPv6 CE Router MUST NOT perform IPv4 Network Address DLW-2: IPv6 CE Router MUST NOT perform IPv4 Network Address
Translation (NAT) on IPv4 traffic encapsulated using DS-Lite. Translation (NAT) on IPv4 traffic encapsulated using DS-Lite.
skipping to change at page 15, line 28 skipping to change at page 16, line 14
5. IANA Considerations 5. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
6. Acknowledgements 6. Acknowledgements
Thanks to the following people (in alphabetical order) for their Thanks to the following people (in alphabetical order) for their
guidance and feedback: guidance and feedback:
Mikael Abrahamsson, Tore Anderson, Merete Asak, Scott Beuker, Mohamed Mikael Abrahamsson, Tore Anderson, Merete Asak, Rajiv Asati, Scott
Boucadair, Rex Bullinger, Brian Carpenter, Tassos Chatzithomaoglou, Beuker, Mohamed Boucadair, Rex Bullinger, Brian Carpenter, Tassos
Lorenzo Colitti, Remi Denis-Courmont, Gert Doering, Alain Durand, Chatzithomaoglou, Lorenzo Colitti, Remi Denis-Courmont, Gert Doering,
Katsunori Fukuoka, Tony Hain, Thomas Herbst, Kevin Johns, Erik Kline, Alain Durand, Katsunori Fukuoka, Tony Hain, Thomas Herbst, Ray
Stephen Kramer, Victor Kuarsingh, Francois-Xavier Le Bail, Arifumi Hunter, Kevin Johns, Erik Kline, Stephen Kramer, Victor Kuarsingh,
Matsumoto, David Miles, Shin Miyakawa, Jean-Francois Mule, Michael Francois-Xavier Le Bail, Arifumi Matsumoto, David Miles, Shin
Newbery, Carlos Pignataro, John Pomeroy, Antonio Querubin, Hiroki Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Pignataro, John
Sato, Teemu Savolainen, Matt Schmitt, David Thaler, Mark Townsley, Pomeroy, Antonio Querubin, Daniel Roesen, Hiroki Sato, Teemu
Bernie Volz, Dan Wing, James Woodyatt, Carl Wuyts, and Cor Zwart. Savolainen, Matt Schmitt, David Thaler, Mark Townsley, Bernie Volz,
Dan Wing, James Woodyatt, Carl Wuyts, and Cor Zwart.
This document is based in part on CableLabs' eRouter specification. This document is based in part on CableLabs' eRouter specification.
The authors wish to acknowledge the additional contributors from the The authors wish to acknowledge the additional contributors from the
eRouter team: eRouter team:
Ben Bekele, Amol Bhagwat, Ralph Brown, Eduardo Cardona, Margo Dolas, Ben Bekele, Amol Bhagwat, Ralph Brown, Eduardo Cardona, Margo Dolas,
Toerless Eckert, Doc Evans, Roger Fish, Michelle Kuska, Diego Toerless Eckert, Doc Evans, Roger Fish, Michelle Kuska, Diego
Mazzola, John McQueen, Harsh Parandekar, Michael Patrick, Saifur Mazzola, John McQueen, Harsh Parandekar, Michael Patrick, Saifur
Rahman, Lakshmi Raman, Ryan Ross, Ron da Silva, Madhu Sudan, Dan Rahman, Lakshmi Raman, Ryan Ross, Ron da Silva, Madhu Sudan, Dan
Torbet, and Greg White. Torbet, and Greg White.
skipping to change at page 16, line 28 skipping to change at page 17, line 12
draft-droms-dhc-dhcpv6-maxsolrt-update-00 (work in draft-droms-dhc-dhcpv6-maxsolrt-update-00 (work in
progress), November 2011. progress), November 2011.
[I-D.ietf-dhc-pd-exclude] [I-D.ietf-dhc-pd-exclude]
Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan,
"Prefix Exclude Option for DHCPv6-based Prefix "Prefix Exclude Option for DHCPv6-based Prefix
Delegation", draft-ietf-dhc-pd-exclude-04 (work in Delegation", draft-ietf-dhc-pd-exclude-04 (work in
progress), December 2011. progress), December 2011.
[I-D.ietf-pcp-base] [I-D.ietf-pcp-base]
Cheshire, S., Boucadair, M., Selkirk, P., Wing, D., and R. Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P.
Penno, "Port Control Protocol (PCP)", Selkirk, "Port Control Protocol (PCP)",
draft-ietf-pcp-base-23 (work in progress), February 2012. draft-ietf-pcp-base-24 (work in progress), March 2012.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
[RFC2030] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", RFC 2030, October 1996.
[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.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", RFC 2464, December 1998. Networks", RFC 2464, December 1998.
[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
skipping to change at page 17, line 13 skipping to change at page 17, line 47
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 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.
[RFC3704] Baker, F. and P. Savola, "Ingress Filtering for Multihomed
Networks", BCP 84, RFC 3704, March 2004.
[RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol
(DHCP) Service for IPv6", RFC 3736, April 2004. (DHCP) Service for IPv6", RFC 3736, April 2004.
[RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP) [RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP)
Configuration Option for DHCPv6", RFC 4075, May 2005. Configuration Option for DHCPv6", RFC 4075, May 2005.
[RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and
More-Specific Routes", RFC 4191, November 2005. More-Specific Routes", RFC 4191, November 2005.
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
skipping to change at page 18, line 25 skipping to change at page 19, line 14
[RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4
Infrastructures (6rd) -- Protocol Specification", Infrastructures (6rd) -- Protocol Specification",
RFC 5969, August 2010. RFC 5969, August 2010.
[RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in
Customer Premises Equipment (CPE) for Providing Customer Premises Equipment (CPE) for Providing
Residential IPv6 Internet Service", RFC 6092, Residential IPv6 Internet Service", RFC 6092,
January 2011. January 2011.
[RFC6177] Narten, T., Huston, G., and L. Roberts, "IPv6 Address
Assignment to End Sites", BCP 157, RFC 6177, March 2011.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, August 2011. Exhaustion", RFC 6333, August 2011.
[RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration [RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite", Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite",
RFC 6334, August 2011. RFC 6334, August 2011.
[RFC6434] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node [RFC6434] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node
Requirements", RFC 6434, December 2011. Requirements", RFC 6434, December 2011.
8.2. Informative References 8.2. Informative References
[I-D.troan-dhc-dhcpv6-stateful-issues]
Troan, O. and B. Volz, "Issues with multiple stateful
DHCPv6 options", draft-troan-dhc-dhcpv6-stateful-issues-00
(work in progress), March 2012.
[MULTIHOMING-WITHOUT-NAT] [MULTIHOMING-WITHOUT-NAT]
Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T., Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T.,
and D. Wing, "IPv6 Multihoming without Network Address and D. Wing, "IPv6 Multihoming without Network Address
Translation", Work in Progress, December 2010. Translation", Work in Progress, December 2010.
[RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", RFC 6144, March 2011. IPv4/IPv6 Translation", RFC 6144, March 2011.
[UPnP-IGD] [UPnP-IGD]
UPnP Forum, "Universal Plug and Play (UPnP) Internet UPnP Forum, "Universal Plug and Play (UPnP) Internet
 End of changes. 33 change blocks. 
76 lines changed or deleted 117 lines changed or added

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