Adding IVY (network inventory). For the network inventory and hardware YANG models, UUID is used (per RFC 6991 and RFC 4122), which does not prescribe a structure but does not preclude it either. (See e.g. RFC 8348 or https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-network-inventory-yang-02) --- Alex
-----Original Message----- From: OPSAWG <[email protected]> On Behalf Of Toerless Eckert Sent: Tuesday, September 19, 2023 9:09 AM To: [email protected] Subject: [OPSAWG] OPSAWG: Examples for IDevID "identifier" field formats (X520SerialNumber or the like) Dear OPSAWG, I am looking for concrete examples of device certificates, specifically the format of any "identifier" field that is uniquely identifying the device, such as the X520SerialNumber field. I was hoping this WG would actually have folks who can look at real equipment for example ;-)) I have found no good examples in RFCs. I hope / suspect that some vendors would use a more structured format, such as X520SerialNumber = "PID:ANI-SDEV-7X9 SN:FBC1234X97A", e.g.: contatenation of device type and actual serial number. If you are aware of any specific standards or other recommendations as to the format of such a field, i welcome points (e.g.: OPC UA has one for their own ProductInstanceUri, but its not clear to me if this is being adopted in reality). Thank you so much Toerless P.S.: reason for asking: In ANIMA/BRSKI, we have the case where we need to use network discovery to find devices based on such information, and we're pondering if/how well enough the information is cross-product-family and cross-vendor unique enough, and/or how much we need to think of further qualification. _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
