I would like to see examples of these use cases where using QUIC is
impossible, but using TurboTLS is.
Best,
Bas
On Wed, Nov 15, 2023 at 6:37 PM David Joseph wrote:
> Hi everyone,
>
> We wanted to speak about this draft on *TurboTLS* at 118 but didn't
> manage to squeeze into the packed sessi
>I would like to see examples of these use cases where using QUIC is
>impossible, but using >TurboTLS is.
+1
QUIC is the obvious future replacement for TCP, (D)TLS, SCTP, and RTP. I think
IETF should focus on QUIC. I think people staying on TLS/TCP need to live with
an extra roundtrip. Visibil
Bumping this up in case anybody missed it.
spt
> On Nov 21, 2023, at 21:03, Sean Turner wrote:
>
> Hi! I sent over the early allocation request and the IANA folks rightly
> pointed out two things that need to be added. This email is to make sure we
> have agreement on the two changes to the r
Internet-Draft draft-ietf-tls-rfc8447bis-06.txt is now available. It is a work
item of the Transport Layer Security (TLS) WG of the IETF.
Title: IANA Registry Updates for TLS and DTLS
Authors: Joe Salowey
Sean Turner
Name:draft-ietf-tls-rfc8447bis-06.txt
Pages: 18
Internet-Draft draft-ietf-tls-rfc8447bis-07.txt is now available. It is a work
item of the Transport Layer Security (TLS) WG of the IETF.
Title: IANA Registry Updates for TLS and DTLS
Authors: Joe Salowey
Sean Turner
Name:draft-ietf-tls-rfc8447bis-07.txt
Pages: 18
Hi! -06 and -07 incorporate the “Comment” column that we discussed at IETF 118.
Joe and I are planning to ask for WGLC on this version.
spt
> On Nov 27, 2023, at 10:11, internet-dra...@ietf.org wrote:
>
> Internet-Draft draft-ietf-tls-rfc8447bis-07.txt is now available. It is a work
> item of
> On Nov 21, 2023, at 21:03, Sean Turner wrote:
>
> Hi! I sent over the early allocation request and the IANA folks rightly
> pointed out two things that need to be added. This email is to make sure we
> have agreement on the two changes to the registrations in s11.1. If you don’t
> agree wi
On Tue, Nov 21, 2023 at 9:03 PM Sean Turner wrote:
>
> Hi! I sent over the early allocation request and the IANA folks rightly
> pointed out two things that need to be added. This email is to make sure we
> have agreement on the two changes to the registrations in s11.1. If you don’t
> agree wi
> Hi! -06 and -07 incorporate the “Comment” column that we discussed at IETF
> 118. Joe and I are planning to ask for WGLC on this version.
Looks good to me, thanks!
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
On Mon, Nov 27, 2023 at 10:14 AM Sean Turner wrote:
>
> Hi! -06 and -07 incorporate the “Comment” column that we discussed at IETF
> 118. Joe and I are planning to ask for WGLC on this version.
Minor quibble with the IANA instructions for instruction type. It
reads " Setting a value to "Y" or "
On Tue, Nov 28, 2023, at 05:03, Watson Ladd wrote:
>> 2. The "TLS 1.3” column for ech_outer_extensions registration needs to
>> indicate a value; remember, this column indicates the messages in which the
>> extension may appear. Currently, it’s “”. “N/A" has been suggested, which
>> makes sense
11 matches
Mail list logo
