Requirements for PAKE schemes
draft-irtf-cfrg-pake-reqs-00

The information below is for an old version of the document
Document Type Active Internet-Draft (cfrg RG)
Last updated 2015-09-23 (latest revision 2015-06-30)
Stream IRTF
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-irtf-cfrg-pake-reqs
Stream IRTF state Active RG Document
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Schmidt
Internet-Draft                                 secunet Security Networks
Intended status: Standards Track                           June 29, 2015
Expires: December 31, 2015

                     Requirements for PAKE schemes
                      draft-irtf-cfrg-pake-reqs-00

Abstract

   Password-Authenticated Key Agreement (PAKE) schemes are interactive
   protocols that allow the participants to authenticate each other and
   derive shared cryptographic keys using a (weaker) shared password.
   This document reviews different types of PAKE schemes and discusses
   their requirements.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 31, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Schmidt                 Expires December 31, 2015               [Page 1]
Internet-Draft        Requirements for PAKE schemes            June 2015

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  PAKE Taxonomy . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Storage of the Password . . . . . . . . . . . . . . . . .   3
     3.2.  Transmission of Public Keys . . . . . . . . . . . . . . .   3
     3.3.  Two Party versus Multiparty . . . . . . . . . . . . . . .   4
   4.  Security of PAKEs . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Implementation Aspects  . . . . . . . . . . . . . . . . .   5
     4.2.  Special case: Elliptic Curves . . . . . . . . . . . . . .   6
   5.  Protocol Considerations and Applications  . . . . . . . . . .   6
   6.  Performance . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   Passwords are the predominant method of accessing the Internet today
   due largely to their intuitiveness and ease of use.  Since a user
   needs to enter her password repeatedly over the course of many
   connections to the Internet, these passwords tend to be easy to
   remember and able to be entered, repeatedly, with a low probability
   of error.  They tend to be low-grade and not-so-random secrets that
   are susceptible to brute-force guessing attacks.  In other words,
   they are horrible credentials to use for authentication.

   A Password-Authenticated Key Exchange (PAKE) attempts to address this
   issue by constructing a cryptographic key exchange that does not
   result in the password, or password-derived data, being transmitted
   across an unsecured channel.  Two parties to the exchange prove
   possession of the shared password without revealing it.  Such
   exchanges are therefore resistant to an off-line, brute-force
   dictionary attack.  PAKEs are especially interesting due to the fact
   that they can achieve mutual authentication without requiring any
   Public Key Infrastructure (PKI).

Schmidt                 Expires December 31, 2015               [Page 2]
Show full document text