[dhcwg] FW: New Version Notification for draft-ietf-dhc-addr-registration-05.txt

Sheng Jiang <jiangsheng@huawei.com> Tue, 24 June 2014 06:16 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A131B283A for <dhcwg@ietfa.amsl.com>; Mon, 23 Jun 2014 23:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7dWqQz7VoK6 for <dhcwg@ietfa.amsl.com>; Mon, 23 Jun 2014 23:16:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE6AD1B2839 for <dhcwg@ietf.org>; Mon, 23 Jun 2014 23:16:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJD00035; Tue, 24 Jun 2014 06:16:41 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 07:15:38 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.249]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Tue, 24 Jun 2014 14:15:35 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-dhc-addr-registration-05.txt
Thread-Index: AQHPj3NvBf4tyNHnxkyDrQ6e74mlpJt/yBiA
Date: Tue, 24 Jun 2014 06:15:33 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AEB5A83@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/fcWc4JTVR76rIM61sbrH4QfvKYk
Subject: [dhcwg] FW: New Version Notification for draft-ietf-dhc-addr-registration-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Jun 2014 06:16:45 -0000

Hi, all,

The authors have submitted an update version. We believe all received comments have been addressed. Modifications are summarized as below:

 - Mandated server's response for error code.
 - Added recommendation for only one registration server out of multiple DHCPv6 servers.
 - Added specification that the registration server should record the binding information.
 - Allowed multiple IA_NA.
 - Clarified that the ADDR-REGISTRATION-REQUEST message is dedicated for clients to initiate an address registration request. So, clients MUST NOT include any ORO.

More reviews and comments are appreciated.

Best regards,

Sheng

>-----Original Message-----
>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>Sent: Tuesday, June 24, 2014 2:13 PM
>To: Suresh Krishnan; Rajiv Asati; Gang Chen; Sheng Jiang; Suresh Krishnan;
>Sheng Jiang; Gang Chen; Rajiv Asati
>Subject: New Version Notification for draft-ietf-dhc-addr-registration-05.txt
>
>
>A new version of I-D, draft-ietf-dhc-addr-registration-05.txt
>has been successfully submitted by Sheng Jiang and posted to the
>IETF repository.
>
>Name:		draft-ietf-dhc-addr-registration
>Revision:	05
>Title:		Registering Self-generated IPv6 Addresses in DNS using DHCPv6
>Document date:	2014-06-23
>Group:		dhc
>Pages:		8
>URL:
>http://www.ietf.org/internet-drafts/draft-ietf-dhc-addr-registration-05.txt
>Status:
>https://datatracker.ietf.org/doc/draft-ietf-dhc-addr-registration/
>Htmlized:
>http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-05
>Diff:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-addr-registration-05
>
>Abstract:
>   In networks that are centrally managed, self-generated addresses
>   cause some traceability issues due to their decentralized nature.
>   One of the most important issues in this regard is the inability to
>   register such addresses in DNS.  This document defines a mechanism to
>   register self-generated and statically configured addresses in DNS
>   through a DHCPv6 server.
>
>
>
>
>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