RFC 7292 on PKCS #12: Personal Information Exchange Syntax v1.1
rfc-editor@rfc-editor.org Tue, 29 July 2014 22:20 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1264A1B292B for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 Im-fdvZOO9FW for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:20:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id B481B1B2927 for <ietf-announce@ietf.org>; Tue, 29 Jul 2014 15:20:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D6F0B188012; Tue, 29 Jul 2014 15:19:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7292 on PKCS #12: Personal Information Exchange Syntax v1.1
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140729221940.D6F0B188012@rfc-editor.org>
Date: Tue, 29 Jul 2014 15:19:40 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/eITGxKzJHH-y6d8iFaD-AqkVEPc
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 29 Jul 2014 22:20:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7292
Title: PKCS #12: Personal Information Exchange
Syntax v1.1
Author: K. Moriarty, Ed.,
M. Nystrom, S. Parkinson,
A. Rusch, M. Scott
Status: Informational
Stream: IETF
Date: July 2014
Mailbox: Kathleen.Moriarty@emc.com,
mnystrom@microsoft.com,
sean.parkinson@rsa.com,
andreas.rusch@rsa.com,
michael2.scott@rsa.com
Pages: 29
Characters: 58991
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-moriarty-pkcs12v1-1-05.txt
URL: https://www.rfc-editor.org/rfc/rfc7292.txt
PKCS #12 v1.1 describes a transfer syntax for personal identity
information, including private keys, certificates, miscellaneous
secrets, and extensions. Machines, applications, browsers, Internet
kiosks, and so on, that support this standard will allow a user to
import, export, and exercise a single set of personal identity
information. This standard supports direct transfer of personal
information under several privacy and integrity modes.
This document represents a republication of PKCS #12 v1.1 from RSA
Laboratories' Public Key Cryptography Standard (PKCS) series. By
publishing this RFC, change control is transferred to the IETF.
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/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
Association Management Solutions, LLC