helper function for_ssh._tcp useful for client UIs to resolve SD service types
should map URL schema to ssh://
take host from SRV record
take optional port (not needed for default port 22) from SRV record
take optional username from TXT attribute "user" ie user=vortex
and map into format ssh://username@><host<:port>
this well known mapping will work for any browser on any platform that has a schema handler defined for ssh://
example: ssh://vortex@zembla.zenr.io
For any browsing domain that wishes to define one or more _ssh._tcp service type instances, a PTR record of (eg)
helper function for_ssh._tcp useful for client UIs to resolve SD service types
should map URL schema to ssh:// take host from SRV record take optional port (not needed for default port 22) from SRV record take optional username from TXT attribute "user" ie user=vortex and map into format ssh://username@><host<:port>
this well known mapping will work for any browser on any platform that has a schema handler defined for ssh://
example:
ssh://vortex@zembla.zenr.io
For any browsing domain that wishes to define one or more _ssh._tcp service type instances, a PTR record of (eg)
_services._dns-sd._udp.<browsing domain> PTR _ssh._tcp.<browsing domain>
must exist.
For any browsing domain that has has no _ssh._tcp service types existing or last remaining has been deleted, then PTR record of
_services._dns-sd._udp.<browsing domain> PTR _ssh._tcp.<browsing domain>
should be deleted.