RADIUS Attribute for MAP
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|Authors||Peter Deacon , Sheng Jiang , Yu Fu|
|Last updated||2012-07-14 (Latest revision 2012-01-11)|
|Replaced by||draft-ietf-softwire-map-radius, draft-ietf-softwire-map-radius, draft-ietf-softwire-map-radius, draft-ietf-softwire-map-radius, draft-ietf-softwire-map-radius, RFC 8658|
|Stream||Stream state||(No stream defined)|
|RFC Editor Note||(None)|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Mapping of Address and Port (MAP) is a stateless mechanism for running IPv4 over IPv6-only infrastructure. It provides both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 co- existing period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) MAP options has been defined to configure MAP Customer Edge (CE). However, in many networks, the configuration information may be stored in Authentication Authorization and Accounting (AAA) servers while user configuration is mainly from Broadband Network Gateway (BNG) through DHCPv6 protocol. This document defines a Remote Authentication Dial In User Service (RADIUS) attribute that carries MAP configuration information from AAA server to BNG. The MAP RADIUS attribute are designed following the simplify principle. It provides just enough information to form the correspondent DHCPv6 MAP option.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)