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

"Bernie Volz" <volz@cisco.com> Mon, 12 April 2004 18:00 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 OAA01763 for <dhcwg-archive@odin.ietf.org>; Mon, 12 Apr 2004 14:00:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD5ik-0001PD-GV for dhcwg-archive@odin.ietf.org; Mon, 12 Apr 2004 13:59:46 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3CHxkSu005404 for dhcwg-archive@odin.ietf.org; Mon, 12 Apr 2004 13:59:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD5ik-0001P5-BW for dhcwg-web-archive@optimus.ietf.org; Mon, 12 Apr 2004 13:59:46 -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 NAA01742 for <dhcwg-web-archive@ietf.org>; Mon, 12 Apr 2004 13:59:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BD5ih-0003Lf-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 13:59:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BD5gS-00034t-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 13:57:25 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BD5fB-0002nZ-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 13:56:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD5f8-0001BR-9p; Mon, 12 Apr 2004 13:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD5em-0001AT-Ar for dhcwg@optimus.ietf.org; Mon, 12 Apr 2004 13:55:43 -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 NAA01590 for <dhcwg@ietf.org>; Mon, 12 Apr 2004 13:55:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BD5ej-0002mB-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 13:55:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BD5dM-0002cF-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 13:54:12 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx with esmtp (Exim 4.12) id 1BD5cM-0002LO-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 13:53:10 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2004 11:03:35 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i3CHqXCC010405; Mon, 12 Apr 2004 13:52:34 -0400 (EDT)
Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHN51081; Mon, 12 Apr 2004 13:52:32 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: dhcwg@ietf.org, ksenthil@india.hp.com
Subject: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-proxyserver-opt-00
Date: Mon, 12 Apr 2004 13:52:32 -0400
Organization: Cisco
Message-ID: <002d01c420b6$ee4c96f0$d0412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Importance: Normal
In-Reply-To: <F27D736F-88BC-11D8-B6D7-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Perhaps this has been discussed in the past and discarded, but what
about removing the need for yet-another-list? If the option where
changed not to use sub-options at all but instead carried tuples of:
	2-octets of well-known protocol number
	4-octets of proxy server internet address
	2-octets of proxy server port number
The option length would then be multiples of 8 bytes.

For example:
	Option Header:	TBD-option-code,24-bytes
	Proxy for HTTP:	80,http-proxy-server-1,8080
	Proxy for HTTP:	80,http-proxy-server-2,8080
	Proxy for FTP:	21,ftp-proxy-server-1,21

This avoids the need for future protocols to have an enumeration and the
current "getservicename" calls can be used to find the port numbers.

Otherwise, I recommend moving this draft forward.

- Bernie
-----Original Message-----
From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of
Ted Lemon
Sent: Wednesday, April 07, 2004 1:57 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc WG last call on
draft-ietf-dhc-proxyserver-opt-00


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.



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