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

Ralph Droms <rdroms@cisco.com> Tue, 20 April 2004 17:17 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 NAA05378 for <dhcwg-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:17:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyVD-0008GJ-7p for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 12:53:43 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KGrhJC031755 for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 12:53:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyGN-0000zd-Gc for dhcwg-web-archive@optimus.ietf.org; Tue, 20 Apr 2004 12:38:23 -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 MAA01895 for <dhcwg-web-archive@ietf.org>; Tue, 20 Apr 2004 12:38:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFyGL-0000xt-Sm for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:38:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFyFT-0000fh-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:37:27 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFyEh-0000O9-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:36:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFxhE-0008VE-DO; Tue, 20 Apr 2004 12:02:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFx6Y-0001qZ-KH for dhcwg@optimus.ietf.org; Tue, 20 Apr 2004 11:24: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 LAA25094 for <dhcwg@ietf.org>; Tue, 20 Apr 2004 11:24:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFx6X-00018o-N5 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:24:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFx5U-0000po-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:23:05 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1BFx4P-0000JQ-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:21:58 -0400
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 20 Apr 2004 08:22:31 -0700
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 i3KFLPhE018215; Tue, 20 Apr 2004 08:21:25 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-104.cisco.com [10.86.240.104]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHS56325; Tue, 20 Apr 2004 11:21:23 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040420112046.02f506d0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 20 Apr 2004 11:21:21 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-proxyserver-opt-00
Cc: ksenthil@india.hp.com
In-Reply-To: <002d01c420b6$ee4c96f0$d0412ca1@amer.cisco.com>
References: <F27D736F-88BC-11D8-B6D7-000A95D9C74C@fugue.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.3 required=5.0 tests=AWL,OPT_HEADER autolearn=no version=2.60

Bernie made a suggestion about the syntax of the option.  Any comment from 
the WG?

- Ralph

At 01:52 PM 4/12/2004 -0400, Bernie Volz wrote:
>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


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