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

Ted Lemon <mellon@fugue.com> Thu, 08 April 2004 02:30 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 WAA08737 for <dhcwg-archive@odin.ietf.org>; Wed, 7 Apr 2004 22:30:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBPIo-0002RT-RX for dhcwg-archive@odin.ietf.org; Wed, 07 Apr 2004 22:30:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i382U2jv009388 for dhcwg-archive@odin.ietf.org; Wed, 7 Apr 2004 22:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBPIo-0002RL-Ip for dhcwg-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 22:30:02 -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 WAA08623 for <dhcwg-web-archive@ietf.org>; Wed, 7 Apr 2004 22:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBPIl-0004Ef-00 for dhcwg-web-archive@ietf.org; Wed, 07 Apr 2004 22:29:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBNpe-0006fl-00 for dhcwg-web-archive@ietf.org; Wed, 07 Apr 2004 20:55:52 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBLfP-0000Wf-00 for dhcwg-web-archive@ietf.org; Wed, 07 Apr 2004 18:37:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBLfM-0004cU-D5; Wed, 07 Apr 2004 18:37:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBLfI-0004Xo-OJ for dhcwg@optimus.ietf.org; Wed, 07 Apr 2004 18:37:00 -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 SAA18004 for <dhcwg@ietf.org>; Wed, 7 Apr 2004 18:36:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBLfF-0000VB-00 for dhcwg@ietf.org; Wed, 07 Apr 2004 18:36:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBKGL-0003Sq-00 for dhcwg@ietf.org; Wed, 07 Apr 2004 17:07:11 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BBIGE-00068P-00 for dhcwg@ietf.org; Wed, 07 Apr 2004 14:58:54 -0400
Received: from [10.224.137.82] (m6a8d36d0.tmodns.net [208.54.141.106]) by toccata.fugue.com (Postfix) with ESMTP id 573993A1DB1 for <dhcwg@ietf.org>; Wed, 7 Apr 2004 13:52:28 -0500 (CDT)
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <4.3.2.7.2.20040403072041.029964c8@flask.cisco.com>
References: <4.3.2.7.2.20040403072041.029964c8@flask.cisco.com>
Content-Type: multipart/mixed; boundary="Apple-Mail-4--25803957"
Message-Id: <F27D736F-88BC-11D8-B6D7-000A95D9C74C@fugue.com>
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-proxyserver-opt-00
Date: Wed, 07 Apr 2004 12:56:51 -0500
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.613)
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.0 required=5.0 tests=none autolearn=no version=2.60

I have a bunch of suggested changes to this draft, which fall into 
three categories:

1. A single change to the protocol itself.
2. Editorial changes - I think there was some extra text in this draft 
explaining proxy servers that isn't needed, and generate questions 
during the IESG review, so I'm suggesting that it be deleted.
3. Copyediting.   There were some minor spelling and grammatical errors.

The change to the protocol is that it currently specifies an 
encapsulation of suboptions, like option 82, but allows for the 
appearance of multiple suboptions, which is different than the behavior 
specified for handling options in RFC3396.   This is not a huge 
problem, but it probably requires additional code in DHCP servers and 
clients that isn't necessary, so I'd suggest changing it so that if you 
want to specify multiple proxy servers for the same protocol, you 
should just list more than one IP address/port tuple in the suboption 
for that protocol.

I've enclosed a diff for all the changes.