[Softwires] RFC 6930 on RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
rfc-editor@rfc-editor.org Wed, 01 May 2013 05:31 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF83B21F84A9; Tue, 30 Apr 2013 22:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.225
X-Spam-Level:
X-Spam-Status: No, score=-102.225 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3y8rsYfxjlyk; Tue, 30 Apr 2013 22:31:45 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7AF21F84CA; Tue, 30 Apr 2013 22:31:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2715CB1E004; Tue, 30 Apr 2013 22:31:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130501053112.2715CB1E004@rfc-editor.org>
Date: Tue, 30 Apr 2013 22:31:12 -0700
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 6930 on RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 05:31:46 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6930 Title: RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) Author: D. Guo, S. Jiang, Ed., R. Despres, R. Maglione Status: Standards Track Stream: IETF Date: April 2013 Mailbox: guoseu@huawei.com, jiangsheng@huawei.com, despres.remi@laposte.net, robmgl@cisco.com Pages: 12 Characters: 23573 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-softwire-6rd-radius-attrib-11.txt URL: http://www.rfc-editor.org/rfc/rfc6930.txt 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. This document is a product of the Softwires Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC