Hi List,
a lot of things have already been written.
So I'm not sure, if my e-mail from September last year could be
considered as well.
https://mailarchive.ietf.org/arch/msg/tls/pY6JDDb_WxBfgGbYh15vCS7sQQQ/
It's about, when replacing a "Y" with "N", then put also the period of
the "Y" amended
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 wrote:
>
> Well, we certainly can change it in 8446-bis.
>
> My put here wou
On Fri, Oct 29, 2021 at 4:01 PM Ira McDonald
wrote:
> Hi Eric,
>
> I agree. Let's get the semantics right. You mentioned a 3-tuple w/
> "Discouraged".
> Should that be "Deprecated" (for clarity)?
>
The implied semantics are are:
Recommended: The IETF has consensus this is good (e.g., AES)
No
Hi Eric,
I agree. Let's get the semantics right. You mentioned a 3-tuple w/
"Discouraged".
Should that be "Deprecated" (for clarity)?
On Fri, Oct 29, 2021 at 5:17 PM Eric Rescorla wrote:
> Well, we certainly can change it in 8446-bis.
>
> My put here would be: let's get consensus on the *sem
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
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
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 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 o
* 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 mailin
I am actually not in favor of changing it to IETF Consensus. I think these
have different meanings.
I prefer: Recommended/Not Recommended/Discouraged
On Fri, Oct 29, 2021 at 7:37 AM Salz, Rich wrote:
>
>- I agree that the "Recommended" column in the IANA registry (which is
>frequently
* I agree that the "Recommended" column in the IANA registry (which is
frequently misunderstood)
* should just be renamed to "IETF Consensus". Obvious and self-explanatory.
The way to do that is to get an RFC out that makes that change. It could be
stand-alone, or part of another (lik
, Rich
> Sent: Tuesday, October 26, 2021 3:19 PM
> To: Ilari Liusvaara ; IETF TLS
> Subject: Re: [TLS] TLS Flags and IANA registration policy
>
> The Recommended column is "was this done via IETF consensus." Some of the
> values you think are odd are from pre-1.3, done b
To: Ilari Liusvaara ; IETF TLS
Subject: Re: [TLS] TLS Flags and IANA registration policy
The Recommended column is "was this done via IETF consensus." Some of the
values you think are odd are from pre-1.3, done by consensus, even if the
protocol is now outdated by 1.3
If there
The Recommended column is "was this done via IETF consensus." Some of the
values you think are odd are from pre-1.3, done by consensus, even if the
protocol is now outdated by 1.3
If there are some 1.0 and 1.1 extensions that are not defined in 1.2, then that
deprecation draft should suggest I
On Mon, Oct 25, 2021 at 05:13:07PM +, Hannes Tschofenig wrote:
> Hi Ilari,
>
> > "If an item is not marked as 'Recommended', it does not necessarily
> > mean that it is flawed; rather, it indicates that the item either
> > has not been through the IETF consensus process, has limited
> > applic
Hi Ilari,
> "If an item is not marked as 'Recommended', it does not necessarily mean that
> it is flawed; rather, it indicates that the item either has not been through
> the IETF consensus process, has limited applicability, or is intended only
> for specific use cases."
I think the flags dra
On Sat, Oct 23, 2021 at 08:46:56AM +, Hannes Tschofenig wrote:
> Hi all,
>
> https://datatracker.ietf.org/doc/html/draft-ietf-tls-tlsflags gives
> guidance on registering values in the TLS Flags namespace.
>
> One of the field is the "Recommended" field and it is described as
> follows:
>
>
16 matches
Mail list logo
