Re: [DNSOP] [Ext] Creating a registry for reserved labels.

Paul Hoffman <> Tue, 02 October 2018 14:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AF4A1130EC0 for <>; Tue, 2 Oct 2018 07:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kdcAOZGradxa for <>; Tue, 2 Oct 2018 07:27:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CA066130E78 for <>; Tue, 2 Oct 2018 07:27:02 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 2 Oct 2018 07:27:00 -0700
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Tue, 2 Oct 2018 07:27:00 -0700
From: Paul Hoffman <>
To: Tim Wicinski <>
CC: dnsop <>
Thread-Topic: [Ext] [DNSOP] Creating a registry for reserved labels.
Thread-Index: AQHUWlv6LT8oZAi+u0e6/zO+kLWetA==
Date: Tue, 2 Oct 2018 14:26:59 +0000
Message-ID: <>
References: <20181001015003.BA0A420062BA6D@ary.qy> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_82CBACB3-ABF6-4828-8387-0775A977E552"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [DNSOP] [Ext] Creating a registry for reserved labels.
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Oct 2018 14:27:05 -0000

On Oct 2, 2018, at 4:56 AM, Tim Wicinski <> wrote:
> My only concern is that I hope kskrol-sentinel and mta-sts are not held up while we quickly hammer out this labels registry. 

MTA-STS is already an RFC, so there is nothing to hold up. I don't think that the IESG would hold up Sentinel because this registry will have other values from existing RFCs.

> Question:  does 8145 (key tag) fall into this bucket? 

I didn't put it there because the label only applies for query type NULL, but others might disagree and want it in the registry.

> I think Terry's comment should be in any document describing this registry:
>  Therefore, it is important to note that the reservation of the labels in this manner is definitely not considered "best practice".

I cannot disagree more. If Terry wants to write a document telling people what he thinks is the best practice is to creating important protocols like IDNA, that's great. I sincerely doubt he'll get IETF consensus, but he's welcome to try. This document is about the registry.

On Oct 2, 2018, at 7:01 AM, Wessels, Duane <> wrote:

> It feels to me like “this bucket” is not well defined enough at this point to say whether 8145 falls in it, or not.   Shouldn’t the dns-special-labels draft lay out some guidelines for what goes in the registry and what doesn’t?  

Yes. I punted that to the WG.

> And maybe even explain in what ways the registry entries are special, not simply that (someone thinks) they are special?

That too.

--Paul Hoffman