<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
> >> mDNS is used more in the UNIX world, SSDP is used more in Windows.<br>
> >><br>
> Was on the Redfish call earlier and this forum thread was discussed. The <br>
> Redfish members on the call did not totally agree with this statement. <br>
> They believe SSDP has a wider adaption than just Windows. A wider <br>
> adaption than mDNS. Since SSDP is already in the Redfish specification <br>
> and has been adapted by Redfish implementations, adding a 2nd discovery <br>
> service would damage interoperability in Redfish.<br>
<br>
I'm not really interested in a debate on this point, but I'm not finding<br>
much evidence to back it up. Can anyone point to well-used OSS<br>
implementation of SSDP? The only thing I can find is gssdp, which seems<br>
to require a lot of Gnome components; not something we could easily pull<br>
in on the BMC.<br>
<br></blockquote><div>The only thing besides gssdp is this <a href="https://github.com/troglobit/ssdp-responder">https://github.com/troglobit/ssdp-responder</a>, but that's only one (presumably easier) half.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> The members on the call really wanted to encourage OpenBMC to implement <br>
> SSDP instead.<br>
<br>
It probably isn't a bad thing to be able to support SSDP, don't get me<br>
wrong, but "instead"? Why would we want to take away service <br>
advertisement functionality, unless someone wants to explicitly disable it?<br>
<br>
I can understand if they don't want to document, in the standard, a way to<br>
advertise the Redfish service over mDNS, but isn't that a different<br>
problem from what we're asking for? Aren't we asking for a method to<br>
manage the enablement of services on the BMC, specifically our mDNS<br>
service? So, if we still have mDNS, don't we need a way to configure it<br>
through Redfish?<br><br></blockquote><div>I see your point here. I guess there might be some implicit assumption that adding it to a schema implies endorsement elsewhere. </div><div>Discovery is probably an area where supporting a diversity of protocols is better than making a single choice.</div></div></div>