[TLS] Fwd: New Version Notification for draft-barnes-tls-pake-04.txt

[Richard Barnes <[e-mail]>]

Hey TLS WG,

In response to some of the list discussion since the last IETF, Owen and I
revised our TLS PAKE draft.  In the current version, instead of binding to
a single PAKE (SPAKE2+), it defines a general container that can carry
messages for any PAKE that has the right shape.  And we think that "right
shape" covers several current PAKEs: SPAKE2+, Dragonfly, SRP, OPAQUE, ...

The chairs have graciously allotted us 5min on the agenda for Thursday,
where I'd like to ask for the WG to adopt the document.  So please speak up
if you think this is an interesting problem for the TLS WG to work on, and
if you think the approach in this document is a good starting point.  Happy
for comments here or at the microphone on Thursday!

Thanks,
--Richard


---------- Forwarded message ---------
From: <[e-mail]>
Date: Mon, Jul 16, 2018 at 3:25 PM
Subject: New Version Notification for draft-barnes-tls-pake-04.txt
To: Richard Barnes <[e-mail]>, Owen Friel <[e-mail]>



A new version of I-D, draft-barnes-tls-pake-04.txt
has been successfully submitted by Richard Barnes and posted to the
IETF repository.

Name:           draft-barnes-tls-pake
Revision:       04
Title:          Usage of PAKE with TLS 1.3
Document date:  2018-07-16
Group:          Individual Submission
Pages:          11
URL:
https://www.ietf.org/internet-drafts/draft-barnes-tls-pake-04.txt
Status:         https://datatracker.ietf.org/doc/draft-barnes-tls-pake/
Htmlized:       https://tools.ietf.org/html/draft-barnes-tls-pake-04
Htmlized:       https://datatracker.ietf.org/doc/html/draft-barnes-tls-pake
Diff:           https://www.ietf.org/rfcdiff?url2=draft-barnes-tls-pake-04

Abstract:
   The pre-shared key mechanism available in TLS 1.3 is not suitable for
   usage with low-entropy keys, such as passwords entered by users.
   This document describes an extension that enables the use of
   password-authenticated key exchange protocols with TLS 1.3.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat