Am 27.02.2013 15:35, schrieb Ted Lemon:
On Feb 27, 2013, at 2:51 AM, Ole Troan <[email protected]> wrote:
let us assume that we don't want anyone to remember these names. the UI will
present a list
of available services, given where you are.
Why would we assume that? Devices have names. My phone has a name, my laptop has a
name. How else would I know which device I was talking to? I don't want my phone to
just be "iPhone" in the discovery list. And if it has a name, I want it to
have the same name everywhere. Adding an extra layer of indirection doesn't make that
problem any easier.
This is a really important problem, and what you are proposing is moving in
exactly the wrong direction: a multiply-indirected naming hierarchy that will
almost certainly display artifacts that will confuse the heck out of users,
because at the bottom of the hierarchy names aren't consistent. We've seen
examples of this in the past--I'm sure that Stuart and Dave can tell you war
stories.
I believe this is what Wide Area Bonjour does these days: If you use
mDNS on one Network/Domain, you'll end up as mydevice.networkone.net,
and if you move to another Network/Domain you'll end up as
mydevice.networktwo.net
Still, someone from a third WAB network knows, that it's the same device
(if the device name is unique enough - but in homenet that shouldn't be
a problem). WAB works using a unicast DNS server, Long Lived Queries and
Dynamic Updates per network segment.
I don't think that's the way to go in the homenet though. WAB is
intended to cross the boundaries of the home network, while we're
talking what to do within the boundaries. If we could cross subnets
without DNS and without confusing domain names it would be better I think.
But as we might want to allow people who want a domain structure to set
it up, it might be a good idea to recommend the inclusion of a DNS
server capable of dynamic DNS updates in each homenet router...
Can be switched off by default... Might be something for a future draft
"naming of devices in the homenet". Is anyone already working on
something like that?
Keeping names consistent across subnets is possible. It can definitely be
done with DHCP, and there are RFCs documenting how it's done. If it can be
done with DHCP, it can be done with whatever protocol we settle on, whether
it's DHCP, mDNS, DNS+CGA+TSIG, or some other thing.
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
