>This document certainly needs more work particularly when it comes to security >considerations.
Thanks Yaroslav. Do you want to see more details on in the current considerations or is there some aspect that you are missing? Cheers, John From: Yaroslav Rosomakho <[email protected]> Date: Friday, 25 October 2024 at 13:07 To: TLS List <[email protected]> Subject: [TLS] Re: Adoption call for Large Record Sizes for TLS and DTLS This document certainly needs more work particularly when it comes to security considerations. However, it is well thought through and it widens applicability of TLS. I believe it is ready to be adopted as a working group item and I support adoption of this work. -yaroslav On Fri, Oct 25, 2024 at 3:47 AM Sean Turner <[email protected]<mailto:[email protected]>> wrote: At the TLS meeting at IETF 119 we discussed the Large Record Sizes for TLS and DTLS I-D; see [0] and [1]. There has been some list discussion; see [2] and [3]. The I-D has been revised a few times since IETF 119 to incorporate list feedback. This message is to judge consensus on whether there is support to adopt this I-D. If you support adoption and are willing to review and contribute text, please send a message to the list. If you do not support adoption of this draft, please send a message to the list and indicate why. This call will close on November 7, 2024. Thanks, Deirdre, Joe, and Sean [0] https://datatracker.ietf.org/doc/draft-mattsson-tls-super-jumbo-record-limit/ [1] https://datatracker.ietf.org/meeting/119/materials/slides-119-tls-large-record-sizes-for-tls-and-dtls-00 [2] https://mailarchive.ietf.org/arch/msg/tls/ZnGzqIWOkpm_F6zaqAxxtReHpVg/ [3] https://mailarchive.ietf.org/arch/msg/tls/cRH9x6nbLeAnkG-fhOS3ASDA3oU/ _______________________________________________ TLS mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
