IETF Logo Mail Archive

RE: the IPv6 Ethernet lost bits - fffe

"TJ" <trejrco@gmail.com> Wed, 01 October 2008 14:49 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66FEA28C118; Wed, 1 Oct 2008 07:49:51 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 113AD28C118 for <ipv6@core3.amsl.com>; Wed, 1 Oct 2008 07:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.832
X-Spam-Level:
X-Spam-Status: No, score=-2.832 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tu698GrIqSwR for <ipv6@core3.amsl.com>; Wed, 1 Oct 2008 07:49:49 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by core3.amsl.com (Postfix) with ESMTP id 27BB228B23E for <ipv6@ietf.org>; Wed, 1 Oct 2008 07:49:49 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so96966yxg.49 for <ipv6@ietf.org>; Wed, 01 Oct 2008 07:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=j7Qprjz0ZIiPOkGKywAh8BIefZi0TsEc1vhXyPG7pP8=; b=L3W75CS1Y7pE3ZNcIrggx0tCDvneQCUS5lNd27+8ScxO7d8jkjQ2s0UZ9lsH1TxICt d5vvQPEWr0zsG/t8Wv8vflzpaERs/rtVy/2HPZa03ezjf1rIXUImtQzUGmYUV4eHisk2 hnwVAb8RCuc4Zhap/I/Z4Pz/4DXX1mnuBXkRw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=Q9vN1x/uJEEtjfi4kgo1p3bitZ2RX5gg3K/Jfq0+WoHt3daESXNyG8RZNyGcAtr09O itt9pWLuB+tGbR7+YVAOIXfpPtwzuRJe2V24r5nbvwxh2yiKaQ+sB1Rp3kvnra4fNjrW hNJvdVmi0XP4BLdOcFPaG6y1MW6+mCpmC2UCk=
Received: by 10.151.145.21 with SMTP id x21mr12185836ybn.97.1222872104960; Wed, 01 Oct 2008 07:41:44 -0700 (PDT)
Received: from Lapci010 ([98.174.20.11]) by mx.google.com with ESMTPS id t26sm5020525ele.6.2008.10.01.07.41.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Oct 2008 07:41:44 -0700 (PDT)
From: TJ <trejrco@gmail.com>
To: ipv6@ietf.org
References: <C0F2465B4F386241A58321C884AC7ECC085AB2AF@E03MVZ2-UKDY.domain1.systemhost.net><48E37330.3060801@gmail.com> <alpine.BSF.2.00.0810011457120.20355@mignon.ki.iif.hu><0AC4B700F00DBB4C94F95727E0991414014B24F6@IMCSRV7.MITRE.ORG> <006c01c923ce$303bcb70$90b36250$@com> <0AC4B700F00DBB4C94F95727E0991414014B24F8@IMCSRV7.MITRE.ORG> <48E387CD.3050200@gmail.com> <48E38B09.9080405@spaghetti.zurich.ibm.com>
In-Reply-To: <48E38B09.9080405@spaghetti.zurich.ibm.com>
Subject: RE: the IPv6 Ethernet lost bits - fffe
Date: Wed, 01 Oct 2008 10:41:43 -0400
Message-ID: <008001c923d3$d2f17180$78d45480$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ackj0z3h0NqcJ5kATM+zIbqD4t1GNgAAFiSA
Content-Language: en-us
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Exactly - (IMHO) reserving bits to ensure more widespread compatibility,
future scalability, etc. is not a loss ... in fact, I am glad we have the
bits to (cough) lose in order to accomplish those goals!


/TJ


>-----Original Message-----
>From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
>Jeroen Massar
>Sent: Wednesday, October 01, 2008 10:37 AM
>To: Alexandru Petrescu
>Cc: Steve_Eiserman@ao.uscourts.gov; ipv6@ietf.org
>Subject: Re: the IPv6 Ethernet lost bits - fffe
>
>Alexandru Petrescu wrote:
>> For what it's worth,
>>
>> Whenever statelessly auto-configuring an IPv6 address on Ethernet the
>> 10th and 11th bytes are always 'fffe', hardcoded.  These are lost bits.
>
>The world has more devices than Ethernet. The Ethernet MAC -> EUI-64 trick
>(thus your lost fffe bits) is just a trick. Take firewire for example which
>uses full EUI-64.
>
>Greets,
> Jeroen


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

v2.46.0 | Report a Bug | By Email | System Status