Browse Prior Art Database

RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) (RFC6930) Disclosure Number: IPCOM000227013D
Original Publication Date: 2013-Apr-01
Included in the Prior Art Database: 2013-May-02
Document File: 24 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Guo: AUTHOR [+5]


Recently, providers have started to deploy IPv6 and to consider transition to IPv6. The IPv6 Rapid Deployment (6rd) [RFC5969] provides both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 coexistence period. 6rd is used to provide IPv6 connectivity service through legacy IPv4-only infrastructure. 6rd uses the Dynamic Host Configuration Protocol (DHCP) [RFC2131], and the 6rd Customer Edge (CE) uses the DHCP 6rd option [RFC5969] to discover a 6rd Border Relay and to configure an IPv6 prefix and address.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Internet Engineering Task Force (IETF)                            D. Guo Request for Comments: 6930                                 S. Jiang, Ed. Category: Standards Track                   Huawei Technologies Co., Ltd ISSN: 2070-1721                                               R. Despres                                                                RD-IPtech                                                              R. Maglione                                                            Cisco Systems                                                               April 2013

                RADIUS Attribute for IPv6 Rapid Deployment                      on IPv4 Infrastructures (6rd)


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Guo, et al.                  Standards Track                    [Page 1]
 RFC 6930                     RADIUS for 6rd                   April 2013

 Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the...