RE: [dhcwg] Internet Drafts to be reviewed by the dhc WG

"Bernie Volz" <volz@cisco.com> Wed, 31 March 2004 23:26 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 SAA20707 for <dhcwg-archive@odin.ietf.org>; Wed, 31 Mar 2004 18:26:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8p5a-00074L-LA for dhcwg-archive@odin.ietf.org; Wed, 31 Mar 2004 18:25:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VNPg2L027173 for dhcwg-archive@odin.ietf.org; Wed, 31 Mar 2004 18:25:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8p5a-00074C-EM for dhcwg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 18:25:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20704 for <dhcwg-web-archive@ietf.org>; Wed, 31 Mar 2004 18:25:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8p5X-0002ZD-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 18:25:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8p4c-0002Vd-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 18:24:43 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B8p4Q-0002TZ-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 18:24:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8p3w-0006sK-Mn; Wed, 31 Mar 2004 18:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8p3a-0006rV-Qt for dhcwg@optimus.ietf.org; Wed, 31 Mar 2004 18:23:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20631 for <dhcwg@ietf.org>; Wed, 31 Mar 2004 18:23:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8p3X-0002SX-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 18:23:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8p2f-0002R4-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 18:22:41 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx with esmtp (Exim 4.12) id 1B8p23-0002Ms-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 18:22:03 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 31 Mar 2004 15:21:33 -0800
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 i2VNLUA6022118; Wed, 31 Mar 2004 18:21:30 -0500 (EST)
Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHG68370; Wed, 31 Mar 2004 18:21:29 -0500 (EST)
From: Bernie Volz <volz@cisco.com>
To: 'Tim Chown' <tjc@ecs.soton.ac.uk>, 'Ralph Droms' <rdroms@cisco.com>
Cc: dhcwg@ietf.org, margaret@thingmagic.com, narten@us.ibm.com, 'Melinda Shore' <mshore@cisco.com>
Subject: RE: [dhcwg] Internet Drafts to be reviewed by the dhc WG
Date: Wed, 31 Mar 2004 18:21:28 -0500
Organization: Cisco
Message-ID: <000201c41776$e52df2b0$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
In-Reply-To: <20040331205044.GL20993@login.ecs.soton.ac.uk>
Importance: Normal
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

It says "Entities using the Midcom Protocol need to know the presence of
Midcom middleboxes, such as firewalls and network address translators,
in order to enable communication across theses devices." in the abstract
of the draft. So, it looks like we're in for NAT with IPv6 ...


I think the WG should take up the issue of how best to handle options
that want to specify either or both domain names and IPv6 addresses. It
seems to me silly to have TWO options for every time this needs to occur
(as is the case in this midcom draft). And, this mechanism provides no
way to specify the preference between the two - order can be used within
each option to specify which to try first, but it can't be used across
the options. So, it is then left up to the draft (or implementor) to
pick which to use first.

The obvious answer would be to use a sub-option technique or a flag byte
before either an address or domain name. Something like:

	DHCP option (either 8-bits or 16-bits)
	Option length (either 8-bits or 16-bits)
	Encoding type (8-bits? - 0 for domain name, 1 for IP addresses)
	Encoding length (8 bits?)
	Data (either domain name or address)
	Encoding type (8-bits? - 0 for domain name, 1 for IP addresses)
	Encoding length (8 bits?)
	Data (either domain name or address)
	...

In the cases where only one type of encoding is used, this would cost 2
extra bytes. In the cases where multiple encodings are used, this would
either be the same length as the two-option method or potentially save
two bytes (depending on the encoding type/length field sizes).

Note: It would also be possible to specify IPv4 AND IPv6 addresses (1
for IPv4 address, 2 for IPv6 addresses for the encoding type, for
example).

- Bernie

-----Original Message-----
From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of
Tim Chown
Sent: Wednesday, March 31, 2004 3:51 PM
To: Ralph Droms
Cc: dhcwg@ietf.org; margaret@thingmagic.com; narten@us.ibm.com; Melinda
Shore
Subject: Re: [dhcwg] Internet Drafts to be reviewed by the dhc WG


On Wed, Mar 31, 2004 at 01:24:05PM -0500, Ralph Droms wrote:
> There are a couple of Internet Drafts under review by the midcom WG 
> that specify new DHCP options:
> 
> draft-tran-midcom-dhcpv6-option-00.txt

So this one assumes that IPv6 NATs exist and midcom will handle IPv6 NAT
traversal?  Or s midcom for IPv6 a means to configure the middlebox for
other ALG or firewall purposes?

Luckily I don't think Keith Moore is on the dhc WG list :)

Tim

_______________________________________________
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