Re: [DNSOP] [art] draft-ietf-dnsop-attrleaf

Dave Crocker <> Fri, 04 August 2017 16:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9E8AA1323A3 for <>; Fri, 4 Aug 2017 09:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 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_HELO_PASS=-0.001, 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 jUQDNbalZjxw for <>; Fri, 4 Aug 2017 09:52:51 -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 99BE0132377 for <>; Fri, 4 Aug 2017 09:52:51 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v74GrGKP017809 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 4 Aug 2017 09:53:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1501865597; bh=CpYQx0ebSvRy5u7mUcqKdo2mdDV33183rbUKEs89Es4=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=DgJZA3MDl3coyC7rM+Oven2au6u3gssolpGTykNwQhi23fKWspfAV+yxWVkh6cRD6 UraA3YPRww2cL2TRzSPwq7H3eJqVN02DjBatNCM+x1ok65ZfTQxzRe30j2X3+BH/H7 M7aWEVyheI87zm/Y4ABALMx4mT2/v0Uf1bSSaKAc=
To: Matthew Pounsett <>
Cc: dnsop <>
References: <> <> <> <>
From: Dave Crocker <>
Organization: Brandenburg InternetWorking
Message-ID: <>
Date: Fri, 4 Aug 2017 09:52:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
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] draft-ietf-dnsop-attrleaf
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: Fri, 04 Aug 2017 16:52:52 -0000

On 8/4/2017 9:02 AM, Matthew Pounsett wrote:
> Do I understand correctly that the intent is to obsolete existing 
> underscore registries (whether they be actual IANA registries, or just 
> code points listed in a draft) and move their data to a new, central 
> registry?   This seems sensible to me.

Arguably, there aren't any underscore registries.  There are some specs 
that allocate underscore names, but a 'registery' per se is not 
specified anywhere.  That's the motivation for the current draft.

SRV does registration-by-inheritance, but that overloads one registry 
semantic with another.

So I'll take the liberty of rephrasing what you describe as:

      Obsolete the existing inheritance registrations and create 
explicit registrations for the currently-inherited names in use.


Dave Crocker
Brandenburg InternetWorking