IETF Logo Mail Archive

[dhcwg] FW: New Version Notification for draft-yeh-dhc-dhcpv6-authorization-opt-00.txt

Leaf yeh <leaf.y.yeh@huawei.com> Tue, 06 March 2012 08:17 UTC

Return-Path: <leaf.y.yeh@huawei.com>
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 D04CF21E80AE for <dhcwg@ietfa.amsl.com>; Tue, 6 Mar 2012 00:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.651
X-Spam-Level:
X-Spam-Status: No, score=-6.651 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8R83diaZrUME for <dhcwg@ietfa.amsl.com>; Tue, 6 Mar 2012 00:17:21 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1B50621E808C for <dhcwg@ietf.org>; Tue, 6 Mar 2012 00:17:21 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0G00LXEEXRUH@szxga03-in.huawei.com> for dhcwg@ietf.org; Tue, 06 Mar 2012 16:15:27 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0G00LFCEX9Z7@szxga03-in.huawei.com> for dhcwg@ietf.org; Tue, 06 Mar 2012 16:15:27 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHP76289; Tue, 06 Mar 2012 16:15:26 +0800
Received: from SZXEML432-HUB.china.huawei.com (10.72.61.60) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Mar 2012 16:15:17 +0800
Received: from SZXEML510-MBX.china.huawei.com ([169.254.7.199]) by SZXEML432-HUB.china.huawei.com ([10.72.61.60]) with mapi id 14.01.0323.003; Tue, 06 Mar 2012 16:15:19 +0800
Date: Tue, 06 Mar 2012 08:15:20 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
X-Originating-IP: [10.70.39.113]
To: dhc WG <dhcwg@ietf.org>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA218D0B71@SZXEML510-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: en-US, zh-CN
Thread-topic: New Version Notification for draft-yeh-dhc-dhcpv6-authorization-opt-00.txt
Thread-index: AQHM+rJ5wB5yedLmdUWX9jy95pvuKZZc55Hw
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
Subject: [dhcwg] FW: New Version Notification for draft-yeh-dhc-dhcpv6-authorization-opt-00.txt
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: Tue, 06 Mar 2012 08:17:22 -0000

Dear WG,

A new draft named "Authorization Option for DHCPv6 Relay Agents on Broadband Access Server" has been posted yesterday. Questions and comments on it are more than welcome.


Best Regards,
Leaf


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, March 05, 2012 5:26 PM
To: Leaf yeh
Subject: New Version Notification for draft-yeh-dhc-dhcpv6-authorization-opt-00.txt

A new version of I-D, draft-yeh-dhc-dhcpv6-authorization-opt-00.txt has been successfully submitted by Leaf Y. Yeh and posted to the IETF repository.

Filename:	 draft-yeh-dhc-dhcpv6-authorization-opt
Revision:	 00
Title:		 Authorization Option for DHCPv6 Relay Agents on Broadband Access Server
Creation date:	 2012-03-05
WG ID:		 Individual Submission
Number of pages: 9

Abstract:
   The DHCPv6 authorization option provides a communication mechanism
   between relay agent and the server.  This mechanism can help the
   centralized DHCPv6 server to select the right configuration for the
   client based on the authorization information got from the
   centralized RADIUS server which is not located at the same place of
   DHCPv6 server in the case when the NAS works as DHCPv6 relay agent
   and RADIUS client simultaneously.

                                                                                  


The IETF Secretariat

v2.30.2 | Report a Bug | By Email | System Status