Re: [TLS] Early code-point assignments for draft-ietf-tls-dtls-connection-id

2019-07-03 Thread Kraus Achim (INST/ECS4)
Great news! Thanks a lot! May be you can spend a couple of words to explain " temporary"? I hope, it's more about the description/entry details than the number. Mit freundlichen Grüßen / Best regards Achim Kraus Engineering Cloud Services 4 Bosch IoT Hub (INST/ECS4) -Ursprüngliche Nach

Re: [TLS] Early code-point assignments for draft-ietf-tls-dtls-connection-id

2019-07-03 Thread Salz, Rich
It means the assignments aren't official until the RFC is published and IANA updates the registry files with that information. From your perspective, there's no difference. On 7/3/19, 7:01 AM, "Kraus Achim (INST/ECS4)" wrote: Great news! Thanks a lot! May be you can spend a coup

Re: [TLS] publishing ESNIKeys under a .well-known URI...

2019-07-03 Thread Stephen Farrell
On 26/06/2019 18:13, Christian Huitema wrote: > I think Stephen's issue will be quite common, especially for small > sites. It doesn't take much to encourage me so I just pushed out that idea in I-D form:-) [1] Comments/PRs etc welcome. > But then, we should ask how often these sites need to

[TLS] AD review of draft-ietf-tls-grease-02

2019-07-03 Thread Benjamin Kaduk
In general this looks to be in good shape, though we do have a remaining TODO item to rebase past the registry changes from RFCs 8446/9447. I see the shepherd writeup says "we hear it is easy to publish RFCs" and note with chagrin that I am not keeping up my end of the bargain. My specific sectio