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

"Bernie Volz" <volz@cisco.com> Wed, 11 August 2004 22:21 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26241; Wed, 11 Aug 2004 18:21:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv18a-0007Bf-3N; Wed, 11 Aug 2004 18:00:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv0x2-0001K2-G1 for dhcwg@megatron.ietf.org; Wed, 11 Aug 2004 17:48:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21630 for <dhcwg@ietf.org>; Wed, 11 Aug 2004 17:48:01 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv11o-0004JI-TE for dhcwg@ietf.org; Wed, 11 Aug 2004 17:53:04 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 11 Aug 2004 14:50:26 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7BLlNVD010155; Wed, 11 Aug 2004 14:47:23 -0700 (PDT)
Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKU01354; Wed, 11 Aug 2004 17:47:21 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-proxyserver-opt-00 - NO GO!
Date: Wed, 11 Aug 2004 17:47:21 -0400
Organization: Cisco
Message-ID: <002001c47fec$c84326f0$d0412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <4.3.2.7.2.20040811150633.02004b08@flask.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: neumann@wu-wien.ac.at, ksenthil@india.hp.com, srihary@cisco.com, exand@wu-wien.ac.at
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

I do *NOT* agree with the last call on this document!

The current document is
http://www.ietf.org/internet-drafts/draft-ietf-dhc-proxyserver-opt-01.txt
and I assume that is really the one being last called and the one I'll
comment on (as there are significant differences between 00 and 01).

First, I'd like to understand how they'll encode values such as 1080 into a
single byte:

   The Proxy Server Configuration entry consists of a sequence of 
   Protocol Type (p), Encoding (e), IP address and port. 
   	  
   	+--+--+--+--+--+--+--+--+
	|p |e |IP address |port |
	+--+--+--+--+--+--+--+--+

   The Protocol(p) and encodig (e) are on octet each; each IP address is
---------------------------------------^^ (I assume this is ONE octet each?)
   four octets, and each port number is a two-octet integer encoded in
   network byte order.

And then:

   The protocol type(p) specifies the type of Protocol and MUST be 
   one of the following assigned numbers.

       +-------------------------------+
       | protocol     |       Number   |
       +-------------------------------+
       |   HTTP       |         80     |
       +-------------------------------+
       |   FTP        |         21     |
       +-------------------------------+
       |   NNTP       |         119    |
       +-------------------------------+
       |   Gopher     |         70     |
       +-------------------------------+
       |   SSL        |         TBD    |
       +-------------------------------+
       |   SOCKS      |         1080   |
  
1080 requires two bytes to encode.

Later, the document goes on about:

   The format of the Proxy Server Configuration using Metadata type is:


            p       Len        RDF Metadata for the Proxy    
   	 +-------+------+----------------------------------+
   	 |  RDF  |  N   |             RDF                  |
   	 +-------+------+----------------------------------+


What is this and where does this go? Is this a new option? Is this encoded
in the existing option in some manner which I can't understand?


And, the option size would seem to exceed the 255 byte limit: "... giving a
total of 418 characters including the overhead", yet nothing is ever
mentioned about RFC 3396 (encoding long options).

So, I think this draft needs much further revision before I feel it would be
acceptable.

Best regards,

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of Ralph Droms
> Sent: Wednesday, August 11, 2004 3:15 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-proxyserver-opt-00
> 
> 
> This message announces a second WG last call on "DHCP Option 
> for Proxy Server Configuration" 
> <draft-ietf-dhc-proxyserver-opt-00>.  There was insufficient 
> (that is, none) response to the first WG last call.  This 
> document can not be submitted to the IESG without positive 
> response during the WG last call.  This last call will 
> conclude at 1700 EDT, 2004-08-27.
> 
> Please respond to this WG last call.  If you support 
> acceptance of the document without change, respond with a 
> simple acknowledgment, so that support for the document can 
> be assessed.
> 
> "DHCP Option for Proxy Server Configuration" defines a 
> Dynamic Host Configuration Protocol (DHCP) option that can be 
> used to configure the TCP/IP host's Proxy Server 
> configuration for standard protocols like HTTP, FTP, NNTP, 
> SOCKS, Gopher, SLL and etc. Proxy servers provide controlled 
> and efficient access to the Internet through the use of 
> access control mechanisms for different types of user 
> requests and caching frequently accessed information (Web 
> pages and other files that might have been downloaded using 
> FTP and other protocols).  This draft is available as 
http://www.ietf.org/internet-drafts/draft-ietf-dhc-proxyserver-opt-00.txt

- Ralph Droms


_______________________________________________
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


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