IETF Logo Mail Archive

Re: why 0xFFFE is used in the modified EUI-64 format

Bob Hinden <bob.hinden@nokia.com> Fri, 20 January 2006 17:54 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F00TJ-0005oK-9r; Fri, 20 Jan 2006 12:54:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F00TH-0005np-OG for ipv6@megatron.ietf.org; Fri, 20 Jan 2006 12:54:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05264 for <ipv6@ietf.org>; Fri, 20 Jan 2006 12:53:19 -0500 (EST)
Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F00c3-0005Fe-2x for ipv6@ietf.org; Fri, 20 Jan 2006 13:03:52 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0KHscPh020575; Fri, 20 Jan 2006 19:54:43 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Jan 2006 19:53:50 +0200
Received: from [172.19.69.50] ([172.19.69.50]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 20 Jan 2006 19:53:49 +0200
In-Reply-To: <6EEEACD9D7F52940BEE26F5467C02C7302217B32@PACDCEXCMB01.cable.comcast.com>
References: <6EEEACD9D7F52940BEE26F5467C02C7302217B32@PACDCEXCMB01.cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <4FE4C067-0889-4DC7-9E55-098D7947CA86@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Fri, 20 Jan 2006 09:53:47 -0800
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 20 Jan 2006 17:53:49.0855 (UTC) FILETIME=[77F22AF0:01C61DEA]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: IPv6 WG <ipv6@ietf.org>, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: why 0xFFFE is used in the modified EUI-64 format
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi,

>> It's only a note at the end of an appendix, but I wouldn't object to
>> removing the last sentence if others are troubled by it.  The intent
>> was to provide some advice to someone writing an IPv6 over <foo>
>> specification.
>
> I concur that the last sentence should be removed. It doesn't help  
> to clarify the current situation
> and may be read as closing the door to other future use of 0xFF and  
> 0xFF.

OK, I will remove the last sentence and send the text off to the RFC- 
Editor.

Thanks,
Bob



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email