RFC 5683 on Password-Authenticated Key (PAK) Diffie-Hellman Exchange

rfc-editor@rfc-editor.org Tue, 09 February 2010 02:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C55B28C1D0 for <ietf-announce@core3.amsl.com>; Mon, 8 Feb 2010 18:54:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level:
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIS+hgU8s3Zz for <ietf-announce@core3.amsl.com>; Mon, 8 Feb 2010 18:54:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9D09528C1E3 for <ietf-announce@ietf.org>; Mon, 8 Feb 2010 18:54:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 986A7E06E2; Mon, 8 Feb 2010 18:55:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5683 on Password-Authenticated Key (PAK) Diffie-Hellman Exchange
From: rfc-editor@rfc-editor.org
Message-Id: <20100209025511.986A7E06E2@rfc-editor.org>
Date: Mon, 8 Feb 2010 18:55:11 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 02:54:07 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5683

        Title:      Password-Authenticated Key (PAK) Diffie-Hellman 
                    Exchange 
        Author:     A. Brusilovsky, I. Faynberg,
                    Z. Zeltsan, S. Patel
        Status:     Informational
        Date:       February 2010
        Mailbox:    Alec.Brusilovsky@alcatel-lucent.com, 
                    igor.faynberg@alcatel-lucent.com, 
                    zeltsan@alcatel-lucent.com,  sarvar@google.com
        Pages:      10
        Characters: 17820
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-brusilovsky-pak-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5683.txt

This document proposes to add mutual authentication, based on a
human-memorizable password, to the basic, unauthenticated Diffie-Hellman
key exchange.  The proposed algorithm is called the Password-Authenticated
Key (PAK) exchange.  PAK allows two parties to authenticate themselves
while performing the Diffie-Hellman exchange.

The protocol is secure against all passive and active attacks.
In particular, it does not allow either type of attacker to obtain any
information that would enable an offline dictionary attack on the
password.  PAK provides Forward Secrecy.  This document is not an 
Internet Standards Track specification; it is published for informational 
purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC