Secure/Multipurpose Internet Mail Extensions (S/ MIME) Version 4.0 Certificate Handling
draft-ietf-lamps-rfc5750-bis-04

Document Type Active Internet-Draft (lamps WG)
Last updated 2017-04-21 (latest revision 2017-04-07)
Replaces draft-schaad-lamps-rfc5750-bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Jul 2016 - WG adoption of a dra... )
Document shepherd Russ Housley
Shepherd write-up Show (last changed 2017-04-14)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to Russ Housley <housley@vigilsec.com>
LAMPS                                                          J. Schaad
Internet-Draft                                            August Cellars
Obsoletes: 5750 (if approved)                                B. Ramsdell
Intended status: Standards Track                  Brute Squad Labs, Inc.
Expires: October 9, 2017                                       S. Turner
                                                                   sn3rd
                                                           April 7, 2017

   Secure/Multipurpose Internet Mail Extensions (S/ MIME) Version 4.0
                          Certificate Handling
                    draft-ietf-lamps-rfc5750-bis-04

Abstract

   This document specifies conventions for X.509 certificate usage by
   Secure/Multipurpose Internet Mail Extensions (S/MIME) v4.0 agents.
   S/MIME provides a method to send and receive secure MIME messages,
   and certificates are an integral part of S/MIME agent processing.
   S/MIME agents validate certificates as described in RFC 5280, the
   Internet X.509 Public Key Infrastructure Certificate and CRL Profile.
   S/MIME agents must meet the certificate processing requirements in
   this document as well as those in RFC 5280.  This document obsoletes
   RFC 5750.

Contributing to this document

   The source for this draft is being maintained in GitHub.  Suggested
   changes should be submitted as pull requests at <https://github.com/
   lamps-wg/smime>.  Instructions are on that page as well.  Editorial
   changes can be managed in GitHub, but any substantial issues need to
   be discussed on the LAMPS mailing list.

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

Schaad, et al.           Expires October 9, 2017                [Page 1]
Internet-Draft       S/MIME 4.0 Certificate Handling          April 2017

   This Internet-Draft will expire on October 9, 2017.

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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Conventions Used in This Document . . . . . . . . . . . .   4
     1.3.  Compatibility with Prior Practice S/MIME  . . . . . . . .   5
     1.4.  Changes from S/MIME v3 to S/MIME v3.1 . . . . . . . . . .   5
     1.5.  Changes from S/MIME v3.1 to S/MIME v3.2 . . . . . . . . .   6
     1.6.  Changes since S/MIME 3.2  . . . . . . . . . . . . . . . .   6
   2.  CMS Options . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Certificate Revocation Lists  . . . . . . . . . . . . . .   7
     2.2.  Certificate Choices . . . . . . . . . . . . . . . . . . .   7
       2.2.1.  Historical Note about CMS Certificates  . . . . . . .   7
     2.3.  CertificateSet  . . . . . . . . . . . . . . . . . . . . .   8
   3.  Using Distinguished Names for Internet Mail . . . . . . . . .   9
Show full document text