draft-ietf-v6ops-6204bis-10.txt   draft-ietf-v6ops-6204bis-11.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: February 17, 2013 CableLabs Expires: March 29, 2013 CableLabs
B. Stark B. Stark
AT&T AT&T
August 16, 2012 September 25, 2012
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-6204bis-10 draft-ietf-v6ops-6204bis-11
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 February 17, 2013. This Internet-Draft will expire on March 29, 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 2, line 22 skipping to change at page 2, line 22
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
3.2.1. Local Communication . . . . . . . . . . . . . . . . . 6 3.2.1. Local Communication . . . . . . . . . . . . . . . . . 6
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7 4.1. General Requirements . . . . . . . . . . . . . . . . . . . 7
4.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . . 7 4.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . . 8
4.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . . 11 4.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . . 12
4.4. Transition Technologies Support . . . . . . . . . . . . . 13 4.4. Transition Technologies Support . . . . . . . . . . . . . 14
4.4.1. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.4.1. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 14 4.4.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 15
4.5. Security Considerations . . . . . . . . . . . . . . . . . 15 4.5. Security Considerations . . . . . . . . . . . . . . . . . 16
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 20 Appendix A. Changes from RFC 6204 . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 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. 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 [RFC6144]. Support for such a translator to access IPv4 servers [RFC6144]. Support for such
skipping to change at page 3, line 37 skipping to change at page 3, line 37
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", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Terminology Even though this document has Informational status, it specifies
requirements using RFC 2119 language, but not strictly for the
purpose of interoperability. Some requirements are intentionally
specified for the purpose of establishing industry-common baseline
functionality. As such, the document points to several other
specifications (preferable in RFC or stable form) to provide
additional guidance to implementers regarding any protocol
implementation required to produce a successful CPE router that
interoperates successfully with a particular subset of currently
deploying and planned common IPv6 access networks.
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.
IPv6 Host any device implementing an IPv6 stack IPv6 Host any device implementing an IPv6 stack
skipping to change at page 5, line 6 skipping to change at page 5, line 19
connections. Opening of ports is typically allowed using a Universal connections. Opening of ports is typically allowed using a Universal
Plug and Play Internet Gateway Device (UPnP IGD) [UPnP-IGD] or some Plug and Play Internet Gateway Device (UPnP IGD) [UPnP-IGD] or some
other firewall control protocol. other firewall control protocol.
Another consequence of using private address space in the end-user Another consequence of using private address space in the end-user
network is that it provides stable addressing; i.e., it never changes network is that it provides stable addressing; i.e., it never changes
even when you change service providers, and the addresses are always even when you change service providers, and the addresses are always
there even when the WAN interface is down or the customer edge router there even when the WAN interface is down or the customer edge router
has not yet been provisioned. has not yet been provisioned.
Rewriting addresses on the edge of the network also allows for some Many existing routers support dynamic routing (which learns routes
rudimentary multihoming, even though using NATs for multihoming does from other routers), and advanced end-users can build arbitrary,
not preserve connections during a fail-over event [RFC4864]. complex networks using manual configuration of address prefixes
combined with a dynamic routing protocol.
Many existing routers support dynamic routing, and advanced end-users
can build arbitrary, complex networks using manual configuration of
address prefixes combined with a dynamic routing protocol.
3.2. IPv6 End-User Network Architecture 3.2. IPv6 End-User Network Architecture
The end-user network architecture for IPv6 should provide equivalent The end-user network architecture for IPv6 should provide equivalent
or better capabilities and functionality than the current IPv4 or better capabilities and functionality than the current IPv4
architecture. architecture.
The end-user network is a stub network. Figure 1 illustrates the The end-user network is a stub network. Figure 1 illustrates the
model topology for the end-user network. model topology for the end-user network.
skipping to change at page 9, line 34 skipping to change at page 10, line 15
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], and DHCPv6 options: IA_NA, Reconfigure Accept [RFC3315], and
DNS_SERVERS [RFC3646]. The IPv6 CE router SHOULD be able to DNS_SERVERS [RFC3646]. The IPv6 CE router SHOULD be able to
support the DNS Search List DNSSL option as specified in support the DNS Search List DNSSL option as specified in
[RFC3646]. [RFC3646].
WAA-5: The IPv6 CE router SHOULD implement the Network Time WAA-5: The IPv6 CE router SHOULD implement the Network Time
Protocol (NTP) as specified in [RFC5905]. If the CE router Protocol (NTP) as specified in [RFC5905] to provide a time
reference common to the service provider for other
protocols, such as DHCPv6, to use. If the CE router
implements NTP, it requests the NTP Server DHCPv6 option implements NTP, it requests the NTP Server DHCPv6 option
[RFC5908] and uses the received list of servers as primary [RFC5908] and uses the received list of servers as primary
time reference, unless explicitly configured otherwise. LAN time reference, unless explicitly configured otherwise. LAN
side support of NTP is out of scope for this document. side support of NTP is out of scope for this document.
WAA-6: If the IPv6 CE router receives a Router Advertisement WAA-6: If the IPv6 CE router receives a Router Advertisement
message (described in [RFC4861]) with the M flag set to 1, message (described in [RFC4861]) with the M flag set to 1,
the IPv6 CE router MUST do DHCPv6 address assignment the IPv6 CE router MUST do DHCPv6 address assignment
(request an IA_NA option). (request an IA_NA option).
skipping to change at page 12, line 11 skipping to change at page 12, line 41
IPv6 CE router's LAN interfaces only. IPv6 CE router's LAN interfaces only.
ULA requirements: ULA requirements:
ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA
prefix [RFC4193]. prefix [RFC4193].
ULA-2: An IPv6 CE router with a ULA prefix MUST maintain this prefix ULA-2: An IPv6 CE router with a ULA prefix MUST maintain this prefix
consistently across reboots. consistently across reboots.
ULA-3: The value of the ULA prefix SHOULD be user-configurable. ULA-3: The value of the ULA prefix SHOULD be configurable.
ULA-4: By default, the IPv6 CE router MUST act as a site border ULA-4: By default, the IPv6 CE router MUST act as a site border
router according to Section 4.3 of [RFC4193] and filter router according to Section 4.3 of [RFC4193] and filter
packets with local IPv6 source or destination addresses packets with local IPv6 source or destination addresses
accordingly. accordingly.
ULA-5: An IPv6 CE router MUST NOT advertise itself as a default ULA-5: An IPv6 CE router MUST NOT advertise itself as a default
router with a Router Lifetime greater than zero whenever all router with a Router Lifetime greater than zero whenever all
of its configured and delegated prefixes are ULA prefixes. of its configured and delegated prefixes are ULA prefixes.
skipping to change at page 17, line 26 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-26 (work in progress), June 2012. draft-ietf-pcp-base-27 (work in progress), September 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. 13 change blocks. 
26 lines changed or deleted 35 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/