[DNSOP] draft-huston-kskroll-sentinel - naming format?

Ray Bellis <ray@bellis.me.uk> Mon, 30 October 2017 16:46 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 139A17D76 for <dnsop@ietfa.amsl.com>; Mon, 30 Oct 2017 09:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id t1rIolvBHVm3 for <dnsop@ietfa.amsl.com>; Mon, 30 Oct 2017 09:46:43 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D55E793A for <dnsop@ietf.org>; Mon, 30 Oct 2017 09:40:42 -0700 (PDT)
Received: from [] (port=51075 helo=rays-mbp.local) by hydrogen.portfast.net ([]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1e9D78-0007UI-9E (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Mon, 30 Oct 2017 16:40:38 +0000
To: dnsop <dnsop@ietf.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <027a469c-5bb6-7940-fd89-55b91dd97275@bellis.me.uk>
Date: Mon, 30 Oct 2017 16:40:40 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eHl3x56qP1IUpWnQi5VhxcUuybQ>
Subject: [DNSOP] draft-huston-kskroll-sentinel - naming format?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 30 Oct 2017 16:46:45 -0000

I see that this draft uses a syntax similar to RFC 8145 Trust Anchor
Telemetry RFC (which uses _ta-<hex_id>) albeit without the leading
underscore, i.e. .ta-<hex_id>.

I'd like to propose instead <hex-id>._ta.<domain>

This would allow _ta to be registered as a standalone entry in the
underscore label registry, whilst also avoid the risk of collisions with
"plain" labels that happen to match ta-<hex>

FWIW, I think in retrospect that RFC 8145 should have taken a similar
approach too.