From a69331d7248345bde8fad2de93e4ce39c753be85 Mon Sep 17 00:00:00 2001
From: Laurence Lundblade <laurencelundblade@users.noreply.github.com>
Date: Thu, 5 Dec 2019 15:05:17 -0800
Subject: [PATCH] OEMID clarifications and references (#41)

* OEMID clarifications and references

* Typographic errors in OEM ID section

* Fix dates in references that seem to be causing build failures
---
 draft-ietf-rats-eat.md | 56 ++++++++++++++++++++++++++++++++----------
 1 file changed, 43 insertions(+), 13 deletions(-)

diff --git a/draft-ietf-rats-eat.md b/draft-ietf-rats-eat.md
index ba359293..149aff2b 100644
--- a/draft-ietf-rats-eat.md
+++ b/draft-ietf-rats-eat.md
@@ -122,6 +122,26 @@ informative:
     date:  June 2011
     target: http://www.ecma-international.org/ecma-262/5.1/ECMA-262.pdf
 
+  OUI.Guide:
+    title: Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)
+    date: August 2017
+    target: https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf
+
+  OUI.Lookup:
+    title: IEEE Registration Authority Assignments
+    target: https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries
+    date: false
+
+  IEEE.RA:
+    title: IEEE Registration Authority
+    target: https://standards.ieee.org/products-services/regauth/index.html
+    date: false
+
+  IEEE.802-2001:
+    title: IEEE Standard For Local And Metropolitan Area Networks Overview And Architecture
+    target: https://webstore.ansi.org/standards/ieee/ieee8022001r2007
+    date: 2007
+
 
 --- abstract
 
@@ -479,19 +499,29 @@ in CWT in that it describes the authority that created the token.
     origination_claim = (
     origination: string_or_uri )
 
-## OEM identification by IEEE OUI (oemid)
-
-This claim identifies a device OEM by the IEEE OUI. Reference TBD. It
-is a byte string representing the OUI in binary form in network byte
-order (TODO: confirm details).
-
-Companies that have more than one IEEE OUI registered with IEEE should
-pick one and prefer that for all their devices. 
-
-Note that the OUI is in common use as a part of MAC Address. This
-claim is only the first bits of the MAC address that identify the
-manufacturer. The IEEE maintains a registry for these in which many
-companies participate.
+## OEM Identification by IEEE (oemid)
+
+The IEEE operates a global registry for MAC addresses and company IDs.
+This claim uses that database to identify OEMs. The contents of the
+claim may be either an IEEE MA-L, MA-M, MA-S or an IEEE CID
+{{IEEE.RA}}.  An MA-L, formerly known as an OUI, is a 24-bit value
+used as the first half of a MAC address. MA-M similarly is a 28-bit
+value uses as the first part of a MAC address, and MA-S, formerly
+known as OUI-36, a 36-bit value.  Many companies already have purchased
+one of these. A CID is also a 24-bit value from the same space as an
+MA-L, but not for use as a MAC address.  IEEE has published Guidelines
+for Use of EUI, OUI, and CID {{OUI.Guide}} and provides a lookup
+services {{OUI.Lookup}}
+
+Companies that have more than one of these IDs or MAC address blocks
+should pick one and prefer that for all their devices.
+
+Commonly, these are expressed in Hexadecimal Representation
+{{IEEE.802-2001}} also called the Canonical format. When this claim is
+encoded order of bytes in the bstr are the same as the order in the
+Hexadecimal Representation. For example, an MA-L like "AC-DE-48" would
+be encoded in 3 bytes with values 0xAC, 0xDE, 0x48. For JSON encoded
+tokens, this is further base64url encoded.
 
 ### CDDL