IETF Logo Mail Archive

Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Wed, 11 February 2004 02:12 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 VAA12761 for <dhcwg-archive@odin.ietf.org>; Tue, 10 Feb 2004 21:12:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqjrV-0008OV-FK for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 21:12:26 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1B2CPx3032261 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 21:12:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqjrV-0008OG-C5 for dhcwg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 21:12:25 -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 VAA12758 for <dhcwg-web-archive@ietf.org>; Tue, 10 Feb 2004 21:12:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqjrS-0007AB-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 21:12:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aqjqb-00074E-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 21:11:29 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Aqjq9-0006xu-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 21:11:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqjqA-0008Db-EU; Tue, 10 Feb 2004 21:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqQhP-00050Y-F1 for dhcwg@optimus.ietf.org; Tue, 10 Feb 2004 00:44:43 -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 AAA17727 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 00:44:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqQhM-00019m-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 00:44:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqQgT-00014r-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 00:43:46 -0500
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1AqQg8-0000z5-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 00:43:24 -0500
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id A95B715210; Tue, 10 Feb 2004 14:43:24 +0900 (JST)
Date: Tue, 10 Feb 2004 14:43:27 +0900
Message-ID: <y7vu11z1ocg.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt
In-Reply-To: <2427813621.1076316018@localhost>
References: <2427813621.1076316018@localhost>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
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

>>>>> On Mon, 09 Feb 2004 08:40:18 -0800, 
>>>>> Harald Tveit Alvestrand <harald@alvestrand.no> said:

> - In all the instances I've seen so far, declare that if you need an IPv4 
> address, put it in as an IPv4-mapped IPv6 address (::12.34.56.78) - no 
> other changes needed.

A couple of minor notes:

- ::12.34.56.78 is NOT an IPv4-mapped IPv6 address (but an
  IPv4-compatible IPv6 address).  You should probably have meant
  ::ffff:12.34.56.78.

- if we really go with this approach, we should also consider
  draft-itojun-v6ops-v4mapped-harmful-02.txt
  which proposes "nodes SHOULD NOT generate packets that contain
  IPv4-mapped addresses in any field" in a packet sent on the wire in
  order to avoid confusion with API usages of IPv4-mapped addresses.
  Though this is still an individual draft, there seems to be a
  consensus on "no IPv4-mapped IPv6 addresses in the wire", at least
  to some extent.

(just to avoid unnecessary flame: I'm not talking about the API usage
of IPv4-mapped IPv6 addresses (whether it's a good idea, etc) at all.
In particular, please do not confuse this issue with
draft-cmetz-v6ops-v4mapped-api-harmful-01.txt)

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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

v2.23.0 | Report a Bug | By Email