IETF Logo Mail Archive

Re: [TLS] TLS Flags and IANA registration policy

Sean Turner <sean@sn3rd.com> Sat, 30 October 2021 02:47 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFB63A1A9A for <tls@ietfa.amsl.com>; Fri, 29 Oct 2021 19:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=sn3rd.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 aESHyaLKXbWa for <tls@ietfa.amsl.com>; Fri, 29 Oct 2021 19:47:47 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 6CF7C3A1A95 for <tls@ietf.org>; Fri, 29 Oct 2021 19:47:47 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id g17so10930401qtk.8 for <tls@ietf.org>; Fri, 29 Oct 2021 19:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ovNLePDNLC4oDPTYe+vvoZW1iKOSosspTn8z/Jl3+lI=; b=GmTVupstGvy0YS126fUuGGqzIHi93sj3ba42pWMXBT2AS+G8k2boNyYjgaFONkAtsv L00PpgEbsxSl+Pz3kWkhFdty8L/LkKNgIKpkZT8+hP09q+0TBrnZAib/KupufCni1MSG EgzJxrJTvWVs9e9uuj4gYnhKpEU36FmLeHhHU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ovNLePDNLC4oDPTYe+vvoZW1iKOSosspTn8z/Jl3+lI=; b=M6ZbOd9zeK8mbfh9Bk4nWjc3DuANjXC8TpdhL3TZUUdhoBtauTxyBJsdlltWWhyrt5 wTI3eQkdtENkaiXJJUIkWljWs1OYZipNSsVv1g2DrOY/P4Frcl11gVnMU8aOtainDLhr jemodvzq0/9vMmlNLGiXd2OlbVljQgTxC7YG7rzYI+SC/m8D0Qf8le/RZZJJ7SanhTA9 2FikD68C4qJTOsm1zEfH7kzyDrvUbGXHHIJ2u97uiI2fc+R+I6N+75rEJBzqpG5d6YEe YFUDHeZJg1+2b/7g1pDqrvzV77uBiQbJo4vNY0RnVX5WhrLesoyFu0lzo8djF6sx2Kvy FkJw==
X-Gm-Message-State: AOAM531pup3wqw43c1RAGF4CEdSgeqSr41RTt/rArvMMbKVB8WpHmCeI XZzGLJPgyjzOluzrwZZgA44xFA==
X-Google-Smtp-Source: ABdhPJyotSi7hYqH100r3g64XkNuPpF81Op4n2zBC5OH8ne/7SadLgSTdxatZhdtaXhR58tAHcQaEg==
X-Received: by 2002:a05:622a:94:: with SMTP id o20mr16133161qtw.169.1635562065884; Fri, 29 Oct 2021 19:47:45 -0700 (PDT)
Received: from smtpclient.apple (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id b18sm4861083qkh.85.2021.10.29.19.47.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Oct 2021 19:47:45 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CABcZeBMY1Z_CmPNatJA5kca1d4jvfg7GquK3+b+fdfwBxS2suA@mail.gmail.com>
Date: Fri, 29 Oct 2021 22:47:44 -0400
Cc: Ira McDonald <blueroofmusic@gmail.com>, TLS List <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC121E09-92D9-477D-B8F2-511D5179B46B@sn3rd.com>
References: <DBBPR08MB59153B444624CEA8EC6E9A66FA819@DBBPR08MB5915.eurprd08.prod.outlook.com> <YXPSz6Uw9CDgl7tX@LK-Perkele-VII2.locald> <DBBPR08MB59157A0F39745E84309DDD8DFA839@DBBPR08MB5915.eurprd08.prod.outlook.com> <YXb02ETjp3dbFrXh@LK-Perkele-VII2.locald> <6DC9931F-7CEC-4DD3-87BC-EEA93A7B9646@akamai.com> <DBBPR08MB591549A109FC15BE09C22C73FA849@DBBPR08MB5915.eurprd08.prod.outlook.com> <CAN40gSvYVSi6A7PVOiqmCxqwa2x3Y9ppowvXR9L46TJ1jmE=WQ@mail.gmail.com> <EADE1F53-1A25-4483-9D42-ADC71D935CBB@akamai.com> <CABcZeBMgW-rbooFPX6psv+jKeHLKuUEqtThA4inR3jiXTLt1qA@mail.gmail.com> <81AEBCC0-4704-4ED0-8A49-B3DC5842C005@akamai.com> <CABcZeBM39bQ3SwCD+NnewLnXd+wo-J+mMr5McsO2i4y922Eqbw@mail.gmail.com> <CAN40gSvu=1wWoYD3p9ygmDP0w13-yuH0SdeOR2mN8UScnuZw7w@mail.gmail.com> <CABcZeBMY1Z_CmPNatJA5kca1d4jvfg7GquK3+b+fdfwBxS2suA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/d1dUgT1l4OpiJVOP2HPVQU3T5CA>
Subject: Re: [TLS] TLS Flags and IANA registration policy
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2021 02:47:53 -0000

I actually think we’re going to try to do this 8447bis:
https://github.com/tls-stuff/rfc8447bis
We need to get it adopted, but that’s on tap for this IETF (or should be).

spt

> On Oct 29, 2021, at 17:16, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> Well, we certainly can change it in 8446-bis.
> 
> My put here would be: let's get consensus on the *semantics* we want for the various categories without worrying about the names (call them A, B, C, etc.) and then we can name them after.
> 
> -Ekr
> 
> 
> On Fri, Oct 29, 2021 at 2:14 PM Ira McDonald <blueroofmusic@gmail.com> wrote:
> Hi Eric,
> 
> Thanks for the background.  I still sympathize with Hannes' point that
> "Recommended" means "IETF Consensus".  I have to explain this
> too often in the insular automotive industry.
> 
> But I certainly wouldn't write an RFC to change the title of a single
> column in an IANA registry.  I've been one of the Designated Experts
> for the IANA Internet Printing Protocol (IPP) registry for 20 years and
> we rename IANA fields as needed by a direct request to our IANA
> folks (after consensus in the IEEE-ISTO Printer Working Group IPP
> WG - successor to IETF IPP WG in the 1990s).
> 
> Cheers,
> - Ira
> 
> 
> On Fri, Oct 29, 2021 at 3:18 PM Eric Rescorla <ekr@rtfm.com> wrote:
> Previous discussion is on this issue: https://github.com/tlswg/tls13-spec/issues/1214
> 
> On Fri, Oct 29, 2021 at 12:13 PM Salz, Rich <rsalz@akamai.com> wrote:
> 	• I am actually not in favor of changing it to IETF Consensus. I think these have different meanings.
>  
> 
> To be clear, I wasn’t expressing an opinion on whether or not to do this, I was just showing folks how to start the change process.
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls

v2.39.1 | Report a Bug | By Email | System Status