(cutting to get to the point) >>>>> "Kerry" == Kerry Lynn <[email protected]> writes: Kerry> What I'm trying to figure out is whether most people in these conversations Kerry> are envisioning a unicast DNS service in the home that has a "locally Kerry> defined" zone, as opposed to mDNS which *distributes* the name service.
We want to make this possible, but not required.
And when possible, make it easy. The easiest way I can think of is;
Kerry> One way in which the latter may be deployed may be to have some
"agent"
Kerry> that listens to mDNS announcements and then enters RRs into a unicast
Kerry> DNS. This still doesn't buy us FQDNs, however, unless the DNS has a
Kerry> delegated zone.
1) the listener populates the reverse zone, which we have proposals on
how to delegate via DHCPv6.
2) the listener could populate a forward zone, if one existed.
I'm talking about #2.
a) if said forward zone existed, it would be nice if mDNS would permit
the "canonical" FQDN for a host to be discoverable (and therefore
bookmarkable).
b) if said forward zone existed, should nodes be able to indicate their
desire to be in it (or not in it) via mDNS? or DHCP? Or ???
Finally, I was wondering if we can through some to-be-defined-magic, get
a new FQDN-ish thing which can be used without pre-arrangement in the
home. Before I propose a solution (my first email hinted at one), I
would like to know if it's a problem worth solving.
Kerry> So you want to remotely access hosts in your residence, but without
Kerry> configuration of any sort?
Yes. I want to discover things in my home, and then remember how to
talk to them.
Kerry> I'd support seeing more about naming/service discovery in homenet
drafts as
Kerry> opposed to the mailing list.
okay.
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpM6aUeT26Rw.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
