Re: [DNSOP] IANA Policy for SVCB

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 22 March 2022 16:01 UTC

Return-Path: <superuser@gmail.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 EECC53A003C for <dnsop@ietfa.amsl.com>; Tue, 22 Mar 2022 09:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4SymIVi4Pbyi for <dnsop@ietfa.amsl.com>; Tue, 22 Mar 2022 09:01:27 -0700 (PDT)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (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 6BFBF3A005F for <dnsop@ietf.org>; Tue, 22 Mar 2022 09:01:27 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id 2so11581347vse.4 for <dnsop@ietf.org>; Tue, 22 Mar 2022 09:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EqiHDj+OMGjpc+Uk9kR6w9mfhEEVAMfcZu9ijvA8euU=; b=CkYUi6vJHjOw/AOskjwM1+eMvu1SRgHQ/2wem/M4mH1mp8EptwYU8P/+VLXRmgGbCC 2EneF5010I0DXkCnYbxxW/5Krdn162yTofVtRZDMfTxdwVyplg+pacWeyWAGK7FHBkEo 3GDMt3s6Z3/YwRr5TRJ5uJZ3a3tjy7sLoC2tG1Q/CuHfp2OZ+ZO4n1ZJsLJclaSyV1qb jnDg+lF0NdN5oPnMnAubkt42mvBDeMkh4RsoHnplf0i6kjocFd9oLAjiG6ELMWgJkFlO VZFkFzNtDm0xxPfyqNAKeDQLNB/OinbExihRyYXYeAGHt9lo2CRqp7K88CzdOMB2NlY4 64Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EqiHDj+OMGjpc+Uk9kR6w9mfhEEVAMfcZu9ijvA8euU=; b=tX8lOA1HuPHIEkHWVtALnNbK3nklSUOid+FQYKIN/sT19+oIp/K897pR/NzADkuxHf B8+TfQQnNi7NMBE7wVMvQHrGh3TXdwFsm1X8aHFp0WspVl2LOsq6h4hIpiew/GsCpY7x EU3VGizwJmnDuQ1Mxl3paoTxpdNsO3m4egw4II9xsk8Q+6q8n3ehfN3V6qWcxUdnyUPj p7ACFqbSJwzcJmYTvVe0OTIsvueFhukpvHjHneP7D9WYXUy1GAQsojwTeziGPdtLwiMn nd25gkxHzzzsKqfb3gCY5QuZKbEBRusW2ginGvOj6/dYuoCSIYn2mfvmDMJLTc5Qh+dc mbjg==
X-Gm-Message-State: AOAM530IUzY+zjU4wVl5eXJ29ARyF6UKoP4oLdsbT8sAp/Lsb2/QW5h0 L4EZwavk7GCobhAjiuOwJ9fdI8++po8TvcTsUMQ2VXcl
X-Google-Smtp-Source: ABdhPJwAu1Xz4N1JFI0e7QdPknzartXv9FzEuT+0pK+R62sdpeHVZ6DesWvacf2/U7b/LjDskE7U9ol2cckKiQfPMQs=
X-Received: by 2002:a67:c912:0:b0:325:456b:4cdd with SMTP id w18-20020a67c912000000b00325456b4cddmr336299vsk.66.1647964885937; Tue, 22 Mar 2022 09:01:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAHbrMsB5Lhm+cUoEzXwwKn74pBCrAOB+wnJG8ATscxkh7zSvLQ@mail.gmail.com> <CAL0qLwY11Z32q2+Co1Gsn=t7mgZOT6gfx6saXuNQTJ8nhK4nvg@mail.gmail.com> <66256ce9-bb9f-4534-87ff-c589566db395@www.fastmail.com>
In-Reply-To: <66256ce9-bb9f-4534-87ff-c589566db395@www.fastmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 22 Mar 2022 09:01:14 -0700
Message-ID: <CAL0qLwaXuXA9SC4vv8wJ025mSwgq0ontC7ACVFo_APE-fWbN-Q@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a0f57805dad0b9ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EF6FXuvAQKzY97IG7EpI8zKsAYg>
Subject: Re: [DNSOP] IANA Policy for SVCB
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, 22 Mar 2022 16:01:33 -0000

On Tue, Mar 22, 2022 at 8:48 AM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Mar 23, 2022, at 02:45, Murray S. Kucherawy wrote:
> > On Mon, Mar 21, 2022 at 2:20 AM Ben Schwartz
> > <bemasc=40google.com@dmarc.ietf.org> wrote:
> >> [...] any individual I-D is considered a qualified specification as
> soon as it is uploaded to the Datatracker.
> >
> > Do you have a reference that asserts this?  An I-D that isn't published
> > will expire, which would appear to contradict "permanent and readily
> > available".
>
> There is precedent (TLS docs), but I don't know if there is a reference.
>

Interesting.

In my role as a media type reviewer, for example, it's unlikely I'd accept
an I-D as a stable reference in a registration request except maybe for a
provisional registration.  I could be wrong, but my understanding of the
intent of "Specification Required" is roughly "permanently published,
though not necessarily by the IETF", so I think the bar is a little higher
than just the existence of an I-D.

As to the options proposed, I agree that Expert Review can introduce delay,
but given the above, so too can Specification Required (maybe worse, in
aggregate).  So I recommend Expert Review.

Finally, I just realized my DISCUSS on this document about the IANA
Considerations is redundant to Ben's, so I'm going to go clear it and just
support Ben's.

-MSK