RFC 8492 on Secure Password Ciphersuites for Transport Layer Security (TLS)

rfc-editor@rfc-editor.org Thu, 21 February 2019 21:31 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 81005131223 for <ietf-announce@ietfa.amsl.com>; Thu, 21 Feb 2019 13:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 OaPSnvLAxZ3H for <ietf-announce@ietfa.amsl.com>; Thu, 21 Feb 2019 13:31:27 -0800 (PST)
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 CF7EF13121E for <ietf-announce@ietf.org>; Thu, 21 Feb 2019 13:31:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 20F07B8209E; Thu, 21 Feb 2019 13:31:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0OTIgb24gU2VjdXJlIFBhc3N3b3JkIENpcGhlcnN1aXRlcyBmb3IgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMp?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20190221213112.20F07B8209E@rfc-editor.org>
Date: Thu, 21 Feb 2019 13:31:12 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/LsEW1vzwvRqJahVFO855CO_H_Ek>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Feb 2019 21:31:30 -0000

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

        
        RFC 8492

        Title:      Secure Password Ciphersuites for 
                    Transport Layer Security (TLS) 
        Author:     D. Harkins, Ed.
        Status:     Informational
        Stream:     Independent
        Date:       February 2019
        Mailbox:    dharkins@lounge.org
        Pages:      40
        Characters: 87027
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-harkins-tls-dragonfly-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8492

        DOI:        10.17487/RFC8492

This memo defines several new ciphersuites for the Transport Layer
Security (TLS) protocol to support certificateless, secure
authentication using only a simple, low-entropy password.  The
exchange is called "TLS-PWD".  The ciphersuites are all based on an
authentication and key exchange protocol, named "dragonfly", that is
resistant to offline dictionary attacks.


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