Re: why 0xFFFE is used in the modified EUI-64 format
Daniel Roesen <dr@cluenet.de> Thu, 15 December 2005 01: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 1EmiK0-000225-Ky; Wed, 14 Dec 2005 20:54:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmiJx-00020u-00 for ipv6@megatron.ietf.org; Wed, 14 Dec 2005 20:54:13 -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 UAA26459 for <ipv6@ietf.org>; Wed, 14 Dec 2005 20:53:05 -0500 (EST)
Received: from mail1.cluenet.de ([195.20.121.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmiL6-00035j-Ok for ipv6@ietf.org; Wed, 14 Dec 2005 20:55:26 -0500
Received: by mail1.cluenet.de (Postfix, from userid 500) id 28A5A17A51; Thu, 15 Dec 2005 02:53:59 +0100 (CET)
Date: Thu, 15 Dec 2005 02:53:59 +0100
From: Daniel Roesen <dr@cluenet.de>
To: ipv6@ietf.org
Message-ID: <20051215015359.GA25390@srv01.cluenet.de>
Mail-Followup-To: ipv6@ietf.org
References: <y7vvexyma2k.wl%jinmei@isl.rdc.toshiba.co.jp> <20051215004028.GA24527@srv01.cluenet.de> <20051215013616.GA25136@srv01.cluenet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20051215013616.GA25136@srv01.cluenet.de>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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
On Thu, Dec 15, 2005 at 02:36:16AM +0100, Daniel Roesen wrote: > Nevertheless, the significance of bits #57 and #58 are not widely > known to IPv6 operators out there. I cannot count. g-bit is bit #56, not #58. My only excuse for this mail flood is that it's almost 3am local time here. :-Z My apologies. Best regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- why 0xFFFE is used in the modified EUI-64 format JINMEI Tatuya / 神明達哉
- Re: why 0xFFFE is used in the modified EUI-64 for… Suresh Krishnan
- Re: why 0xFFFE is used in the modified EUI-64 for… Daniel Roesen
- Re: why 0xFFFE is used in the modified EUI-64 for… Daniel Roesen
- Re: why 0xFFFE is used in the modified EUI-64 for… Daniel Roesen
- Re: why 0xFFFE is used in the modified EUI-64 for… Daniel Roesen
- Re: why 0xFFFE is used in the modified EUI-64 for… JINMEI Tatuya / 神明達哉
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- Re: why 0xFFFE is used in the modified EUI-64 for… JINMEI Tatuya / 神明達哉
- Re: why 0xFFFE is used in the modified EUI-64 for… Juergen Schoenwaelder
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- Re: why 0xFFFE is used in the modified EUI-64 for… JINMEI Tatuya / 神明達哉
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- RE: why 0xFFFE is used in the modified EUI-64 for… Durand, Alain
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- Re: why 0xFFFE is used in the modified EUI-64 for… Bob Hinden
- RE: why 0xFFFE is used in the modified EUI-64 for… Manfredi, Albert E