Re: [TLS] Working Group Last Call for draft-ietf-tls-pwd

[resend now that i’m subscribed to the mailinglist]

AugPAKE is not defined for ECC, the draft just say that is possible to implement but not how. For example, is it safe for all kind of curves ?

AugPAKE have not test vectors in the draft. (very important because of the next point).

AugPAKE have no reference implementation that I’ve found.

I have not seen a review of AugPAKE by IRTF CFRG.

AugPAKE is currently encumbered by IPR issues for all protocols.

Love

8 nov 2013 kl. 18:03 skrev SeongHan Shin <seonghan.shin@aist.go.jp>:

> FYI,
> AugPAKE is provably secure and can be used royal-free.
> AugPAKE
> https://tools.ietf.org/html/draft-shin-tls-augpake-01
> IPR Disclosures
> https://datatracker.ietf.org/ipr/2037/
> 
> Regards,
> Shin
> 
> 
> 
> On Sat, Nov 9, 2013 at 1:35 AM, Blumenthal, Uri - 0558 - MITLL <uri@ll.mit.edu> wrote:
> On 11/8/13 1:50 , "Douglas Stebila" <stebila@qut.edu.au> wrote:
> 
> >I believe that where possible the IETF should aim to standardize
> >cryptographic protocols that have provable security results.  Such proofs
> >of course don't guarantee the protocol is secure in all scenarios, but at
> >least rule out some classes of attacks.  In the field of password
> >authenticated key exchange, there are many provably secure protocols, and
> >so it would be preferable to see one such protocol adopted.
> 
> I concur - except I believe that whenever possible the IETF should aim to
> standardize cryptographic protocols that are unencumbered by license fees
> and patents. If the choice arises between a protocol that carries both
> (provable security and Intellectual Property) and a protocol that has
> neither - I'd strongly prefer the latter.
> 
> 
> 
> >On Nov 8, 2013, at 2:11 AM, Joseph Salowey (jsalowey)
> ><jsalowey@cisco.com> wrote:
> >
> >> This is the beginning of the working group last call for
> >>draft-ietf-tls-pwd-01.   The underlying cryptographic protocol for
> >>TLS-PWD has been reviewed by the IRTF CFRG group with satisfactory
> >>results.  The document needs particular attention paid to the
> >>integration of this mechanism into the TLS protocol.   Please send
> >>comments to the TLS list by December 2, 2013.
> >>
> >> - Joe
> >> (For the TLS chairs)
> >> _______________________________________________
> >> TLS mailing list
> >> TLS@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tls
> >
> >_______________________________________________
> >TLS mailing list
> >TLS@ietf.org
> >https://www.ietf.org/mailman/listinfo/tls
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
> 
> 
> 
> 
> -- 
> ------------------------------------------------------------------
> SeongHan Shin
> Research Institute for Secure Systems (RISEC),
> National Institute of Advanced Industrial Science and Technology (AIST),
> Central 2, 1-1-1, Umezono, Tsukuba City, Ibaraki 305-8568 Japan
> Tel : +81-29-861-2670/5284
> Fax : +81-29-861-5285
> E-mail : seonghan.shin@aist.go.jp
> ------------------------------------------------------------------
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls