Re: [DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-00.txt

2015-03-22 Thread John Levine
>To begin with, in general I think this document is on the right path >and something very close to it should be published. It's >narrowly-focussed, Agreed. Let's do these special case TLDLTs (top level domain like things) one at a time unless there's a group with identical technical and usage i

Re: [DNSOP] [dns-operations] dnsop-any-notimp violates the DNS standards

2015-03-22 Thread Florian Weimer
* Olafur Gudmundsson: >> On Mar 18, 2015, at 11:55 AM, Paul Vixie wrote: >> >> we need a document that says "If you don't want to answer ANY, >> here's how to do it interoperably." we don't need to say "you >> should not answer ANY", but we do need to say "if you want to query >> for ANY, here's

Re: [DNSOP] remarks on draft-ietf-dnsop-5966bis-01

2015-03-22 Thread Florian Weimer
* Paul Vixie: >> As a counterexample, RFC 6891 requires FORMERR responses without OPT >> RRs from implementations which do not support EDNS: >> >>Responders that choose not to implement the protocol extensions >>defined in this document MUST respond with a return code (RCODE) of >>FORM

Re: [DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-00.txt

2015-03-22 Thread Warren Kumari
On Sat, Mar 21, 2015 at 6:12 PM, Andrew Sullivan wrote: > Dear colleagues, > > On Mon, Mar 16, 2015 at 10:16:37PM +, Jacob Appelbaum wrote: > >> I realized after uploading that I hadn't sent this along for discussion. > >> > Name: draft-appelbaum-dnsop-onion-tld > > I've read th