[rfc-dist] RFC 8351 on The PKCS #8 EncryptedPrivateKeyInfo Media Type

rfc-editor@rfc-editor.org Wed, 27 June 2018 05:36 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C238130F0D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 JzJX9IyxjUvh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36:30 -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 AD061130E85 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 26 Jun 2018 22:36:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 28A58B8122F; Tue, 26 Jun 2018 22:36:25 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 547FBB8122F; Tue, 26 Jun 2018 22:36:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180627053623.547FBB8122F@rfc-editor.org>
Date: Tue, 26 Jun 2018 22:36:23 -0700
Subject: [rfc-dist] RFC 8351 on The PKCS #8 EncryptedPrivateKeyInfo Media Type
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8351

        Title:      The PKCS #8 EncryptedPrivateKeyInfo Media Type 
        Author:     S. Leonard
        Status:     Informational
        Stream:     Independent
        Date:       June 2018
        Mailbox:    dev+ietf@seantek.com
        Pages:      7
        Characters: 14797
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-seantek-pkcs8-encrypted-03.txt

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

        DOI:        10.17487/RFC8351

This document registers the application/pkcs8-encrypted media type
for the EncryptedPrivateKeyInfo type of PKCS #8.  An instance of this
media type carries a single encrypted private key, BER-encoded as a
single EncryptedPrivateKeyInfo value.


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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org