draft-ietf-v6ops-transition-ipv4aas-06.txt   draft-ietf-v6ops-transition-ipv4aas-07.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: February 11, 2019 D-Link Systems, Inc. Expires: February 14, 2019 D-Link Systems, Inc.
M. Kawashima M. Kawashima
NEC Platforms, Ltd. NEC Platforms, Ltd.
August 10, 2018 August 13, 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-06 draft-ietf-v6ops-transition-ipv4aas-07
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 February 11, 2019. This Internet-Draft will expire on February 14, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language - Special Note . . . . . . . . . . 3 1.1. Requirements Language - Special Note . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. LAN-Side Configuration . . . . . . . . . . . . . . . . . 4 3.1. LAN-Side Configuration . . . . . . . . . . . . . . . . . 4
3.2. Transition Technologies Support for IPv4 Service 3.2. Transition Technologies Support for IPv4 Service
Continuity (IPv4 as-a-Service - IPv4aaS) . . . . . 5 Continuity (IPv4 as-a-Service - IPv4aaS) . . . . . 5
3.2.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 6 3.2.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7 3.2.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . . . 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. ANNEX F: Changes from -04 . . . . . . . . . . . . . . . . . . 17 17. ANNEX F: Changes from -04 . . . . . . . . . . . . . . . . . . 17
18. ANNEX G: Changes from -05 . . . . . . . . . . . . . . . . . . 17 18. ANNEX G: Changes from -05 . . . . . . . . . . . . . . . . . . 17
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 19. ANNEX G: Changes from -06 . . . . . . . . . . . . . . . . . . 17
19.1. Normative References . . . . . . . . . . . . . . . . . . 17 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
19.2. Informative References . . . . . . . . . . . . . . . . . 20 20.1. Normative References . . . . . . . . . . . . . . . . . . 17
20.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 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.
skipping to change at page 4, line 23 skipping to change at page 4, line 29
Additionally, the keyword "DEFAULT" is to be interpreted in this Additionally, the keyword "DEFAULT" is to be interpreted in this
document as pertaining to a configuration as applied by a vendor, document as pertaining to a configuration as applied by a vendor,
prior to the administrator changing it for its initial activation. 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 connectivity.
The term "IPv6 transition Customer Edge Router with IPv4aaS" The term "IPv6 transition Customer Edge Router with IPv4aaS"
(shortened as "IPv6 Transition CE Router") is defined as an "IPv6 (shortened as "IPv6 Transition CE Router") is defined as an "IPv6
Customer Edge Router" that provides features for the delivery of IPv4 Customer Edge Router" that provides features for the delivery of IPv4
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.
skipping to change at page 5, line 12 skipping to change at page 5, line 15
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.2. 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 in the customer-side LANs of
CE Router are able to reach the IPv4-only services. the IPv6 Transition 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 mechanisms 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:
skipping to change at page 6, line 7 skipping to change at page 6, line 11
TRANS-6: If an IPv6 Transition CE Router supports more than one LAN TRANS-6: If an IPv6 Transition CE Router supports more than one LAN
subnet, the IPv6 Transition CE Router MUST allow subnet, the IPv6 Transition CE Router MUST allow
appropriate subnetting and configuring the address space appropriate subnetting and configuring the address space
(which may depend on each transition mechanism) among the (which may depend on each transition mechanism) among the
several interfaces. In some transition mechanisms, this several interfaces. In some transition mechanisms, this
may require differentiating mappings/translations per may require differentiating mappings/translations per
interfaces. 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. An IPv6 Transition CE Router
intended for the retail market MUST support all of them.
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.
The IPv6 Transition CE Router SHOULD support CLAT functionality. If The IPv6 Transition CE Router SHOULD support CLAT functionality. If
skipping to change at page 6, line 41 skipping to change at page 6, line 46
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 464XLAT-4: The IPv6 Transition CE Router MUST implement [RFC7050]
[I-D.pref64folks-6man-ra-pref64] (Discovering PREF64 in (Discovery of the IPv6 Prefix Used for IPv6 Address
Router Advertisements) and [RFC7050] (Discovery of the Synthesis) in order to discover the PLAT-side translation
IPv6 Prefix Used for IPv6 Address Synthesis) in order to IPv4 and IPv6 prefix(es)/suffix(es).
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: [RFC8115] MUST be implemented and a DHCPv6 Option 464XLAT-6: [RFC8115] MUST be implemented and a DHCPv6 Option
"OPTION_V6_PREFIX64" ([RFC8115]), with zeroed "OPTION_V6_PREFIX64" ([RFC8115]), with zeroed
ASM_mPrefix64 and SSM_mPrefix64, MUST also be considered ASM_mPrefix64 and SSM_mPrefix64, MUST also be considered
as a valid NAT64 prefix (uPrefix64). as a valid NAT64 prefix (uPrefix64).
464XLAT-7: The priority for the NAT64 prefix, in case the network 464XLAT-7: The priority for the NAT64 prefix, in case the network
provides several choices, MUST be: 1) [RFC7225], 2) provides several choices, MUST be: 1) [RFC7225], 2)
[RFC8115], 3) [I-D.pref64folks-6man-ra-pref64] and 4) [RFC8115], and 3) [RFC7050].
[RFC7050].
464XLAT-8: If a DHCPv6 Option "OPTION_V6_PREFIX64" ([RFC8115]), with 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
skipping to change at page 17, line 38 skipping to change at page 17, line 38
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. Reworded and shorter UPnP section and new informative reference. 1. Reworded and shorter UPnP section and new informative reference.
2. New general transition requirement in case multiple public IPv4 2. New general transition requirement in case multiple public IPv4
prefixes are provided, so to run multiple instances according to prefixes are provided, so to run multiple instances according to
each specific transition mechanism. each specific transition mechanism.
3. General text clarifications. 3. General text clarifications.
19. References 19. ANNEX G: Changes from -06
19.1. Normative References Section to be removed for WGLC. Significant updates are:
[I-D.pref64folks-6man-ra-pref64] 1. Removed reference and text related to pref64folks-6man-ra-pref64.
Colitti, L., Kline, E., and J. Linkova, "Discovering
PREF64 in Router Advertisements", draft-pref64folks-6man- 2. General text clarifications.
ra-pref64-01 (work in progress), July 2018.
20. References
20.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 20, line 31 skipping to change at page 20, line 37
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>.
19.2. Informative References 20.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. 16 change blocks. 
29 lines changed or deleted 33 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/