[TLS] I-D Action: draft-ietf-tls-exported-authenticator-10.txt

2019-11-04 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Layer Security WG of the IETF. Title : Exported Authenticators in TLS Author : Nick Sullivan Filename: draft-ietf-tls-expo

[TLS] comment on draft-ietf-tls-subcerts

2019-11-04 Thread Rob Sayre
Hi, I left a comment wondering how this draft might interact with security issues in the network layer, like the various kinds of BGP hijacking. https://github.com/tlswg/tls-subcerts/issues/42 That's not to say this draft is the place to fix those problems, but it seems like it could make them m

[TLS] TLS 1.3 Extended Key Schedule

2019-11-04 Thread Jonathan Hoyland
Hi TLSWG, Chris and I have put together a draft for adding extra key material into the TLS 1.3 handshake. There are various drafts that want to inject extra information into the key schedule, so it would be great if we could manage to do this in a generic way. You can have a look here

[TLS] I-D Action: draft-ietf-tls-esni-05.txt

2019-11-04 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Layer Security WG of the IETF. Title : Encrypted Server Name Indication for TLS 1.3 Authors : Eric Rescorla Kazuh

Re: [TLS] I-D Action: draft-ietf-tls-ticketrequests-04.txt

2019-11-04 Thread Sean Turner
Sorry folks I was jumping the gun there. I need to kick off the WGLC before sending it on the IESG. Stay tuned. spt > On Nov 4, 2019, at 11:05, Sean Turner wrote: > > This version makes the track change: informational->standards. Once I get > the BCP 78 and 79 confirmations from the author

[TLS] I-D Action: draft-ietf-tls-tlsflags-01.txt

2019-11-04 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Layer Security WG of the IETF. Title : A Flags Extension for TLS 1.3 Author : Yoav Nir Filename: draft-ietf-tls-tlsflags-0

Re: [TLS] 2nd WGLC for draft-ietf-tls-dtls13

2019-11-04 Thread Sean Turner
This WGLC has concluded. I will complete my shepherd write-up and forward this to the IESG once I have received the BCP 78 and 70 confirmations. spt > On Oct 13, 2019, at 21:13, Sean Turner wrote: > > This is the second working group last call for the "The Datagram Transport > Layer Security

Re: [TLS] I-D Action: draft-ietf-tls-ticketrequests-04.txt

2019-11-04 Thread Sean Turner
This version makes the track change: informational->standards. Once I get the BCP 78 and 79 confirmations from the authors I will be forwarding this to the IESG. spt > On Nov 4, 2019, at 10:40, internet-dra...@ietf.org wrote: > > > A New Internet-Draft is available from the on-line Internet-

[TLS] I-D Action: draft-ietf-tls-external-psk-importer-02.txt

2019-11-04 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Layer Security WG of the IETF. Title : Importing External PSKs for TLS Authors : David Benjamin Christopher A. Wo

[TLS] I-D Action: draft-ietf-tls-ticketrequests-04.txt

2019-11-04 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Layer Security WG of the IETF. Title : TLS Ticket Requests Authors : Tommy Pauly David Schinazi

Re: [TLS] Standards Track for draft-ietf-tls-ticketrequests

2019-11-04 Thread Sean Turner
November 1st has come and gone. Though silence is not consensus, I will interpret this particular silence as such because I suspect that this particular piece of process is not that interesting to most. I submitted a PR to change the track to “Standards": https://github.com/tlswg/draft-ietf-tl

Re: [TLS] Secdir last call review of draft-ietf-tls-exported-authenticator-09

2019-11-04 Thread Yaron Sheffer
Hi Nick, Apologies for not responding on time. I may be missing some follow-on discussions, but: Ben suggested that we mention that QUIC is also an option, even if informatively, in addition to the “SHOULD use TLS” statement. I think we left my question re: back-fitting this protocol in