RFC 8658

RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P), November 2019

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
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

DOI:  10.17487/RFC8658

Discuss this RFC: Send questions or comments to softwires@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity services over IPv6 native networks during the IPv4/IPv6 coexistence period. DHCPv6 options have been defined to configure clients for Lightweight 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, in many networks, configuration information is stored in an Authentication, Authorization, and Accounting (AAA) server, which utilizes the Remote Authentication Dial In User Service (RADIUS) protocol to provide centralized management for users. When a new transition mechanism is developed, new RADIUS attributes need to be defined correspondingly.

This document defines new RADIUS attributes to carry softwire configuration parameters based on Address plus Port from a AAA server to a Broadband Network Gateway. Both unicast and multicast attributes are covered.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader