We're simply making no statement either way about DTLS right now. Though PQ
means that DTLS 1.2's reprieve is just temporary. We still need to get to DTLS
1.3 for PQ.
Yes, I expect that once DTLS 1.3bis is done, we will update this and the
tls12-frozen draft to cover DTLS.
What if we added jus
On Wed, Jan 29, 2025 at 9:39 AM Salz, Rich wrote:
>
> > Small correction: BoringSSL has an implementation as of around November.
> Our main DTLS application (WebRTC) is still in the process of integrating
> it, so we may yet find that we messed something up, but in principle it's
> working now.
>
> Small correction: BoringSSL has an implementation as of around November. Our
> main DTLS application (WebRTC) is still in the process of integrating it, so
> we may yet find that we messed something up, but in principle it's working
> now.
Thanks for that update, David. Are people okay with
On Tue, Jan 28, 2025 at 11:48 AM Salz, Rich wrote:
>
>
> First, it keeps stating DTLS is excluded from this draft's recommendations
> but the reasons cited for why this is needed for TLS apply eually to DTLS.
> So why is DTLS excluded from this? If there are valid reasons, I think the
> document
First, it keeps stating DTLS is excluded from this draft's recommendations but
the reasons cited for why this is needed for TLS apply eually to DTLS. So why
is DTLS excluded from this? If there are valid reasons, I think the document
should at least state these.
DTLS is excluded because DTLS 1
