On 10/22/2012 07:22 AM, Tim Chown wrote:
And I don't think this possibility is excluded at all by the current arch text
either. It talks of an authoritative name service running on the CER, with a
dynamic registration service (e.g. dyndns). I have added 'as far as possible'
to the unmanaged text.
It's been hard for me to gauge what is and isn't in scope on the naming
front. For the most part, this wg looks like it's only interested in putting
some band-aides on mdns/dns-sd. That's a mistake, IMO, because there's
nothing inevitable about a zeroconf driven design. We should consider
littleconf solutions especially for naming because there is no way that
mikes-toothbrush.mtcc.com got named that way coming from the factory.
Mechanistically, we already have things like IXFR for DNS, so it's not likely
that
this is wholesale invention, though it may well involve some tweaks. IXFR also
gives the possibility for enrollment and access control which is pretty
problematic
with service discovery.
I think these issues may come up in the mdnsext BoF - I encourage you to join
that list and give comment there.
Correct me if I'm wrong, but I'd think that a mdnsext bof is interested in
extending mdns. What I'm talking about has nothing to do with multicast,
dns or otherwise. So I'm not sure that my participation would be all that
welcome.
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
