[dhcwg] FW: New Version Notification for draft-jiang-dhc-sedhcpv6-01.txt

Sheng Jiang <jiangsheng@huawei.com> Thu, 10 October 2013 01:07 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 95BF321E823A for <dhcwg@ietfa.amsl.com>; Wed, 9 Oct 2013 18:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id TmyIlKefjuCw for <dhcwg@ietfa.amsl.com>; Wed, 9 Oct 2013 18:07:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) by ietfa.amsl.com (Postfix) with ESMTP id 38DEA21E81B2 for <dhcwg@ietf.org>; Wed, 9 Oct 2013 18:07:07 -0700 (PDT)
Received: from (EHLO lhreml203-edg.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYX66288; Thu, 10 Oct 2013 01:07:05 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com ( by lhreml203-edg.huawei.com ( with Microsoft SMTP Server (TLS) id; Thu, 10 Oct 2013 02:06:28 +0100
Received: from NKGEML408-HUB.china.huawei.com ( by lhreml405-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Thu, 10 Oct 2013 02:07:01 +0100
Received: from NKGEML512-MBX.china.huawei.com ([]) by nkgeml408-hub.china.huawei.com ([]) with mapi id 14.03.0146.000; Thu, 10 Oct 2013 09:06:56 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Thread-Topic: New Version Notification for draft-jiang-dhc-sedhcpv6-01.txt
Thread-Index: AQHOw/oxN5loSW/dEkauJe4nbHCE75ntHsBw
Date: Thu, 10 Oct 2013 01:06:55 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AD46C61@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [dhcwg] FW: New Version Notification for draft-jiang-dhc-sedhcpv6-01.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: Thu, 10 Oct 2013 01:07:13 -0000

Hi, DHCers,

We have just submitted an update version, which address most of comments raised by several reviewers. Could you please review this new version?

FYI, this draft is a replacement of draft-ietf-dhc-secure-dhcpv6, which reached IESG and dead because of consideration regarding to CGA. The authors followed the suggestion from IESG making a general public key based mechanism.


Many thanks and best regards,


>-----Original Message-----
>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>Sent: Tuesday, October 08, 2013 3:44 PM
>To: Sheng Jiang; Sean Shen
>Subject: New Version Notification for draft-jiang-dhc-sedhcpv6-01.txt
>A new version of I-D, draft-jiang-dhc-sedhcpv6-01.txt
>has been successfully submitted by Sheng Jiang and posted to the
>IETF repository.
>Filename:	 draft-jiang-dhc-sedhcpv6
>Revision:	 01
>Title:		 Secure DHCPv6 with Public Key
>Creation date:	 2013-10-08
>Group:		 Individual Submission
>Number of pages: 16
>Status:          http://datatracker.ietf.org/doc/draft-jiang-dhc-sedhcpv6
>Htmlized:        http://tools.ietf.org/html/draft-jiang-dhc-sedhcpv6-01
>   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables
>   DHCPv6 servers to pass configuration parameters.  It offers
>   configuration flexibility.  If not secured, DHCPv6 is vulnerable to
>   various attacks, particularly spoofing attacks.  This document
>   analyzes the security issues of DHCPv6 and specifies a Secure DHCPv6
>   mechanism.  This mechanism is based on public/private key pairs.  The
>   authority of the sender may depend on either pre-configuration
>   mechanism or Public Key Infrastructure.
>Please note that it may take a couple of minutes from the time of submission
>until the htmlized version and diff are available at tools.ietf.org.
>The IETF Secretariat