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

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 15 August 2012 01:36 UTC

Return-Path: <leo.liubing@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 41FF221E80E2 for <dhcwg@ietfa.amsl.com>; Tue, 14 Aug 2012 18:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.333
X-Spam-Level:
X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.266, 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 i1XtZOtgC+Pp for <dhcwg@ietfa.amsl.com>; Tue, 14 Aug 2012 18:35:58 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB6B21E80E1 for <dhcwg@ietf.org>; Tue, 14 Aug 2012 18:35:58 -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 AJK63162; Tue, 14 Aug 2012 17:35:57 -0800 (PST)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 14 Aug 2012 18:32:26 -0700
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 14 Aug 2012 18:32:30 -0700
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml405-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 15 Aug 2012 09:32:20 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Thread-Topic: WGLC: draft-ietf-dhc-host-gen-id-02
Thread-Index: AQHNePgJ6EjzoGF6j0KwHUjTOoQDGZdY5bRAgAAkl+CAAQ7iQA==
Date: Wed, 15 Aug 2012 01:32:19 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F452932ED18@szxeml509-mbs>
References: <2DCA645F-CDDF-4311-8417-3A9771AD3F71@nominum.com> <8AE0F17B87264D4CAC7DE0AA6C406F452932EAEC@szxeml509-mbs> <5D36713D8A4E7348A7E10DF7437A4B9239F059F5@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B9239F059F5@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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 01:36:00 -0000


-----Original Message-----
From: Sheng Jiang 
Sent: Tuesday, August 14, 2012 5:26 PM
To: Liubing (Leo); Ted Lemon; dhc WG
Subject: RE: WGLC: draft-ietf-dhc-host-gen-id-02

Hi, Bing,

Thanks for your support and comments. See my replies in lines.

Regards,

Sheng

>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
>Of Liubing (Leo)
>Sent: Tuesday, August 14, 2012 3:59 PM
>To: Ted Lemon; dhc WG
>Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-host-gen-id-02
>
>Support advancing it. Few minor comments:
>
>Section 3, first paragraph. It is not proper to say routers can "specify" the
>hosts should use DHCPv6 and/or stateless address configuration. In fact the
>RFC4862 doesn't clearly defined the hosts should interpret the M/O flags as
>prescriptive, but just advisory. In other word, it is not determined by the
>routers, but the hosts themselves.

This sentence is almost the same with original sentence in RFC4862, including the word "specify". The object of "specify" is a "should", rather than "MUST". So, router is not determined the address configuration model. Router gives advices. This description is compatible with your understanding, I believe. 

[Bing] That is what I mean. Thanks.

>In last paragraph of section 4, what is the "address registration procedure"?
>Do you mean the procedure defined in draft-ietf-dhc-addr-registration ? If it is,
>it's better to add a reference.

Echo. Thanks.

Sheng

>
>-----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