> Technically, this I-D has already been through WGLC and this version is to
> address the remaining WGLC. Any objection to progressing this while we debate
> in parallel whether to change the name?
No objection at all.
And my feelings will not be hurt if it stays as-is. :)
___
Technically, this I-D has already been through WGLC and this version is to
address the remaining WGLC. Any objection to progressing this while we debate
in parallel whether to change the name?
spt
> On Aug 20, 2024, at 13:00, Salz, Rich
> wrote:
>
>
> I read the document [1]. I think it's
This draft makes the changes described at IETF 120
Slides:
https://datatracker.ietf.org/meeting/120/materials/slides-120-tls-chipping-flakes-from-tls-12-is-still-frozen-00
Minutes:
https://datatracker.ietf.org/meeting/120/materials/minutes-120-tls-202407242000-00
(search for "frozen")
I ask th
Internet-Draft draft-ietf-tls-tls12-frozen-02.txt is now available. It is a
work item of the Transport Layer Security (TLS) WG of the IETF.
Title: TLS 1.2 is in Feature Freeze
Authors: Rich Salz
Nimrod Aviram
Name:draft-ietf-tls-tls12-frozen-02.txt
Pages: 5
Dates
I read the document [1]. I think it's ready for WGLC. I suggest one change. I
find the use of "bootstrapping" in the title misleading. I suggest "Enabling
TLS Encrypted ClientHello via DNS Service Bindings."
[1] https://datatracker.ietf.org/doc/draft-ietf-tls-svcb-ech/
_
Internet-Draft draft-ietf-tls-svcb-ech-04.txt is now available. It is a work
item of the Transport Layer Security (TLS) WG of the IETF.
Title: Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings
Authors: Ben Schwartz
Mike Bishop
Erik Nygren
Name:
Felix,
I definitely don't understand something here, so I have tried to abstract
things slightly to try to illustrate why I think there might still be an issue.
I'm reasonably (but not completely) confident that I haven't abstracted
away anything significant. Apologies if I've missed something im
