Re: [TLS] TLS Flags and IANA registration policy

Eric Rescorla <ekr@rtfm.com> Fri, 29 October 2021 21:17 UTC

MIME-Version: 1.0
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>
In-Reply-To: <CAN40gSvu=1wWoYD3p9ygmDP0w13-yuH0SdeOR2mN8UScnuZw7w@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 29 Oct 2021 14:16:59 -0700
Message-ID: <CABcZeBMY1Z_CmPNatJA5kca1d4jvfg7GquK3+b+fdfwBxS2suA@mail.gmail.com>
To: Ira McDonald <blueroofmusic@gmail.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, IETF TLS <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000297cfb05cf845bc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/RRpIeROQD6ODcVdd9DXp02OGjII>
Subject: Re: [TLS] TLS Flags and IANA registration policy
Precedence: list

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] TLS Flags and IANA registration policy Hannes Tschofenig
Re: [TLS] TLS Flags and IANA registration policy Ilari Liusvaara
Re: [TLS] TLS Flags and IANA registration policy Hannes Tschofenig
Re: [TLS] TLS Flags and IANA registration policy Ilari Liusvaara
Re: [TLS] TLS Flags and IANA registration policy Salz, Rich
Re: [TLS] TLS Flags and IANA registration policy Hannes Tschofenig
Re: [TLS] TLS Flags and IANA registration policy Ira McDonald
Re: [TLS] TLS Flags and IANA registration policy Salz, Rich
Re: [TLS] TLS Flags and IANA registration policy Eric Rescorla
Re: [TLS] TLS Flags and IANA registration policy Salz, Rich
Re: [TLS] TLS Flags and IANA registration policy Eric Rescorla
Re: [TLS] TLS Flags and IANA registration policy Ira McDonald
Re: [TLS] TLS Flags and IANA registration policy Eric Rescorla
Re: [TLS] TLS Flags and IANA registration policy Ira McDonald
Re: [TLS] TLS Flags and IANA registration policy Eric Rescorla
Re: [TLS] TLS Flags and IANA registration policy Sean Turner
Re: [TLS] TLS Flags and IANA registration policy Achim Kraus