Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Algorithms for Asymmetric Key Package Content Type (RFC5959)

IP.com Disclosure Number: IPCOM000199037D
Original Publication Date: 2010-Aug-01
Included in the Prior Art Database: 2010-Aug-24
Document File: 14 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Turner: AUTHOR

Abstract

This document also includes conventions necessary to protect the AsymmetricKeyPackage content type [RFC5958] with Cryptographic Message Syntax (CMS) protecting content types: SignedData [RFC5652], EnvelopedData [RFC5652], EncryptedData [RFC5652], AuthenticatedData [RFC5652], and AuthEnvelopedData [RFC5083]. Implementations of AsymmetricKeyPackage do not require support for any CMS protecting content type; however, if the AsymmetricKeyPackage is CMS protected it is RECOMMENDED that conventions defined herein be followed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 20% of the total text.

Internet Engineering Task Force (IETF)                         S. Turner Request for Comments: 5959                                          IECA Category: Standards Track                                    August 2010 ISSN: 2070-1721

            Algorithms for Asymmetric Key Package Content Type

Abstract

   This document describes the conventions for using several    cryptographic algorithms with the EncryptedPrivateKeyInfo structure,    as defined in RFC 5958.  It also includes conventions necessary to    protect the AsymmetricKeyPackage content type with SignedData,    EnvelopedData, EncryptedData, AuthenticatedData, and    AuthEnvelopedData.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5959.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Turner                       Standards Track                    [Page 1]
 RFC 5959         Algorithms for Asymmetric Key Packages      August 2010

 1.  Introduction

   This document describes the conventions for using several    cryptographic algorithms with the EncryptedPrivateKeyInfo structure    [RFC5958].  The EncryptedPrivateKeyInfo is used by [P12] to encrypt    PrivateKeyInfo [RFC5958].  It is similar to EncryptedData [RFC5652]    in that it has no recipients, no originators, and no content    encryption keys and requires keys to be managed by other means.

   This document also includes conventions necessary to protect the    AsymmetricKeyPackage content type [RFC5958] with Cryptographic    Message Syntax (CMS) protecting content types: SignedData [RFC5652],    EnvelopedData...