draft-ietf-v6ops-transition-ipv4aas-09.txt   draft-ietf-v6ops-transition-ipv4aas-10.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: April 8, 2019 D-Link Systems, Inc. Expires: April 19, 2019 D-Link Systems, Inc.
M. Kawashima M. Kawashima
NEC Platforms, Ltd. NEC Platforms, Ltd.
October 5, 2018 October 16, 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-09 draft-ietf-v6ops-transition-ipv4aas-10
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 through the retail market. provider or through 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)
by means of new transition mechanisms. The document only covers by means of new transition mechanisms. The document only covers
transition technologies for delivering IPv4 in IPv6-only access transition technologies for delivering IPv4 in IPv6-only access
networks, commonly called "IPv4 as-a-Service" (IPv4aaS). This is networks, commonly called "IPv4 as-a-Service" (IPv4aaS). This is
required in a world where public IPv4 addresses are no longer required in a world where sufficient IPv4 addresses are no longer
available for every possible customer. However, devices or available for every possible customer/device. However, devices or
applications in the customer LANs may be IPv4-only or IPv6-only and applications in the customer LANs may be IPv4-only or IPv6-only and
still need to communicate with IPv4-only services at the Internet. still need to communicate with IPv4-only services at the Internet.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 April 8, 2019. This Internet-Draft will expire on April 19, 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 . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . 5
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. Comparison to RFC7084 . . . . . . . . . . . . . . . . . . . . 10 6. Comparison to RFC7084 . . . . . . . . . . . . . . . . . . . . 11
7. Code Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. Code Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
11. Annex A: Usage Scenarios . . . . . . . . . . . . . . . . . . 12 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 G: Changes from -04 . . . . . . . . . . . . . . . . . . 17 17. ANNEX G: Changes from -04 . . . . . . . . . . . . . . . . . . 17
18. ANNEX H: Changes from -05 . . . . . . . . . . . . . . . . . . 17 18. ANNEX H: Changes from -05 . . . . . . . . . . . . . . . . . . 17
19. ANNEX I: Changes from -06 . . . . . . . . . . . . . . . . . . 17 19. ANNEX I: Changes from -06 . . . . . . . . . . . . . . . . . . 17
20. ANNEX J: Changes from -07 . . . . . . . . . . . . . . . . . . 17 20. ANNEX J: Changes from -07 . . . . . . . . . . . . . . . . . . 17
21. ANNEX K: Changes from -08 . . . . . . . . . . . . . . . . . . 18 21. ANNEX K: Changes from -08 . . . . . . . . . . . . . . . . . . 18
22. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 22. ANNEX K: Changes from -09 . . . . . . . . . . . . . . . . . . 18
22.1. Normative References . . . . . . . . . . . . . . . . . . 18 23. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
22.2. Informative References . . . . . . . . . . . . . . . . . 20 23.1. Normative References . . . . . . . . . . . . . . . . . . 18
23.2. Informative References . . . . . . . . . . . . . . . . . 21
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.
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, or want to have, an IPv6-only access network. This is a ISPs have, or want to have, an IPv6-only access network. This is a
common situation in a world where public IPv4 addresses are no longer common situation in a world where sufficient public IPv4 addresses
available for every possible customer, and become prohibitive are no longer available for every possible customer and device, and
expense, so the service providers need to provision IPv6-only WAN become prohibitive expense, so the service providers need to
access. At the same time, they need to ensure that both IPv4-only provision IPv6-only WAN access. At the same time, they need to
and IPv6-only devices or applications in the customer networks can ensure that both IPv4-only and IPv6-only devices or applications in
still reach IPv4-only devices and applications in the Internet. the customer networks can 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 18, line 11 skipping to change at page 18, line 11
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. Added text to UPnP section. 1. Added text to UPnP section.
21. ANNEX K: Changes from -08 21. ANNEX K: Changes from -08
Section to be removed for WGLC. Significant updates are: Section to be removed for WGLC. Significant updates are:
1. Editorial edits. 1. Editorial edits.
22. References 22. ANNEX K: Changes from -09
22.1. Normative References Section to be removed for WGLC. Significant updates are:
1. Minor editorial edit.
23. References
23.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 48 skipping to change at page 21, line 5
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>.
22.2. Informative References 23.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>.
[OpenWRT] OpenWRT, "OpenWRT Packages", January 2018, [OpenWRT] OpenWRT, "OpenWRT Packages", January 2018,
<https://openwrt.org/packages/start>. <https://openwrt.org/packages/start>.
 End of changes. 13 change blocks. 
21 lines changed or deleted 29 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/