Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-06.txt

Dave Crocker <> Thu, 29 March 2018 15:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9932012711B for <>; Thu, 29 Mar 2018 08:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eXEoTYVb2c8r for <>; Thu, 29 Mar 2018 08:24:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9BBD512D963 for <>; Thu, 29 Mar 2018 08:24:08 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w2TFPYrN016900 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 29 Mar 2018 08:25:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1522337134; bh=pF3WJUj6Dskatx3ckD/6unOv267E91Up6Ees9iBUyj4=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From; b=iA3uKCKuuBrCHJfXueM8flfeF8ACUxRU4czxLShg9y15jM6oC0PJgii1TeB6U0Ne7 lGo1tf8HU/qR10z1Ls48HWbOmY3MwRrsWz5lKqJQHSlaeB2vnTMFIPBzX9mzXYh5xb bEByk/h7REMmbTWKnpfMJokG4+HtQlh1X5UncUXo=
To: Paul Vixie <>
References: <> <>
From: Dave Crocker <>
Organization: Brandenburg InternetWorking
Message-ID: <>
Date: Thu, 29 Mar 2018 08:24:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-06.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Mar 2018 15:24:18 -0000

On 3/28/2018 11:41 AM, Paul Vixie wrote:
> dave, HEREIS. --paul

Cool.  Thanks!

(Sorry for the sloppy vocabulary usage.  By way of an empathy signal cf, 
common use of 'header' in email when it should be 'header field'...)

I've gone through the entire document and reviewed all occurrences RR 
and resource record strings.  The results don't exactly the match the 
set of changes you specify, but did produce quite a few changes.

The RFC 2181 definition resource record set is a set of records of the 
/same/ type.  In some cases, that isn't what's meant, so I didn't change 
the text. In some cases, the text's intent is to to cover RRs of 
/different/ types populating the same leaf.  As I read the definition, 
that's not covered by RRset.

Inline questions/comments/concerns...

> in: 1.1. _Underscore Scoping
> s/specific resource records/specific resource record sets/

Current text:

      "That scope is a leaf node, within which the uses of specific 
resource records can be formally defined and constrained."

I often find that there is wording danger in using plurals, that can be 
avoided with the singular.  I think the issue here can be simplified by 
changing the text to:

      "That scope is a leaf node, within which the uses of a specific 
resource record type can be formally defined and constrained."

> s/[RFC1035]/[RFC952]/ (first occurrence)

hmmm. I suggest listing both, since RFC1035 both cites the precedence of 
RFC952 as well as supplying an (apparently redundant) formal syntax 
specification for host name.

> in: 1.2. Scaling Benefits for TXT, SRV, and URI Resource Records
> s/SRV,//; S/"SRV",//
> OR s/Some resource records are generic and support a variety of uses.//;
>     s/Their use can scale poorly.*different uses\.//;
>     s/increasingly-popular//; s/approach,/approach/

Sorry, not understanding the issue(s). Please clarify.

Here's my guess at the concern:

      SRV is viewed as not generic and/or doesn't have scaling problems?

There is a type of variability to the use of some RR types that 
effectively means they have variation in their role, not just their 
payload.  TXT is the extreme example of this.  SRV is more interesting, 
because it was designed for that variability.  Glad to use a term other 
than generic, but I don't have an obvious alternative that suits.

The variability of such types can make it problematic to aggregate all 
occurrences of them into the same node, even though they are associated 
with that node. The underscore naming approach separates these subsets. 
Again, SRV is interesting because it was designed with that naming as 
part of its original design.  However the fact that it was designed with 
the solution from the start doesn't relieve it of needing that solution. 
  The text, here, is attempting to characterize a motivating issue, 
namely a scaling challenge that occurs due to the variability of use for 
some RR types.

> s/RR/RRset/ (note, leave "RR"s alone)

The substitution command seems to be at odds with the comment.  Please 

> in: 2. DNS Underscore Scoped Entry Registries Function
> /name space/name space, just as every RR type owns a distinct, 
> subordinate name space./

An RR type owns a name space?  I don't understand what that means or how 
it is correct.

Dave Crocker
Brandenburg InternetWorking