Re: [dhcwg] WGLC: draft-ietf-dhc-host-gen-id-02

Sheng Jiang <jiangsheng@huawei.com> Wed, 15 August 2012 06:14 UTC

Return-Path: <jiangsheng@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 4168711E80A6 for <dhcwg@ietfa.amsl.com>; Tue, 14 Aug 2012 23:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.348
X-Spam-Level:
X-Spam-Status: No, score=-6.348 tagged_above=-999 required=5 tests=[AWL=0.251, 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 ls+N-Lvw6dqs for <dhcwg@ietfa.amsl.com>; Tue, 14 Aug 2012 23:14:08 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB4011E80A4 for <dhcwg@ietf.org>; Tue, 14 Aug 2012 23:14:08 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath) with ESMTP id AJK76428; Tue, 14 Aug 2012 22:14:08 -0800 (PST)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 14 Aug 2012 23:11:18 -0700
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 14 Aug 2012 23:11:22 -0700
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.140]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 15 Aug 2012 14:10:56 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: WGLC: draft-ietf-dhc-host-gen-id-02
Thread-Index: AQHNePgJ6EjzoGF6j0KwHUjTOoQDGZdaQLLQgAAgdoA=
Date: Wed, 15 Aug 2012 06:10:56 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239F061A5@szxeml545-mbx.china.huawei.com>
References: <2DCA645F-CDDF-4311-8417-3A9771AD3F71@nominum.com> <EF6A204047BD994A860EE26D5F23BF582B8CDC9B@SZXEML512-MBX.china.huawei.com>
In-Reply-To: <EF6A204047BD994A860EE26D5F23BF582B8CDC9B@SZXEML512-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.99.31]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-host-gen-id-02
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: Wed, 15 Aug 2012 06:14:09 -0000

Hi, Yu,

Thanks your support and comments. Some replies in lines.

Regards,

Sheng

>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
>Of Fuyu (Eleven)
>Sent: Wednesday, August 15, 2012 12:55 PM
>To: Ted Lemon
>Cc: dhc WG
>Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-host-gen-id-02
>
>I am in favor of advancing this work.
>
>BTW, some comments below
>Section 4 part 1: This part describes that referring the IA_PD, a new IA_PA
>option is defined to insert into the DHCP message.
>And Section 5 the last sentence also describes that " However, the two
>options are different on the semantics and usage models."
>I think it need some more words to describe the difference between these
>two options in which scenario use IA_PD and in which scenario
>use the IA_PA in this part.

Prefix delegation and Prefix assignment are quite different: IA_PD is actually used among routers. This has been described in third paragraph of introduction session.

>Figure 1: I suggest to add message 4 (Request message) after the message 3
>to confirm the usage of the new address as the whole
>configuration process.

We have stated this is out of scope and added a reference to I-D.ietf-dhc-addr-registration, which defines the address confirmation/registration process.

>And I also think it is better to add the option name
>after the DHCP message in the figure 1.

Added

>Some typo: Section 1 the last sentence: supports-support
>         Section 1 paragraph 4 the last sentence: separats->separates

Echo.

Sheng

>Cheers
>Yu
>
>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
>Of Ted Lemon
>Sent: Monday, August 13, 2012 10:05 AM
>To: dhc WG
>Subject: [dhcwg] WGLC: draft-ietf-dhc-host-gen-id-02
>
>The authors have requested a working group last call for this draft.   The
>draft provides a mechanism whereby the DHCP server can indicate to the
>DHCP client which prefix it should use for autoconfiguration, for instance for
>CGA address generation.   This draft has been hanging around for a while,
>and could definitely use more eyes on it.   Please take the time to review it;
>if you think it's a good idea, please indicate your support for advancing the
>draft.   If you think it's a bad idea, please indicate that you do not support
>advancing it.   If you have comments, they would be very much appreciated.
>
>We will determine consensus on August 27.
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg