[dhcwg] RFC 7037 on RADIUS Option for the DHCPv6 Relay Agent

rfc-editor@rfc-editor.org Thu, 17 October 2013 21:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210A611E8285; Thu, 17 Oct 2013 14:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.182
X-Spam-Level:
X-Spam-Status: No, score=-102.182 tagged_above=-999 required=5 tests=[AWL=-0.181, 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 HZJ04v4Ebq0S; Thu, 17 Oct 2013 14:57:14 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 2B96D11E82A2; Thu, 17 Oct 2013 14:57:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4F5C5B1E078; Thu, 17 Oct 2013 14:48:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131017214856.4F5C5B1E078@rfc-editor.org>
Date: Thu, 17 Oct 2013 14:48:56 -0700
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] RFC 7037 on RADIUS Option for the DHCPv6 Relay Agent
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 21:57:15 -0000

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

        
        RFC 7037

        Title:      RADIUS Option for the DHCPv6 
                    Relay Agent 
        Author:     L. Yeh, M. Boucadair
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2013
        Mailbox:    leaf.yeh.sdo@gmail.com, 
                    mohamed.boucadair@orange.com
        Pages:      10
        Characters: 23356
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcpv6-radius-opt-14.txt

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

The DHCPv6 RADIUS option provides a mechanism to exchange
authorization and identification information between the DHCPv6 relay
agent and DHCPv6 server.  This architecture assumes that the Network
Access Server (NAS) acts as both a DHCPv6 relay agent and RADIUS
client.  When receiving messages from the DHCPv6 clients, the NAS
consults the RADIUS server and adds the RADIUS response when
forwarding the DHCPv6 client's messages to the DHCPv6 server.  The
DHCPv6 server then uses that additional information to generate an
appropriate response to the DHCPv6 client's requests.

This document is a product of the Dynamic Host Configuration 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/search/rfc_search.php
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