IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Tue, 02 October 2018 18:59 UTC

Return-Path: <jabley@hopcount.ca>
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 EBEEC130FF0 for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 11:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 40VWwvTCmghe for <dnsop@ietfa.amsl.com>; Tue, 2 Oct 2018 11:59:35 -0700 (PDT)
Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61ED8130DC2 for <dnsop@ietf.org>; Tue, 2 Oct 2018 11:59:35 -0700 (PDT)
Received: by mail-it1-x12c.google.com with SMTP id i191-v6so5214470iti.5 for <dnsop@ietf.org>; Tue, 02 Oct 2018 11:59:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6hT5rG6oI/kfn3XOMBKklAoblg7U7y/jGsXh/TwF1i4=; b=euN0/OBX6YcE9ZIU2ivQ7WDsTK95a07aeCYtJeEJ2LLU9dnMQQRs8XEMqVBoSTp2mo 4py1i5puJ3rduxbHjDBVwg57G9Z+u+RIkrvFlI5FUwSofVfH0byuaSW46m0ykI7QS+On qEnCHGZGYojhuoahApwZZHMZ4//RqEBkIlbxk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6hT5rG6oI/kfn3XOMBKklAoblg7U7y/jGsXh/TwF1i4=; b=bnEneg66t1ra1Z7D+mcW1KG83dS78HU7FDuyLML7S2joI1GbJXZdD8jLx1KKHYIz65 7UnGHIhGsxLYTL8ucTQxFa5hm5CZbm2T6H87A5M2AQ/K/V+Y/YOtCYxCRxtuuWPTs/hD sSigd8vkOQPKG4QPGqEgQENTNdMb7d6XjfPFyK4BOhTcKT/vFhdWYJK3zqRzyfCYvgok qWNfu4ym7RVz42vl1bIeSNUp/9yurQ+EPk9Vr9BqBnlp9nLFEBkIRNi3rYZcbIBs1G6u 4k3VwYpdGVg6l0EZsdkqFvhLdE8vc9Tp8jczJVlaKf0EnsSKNhljPL3hCyHZeSAsY1IK gHFQ==
X-Gm-Message-State: ABuFfogt3cVDYWZCCRMLJPBs8Runt/NC07tButgjqOxnfzPIXCK5enQ1 OqZYFGZkrrRHqED5A04MWPwlY9WEkVE=
X-Google-Smtp-Source: ACcGV60F2dL2Ns/fbnH+bcDI1V0c+Cu5qnUIDRn1aYk6ucpnJ+JzOkIUR2fShD0hYW9xsHqCjaVI7g==
X-Received: by 2002:a24:2751:: with SMTP id g78-v6mr2905227ita.17.1538506774528; Tue, 02 Oct 2018 11:59:34 -0700 (PDT)
Received: from node-131dv60dhzv243951g.ipv6.teksavvy.com (node-131dv60dhzv243951g.ipv6.teksavvy.com. [2607:f2c0:101:3:d001:a814:4c3c:d4c4]) by smtp.gmail.com with ESMTPSA id i5-v6sm5618007ioq.5.2018.10.02.11.59.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Oct 2018 11:59:33 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <pp0f1c$qnn$1@gal.iecc.com>
Date: Tue, 02 Oct 2018 14:59:32 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kt5JI7_-rHu-TRovArAf0WthW4E>
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:59:37 -0000

On 2 Oct 2018, at 14:56, John Levine <johnl@taugh.com> wrote:

> 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.


Joe

v2.23.0 | Report a Bug | By Email