IETF Logo Mail Archive

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

Charlie Perkins <charles.perkins@earthlink.net> Sat, 23 June 2018 01:54 UTC

Return-Path: <charles.perkins@earthlink.net>
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 02155130DCD for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 22 Jun 2018 18:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.731
X-Spam-Level:
X-Spam-Status: No, score=-2.731 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 e3ESz4i9nKjZ for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 22 Jun 2018 18:54:20 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) (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 574F7130DC3 for <ieee-ietf-coord@ietf.org>; Fri, 22 Jun 2018 18:54:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1529719254; bh=Jc4f77AqjT6HwLnyYwAeqpljqEoyZZYgxO0+ YMyBoR8=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:Content-Language:X-ELNK-Trace: X-Originating-IP; b=RdLdpN8k7jDKbJvKVfOdiaTus/qTamE55xx8ZDDru5SXTs B3BcbK37b8zkqJPN8AARTWOMrQA1+HspHu1r/hqte/QxywEgNRV2CjSW3faJB5EEtC5 060/U0bJRQpLZAZ9YmmkKh5xFk5LHFFsUeeuSAIKLp2Up7BwI/LKLuL6JV3afZdPBPj nyPwYgJ2wQdt2pavOqB0x0F3FobpGvtOWU4DczX+PjcdZp6wCS0ve803NPo36mbJFdH k2Qj3MsJZLDX1sF2rVCg6epGwrZ/dZ++JsD32dxClN7sIu8U0NZFAkwsvL0UJRUzWjr tkTWArPijGvpvxuep27rqCTrPQ5g==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=ng9sXyniBFBkfuluu4em4ZjDJbDmSEMqx5GQhon5qbjH0cRRIKDwvGi8d52/Jdm1VR5Ia2Ln5//+o1eLQmxILluSNP8cpjAsA4bY5SaamSz0u+7uju0QDNnWyz2OfnuQhW76xx7vVYcW6Q7WPEbw6uJws78jo2pPwwEkkgy3vdyAjL3RJqwNPksjmJhZLVMC1iWRY6banW4L5FnCVf+R4CH1K1lKkgb9reRueOS7iW1t45eFFY4VThoO1R/qZZXoIU94kKCNP/D38iNHLmBnxtvINK0FDL87UlKY7bxI0A6LulJ6ednmXfmocbxFR1/KxMGewRlfzt/Z7UaBYrnTyw==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1fWXrA-000GEF-6J for ieee-ietf-coord@ietf.org; Fri, 22 Jun 2018 22:00:52 -0400
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
References: <TU4PR8401MB06214FDFC0652364F7728557ED750@TU4PR8401MB0621.NAMPRD84.PROD.OUTLOOK.COM>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <70d78698-7ec3-3a6e-3200-a958ba520141@earthlink.net>
Date: Fri, 22 Jun 2018 18:54:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <TU4PR8401MB06214FDFC0652364F7728557ED750@TU4PR8401MB0621.NAMPRD84.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95769e5d9c9066c9d0a1235e23e5206369350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/b7SF9-ikJUhnILeNvPHI4hQ_VyM>
Subject: [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: Sat, 23 Jun 2018 01:54:22 -0000

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.

v2.23.0 | Report a Bug | By Email