draft-ietf-v6ops-transition-ipv4aas-03.txt   draft-ietf-v6ops-transition-ipv4aas-04.txt 
IPv6 Operations (v6ops) J. Palet Martinez IPv6 Operations (v6ops) J. Palet Martinez
Internet-Draft The IPv6 Company Internet-Draft The IPv6 Company
Intended status: Informational H. M.-H. Liu Intended status: Informational H. M.-H. Liu
Expires: December 17, 2018 D-Link Systems, Inc. Expires: December 26, 2018 D-Link Systems, Inc.
M. Kawashima M. Kawashima
NEC Platforms, Ltd. NEC Platforms, Ltd.
June 15, 2018 June 24, 2018
Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity
as-a-Service as-a-Service
draft-ietf-v6ops-transition-ipv4aas-03 draft-ietf-v6ops-transition-ipv4aas-04
Abstract Abstract
This document specifies the IPv4 service continuity requirements for This document specifies the IPv4 service continuity requirements for
an IPv6 Customer Edge (CE) router, either provided by the service an IPv6 Customer Edge (CE) router, either provided by the service
provider or thru the retail market. provider or thru the retail market.
Specifically, this document extends the "Basic Requirements for IPv6 Specifically, this document extends the "Basic Requirements for IPv6
Customer Edge Routers" in order to allow the provisioning of IPv6 Customer Edge Routers" in order to allow the provisioning of IPv6
transition services for the support of "IPv4 as-a-Service" (IPv4aaS) transition services for the support of "IPv4 as-a-Service" (IPv4aaS)
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 December 17, 2018. This Internet-Draft will expire on December 26, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 27 skipping to change at page 2, line 27
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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language - Special Note . . . . . . . . . . 3 1.1. Requirements Language - Special Note . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. General Requirements . . . . . . . . . . . . . . . . . . 4 3.1. General Requirements . . . . . . . . . . . . . . . . . . 4
3.2. LAN-Side Configuration . . . . . . . . . . . . . . . . . 4 3.2. LAN-Side Configuration . . . . . . . . . . . . . . . . . 5
3.3. Transition Technologies Support for IPv4 service 3.3. Transition Technologies Support for IPv4 Service
continuity (IPv4 as-a-Service - IPv4aaS) . . . . . 5 Continuity (IPv4 as-a-Service - IPv4aaS) . . . . . 5
3.3.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 6 3.3.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7 3.3.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7
3.3.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8 3.3.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8
3.3.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9 3.3.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9
4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 9 4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 9
5. UPnP Support . . . . . . . . . . . . . . . . . . . . . . . . 10 5. UPnP Support . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Differences from RFC7084 . . . . . . . . . . . . . . . . . . 10 6. Differences from RFC7084 . . . . . . . . . . . . . . . . . . 10
7. Code Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. Code Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
11. Annex A: Usage Scenarios . . . . . . . . . . . . . . . . . . 11 11. Annex A: Usage Scenarios . . . . . . . . . . . . . . . . . . 11
12. Annex B: End-User Network Architecture . . . . . . . . . . . 13 12. Annex B: End-User Network Architecture . . . . . . . . . . . 13
13. ANNEX C: Changes from -00 . . . . . . . . . . . . . . . . . . 16 13. ANNEX C: Changes from -00 . . . . . . . . . . . . . . . . . . 16
14. ANNEX D: Changes from -01 . . . . . . . . . . . . . . . . . . 16 14. ANNEX D: Changes from -01 . . . . . . . . . . . . . . . . . . 16
15. ANNEX E: Changes from -02 . . . . . . . . . . . . . . . . . . 16 15. ANNEX E: Changes from -02 . . . . . . . . . . . . . . . . . . 16
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 16. ANNEX F: Changes from -03 . . . . . . . . . . . . . . . . . . 17
16.1. Normative References . . . . . . . . . . . . . . . . . . 17 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
16.2. Informative References . . . . . . . . . . . . . . . . . 19 17.1. Normative References . . . . . . . . . . . . . . . . . . 17
17.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document defines IPv4 service continuity features over an This document defines IPv4 service continuity features over an
IPv6-only network, for a residential or small-office router, referred IPv6-only network, for a residential or small-office router, referred
to as an "IPv6 Transition CE Router", in order to establish an to as an "IPv6 Transition CE Router", in order to establish an
industry baseline for transition features to be implemented on such a industry baseline for transition features to be implemented on such a
router. router.
skipping to change at page 3, line 46 skipping to change at page 3, line 46
([RFC7788]), which is out of the scope of this document. ([RFC7788]), which is out of the scope of this document.
Service providers who specify feature sets for IPv6 Transition CE Service providers who specify feature sets for IPv6 Transition CE
Router MAY specify a different set of features than those included in Router MAY specify a different set of features than those included in
this document. Since it is impossible to know prior to sale which this document. Since it is impossible to know prior to sale which
transition mechanism a device will need over the lifetime of the transition mechanism a device will need over the lifetime of the
device, IPv6 Transition CE Router intended for the retail market MUST device, IPv6 Transition CE Router intended for the retail market MUST
support all of them. support all of them.
A complete description of "Usage Scenarios" and "End-User Network A complete description of "Usage Scenarios" and "End-User Network
Architecture" is provided in Annex A and B, respectively. Architecture" is provided in Annexes A and B, respectively.
1.1. Requirements Language - Special Note 1.1. Requirements Language - Special Note
Unlike other IETF documents, the key words "MUST", "MUST NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are not used as document are not used as described in RFC 2119 [RFC2119]. This
described in RFC 2119 [RFC2119]. This document uses these keywords document uses these keywords not strictly for the purpose of
not strictly for the purpose of interoperability, but rather for the interoperability, but rather for the purpose of establishing
purpose of establishing industry-common baseline functionality. As industry-common baseline functionality. As such, the document points
such, the document points to several other specifications to provide to several other specifications to provide additional guidance to
additional guidance to implementers regarding any protocol implementers regarding any protocol implementation required to
implementation required to produce a successful IPv6 Transition CE produce a successful IPv6 Transition CE Router that interoperates
Router that interoperates successfully with a particular subset of successfully with a particular subset of currently deploying and
currently deploying and planned common IPv6-only access networks. planned common IPv6-only access networks.
Additionally, the keyword "DEFAULT" is to be interpreted in this
document as pertaining to a configuration as applied by a vendor,
prior to the administrator changing it for its initial activation.
2. Terminology 2. Terminology
This document uses the same terms as in [RFC7084], with minor This document uses the same terms as in [RFC7084], with minor
clarifications. clarifications.
"IPv4aaS" stands for "IPv4 as-a-Service", meaning transition "IPv4aaS" stands for "IPv4 as-a-Service", meaning transition
technologies for delivering IPv4 in IPv6-only access networks. technologies for delivering IPv4 in IPv6-only access networks.
The term "IPv6 transition Customer Edge Router with IPv4aaS" The term "IPv6 transition Customer Edge Router with IPv4aaS"
skipping to change at page 4, line 34 skipping to change at page 4, line 38
services over an IPv6-only WAN network including IPv6-IPv4 services over an IPv6-only WAN network including IPv6-IPv4
communications. communications.
The "WAN Interface" term used across this document, means that can The "WAN Interface" term used across this document, means that can
also support link technologies based in Internet-layer (or higher- also support link technologies based in Internet-layer (or higher-
layers) "tunnels", such as IPv4-in-IPv6 tunnels. layers) "tunnels", such as IPv4-in-IPv6 tunnels.
3. Requirements 3. Requirements
The IPv6 Transition CE Router MUST comply with [RFC7084] (Basic The IPv6 Transition CE Router MUST comply with [RFC7084] (Basic
Requirements for IPv6 Customer Edge Routers). Requirements for IPv6 Customer Edge Routers) and this document add
new requirements, as described in the following sub-sections.
3.1. General Requirements 3.1. General Requirements
A new general requirement is added, in order to ensure that the IPv6 A new general requirement is added, in order to ensure that the IPv6
Transition CE Router respects the IPv6 prefix length as a parameter: Transition CE Router respects the IPv6 prefix length as a parameter:
G-6 The IPv6 Transition CE Router MUST comply with [RFC7608] (IPv6 G-1: The IPv6 Transition CE Router MUST comply with [RFC7608] (IPv6
Prefix Length Recommendation for Forwarding). Prefix Length Recommendation for Forwarding).
3.2. LAN-Side Configuration 3.2. LAN-Side Configuration
A new LAN requirement is added, which in fact is common in regular A new LAN requirement is added, which in fact is common in regular
IPv6 Transition CE Router, and it is required by most of the IPv6 Transition CE Router, and it is required by most of the
transition mechanisms: transition mechanisms:
L-15 The IPv6 Transition CE Router SHOULD implement a DNS proxy as L-1: The IPv6 Transition CE Router MUST implement a DNS proxy as
described in [RFC5625] (DNS Proxy Implementation Guidelines). described in [RFC5625] (DNS Proxy Implementation Guidelines).
3.3. Transition Technologies Support for IPv4 service continuity (IPv4 3.3. Transition Technologies Support for IPv4 Service Continuity (IPv4
as-a-Service - IPv4aaS) as-a-Service - IPv4aaS)
The main target of this document is the support of IPv6-only WAN The main target of this document is the support of IPv6-only WAN
access. To enable legacy IPv4 functionality, this document also access. To enable legacy IPv4 functionality, this document also
includes the support of IPv4-only devices and applications in the includes the support of IPv4-only devices and applications in the
customers LANs, as well as IPv4-only services on the Internet. Thus, customers LANs, as well as IPv4-only services on the Internet. Thus,
both IPv4-only and the IPv6-only devices inside the IPv6 Transition both IPv4-only and the IPv6-only devices inside the IPv6 Transition
CE Router are able to reach the IPv4-only services. CE Router are able to reach the IPv4-only services.
This document takes no position on simultaneous operation of any This document takes no position on simultaneous operation of one or
transition mechanism and native IPv4. several transition mechanism and/or native IPv4.
In order to seamlessly provide the IPv4 Service Continuity in In order to seamlessly provide the IPv4 Service Continuity in
Customer LANs, allowing an automated IPv6 transition mechanism Customer LANs, allowing an automated IPv6 transition mechanism
provisioning, general transition requirements are added. provisioning, general transition requirements are defined.
General transition requirements: General transition requirements:
TRANS-1: All the supported transition mechanisms MUST be disabled by TRANS-1: The IPv6 Transition CE Router MUST support the DHCPv6 S46
default configuration of the IPv6 Transition CE Router. priority options described in [RFC8026] (Unified IPv4-in-
IPv6 Softwire Customer Premises Equipment (CPE): A
DHCPv6-Based Prioritization Mechanism).
TRANS-2: The IPv6 Transition CE Router MUST have a GUI and/or CLI TRANS-2: The IPv6 Transition CE Router MUST have a GUI and/or CLI
option to manually enable/disable each of the supported option to manually enable/disable each of the supported
transition mechanisms. transition mechanisms.
TRANS-3: The IPv6 Transition CE Router MUST support the DHCPv6 S46 TRANS-3: The IPv6 Transition CE Router MUST request the relevant
priority options described in [RFC8026] (Unified IPv4-in- configuration options for each supported transition
IPv6 Softwire Customer Premises Equipment (CPE): A mechanisms, which MUST remain disabled at this step.
DHCPv6-Based Prioritization Mechanism).
TRANS-4: The IPv6 Transition CE Router, following Section 1.4 of TRANS-4: The IPv6 Transition CE Router, following Section 1.4 of
[RFC8026], MUST check for a valid match in [RFC8026], MUST check for a valid match in
OPTION_S46_PRIORITY, which will allow enabling/configuring OPTION_S46_PRIORITY, which allows enabling/disabling a
a transition mechanism. transition mechanism.
TRANS-5: In order to allow the service provider to disable all the TRANS-5: In order to allow the service provider to disable all the
transition mechanisms, the IPv6 Transition CE Router MUST transition mechanisms, the IPv6 Transition CE Router MUST
NOT enable any transition mechanisms if no match is found NOT enable any transition mechanisms if no match is found
between the priority list and the candidate list. between the priority list and the candidate list.
The following sections describe the requirements for supporting each The following sections describe the requirements for supporting each
one of the transition mechanisms. one of the transition mechanisms.
3.3.1. 464XLAT 3.3.1. 464XLAT
skipping to change at page 6, line 31 skipping to change at page 6, line 36
using the CLAT, unless a dedicated /64 prefix has been using the CLAT, unless a dedicated /64 prefix has been
acquired, either using DHCPv6-PD [RFC3633] (IPv6 Prefix acquired, either using DHCPv6-PD [RFC3633] (IPv6 Prefix
Options for DHCPv6) or by alternative means. Options for DHCPv6) or by alternative means.
464XLAT-2: The IPv6 Transition CE Router SHOULD support IGD-PCP IWF 464XLAT-2: The IPv6 Transition CE Router SHOULD support IGD-PCP IWF
[RFC6970] (UPnP Internet Gateway Device - Port Control [RFC6970] (UPnP Internet Gateway Device - Port Control
Protocol Interworking Function). Protocol Interworking Function).
464XLAT-3: If PCP ([RFC6887]) is implemented, the IPv6 Transition CE 464XLAT-3: If PCP ([RFC6887]) is implemented, the IPv6 Transition CE
Router MUST also implement [RFC7291] (DHCP Options for Router MUST also implement [RFC7291] (DHCP Options for
the PCP). If no PCP server is configured, the IPv6 the PCP). Following ([RFC6887]), if no PCP server is
Transition CE Router MAY verify if the default gateway, configured, the IPv6 Transition CE Router MAY verify if
or the NAT64 is the PCP server. A plain IPv6 mode is the default gateway, or the NAT64 is the PCP server. A
used to send PCP requests to the server. plain IPv6 mode MUST be used to send PCP requests to the
server.
464XLAT-4: The IPv6 Transition CE Router MUST implement [RFC7050] 464XLAT-4: The IPv6 Transition CE Router MUST implement [RFC7050]
(Discovery of the IPv6 Prefix Used for IPv6 Address (Discovery of the IPv6 Prefix Used for IPv6 Address
Synthesis) in order to discover the PLAT-side translation Synthesis) in order to discover the PLAT-side translation
IPv4 and IPv6 prefix(es)/suffix(es). IPv4 and IPv6 prefix(es)/suffix(es).
464XLAT-5: If PCP is implemented, the IPv6 Transition CE Router MUST 464XLAT-5: If PCP is implemented, the IPv6 Transition CE Router MUST
follow [RFC7225] (Discovering NAT64 IPv6 Prefixes Using follow [RFC7225] (Discovering NAT64 IPv6 Prefixes Using
the PCP), in order to learn the PLAT-side translation the PCP), in order to learn the PLAT-side translation
IPv4 and IPv6 prefix(es)/suffix(es) used by an upstream IPv4 and IPv6 prefix(es)/suffix(es) used by an upstream
skipping to change at page 7, line 20 skipping to change at page 7, line 27
the case the service provider uses DNS64 ([RFC6147]). If DNS64 the case the service provider uses DNS64 ([RFC6147]). If DNS64
([RFC6147]) is not used, or not trusted, as the DNS configuration at ([RFC6147]) is not used, or not trusted, as the DNS configuration at
the CE (or hosts behind the CE) may be modified by the customer, then the CE (or hosts behind the CE) may be modified by the customer, then
the service provider may opt to configure the NAT64 prefix either by the service provider may opt to configure the NAT64 prefix either by
means of [RFC7225] or [RFC8115], which also can be used if the means of [RFC7225] or [RFC8115], which also can be used if the
service provider uses DNS64 ([RFC6147]). service provider uses DNS64 ([RFC6147]).
3.3.2. Dual-Stack Lite (DS-Lite) 3.3.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 de- services. Dual-Stack Lite enables a broadband service provider to
couples IPv6 deployment in the service provider network from the rest share IPv4 addresses among customers by combining two well-known
of the Internet, making incremental deployment easier. Dual-Stack technologies: IP in IP (IPv4-in-IPv6) and Network Address Translation
Lite enables a broadband service provider to share IPv4 addresses (NAT). It is expected that DS-Lite traffic is forwarded over the
among customers by combining two well-known technologies: IP in IP IPv6 Transition CE Router's native IPv6 WAN interface, and not
(IPv4-in-IPv6) and Network Address Translation (NAT). It is expected encapsulated in another tunnel.
that DS-Lite traffic is forwarded over the IPv6 Transition CE
Router's native IPv6 WAN interface, and not encapsulated in another
tunnel.
The IPv6 Transition CE Router SHOULD implement DS-Lite [RFC6333] The IPv6 Transition CE Router SHOULD implement DS-Lite B4
functionality. If DS-Lite is supported, it MUST be implemented functionality [RFC6333]. If DS-Lite is supported, it MUST be
according to [RFC6333]. The following IPv6 Transition CE Router implemented according to [RFC6333]. The following IPv6 Transition CE
requirements also apply: Router requirements also apply:
DS-Lite requirements: DS-Lite requirements:
DSLITE-1: The IPv6 Transition CE Router MUST support configuration DSLITE-1: The IPv6 Transition CE Router MUST support configuration
of DS-Lite via the DS-Lite DHCPv6 option [RFC6334] (DHCPv6 of DS-Lite via the DS-Lite DHCPv6 option [RFC6334] (DHCPv6
Option for Dual-Stack Lite). The IPv6 Transition CE Option for Dual-Stack Lite). The IPv6 Transition CE
Router MAY use other mechanisms to configure DS-Lite Router MAY use other mechanisms to configure DS-Lite
parameters. Such mechanisms are outside the scope of this parameters. Such mechanisms are outside the scope of this
document. document.
DSLITE-2: The IPv6 Transition CE Router SHOULD support IGD-PCP IWF DSLITE-2: The IPv6 Transition CE Router SHOULD support IGD-PCP IWF
[RFC6970] (UPnP Internet Gateway Device - Port Control [RFC6970] (UPnP Internet Gateway Device - Port Control
Protocol Interworking Function). Protocol Interworking Function).
DSLITE-3: If PCP ([RFC6887]) is implemented, the IPv6 Transition CE DSLITE-3: If PCP ([RFC6887]) is implemented, the IPv6 Transition CE
Router SHOULD also implement [RFC7291] (DHCP Options for Router SHOULD implement [RFC7291] (DHCP Options for the
the PCP). If PCP ([RFC6887]) is implemented and a PCP PCP). If PCP ([RFC6887]) is implemented and a PCP server
server is not configured, the IPv6 Transition CE Router is not configured, the IPv6 Transition CE Router MUST
MUST assume, by default, that the AFTR is the PCP server. assume, by DEFAULT, that the AFTR is the PCP server. A
A plain IPv6 mode is used to send PCP requests to the plain IPv6 mode MUST be used to send PCP requests to the
server. server.
DSLITE-4: The IPv6 Transition CE Router MUST NOT perform IPv4 DSLITE-4: The IPv6 Transition CE Router MUST NOT perform IPv4
Network Address Translation (NAT) on IPv4 traffic Network Address Translation (NAT) on IPv4 traffic
encapsulated using DS-Lite ([RFC6333]). encapsulated using DS-Lite ([RFC6333]).
3.3.3. Lightweight 4over6 (lw4o6) 3.3.3. Lightweight 4over6 (lw4o6)
lw4o6 [RFC7596] specifies an extension to DS-Lite, which moves the lw4o6 [RFC7596] specifies an extension to DS-Lite, which moves the
NAPT function from the DS-Lite tunnel concentrator to the tunnel NAPT function from the DS-Lite tunnel concentrator to the tunnel
client located in the IPv6 Transition CE Router, removing the client located in the IPv6 Transition CE Router, removing the
requirement for a CGN function in the tunnel concentrator and requirement for a CGN function in the tunnel concentrator and
reducing the amount of centralized state. reducing the amount of centralized state.
The IPv6 Transition CE Router SHOULD implement lw4o6 functionality. The IPv6 Transition CE Router SHOULD implement lwB4 functionality
If DS-Lite is implemented, lw4o6 SHOULD be supported as well. If [RFC7596]. If DS-Lite is implemented, lw4o6 SHOULD be supported as
lw4o6 is supported, it MUST be implemented according to [RFC7596]. well. If lw4o6 is supported, it MUST be implemented according to
The following IPv6 Transition CE Router requirements also apply: [RFC7596]. The following IPv6 Transition CE Router requirements also
apply:
lw4o6 requirements: lw4o6 requirements:
LW4O6-1: The IPv6 Transition CE Router MUST support configuration of LW4O6-1: The IPv6 Transition CE Router MUST support configuration of
lw4o6 via the lw4o6 DHCPv6 options [RFC7598] (DHCPv6 lw4o6 via the lw4o6 DHCPv6 options [RFC7598] (DHCPv6
Options for Configuration of Softwire Address and Port- Options for Configuration of Softwire Address and Port-
Mapped Clients). The IPv6 Transition CE Router MAY use Mapped Clients). The IPv6 Transition CE Router MAY use
other mechanisms to configure lw4o6 parameters. Such other mechanisms to configure lw4o6 parameters. Such
mechanisms are outside the scope of this document. mechanisms are outside the scope of this document.
skipping to change at page 8, line 49 skipping to change at page 9, line 5
Allocation of Shared IPv4 Addresses as described in Allocation of Shared IPv4 Addresses as described in
[RFC7618] (Dynamic Allocation of Shared IPv4 Addresses). [RFC7618] (Dynamic Allocation of Shared IPv4 Addresses).
3.3.4. MAP-E 3.3.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 an algorithmic an IPv6 network using IP encapsulation, including an algorithmic
mechanism for mapping between IPv6 addresses and IPv4 addresses as mechanism for mapping between IPv6 addresses and IPv4 addresses as
well as transport-layer ports. well as transport-layer ports.
The IPv6 Transition CE Router SHOULD support MAP-E functionality. If The IPv6 Transition CE Router SHOULD support MAP-E CE functionality
MAP-E is supported, it MUST be implemented according to [RFC7597]. [RFC7597]. If MAP-E is supported, it MUST be implemented according
The following IPv6 Transition CE Router requirements also apply: to [RFC7597]. The following IPv6 Transition CE Router requirements
also apply:
MAP-E requirements: MAP-E requirements:
MAPE-1: The IPv6 Transition CE Router MUST support configuration of MAPE-1: The IPv6 Transition CE Router MUST support configuration of
MAP-E via the MAP-E DHCPv6 options [RFC7598] (DHCPv6 Options MAP-E via the MAP-E DHCPv6 options [RFC7598] (DHCPv6 Options
for Configuration of Softwire Address and Port-Mapped for Configuration of Softwire Address and Port-Mapped
Clients). The IPv6 Transition CE Router MAY use other Clients). The IPv6 Transition CE Router MAY use other
mechanisms to configure MAP-E parameters. Such mechanisms mechanisms to configure MAP-E parameters. Such mechanisms
are outside the scope of this document. are outside the scope of this document.
MAPE-2: The IPv6 Transition CE Router MAY support Dynamic Allocation MAPE-2: The IPv6 Transition CE Router MAY support Dynamic Allocation
of Shared IPv4 Addresses as described in [RFC7618] (Dynamic of Shared IPv4 Addresses as described in [RFC7618] (Dynamic
Allocation of Shared IPv4 Addresses). Allocation of Shared IPv4 Addresses).
3.3.5. MAP-T 3.3.5. MAP-T
MAP-T [RFC7599] is a mechanism similar to MAP-E, differing from it in MAP-T [RFC7599] is a mechanism similar to MAP-E, differing from it in
that MAP-T uses IPv4-IPv6 translation, rather than encapsulation, as that MAP-T uses IPv4-IPv6 translation, rather than encapsulation, as
the form of IPv6 domain transport. the form of IPv6 domain transport.
The IPv6 Transition CE Router SHOULD support MAP-T functionality. If The IPv6 Transition CE Router SHOULD support MAP-T CE functionality
MAP-T is supported, it MUST be implemented according to [RFC7599]. [RFC7599]. If MAP-T is supported, it MUST be implemented according
The following IPv6 Transition CE Router requirements also apply: to [RFC7599]. The following IPv6 Transition CE Router requirements
also apply:
MAP-T requirements: MAP-T requirements:
MAPT-1: The IPv6 Transition CE Router MUST support configuration of MAPT-1: The IPv6 Transition CE Router MUST support configuration of
MAP-T via the MAP-T DHCPv6 options [RFC7598] (DHCPv6 Options MAP-T via the MAP-T DHCPv6 options [RFC7598] (DHCPv6 Options
for Configuration of Softwire Address and Port-Mapped for Configuration of Softwire Address and Port-Mapped
Clients). The IPv6 Transition CE Router MAY use other Clients). The IPv6 Transition CE Router MAY use other
mechanisms to configure MAP-T parameters. Such mechanisms mechanisms to configure MAP-T parameters. Such mechanisms
are outside the scope of this document. are outside the scope of this document.
skipping to change at page 10, line 7 skipping to change at page 10, line 13
still be provided using IPv4 to the customer LANs. still be provided using IPv4 to the customer LANs.
If the IPv6 Transition CE Router supports delivery of IPv4 multicast If the IPv6 Transition CE Router supports delivery of IPv4 multicast
services, then it MUST support [RFC8114] (Delivery of IPv4 Multicast services, then it MUST support [RFC8114] (Delivery of IPv4 Multicast
Services to IPv4 Clients over an IPv6 Multicast Network) and Services to IPv4 Clients over an IPv6 Multicast Network) and
[RFC8115] (DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 [RFC8115] (DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes). Prefixes).
5. UPnP Support 5. UPnP Support
UPnP SHOULD be disabled by default on the IPv6 Transition CE Router UPnP SHOULD be disabled by DEFAULT on the IPv6 Transition CE Router
when using an IPv4aaS transition mechanism. when using an IPv4aaS transition mechanism.
UPnP MAY be enabled when a IPv6 Transition CE Router is configured to UPnP MAY be enabled when an IPv6 Transition CE Router is configured
use a stateless mechanism that allows unsolicited inbound packets to use a stateless mechanism that allows unsolicited inbound packets
through to the CE, such as MAP or lw4o6, or when configured with 4 a through to the CE, such as MAP or lw4o6, or when configured with a
port set containing all 65535 ports, e.g. with an IPv4 address port set containing all 65535 ports, e.g., with an IPv4 address
sharing ratio of 1. sharing ratio of 1.
If UPnP is enabled on a IPv6 Transition CE Router, the UPnP agent If UPnP is enabled on an IPv6 Transition CE Router, the UPnP agent
MUST reject any port mapping requests for ports outside of the port MUST reject any port mapping requests for port numbers outside of the
set allocated to the IPv6 Transition CE Router. port set allocated to the IPv6 Transition CE Router.
UPnP MAY also be enabled on a IPv6 Transition CE Router configured UPnP SHOULD also be enabled on an IPv6 Transition CE Router
for IPv4aaS mechanisms that support PCP [RFC6887], if implemented in configured for IPv4aaS mechanisms that support PCP [RFC6887], if
conjunction with a method to control the external port mapping, such implemented in conjunction with a method to control the external port
as IGD-PCP IWF [RFC6970]. mapping, such as IGD-PCP IWF [RFC6970].
A IPv6 Transition CE Router that implements a UPnP agent, SHOULD A IPv6 Transition CE Router that implements a UPnP agent, SHOULD
support the Open Connectivity Foundation's IGD:2 specification, support the Open Connectivity Foundation's IGD:2 specification,
including the AddAnyPortMapping() function. including the AddAnyPortMapping() function.
6. Differences from RFC7084 6. Differences from RFC7084
This document no longer consider the need to support 6rd ([RFC5969]) This document no longer considers the need to support 6rd ([RFC5969])
and includes slightly different requirements for DS-LITE [RFC6333]. and includes slightly different requirements for DS-LITE [RFC6333].
7. Code Considerations 7. Code Considerations
One of the apparent main issues for vendors to include new One of the apparent main issues for vendors to include new
functionalities, such as support for new transition mechanisms, is functionalities, such as support for new transition mechanisms, is
the lack of space in the flash (or equivalent) memory. However, it the lack of space in the flash (or equivalent) memory. However, it
has been confirmed from existing open source implementations has been confirmed from existing open source implementations
(OpenWRT/LEDE, Linux, others), that adding the support for the new (OpenWRT/LEDE, Linux, others), that adding the support for the new
transitions mechanisms, requires around 10-12 Kbytes (because most of transitions mechanisms, requires around 10-12 Kbytes (because most of
skipping to change at page 11, line 19 skipping to change at page 11, line 26
8. Security Considerations 8. Security Considerations
The IPv6 Transition CE Router must comply with the Security The IPv6 Transition CE Router must comply with the Security
Considerations as stated in [RFC7084], as well as those stated by Considerations as stated in [RFC7084], as well as those stated by
each transition mechanism implemented by the IPv6 Transition CE each transition mechanism implemented by the IPv6 Transition CE
Router. Router.
9. IANA Considerations 9. IANA Considerations
IANA is instructed, by means of this document, to create a new Option IANA is requested, by means of this document, to update the "Option
Code for 464XLAT in the registry "Option Codes permitted in the S46 Codes permitted in the S46 Priority Option" registry available at
Priority Option", with a referente to this document, as follows. https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-
parameters.xhtml#option-codes-s46-priority-option, with the following
entry.
+-------------+--------------------+-----------+ +-------------+--------------------+-----------+
| Option Code | S46 Mechanism | Reference | | Option Code | S46 Mechanism | Reference |
+-------------+--------------------+-----------+ +-------------+--------------------+-----------+
| 113 | 464XLAT | [thisdoc] | | 113 | 464XLAT | [thisdoc] |
+-------------+--------------------+-----------+ +-------------+--------------------+-----------+
Table 1: DHCPv6 Option Code for 464XLAT Table 1: DHCPv6 Option Code for 464XLAT
10. Acknowledgements 10. Acknowledgements
skipping to change at page 17, line 7 skipping to change at page 17, line 7
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. RFC8026 update removed, not needed with new approach. 1. RFC8026 update removed, not needed with new approach.
2. TRANS and 464XLAT requirements reworded in order to match new 2. TRANS and 464XLAT requirements reworded in order to match new
approach to allow operator control on each/all the transition approach to allow operator control on each/all the transition
mechanisms. mechanisms.
3. Added text in 464XLAT to clarify the usage. 3. Added text in 464XLAT to clarify the usage.
16. References 16. ANNEX F: Changes from -03
16.1. Normative References Section to be removed for WGLC. Significant updates are:
1. Several editorial changes across the document, specially TRANS
requirements.
2. DNS proxy MUST instead of SHOULD.
17. References
17.1. Normative References
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
DOI 10.17487/RFC3633, December 2003, DOI 10.17487/RFC3633, December 2003,
<https://www.rfc-editor.org/info/rfc3633>. <https://www.rfc-editor.org/info/rfc3633>.
skipping to change at page 19, line 48 skipping to change at page 20, line 10
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,
<https://www.rfc-editor.org/info/rfc8114>. <https://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,
<https://www.rfc-editor.org/info/rfc8115>. <https://www.rfc-editor.org/info/rfc8115>.
16.2. Informative References 17.2. Informative References
[IPv6Survey] [IPv6Survey]
Palet Martinez, J., "IPv6 Deployment Survey", January Palet Martinez, J., "IPv6 Deployment Survey", January
2018, 2018,
<https://indico.uknof.org.uk/event/41/contribution/5/ <https://indico.uknof.org.uk/event/41/contribution/5/
material/slides/0.pdf>. material/slides/0.pdf>.
[RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking [RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking
Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April
2016, <https://www.rfc-editor.org/info/rfc7788>. 2016, <https://www.rfc-editor.org/info/rfc7788>.
 End of changes. 33 change blocks. 
90 lines changed or deleted 109 lines changed or added

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