The PKCS #8 EncryptedPrivateKeyInfo Media Type
draft-seantek-pkcs8-encrypted-03

Document Type Active Internet-Draft (individual)
Last updated 2017-11-27 (latest revision 2017-11-13)
Stream ISE
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-seantek-pkcs8-encrypted
Stream ISE state Response to Review Needed
Consensus Boilerplate Unknown
Document shepherd Nevil Brownlee
Shepherd write-up Show (last changed 2017-11-14)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Nevil Brownlee <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                         S. Leonard
Internet-Draft                                             Penango, Inc.
Intended Status: Informational                         November 14, 2017
Expires: May 18, 2018                                                   

             The PKCS #8 EncryptedPrivateKeyInfo Media Type
                    draft-seantek-pkcs8-encrypted-03

Abstract

   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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2017 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.

 

Leonard                    Exp. May 18, 2018                    [Page 1]
Internet-Draft        PKCS #8 Encrypted Media Type         November 2017

1. Definitions

   The key words "SHOULD", "SHOULD NOT", and "RECOMMENDED" in this
   document are to be interpreted as described in [RFC2119].

2. Registration Application

   Type name: application

   Subtype name: pkcs8-encrypted

   Required parameters: None.

   Optional parameters:

    password-mapping: The private key is encrypted with an encryption
     algorithm, which could be a password-based encryption scheme as
     that term is used in PKCS #5 [RFC2898]. Such algorithms take a
     password as input. A "password" is a secret text value (Section 3
     of PKCS #5), but for algorithmic purposes the term "password"
     refers to an octet string (Section 2 of PKCS #5). Therefore, there
     must be some mapping between the text value (which might be user
     input) and the octet string. Section 3 of PKCS #5 recommends "that
     applications follow some common text encoding rules"; it then
     offers, but does not recommend, ASCII and UTF-8.

     While many modern applications support Unicode and Unicode-based
     encodings such as UTF-8 and UTF-16, interchange is still needed
     with private key artifacts that are encrypted with passwords in
     other encodings. Therefore, this parameter specifies the charset
     (see Section 1.3 of [RFC2978]) that a recipient SHOULD attempt
     first, in "reverse", when mapping from a sequence of characters to
     an octet string. This parameter is not cryptographically protected,
     so recipients SHOULD NOT rely on it as the exclusive mapping
     possibility.

     This parameter has similar semantics to the charset parameter from
     text/plain, except that it only applies to the user's input (text
     value) of a password. There is no default value.

     The following special values, which all begin with "*" to
     distinguish them from registered charsets, are defined:
     *pkcs12     = UTF-16LE with U+0000 NULL terminator: PKCS #12-style,
                   see [RFC7292]
     *precis     = PRECIS password profile, i.e., OpaqueString from
                   Section 4 of [RFC7613]: always UTF-8 in Normalization
                   Form C (NFC)
     *precis-XXX = PRECIS profile as named XXX in the IANA PRECIS
 

Leonard                    Exp. May 18, 2018                    [Page 2]
Internet-Draft        PKCS #8 Encrypted Media Type         November 2017

                   Profiles Registry
     *hex        = hexadecimal input: the input is mapped to 0-9, A-F,
                   and then converted directly to octets. If there are
                   an odd number of hex digits, either the final digit 0
                   is appended, or an error condition is raised. Compare
Show full document text