search

cose-wg / CBOR-certificates

Other
11 stars 7 forks source link

EUI-64 encoding in X.509 #22

Closed emanjon closed 4 years ago

emanjon commented 4 years ago

Is it specified somewhere how an EUI-64 in encoded to a text string for use in X.509. In that case we should refer to that specification.

If not, we should specify that we assume the EUI-64 is encoded as xx-xx-xx-xx-x-xx-xx-xx

emanjon commented 4 years ago

Note: According to the IEEE guidelines, the first four digits of the organizationally assigned identifier (i.e., the first four digits of the extension identifier) portion of an EUI-64 “shall not be FFFE16 or FFFF16” (i.e., EUI-64 identifiers of the form ccccccFFFEeeeeee and ccccccFFFFeeeeee are not allowed) – this is to support the encapsulation of EUI-48 (FFFE16) and MAC-48 (FFFF16) values into EUI-64 values (though now the encapsulation is deprecated).

Other identifiers

emanjon commented 4 years ago

Decision to just try to encode what is used out in the wild. common names with the format "HH-HH-HH-HH-HH-HH-HH-HH" and "HH-HH-HH-FF-FE-HH-HH-HH" are not optimized