RFC 6519: RADIUS Extensions for Dual-Stack Lite
In plain English — editorial summary, not part of the RFC
Dual-Stack Lite is a solution to offer both IPv4 and IPv6 connectivity to customers that are addressed only with an IPv6 prefix. Dual-Stack Lite requires pre-configuration of the Dual-Stack Lite Address Family Transition Router (AFTR) tunnel information on the Basic Bridging BroadBand (B4) element. In many networks, the customer profile information may be stored in Authentication, Authorization, and Accounting (AAA) servers, while client configurations are mainly provided through the Dynamic Host Configuration Protocol (DHCP). This document specifies a new Remote Authentication Dial-In User Service (RADIUS) attribute to carry the Dual-Stack Lite AFTR tunnel name; the RADIUS attribute is defined based on the equivalent DHCPv6 OPTION_AFTR_NAME option. This RADIUS attribute is meant to be used between the RADIUS server and the Network Access Server (NAS); it is not intended to be used directly between the B4 element and the RADIUS server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6519
- Published
- February 2012
- Authors
- R. Maglione; A. Durand
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 6547RFC 3627 to Historic StatusCurrent
February 2012
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6221Lightweight DHCPv6 Relay AgentCurrent
May 2011
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
- RFC 6139Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) ScenariosCurrent
February 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?