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

"John Levine" <johnl@taugh.com> Tue, 02 October 2018 18:56 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA3AE130DC2 for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 11:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWzvA5UyK14x for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 11:56:46 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61911130FF0 for <dnsop@ietf.org>; Tue, 2 Oct 2018 11:56:46 -0700 (PDT)
Received: (qmail 27394 invoked by uid 100); 2 Oct 2018 18:56:45 -0000
Date: 2 Oct 2018 18:56:44 -0000
Message-ID: <pp0f1c$qnn$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Organization: Taughannock Networks
References: <20181001015003.BA0A420062BA6D@ary.qy> <CADyWQ+FoCBGg6Hhzm2o8vhjCyOhdsMzkVSTRNQRaQhPUDNF6Jw@mail.gmail.com> <CADyWQ+FoCBGg6Hhzm2o8vhjCyOhdsMzkVSTRNQRaQhPUDNF6Jw@mail.gmail.com> <9BDDE6A6-7EE8-43A7-AB97-84286E82F3B8@icann.org>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hsX0qmz2Z7ms926ACQ63n1jaIV0>
Subject: Re: [DNSOP] [Ext] Creating a registry for reserved labels.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2018 18:56:48 -0000

In article <9BDDE6A6-7EE8-43A7-AB97-84286E82F3B8@icann.org>rg>,
Paul Hoffman  <paul.hoffman@icann.org> 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.

It seems to me that the most useful purpose for this registry is to
identify names that are resolved using the normal DNS protocol (not
like .local or .onion) but that are treated specially by some
application(s) above the DNS stack. So the 8145 key tag would go in,
as would evertything in _attrleaf, the latter likely by reference.

As to whether it's best or worst practice, I'd stay away from that and
just clarify that the bar for adding new entries is high because of
the risk that they will collide with existing non-special use.

R's,
John
-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly