draft-ietf-v6ops-rfc7084-bis-02.txt   draft-ietf-v6ops-rfc7084-bis-03.txt 
IPv6 Operations (v6ops) J. Palet Martinez IPv6 Operations (v6ops) J. Palet Martinez
Internet-Draft Consulintel, S.L. Internet-Draft Consulintel, S.L.
Obsoletes: 7084 (if approved) May 27, 2017 Obsoletes: 7084 (if approved) June 9, 2017
Intended status: Informational Intended status: Informational
Expires: November 28, 2017 Expires: December 11, 2017
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-rfc7084-bis-02 draft-ietf-v6ops-rfc7084-bis-03
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 several of IPv6 hosts attached to it. The document also covers several
transition technologies, as required in a world where IPv4 addresses transition technologies, as required in a world where IPv4 addresses
are no longer available, so hosts in the customer LANs with IPv4-only are no longer available, so hosts in the customer LANs with IPv4-only
or IPv6-only applications or devices, requiring to communicate with or IPv6-only applications or devices, requiring to communicate with
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 November 28, 2017. This Internet-Draft will expire on December 11, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . 4 3. Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . 5
4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Current IPv4 End-User Network Architecture . . . . . . . 6 4.1. Current IPv4 End-User Network Architecture . . . . . . . 6
4.2. IPv6 End-User Network Architecture . . . . . . . . . . . 7 4.2. IPv6 End-User Network Architecture . . . . . . . . . . . 7
4.2.1. Local Communication . . . . . . . . . . . . . . . . . 8 4.2.1. Local Communication . . . . . . . . . . . . . . . . . 8
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. General Requirements . . . . . . . . . . . . . . . . . . 8 5.1. General Requirements . . . . . . . . . . . . . . . . . . 9
5.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . 9 5.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . 9
5.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . 13 5.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . 13
5.4. Transition Technologies Support . . . . . . . . . . . . . 15 5.4. Transition Technologies Support . . . . . . . . . . . . . 15
5.4.1. IPv4 Service Continuity in Customer LANs . . . . . . 15 5.4.1. IPv4 Service Continuity in Customer LANs . . . . . . 16
5.4.1.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . 15 5.4.1.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . 16
5.4.1.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . 16 5.4.1.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . 16
5.4.1.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . 17 5.4.1.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . 17
5.4.1.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . 17 5.4.1.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . 17
5.4.1.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . 18 5.4.1.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . 18
5.4.2. Support of IPv6 in IPv4-only WAN access . . . . . . . 18 5.4.2. Support of IPv6 in IPv4-only WAN access . . . . . . . 18
5.4.2.1. 6in4 . . . . . . . . . . . . . . . . . . . . . . 18 5.4.2.1. 6in4 . . . . . . . . . . . . . . . . . . . . . . 18
5.4.2.2. 6rd . . . . . . . . . . . . . . . . . . . . . . . 19 5.4.2.2. 6rd . . . . . . . . . . . . . . . . . . . . . . . 20
5.5. IPv4 Multicast Support . . . . . . . . . . . . . . . . . 21 5.5. IPv4 Multicast Support . . . . . . . . . . . . . . . . . 21
5.6. Security Considerations . . . . . . . . . . . . . . . . . 21 5.6. Security Considerations . . . . . . . . . . . . . . . . . 21
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
8. ANNEX A: Code Considerations . . . . . . . . . . . . . . . . 22 8. ANNEX A: Code Considerations . . . . . . . . . . . . . . . . 23
9. ANNEX B: Changes from RFC7084 . . . . . . . . . . . . . . . . 23 9. ANNEX B: Changes from RFC7084 . . . . . . . . . . . . . . . . 23
10. ANNEX C: Changes from RFC7084-bis-00 . . . . . . . . . . . . 23 10. ANNEX C: Changes from RFC7084-bis-00 . . . . . . . . . . . . 24
11. ANNEX D: Changes from RFC7084-bis-01 . . . . . . . . . . . . 24 11. ANNEX D: Changes from RFC7084-bis-01 . . . . . . . . . . . . 24
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 12. ANNEX E: Changes from RFC7084-bis-02 . . . . . . . . . . . . 25
12.1. Normative References . . . . . . . . . . . . . . . . . . 24 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.2. Informative References . . . . . . . . . . . . . . . . . 29 13.1. Normative References . . . . . . . . . . . . . . . . . . 25
13.2. Informative References . . . . . . . . . . . . . . . . . 30
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 30 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 30
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", in order to office router, referred to as an "IPv6 CE router", in order to
establish an industry baseline for features to be implemented on such establish an industry baseline for features to be implemented on such
a router. a router.
These routers typically also support IPv4, at least in the LAN side. These routers typically also support IPv4, at least in the LAN side.
skipping to change at page 16, line 10 skipping to change at page 16, line 28
464XLAT-1: The IPv6 CE router MUST perform IPv4 Network Address 464XLAT-1: The IPv6 CE router MUST perform IPv4 Network Address
Translation (NAT) on IPv4 traffic translated using the Translation (NAT) on IPv4 traffic translated using the
CLAT, unless a dedicated /64 prefix has been acquired CLAT, unless a dedicated /64 prefix has been acquired
using DHCPv6-PD [RFC3633]. using DHCPv6-PD [RFC3633].
464XLAT-2: The CE router MUST implement [RFC7050] in order to 464XLAT-2: The CE router MUST implement [RFC7050] in order to
discover the PLAT-side translation IPv4 and IPv6 discover the PLAT-side translation IPv4 and IPv6
prefix(es)/suffix(es). In environments with PCP support, prefix(es)/suffix(es). In environments with PCP support,
the CE SHOULD follow [RFC7225] to learn the PLAT-side the CE SHOULD follow [RFC7225] to learn the PLAT-side
translation IPv4 and IPv6 prefix(es)/suffix(es) used by translation IPv4 and IPv6 prefix(es)/suffix(es) used by
an upstream PCP-controlled NAT64 device. Alternatively an upstream PCP-controlled NAT64 device.
SHOULD support draft-li-intarea-nat64-prefix-dhcp-option.
5.4.1.2. Dual-Stack Lite (DS-Lite) 5.4.1.2. Dual-Stack Lite (DS-Lite)
Dual-Stack Lite [RFC6333] enables both continued support for IPv4 Dual-Stack Lite [RFC6333] enables both continued support for IPv4
services and incentives for the deployment of IPv6. It also services and incentives for the deployment of IPv6. It also
de-couples IPv6 deployment in the service provider network from the de-couples IPv6 deployment in the service provider network from the
rest of the Internet, making incremental deployment easier. Dual- rest of the Internet, making incremental deployment easier. Dual-
Stack Lite enables a broadband service provider to share IPv4 Stack Lite enables a broadband service provider to share IPv4
addresses among customers by combining two well-known technologies: addresses among customers by combining two well-known technologies:
IP in IP (IPv4-in-IPv6) and Network Address Translation (NAT). It is IP in IP (IPv4-in-IPv6) and Network Address Translation (NAT). It is
skipping to change at page 17, line 35 skipping to change at page 17, line 48
LW4O6-2: The CE router MUST support the DHCPv6 S46 priority option LW4O6-2: The CE router MUST support the DHCPv6 S46 priority option
described in [RFC8026]. described in [RFC8026].
LW4O6-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP LW4O6-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP
4o6) transport described in [RFC7341]. 4o6) transport described in [RFC7341].
LW4O6-4: The CE router MAY support Dynamic Allocation of Shared IPv4 LW4O6-4: The CE router MAY support Dynamic Allocation of Shared IPv4
Addresses as described in [RFC7618]. Addresses as described in [RFC7618].
LW4O6-5: If the IPv6 CE router is configured with an IPv4 address on
its WAN interface, then the IPv6 CE router SHOULD disable
the Lightweight Basic Bridging BroadBand (B4) element.
5.4.1.4. MAP-E 5.4.1.4. MAP-E
MAP-E [RFC7597] is a mechanism for transporting IPv4 packets across MAP-E [RFC7597] is a mechanism for transporting IPv4 packets across
an IPv6 network using IP encapsulation, including a generic mechanism an IPv6 network using IP encapsulation, including a generic mechanism
for mapping between IPv6 addresses and IPv4 addresses as well as for mapping between IPv6 addresses and IPv4 addresses as well as
transport-layer ports. transport-layer ports.
The CE router SHOULD support MAP-E functionality. If MAP-E is The CE router SHOULD support MAP-E functionality. If MAP-E is
supported, it MUST be implemented according to [RFC7597]. The supported, it MUST be implemented according to [RFC7597]. The
following CE Requirements also apply: following CE Requirements also apply:
skipping to change at page 24, line 37 skipping to change at page 25, line 5
3. MAPE-3 removed. 3. MAPE-3 removed.
4. MAPT-3 removed. 4. MAPT-3 removed.
5. Included non-normative reference to [RFC7849] to clarify that the 5. Included non-normative reference to [RFC7849] to clarify that the
details of the connectivity to 3GPP/LTE networks is out of the details of the connectivity to 3GPP/LTE networks is out of the
scope. scope.
6. Split of transition in two sub-sections for the sake of clarity. 6. Split of transition in two sub-sections for the sake of clarity.
12. References 12. ANNEX E: Changes from RFC7084-bis-02
12.1. Normative References Section to be removed for WGLC. Significant updates are:
1. LW4O6-5 removed, was a mistake due to copy-paste from DS-LITE.
2. Removed citation to individual I-Ds for DHCPv6 options.
13. References
13.1. Normative References
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, Communication Layers", STD 3, RFC 1122,
DOI 10.17487/RFC1122, October 1989, DOI 10.17487/RFC1122, October 1989,
<http://www.rfc-editor.org/info/rfc1122>. <http://www.rfc-editor.org/info/rfc1122>.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 29, line 46 skipping to change at page 30, line 21
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114, over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017, DOI 10.17487/RFC8114, March 2017,
<http://www.rfc-editor.org/info/rfc8114>. <http://www.rfc-editor.org/info/rfc8114>.
[RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 [RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6 Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017, Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017,
<http://www.rfc-editor.org/info/rfc8115>. <http://www.rfc-editor.org/info/rfc8115>.
12.2. Informative References 13.2. Informative References
[RFC7157] Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T., [RFC7157] Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T.,
and D. Wing, "IPv6 Multihoming without Network Address and D. Wing, "IPv6 Multihoming without Network Address
Translation", RFC 7157, DOI 10.17487/RFC7157, March 2014, Translation", RFC 7157, DOI 10.17487/RFC7157, March 2014,
<http://www.rfc-editor.org/info/rfc7157>. <http://www.rfc-editor.org/info/rfc7157>.
[RFC7550] Troan, O., Volz, B., and M. Siodelski, "Issues and [RFC7550] Troan, O., Volz, B., and M. Siodelski, "Issues and
Recommendations with Multiple Stateful DHCPv6 Options", Recommendations with Multiple Stateful DHCPv6 Options",
RFC 7550, DOI 10.17487/RFC7550, May 2015, RFC 7550, DOI 10.17487/RFC7550, May 2015,
<http://www.rfc-editor.org/info/rfc7550>. <http://www.rfc-editor.org/info/rfc7550>.
skipping to change at page 30, line 21 skipping to change at page 30, line 44
N., Chandler, R., Michaud, D., Lopez, D., and W. Haeffner, N., Chandler, R., Michaud, D., Lopez, D., and W. Haeffner,
"An IPv6 Profile for 3GPP Mobile Devices", RFC 7849, "An IPv6 Profile for 3GPP Mobile Devices", RFC 7849,
DOI 10.17487/RFC7849, May 2016, DOI 10.17487/RFC7849, May 2016,
<http://www.rfc-editor.org/info/rfc7849>. <http://www.rfc-editor.org/info/rfc7849>.
[TR-069] Broadband Forum, "CPE WAN Management Protocol", TR-069 [TR-069] Broadband Forum, "CPE WAN Management Protocol", TR-069
Amendment 4, July 2011, Amendment 4, July 2011,
<http://www.broadband-forum.org/technical/trlist.php>. <http://www.broadband-forum.org/technical/trlist.php>.
[UPnP-IGD] [UPnP-IGD]
UPnP Forum, , "InternetGatewayDevice:2 Device Template UPnP Forum, "InternetGatewayDevice:2 Device Template
Version 1.01", December 2010, Version 1.01", December 2010,
<http://upnp.org/specs/gw/igd2/>. <http://upnp.org/specs/gw/igd2/>.
Author's Address Author's Address
Jordi Palet Martinez Jordi Palet Martinez
Consulintel, S.L. Consulintel, S.L.
Molino de la Navata, 75 Molino de la Navata, 75
La Navata - Galapagar, Madrid 28420 La Navata - Galapagar, Madrid 28420
Spain Spain
EMail: jordi.palet@consulintel.es EMail: jordi.palet@consulintel.es
URI: http://www.consulintel.es/ URI: http://www.consulintel.es/
 End of changes. 20 change blocks. 
29 lines changed or deleted 32 lines changed or added

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