RFC 8133 on The Security Evaluated Standardized Password-Authenticated Key Exchange (SESPAKE) Protocol
rfc-editor@rfc-editor.org Thu, 30 March 2017 21:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCA2129704 for <ietf-announce@ietfa.amsl.com>; Thu, 30 Mar 2017 14:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aa6jOpF3n2M for <ietf-announce@ietfa.amsl.com>; Thu, 30 Mar 2017 14:40:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42BD412953D for <ietf-announce@ietf.org>; Thu, 30 Mar 2017 14:40:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 51FBCB80E63; Thu, 30 Mar 2017 14:40:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8133 on The Security Evaluated Standardized Password-Authenticated Key Exchange (SESPAKE) Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170330214022.51FBCB80E63@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:40:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/e3QzA4afx4LnJm371qM1yCRarUY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 30 Mar 2017 21:41:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8133
Title: The Security Evaluated Standardized
Password-Authenticated
Key Exchange (SESPAKE) Protocol
Author: S. Smyshlyaev. Ed.,
E. Alekseev,
I. Oshkin,
V. Popov
Status: Informational
Stream: Independent
Date: March 2017
Mailbox: svs@cryptopro.ru,
alekseev@cryptopro.ru,
oshkin@cryptopro.ru,
vpopov@cryptopro.ru
Pages: 51
Characters: 89986
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-smyshlyaev-sespake-16.txt
URL: https://www.rfc-editor.org/info/rfc8133
DOI: 10.17487/RFC8133
This document describes the Security Evaluated Standardized Password-
Authenticated Key Exchange (SESPAKE) protocol. The SESPAKE protocol
provides password-authenticated key exchange for usage in systems for
protection of sensitive information. The security proofs of the
protocol were made for situations involving an active adversary in
the channel, including man-in-the-middle (MitM) attacks and attacks
based on the impersonation of one of the subjects.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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