On Mon, Jan 16, 2017 at 8:22 PM, Warren Kumari <war...@kumari.net> wrote:

>
> On Fri, Jan 13, 2017 at 9:47 PM Warren Kumari <war...@kumari.net> wrote:
>
>> ...
>>
>> We have had a proposal, for the ALT TLD, before us for some time now,
>> which we put aside while we worked on the problem statement. As part of
>> assessing solutions, we need to review https://datatracker.ietf.org/
>> doc/draft-ietf-dnsop-alt-tld/ and determine what the WG wants to do with
>> it. Comments to the list, please.
>>
>>
>> Yes please. The document is still parked, but please send me comments *on
>> the draft* and I'll try keep track of them to incorporate. I know that
>> there is much background which can be culled, I'll post a new version to
>> GitHub with that done soon.
>>
>
> ... and I just posted a new version at https://github.com/wkumari/
> draft-wkumari-dnsop-alt-tld
>
> Please take a look and provide any feedback.
> This document has been in limbo for a really long time - I apologize if I
> have forgotten any of the comments -- please resend, or just provide
> pointers to the emails and I'll go reread them.
>
> We *know* that this doesn't solve everyone's issues, but, had it existed,
> it may have provided an option for e.g homenet.alt. Also, we will need to
> decide what to do about the insecure delegation question -- .onion didn't
> need one, but perhaps we do? This will add an interesting wrinkle to the
> whole "coordination with ICANN" discussion.
> >> W
>

In this section:

4.1. Domain Name Reservation Considerations
3. In general, writers of name resolution APIs and libraries do not
       need to perform special handing of these names.  If developers of
       other namespaces implement their namespace through a "shim" or
       library, they will need to intercept and perform their own
       handling.

-- I was hoping that name resolution APIs and libraries would be encouraged
to filter out these names.  So that over time all the major OS versions
would filter them for privacy.  That would greatly reduce the chances of
them reaching DNS if accidentally used on a device that is not expecting
them.

-- 
Bob Harold
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to