draft-ietf-v6ops-transition-ipv4aas-04.txt   draft-ietf-v6ops-transition-ipv4aas-05.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 26, 2018 D-Link Systems, Inc. Expires: January 21, 2019 D-Link Systems, Inc.
M. Kawashima M. Kawashima
NEC Platforms, Ltd. NEC Platforms, Ltd.
June 24, 2018 July 20, 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-04 draft-ietf-v6ops-transition-ipv4aas-05
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 26, 2018. This Internet-Draft will expire on January 21, 2019.
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 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . . . . . . 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. LAN-Side Configuration . . . . . . . . . . . . . . . . . 4
3.2. LAN-Side Configuration . . . . . . . . . . . . . . . . . 5 3.2. 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.2.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7 3.2.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7
3.3.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8 3.2.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8
3.3.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9
4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 9 4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . 12
12. Annex B: End-User Network Architecture . . . . . . . . . . . 13 12. Annex B: End-User Network Architecture . . . . . . . . . . . 14
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. ANNEX F: Changes from -03 . . . . . . . . . . . . . . . . . . 17 16. ANNEX F: Changes from -03 . . . . . . . . . . . . . . . . . . 17
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 17. ANNEX F: Changes from -04 . . . . . . . . . . . . . . . . . . 17
17.1. Normative References . . . . . . . . . . . . . . . . . . 17 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
17.2. Informative References . . . . . . . . . . . . . . . . . 20 18.1. Normative References . . . . . . . . . . . . . . . . . . 17
18.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.
These routers are likely to rely upon "Basic Requirements for IPv6 These routers rely upon "Basic Requirements for IPv6 Customer Edge
Customer Edge Routers" ([RFC7084]), so the scope of this document is Routers" ([RFC7084]), so the scope of this document is to ensure the
to ensure the IPv4 "service continuity" support, in the LAN side and IPv4 "service continuity" support, in the LAN side and the access to
the access to IPv4-only Internet services from an IPv6-only access IPv4-only Internet services from an IPv6-only access WAN even from
WAN even from IPv6-only applications or devices in the LAN side. IPv6-only applications or devices in the LAN side.
This document covers a set of IP transition techniques required when This document covers a set of IP transition techniques required when
ISPs have an IPv6-only access network. This is a common situation in ISPs have an IPv6-only access network. This is a common situation in
a world where IPv4 addresses are no longer available, so the service a world where IPv4 addresses are no longer available, so the service
providers need to provision IPv6-only WAN access. At the same time, providers need to provision IPv6-only WAN access. At the same time,
they need to ensure that both IPv4-only and IPv6-only devices or they need to ensure that both IPv4-only and IPv6-only devices or
applications in the customer networks, can still reach IPv4-only applications in the customer networks, can still reach IPv4-only
devices and applications in the Internet. devices and applications in the Internet.
This document specifies the IPv4 service continuity mechanisms to be This document specifies the IPv4 service continuity mechanisms to be
skipping to change at page 4, line 41 skipping to change at page 4, line 41
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) and this document add Requirements for IPv6 Customer Edge Routers) and this document add
new requirements, as described in the following sub-sections. new requirements, as described in the following sub-sections.
3.1. General Requirements 3.1. LAN-Side Configuration
A new general requirement is added, in order to ensure that the IPv6
Transition CE Router respects the IPv6 prefix length as a parameter:
G-1: The IPv6 Transition CE Router MUST comply with [RFC7608] (IPv6
Prefix Length Recommendation for Forwarding).
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-1: The IPv6 Transition CE Router MUST 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.2. 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 one or This document takes no position on simultaneous operation of one or
skipping to change at page 5, line 38 skipping to change at page 5, line 29
Customer LANs, allowing an automated IPv6 transition mechanism Customer LANs, allowing an automated IPv6 transition mechanism
provisioning, general transition requirements are defined. provisioning, general transition requirements are defined.
General transition requirements: General transition requirements:
TRANS-1: The IPv6 Transition CE Router MUST support the DHCPv6 S46 TRANS-1: The IPv6 Transition CE Router MUST support the DHCPv6 S46
priority options described in [RFC8026] (Unified IPv4-in- priority options described in [RFC8026] (Unified IPv4-in-
IPv6 Softwire Customer Premises Equipment (CPE): A IPv6 Softwire Customer Premises Equipment (CPE): A
DHCPv6-Based Prioritization Mechanism). 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, CLI and/or
option to manually enable/disable each of the supported API option to manually enable/disable each of the supported
transition mechanisms. transition mechanisms.
TRANS-3: The IPv6 Transition CE Router MUST request the relevant TRANS-3: The IPv6 Transition CE Router MUST request the relevant
configuration options for each supported transition configuration options for each supported transition
mechanisms, which MUST remain disabled at this step. mechanisms, which MUST remain disabled at this step.
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 allows enabling/disabling a OPTION_S46_PRIORITY, which allows enabling/disabling 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.2.1. 464XLAT
464XLAT [RFC6877] is a technique to provide IPv4 service over an 464XLAT [RFC6877] is a technique to provide IPv4 service over an
IPv6-only access network without encapsulation. This architecture IPv6-only access network without encapsulation. This architecture
assumes a NAT64 [RFC6146] (Stateful NAT64: Network Address and assumes a NAT64 [RFC6146] (Stateful NAT64: Network Address and
Protocol Translation from IPv6 Clients to IPv4 Servers) function Protocol Translation from IPv6 Clients to IPv4 Servers) function
deployed at the service provider or a third-party network. deployed at the service provider or a third-party network.
The IPv6 Transition CE Router SHOULD support CLAT functionality. If The IPv6 Transition CE Router SHOULD support CLAT functionality. If
464XLAT is supported, it MUST be implemented according to [RFC6877]. 464XLAT is supported, it MUST be implemented according to [RFC6877].
The following IPv6 Transition CE Router requirements also apply: The following IPv6 Transition CE Router requirements also apply:
skipping to change at page 6, line 42 skipping to change at page 6, line 37
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). Following ([RFC6887]), if no PCP server is the PCP). Following ([RFC6887]), if no PCP server is
configured, the IPv6 Transition CE Router MAY verify if configured, the IPv6 Transition CE Router MAY verify if
the default gateway, or the NAT64 is the PCP server. A the default gateway, or the NAT64 is the PCP server. A
plain IPv6 mode MUST be used to send PCP requests to the plain IPv6 mode MUST be used to send PCP requests to the
server. server.
464XLAT-4: The IPv6 Transition CE Router MUST implement [RFC7050] 464XLAT-4: The IPv6 Transition CE Router MUST implement
(Discovery of the IPv6 Prefix Used for IPv6 Address [I-D.pref64folks-6man-ra-pref64] (Discovering PREF64 in
Synthesis) in order to discover the PLAT-side translation Router Advertisements) and [RFC7050] (Discovery of the
IPv4 and IPv6 prefix(es)/suffix(es). IPv6 Prefix Used for IPv6 Address Synthesis) in order to
discover the PLAT-side translation 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
PCP-controlled NAT64 device. PCP-controlled NAT64 device.
464XLAT-6: A DHCPv6 Option "OPTION_V6_PREFIX64" ([RFC8115]), with 464XLAT-6: [RFC8115] MUST be implemented and a DHCPv6 Option
zeroed ASM_mPrefix64 and SSM_mPrefix64, MUST also be "OPTION_V6_PREFIX64" ([RFC8115]), with zeroed
considered as a valid NAT64 prefix (uPrefix64). ASM_mPrefix64 and SSM_mPrefix64, MUST also be considered
as a valid NAT64 prefix (uPrefix64).
464XLAT-7: If a DHCPv6 Option "OPTION_V6_PREFIX64" ([RFC8115]), with 464XLAT-7: The priority for the NAT64 prefix, in case the network
provides several choices, MUST be: 1) [RFC7225], 2)
[RFC8115], 3) [I-D.pref64folks-6man-ra-pref64] and 4)
[RFC7050].
464XLAT-8: If a DHCPv6 Option "OPTION_V6_PREFIX64" ([RFC8115]), with
zeroed ASM_mPrefix64 and SSM_mPrefix64 provides a NAT64 zeroed ASM_mPrefix64 and SSM_mPrefix64 provides a NAT64
prefix, or one or more NAT64 prefixes are learnt by means prefix, or one or more NAT64 prefixes are learnt by means
of either [RFC7050] or [RFC7225], then 464XLAT MUST be of either [RFC7050] or [RFC7225], then 464XLAT MUST be
included in the candidate list of possible S46 mechanism included in the candidate list of possible S46 mechanism
(Section 1.4.1 of [RFC8026]). (Section 1.4.1 of [RFC8026]).
The NAT64 prefix could be discovered by means of [RFC7050] only in The NAT64 prefix could be discovered by means of [RFC7050] only in
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.2.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. Dual-Stack Lite enables a broadband service provider to services. Dual-Stack Lite enables a broadband service provider to
share IPv4 addresses among customers by combining two well-known share IPv4 addresses among customers by combining two well-known
technologies: IP in IP (IPv4-in-IPv6) and Network Address Translation technologies: IP in IP (IPv4-in-IPv6) and Network Address Translation
(NAT). It is expected that DS-Lite traffic is forwarded over the (NAT). It is expected that DS-Lite traffic is forwarded over the
IPv6 Transition CE Router's native IPv6 WAN interface, and not IPv6 Transition CE Router's native IPv6 WAN interface, and not
encapsulated in another tunnel. encapsulated in another tunnel.
The IPv6 Transition CE Router SHOULD implement DS-Lite B4 The IPv6 Transition CE Router SHOULD implement DS-Lite B4
skipping to change at page 8, line 15 skipping to change at page 8, line 18
PCP). If PCP ([RFC6887]) is implemented and a PCP server PCP). If PCP ([RFC6887]) is implemented and a PCP server
is not configured, the IPv6 Transition CE Router MUST is not configured, the IPv6 Transition CE Router MUST
assume, by DEFAULT, that the AFTR is the PCP server. A assume, by DEFAULT, that the AFTR is the PCP server. A
plain IPv6 mode MUST be 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.2.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 lwB4 functionality The IPv6 Transition CE Router SHOULD implement lwB4 functionality
[RFC7596]. If DS-Lite is implemented, lw4o6 SHOULD be supported as [RFC7596]. If DS-Lite is implemented, lw4o6 SHOULD be supported as
well. If lw4o6 is supported, it MUST be implemented according to well. If lw4o6 is supported, it MUST be implemented according to
skipping to change at page 8, line 46 skipping to change at page 9, line 5
mechanisms are outside the scope of this document. mechanisms are outside the scope of this document.
LW4O6-2: The IPv6 Transition CE Router MUST support the DHCPv4-over- LW4O6-2: The IPv6 Transition CE Router MUST support the DHCPv4-over-
DHCPv6 (DHCP 4o6) transport described in [RFC7341] (DHCPv4- DHCPv6 (DHCP 4o6) transport described in [RFC7341] (DHCPv4-
over-DHCPv6 Transport). over-DHCPv6 Transport).
LW4O6-3: The IPv6 Transition CE Router MAY support Dynamic LW4O6-3: The IPv6 Transition CE Router MAY support Dynamic
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.2.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 CE functionality The IPv6 Transition CE Router SHOULD support MAP-E CE functionality
[RFC7597]. If MAP-E is supported, it MUST be implemented according [RFC7597]. If MAP-E is supported, it MUST be implemented according
to [RFC7597]. The following IPv6 Transition CE Router requirements to [RFC7597]. The following IPv6 Transition CE Router requirements
also apply: also apply:
skipping to change at page 9, line 23 skipping to change at page 9, line 30
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.2.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 CE functionality The IPv6 Transition CE Router SHOULD support MAP-T CE functionality
[RFC7599]. If MAP-T is supported, it MUST be implemented according [RFC7599]. If MAP-T is supported, it MUST be implemented according
to [RFC7599]. The following IPv6 Transition CE Router requirements to [RFC7599]. The following IPv6 Transition CE Router requirements
also apply: also apply:
skipping to change at page 10, line 31 skipping to change at page 10, line 37
If UPnP is enabled on an 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 port numbers outside of the MUST reject any port mapping requests for port numbers outside of the
port set allocated to the IPv6 Transition CE Router. port set allocated to the IPv6 Transition CE Router.
UPnP SHOULD also be enabled on an IPv6 Transition CE Router UPnP SHOULD also be enabled on an IPv6 Transition CE Router
configured for IPv4aaS mechanisms that support PCP [RFC6887], if configured for IPv4aaS mechanisms that support PCP [RFC6887], if
implemented in conjunction with a method to control the external port implemented in conjunction with a method to control the external port
mapping, such as IGD-PCP IWF [RFC6970]. mapping, such as IGD-PCP IWF [RFC6970].
A IPv6 Transition CE Router that implements a UPnP agent, SHOULD An 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 considers 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
skipping to change at page 11, line 32 skipping to change at page 11, line 37
Router. Router.
9. IANA Considerations 9. IANA Considerations
IANA is requested, by means of this document, to update the "Option IANA is requested, by means of this document, to update the "Option
Codes permitted in the S46 Priority Option" registry available at Codes permitted in the S46 Priority Option" registry available at
https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6- https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-
parameters.xhtml#option-codes-s46-priority-option, with the following parameters.xhtml#option-codes-s46-priority-option, with the following
entry. 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
Thanks to Mikael Abrahamsson, Fred Baker, Mohamed Boucadair, Brian Thanks to Mikael Abrahamsson, Fred Baker, Mohamed Boucadair, Brian
Carpenter, Ian Farrer, Lee Howard, Richard Patterson, Barbara Stark, Carpenter, Ian Farrer, Lee Howard, Richard Patterson, Barbara Stark,
Ole Troan, James Woodyatt and ..., for their review and comments in Ole Troan, James Woodyatt and Lorenzo Colitti, for their review and
this and/or previous versions of this document. comments in this and/or previous versions of this document.
11. Annex A: Usage Scenarios 11. Annex A: Usage Scenarios
The situation previously described, where there is ongoing IPv6 The situation previously described, where there is ongoing IPv6
deployment and lack of IPv4 addresses, is not happening at the same deployment and lack of IPv4 addresses, is not happening at the same
pace at every country, and even within every country, every ISP. For pace at every country, and even within every country, every ISP. For
different technical, financial, commercial/marketing and socio- different technical, financial, commercial/marketing and socio-
economic reasons, each network is transitioning at their own pace, economic reasons, each network is transitioning at their own pace,
and nobody has a magic crystal ball, to make a guess. and nobody has a magic crystal ball, to make a guess.
Different studies (for example [IPv6Survey]) also show that this is a Different studies (for example [IPv6Survey]) also show that this is a
changing situation, because in a single country, it may be that not changing situation, because in a single country, it may be that not
all operators provide IPv6 support, and consumers may switch ISPs and all operators provide IPv6 support, and consumers may switch ISPs and
use the same IPv6 Transition CE Router with an ISP that provides use the same IPv6 Transition CE Router with an ISP that provides
IPv4-only and an ISP that provides IPv6 plus IPv4aaS. IPv4-only and an ISP that provides IPv6 plus IPv4aaS.
So, it is clear that, to cover all those evolving situations, a IPv6 So, it is clear that, to cover all those evolving situations, an IPv6
Transition CE Router is required, at least from the perspective of Transition CE Router is required, at least from the perspective of
the transition support, which can accommodate those changes. the transition support, which can accommodate those changes.
Moreover, because some services will remain IPv4-only for an Moreover, because some services will remain IPv4-only for an
undetermined time, and some service providers will remain IPv4-only undetermined time, and some service providers will remain IPv4-only
for an undetermined period of time, IPv4 will be needed for an for an undetermined period of time, IPv4 will be needed for an
undetermined period of time. There will be a need for CEs with undetermined period of time. There will be a need for CEs with
support "IPv4 as-a-Service" for an undetermined period of time. support "IPv4 as-a-Service" for an undetermined period of time.
This document is consequently, based on those premises, in order to This document is consequently, based on those premises, in order to
skipping to change at page 13, line 4 skipping to change at page 13, line 10
The above list is not intended to be comprehensive of all the The above list is not intended to be comprehensive of all the
possible usage scenarios, just an overall view. In fact, possible usage scenarios, just an overall view. In fact,
combinations of the above usages are also possible, as well as combinations of the above usages are also possible, as well as
situations where the same CE is used at different times in different situations where the same CE is used at different times in different
scenarios or even different services providers that may use a scenarios or even different services providers that may use a
different transition mechanism. different transition mechanism.
The mechanisms for allowing inbound connections are "naturally" The mechanisms for allowing inbound connections are "naturally"
available in any IPv6 router, as when using GUA, unless they are available in any IPv6 router, as when using GUA, unless they are
blocked by firewall rules, which may require some manual blocked by firewall rules, which may require some manual
configuration by means of a GUI and/or CLI. configuration by means of a GUI, CLI and/or API.
However, in the case of IPv4aaS, because the usage of private However, in the case of IPv4aaS, because the usage of private
addresses and NAT and even depending on the specific transition addresses and NAT and even depending on the specific transition
mechanism, it typically requires some degree of more complex manual mechanism, it typically requires some degree of more complex manual
configuration such as setting up a DMZ, virtual servers, or port/ configuration such as setting up a DMZ, virtual servers, or port/
protocol forwarding. In general, IPv4 CE Routers already provide GUI protocol forwarding. In general, IPv4 CE Routers already provide GUI
and/or CLI to manually configure them, or the possibility to setup and/or CLI to manually configure them, or the possibility to setup
the CE in bridge mode, so another CE behind it, takes care of that. the CE in bridge mode, so another CE behind it, takes care of that.
It is out of the scope of this document the definition of any It is out of the scope of this document the definition of any
requirements for that. requirements for that.
skipping to change at page 17, line 16 skipping to change at page 17, line 16
16. ANNEX F: Changes from -03 16. ANNEX F: Changes from -03
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. Several editorial changes across the document, specially TRANS 1. Several editorial changes across the document, specially TRANS
requirements. requirements.
2. DNS proxy MUST instead of SHOULD. 2. DNS proxy MUST instead of SHOULD.
17. References 17. ANNEX F: Changes from -04
17.1. Normative References Section to be removed for WGLC. Significant updates are:
1. Removed G-1.
2. Added support for draft-pref64folks-6man-ra-pref64.
3. General text clarifications.
18. References
18.1. Normative References
[I-D.pref64folks-6man-ra-pref64]
Colitti, L., Kline, E., and J. Linkova, "Discovering
PREF64 in Router Advertisements", draft-pref64folks-6man-
ra-pref64-00 (work in progress), July 2018.
[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 32 skipping to change at page 19, line 42
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
Configuration of Softwire Address and Port-Mapped Configuration of Softwire Address and Port-Mapped
Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015,
<https://www.rfc-editor.org/info/rfc7598>. <https://www.rfc-editor.org/info/rfc7598>.
[RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
and T. Murakami, "Mapping of Address and Port using and T. Murakami, "Mapping of Address and Port using
Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July
2015, <https://www.rfc-editor.org/info/rfc7599>. 2015, <https://www.rfc-editor.org/info/rfc7599>.
[RFC7608] Boucadair, M., Petrescu, A., and F. Baker, "IPv6 Prefix
Length Recommendation for Forwarding", BCP 198, RFC 7608,
DOI 10.17487/RFC7608, July 2015,
<https://www.rfc-editor.org/info/rfc7608>.
[RFC7618] Cui, Y., Sun, Q., Farrer, I., Lee, Y., Sun, Q., and M. [RFC7618] Cui, Y., Sun, Q., Farrer, I., Lee, Y., Sun, Q., and M.
Boucadair, "Dynamic Allocation of Shared IPv4 Addresses", Boucadair, "Dynamic Allocation of Shared IPv4 Addresses",
RFC 7618, DOI 10.17487/RFC7618, August 2015, RFC 7618, DOI 10.17487/RFC7618, August 2015,
<https://www.rfc-editor.org/info/rfc7618>. <https://www.rfc-editor.org/info/rfc7618>.
[RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6 [RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6
Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Softwire Customer Premises Equipment (CPE): A DHCPv6-Based
Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026, Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026,
November 2016, <https://www.rfc-editor.org/info/rfc8026>. November 2016, <https://www.rfc-editor.org/info/rfc8026>.
skipping to change at page 20, line 10 skipping to change at page 20, line 16
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>.
17.2. Informative References 18.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. 29 change blocks. 
66 lines changed or deleted 76 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/