Bugzilla

(In reply to Marco Bonardo [:mak] from comment #13)
> I think the RFC should be respected when it says .local should not be used, moreover the page you linked points out .internal should instead be used in those cases, but that's still a draft. We should add .internal once it's confirmed, or even sooner. 

I think you may have me confused with someone else - I haven't linked to much of anything in this bug. 

In any case, have you seen RFC 6762: https://tools.ietf.org/html/rfc6762 ?

It is not a draft and it states:

>Multicast DNS (mDNS) provides the ability to perform DNS-like operations on the local link in the absence of any conventional  Unicast DNS server.  In addition, Multicast DNS designates a portion of the DNS namespace to be free for local use, without the need to  pay any annual fee, and without the need to set up delegations or otherwise configure a conventional DNS server to answer for those names.

> Let me be clear, I think it's WRONG, .local should have never been used to indicate a specific kind of service or protocol, but that's the world we must live with.

Wrong like `-webkit-grid` and the rest of the properties here: https://developer.mozilla.org/docs/Web/CSS/WebKit_Extensions#Formerly_proprietary_properties_that_are_now_standard ?

It isn't even the case here that this is a pragmatic move made under pressure like the webkit properties becoming standard (even if WRONG) -- the mDNS RFC exists and is uncontroversial! It is probably stupid to use .local as a tld when you aren't actually using mDNS, but if you are it is perfectly valid and I expect it to work per the RFC.

(In reply to Marco Bonardo [:mak] from comment #13)
> I think the RFC should be respected when it says .local should not be used, moreover the page you linked points out .internal should instead be used in those cases, but that's still a draft. We should add .internal once it's confirmed, or even sooner. 

I think you may have me confused with someone else - I haven't linked to much of anything in this bug. 

In any case, have you seen RFC 6762: https://tools.ietf.org/html/rfc6762 ?

It is not a draft and it states:

>Multicast DNS (mDNS) provides the ability to perform DNS-like operations on the local link in the absence of any conventional  Unicast DNS server.  In addition, Multicast DNS designates a portion of the DNS namespace to be free for local use, without the need to  pay any annual fee, and without the need to set up delegations or otherwise configure a conventional DNS server to answer for those names.

I think this is unambiguous evidence showing that IETF believes that mDNS ought to be supported with .local.

> Let me be clear, I think it's WRONG, .local should have never been used to indicate a specific kind of service or protocol, but that's the world we must live with.

Wrong like `-webkit-grid` and the rest of the properties here: https://developer.mozilla.org/docs/Web/CSS/WebKit_Extensions#Formerly_proprietary_properties_that_are_now_standard ?

It isn't even the case here that this is a pragmatic move made under pressure like the webkit properties becoming standard (even if WRONG) -- the mDNS RFC exists and is uncontroversial! It is probably stupid to use .local as a tld when you aren't actually using mDNS, but if you are it is perfectly valid and I expect it to work per the RFC.