RFC 6930: RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
In plain English — editorial summary, not part of the RFC
The IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) provides both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 coexistence period. The Dynamic Host Configuration Protocol (DHCP) 6rd option has been defined to configure the 6rd Customer Edge (CE). However, in many networks, the configuration information may be stored in the Authentication Authorization and Accounting (AAA) servers, while user configuration is mainly acquired from a Broadband Network Gateway (BNG) through the DHCP protocol. This document defines a Remote Authentication Dial-In User Service (RADIUS) attribute that carries 6rd configuration information from the AAA server to BNGs.
Document record
- Document ID
- RFC6930
- Published
- April 2013
- Authors
- D. Guo; S. Jiang; R. Despres; R. Maglione
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6926DHCPv4 Bulk LeasequeryUpdated
April 2013
- RFC 6934Applicability of the Access Node Control Mechanism to Broadband Networks Based on Passive Optical Networks (PONs)Current
June 2013
- RFC 6925The DHCPv4 Relay Agent Identifier Sub-OptionCurrent
April 2013
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 6936Applicability Statement for the Use of IPv6 UDP Datagrams with Zero ChecksumsCurrent
April 2013
- RFC 6939Client Link-Layer Address Option in DHCPv6Current
May 2013
- RFC 6944Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation StatusObsoleted
April 2013
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
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?