draft-ietf-v6ops-ipv6-cpe-router-02.txt   draft-ietf-v6ops-ipv6-cpe-router-03.txt 
Internet Engineering Task Force H. Singh Internet Engineering Task Force H. Singh
Internet-Draft W. Beebee Internet-Draft W. Beebee
Intended status: Informational Cisco Systems, Inc. Intended status: Informational Cisco Systems, Inc.
Expires: April 29, 2010 C. Donley Expires: June 21, 2010 C. Donley
CableLabs CableLabs
B. Stark B. Stark
AT&T AT&T
O. Troan, Ed. O. Troan, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
October 26, 2009 December 18, 2009
Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-ipv6-cpe-router-02 draft-ietf-v6ops-ipv6-cpe-router-03
Abstract
This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses
on the provisioning of an IPv6 CE router and the provisioning of IPv6
hosts attached to it.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 45
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 29, 2010. This Internet-Draft will expire on June 21, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This document specifies requirements for an IPv6 Customer Edge (CE) described in the BSD License.
router. Specifically, the current version of this document focuses
on the provisioning of an IPv6 CE router and the provisioning of IPv6
hosts attached to it.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . 5
4. Use Cases and Requirements . . . . . . . . . . . . . . . . . . 6 4. Use Cases and Requirements . . . . . . . . . . . . . . . . . . 6
4.1. WAN side configuration . . . . . . . . . . . . . . . . . . 6 4.1. WAN side configuration . . . . . . . . . . . . . . . . . . 6
4.2. LAN side configuration . . . . . . . . . . . . . . . . . . 8 4.2. LAN side configuration . . . . . . . . . . . . . . . . . . 8
4.3. General requirements . . . . . . . . . . . . . . . . . . . 9 4.3. General requirements . . . . . . . . . . . . . . . . . . . 9
4.4. Security Considerations . . . . . . . . . . . . . . . . . 10 4.4. Security Considerations . . . . . . . . . . . . . . . . . 10
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Normative References . . . . . . . . . . . . . . . . . . . . . 11 8. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Changes in revision 3 . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
This document defines IPv6 features for a residential or small office This document defines IPv6 features for a residential or small office
router referred to as an IPv6 CE router. Typically these routers router referred to as an IPv6 CE router. Typically these routers
also support IPv4. also support IPv4.
This document specifies how an IPv6 CE router automatically This document specifies how an IPv6 CE router automatically
provisions its WAN interface, acquires an address block for provisions its WAN interface, acquires an address block for
skipping to change at page 3, line 46 skipping to change at page 3, line 46
provider network. provider network.
IPv6 host any device implementing an IPv6 stack receiving IPv6 host any device implementing an IPv6 stack receiving
IPv6 Internet connectivity through the IPv6 CE IPv6 Internet connectivity through the IPv6 CE
router router
LAN interface an IPv6 CE router's attachment to a link in the LAN interface an IPv6 CE router's attachment to a link in the
end-user network. Examples are Ethernets end-user network. Examples are Ethernets
(simple or bridged), 802.11 wireless or other (simple or bridged), 802.11 wireless or other
LAN technologies. An IPv6 CE router may have LAN technologies. An IPv6 CE router may have
one or more LAN Interfaces. one or more network layer LAN Interfaces.
Service Provider a company that offers its customers access to Service Provider a company that offers its customers access to
the Internet. In this document, a Service the Internet. In this document, a Service
Provider specifically offers Internet access Provider specifically offers Internet access
using IPv6, and may also offer IPv4 Internet using IPv6, and may also offer IPv4 Internet
access. The Service Provider can provide such access. The Service Provider can provide such
access over a variety of different transport access over a variety of different transport
methods such as DSL, cable, wireless, and methods such as DSL, cable, wireless, and
others. others.
skipping to change at page 6, line 24 skipping to change at page 6, line 24
4.1. WAN side configuration 4.1. 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 supports all commonly used architectures.
IPv6 Neighbor Discovery and DHCP protocols operate over any type of IPv6 Neighbor Discovery and DHCP 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 like what's e.g. in PPP IPCP for IPv4. This section makes options as in PPP IPCP for IPv4. This section makes the assumption
the assumption that the same mechanism will work for any link-layer, that the same mechanism will work for any link-layer, be it Ethernet,
be it Ethernet, DOCSIS, PPP/PPPoE or others. DOCSIS, PPP/PPPoE or others.
When the router is attached to the WAN interface link it must act as When the router is attached to the WAN interface link it must act as
an IPv6 host for the purposes of IPv6 interface initialisation, ND an IPv6 host for the purposes of stateless or stateful interface
Router Discovery, Prefix Discovery and interface address assignment address assignment ([RFC4862]/[RFC3315]). The router acts as a
([RFC4861]/[RFC4862]). The router acts as a requesting router for requesting router for the purposes of DHCP prefix delegation
the purposes of DHCP prefix delegation ([RFC3633]). ([RFC3633]).
DHCP address assignment (IA_NA) and DHCP prefix delegation (IA_PD) DHCP address assignment (IA_NA) and DHCP prefix delegation (IA_PD)
should be done as a single DHCP session. should be done as a single DHCP session.
Link-layer requirements: Link-layer requirements:
WLL-1: The IPv6 CE router MUST support IPv6 over Ethernet [RFC2464]. WLL-1: The IPv6 CE router MUST support IPv6 over Ethernet [RFC2464].
WLL-2: The IPv6 CE router MUST support IPv6 over PPP [RFC5072]. It WLL-2: The IPv6 CE router MUST support IPv6 over PPP [RFC5072] and
MUST support use of IPv6 over PPP within PPPoE. PPPoE [RFC2516]. In a dual-stack environment with IPCP and
IPV6CP running over one PPP logical channel, the NCPs MUST be
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 SLAAC [RFC4862].
WAA-2: The IPv6 CE router MUST follow the recommendation in WAA-2: The IPv6 CE router MUST follow the recommendation in
[I-D.ietf-6man-ipv6-subnet-model] and in particular the [I-D.ietf-6man-ipv6-subnet-model] and in particular the
handling of the L-bit in the Router Advertisement Prefix handling of the L-bit in the Router Advertisement Prefix
Information Option. Information Option.
WAA-3: The IPv6 CE router MUST support DHCP [RFC3315] client WAA-3: The IPv6 CE router MUST support DHCP [RFC3315] client
behavior. It MUST be able to support the following DHCP behavior. It MUST be able to support the following DHCP
options: IA_NA, Reconfigure Accept([RFC3315]), DNS_SERVERS options: IA_NA, Reconfigure Accept [RFC3315], DNS_SERVERS
([RFC3646]). [RFC3646].
WAA-4: Th IPv6 CE router SHOULD support the DHCP SNTP option WAA-4: The IPv6 CE router SHOULD support the DHCP SNTP option
([RFC4075]) and the Information Refresh Time Option [RFC4075] and the Information Refresh Time Option [RFC4242].
([RFC4242].
WAA-5: If the IPv6 CE router receives an RA message (described in WAA-5: If the IPv6 CE router receives an RA message (described in
[RFC4861]) with the M-bit set to 1, the IPv6 CE router MUST [RFC4861]) with the M-bit set to 1, the IPv6 CE router MUST
request an IA_NA. If the IPv6 CE router is unable to assign do DHCP address assignment (request an IA_NA option). If the
an address through SLAAC it MAY request an IA_NA even if the IPv6 CE router is unable to assign an address through SLAAC
M-bit is set to 0. it MAY do DHCP address assignment (request an IA_NA) even if
the M-bit is set to 0.
WAA-6: If the IPv6 CE router does not acquire a global IPv6 address WAA-6: If the IPv6 CE router does not acquire a global IPv6 address
from either SLAAC or DHCP, then it MUST create a global IPv6 from either SLAAC or DHCP, then it MUST create a global IPv6
address from its delegated prefix and configure that on one address from its delegated prefix and configure that on one
of its internal virtual network interfaces. of its internal virtual network interfaces. As a router the
IPv6 CE router follows the weak host model [RFC1122] and when
originating packets out the WAN-interface will use a suitably
scoped source address from one of its other interfaces.
Prefix Delegation requirements: Prefix Delegation requirements:
WPD-1: The IPv6 CE router MUST support DHCP prefix delegation WPD-1: The IPv6 CE router MUST support DHCP prefix delegation
requesting router behaviour as specified in [RFC3633] (IA_PD requesting router behavior as specified in [RFC3633] (IA_PD
option). The IPv6 CE router MUST ask for a prefix large option). The IPv6 CE router MUST ask for a prefix large
enough to cover all of its LAN interfaces. enough to cover all of its LAN interfaces.
WPD-2: The IPv6 CE router MUST always initiate DHCP prefix WPD-2: The IPv6 CE router MUST always initiate DHCP prefix
delegation, regardless of the M and O-bits in a received delegation, regardless of the M and O-bits in a received
Router Advertisement. If the IPv6 CE Router initiates DHCP Router Advertisement. If the IPv6 CE Router initiates DHCP
before receiving a Router Advertisement it MUST also request before receiving a Router Advertisement it MUST also request
an IA_NA. an IA_NA option in DHCP.
WPD-3: If the delegated prefix is an aggregate route of multiple, WPD-3: Absent of other routing information the IPv6 CE router MUST
use Router Discovery as specified in [RFC4861] to discover a
default router and install a default route in its routing
table with the discovered router's address as the next-hop.
WPD-4: If the delegated prefix is an aggregate route of multiple,
more-specific routes the IPv6 CE router MUST discard packets more-specific routes the IPv6 CE router MUST discard packets
that match the aggregate route, but not any of the more- that match the aggregate route, but not any of the more-
specific routes. In other words, the "next-hop" for the specific routes. In other words, the "next-hop" for the
aggregate route should be the null destination. This is aggregate route should be the null destination. This is
necessary to prevent forwarding loops when some addresses necessary to prevent forwarding loops when some addresses
covered by the aggregate are not reachable. [RFC4632] covered by the aggregate are not reachable [RFC4632]. The
IPv6 CE Router SHOULD send an ICMPv6 Destination Unreachable
according to section 3.1 [RFC4443] back to the source of the
packet if the packet is to be dropped due to this rule.
WPD-4: If the IPv6 CE router requests both an IA_NA and an IA_PD in WPD-5: If the IPv6 CE router requests both an IA_NA and an IA_PD in
DHCP, it MUST accept an IA_PD in DHCP Advertise/Reply DHCP, it MUST accept an IA_PD in DHCP Advertise/Reply
messages, even if the message does not contain any addresses messages, even if the message does not contain any addresses
(IA_NA options with status code NoAddrsAvail). (IA_NA options with status code NoAddrsAvail).
WPD-5: An IPv6 CE router MUST not by default initiate any dynamic WPD-6: An IPv6 CE router MUST not by default initiate any dynamic
routing protocol on its WAN interface. routing protocol on its WAN interface.
4.2. LAN side configuration 4.2. 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 will be expected to support an IPv6 end-user An IPv6 CE router will be expected to support an IPv6 end-user
network and IPv6 hosts that exhibit the following characteristics: network and IPv6 hosts that exhibit the following characteristics:
1. Link-local addresses are insufficient for allowing IPv6 1. Link-local addresses are 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 whether or not WAN connectivity exists. ULAs [RFC4193] whether or not WAN connectivity exists.
2. IPv6 hosts will be capable of using SLAAC and may be capable of 2. IPv6 hosts will be capable of using SLAAC and may be capable of
using DHCP for acquiring their addresses. using DHCP for acquiring their addresses.
3. IPv6 hosts will use DHCP for other configuration information, 3. IPv6 hosts will use DHCP 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 these requirements only apply to the IPv6 Unless otherwise specified these requirements only apply to the IPv6
CE router's LAN interfaces. CE router's LAN interfaces.
Requirements: Requirements:
L-1: The IPv6 CE router MUST support ULA addressing ([RFC4193]). L-1: The IPv6 CE router MUST support ULA addressing [RFC4193].
L-2: The IPv6 CE router MUST have a ULA prefix that it maintains L-2: The IPv6 CE router MUST have a ULA prefix that it maintains
consistently across reboots. The value of the ULA prefix consistently across reboots. The value of the ULA prefix
SHOULD be user configurable. SHOULD be user configurable.
L-3: The IPv6 CE router by default MUST act as a site border router L-3: The IPv6 CE router by default MUST act as a site border router
according to section 4.3 of RFC4193 and filter packets with according to section 4.3 of [RFC4193] and filter packets with
Local IPv6 source or destination addresses accordingly. Local IPv6 source or destination addresses accordingly.
L-4: The IPv6 CE router MUST support router behavior of Neighbor L-4: The IPv6 CE router MUST support router behavior of Neighbor
Discovery for IPv6 ([RFC4861]). Discovery for IPv6 [RFC4861].
L-5: The IPv6 CE router must assign a separate /64 from its L-5: The IPv6 CE router MUST assign a separate /64 from its
delegated prefix (and ULA prefix if configured to provide ULA delegated prefix (and ULA prefix if configured to provide ULA
addressing) for each of its LAN interfaces. The IPV6 CE router addressing) for each of its LAN interfaces. The IPV6 CE
MUST make the interface an advertising interface according to router MUST make the interface an advertising interface
RFC4861. In router advertisements messages, the Prefix according to [RFC4861]. In router advertisements messages,
Information Option's A/L-bits MUST be set to 1 by default; the the Prefix Information Option's A/L-bits MUST be set to 1 by
A/L bits setting SHOULD be user configurable. default; the A/L bits setting SHOULD be user configurable.
L-6: The IPv6 CE router MUST support a DHCP server ([RFC3315]) on L-6: The IPv6 CE router MUST support a DHCP server [RFC3315] on its
its LAN interfaces. It SHOULD support DHCP address assignment LAN interfaces. It MAY support Stateless Dynamic Host
(IA_NA). Configuration Protocol (DHCP) Service for IPv6 [RFC3736].
L-7: Unless the IPv6 CE router is configured to support DHCP IA_NA, L-7: The IPv6 CE SHOULD support DHCP address assignment (IA_NA)
it SHOULD set M=0 and O=1 in its RA messages. [RFC3315].
L-8: The IPv6 CE router MUST support providing DNS information in L-8: Unless the IPv6 CE router is configured to support the DHCP
the DHCP DNS_SERVERS option ([RFC3646]). IA_NA option, it SHOULD set M=0 and O=1 in its Router
Advertisement messages [RFC4861].
L-9: The IPv6 CE router SHOULD pass the additional set of DHCP L-9: The IPv6 CE router MUST support providing DNS information in
options received from the DHCP client on its WAN interface from the DHCP DNS_SERVERS option [RFC3646].
the Service Provider to IPv6 hosts.
L-10: The IPv6 CE router SHOULD pass the additional set of DHCP
options received from the DHCP client on its WAN interface
from the Service Provider to IPv6 hosts.
4.3. General requirements 4.3. 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.
Requirements: An IPv6 CE router is an IPv6 node according to the IPv6 Node
Requirements [RFC4294] specification.
G-1: An IPv6 CE router is an IPv6 node and MUST follow the IPv6 Node
Requirements [RFC4294] specification.
G-2: The IPV6 CE router SHOULD support the following RFCs:
* Internet Protocol, Version 6 (IPv6) Specification [RFC2460]
* Stateless Dynamic Host Configuration Protocol (DHCP) Service
for IPv6 [RFC3736]
* Default Router Preferences and More-Specific Routes
[RFC4191]
* IP Version 6 Addressing Architecture [RFC4291]
* IPv6 Subnet Model: the Relationship between Links and Subnet
Prefixes [I-D.ietf-6man-ipv6-subnet-model]
G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between The IPv6 CE router MUST NOT forward any IPv6 traffic between its LAN
its LAN Interface(s) and its WAN Interface until the router has Interface(s) and its WAN Interface until the router has successfully
successfully completed the IPv6 address acquisition process. completed the IPv6 address acquisition process.
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, the
IPv6 CE router should support basic stateless egress and ingress IPv6 CE router should support basic stateless egress and ingress
filters. The CE router should also offer mechanisms to filter filters. The CE router should also offer mechanisms to filter
traffic entering the customer network; however, the method by which traffic entering the customer network; however, the method by which
vendors implement configurable packet filtering is beyond the scope vendors implement configurable packet filtering is beyond the scope
of this document. of this document.
skipping to change at page 10, line 32 skipping to change at page 10, line 36
[I-D.ietf-v6ops-cpe-simple-security]. [I-D.ietf-v6ops-cpe-simple-security].
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 [RFC2827](BCP 38)
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, Scott Beuker, Rex Bullinger, Brian Carpenter, Mikael Abrahamsson, Merete Asak, Scott Beuker, Rex Bullinger, Brian
Remi Denis-Courmont, Alain Durand, Katsunori Fukuoka, Tony Hain, Carpenter, Remi Denis-Courmont, Alain Durand, Katsunori Fukuoka, Tony
Thomas Herbst, Kevin Johns, Stephen Kramer, Victor Kuarsingh, Hain, Thomas Herbst, Kevin Johns, Stephen Kramer, Victor Kuarsingh,
Francois-Xavier Le Bail, David Miles, Shin Miyakawa, Jean-Francois Francois-Xavier Le Bail, David Miles, Shin Miyakawa, Jean-Francois
Mule, Carlos Pignataro, John Pomeroy, Antonio Querubin, Teemu Mule, Michael Newbery, Carlos Pignataro, John Pomeroy, Antonio
Savolainen, Matt Schmitt, Mark Townsley, Bernie Volz, James Woodyatt, Querubin, Teemu Savolainen, Matt Schmitt, Hiroki Sato, Mark Townsley,
Dan Wing and Cor Zwart Bernie Volz, James Woodyatt, Dan Wing and Cor Zwart
This draft is based in part on CableLabs' eRouter specification. The This draft is based in part on CableLabs' eRouter specification. The
authors wish to acknowledge the additional contributors from 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 11, line 21 skipping to change at page 11, line 23
7. IANA Considerations 7. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
8. Normative References 8. Normative References
[I-D.ietf-6man-ipv6-subnet-model] [I-D.ietf-6man-ipv6-subnet-model]
Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet
Model: the Relationship between Links and Subnet Model: the Relationship between Links and Subnet
Prefixes", draft-ietf-6man-ipv6-subnet-model-05 (work in Prefixes", draft-ietf-6man-ipv6-subnet-model-06 (work in
progress), May 2009. progress), November 2009.
[I-D.ietf-v6ops-cpe-simple-security] [I-D.ietf-v6ops-cpe-simple-security]
Woodyatt, J., "Recommended Simple Security Capabilities in Woodyatt, J., "Recommended Simple Security Capabilities in
Customer Premises Equipment for Providing Residential Customer Premises Equipment for Providing Residential IPv6
IPv6 Internet Service", Internet Service", draft-ietf-v6ops-cpe-simple-security-08
draft-ietf-v6ops-cpe-simple-security-08 (work in (work in progress), October 2009.
progress), October 2009.
[RFC1122] Braden, R., "Requirements for Internet Hosts -
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.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[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.
[RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D.,
and R. Wheeler, "A Method for Transmitting PPP Over
Ethernet (PPPoE)", RFC 2516, February 1999.
[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., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[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,
skipping to change at page 12, line 15 skipping to change at page 12, line 23
[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.
[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
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.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294, [RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294,
April 2006. April 2006.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet 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.
[RFC4779] Asadullah, S., Ahmed, A., Popoviciu, C., Savola, P., and [RFC4779] Asadullah, S., Ahmed, A., Popoviciu, C., Savola, P., and
skipping to change at page 13, line 9 skipping to change at page 13, line 15
[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] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over
PPP", RFC 5072, September 2007. PPP", RFC 5072, September 2007.
Appendix A. Changes in revision 3
o Added "the CPE Router SHOULD send an ICMPv6 Destination
Unreachable ([RFC4443] section 3.1) back to the source of the
packet if the packet is to be dropped due to aggregate null
route."
o Clarified that if IPV6CP and IPCP run over the same PPP session
they should be treated independently.
o Removed RFC2460 in the section of RFCs that SHOULD be supported.
o Clarified that the router acts as a host for the purposes of
address assignment. Not for any other ND function e.g Redirects.
o Improved default router selection / default route RIB insertion
text.
o Added text describing that the weak host model has to be supported
in the unnumbered WAN case.
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
skipping to change at page 14, line 4 skipping to change at page 14, line 29
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 Veversmauet 8
BERGEN, 5017 N-5017 BERGEN,
Norway Norway
Phone: Phone:
Email: ot@cisco.com Email: ot@cisco.com
 End of changes. 45 change blocks. 
113 lines changed or deleted 142 lines changed or added

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