Hiya,
On 19/12/2023 16:42, Stephen Farrell wrote:
On 19/12/2023 16:34, Sean Turner wrote:FYI the assignments have been made.Great. Can I ask what's the plan for WGLC? Be great if that could be started before the holidays:-)
Good that the IANA registrations are done. Can I ask when will we see the long-overdue WGLC? I would assert that this now almost 5 year old draft is pretty well-baked, having been widely deployed already, and it's time we extract it from of the IETF oven:-) Thanks, S. PS: There is a previously-stated reason to push on this - with some open source libraries, (in particular OpenSSL), having the RFC issued is required before code is merged, and getting ECH code into such libraries is a prerequisite for it getting into some web server applications, so the longer we take with this, the more we encourage centralisation of services and the worse we do with encouraging potential adoption for de-centralised sets of servers. So, how about we get off the pot?
Ta, S.sptOn Dec 12, 2023, at 09:11, Sean Turner <[email protected]> wrote: I should also included a link to the revised PR: https://github.com/tlswg/draft-ietf-tls-esni/pull/597 sptOn Dec 11, 2023, at 22:01, Sean Turner <[email protected]> wrote:I am going to go ahead and forward this. Note that since the “Comments” column isn’t a thing until we get 8447bis through the door the note will follow.sptOn Dec 6, 2023, at 14:46, Sean Turner <[email protected]> wrote: Okay a new proposal the ech_outer_extensions registration: - Set "TLS 1.3" column to “CH”- Include the following note in our new “Comments” column [0]: "Only appears in inner CH."spt [0] PRs: https://github.com/tlswg/rfc8447bis/pull/48 https://github.com/tlswg/rfc8447bis/pull/49On Nov 29, 2023, at 16:09, Stephen Farrell <[email protected]> wrote:Hiya, On 27/11/2023 14:35, Sean Turner wrote:Bumping this up in case anybody missed it.'case it helps, I'm fine with the original mail you sent and any of "n/a" or "CH" being used rather than "-". If it helps, I've a veryminuscule hint of a preference for "CH" so you can count me as agreeingwith MT. But I won't object to any other thing, 'cause I don't think there's a perfect answer, and it matters very little, and defining a new thing like "CHI" just for this seems OTT, but meh, I could even live with that too. I'd also be fine with this just left to chair/editor discretion FWIW. While it's good to bring things like that to the list, I don't think you need to delay based on a small-ish set of responses. Cheers, S.sptOn Nov 21, 2023, at 21:03, Sean Turner <[email protected]> wrote:Hi! I sent over the early allocation request and the IANA folks rightly pointed out two things that need to be added. This email is to make sure we have agreement on the two changes to the registrations in s11.1. If you don’t agree with the values proposed below please let the list know by 1 December 2023.1. The encrypted_client_hello and ech_outer_extensions registrations need to indicate the value for the "DTLS-Only” column. Unless I am mistaken, “N” is the obvious value for both. See https://github.com/tlswg/draft-ietf-tls-esni/pull/5842. The "TLS 1.3” column for ech_outer_extensions registration needs to indicate a value; remember, this column indicates the messages in which the extension may appear. Currently, it’s “”. “N/A" has been suggested, which makes sense to me considering this extension never directly appears in CH, SH, EE, CT, CR, NST, or HRR extensions field. We can’t use “-“ because that means not used in TLS 1.3. “” is used elsewhere in the registry by only for unassigned and reserved values. The following PR change “” to “N/A”: https://github.com/tlswg/draft-ietf-tls-esni/pull/59Cheers, spt_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls<OpenPGP_0xE4D8E9F997A833DD.asc>_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
OpenPGP_0xE4D8E9F997A833DD.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
