> Actually, it's fatal, because you can't get a certificate for "boombox.local" > so you can't secure it that way. So you always have to use the FQDN.
That sucks, of course, but the problem is completely unrelated to being published in the global DNS -- the very same problem applies to names that only appear in local MDNS. >> I think that's our main disagreement. >> For some reason, you guys seem to be assuming that the average user will >> want to publish hundreds of names in the global DNS. > Hundreds? How about two. > My son wants to publish his desktop's name so that his friend can reach his > system directly for minecraft. I want the same. Your son clicks "publish name" in the Minecraft server's UI, at which point he faces the following dialog box: Domain: dyndns.minecraft.example.com Hostname: minecraft-7ac8 Password: The young man considers that default values are for noobz, and edits as follows: Domain: richardson-family.vanity-dyndns.example.com Hostname: better-server-than-dads Password: After the name is published (which takes half a second), the Minecraft UI displays a "share" icon, so that your son can publish the server's name over UUCP, or whatever it is that them youngsters use nowadays for chatting. Your turn now. Could you please describe the UI that you envision? -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
