In message <[email protected]>
Andrew Sullivan writes:
> On Wed, Aug 08, 2012 at 01:09:00PM -0400, Curtis Villamizar wrote:
> >
> > Yes this is a good suggestion.
> >
> > Examples:
> >
> > printer3 is unqualified.
> >
> > printer3.local. in mDNS is a LQDN.
>
> Except, of course, that it's not a "DN" at all: it's not a domain
> name. It's an mDNS name. Different protocol on a different port.
> Most notably, mDNS always uses UTF-8 and DNS often does not, and
> normally when you want to look up a Unicode string in the global DNS
> what you actually look up is a name made of A-labels.
Good point. I agree. Change this to:
printer3.local. in mDNS is not a domain name at all
Perhaps mDNS should not have used DNS in the name. It might be
possible to tie mDNS into DNS such that a DNS resolver could return
something useful for a printer3.local query in which case
printer3.local would be a LQDN. Without that tie in, it is not.
Curtis
> This is problematic, because if you just put
>
> http://café
>
> in your browser's URL bar, you're going to get different behaviour
> depending on your network, your browser, and your operating system.
>
> I'm aware that from the user's point of view, they're all just names,
> but I don't think it helps us as protocol people to gloss over the
> differences among different name technologies that are all in use at
> the same time.
>
> Best,
>
> A
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
