Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions
RFC 7678
Document | Type | RFC - Proposed Standard (October 2015; No errata) | |
---|---|---|---|
Authors | Cathy Zhou , Tom Taylor , Qiong Sun , Mohamed Boucadair | ||
Last updated | 2015-10-22 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Lionel Morand | ||
Shepherd write-up | Show (last changed 2015-06-24) | ||
IESG | IESG state | RFC 7678 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Stephen Farrell | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) C. Zhou Request for Comments: 7678 Huawei Technologies Category: Standards Track T. Taylor ISSN: 2070-1721 PT Taylor Consulting Q. Sun China Telecom M. Boucadair France Telecom October 2015 Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions Abstract During the transition from IPv4 to IPv6, customer equipment may have to support one of the various transition methods that have been defined for carrying IPv4 packets over IPv6. This document enumerates the information that needs to be provisioned on a customer edge router to support a list of transition techniques based on tunneling IPv4 in IPv6, with a view to defining reusable components for a reasonable transition path between these techniques. To the extent that the provisioning is done dynamically, Authentication, Authorization, and Accounting (AAA) support is needed to provide the information to the network server responsible for passing the information to the customer equipment. This document specifies Diameter (RFC 6733) Attribute-Value Pairs (AVPs) to be used for that purpose. Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7678. Zhou, et al. Standards Track [Page 1] RFC 7678 AVPs for 4over6 CPE Provisioning October 2015 Copyright Notice Copyright (c) 2015 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 (http://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. Zhou, et al. Standards Track [Page 2] RFC 7678 AVPs for 4over6 CPE Provisioning October 2015 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5 2. Description of the Parameters Required by Each Transition Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Parameters for Dual-Stack Lite (DS-Lite) . . . . . . . . 6 2.2. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . . . 6 2.3. Port Set Specification . . . . . . . . . . . . . . . . . 7 2.4. Mapping of Address and Port with Encapsulation (MAP-E) . 7 2.5. Parameters for Multicast . . . . . . . . . . . . . . . . 8 2.6. Summary and Discussion . . . . . . . . . . . . . . . . . 9 3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . 9 3.1. IP-Prefix-Length AVP . . . . . . . . . . . . . . . . . . 10 3.2. Border-Router-Name AVP . . . . . . . . . . . . . . . . . 10 3.3. 64-Multicast-Attributes AVP . . . . . . . . . . . . . . . 10 3.3.1. ASM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 11 3.3.2. SSM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 11 3.3.3. Delegated-IPv6-Prefix AVP as uPrefix64 . . . . . . . 12 3.4. Tunnel-Source-Pref-Or-Addr AVP . . . . . . . . . . . . . 12 3.4.1. Delegated-IPv6-Prefix as the IPv6 Binding Prefix . . 12 3.4.2. Tunnel-Source-IPv6-Address AVP . . . . . . . . . . . 12 3.5. Port-Set-Identifier . . . . . . . . . . . . . . . . . . . 13 3.6. Lw4o6-Binding AVP . . . . . . . . . . . . . . . . . . . . 13 3.6.1. Lw4o6-External-IPv4-Addr AVP . . . . . . . . . . . . 14 3.7. MAP-E-Attributes . . . . . . . . . . . . . . . . . . . . 14Show full document text