Re: [DNSOP] HTTPS/SVCB on Cloudflare DNS

Dick Franks <rwfranks@gmail.com> Thu, 23 July 2020 08:40 UTC

Return-Path: <rwfranks@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 951AE3A0A6A for <dnsop@ietfa.amsl.com>; Thu, 23 Jul 2020 01:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 X8IBRov7ZxR5 for <dnsop@ietfa.amsl.com>; Thu, 23 Jul 2020 01:40:50 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 27F433A0A69 for <dnsop@ietf.org>; Thu, 23 Jul 2020 01:40:50 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id v6so5426544iob.4 for <dnsop@ietf.org>; Thu, 23 Jul 2020 01:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zbxPMAF3Q8wC7ek8n0IToFa6TTqVFcE41b0NbU7TQ/E=; b=LCShTVfdgIbLL2XQUIAR/XBuNx5FElLSFJokWbWlQcMRYdNPOJAO9w7q/XLP7DkV01 l6ewEDYTabxIR0wKzf1pAqq4svDzyNl1LBZXQuF4ppk9neWAtWX1U9Bq7RJwxBjTKPxF Y2v7iAGQs+2UTgCxulwg956Ytu32qEItaW+pBvU+aRc8uacIBRE1IAKVVuwHaXdY1tx6 cFnpzw6uEbuXo6lK6A0psL9N2j8Hw26UZPG4WncyRbt0Gd8KvhyhtcvZg69CZgURmi7/ v/14BTJsT8Blwe9j0JKnjSpbZQsQ1UL2eW+fQ1bOEMx3hlZFNsbAQNfkN3hqZyoil221 AoVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zbxPMAF3Q8wC7ek8n0IToFa6TTqVFcE41b0NbU7TQ/E=; b=R5U3abaUXdacA/r1PrPdLwmmlR/Du2/VwjV3/qTFFTuck61XUu8YXOFb6GXJ3er2SQ NvHD9S4FrDn66PIJAxbtXAx2OCt0YelAvld5st1cjfrb9ANkR26cbFDX2zJ20Sh2h0Zt lBi2XImuvRivnszvt4sAiq/naCi6VzzBtH4RYHq9rdiFIFXNl0+qR47iUgF/lT3pydPt +b5Y1hxk74fTMB2D+4/iJRzRJNAYIJZTvo5E5pmeoavRyLxv9Cv8L7E5YERUVkE+qqlU W7u4dXrj23vwJ0wIMCA2UD0gBH9NgGGu41kIzPY/g6aocpFeXrQqQOMDRIDeeBFo86lt 54Ew==
X-Gm-Message-State: AOAM533F/GkocUXs10mQzk+2HDdZmdj6TmdSH4JGh/E6Bk603LKawRUn g+bfaFPEPRfAhCCuqd4SG7RoEQ+81p2j4Fqh8VQ=
X-Google-Smtp-Source: ABdhPJyYODwf5Cwk4YIZiS0rx/mR0uPZ1JIE+/H32TrrL4nDAp2Og+YN8Lkpdf1dBOl6jVfs5h+GNJbnKtJTQpyu1bs=
X-Received: by 2002:a05:6602:2555:: with SMTP id j21mr3824998ioe.11.1595493649038; Thu, 23 Jul 2020 01:40:49 -0700 (PDT)
MIME-Version: 1.0
References: <20200716151356.GA60024@wakko.flat11.house> <9975DA88-525A-4FC3-9517-70E128A4776D@akamai.com> <099D8D6A-FBBD-4A5A-B1A9-C67CF83DD3DF@apple.com> <E5679D36-1C01-4534-BDFA-836B1FD5A33D@akamai.com> <CAHbrMsDWwahCWoDtQRHQOb5ThGZHuVaOU+e3zkd=H-CZF1s3wg@mail.gmail.com> <e82c0023-478a-4507-10dc-4f2c6deb68ba@nic.cz> <1398296D-D020-4652-8BA9-27C16D378578@isc.org>
In-Reply-To: <1398296D-D020-4652-8BA9-27C16D378578@isc.org>
From: Dick Franks <rwfranks@gmail.com>
Date: Thu, 23 Jul 2020 09:40:12 +0100
Message-ID: <CAKW6Ri5vEp1tShjMJfF0rptcum3gqSEey6eky6mQ8yDz7wKXmA@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Petr Špaček <petr.spacek@nic.cz>, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031448305ab17d06b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/MmeYjz08q3DLlzYnXhJCbmww9_E>
Subject: Re: [DNSOP] HTTPS/SVCB on Cloudflare DNS
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: Thu, 23 Jul 2020 08:40:52 -0000

On Thu, 23 Jul 2020 at 08:33, Mark Andrews <marka@isc.org> wrote:

> On 23 Jul 2020, at 16:51, Petr Špaček <petr.spacek@nic.cz> wrote:
>
 >8

>
> > I'm not native English speaker and I personally find confusing that
> sequence of characters "mandatory" is used as verb and also as name of the
> key. "optional mandatory" sounds like a joke.
>
s/verb/adjective/

>
> > To clarify this I propose to rename "mandatory" field to "critical",
> which terminologically aligns with X.509 and also LDAP.
>
> Please don’t change field names.  Master files are interchange documents
> (see STD13) and the presentation format is theoretically fixed when the
> type code is allocated.
>

+1

Apart from "mandatory" itself, which cannot avoid being mandatory, what
distinguishes an "automatically mandatory" key from any other optional key
not listed in key0?

If there is no distinction, why persist with this "automatically mandatory"
nonsense.


--Dick




> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>