Re: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-00

Ralph Droms <rdroms@cisco.com> Fri, 09 April 2004 00:04 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 UAA13182 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Apr 2004 20:04:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjVC-0000qi-CP for dhcwg-archive@odin.ietf.org; Thu, 08 Apr 2004 20:04:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3904A4b003260 for dhcwg-archive@odin.ietf.org; Thu, 8 Apr 2004 20:04:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjVC-0000qV-8v for dhcwg-web-archive@optimus.ietf.org; Thu, 08 Apr 2004 20:04:10 -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 UAA12969 for <dhcwg-web-archive@ietf.org>; Thu, 8 Apr 2004 20:04:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBjV9-0000Z9-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 20:04:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBie3-0001tt-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 19:09:17 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBhmb-0003hz-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 18:14:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBhmc-0003Oc-5x; Thu, 08 Apr 2004 18:14:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBhm1-0003CK-FL for dhcwg@optimus.ietf.org; Thu, 08 Apr 2004 18:13:25 -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 SAA01092 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 18:13:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBhlx-0003bd-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 18:13:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBfiW-0002bd-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 16:01:44 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1BBZT8-0006gX-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 09:21:22 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i38DKmew013131 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 06:20:48 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.128]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHL49118; Thu, 8 Apr 2004 09:20:47 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040408090911.02af0ed8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Apr 2004 09:20:45 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-00
In-Reply-To: <4.3.2.7.2.20040403073841.029964c8@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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=1.2 required=5.0 tests=AWL,OPT_HEADER autolearn=no version=2.60

I see that this draft includes a notice regarding IPR.  The Samsung IPR
statement appears to apply across all IETF submissions.  Can the authors
clarify if there are any IPR claims that apply specifically to this document?

The format of the option - specifically, option length == 0 - is consistent
with other DHCP options.  Will length 0 cause problems in practice with
deployed DHCP servers?

The document should be republished to include RFC 3667 boilerplate,
including the RFC 3667 IPR notification statement.

I have one editorial comment: the document should indicate that the use of
Rapid Commit is optional on the part of the client, under local (client)
admin control.  In section 3, I suggest changing the first sentence:

      A client that supports the Rapid Commit option SHOULD include it in
      DHCPDISCOVER messages that it sends.

to:

      If a client that supports the Rapid Commit option intends to use
      the rapid commit capability, it includes a Rapid Commit option in
      DHCPDISCOVER messages that it sends.

In section 3.1, list item 1, I suggest changing the first sentence:

         1. The client broadcasts a DHCPDISCOVER message on its local
            physical subnet and  SHOULD include the Rapid Commit option if
            it supports this option.

to:

         1. The client broadcasts a DHCPDISCOVER message on its local
            physical.  If the client supports the Rapid Commit option
            and intends to use the rapid commit capability, it includes
            a Rapid Commit option in the DHCPDISCOVER message.


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg