Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

S. Jiang, Ed.
Y. Fu, Ed.
C. Xie
T. Li
M. Boucadair, Ed.

Stream:

IETF

Source:

softwire (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8658

Discuss this RFC: Send questions or comments to the mailing listsoftwires@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8658

Abstract

IPv4-over-IPv6 transition mechanisms provide IPv4 connectivityservices over IPv6 native networks during the IPv4/IPv6 coexistenceperiod. DHCPv6 options have been defined to configure clients forLightweight 4over6, Mapping of Address and Port with Encapsulation(MAP-E), Mapping of Address and Port using Translation (MAP-T)unicast softwire mechanisms, and multicast softwires. However, inmany networks, configuration information is stored in anAuthentication, Authorization, and Accounting (AAA) server, whichutilizes the Remote Authentication Dial In User Service (RADIUS)protocol to provide centralized management for users. When a newtransition mechanism is developed, new RADIUS attributes need to bedefined correspondingly.

This document defines new RADIUS attributes to carry softwireconfiguration parameters based on Address plus Port from a AAA serverto a Broadband Network Gateway. Both unicast and multicastattributes are covered.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.