RFC 8018 on PKCS #5: Password-Based Cryptography Specification Version 2.1

rfc-editor@rfc-editor.org Wed, 25 January 2017 00:47 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 95AC31295D8 for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 16:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id dKKxXnkVAPQI for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 16:47:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74EEA1295D1 for <ietf-announce@ietf.org>; Tue, 24 Jan 2017 16:47:42 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6A829B810F3; Tue, 24 Jan 2017 16:47:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8018 on PKCS #5: Password-Based Cryptography Specification Version 2.1
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170125004742.6A829B810F3@rfc-editor.org>
Date: Tue, 24 Jan 2017 16:47:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gH62cazlbFXvH-V6VvyLMTpnI0w>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 25 Jan 2017 00:47:43 -0000

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

        RFC 8018

        Title:      PKCS #5: Password-Based Cryptography Specification 
                    Version 2.1 
        Author:     K. Moriarty, Ed.,
                    B. Kaliski, 
                    A. Rusch
        Status:     Informational
        Stream:     IETF
        Date:       January 2017
        Mailbox:    Kathleen.Moriarty@Dell.com, 
        Pages:      40
        Characters: 80887
        Obsoletes:  RFC 2898

        I-D Tag:    draft-moriarty-pkcs5-v2dot1-04.txt

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

        DOI:        10.17487/RFC8018

This document provides recommendations for the implementation of
password-based cryptography, covering key derivation functions,
encryption schemes, message authentication schemes, and ASN.1 syntax
identifying the techniques.

This document represents a republication of PKCS #5 v2.1 from RSA
Laboratories' Public-Key Cryptography Standards (PKCS) series.  By
publishing this RFC, change control is transferred to the IETF.

This document also obsoletes RFC 2898.

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

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