IETF Logo Mail Archive

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

Harald Tveit Alvestrand <harald@alvestrand.no> Tue, 10 February 2004 06:50 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 BAA19586 for <dhcwg-archive@odin.ietf.org>; Tue, 10 Feb 2004 01:50:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqRiH-0000Ou-2c for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 01:49:41 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1A6nftp001534 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 01:49:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqRiG-0000Of-Un for dhcwg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 01:49:40 -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 BAA19574 for <dhcwg-web-archive@ietf.org>; Tue, 10 Feb 2004 01:49:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqRiD-0007Ec-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 01:49:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqRhN-00079W-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 01:48:46 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AqRgg-00073w-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 01:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqRgf-0000HW-Bw; Tue, 10 Feb 2004 01:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqRgK-0000Gg-T0 for dhcwg@optimus.ietf.org; Tue, 10 Feb 2004 01:47:40 -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 BAA19499 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 01:47:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqRgH-000727-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 01:47:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqRfF-0006vo-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 01:46:34 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx with esmtp (Exim 4.12) id 1AqReK-0006lV-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 01:45:36 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 406E161B92; Tue, 10 Feb 2004 07:45:05 +0100 (CET)
Date: Mon, 09 Feb 2004 22:13:43 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt
Message-ID: <2476616956.1076364823@localhost>
In-Reply-To: <y7vu11z1ocg.wl@ocean.jinmei.org>
References: <2427813621.1076316018@localhost> <y7vu11z1ocg.wl@ocean.jinmei.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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


--On 10. februar 2004 14:43 +0900 "JINMEI Tatuya / 
=?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=" <jinmei@isl.rdc.toshiba.co.jp> 
wrote:

>>>>>> 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.

thank you!
I really have no idea which of those two formats is the better one to use 
in this context, but have a strong preference that the drafts specify one, 
the other or "you shouldn't do this". Having users do (and expect) all 
three is the worst of all the outcomes....

> - 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.

I'll leave that to the IPv6 experts....

               Harald


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

v2.23.0 | Report a Bug | By Email