[TLS] Internet-Draft on TLS resumption across Server Name Indications

2019-03-04 Thread Erik Sy
Hi folks, we investigated the potential benefit of resuming TLS sessions across different SNI values [1]. We found, that enabling TLS resumption across different SNI values allows converting 58.7% of the required full TLS handshakes to resumed connection establishments when retrieving an average A

Re: [TLS] Internet-Draft on TLS resumption across Server Name Indications

2019-03-04 Thread Salz, Rich
Have you looked at the HTTP "secondary cert" stuff? ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

[TLS] WGLC for draft-ietf-tls-dtls-connection-id-03

2019-03-04 Thread Joseph Salowey
This is a working group last call for draft-ietf-tls-dtls-connection-id-03. The last working group last call resulted in some issues. The authors worked with the reviewers to publish a new draft to address these issue. Please focus your review on the changes since the previous last call. You can

Re: [TLS] EXTERNAL: Re: Authentication Only Ciphersuites RFC

2019-03-04 Thread Jack Visoky
Hi John, OK I will add an update to the draft which further emphasizes that these cipher suites are strictly to be used when confidentiality is not a concern. Yes good catch on the tag length for SHA-384, I’ll also update that to 48, that appears to be a typo. Thanks, --Jack From: John Matts

Re: [TLS] EXTERNAL: Re: Authentication Only Ciphersuites RFC

2019-03-04 Thread Stephen Farrell
Jack, (With the proviso that this isn't and I agree ought not be a WG item, so the chairs should feel free to tell me to stop...) On 04/03/2019 21:49, Jack Visoky wrote: > OK I will add an update to the draft which further emphasizes that > these cipher suites are strictly to be used when confid

Re: [TLS] WGLC for draft-ietf-tls-dtls-connection-id-03

2019-03-04 Thread Martin Thomson
LGTM. I would strike ", if these privacy properties are important in a given deployment" from the acknowledgments section (which is an odd place for the accompanying statement. I would add an explicit note about the lack of CID update making this unsuitable for mobility scenarios. That's a c

Re: [TLS] Two Multi-CDN proposals

2019-03-04 Thread Kazuho Oku
2019年3月2日(土) 1:57 Christopher Wood : > > On Wed, Feb 27, 2019 at 11:34 PM Kazuho Oku wrote: > > > > Hi Chris, > > > > Thank you for writing down the PRs describing possible designs that we > > might adopt. I think it helps a lot in understanding the details and > > making accurate comparisons. > >

Re: [TLS] Two Multi-CDN proposals

2019-03-04 Thread Kazuho Oku
2019年3月3日(日) 5:57 Eric Rescorla : > > > > On Fri, Mar 1, 2019 at 11:03 PM Mike Bishop wrote: >> >> Totally agree that we want to avoid the extra DNS round-trip as often as >> possible. However, I see the options in the opposite light – if all you >> need is #136, then you can put exact addresse

Re: [TLS] WGLC for draft-ietf-tls-dtls-connection-id-03

2019-03-04 Thread Thomas Fossati
On Mon, Mar 4, 2019 at 4:43 PM Joseph Salowey wrote: > This is a working group last call for draft-ietf-tls-dtls-connection-id-03. > The last working group last call resulted in some issues. The authors worked > with the reviewers to publish a new draft to address these issue. Please > focus