TLS Encrypted Client Hello (formerly ESNI) Enters Draft Status

Re:TLS Encrypted Client Hello (formerly ESNI) Enters Draft S... by brongondwana on Monday June 15, 2020 @01:05AM (#23523958)

The complaint is more "the title of this link does not reflect anything about how the IETF works or the status of this particular revision of the draft rather".

If you're expecting to get any value from this hacker news story, you need to understand enough of how the IETF works to know what meaning this particular draft has as opposed to any of the previous 6 revisions.

[ Parent | on HN ]

Re:TLS Encrypted Client Hello (formerly ESNI) Enters Draft S... by tialaramex on Monday June 15, 2020 @12:24PM (#23529127)

> the previous 6 revisions

Seven, or, depending on how you squint, eight :D

Draft numbering starts from zero: https://tools.ietf.org/html/draft-ietf-tls-esni-00

And also the number resets if (as happened in this case) a draft is adopted by a Working Group and acquires that "ietf" in place of an author's name, so the predecessor to that zero zero draft was ekr's draft-rescorla-tls-esni-00.

[ Parent | on HN ]

Re:TLS Encrypted Client Hello (formerly ESNI) Enters Draft S... by brongondwana on Monday June 15, 2020 @05:05PM (#23532963)

Well.... yeah. If I wanted to be a smartass I would be saying something like "the 00 when it got adopted into the working group is important" though, unlike random changes before wglc.

[ Parent | on HN ]

Re:TLS Encrypted Client Hello (formerly ESNI) Enters Draft S... by loyukfai on Monday June 15, 2020 @06:34AM (#23525866)

Many thanks for the info and sorry for the confusion.

[ Parent | on HN ]