draft-ietf-v6ops-ipv6-cpe-router-04.txt   draft-ietf-v6ops-ipv6-cpe-router-05.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: July 28, 2010 C. Donley Expires: November 12, 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.
January 24, 2010 May 11, 2010
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-ipv6-cpe-router-04 draft-ietf-v6ops-ipv6-cpe-router-05
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 to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 12, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the 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 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. General Requirements . . . . . . . . . . . . . . . . . . . 6 4.1. General Requirements . . . . . . . . . . . . . . . . . . . 6
4.2. WAN Side Configuration . . . . . . . . . . . . . . . . . . 6 4.2. WAN Side Configuration . . . . . . . . . . . . . . . . . . 6
4.3. LAN Side Configuration . . . . . . . . . . . . . . . . . . 9 4.3. LAN Side Configuration . . . . . . . . . . . . . . . . . . 9
4.4. Security Considerations . . . . . . . . . . . . . . . . . 11 4.4. Security Considerations . . . . . . . . . . . . . . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
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
skipping to change at page 6, line 35 skipping to change at page 6, line 35
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 [I-D.ietf-6man-node-req-bis] specification.
G-2: The IPv6 CE router MUST NOT forward any IPv6 traffic between G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443].
In particular point to point links MUST be handled as described
in section 3.1 of [RFC4443].
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.
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.
skipping to change at page 7, line 13 skipping to change at page 7, line 18
options as in e.g. PPP IPCP for IPv4. This section makes the options as in e.g. PPP IPCP for IPv4. This section makes the
assumption that the same mechanism will work for any link-layer, be assumption that the same mechanism will work for any link-layer, be
it Ethernet, DOCSIS, PPP or others. it Ethernet, 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 or stateful
interface address assignment ([RFC4862]/[RFC3315]). interface address assignment ([RFC4862]/[RFC3315]).
W-2: The router MUST act as a requesting router for the purposes of W-2: The IPv6 CE router MUST generate a link-local address and
finish Duplicate Address Detection according to [RFC4862] prior
to sending any Router Solicitations on the interface. The
source address used in the subsequent Router Solicitation MUST
be the link-local address on the WAN interface.
W-3: Absent of other routing information the IPv6 CE router MUST use
Router Discovery as specified in [RFC4861] to discover a
default router(s) and install default route(s) in its routing
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
DHCPv6 prefix delegation ([RFC3633]). DHCPv6 prefix delegation ([RFC3633]).
W-3: 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.
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].
skipping to change at page 9, line 5 skipping to change at page 9, line 19
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: Absent of other routing information the IPv6 CE router MUST WPD-6: If the delegated prefix(es) are aggregate route(s) of
use Router Discovery as specified in [RFC4861] to discover a
default router(s) and install default route(s) in its routing
table with the discovered router's address as the next-hop.
WPD-7: 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 according to section 3.1 [RFC4443] back to
the source of the packet, if the packet is to be dropped the source of the packet, if the packet is to be dropped
due to this rule. due to this rule.
WPD-8: 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 in
DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply DHCPv6, it MUST accept an IA_PD in DHCPv6 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 equal to NoAddrsAvail). (IA_NA options with status code equal to NoAddrsAvail).
WPD-9: 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
skipping to change at page 11, line 5 skipping to change at page 11, line 17
Advertisement messages [RFC4861]. Advertisement messages [RFC4861].
L-12: The IPv6 CE router MUST support providing DNS information in L-12: The IPv6 CE router MUST support providing DNS information in
the DHCPv6 DNS_SERVERS option [RFC3646]. the DHCPv6 DNS_SERVERS option [RFC3646].
L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6 L-13: 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
replaced with a new prefix without any overlapping time
period, then the IPv6 CE router MUST immediately advertise the
old prefix with a preferred lifetime of 0 and a valid lifetime
of 2 hours (which must be decremented in real time) in a
Router Advertisement message.
L-15: The IPv6 CE router MUST send an ICMP Destination Unreachable
Message, code 5 (Source address failed ingress/egress policy)
for packets forwarded to it using an address from a prefix
which 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, 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 12, line 18 skipping to change at page 12, line 42
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] [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-07 (work in Prefixes", draft-ietf-6man-ipv6-subnet-model-12 (work in
progress), December 2009. 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-04 (work in progress),
March 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-08 Internet Service", draft-ietf-v6ops-cpe-simple-security-11
(work in progress), October 2009. (work in progress), April 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 19 skipping to change at page 13, line 49
[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.
[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 10 skipping to change at page 14, line 37
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.
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-04 (work in progress), draft-ietf-behave-v6v4-framework-08 (work in progress),
December 2009. March 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. 20 change blocks. 
37 lines changed or deleted 56 lines changed or added

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