On Jun 9, 2016, at 3:44 PM, Ralph Droms <rdroms.i...@gmail.com> wrote:

> 
>> On Jun 9, 2016, at 1:45 PM 6/9/16, Juliusz Chroboczek 
>> <j...@pps.univ-paris-diderot.fr> wrote:
>> 
>>> The specification (AFAIK) does not really require all implementations to
>>> agree on the same network-wide default (as it is not omitted from DDZ
>>> TLVs, the sub-zones are fully qualified), but I do not see any other
>>> sensible default than the one we use now. So I am not sure what this
>>> will change in practise.
>> 
>> I can be convinced to change the default in shncpd.  Please let ICANN know
>> that I prefer slightly used, non-sequential banknotes.
> 
> Regrettably, your response is a little misleading, as ICANN has nothing to do 
> with this process.  RFC 6761 outlines the process, which requires Standards 
> Action or IESG Approval and an IANA Considerations section that provides the 
> relevant information to be included in the Special-Use Names registry.

This is true, and I further suggest reviewing 
https://datatracker.ietf.org/doc/draft-adpkja-dnsop-special-names-problem/ and 
https://datatracker.ietf.org/doc/draft-tldr-sutld-ps/ for two different 
attempts to describe the challenges arising from trying to apply RFC 6761.

DNSOP has been working for a very long time now on a problem statement for the 
ways this can go wrong. 

> RFC 7788 seems to imply some special use characteristics for .home by making 
> it the default zone to be "appended to all single labels or unqualified zones 
> in order to qualify them.", as such generated names would not be unique nor 
> appear in the global DNS.

More specifically, it seems to assume those names will not resolve in the 
global public DNS, and will not already have a local resolution context, 
without providing any reason for that assumption-- such as an attempt to 
register such names in the special use names registry, or describing what the 
operator is expected to do to avoid possible collisions caused by existing 
local use of names ending in .home (there's widespread evidence of this, 
documented in the discussion of why ICANN isn't delegating it in the first 
place).


Suzanne

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to