draft-ietf-v6ops-6204bis-11.txt   draft-ietf-v6ops-6204bis-12.txt 
Network Working Group H. Singh Network Working Group H. Singh
Internet-Draft W. Beebee Internet-Draft W. Beebee
Obsoletes: 6204 (if approved) Cisco Systems, Inc. Obsoletes: 6204 (if approved) Cisco Systems, Inc.
Intended status: Informational C. Donley Intended status: Informational C. Donley
Expires: March 29, 2013 CableLabs Expires: May 3, 2013 CableLabs
B. Stark B. Stark
AT&T AT&T
September 25, 2012 October 30, 2012
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-6204bis-11 draft-ietf-v6ops-6204bis-12
Abstract Abstract
This document specifies requirements for an IPv6 Customer Edge (CE) This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. The document also covers IP transition of IPv6 hosts attached to it. The document also covers IP transition
technologies. Two transition technologies in RFC 5969's 6rd and RFC technologies. Two transition technologies in RFC 5969's 6rd and RFC
6333's DS-Lite are covered in the document. The document obsoletes 6333's DS-Lite are covered in the document. The document obsoletes
RFC 6204, if approved. RFC 6204, if approved.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 March 29, 2013. This Internet-Draft will expire on May 3, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 8 skipping to change at page 3, line 8
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 21 Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
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, in order to
routers also support IPv4. establish an industry baseline for features to be implemented on such
a router.
These routers typically 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 [RFC6144]. Support for such a translator to access IPv4 servers [RFC6144]. 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
skipping to change at page 3, line 33 skipping to change at page 3, line 36
See [RFC4779] for a discussion of options available for deploying See [RFC4779] for a discussion of options available for deploying
IPv6 in service provider access networks. IPv6 in service provider access networks.
The document also covers the IP transition technologies that were The document also covers the IP transition technologies that were
available at the time this document was written. Two transition available at the time this document was written. Two transition
technologies in 6rd [RFC5969] and DS-Lite [RFC6333] are covered in technologies in 6rd [RFC5969] and DS-Lite [RFC6333] are covered in
the document. the document.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Take careful note: Unlike other IETF documents, the key words "MUST",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
document are to be interpreted as described in RFC 2119 [RFC2119]. "RECOMMENDED", "MAY", and "OPTIONAL" in this document are not used as
described in RFC 2119 [RFC2119]. This document uses these keyword
Even though this document has Informational status, it specifies not strictly for the purpose of interoperability, but rather for the
requirements using RFC 2119 language, but not strictly for the purpose of establishing industry-common baseline functionality. As
purpose of interoperability. Some requirements are intentionally such, the document points to several other specifications (preferable
specified for the purpose of establishing industry-common baseline in RFC or stable form) to provide additional guidance to implementers
functionality. As such, the document points to several other regarding any protocol implementation required to produce a
specifications (preferable in RFC or stable form) to provide successful CPE router that interoperates successfully with a
additional guidance to implementers regarding any protocol particular subset of currently deploying and planned common IPv6
implementation required to produce a successful CPE router that access networks.
interoperates successfully with a particular subset of currently
deploying and planned common IPv6 access networks.
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 that 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.
skipping to change at page 11, line 24 skipping to change at page 11, line 24
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. [RFC6177] covers the recommendations for service error. [RFC6177] covers the recommendations for service
providers for prefix allocation sizes. providers for prefix allocation sizes.
WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix
delegation when either the M or O flags are set to 1 in a delegation when either the M or O flags are set to 1 in a
received Router Advertisement message. received Router Advertisement (RA) message. Behavior of the
CE router to use DHCPv6 prefix delegation when the CE router
has not received any RA or received an RA with the M and the
O bits set to zero is out of scope for this document.
WPD-5: If the delegated prefix(es) are aggregate route(s) of WPD-5: Any packet received by the CE router with a destination
multiple, more-specific routes, the IPv6 CE router MUST address in the prefix(es) delegated to the CE router but not
discard packets that match the aggregate route(s), but not in the set of prefixes assigned by the CE router to the LAN
any of the more-specific routes. In other words, the next must be dropped. In other words, the next hop for the
hop for the aggregate route(s) should be the null prefix(es) delegated to the CE router 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 message in accordance with Section 3.1 of Unreachable message in accordance with Section 3.1 of
[RFC4443] back to the source of the packet, if the [RFC4443] back to the source of the packet, if the
packet is to be dropped due to this rule. packet is to be dropped due to this rule.
WPD-6: If the IPv6 CE router requests both an IA_NA and an IA_PD WPD-6: If the IPv6 CE router requests both an IA_NA and an IA_PD
skipping to change at page 18, line 11 skipping to change at page 18, line 11
[I-D.ietf-dhc-pd-exclude] [I-D.ietf-dhc-pd-exclude]
Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan,
"Prefix Exclude Option for DHCPv6-based Prefix "Prefix Exclude Option for DHCPv6-based Prefix
Delegation", draft-ietf-dhc-pd-exclude-04 (work in Delegation", draft-ietf-dhc-pd-exclude-04 (work in
progress), December 2011. progress), December 2011.
[I-D.ietf-pcp-base] [I-D.ietf-pcp-base]
Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P. Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P.
Selkirk, "Port Control Protocol (PCP)", Selkirk, "Port Control Protocol (PCP)",
draft-ietf-pcp-base-27 (work in progress), September 2012. draft-ietf-pcp-base-28 (work in progress), October 2012.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
 End of changes. 9 change blocks. 
27 lines changed or deleted 31 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/