Re: [edu-team] IETF Tutorial on TLS1.3

Sean,

When you present your slides, can you also include a link to the tutorial survey that we’ve developed? Also, do you have a version ready for posting to the Datatracker?

https://www.surveymonkey.com/r/100tls <https://www.surveymonkey.com/r/100tls>

Thanks,
Alexa

> On Nov 10, 2017, at 10:33 AM, Sean Turner <sean@sn3rd.com> wrote:
> 
> Please wait Joe’s got some edits I’d like to talk over.  I suspect we’ll be able to upload them Saturday afternoon.
> 
> spt
> 
>> On Nov 9, 2017, at 17:31, Karen O'Donoghue <odonoghue@isoc.org> wrote:
>> 
>> Do you have an updated version of the slides (or can I upload the draft sent by Mirjam?)
>> 
>> Thanks,
>> Karen
>> 
>>> On Nov 10, 2017, at 1:19 AM, Joseph Salowey <jsalowey@gmail.com> wrote:
>>> 
>>> I agree with Sean that we should probably stick to things that are working group items.  There are a few other working group items,  such as draft-ietf-tls-grease-00, that I would include before non adopted drafts.  We will mention some the issues behind these non-wg drafts when we talk about forward secrecy and privacy.  
>>> 
>>> Cheers,
>>> 
>>> Joe
>>> 
>>> On Wed, Nov 8, 2017 at 5:05 PM, Sean Turner <sean@sn3rd.com> wrote:
>>> Hi Sean,
>>> Thank you for your work on this tutorial for IETF 100. A couple nits:
>>> - s1: suggest removing "Newcomer's" because that typically refers to a specific tutorial session. perhaps IETF Newcomer's Tutorial 20171112 -> IETF 100 Singapore 20171112
>>> 
>>> [spt] sold
>>> 
>>> - s?: how about adding a list of relevant drafts. e.g., a roadmap of the 1.3-related drafts. If you decide to include ones that aren't WG docs yet, it might help people find what they're interested in. (Searching for 1.3 in the datatracker turns up the list below.)
>>> 
>>> [spt] Here be dragons!  the main draft is referred to on page 6 - they just need to click the link.  Only two others are really relevant: vectors and DTLS1.3; I’ll add a slide at the end for those.  draft-camwinget, draft-green, and draft-rhdh all want to be TLS1.3-related but the WG is not yet sold - some in the WG are very, violently not sold on them and would probably scream bloody murder if we were to suggest that they are even related.  draft-whyte desperately wants to be “related” but the WG is not yet sold that his solution is the “one” so I think it would not be fair to elevate it in our talk.  tokbind is something really different and is probably worthy of a whole other tutorial.
>>> 
>>> draft-ietf-tls-tls13-21
>>> The Transport Layer Security (TLS) Protocol Version 1.3
>>> 
>>> draft-ietf-tls-tls13-vectors-02
>>> Example Handshake Traces for TLS 1.3
>>> 
>>> draft-ietf-tls-dtls13-02
>>> The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
>>> 
>>> draft-ietf-tokbind-tls13-0rtt-02
>>> Token Binding for 0-RTT TLS 1.3 Connections
>>> 
>>> draft-camwinget-tls-use-cases-00
>>> TLS 1.3 Impact on Network-Based Security
>>> 
>>> draft-green-tls-static-dh-in-tls13-01
>>> Data Center use of Static Diffie-Hellman in TLS 1.3
>>> 
>>> draft-nharper-tokbind-tls13-00
>>> Token Binding for Transport Layer Security (TLS) Version 1.3 Connections
>>> 
>>> draft-rhrd-tls-tls13-visibility-00
>>> TLS 1.3 Option for Negotiation of Visibility in the Datacenter
>>> 
>>> draft-whyte-qsh-tls13-06
>>> Quantum-Safe Hybrid (QSH) Key Exchange for Transport Layer Security (TLS) version 1.3
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> edu-team mailing list
>>> edu-team@ietf.org
>>> https://www.ietf.org/mailman/listinfo/edu-team
>> 
> 
> _______________________________________________
> edu-team mailing list
> edu-team@ietf.org
> https://www.ietf.org/mailman/listinfo/edu-team