IETF Logo Mail Archive

Re: [DNSOP] [IANA #1362913] expert review for draft-ietf-dnsop-dnssec-bootstrapping (dns-parameters)

John Levine <johnl@taugh.com> Sat, 13 April 2024 02:17 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 336B4C14F69C for <dnsop@ietfa.amsl.com>; Fri, 12 Apr 2024 19:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.149
X-Spam-Level:
X-Spam-Status: No, score=-4.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="DwgKWcKp"; dkim=pass (2048-bit key) header.d=taugh.com header.b="YpeFYUel"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqqfrIXaiCPA for <dnsop@ietfa.amsl.com>; Fri, 12 Apr 2024 19:17:21 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE38C14F68A for <dnsop@ietf.org>; Fri, 12 Apr 2024 19:17:20 -0700 (PDT)
Received: (qmail 55143 invoked from network); 13 Apr 2024 02:17:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d7656619eb2f.k2404; bh=77FRN3AayVXRjFIQV7f+dHlbBeZFxg/z1HGJgRT/ffc=; b=DwgKWcKp4Xe0XZw5i1cUJji7md23WjRWisCsegs5GYcC16Ng9Jj7IHvNtcIjAaTxCxiF41tBHY6eq1rl89dfjoDtY9c2ifjwl8dKpA93C20xu2/pcAuSh4vvd0wWR0GC33LfLlP2I+jzcJhP5x/bIi9zw6lTDuNNEe5UUHAB6CQK/GeAzoXbvX3IWGxBxeDewza72ljqyeNf0SHiD0ySdVn8F/qpQFXZf82T4bw+E9ks+Q0W0F07IEfc9T3qit+EdYn5FP4bj2Ouj6nZ3dBHPcmSM9afk7EnpgGhb69UzLxqb5LkoHjwaiaMP65bMqiBie3dNMEW+NETJiEAJcEguQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d7656619eb2f.k2404; bh=77FRN3AayVXRjFIQV7f+dHlbBeZFxg/z1HGJgRT/ffc=; b=YpeFYUelthOuISkpBoKTloPLRm1cSLt5CD26yaZexVOgKxfjY9Dv1whvr8LtGz26Z6ac4yv5hBpj6bc+uxKk/6gyk8ldU/lF4gf48CWBE7T1RTGP0CtSOJPkFnRL6R3idtLjVSHQOXY9BkcroPUj/o3HHC/xcrT5+VOaB27jV8qupGih/YQ3ccyziSQyI/vt+NfQuFbqHddeVXi+CndWqTVtQyP72Ut9bExV5pT600fYxi+QWKS9RNDr6NNgRsbROSa9di6+uvty2DHH+Flrc+3bRjcDIkcooy0ufKQtkEKOSFNV70ztYkB3V9Ot0360k2GN0Sof7qcRV8r4GVp6VQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 13 Apr 2024 02:17:19 -0000
Received: by ary.qy (Postfix, from userid 501) id DA3E18856E13; Fri, 12 Apr 2024 22:17:17 -0400 (EDT)
Date: Fri, 12 Apr 2024 22:17:17 -0400
Message-Id: <20240413021718.DA3E18856E13@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: peter@desec.io
In-Reply-To: <68dc75b3-afa3-4c46-9ddd-5440e9b85446@desec.io>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mPoiSyNEJ1Wg5X_UGrng_14LPrw>
Subject: Re: [DNSOP] [IANA #1362913] expert review for draft-ietf-dnsop-dnssec-bootstrapping (dns-parameters)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 13 Apr 2024 02:17:26 -0000

It appears that Peter Thomassen  <peter@desec.io> said:
>The _signal label generically indicates that ns2.foobar.fi likes to signal something about nohats.ca. Its presence is needed to allow separating the object from the source without ambiguity.
>
>We could change _signal to something else, but not to _dnssec-bootstrap as that's not generic. Suggestions are welcome.

They're all DNSSEC related so how about _dnssec-signal ?

>I'd like to add some considerations:
>
>- The spec has quite a few production implementations (see Section 8), and changing them would come with significant costs.
>
>- I don't think the _signal label is in use for the Signal messenger. Even in case it's used in the future, a collision (in terms of prefix labels + rdtype) seems unlikely.

It's not but _signal is an awfully generic term, and I do not want to
count on people inventing sufficiently distinct second level _label
names to keep unrelated uses separate.

When we were collecting names for the _label registry there were a
few places with overlapping names like the URI RRTYPE, and it's
a mess.  Let's not do it again.

R's,
John

v2.23.0 | Report a Bug | By Email