add optional 'name' key to mDNS specification

[chrisuthe]

Problem: In both a server-initated and client-initiated connection the end user must select something to connect to with only the information in the mDNS advertisement as the basis for that selection.

Solution: This addition would add an optional 'name' field, which would allow clients and servers to advertise their friendly names as part of the mDNS message. This will allow a user to see the name of the device (if set) instead of an ID, which could be non-descriptive.

[balloob]

I support this proposal.

[chrisuthe]

Problem: In both a server-initated and client-initiated connection the end user must select something to connect to with only the information in the mDNS advertisement as the basis for that selection.

Solution: This addition would add an optional 'name' field, which would allow clients and servers to advertise their friendly names as part of the mDNS message. This will allow a user to see the name of the device (if set) instead of an ID, which could be non-descriptive.

Note, this initial message contained incorrect assumptions.
The server/client can/should send hello to each client discoverd with the connection reason "Discovery" - this would allow the already existing name to be communicated for identification purposes.

This still may be useful since multi-player support is left to the client implementation; they may not choose to connect for discovery to every server prior to displaying them (such as what the SendSpinCLI does now), and it would be nice to have the simple additional name to display.