Hi! While drafting the Shepherd write-up, the authors agreed to pause the publication process until implementations arrived. 20204Q1 (maybe earlier) is the expected timeframe for implementations. But, those implemntations need code points. We are at the point where this I-D is stable (it has been through 2 WGLCs). I will kick off an early IANA allocation request for the codes points Section 10 of the I-D in another email thread.
spt > On Oct 17, 2023, at 18:36, Sean Turner <s...@sn3rd.com> wrote: > > As part of my Shepherd review, I noted two changes that needed to be made: > > 1) IANA - we need to explicitly state how to set the DTLS-OK column and a > note that says the rrc content type is helpful. > > 2) Update Header - This document doesn’t really update RFCs 6147 or 91447. > > Both are addressed here: > > https://github.com/tlswg/dtls-rrc/pull/65 > > If you object to these please let me know ASAP! > > Cheers, > spt > >> On Sep 18, 2023, at 17:03, Sean Turner <s...@sn3rd.com> wrote: >> >> This email starts the 2nd working group last call for "Return Routability >> Check for DTLS 1.2 and DTLS 1.3” I-D, located here: >> >> https://datatracker.ietf.org/doc/draft-ietf-tls-dtls-rrc/ >> >> The WG Last Call will end 3 October 2023 @ 2359 UTC. >> >> Please review the I-D and submit issues and pull requests via the GitHub >> repository that can be found at: >> >> https://github.com/tlswg/dtls-rrc >> >> Alternatively, you can also send your comments to tls@ietf.org. >> >> Thanks, >> Chris, Joe, & Sean > _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
