Re: [homenet] alternatives to .home

Michael Richardson wrote: > AFAIK, ".local" is not used on the wire with mDNS. The .local is a > clue from the end-user to the resolver that you should use mDNS to > resolve the name. I stand corrected: it's on the wire. -- Michael Richardson

[homenet] "mDNS proxy" in RFC 7788

While I was reviewing RFC 7788 because of the .home issue, I ran some other text that I think needs to be clarified. Section 7.4 refers to a "Multicast DNS Proxy", with a citation of RFC 6762. The problem here is that RFC 6762 does not provide a definition of "Multicast DNS Proxy Servers"

Re: [homenet] RFC 7788-bis

On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote: > As for #2, yeah, that's hard, but it seems ICANN won't do anything about > ".home" because of #1 anyway, but they seemed stalled on outright > rejecting it and have said (AFAICR) that an RFC 6761 registration would > allow them to

Re: [homenet] alternatives to .home

> On Jun 20, 2016, at 10:23 AM 6/20/16, Michael Richardson > wrote: > > Juliusz Chroboczek wrote: - how does software running on my laptop, which just connected to an unknown network, find out what is the local translation of

Re: [homenet] alternatives to .home

Juliusz Chroboczek wrote: >>> - how does software running on my laptop, which just connected to an >>> unknown network, find out what is the local translation of "home"? >> It doesn't. It uses HNCP. > Please describe exactly how my laptop (which