Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt

Dave Crocker <> Wed, 21 March 2018 18:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A8B8912E050; Wed, 21 Mar 2018 11:17:35 -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 6jgGYqaJI9xD; Wed, 21 Mar 2018 11:17:34 -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 38B8C12762F; Wed, 21 Mar 2018 11:17:34 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w2LIIqxN000814 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 11:18:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1521656332; bh=0KFisZR4HZoTZBZ8+y1BBOkqFwTzZlxIdfEhmKKfHBY=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=VaKe1/3ZOK/+0sr1tx5LR6cxpO0ilL2/ANDf6BdycUPBu4Vmbhmw8vMl3uJEy/jtt cFFcqv8WZl7kjcDhn5f4NmlWYmklHQK3Ae/0vj9O7h+GnYt7iUWYD79U252JQ2GnCr gZO2MEZlQkXhDn6akmuUSV18Ey86x/LeR6GR68xI=
To: Paul Vixie <>
Cc: "John R. Levine" <>,,
References: <> <> <> <> <> <alpine.OSX.2.21.1803211104210.9553@ary.local> <> <>
From: Dave Crocker <>
Organization: Brandenburg InternetWorking
Message-ID: <>
Date: Wed, 21 Mar 2018 11:17:24 -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: 7bit
Archived-At: <>
Subject: Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.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: Wed, 21 Mar 2018 18:17:35 -0000

On 3/21/2018 8:03 AM, Paul Vixie wrote:
> dave, i wasn't going to reply at all, since your snark is a turn-off. 

Snark?  You think my note was "crotchety, snappish; sarcastic, 
impertinent, or irreverent"?  It wasn't any of those things, though 
perhaps it's interesting you thought it was.  But only perhaps.

Your note made no obvious sense to me, since it began with what is 
really a platitude (that I really do agree with) and ended with a 
generality that had no obvious linkage to the current work.

> however, john decided to make this thing real, so now i'm stuck with it.
> srv has a registry. that's working. that need not change.
> adding another registry for other rr types who want to have well known 
> underscored names will harm nobody and i'm unopposed.

Much of the discussion of the current topic -- previously and now -- has 
tended to stray from the pragmatics, whereas that is the only thinking 
driving my concerns and suggestions.  In particular, some people seem to 
have a mystical -- or equally impractical -- view of how name collisions 
will be avoided between independent registries making assignments out of 
the same name space.

I prefer to take as simple an approach as possible: have a single 
registry control all allocations out of a name space.

So if you will please explain:

   1.  How the SRV underscore registration process and the new 
registration process will avoid collisions

   2.  How people revising existing specs that use _underscore naming 
will know that their document needs to use the new registry

it would be helpful.


Dave Crocker
Brandenburg InternetWorking