[radext] RFC 6911 on RADIUS Attributes for IPv6 Access Networks

rfc-editor@rfc-editor.org Mon, 29 April 2013 18:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A51A221F9AC5; Mon, 29 Apr 2013 11:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[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 a+dgFHRMiyHR; Mon, 29 Apr 2013 11:50:38 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B2B0F21F9B06; Mon, 29 Apr 2013 11:50:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EBA71B1E008; Mon, 29 Apr 2013 11:49:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130429184952.EBA71B1E008@rfc-editor.org>
Date: Mon, 29 Apr 2013 11:49:52 -0700
Cc: radext@ietf.org, rfc-editor@rfc-editor.org
Subject: [radext] RFC 6911 on RADIUS Attributes for IPv6 Access Networks
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 18:50:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6911

        Title:      RADIUS Attributes for IPv6 Access 
                    Networks 
        Author:     W. Dec, Ed.,
                    B. Sarikaya,
                    G. Zorn, Ed.,
                    D. Miles,
                    B. Lourdelet
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    wdec@cisco.com, 
                    sarikaya@ieee.org, 
                    glenzorn@gmail.com,
                    davidmiles@google.com, 
                    blourdel@juniper.net
        Pages:      15
        Characters: 28123
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-radext-ipv6-access-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6911.txt

This document specifies additional IPv6 RADIUS Attributes useful in
residential broadband network deployments.  The Attributes, which are
used for authorization and accounting, enable assignment of a host
IPv6 address and an IPv6 DNS server address via DHCPv6, assignment of
an IPv6 route announced via router advertisement, assignment of a
named IPv6 delegated prefix pool, and assignment of a named IPv6 pool
for host DHCPv6 addressing.

This document is a product of the RADIUS EXTensions 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