RFC 5208 on Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2

rfc-editor@rfc-editor.org Thu, 29 May 2008 23:31 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A9A63A6CCE; Thu, 29 May 2008 16:31:48 -0700 (PDT)
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 048593A6BFF for <ietf-announce@core3.amsl.com>; Thu, 29 May 2008 16:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.353
X-Spam-Level:
X-Spam-Status: No, score=-17.353 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 I8o5pJqBE0Qs for <ietf-announce@core3.amsl.com>; Thu, 29 May 2008 16:31:44 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 30E0A3A6CBA for <ietf-announce@ietf.org>; Thu, 29 May 2008 16:31:00 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 09E7A12D830; Thu, 29 May 2008 16:31:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5208 on Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2
From: rfc-editor@rfc-editor.org
Message-Id: <20080529233100.09E7A12D830@bosco.isi.edu>
Date: Thu, 29 May 2008 16:31:00 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5208

        Title:      Public-Key Cryptography Standards (PKCS) #8: 
                    Private-Key Information Syntax Specification 
                    Version 1.2 
        Author:     B. Kaliski
        Status:     Informational
        Date:       May 2008
        Mailbox:    kaliski_burt@emc.com
        Pages:      8
        Characters: 12063
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kaliski-pkcs8-00.txt

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

This document represents a republication of PKCS #8 v1.2 from RSA
Laboratories' Public Key Cryptography Standard (PKCS) series.  Change
control is transferred to the IETF.  The body of this document,
except for the security considerations section, is taken directly
from the PKCS #8 v1.2 specification.

This document describes a syntax for private-key information.  This memo 
provides information for the Internet community.


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
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce