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

Martin Stiemerling <stiemerling@netlab.nec.de> Tue, 06 April 2004 10: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 GAA00308 for <dhcwg-archive@odin.ietf.org>; Tue, 6 Apr 2004 06:17:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAne6-0002Yj-EQ for dhcwg-archive@odin.ietf.org; Tue, 06 Apr 2004 06:17:30 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i36AHU9m009838 for dhcwg-archive@odin.ietf.org; Tue, 6 Apr 2004 06:17:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAne5-0002YY-S7 for dhcwg-web-archive@optimus.ietf.org; Tue, 06 Apr 2004 06:17:30 -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 GAA00213 for <dhcwg-web-archive@ietf.org>; Tue, 6 Apr 2004 06:17:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAne2-00032y-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 06:17:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAnQ0-00009E-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 06:02:57 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BAmpu-0004xQ-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 05:25:38 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BAmpw-0007MR-DT for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 05:25:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAmpL-0005vb-Jd; Tue, 06 Apr 2004 05:25:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAmoJ-0005IS-FV for dhcwg@optimus.ietf.org; Tue, 06 Apr 2004 05:23:59 -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 FAA26016 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 05:23:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAmoF-0004YC-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 05:23:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAmho-0003Dv-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 05:17:18 -0400
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BAmQg-0000JV-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 04:59:34 -0400
Received: from tokyo.ccrle.nec.de (localhost [127.0.0.1]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i368x39l090001 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 10:59:05 +0200 (CEST)
Received: (from defang@localhost) by tokyo.ccrle.nec.de (8.12.10/8.12.8/Submit) id i368t0id089518 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 10:55:00 +0200 (CEST)
X-Authentication-Warning: tokyo.ccrle.nec.de: defang set sender to <stiemerling@netlab.nec.de> using -f
Received: from venus.office (venus.office [10.1.1.11]) by pluto.office (8.12.9/8.12.9+MIMEDefang) with ESMTP id i368sw9h089507; Tue, 06 Apr 2004 10:55:00 +0200 (CEST)
Received: from [10.1.1.109] (n-stiemerling.office [10.1.1.109]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 4063211DBC6; Tue, 6 Apr 2004 10:54:57 +0200 (CEST)
Date: Tue, 06 Apr 2004 10:54:54 +0200
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Ralph Droms <rdroms@cisco.com>, 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
Message-ID: <2147483647.1081248894@[10.1.1.109]>
In-Reply-To: <20040405151025.GA12352@login.ecs.soton.ac.uk>
References: <4.3.2.7.2.20040331131912.02663cc0@flask.cisco.com> <20040331205044.GL20993@login.ecs.soton.ac.uk> <2147483647.1081180497@[10.1.1.109]> <20040405151025.GA12352@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.1.2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.35
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Tim,

--On Montag, 5. April 2004 16:10 Uhr +0100 Tim Chown <tjc@ecs.soton.ac.uk> 
wrote:

| On Mon, Apr 05, 2004 at 03:54:57PM +0200, Martin Stiemerling wrote:
|>
|> Hmm, I don't see any assumption saying that there will be IPv6 NATs. The
|> document ist just saying that the MIDCOM server can be reached via IPv6,
|> whether there is a NAT at the box or not is a different story.
|
| Taken from the intro draft-tran-midcom-dhcpv6-option-01:
|
|   "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.
|    A DHCPv6 option provides a means for these entities to determine the
|    Midcom middleboxes IPv6 address or the domain name."
|
| But that text is cut and paste from the IPv4 version of the draft.
| Perhaps the v6 version can omit mention of translators? (If people use
| it for that, so be it, but we're not then "suggesting" it...)

The text gives the freedom to read it different ways. As a MIDCOM guy I do 
read it as "the configuration protocol's endpoint address might be IPv6 
capable, but not the middlebox engine (=firewall and/or NAT)".
But indeed I see the point of given a more elaborated text.

  Martin


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