On 09/21/2016 11:30 PM, George Michaelson wrote:
> None of these named spaces would "fail" to work as sub-spaces of .ALT
> or .arpa or any other community-led IETF tech community managed label.
>
All of them with a requirement for global uniqueness will fail with
.ALT, per .ALT draft. Etc.
> yo
>Please review the draft and offer relevant comments. Also, if someone
>feels the document is *not* ready for publication, please speak out with
>your reasons.
I think it's ready to publish with one small caveat. In section 5.1,
the text in the box says "resolvers MAY use NSEC/NSEC3 resource
re
On Thursday, September 22, 2016, Tim Wicinski wrote:
> All
>
> This draft has been worked on and it seems that the Working Group is happy
> with the updates that have been made and I feel it's ready for the next
> step.
>
> This starts a Working Group Last Call for:
> "Aggressive use of N
All
This draft has been worked on and it seems that the Working Group is
happy with the updates that have been made and I feel it's ready for the
next step.
This starts a Working Group Last Call for:
"Aggressive use of NSEC/NSEC3"
draft-ietf-dnsop-nsec-aggressiveuse
Current ver
On 09/22/2016 12:31 AM, George Michaelson wrote:
>
> what community burden is taken in the wide, if a new TLD is
> allocated in 6761 to break out of the DNS.
>
I'm sorry but, what do you mean 'to break out of the DNS'?
==
hk
___
DNSOP mailing list
DNSO
