Re: [DNSOP] I-D Action: draft-ietf-dnsop-refuse-any-07.txt

Greetings, refuse-any fans! I updated the document to address our AD's comments. We also fixed the oversight by which Evan was not already an author. There are some brief notes in the change section for anybody who wants more detailed insight. > On 14 Aug 2018, at 15:28, internet-dra...@ietf.or

[DNSOP] I-D Action: draft-ietf-dnsop-refuse-any-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Providing Minimal-Sized Responses to DNS Queries that have QTYPE=ANY Authors : Joe Abley

Re: [DNSOP] [Ext] Tsvart last call review of draft-ietf-dnsop-terminology-bis-12

Thanks for the review! On Aug 13, 2018, at 8:18 PM, Allison Mankin wrote: > > Reviewer: Allison Mankin > Review result: Almost Ready > > Overall Comment - there is a lot of illumination in here, but one overall > point > and a few smaller ones explain why I rated the draft Almost Ready, rather

Re: [DNSOP] [Ext] Re: Last Call: (DNS Terminology) to Best Current Practice

Here we go with a thread on the set of Domain Names being a superset of host names again. ;) On 8/14/18, 09:09, "DNSOP on behalf of Tony Finch" wrote: Viktor Dukhovni wrote: > > Indeed in a non-public network, I'm free to provision a > ".1" TLD, and even create hosts as sub-do

Re: [DNSOP] [Ext] Re: Comments on draft-wessels-dns-zone-digest-02

My reason for replying to this thead is to say that “we have other solutions in place for this, why one more?” On 8/13/18, 16:43, "DNSOP on behalf of Brian Dickson" mailto:dnsop-boun...@ietf.org> on behalf of brian.peter.dick...@gmail.com> wro >While it is

Re: [DNSOP] Last Call: (DNS Terminology) to Best Current Practice

Viktor Dukhovni wrote: > > Indeed in a non-public network, I'm free to provision a > ".1" TLD, and even create hosts as sub-domains of this name: This would break a (non-normative) promise in RFC 1123 However, a valid host name can never have the dot