|
|
Post by nschellenberger on Jun 9, 2023 17:24:36 GMT
Related to my previous inquiry, what are the semantics (or at least intended use) of ServiceRoot/ServiceIdentification? In what circumstances does it provide value beyond ServiceRoot/UUID? (Perhaps e.g. a cryptographically testable value--like an HMAC of a serial number or similar--to provide a degree of mutual repudiation during provisioning/adoption of a Redfish service? "OK Redfish Manager Entity, you claim to be the legitimate manager for rack S/N 1234 out somewhere on the data centre floor. Prove it to me over here in the ops centre.")
|
|
|
|
Post by jautor on Jun 9, 2023 22:52:49 GMT
The intent was to surface whatever identifier the manufacturer provides to the end customer/user to "match up" a device discovered on the network (via DHCP, SSDP , or whatever means) with initial, pre-shared credentials. While UUID can absolutely serve that purpose - that value is not generally what is provided to end users. It may be the unit serial number, the MAC address of the BMC, or something else entirely. Since we have no control over the factory or deployment processes that assign those values, and those will all be vendor-specific, we defined this property to solely provide that identifier - regardless of its origin or use elsewhere...
That said, the description in the schema doesn't seem to get that point across, so we need to improve it.
Jeff
|
|
|
|
Post by nschellenberger on Jun 11, 2023 16:05:55 GMT
Thanks Jeff! FWIW that's what we thought, but I thought I should check if there were any very specific expected semantics.
|
|
