Pat, et al, I have suggested one paragraph to be added by 802.11, stating that we are considering clarifying the language in 802.11 around the specific protocol elements that WBA is referencing, and how they relate to/use OUI and CID. In my opinion, the 802.11 language could be a bit more clear about how 802.11 supports extended OUIs/CIDs, in this context. I intend to bring this language to the 802.11 closing plenary tomorrow, to get WG11 approval of both the 802.1 language (just as a double-check) and the 802.11 addition of this paragraph. I’m assuming this is the right process, and will result in a combined letter getting to 802 for their approval and forwarding to WBA. The letter (802.1’s response, with my one paragraph addition) can be found here: https://mentor.ieee.org/802.11/dcn/17/11-17-1797-00-0000-liaison-reply-to-the-wba-on-oui-usage.docx If anyone has any concerns, please let me know. Mark From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Pat Thaler
Sent: Thursday, November 09, 2017 9:23 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Fw[2]: Liaison Statement from WBA on Roaming OUI On Wed, Nov 8, 2017 at 2:39 PM, Pat Thaler <pat.thaler@broadcom.com> wrote: IEEE 802.1 assigned working on a liaison response to the Data Center Bridging and Addressing Task Group. Roger Marks and Bob Grow had drafted proposed responses and both were present to help us. The draft produced by the Working Group has been uploaded to the EC Mentor area for review: We understand that IEEE 802.11 may also have some material it wants to communicate and would prefer to send one liaison from IEEE 802 so we would welcome their additions. On Tue, Nov 7, 2017 at 11:52 AM, ROBERT GROW <bobgrow@cox.net> wrote: Paul, and WG Chairs. I hope the following might be helpful in responding to the incoming WBA liaison. IEEE Std 802c-2017 was published in August 2017. The IEEE Registration Authority tutorial on Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID) can be found at http://standards.ieee.org/develop/regauth/tut/eui.pdf. This tutorial was published at the same time as IEEE Std 802c-2017. The tutorial provides useful information on your questions including guidance you have requested. In response to your questions. 1. Where MAC Addresses are not required IEEE Registration Authority customers will be guided to request a CID instead of an MA-L (with its included OUI). An MA-S assignment would not be appropriate because the included OUI-36 would not provide any room for extension for the 36-bit RCOI. If the organization already has been assigned an OUI, They could use that OUI instead of a CID.
Quoting from the tutorial, “Two types of identifier– the 24-bit Organizationally Unique Identifier (OUI) and the 24-bit Company ID (CID)– are related to each other in that they come from the same 24-bit space but fall in different subspaces…” “An OUI or a CID may be used for identification of a company, organization, entity, manufacturer, vendor, etc.” 2. The ranges specified on MA-L, MA-M and MA-S assignments are for EUI-48 and EUI-64 (which are typically used as MAC addresses). It is not appropriate to describe for example picking a 40-bit number from a range of 48-bit EUIs. The context dependent extended identifier should be specified using a base of a CID or OUI assignment, extending the 24-bits of that identifier to 36-bits or 40-bits as required by RCOI specifications you would write. 3. Your RCOI as described is one of many possible context dependent extended identifiers. Quoting from the tutorial: “In addition to serving as a globally unique organization identifier, an OUI, OUI- 36, or CID may also be used as the basis of extended identifiers, including protocol identifiers and context dependent identifiers, by concatenating additional differentiating bits. These extended identifiers might be globally unique (e.g., EUI-48 and EUI-64) or only unique within the context in which they are used.”
This means for example, in specifying a protocol exchange that includes an RCOI, the device creating the RCOI for inclusion in the protocol field generates a number that is unique using an assigned CID or OUI as a base, and concatenating bits that create a unique RCOI. ------ Forwarded Message ------ Sent: 11/7/2017 8:24:54 AM Subject: Fw: Liaison Statement from WBA on Roaming OUI I am remiss in forwarding the below liaison from WBA to our group, please add it to your agendas for consideration this week as appropriate. ------ Forwarded Message ------ Sent: 11/1/2017 4:47:46 PM Subject: Liaison Statement from WBA on Roaming OUI Dear Bruce, Paul and Adrian, Please see in attach a liaison statement from the WBA Testing & Interoperability Workgroup on the topic of IEEE Roaming OUI. This liaison statement is to the attention of the following groups IEEE 802, IEEE 802.1 and IEEE 802.11. Feel free to contact me if you have any enquiry. ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.<WBA LS on IEEE Roaming OUI v1.0 20171031.docx>
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. |