IETF Logo Mail Archive

Re: [ieee-ietf-coord] Rationale for 0xFFFE as octets 4 and 5 pf EUI-64?

John Messenger <jmessenger@advaoptical.com> Sun, 24 June 2018 23:37 UTC

Return-Path: <jmessenger@advaoptical.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64AEC130E78 for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 24 Jun 2018 16:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-PbzyKw2pkT for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 24 Jun 2018 16:37:37 -0700 (PDT)
Received: from mail2.advaoptical.com (mail2.advaoptical.com [91.217.199.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CD57130E72 for <ieee-ietf-coord@ietf.org>; Sun, 24 Jun 2018 16:37:36 -0700 (PDT)
Received: from MUC-S-EX16D.advaoptical.com ([172.20.1.28]) by muc-vs-fsmail2.advaoptical.com (8.16.0.22/8.16.0.22) with ESMTPS id w5ONbWiF010770 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=FAIL); Mon, 25 Jun 2018 01:37:32 +0200
Received: from MGN-S-EX16A.advaoptical.com (172.25.1.191) by MUC-S-EX16D.advaoptical.com (172.20.1.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Mon, 25 Jun 2018 01:37:32 +0200
Received: from MGN-S-EX16B.advaoptical.com (172.25.1.192) by MGN-S-EX16A.advaoptical.com (172.25.1.191) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Mon, 25 Jun 2018 01:37:31 +0200
Received: from MGN-S-EX16B.advaoptical.com ([fe80::c022:bed0:3eb:b5c5]) by MGN-S-EX16B.advaoptical.com ([fe80::c022:bed0:3eb:b5c5%7]) with mapi id 15.01.1531.003; Mon, 25 Jun 2018 01:37:31 +0200
From: John Messenger <jmessenger@advaoptical.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
CC: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
Thread-Topic: [ieee-ietf-coord] Rationale for 0xFFFE as octets 4 and 5 pf EUI-64?
Thread-Index: AQHUCpUfLWK8lMTOYkaA2U3mUPJlRaRwE3g5
Date: Sun, 24 Jun 2018 23:37:30 +0000
Message-ID: <D6E9B1A2-2D0D-44D2-8798-8D80C1C5B3F0@advaoptical.com>
References: <TU4PR8401MB06214FDFC0652364F7728557ED750@TU4PR8401MB0621.NAMPRD84.PROD.OUTLOOK.COM>, <70d78698-7ec3-3a6e-3200-a958ba520141@earthlink.net>
In-Reply-To: <70d78698-7ec3-3a6e-3200-a958ba520141@earthlink.net>
Accept-Language: en-GB, de-DE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-24_13:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/c6PgJWTAYn-m3ksbBhwSFrWOqYA>
Subject: Re: [ieee-ietf-coord] Rationale for 0xFFFE as octets 4 and 5 pf EUI-64?
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2018 23:37:42 -0000

I asked a couple of people in 802.1 without getting an answer.

      -- John

> On 23 Jun 2018, at 02:54, Charlie Perkins <charles.perkins@earthlink.net> wrote:
> 
> Hello folks,
> 
> Does anyone here remember why 0xFFFE were chosen to be the filler bits (i.e., bytes 4 and 5 of 8) when expanding a 48-bit MAC address to be EUI-64?  It is not explained in RFC 2464.
> 
> Or maybe there was not a reason...?
> 
> Thanks in advance,
> Charlie P.
> 
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord

v2.23.0 | Report a Bug | By Email