draft-ietf-v6ops-transition-ipv4aas-05.txt   draft-ietf-v6ops-transition-ipv4aas-06.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: January 21, 2019 D-Link Systems, Inc. Expires: February 11, 2019 D-Link Systems, Inc.
M. Kawashima M. Kawashima
NEC Platforms, Ltd. NEC Platforms, Ltd.
July 20, 2018 August 10, 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-05 draft-ietf-v6ops-transition-ipv4aas-06
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 January 21, 2019. This Internet-Draft will expire on February 11, 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 41 skipping to change at page 2, line 41
3.2.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8 3.2.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 8
3.2.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 9
4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . 12 11. Annex A: Usage Scenarios . . . . . . . . . . . . . . . . . . 11
12. Annex B: End-User Network Architecture . . . . . . . . . . . 14 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. ANNEX F: Changes from -03 . . . . . . . . . . . . . . . . . . 17 16. ANNEX F: Changes from -03 . . . . . . . . . . . . . . . . . . 17
17. ANNEX F: Changes from -04 . . . . . . . . . . . . . . . . . . 17 17. ANNEX F: Changes from -04 . . . . . . . . . . . . . . . . . . 17
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 18. ANNEX G: Changes from -05 . . . . . . . . . . . . . . . . . . 17
18.1. Normative References . . . . . . . . . . . . . . . . . . 17 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
18.2. Informative References . . . . . . . . . . . . . . . . . 20 19.1. Normative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 19.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
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 rely upon "Basic Requirements for IPv6 Customer Edge These routers rely upon "Basic Requirements for IPv6 Customer Edge
Routers" ([RFC7084]), so the scope of this document is to ensure the Routers" ([RFC7084]), so the scope of this document is to ensure the
IPv4 "service continuity" support, in the LAN side and the access to IPv4 "service continuity" support, in the LAN side and the access to
IPv4-only Internet services from an IPv6-only access WAN even from IPv4-only Internet services from an IPv6-only access 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, or want to have, an IPv6-only access network. This is a
a world where IPv4 addresses are no longer available, so the service common situation in a world where IPv4 addresses are no longer
providers need to provision IPv6-only WAN access. At the same time, available, so the service providers need to provision IPv6-only WAN
they need to ensure that both IPv4-only and IPv6-only devices or access. At the same time, they need to ensure that both IPv4-only
applications in the customer networks, can still reach IPv4-only and IPv6-only devices or applications in the customer networks, can
devices and applications in the Internet. still reach IPv4-only 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
supported by an IPv6 Transition CE Router, and relevant provisioning supported by an IPv6 Transition CE Router, and relevant provisioning
or configuration information differences from [RFC7084]. or configuration information differences from [RFC7084].
This document is not a recommendation for service providers to use This document is not a recommendation for service providers to use
any specific transition mechanism. any specific transition mechanism.
Automatic provisioning of more complex topology than a single router Automatic provisioning of more complex topology than a single router
with multiple LAN interfaces may be handled by means of HNCP with multiple LAN interfaces may be handled by means of HNCP
skipping to change at page 5, line 16 skipping to change at page 5, line 16
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
several transition mechanism and/or native IPv4. several transition mechanisms 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 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
skipping to change at page 5, line 47 skipping to change at page 5, line 47
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.
TRANS-6: If an IPv6 Transition CE Router supports more than one LAN
subnet, the IPv6 Transition CE Router MUST allow
appropriate subnetting and configuring the address space
(which may depend on each transition mechanism) among the
several interfaces. In some transition mechanisms, this
may require differentiating mappings/translations per
interfaces.
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.2.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.
skipping to change at page 10, line 19 skipping to change at page 10, line 21
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 If the UPnP WANIPConnection:2 service [UPnP-WANIPC] is enabled on a
when using an IPv4aaS transition mechanism. CE router, but cannot be associated with an IPv4 interface
established by an IPv4aaS mechanism or cannot determine which ports
UPnP MAY be enabled when an IPv6 Transition CE Router is configured are available (through PCP or access to a configured port set, if the
to use a stateless mechanism that allows unsolicited inbound packets IPv4aaS mechanism limits the available ports), an AddPortMapping() or
through to the CE, such as MAP or lw4o6, or when configured with a AddAnyPortMapping() action MUST be rejected with error code 729
port set containing all 65535 ports, e.g., with an IPv4 address "ConflictWithOtherMechanisms".
sharing ratio of 1.
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
port set allocated to the IPv6 Transition CE Router.
UPnP SHOULD also be enabled on an IPv6 Transition CE Router An AddPortMapping() request for a port that is not available MUST
configured for IPv4aaS mechanisms that support PCP [RFC6887], if result in "ConflictInMappingEntry".
implemented in conjunction with a method to control the external port
mapping, such as IGD-PCP IWF [RFC6970].
An IPv6 Transition CE Router that implements a UPnP agent, SHOULD Note that IGD:1 and its WANIPConnection:1 service have been
support the Open Connectivity Foundation's IGD:2 specification, deprecated by OCF.
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
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
skipping to change at page 11, line 49 skipping to change at page 11, line 44
+-------------+--------------------+-----------+ +-------------+--------------------+-----------+
| 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 Lorenzo Colitti, for their review and Ole Troan, James Woodyatt, Lorenzo Colitti and Alejandro D'Egidio,
comments in this and/or previous versions of this document. for their review and 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.
skipping to change at page 17, line 26 skipping to change at page 17, line 26
17. ANNEX F: Changes from -04 17. ANNEX F: Changes from -04
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. Removed G-1. 1. Removed G-1.
2. Added support for draft-pref64folks-6man-ra-pref64. 2. Added support for draft-pref64folks-6man-ra-pref64.
3. General text clarifications. 3. General text clarifications.
18. References 18. ANNEX G: Changes from -05
18.1. Normative References Section to be removed for WGLC. Significant updates are:
1. Reworded and shorter UPnP section and new informative reference.
2. New general transition requirement in case multiple public IPv4
prefixes are provided, so to run multiple instances according to
each specific transition mechanism.
3. General text clarifications.
19. References
19.1. Normative References
[I-D.pref64folks-6man-ra-pref64] [I-D.pref64folks-6man-ra-pref64]
Colitti, L., Kline, E., and J. Linkova, "Discovering Colitti, L., Kline, E., and J. Linkova, "Discovering
PREF64 in Router Advertisements", draft-pref64folks-6man- PREF64 in Router Advertisements", draft-pref64folks-6man-
ra-pref64-00 (work in progress), July 2018. ra-pref64-01 (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 20, line 16 skipping to change at page 20, line 31
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>.
18.2. Informative References 19.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>.
[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/>.
[UPnP-WANIPC]
UPnP Forum, "WANIPConnection:2 Service", December 2010,
<http://upnp.org/specs/gw/
UPnP-gw-WANIPConnection-v2-Service.pdf>.
Authors' Addresses Authors' Addresses
Jordi Palet Martinez Jordi Palet Martinez
The IPv6 Company The IPv6 Company
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@theipv6company.com Email: jordi.palet@theipv6company.com
URI: http://www.theipv6company.com/ URI: http://www.theipv6company.com/
 End of changes. 18 change blocks. 
42 lines changed or deleted 61 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/