Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service
RFC 8585
Document | Type | RFC - Informational (May 2019; No errata) | |
---|---|---|---|
Authors | Jordi Palet Martinez , Hans Liu , Masanobu Kawashima | ||
Last updated | 2019-05-02 | ||
Replaces | draft-palet-v6ops-transition-ipv4aas | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Ron Bonica | ||
Shepherd write-up | Show (last changed 2018-09-07) | ||
IESG | IESG state | RFC 8585 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Warren Kumari | ||
Send notices to | Ron Bonica <rbonica@juniper.net> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) J. Palet Martinez Request for Comments: 8585 The IPv6 Company Category: Informational H. M.-H. Liu ISSN: 2070-1721 D-Link Systems, Inc. M. Kawashima NEC Platforms, Ltd. May 2019 Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service Abstract This document specifies the IPv4 service continuity requirements for IPv6 Customer Edge (CE) routers that are provided either by the service provider or by vendors who sell through the retail market. Specifically, this document extends the basic requirements for IPv6 CE routers as described in RFC 7084 to allow the provisioning of IPv6 transition services for the support of IPv4-as-a-Service (IPv4aaS) by means of new transition mechanisms. The document only covers IPv4aaS, i.e., transition technologies for delivering IPv4 in IPv6-only access networks. IPv4aaS is necessary because there aren't sufficient IPv4 addresses available for every possible customer/ device. However, devices or applications in the customer Local Area Networks (LANs) may be IPv4-only or IPv6-only and still need to communicate with IPv4-only services on the Internet. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8585. Palet Martinez, et al. Informational [Page 1] RFC 8585 Requirements for IPv6 CE to Support IPv4aaS May 2019 Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. LAN-Side Configuration . . . . . . . . . . . . . . . . . 5 3.2. Transition Technologies Support for IPv4 Service Continuity (IPv4-as-a-Service) . . . . . . . . . . . . . 5 3.2.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 7 3.2.2. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 8 3.2.3. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 9 3.2.4. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 10 3.2.5. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 10 4. IPv4 Multicast Support . . . . . . . . . . . . . . . . . . . 11 5. UPnP Support . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Comparison to RFC 7084 . . . . . . . . . . . . . . . . . . . 12 7. Code Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 16 Appendix A. Usage Scenarios . . . . . . . . . . . . . . . . . . 17 Appendix B. End-User Network Architecture . . . . . . . . . . . 18 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Palet Martinez, et al. Informational [Page 2] RFC 8585 Requirements for IPv6 CE to Support IPv4aaS May 2019Show full document text