draft-ietf-v6ops-ipv6-cpe-router-07.txt   draft-ietf-v6ops-ipv6-cpe-router-08.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: February 12, 2011 C. Donley Expires: June 19, 2011 C. Donley
CableLabs CableLabs
B. Stark B. Stark
AT&T AT&T
O. Troan, Ed. O. Troan, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
August 11, 2010 December 16, 2010
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-ipv6-cpe-router-07 draft-ietf-v6ops-ipv6-cpe-router-08
Abstract Abstract
This document specifies requirements for an IPv6 Customer Edge (CE) This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. of IPv6 hosts attached to it.
Status of this Memo Status of this Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 12, 2011. This Internet-Draft will expire on June 19, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
described in the Simplified BSD License. described in the Simplified BSD License.
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. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2.1. Local communication . . . . . . . . . . . . . . . . . 6
4.1. General Requirements . . . . . . . . . . . . . . . . . . . 6 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2. WAN Side Configuration . . . . . . . . . . . . . . . . . . 6 4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7
4.3. LAN Side Configuration . . . . . . . . . . . . . . . . . . 9 4.2. WAN Side Configuration . . . . . . . . . . . . . . . . . . 7
4.4. Security Considerations . . . . . . . . . . . . . . . . . 11 4.3. LAN Side Configuration . . . . . . . . . . . . . . . . . . 10
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 4.4. Security Considerations . . . . . . . . . . . . . . . . . 13
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 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 [I-D.ietf-behave-v6v4-framework].
skipping to change at page 6, line 7 skipping to change at page 6, line 7
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
Unique Local IPv6 Unicast Addresses (ULA) [RFC4193] are used by hosts
communicating within the End-user Network; this is functionally
similar to RFC1918 addresses used within an IPv4 End-user Network.
The IPv6 CE router defaults to acting as the demarcation point
between two networks by providing a ULA boundary, a multicast zone
boundary and ingress and egress traffic filters.
For IPv6 multicast traffic the IPv6 CE router may act as an Multicast For IPv6 multicast traffic the IPv6 CE router may act as an 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 is described for a single IPv6 CE router only.
3.2.1. Local communication
Link-local IPv6 addresses are used by hosts communicating on a single
link. Unique Local IPv6 Unicast Addresses (ULA) [RFC4193] are used
by hosts communicating within the End-user Network across multiple
links, but without requiring the application to use a globally
routable address. The IPv6 CE router defaults to acting as the
demarcation point between two networks by providing a ULA boundary, a
multicast zone boundary and ingress and egress traffic filters.
A dual-stacked host is multi-homed to IPv4 and IPv6 networks. The
IPv4 and IPv6 topologies may not be congruent and different addresses
may have different reachability, e.g. ULA addresses. A host stack
has to be able to quickly failover and try a different source address
and destination address pair if communication fails as outlined in
[I-D.wing-v6ops-happy-eyeballs-ipv6].
At the time of writing, several hosts implementations do not handle
the case where they have an IPv6 address configured and no IPv6
connectivity. Either because the address itself has a limited
topological reachability (e.g. ULA) or because the IPv6 CE router is
not connected to the IPv6 network on its WAN interface. To support
host implementations that do not handle multi-homing in a multi-
prefix environment [I-D.ietf-v6ops-multihoming-without-nat66], the
IPv6 CE router should, as detailed in the below requirements, not
advertise itself as a default router on the LAN interface(s) when it
does not have IPv6 connectivity on the WAN interface or when it is
not provisioned with IPv6 addresses. For local IPv6 communication
the mechanisms specified in [RFC4191] are used.
ULA addressing is useful where the IPv6 CE router has multiple LAN
interfaces with hosts that need to communicate with each other. If
the IPv6 CE router has only a single LAN interface (IPv6 link) then
link-local addressing can be used instead.
In the event more than one IPv6 CE router is present on the LAN, then
coexistence with IPv4 requires all of them to conform to these
recommendations, especially requirements ULA-5 and L-4.
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 [I-D.ietf-6man-node-req-bis] 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 described
in section 3.1 of [RFC4443]. 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
its WAN interface MUST NOT advertise itself as an IPv6 default
router on its LAN interfaces. That is, the "Router Lifetime"
field is set to zero in all Router Advertisement messages it
originates [RFC4861].
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
explicitly invalidate itself as an IPv6 default router on each
of its advertising interfaces by immediately transmitting one
or more Router Advertisement messages with the "Router
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 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
skipping to change at page 8, line 8 skipping to change at page 9, line 8
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 NCPs MUST be treated as independent of
each other and start and terminate independently. 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 [RFC5942]. and in particular the handling of the L-flag in
handling of the L-flag in the Router Advertisement Prefix the Router Advertisement Prefix Information Option.
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],
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 SNTP option
[RFC4075] and the Information Refresh Time Option [RFC4242]. [RFC4075] and the Information Refresh Time Option [RFC4242].
skipping to change at page 9, line 50 skipping to change at page 10, line 50
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 are 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.
Requirements: ULA requirements:
L-1: The IPv6 CE router MUST support ULA addressing [RFC4193]. ULA-1: The IPv6 CE router MUST be capable of generating a ULA prefix
[RFC4193].
L-2: The IPv6 CE router MUST have a ULA prefix that it maintains ULA-2: A IPv6 CE router with a ULA prefix, MUST maintain this
consistently across reboots. consistently across reboots.
L-3: The value of the ULA prefix SHOULD be user configurable. ULA-3: The value of the ULA prefix SHOULD be user configurable.
L-4: By default the IPv6 CE router MUST act as a site border router ULA-4: By default the IPv6 CE router MUST act as a site border
according to section 4.3 of [RFC4193] and filter packets with router according to section 4.3 of [RFC4193] and filter
Local IPv6 source or destination addresses accordingly. packets with Local IPv6 source or destination addresses
accordingly.
L-5: The IPv6 CE router MUST support router behavior according to ULA-5: An IPv6 CE router MUST NOT advertise itself as a default
router with Router Lifetime greater than zero whenever all of
its configured and delegated prefixes are ULA prefixes.
LAN requirements:
L-1: The IPv6 CE router MUST support router behavior according to
Neighbor Discovery for IPv6 [RFC4861]. Neighbor Discovery for IPv6 [RFC4861].
L-6: 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-7: The IPv6 CE router MUST make each LAN interface an advertising L-3: An IPv6 CE router MUST advertise itself as a router for the
delegated prefix(es) (and ULA prefix if configured to provide
ULA addressing) using the "Route Information Option" specified
in section 2.3 of [RFC4191]. This advertisement is
independent of having IPv6 connectivity on the WAN interface
or not.
L-4: An IPv6 CE router MUST NOT advertise itself as a default
router with a Router Lifetime [RFC4861] greater than zero if
it has no prefixes configured or delegated to it.
L-5: The IPv6 CE router MUST make each LAN interface an advertising
interface according to [RFC4861]. interface according to [RFC4861].
L-8: In Router Advertisements messages, the Prefix Information L-6: In Router Advertisements 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-9: The A and L-flags setting SHOULD be user configurable. L-7: The A and L-flags setting SHOULD be user configurable.
L-10: 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-11: 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 M=0 and O=1 in its Router
Advertisement messages [RFC4861]. Advertisement messages [RFC4861].
L-12: 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 option [RFC3646]. the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [RFC3646].
L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6 L-11: The IPv6 CE router SHOULD support providing DNS information in
Router Advertisement RDNSS and DNSSL options as specified in
[RFC6106].
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-14: 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 0 and a valid lifetime
of 2 hours (which must be decremented in real time) in a of 2 hours (which must be decremented in real time) in a
Router Advertisement message. Router Advertisement message.
L-15: 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 using an address from a prefix
which has been deprecated. which has been deprecated.
L-16: If the IPv6 CE router loses its default route it SHOULD stop
advertising itself as a default router. I.e. by setting the
"Router Lifetime" field to 0 in subsequent Router
Advertisement messages.
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 ought to support basic stateless egress and ingress IPv6 CE router ought to support basic stateless egress and ingress
filters. The CE router is also expected to offer mechanisms to filters. The CE router is also expected to offer mechanisms to
filter traffic entering the customer network; however, the method by filter traffic entering the customer network; however, the method by
which vendors implement configurable packet filtering is beyond the which vendors implement configurable packet filtering is beyond the
scope of this document. scope of this document.
Security requirements: Security requirements:
S-1: The IPv6 CE router SHOULD support S-1: The IPv6 CE router SHOULD support
[I-D.ietf-v6ops-cpe-simple-security]. In particular, the IPv6 [I-D.ietf-v6ops-cpe-simple-security]. In particular, the IPv6
CE router SHOULD support functionality sufficient for CE router SHOULD support functionality sufficient for
implementing the set of recommendations in implementing the set of recommendations in
[I-D.ietf-v6ops-cpe-simple-security] section 4. Ths document [I-D.ietf-v6ops-cpe-simple-security] section 4. This document
takes no position on whether such functionality is enabled by takes no position on whether such functionality is enabled by
default or mechanisms by which 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 [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, Merete Asak, Scott Beuker, Mohamed Boucadair, Rex Mikael Abrahamsson, Tore Anderson, Merete Asak, Scott Beuker, Mohamed
Bullinger, Brian Carpenter, Remi Denis-Courmont, Gert Doering, Alain Boucadair, Rex Bullinger, Brian Carpenter, Lorenzo Colitti, Remi
Durand, Katsunori Fukuoka, Tony Hain, Thomas Herbst, Kevin Johns, Denis-Courmont, Gert Doering, Alain Durand, Katsunori Fukuoka, Tony
Stephen Kramer, Victor Kuarsingh, Francois-Xavier Le Bail, David Hain, Thomas Herbst, Kevin Johns, Erik Kline, Stephen Kramer, Victor
Miles, Shin Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Kuarsingh, Francois-Xavier Le Bail, David Miles, Arifumi Matsumoto,
Pignataro, John Pomeroy, Antonio Querubin, Teemu Savolainen, Matt Shin Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Pignataro,
Schmitt, Hiroki Sato, Mark Townsley, Bernie Volz, James Woodyatt, Dan John Pomeroy, Antonio Querubin, Teemu Savolainen, Matt Schmitt,
Wing and Cor Zwart Hiroki Sato, David Thaler, Mark Townsley, 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 12, line 47 skipping to change at page 14, line 20
Yiu Lee, John Jason Brzozowski and Heather Kirksey. Yiu Lee, John Jason Brzozowski and Heather Kirksey.
7. IANA Considerations 7. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-6man-ipv6-subnet-model]
Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet
Model: the Relationship between Links and Subnet
Prefixes", draft-ietf-6man-ipv6-subnet-model-12 (work in
progress), April 2010.
[I-D.ietf-6man-node-req-bis]
Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node
Requirements RFC 4294-bis",
draft-ietf-6man-node-req-bis-05 (work in progress),
July 2010.
[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 IPv6 Customer Premises Equipment for Providing Residential IPv6
Internet Service", draft-ietf-v6ops-cpe-simple-security-12 Internet Service", draft-ietf-v6ops-cpe-simple-security-16
(work in progress), June 2010. (work in progress), October 2010.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
[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.
skipping to change at page 13, line 51 skipping to change at page 15, line 11
[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.
[RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294,
April 2006.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control [RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", RFC 4443, March 2006. 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
skipping to change at page 14, line 41 skipping to change at page 16, line 6
[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.
[RFC5942] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet
Model: The Relationship between Links and Subnet
Prefixes", RFC 5942, July 2010.
[RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
"IPv6 Router Advertisement Options for DNS Configuration",
RFC 6106, November 2010.
8.2. Informative References 8.2. Informative References
[I-D.ietf-behave-v6v4-framework] [I-D.ietf-behave-v6v4-framework]
Baker, F., Li, X., Bao, C., and K. Yin, "Framework for Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", IPv4/IPv6 Translation",
draft-ietf-behave-v6v4-framework-09 (work in progress), draft-ietf-behave-v6v4-framework-10 (work in progress),
May 2010. August 2010.
[I-D.ietf-v6ops-multihoming-without-nat66]
Troan, O., Miles, D., Matsushima, S., Okimoto, T., and D.
Wing, "IPv6 Multihoming without Network Address
Translation",
draft-ietf-v6ops-multihoming-without-nat66-00 (work in
progress), December 2010.
[I-D.wing-v6ops-happy-eyeballs-ipv6]
Wing, D. and A. Yourtchenko, "Happy Eyeballs: Trending
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/standardizeddcps/igd.asp>.
Authors' Addresses Authors' Addresses
Hemant Singh Hemant Singh
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 36 change blocks. 
78 lines changed or deleted 157 lines changed or added

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