S/MIME Capabilities for Public Key Definitions
draft-ietf-pkix-pubkey-caps-04

The information below is for an old version of the document
Document Type Active Internet-Draft (pkix WG)
Last updated 2012-04-20 (latest revision 2011-11-15)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation
Telechat date
Needs a YES.
Responsible AD spt
IESG note Document Shepherd: Stephen Kent (kent@bbn.com)
Send notices to pkix-chairs@tools.ietf.org, draft-ietf-pkix-pubkey-caps@tools.ietf.org
Network Working Group                                          J. Schaad
Internet-Draft                                   Soaring Hawk Consulting
Intended status: Informational                         November 16, 2011
Expires: May 19, 2012

             S/MIME Capabilities for Public Key Definitions
                     draft-ietf-pkix-pubkey-caps-04

Abstract

   This document defines a set of S/MIME Capability types for ASN.1
   encoding for the current set of public keys define in the PKIX
   working group.  This facilitates the ability for a requester to
   specify information on the public keys and signature algorithms to be
   used in responses.  An example of where this is used is with the OCSP
   Agility draft.

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."

   This Internet-Draft will expire on May 19, 2012.

Copyright Notice

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

Schaad                    Expires May 19, 2012                  [Page 1]
Internet-Draft                 PubKey Caps                 November 2011

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  ASN.1 Notation . . . . . . . . . . . . . . . . . . . . . .  3
     1.2.  Requirements Terminology . . . . . . . . . . . . . . . . .  4
   2.  RSA Public Keys  . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Generic RSA Public Keys  . . . . . . . . . . . . . . . . .  5
     2.2.  RSASSA-PSS Signature Public Keys . . . . . . . . . . . . .  6
     2.3.  RSA ES-OAEP Key Transport Public Keys  . . . . . . . . . .  6
   3.  Diffie-Hellman Keys  . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  DSA Signature Public Key . . . . . . . . . . . . . . . . .  8
     3.2.  DH Key Agreement Keys  . . . . . . . . . . . . . . . . . .  9
   4.  Elliptical Curve Keys  . . . . . . . . . . . . . . . . . . . . 10
     4.1.  Generic Elliptical Curve Keys  . . . . . . . . . . . . . . 10
     4.2.  Elliptical Curve DH Keys . . . . . . . . . . . . . . . . . 11
     4.3.  Elliptical Curve MQV Keys  . . . . . . . . . . . . . . . . 11
   5.  RSASSA-PSS Signature Algorithm Capability  . . . . . . . . . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 16
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 16
   Appendix A.  2008 ASN.1 Module . . . . . . . . . . . . . . . . . . 17
   Appendix B.  1988 ASN.1 Module . . . . . . . . . . . . . . . . . . 20
   Appendix C.  Future Work . . . . . . . . . . . . . . . . . . . . . 22
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23

Schaad                    Expires May 19, 2012                  [Page 2]
Internet-Draft                 PubKey Caps                 November 2011

1.  Introduction

   In the process of dealing with the OCSP agility issues in [RFC6277]
   it was noted that we really wanted to describe information to be used
   in selecting a public key, but we did not currently have any way of
   doing so at the current time.  This document fills that hole by
   defining a set of S/MIME Capability types for a small set of public
   key representations.

   S/MIME Capabilities where originally defined in [SMIMEv3-MSG] as a
   way for the sender of an S/MIME message to tell the recipient of the
   message the set of encryption algorithms that were supported by the
Show full document text