RE: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-02.txt

"Kostur, Andre" <akostur@incognito.com> Wed, 21 April 2004 06:26 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22547 for <dhcwg-archive@odin.ietf.org>; Wed, 21 Apr 2004 02:26:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGB8k-00074U-9n for dhcwg-archive@odin.ietf.org; Wed, 21 Apr 2004 02:23:23 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L6NMTK027144 for dhcwg-archive@odin.ietf.org; Wed, 21 Apr 2004 02:23:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGAzl-0001k0-I0 for dhcwg-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 02:14:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11361 for <dhcwg-web-archive@ietf.org>; Wed, 21 Apr 2004 02:14:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGAzi-0003iX-0e for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 02:14:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGAyc-0003Zx-00 for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 02:12:55 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BGAxu-0003T1-00 for dhcwg-web-archive@ietf.org; Wed, 21 Apr 2004 02:12:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGAsv-00056h-N4; Wed, 21 Apr 2004 02:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGAoZ-0000za-I8 for dhcwg@optimus.ietf.org; Wed, 21 Apr 2004 02:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00626 for <dhcwg@ietf.org>; Wed, 21 Apr 2004 02:02:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGAoW-0002X4-31 for dhcwg@ietf.org; Wed, 21 Apr 2004 02:02:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGAnb-0002Sc-00 for dhcwg@ietf.org; Wed, 21 Apr 2004 02:01:32 -0400
Received: from chimera.incognito.com ([206.172.52.66]) by ietf-mx with esmtp (Exim 4.12) id 1BGAmq-0002IF-00 for dhcwg@ietf.org; Wed, 21 Apr 2004 02:00:44 -0400
Received: from homerdmz.incognito.com ([206.172.52.116] helo=HOMER.incognito.com.) by chimera.incognito.com with esmtp (Exim 4.30) id 1BGAmL-0005g9-30; Tue, 20 Apr 2004 23:00:13 -0700
Received: by homer.incognito.com with Internet Mail Service (5.5.2653.19) id <HP3FQ02W>; Tue, 20 Apr 2004 22:59:42 -0700
Message-ID: <B34580038487494C8B7F36DA06160B870125C0C8@homer.incognito.com>
From: "Kostur, Andre" <akostur@incognito.com>
To: "'S. Daniel Park'" <soohong.park@samsung.com>, "Kostur, Andre" <akostur@incognito.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-02.txt
Date: Tue, 20 Apr 2004 22:59:35 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C42765.D283CE10"
X-Spam-Score: 2.0 (++)
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60

> From: S. Daniel Park [mailto:soohong.park@samsung.com]
> Sent: Tuesday, April 20, 2004 10:13 PM
> To: 'Kostur, Andre'; dhcwg@ietf.org
> Subject: RE: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-02.txt
>  
> Thanks Kostur and see my inline comments.
> 
> >The second step talks about using the client identifier or chaddr 
> >plus assigned network address as the identifier for the lease.  
> >I believe this puts it in conflict with RFC 2131 (which talks about
> using
> >a subnet address, not necessarily the address of the lease), and 
> >RFC 3046 which adds in the Remote ID.  I believe that this 
> draft should
> 
> >probably reference RFC 3046 on this topic.
> 
> I am not sure why it occurs confliction with RFC2131.

Maybe "conflict" is too strong of a word...

I guess to me specifying the lease address implies that a unique identifier
(ClientID/CHADDR + RemoteID) may have multiple leases on the same subnet.
By specifying a subnet address instead, this implies that a unique
identifier may have only one lease on a subnet.  If a client wished to have
multiple leases on the same subnet, then it would need to mutate it's client
ID, and thus effectively becoming a distinct client (from the DHCP server's
point of view).

> >Section 4: 
> >This states that a client SHOULD include this option in a discover if
> it's 
> >prepared to perform the DISCOVER-ACK exchange.  Shouldn't that be 
> >a MUST since there is that if clause at the end?
> 
> I thought MUST is too hard, but I have no hard stance to replace it
> if we agree that.

I think that SHOULD is too loose in this case.  The statement is modified by
saying "if the device is prepared to perform the DISCOVER-ACK exchange".
With a SHOULD this would imply that the device may be prepared to perform
the DISCOVER-ACK exchange, but isn't required to supply the Rapid Commit
option.  Which would lead to the question of how else would the device
inform the server that it is prepared to do Rapid Commit?