Hiya,
Interesting question... On 11/01/2024 00:07, Christian Huitema wrote:
I am wondering what the proper fix should be.
I don't know the answer (or if there's one answer) but suspect that it may be better to first explore various scenarios (as you've kinda kicked off with forwarding to the deepspace list) and then come back to TLS implementers with an ask based on some of those. I also suspect that one'd need to use some kind of callback that e.g. can query ephemeris data, as a number of scenarios would involve RTTs that vary significantly over time, but adding such callbacks to implementations could be dangerous in more typical Internet environments. Lastly, I'd guess that replay of early_data for applications in some deepspace scenarios would be so dangerous that one'd be better to not use early_data but rather to export a key and then use that with an application that itself knows how to handle replayed data. So maybe exploring ways to use key exporters is also something to consider, rather than using early_data. (For cases where new deepspace applications are developed that want to use TLS.) Cheers, S.
OpenPGP_0xE4D8E9F997A833DD.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
