On 06/29/2012 12:58 PM, james woodyatt wrote:
On Jun 29, 2012, at 11:27 , Michael Thomas <[email protected]> wrote:
Maybe I can add some fuel to Olafur's fire. I'd like to say that the homenet
name service MUST be DNS.
Let's go further. Let's say that it must be DNS-Based Service Discovery
[I-D.cheshire-dnsext-dns-sd], which has been in the RFC Editor Queue for 199
days at this point, so one imagines that it stands a decent chance of being a
published RFC by the time HOMENET finishes its first round of major work.
James -- I'm not that familiar with dns-sd and it's been 1000 years since i've
thought about nbp, but services aren't the only thing I have in my home. Or
at least I wouldn't necessarily think of some things grouped together as named
services like, oh say, my light switches. Maybe I'd want to think of them that
way, but maybe I wouldn't. So I'm not sure that I'd be comfortable saying that
it's a particular flavor of DNS like DNS-sd.
That, and I can't tell whether this makes it easier, harder or neutral on my
original request that making the transition from a private name space to a
public one trivial. Can I use service discovery from across the Internet to get
back to things in my home assuming that I have a registered domain? Sorry
for the ignorance, but nbp was a decidedly localized protocol.
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
