IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Tue, 02 October 2018 19:01 UTC

Return-Path: <johnl@taugh.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 3AB82131226 for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 12:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=NIzf2TU8; dkim=pass (1536-bit key) header.d=taugh.com header.b=my9GKFHz
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 Q8jhcasBBwJD for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 12:01:43 -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 8C6D3131212 for <dnsop@ietf.org>; Tue, 2 Oct 2018 12:01:06 -0700 (PDT)
Received: (qmail 29917 invoked from network); 2 Oct 2018 19:01:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=74d9.5bb3c071.k1810; bh=qMBYVDxZoYQDIsF/AgGQtTti4+HDXYfcbx84wSEDXYA=; b=NIzf2TU8rPz1yfiyS/fz7XySLlCsDpbeneDX90ELHRnARnjLiXB06Fbru6eWo+ONjWjXqryihlTpMwNKK+BagkjpVIg/ZsqwFomux0bbGr1Md5+Na5LTIEX7dN8LoUwMsivLA79yEHPDZx10rOhj/4yUEG8bizj1Xbwp5AuCT3YzzYEf+zc2Xd3O+ft1ZngZYm3psjns8A4DPGPjpFMYkQ4RNu//fTu/nM/wtecHeMHs/ZyYlG8bFsyYGDEiVKb7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=74d9.5bb3c071.k1810; bh=qMBYVDxZoYQDIsF/AgGQtTti4+HDXYfcbx84wSEDXYA=; b=my9GKFHzOdsoXfd9jp3xU9W7oghZeoOAmsHhYBfgmW8UU58Eag8A5b5TG6AKqtFNhdRMRip3Kt4MPGGLNMJ/xaIjgPU8UHYF4J3iIl1w84aomfrBKrgVuiNJYZHd9dK5EgDseltlDoVE+GiXdv8SuS6RvopPxflVdyfwTU7frbj01sn0E7kgS3DW4mJk/QhzOJTZRvWYxKpr2aQlPCkRY9qnLjCYKX/CmSe0HXfQGDUGdDlzqtyhH7goHUZW87ng
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 02 Oct 2018 19:01:05 -0000
Date: Tue, 02 Oct 2018 15:01:04 -0400
Message-ID: <alpine.OSX.2.21.1810021500460.19017@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Joe Abley <jabley@hopcount.ca>
Cc: John Levine <johnl@taugh.com>, dnsop@ietf.org
In-Reply-To: <3D3A626F-6B27-4D42-81F2-276B6024394F@hopcount.ca>
References: <20181001015003.BA0A420062BA6D@ary.qy> <CADyWQ+FoCBGg6Hhzm2o8vhjCyOhdsMzkVSTRNQRaQhPUDNF6Jw@mail.gmail.com> <CADyWQ+FoCBGg6Hhzm2o8vhjCyOhdsMzkVSTRNQRaQhPUDNF6Jw@mail.gmail.com> <9BDDE6A6-7EE8-43A7-AB97-84286E82F3B8@icann.org> <pp0f1c$qnn$1@gal.iecc.com> <3D3A626F-6B27-4D42-81F2-276B6024394F@hopcount.ca>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nSZt-znk4sypT8YhzshXhZEeGP4>
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 19:01:53 -0000

>> 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.
>
> Note also that if the document intends to create a registry, it will need to specify the procedures for change control (i.e. it will need to describe the bar in useful detail, not just clarify that it is high). RFC 8126 contains the authoritative and current guidance for how to do that.

The draft currently says IESG action which seems fine, or maybe require an 
RFC.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email