draft-ietf-v6ops-ipv6-cpe-router-09.txt   rfc6204.txt 
Internet Engineering Task Force H. Singh Internet Engineering Task Force (IETF) H. Singh
Internet-Draft W. Beebee Request for Comments: 6204 W. Beebee
Intended status: Informational Cisco Systems, Inc. Category: Informational Cisco Systems, Inc.
Expires: June 23, 2011 C. Donley ISSN: 2070-1721 C. Donley
CableLabs CableLabs
B. Stark B. Stark
AT&T AT&T
O. Troan, Ed. O. Troan, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
December 20, 2010 April 2011
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-ipv6-cpe-router-09
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. of IPv6 hosts attached to it.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on June 23, 2011. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6204.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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 Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language ......................................3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology .....................................................3
3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Architecture ....................................................4
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 .........................4
3.2.1. Local communication . . . . . . . . . . . . . . . . . 6 3.2.1. Local Communication .................................6
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Requirements ....................................................6
4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7 4.1. General Requirements .......................................6
4.2. WAN Side Configuration . . . . . . . . . . . . . . . . . . 7 4.2. WAN-Side Configuration .....................................7
4.3. LAN Side Configuration . . . . . . . . . . . . . . . . . . 10 4.3. LAN-Side Configuration ....................................11
4.4. Security Considerations . . . . . . . . . . . . . . . . . 13 4.4. Security Considerations ...................................13
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 5. Acknowledgements ...............................................13
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Contributors ...................................................14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. References .....................................................14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7.1. Normative References ......................................14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 14 7.2. Informative References ....................................16
8.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
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
the CE router) can be more complex if the IPv6-only devices are using the CE router) can be more complex if the IPv6-only devices are using
a translator to access IPv4 servers [I-D.ietf-behave-v6v4-framework]. a translator to access IPv4 servers [RFC6144]. Support for such
Support for such mixed environments is not in scope of this document. mixed environments is not in scope of this document.
This document specifies how an IPv6 CE router automatically This document specifies how an IPv6 CE router automatically
provisions its WAN interface, acquires address space for provisioning provisions its WAN interface, acquires address space for provisioning
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.
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
router that connect IPv6 hosts. router that connect IPv6 hosts.
IPv6 Customer Edge router a node intended for home or small office IPv6 Customer Edge Router a node intended for home or small-office
use which forwards IPv6 packets not use that forwards IPv6 packets not
explicitly addressed to itself. The IPv6 explicitly addressed to itself. The IPv6
CE router connects the end-user network to CE router connects the end-user network to
a service provider network. a service provider network.
IPv6 host any device implementing an IPv6 stack IPv6 Host any device implementing an IPv6 stack
receiving IPv6 connectivity through the receiving IPv6 connectivity through the
IPv6 CE router IPv6 CE router.
LAN interface an IPv6 CE router's attachment to a link in LAN Interface an IPv6 CE router's attachment to a link in
the end-user network. Examples are the end-user network. Examples are
Ethernets (simple or bridged), 802.11 Ethernets (simple or bridged), 802.11
wireless or other LAN technologies. An wireless, or other LAN technologies. An
IPv6 CE router may have one or more network IPv6 CE router may have one or more
layer LAN Interfaces. network-layer LAN interfaces.
Service Provider an entity that provides access to the Service Provider an entity that provides access to the
Internet. In this document, a Service Internet. In this document, a service
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 Ethernets (simple or bridged), PPP
links, Frame Relay, or ATM networks as well links, Frame Relay, or ATM networks, as
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
not expected that an end-user will change their existing network not expected that an end-user will change their existing network
topology with the introduction of IPv6. There are some differences topology with the introduction of IPv6. There are some differences
in how IPv6 works and is provisioned which has implications for the in how IPv6 works and is provisioned; these differences have
network architecture. A typical IPv4 end-user network consist of a implications for the network architecture. A typical IPv4 end-user
"plug and play" router with NAT functionality and a single link network consists of a "plug and play" router with NAT functionality
behind it, connected to the Service Provider network. and a single link behind it, connected to the service provider
network.
A typical IPv4 NAT deployment by default blocks all incoming A typical IPv4 NAT deployment by default blocks all incoming
connections. Opening of ports is typically allowed using UPnP IGD connections. Opening of ports is typically allowed using a Universal
[UPnP-IGD] or some other firewall control protocol. Plug and Play Internet Gateway Device (UPnP IGD) [UPnP-IGD] or some
other firewall control protocol.
Another consequence of using private address space in the end-user Another consequence of using private address space in the end-user
network is that it provides stable addressing, i.e. it never changes network is that it provides stable addressing; i.e., it never changes
even when you change Service Providers, and the addresses are always even when you change service providers, and the addresses are always
there even when the WAN interface is down or the customer edge router there even when the WAN interface is down or the customer edge router
has not yet been provisioned. has not yet been provisioned.
Rewriting addresses on the edge of the network also allows for some Rewriting addresses on the edge of the network also allows for some
rudimentary multi-homing; even though using NATs for multi-homing rudimentary multihoming, even though using NATs for multihoming does
does not preserve connections during a fail-over event [RFC4864]. not preserve connections during a fail-over event [RFC4864].
Many existing routers support dynamic routing, and advanced end users Many existing routers support dynamic routing, and advanced end-users
can build arbitrary, complex networks using manual configuration of can build arbitrary, complex networks using manual configuration of
address prefixes combined with a dynamic routing protocol. address prefixes combined with a dynamic routing protocol.
3.2. IPv6 End-user Network Architecture 3.2. IPv6 End-User Network Architecture
The end-user network architecture for IPv6 should provide equivalent The end-user network architecture for IPv6 should provide equivalent
or better capabilities and functionality than the current IPv4 or better capabilities and functionality than the current IPv4
architecture. architecture.
The end-user network is a stub network. Figure 1 illustrates the The end-user network is a stub network. Figure 1 illustrates the
model topology for the end-user network. model topology for the end-user network.
An example of a typical end-user network. +-------+-------+ \
| Service | \
+-------+-------+ \ | Provider | | Service
| Service | \ | Router | | Provider
| Provider | | Service +-------+-------+ | network
| Router | | Provider | /
+-------+-------+ | network | Customer /
| / | Internet connection /
| Customer /
| Internet connection /
| |
+------+--------+ \ +------+--------+ \
| IPv6 | \ | IPv6 | \
| Customer Edge | \ | Customer Edge | \
| Router | / | Router | /
+---+-------+-+-+ / +---+-------+-+-+ /
Network A | | Network B | End-User Network A | | Network B | End-User
---+-------------+----+- --+--+-------------+--- |network(s) ---+-------------+----+- --+--+-------------+--- | network(s)
| | | | \ | | | | \
+----+-----+ +-----+----+ +----+-----+ +-----+----+ \ +----+-----+ +-----+----+ +----+-----+ +-----+----+ \
|IPv6 Host | |IPv6 Host | | IPv6 Host| |IPv6 Host | / |IPv6 Host | |IPv6 Host | | IPv6 Host| |IPv6 Host | /
| | | | | | | | / | | | | | | | | /
+----------+ +-----+----+ +----------+ +----------+/ +----------+ +-----+----+ +----------+ +----------+ /
Figure 1 Figure 1: An Example of a Typical End-User Network
This architecture describes the: This architecture describes the:
o Basic capabilities of an IPv6 CE router o Basic capabilities of an IPv6 CE router
o Provisioning of the WAN interface connecting to the Service o Provisioning of the WAN interface connecting to the service
Provider provider
o Provisioning of the LAN interfaces o Provisioning of the LAN interfaces
For IPv6 multicast traffic the IPv6 CE router may act as an Multicast For IPv6 multicast traffic, the IPv6 CE router may act as a Multicast
Listener Discovery (MLD) proxy [RFC4605] and may support a dynamic Listener Discovery (MLD) proxy [RFC4605] and may support a dynamic
multicast routing protocol. multicast routing protocol.
The IPv6 CE router may be manually configured in an arbitrary The IPv6 CE router may be manually configured in an arbitrary
topology with a dynamic routing protocol. Automatic provisioning and topology with a dynamic routing protocol. Automatic provisioning and
configuration is described for a single IPv6 CE router only. configuration are described for a single IPv6 CE router only.
3.2.1. Local communication 3.2.1. Local Communication
Link-local IPv6 addresses are used by hosts communicating on a single Link-local IPv6 addresses are used by hosts communicating on a single
link. Unique Local IPv6 Unicast Addresses (ULA) [RFC4193] are used link. Unique Local IPv6 Unicast Addresses (ULAs) [RFC4193] are used
by hosts communicating within the End-user Network across multiple by hosts communicating within the end-user network across multiple
links, but without requiring the application to use a globally links, but without requiring the application to use a globally
routable address. The IPv6 CE router defaults to acting as the routable address. The IPv6 CE router defaults to acting as the
demarcation point between two networks by providing a ULA boundary, a demarcation point between two networks by providing a ULA boundary, a
multicast zone boundary and ingress and egress traffic filters. multicast zone boundary, and ingress and egress traffic filters.
A dual-stacked host is multi-homed to IPv4 and IPv6 networks. The A dual-stack host is multihomed to IPv4 and IPv6 networks. The IPv4
IPv4 and IPv6 topologies may not be congruent and different addresses and IPv6 topologies may not be congruent, and different addresses may
may have different reachability, e.g. ULA addresses. A host stack have different reachability, e.g., ULAs. A host stack has to be able
has to be able to quickly failover and try a different source address to quickly fail over and try a different source address and
and destination address pair if communication fails as outlined in destination address pair if communication fails, as outlined in
[I-D.wing-v6ops-happy-eyeballs-ipv6]. [HAPPY-EYEBALLS].
At the time of writing, several hosts implementations do not handle At the time of this writing, several host implementations do not
the case where they have an IPv6 address configured and no IPv6 handle the case where they have an IPv6 address configured and no
connectivity. Either because the address itself has a limited IPv6 connectivity, either because the address itself has a limited
topological reachability (e.g. ULA) or because the IPv6 CE router is topological reachability (e.g., ULA) or because the IPv6 CE router is
not connected to the IPv6 network on its WAN interface. To support not connected to the IPv6 network on its WAN interface. To support
host implementations that do not handle multi-homing in a multi- host implementations that do not handle multihoming in a multi-prefix
prefix environment [I-D.ietf-v6ops-multihoming-without-nat66], the environment [MULTIHOMING-WITHOUT-NAT], the IPv6 CE router should not,
IPv6 CE router should, as detailed in the below requirements, not as detailed in the requirements below, advertise itself as a default
advertise itself as a default router on the LAN interface(s) when it router on the LAN interface(s) when it does not have IPv6
does not have IPv6 connectivity on the WAN interface or when it is connectivity on the WAN interface or when it is not provisioned with
not provisioned with IPv6 addresses. For local IPv6 communication IPv6 addresses. For local IPv6 communication, the mechanisms
the mechanisms specified in [RFC4191] are used. specified in [RFC4191] are used.
ULA addressing is useful where the IPv6 CE router has multiple LAN ULA addressing is useful where the IPv6 CE router has multiple LAN
interfaces with hosts that need to communicate with each other. If interfaces with hosts that need to communicate with each other. If
the IPv6 CE router has only a single LAN interface (IPv6 link) then the IPv6 CE router has only a single LAN interface (IPv6 link), then
link-local addressing can be used instead. link-local addressing can be used instead.
In the event more than one IPv6 CE router is present on the LAN, then In the event that more than one IPv6 CE router is present on the LAN,
coexistence with IPv4 requires all of them to conform to these then coexistence with IPv4 requires all of them to conform to these
recommendations, especially requirements ULA-5 and L-4. recommendations, especially requirements ULA-5 and L-4 below.
4. Requirements 4. Requirements
4.1. General Requirements 4.1. General Requirements
The IPv6 CE router is responsible for implementing IPv6 routing; that The IPv6 CE router is responsible for implementing IPv6 routing; that
is, the IPv6 CE router must look up the IPv6 Destination address in is, the IPv6 CE router must look up the IPv6 destination address in
its routing table to decide to which interface it should send the its routing table to decide to which interface it should send the
packet. packet.
In this role, the IPv6 CE router is responsible for ensuring that In this role, the IPv6 CE router is responsible for ensuring that
traffic using its ULA addressing does not go out the WAN interface, traffic using its ULA addressing does not go out the WAN interface,
and does not originate from the WAN interface. and does not originate from the WAN interface.
G-1: An IPv6 CE router is an IPv6 node according to the IPv6 Node G-1: An IPv6 CE router is an IPv6 node according to the IPv6 Node
Requirements [RFC4294] specification. Requirements [RFC4294] specification.
G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443]. G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443].
In particular point to point links MUST be handled as described In particular, point-to-point links MUST be handled as
in section 3.1 of [RFC4443]. described in Section 3.1 of [RFC4443].
G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between
its LAN Interface(s) and its WAN Interface until the router has its LAN interface(s) and its WAN interface until the router has
successfully completed the IPv6 address acquisition process. successfully completed the IPv6 address acquisition process.
G-4: By default an IPv6 CE router that has no default router(s) on G-4: By default, an IPv6 CE router that has no default router(s) on
its WAN interface MUST NOT advertise itself as an IPv6 default its WAN interface MUST NOT advertise itself as an IPv6 default
router on its LAN interfaces. That is, the "Router Lifetime" router on its LAN interfaces. That is, the "Router Lifetime"
field is set to zero in all Router Advertisement messages it field is set to zero in all Router Advertisement messages it
originates [RFC4861]. originates [RFC4861].
G-5: By default if the IPv6 CE router is an advertising router and G-5: By default, if the IPv6 CE router is an advertising router and
loses its IPv6 default router(s) on the WAN interface, it MUST loses its IPv6 default router(s) on the WAN interface, it MUST
explicitly invalidate itself as an IPv6 default router on each explicitly invalidate itself as an IPv6 default router on each
of its advertising interfaces by immediately transmitting one of its advertising interfaces by immediately transmitting one
or more Router Advertisement messages with the "Router or more Router Advertisement messages with the "Router
Lifetime" field set to zero [RFC4861]. Lifetime" field set to zero [RFC4861].
4.2. WAN Side Configuration 4.2. WAN-Side Configuration
The IPv6 CE router will need to support connectivity to one or more The IPv6 CE router will need to support connectivity to one or more
access network architectures. This document describes an IPv6 CE access network architectures. This document describes an IPv6 CE
router that is not specific to any particular architecture or Service router that is not specific to any particular architecture or service
Provider, and supports all commonly used architectures. provider and that supports all commonly used architectures.
IPv6 Neighbor Discovery and DHCPv6 protocols operate over any type of IPv6 Neighbor Discovery and DHCPv6 protocols operate over any type of
IPv6 supported link-layer and there is no need for a link-layer IPv6-supported link layer, and there is no need for a link-layer-
specific configuration protocol for IPv6 network layer configuration specific configuration protocol for IPv6 network-layer configuration
options as in e.g. PPP IPCP for IPv4. This section makes the options as in, e.g., PPP IP Control Protocol (IPCP) for IPv4. This
assumption that the same mechanism will work for any link-layer, be section makes the assumption that the same mechanism will work for
it Ethernet, DOCSIS, PPP or others. any link layer, be it Ethernet, the Data Over Cable Service Interface
Specification (DOCSIS), PPP, or others.
WAN side requirements: WAN-side requirements:
W-1: When the router is attached to the WAN interface link it MUST W-1: When the router is attached to the WAN interface link, it MUST
act as an IPv6 host for the purposes of stateless or stateful act as an IPv6 host for the purposes of stateless [RFC4862] or
interface address assignment ([RFC4862] / [RFC3315]). stateful [RFC3315] interface address assignment.
W-2: The IPv6 CE router MUST generate a link-local address and W-2: The IPv6 CE router MUST generate a link-local address and
finish Duplicate Address Detection according to [RFC4862] prior finish Duplicate Address Detection according to [RFC4862] prior
to sending any Router Solicitations on the interface. The to sending any Router Solicitations on the interface. The
source address used in the subsequent Router Solicitation MUST source address used in the subsequent Router Solicitation MUST
be the link-local address on the WAN interface. be the link-local address on the WAN interface.
W-3: Absent of other routing information the IPv6 CE router MUST use W-3: Absent other routing information, the IPv6 CE router MUST use
Router Discovery as specified in [RFC4861] to discover a Router Discovery as specified in [RFC4861] to discover a
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: DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation W-5: DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
(IA_PD) SHOULD be done as a single DHCPv6 session. (IA_PD) SHOULD be done as a single DHCPv6 session.
W-6: The IPv6 CE router MUST use a persistent DUID for DHCPv6 W-6: The IPv6 CE router MUST use a persistent DHCP Unique Identifier
messages. The DUID MUST NOT change between network interface (DUID) for DHCPv6 messages. The DUID MUST NOT change between
resets or IPv6 CE router reboot. network interface resets or IPv6 CE router reboots.
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 NCPs MUST be treated as independent of logical channel, the Network Control Protocols (NCPs) MUST be
each other and start and terminate independently. treated as independent of each other and start and terminate
independently.
Address assignment requirements: Address assignment requirements:
WAA-1: The IPv6 CE router MUST support SLAAC [RFC4862]. WAA-1: The IPv6 CE router MUST support Stateless Address
Autoconfiguration (SLAAC) [RFC4862].
WAA-2: The IPv6 CE router MUST follow the recommendation in WAA-2: The IPv6 CE router MUST follow the recommendations in Section
[RFC5942]. and in particular the handling of the L-flag in 4 of [RFC5942], and in particular the handling of the L flag
the Router Advertisement Prefix Information Option. 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], DHCPv6 options: IA_NA, Reconfigure Accept [RFC3315], and
DNS_SERVERS [RFC3646]. DNS_SERVERS [RFC3646].
WAA-5: The IPv6 CE router SHOULD support the DHCPv6 SNTP option WAA-5: The IPv6 CE router SHOULD support the DHCPv6 Simple Network
[RFC4075] and the Information Refresh Time Option [RFC4242]. Time Protocol (SNTP) option [RFC4075] and the Information
Refresh Time option [RFC4242].
WAA-6: If the IPv6 CE router receives an RA message (described in WAA-6: If the IPv6 CE router receives a Router Advertisement message
[RFC4861]) with the M-flag set to 1, the IPv6 CE router MUST (described in [RFC4861]) with the M flag set to 1, the IPv6
do DHCPv6 address assignment (request an IA_NA option). CE router MUST do DHCPv6 address assignment (request an IA_NA
option).
WAA-7: If the IPv6 CE router is unable to assign address(es) through WAA-7: If the IPv6 CE router is unable to assign address(es) through
SLAAC it MAY do DHCPv6 address assignment (request an IA_NA) SLAAC, it MAY do DHCPv6 address assignment (request an IA_NA
even if the M-flag is set to 0. option) even if the M flag is set to 0.
WAA-8: If the IPv6 CE router does not acquire global IPv6 WAA-8: 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. interfaces.
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
model [RFC1122]. When originating packets out an interface (Weak ES) model [RFC1122]. When originating packets from an
it will use a source address from another of its interfaces interface, it will use a source address from another one of
if the outgoing interface does not have an address of its interfaces if the outgoing interface does not have an
suitable scope. address of suitable scope.
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). 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 MUST be its interfaces, rounded up to the nearest nibble, and MUST be
configurable to ask for more. 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.
WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix
delegation, regardless of the M and O-flags in a received delegation, regardless of the M and O flags in a received
Router Advertisement message. Router Advertisement message.
WPD-5: If the IPv6 CE Router initiates DHCPv6 before receiving a WPD-5: If the IPv6 CE router initiates DHCPv6 before receiving a
Router Advertisement it MUST also request an IA_NA option in Router Advertisement, it MUST also request an IA_NA option in
DHCPv6. DHCPv6.
WPD-6: If the delegated prefix(es) are aggregate route(s) of WPD-6: 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
destination. This is necessary to prevent forwarding loops destination. This is necessary to prevent forwarding loops
when some addresses covered by the aggregate are not when some addresses covered by the aggregate are not
reachable [RFC4632]. reachable [RFC4632].
(a) The IPv6 CE router SHOULD send an ICMPv6 Destination (a) The IPv6 CE router SHOULD send an ICMPv6 Destination
Unreachable according to section 3.1 [RFC4443] back to Unreachable message in accordance with Section 3.1 of
the source of the packet, if the packet is to be dropped [RFC4443] back to the source of the packet, if the
due to this rule. packet is to be dropped due to this rule.
WPD-7: If the IPv6 CE router requests both an IA_NA and an IA_PD in WPD-7: If the IPv6 CE router requests both an IA_NA and an IA_PD
DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
messages, even if the message does not contain any addresses. Advertise/Reply messages, even if the message does not
contain any addresses.
WPD-8: By default an IPv6 CE router MUST NOT initiate any dynamic WPD-8: By default, an IPv6 CE router MUST NOT initiate any dynamic
routing protocol on its WAN interface. routing protocol on its WAN interface.
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:
1. Link-local addresses may be insufficient for allowing IPv6 1. Link-local addresses may be insufficient for allowing IPv6
applications to communicate with each other in the end-user applications to communicate with each other in the end-user
network. The IPv6 CE router will need to enable this network. The IPv6 CE router will need to enable this
communication by providing globally-scoped unicast addresses or communication by providing globally scoped unicast addresses or
ULAs [RFC4193] whether or not WAN connectivity exists. ULAs [RFC4193], whether or not WAN connectivity exists.
2. IPv6 hosts should be capable of using SLAAC and may be capable of 2. IPv6 hosts should be capable of using SLAAC and may be capable of
using DHCPv6 for acquiring their addresses. using DHCPv6 for acquiring their addresses.
3. IPv6 hosts may use DHCPv6 for other configuration information, 3. IPv6 hosts may use DHCPv6 for other configuration information,
such as the DNS_SERVERS option for acquiring DNS information. such as the DNS_SERVERS option for acquiring DNS information.
Unless otherwise specified, the following requirements apply to the Unless otherwise specified, the following requirements apply to the
IPv6 CE router's LAN interfaces only. IPv6 CE router's LAN interfaces only.
ULA requirements: ULA requirements:
ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA
prefix [RFC4193]. prefix [RFC4193].
ULA-2: A IPv6 CE router with a ULA prefix, MUST maintain this ULA-2: An IPv6 CE router with a ULA prefix MUST maintain this prefix
consistently across reboots. consistently across reboots.
ULA-3: The value of the ULA prefix SHOULD be user configurable. ULA-3: The value of the ULA prefix SHOULD be user-configurable.
ULA-4: By default the IPv6 CE router MUST act as a site border ULA-4: By default, the IPv6 CE router MUST act as a site border
router according to section 4.3 of [RFC4193] and filter router according to Section 4.3 of [RFC4193] and filter
packets with Local IPv6 source or destination addresses packets with local IPv6 source or destination addresses
accordingly. accordingly.
ULA-5: An IPv6 CE router MUST NOT advertise itself as a default ULA-5: An IPv6 CE router MUST NOT advertise itself as a default
router with Router Lifetime greater than zero whenever all of router with a Router Lifetime greater than zero whenever all
its configured and delegated prefixes are ULA prefixes. of its configured and delegated prefixes are ULA prefixes.
LAN requirements: LAN requirements:
L-1: The IPv6 CE router MUST support router behavior according to L-1: The IPv6 CE router MUST support router behavior according to
Neighbor Discovery for IPv6 [RFC4861]. Neighbor Discovery for IPv6 [RFC4861].
L-2: The IPv6 CE router MUST assign a separate /64 from its L-2: The IPv6 CE router MUST assign a separate /64 from its
delegated prefix(es) (and ULA prefix if configured to provide delegated prefix(es) (and ULA prefix if configured to provide
ULA addressing) for each of its LAN interfaces. ULA addressing) for each of its LAN interfaces.
L-3: An IPv6 CE router MUST advertise itself as a router for the L-3: An IPv6 CE router MUST advertise itself as a router for the
delegated prefix(es) (and ULA prefix if configured to provide delegated prefix(es) (and ULA prefix if configured to provide
ULA addressing) using the "Route Information Option" specified ULA addressing) using the "Route Information Option" specified
in section 2.3 of [RFC4191]. This advertisement is in Section 2.3 of [RFC4191]. This advertisement is
independent of having IPv6 connectivity on the WAN interface independent of having or not having IPv6 connectivity on the
or not. WAN interface.
L-4: An IPv6 CE router MUST NOT advertise itself as a default L-4: An IPv6 CE router MUST NOT advertise itself as a default
router with a Router Lifetime [RFC4861] greater than zero if router with a Router Lifetime [RFC4861] greater than zero if
it has no prefixes configured or delegated to it. it has no prefixes configured or delegated to it.
L-5: The IPv6 CE router MUST make each LAN interface an advertising L-5: The IPv6 CE router MUST make each LAN interface an advertising
interface according to [RFC4861]. interface according to [RFC4861].
L-6: In Router Advertisements messages, the Prefix Information L-6: In Router Advertisement messages, the Prefix Information
Option's A and L-flags MUST be set to 1 by default. option's A and L flags MUST be set to 1 by default.
L-7: The A and L-flags setting SHOULD be user configurable. L-7: The A and L flags' settings SHOULD be user-configurable.
L-8: The IPv6 CE router MUST support a DHCPv6 server capable of L-8: The IPv6 CE router MUST support a DHCPv6 server capable of
IPv6 address assignment according to [RFC3315] OR a stateless IPv6 address assignment according to [RFC3315] OR a stateless
DHCPv6 server according to [RFC3736] on its LAN interfaces. DHCPv6 server according to [RFC3736] on its LAN interfaces.
L-9: Unless the IPv6 CE router is configured to support the DHCPv6 L-9: Unless the IPv6 CE router is configured to support the DHCPv6
IA_NA option, it SHOULD set M=0 and O=1 in its Router IA_NA option, it SHOULD set the M flag to 0 and the O flag to
Advertisement messages [RFC4861]. 1 in its Router Advertisement messages [RFC4861].
L-10: The IPv6 CE router MUST support providing DNS information in L-10: The IPv6 CE router MUST support providing DNS information in
the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [RFC3646]. the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [RFC3646].
L-11: The IPv6 CE router SHOULD support providing DNS information in L-11: The IPv6 CE router SHOULD support providing DNS information in
Router Advertisement RDNSS and DNSSL options as specified in the Router Advertisement Recursive DNS Server (RDNSS) and DNS
[RFC6106]. Search List (DNSSL) options as specified in [RFC6106].
L-12: The IPv6 CE router SHOULD make available a subset of DHCPv6 L-12: The IPv6 CE router SHOULD make available a subset of DHCPv6
options (as listed in section 5.3 of [RFC3736]) received from options (as listed in Section 5.3 of [RFC3736]) received from
the DHCPv6 client on its WAN interface to its LAN side DHCPv6 the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
server. server.
L-13: If the delegated prefix changes, i.e. the current prefix is L-13: If the delegated prefix changes, i.e., the current prefix is
replaced with a new prefix without any overlapping time replaced with a new prefix without any overlapping time
period, then the IPv6 CE router MUST immediately advertise the period, then the IPv6 CE router MUST immediately advertise the
old prefix with a preferred lifetime of 0 and a valid lifetime old prefix with a Preferred Lifetime of zero and a Valid
of 2 hours (which must be decremented in real time) in a Lifetime of the lower of the current Valid Lifetime and 2
Router Advertisement message. hours (which must be decremented in real time) in a Router
Advertisement message as described in Section 5.5.3, (e) of
[RFC4862].
L-14: The IPv6 CE router MUST send an ICMP Destination Unreachable L-14: The IPv6 CE router MUST send an ICMP Destination Unreachable
Message, code 5 (Source address failed ingress/egress policy) message, code 5 (Source address failed ingress/egress policy)
for packets forwarded to it using an address from a prefix for packets forwarded to it that use an address from a prefix
which has been deprecated. that has been deprecated.
4.4. Security Considerations 4.4. Security Considerations
It is considered a best practice to filter obviously malicious It is considered a best practice to filter obviously malicious
traffic (e.g. spoofed packets, "martian" addresses, etc.). Thus, the traffic (e.g., spoofed packets, "Martian" addresses, etc.). Thus,
IPv6 CE router ought to support basic stateless egress and ingress the IPv6 CE router ought to support basic stateless egress and
filters. The CE router is also expected to offer mechanisms to ingress filters. The CE router is also expected to offer mechanisms
filter traffic entering the customer network; however, the method by to filter traffic entering the customer network; however, the method
which vendors implement configurable packet filtering is beyond the by which vendors implement configurable packet filtering is beyond
scope of this document. the scope of this document.
Security requirements: Security requirements:
S-1: The IPv6 CE router SHOULD support S-1: The IPv6 CE router SHOULD support [RFC6092]. In particular,
[I-D.ietf-v6ops-cpe-simple-security]. In particular, the IPv6 the IPv6 CE router SHOULD support functionality sufficient for
CE router SHOULD support functionality sufficient for implementing the set of recommendations in [RFC6092],
implementing the set of recommendations in Section 4. This document takes no position on whether such
[I-D.ietf-v6ops-cpe-simple-security] section 4. This document functionality is enabled by default or mechanisms by which
takes no position on whether such functionality is enabled by users would configure it.
default or mechanisms by which users would configure it.
S-2: The IPv6 CE router MUST support ingress filtering in accordance S-2: The IPv6 CE router MUST support ingress filtering in accordance
with [RFC2827] (BCP 38) with BCP 38 [RFC2827].
5. Acknowledgements 5. 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, Scott Beuker, Mohamed
Boucadair, Rex Bullinger, Brian Carpenter, Lorenzo Colitti, Remi Boucadair, Rex Bullinger, Brian Carpenter, Lorenzo Colitti, Remi
Denis-Courmont, Gert Doering, Alain Durand, Katsunori Fukuoka, Tony Denis-Courmont, Gert Doering, Alain Durand, Katsunori Fukuoka, Tony
Hain, Thomas Herbst, Kevin Johns, Erik Kline, Stephen Kramer, Victor Hain, Thomas Herbst, Kevin Johns, Erik Kline, Stephen Kramer, Victor
Kuarsingh, Francois-Xavier Le Bail, David Miles, Arifumi Matsumoto, Kuarsingh, Francois-Xavier Le Bail, Arifumi Matsumoto, David Miles,
Shin Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Pignataro, Shin Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Pignataro,
John Pomeroy, Antonio Querubin, Teemu Savolainen, Matt Schmitt, John Pomeroy, Antonio Querubin, Hiroki Sato, Teemu Savolainen, Matt
Hiroki Sato, David Thaler, Mark Townsley, Bernie Volz, James Schmitt, David Thaler, Mark Townsley, Bernie Volz, Dan Wing, James
Woodyatt, Dan Wing and Cor Zwart Woodyatt, and Cor Zwart.
This draft is based in part on CableLabs' eRouter specification. The This document is based in part on CableLabs' eRouter specification.
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.
6. Contributors 6. Contributors
The following people have participated as co-authors or provided The following people have participated as co-authors or provided
substantial contributions to this document: Ralph Droms, Kirk substantial contributions to this document: Ralph Droms, Kirk
Erichsen, Fred Baker, Jason Weil, Lee Howard, Jean-Francois Tremblay, Erichsen, Fred Baker, Jason Weil, Lee Howard, Jean-Francois Tremblay,
Yiu Lee, John Jason Brzozowski and Heather Kirksey. Yiu Lee, John Jason Brzozowski, and Heather Kirksey.
7. IANA Considerations
This memo includes no request to IANA.
8. References
8.1. Normative References 7. References
[I-D.ietf-v6ops-cpe-simple-security] 7.1. Normative References
Woodyatt, J., "Recommended Simple Security Capabilities in
Customer Premises Equipment for Providing Residential IPv6
Internet Service", draft-ietf-v6ops-cpe-simple-security-16
(work in progress), October 2010.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
[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.
[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:
Defeating Denial of Service Attacks which employ IP Source Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", BCP 38, RFC 2827, May 2000. Address Spoofing", BCP 38, RFC 2827, May 2000.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
and M. Carney, "Dynamic Host Configuration Protocol for C., and M. Carney, "Dynamic Host Configuration Protocol
IPv6 (DHCPv6)", RFC 3315, July 2003. for 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., Ed., "DNS Configuration options for Dynamic
Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
December 2003. December 2003.
[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
Addresses", RFC 4193, October 2005. Addresses", RFC 4193, October 2005.
[RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh [RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh
Time Option for Dynamic Host Configuration Protocol for Time Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 4242, November 2005. IPv6 (DHCPv6)", RFC 4242, November 2005.
[RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294, [RFC4294] Loughney, J., Ed., "IPv6 Node Requirements", RFC 4294,
April 2006. April 2006.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Message Protocol (ICMPv6) for the Internet Protocol Control Message Protocol (ICMPv6) for the Internet
Version 6 (IPv6) Specification", RFC 4443, March 2006. Protocol Version 6 (IPv6) Specification", RFC 4443,
March 2006.
[RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick, [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick,
"Internet Group Management Protocol (IGMP) / Multicast "Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding Listener Discovery (MLD)-Based Multicast Forwarding
("IGMP/MLD Proxying")", RFC 4605, August 2006. ("IGMP/MLD Proxying")", RFC 4605, August 2006.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation (CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, August 2006. Plan", BCP 122, RFC 4632, August 2006.
skipping to change at page 15, line 52 skipping to change at page 16, line 9
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[RFC4864] Van de Velde, G., Hain, T., Droms, R., Carpenter, B., and [RFC4864] Van de Velde, G., Hain, T., Droms, R., Carpenter, B., and
E. Klein, "Local Network Protection for IPv6", RFC 4864, E. Klein, "Local Network Protection for IPv6", RFC 4864,
May 2007. May 2007.
[RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over [RFC5072] Varada, S., Ed., Haskins, D., and E. Allen, "IP Version 6
PPP", RFC 5072, September 2007. over PPP", RFC 5072, September 2007.
[RFC5942] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet [RFC5942] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet
Model: The Relationship between Links and Subnet Model: The Relationship between Links and Subnet
Prefixes", RFC 5942, July 2010. Prefixes", RFC 5942, July 2010.
[RFC6092] Woodyatt, J., Ed., "Recommended Simple Security
Capabilities in Customer Premises Equipment (CPE) for
Providing Residential IPv6 Internet Service", RFC 6092,
January 2011.
[RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
"IPv6 Router Advertisement Options for DNS Configuration", "IPv6 Router Advertisement Options for DNS Configuration",
RFC 6106, November 2010. RFC 6106, November 2010.
8.2. Informative References 7.2. Informative References
[I-D.ietf-behave-v6v4-framework] [HAPPY-EYEBALLS]
Baker, F., Li, X., Bao, C., and K. Yin, "Framework for Wing, D. and A. Yourtchenko, "Happy Eyeballs: Trending
IPv4/IPv6 Translation", Towards Success with Dual-Stack Hosts", Work in Progress,
draft-ietf-behave-v6v4-framework-10 (work in progress), March 2011.
August 2010.
[I-D.ietf-v6ops-multihoming-without-nat66] [MULTIHOMING-WITHOUT-NAT]
Troan, O., Miles, D., Matsushima, S., Okimoto, T., and D. Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T.,
Wing, "IPv6 Multihoming without Network Address and D. Wing, "IPv6 Multihoming without Network Address
Translation", Translation", Work in Progress, March 2011.
draft-ietf-v6ops-multihoming-without-nat66-00 (work in
progress), December 2010.
[I-D.wing-v6ops-happy-eyeballs-ipv6] [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
Wing, D. and A. Yourtchenko, "Happy Eyeballs: Trending IPv4/IPv6 Translation", RFC 6144, April 2011.
Towards Success with Dual-Stack Hosts",
draft-wing-v6ops-happy-eyeballs-ipv6-01 (work in
progress), October 2010.
[UPnP-IGD] [UPnP-IGD]
UPnP Forum, "Universal Plug and Play (UPnP) Internet UPnP Forum, "Universal Plug and Play (UPnP) Internet
Gateway Device (IGD)", November 2001, Gateway Device (IGD)", November 2001,
<http://www.upnp.org/standardizeddcps/igd.asp>. <http://www.upnp.org/>.
Authors' Addresses Authors' Addresses
Hemant Singh Hemant Singh
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 1622 Phone: +1 978 936 1622
Email: shemant@cisco.com EMail: shemant@cisco.com
URI: http://www.cisco.com/ URI: http://www.cisco.com/
Wes Beebee Wes Beebee
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 2030 Phone: +1 978 936 2030
Email: wbeebee@cisco.com EMail: wbeebee@cisco.com
URI: http://www.cisco.com/ URI: http://www.cisco.com/
Chris Donley Chris Donley
CableLabs CableLabs
858 Coal Creek Circle 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
EMail: c.donley@cablelabs.com
Email: c.donley@cablelabs.com
Barbara Stark Barbara Stark
AT&T AT&T
725 W Peachtree St 725 W Peachtree St.
Atlanta, GA 30308 Atlanta, GA 30308
USA USA
EMail: barbara.stark@att.com
Email: barbara.stark@att.com
Ole Troan (editor) Ole Troan (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Veversmauet 8 Telemarksvingen 20
N-5017 BERGEN, N-0655 OSLO,
Norway Norway
EMail: ot@cisco.com
Email: ot@cisco.com
 End of changes. 121 change blocks. 
286 lines changed or deleted 276 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/