BMC SSDP Service Discovery

[svenrademakers]

for a better user experience for our client tools, such as tpi, implement a service discovery mechanism as defined in the redfish spec.

Goal

The objective of discovery is for client software to locate managed devices that conform to the Redfish
Specification. Therefore, the primary SSDP functionality is incorporated in the M-SEARCH query.

Example response

HTTP/1.1 200 OK
CACHE-CONTROL:max-age=<seconds, at least 1800>
ST:urn:dmtf-org:service:redfish-rest:1
USN:uuid:<UUID of the service>::urn:dmtf-org:service:redfish-rest:1
AL:<URL of Redfish Service Root>
EXT:

Acceptance Criteria

• the service should use UDP port 1900 for all SSDP traffic.
• the Time-to-Live (TTL) hop count setting for SSDP multicast messages should default to 2.
• The UUID in the USN field of the service shall equal the UUID property in the Service Root.
• The unique ID shall be in the canonical UUID format, followed by ::dmtf-org.
• the bmc responds to search targets: urn:dmtf-org:service:redfish-rest:1 and ssdp:all and upnp:rootdevice
• The URN provided in the ST header in the reply shall use the redfish-rest: service name followed by
  the major version of the Redfish Specification

[svenrademakers]

cloned issue to turing-machines/bmcd#27