[lamps] RFC 8550 on Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling

rfc-editor@rfc-editor.org Wed, 01 May 2019 01:08 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318811201D3; Tue, 30 Apr 2019 18:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 CeiWx_VTj4qx; Tue, 30 Apr 2019 18:08:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EAA61201CF; Tue, 30 Apr 2019 18:08:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 207EEB81B19; Tue, 30 Apr 2019 18:07:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spasm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190501010756.207EEB81B19@rfc-editor.org>
Date: Tue, 30 Apr 2019 18:07:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ketvs3KPbMuuoAXcz6oJl9ESiLo>
Subject: [lamps] RFC 8550 on Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 01:08:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8550

        Title:      Secure/Multipurpose Internet Mail Extensions (S/MIME) 
                    Version 4.0 Certificate Handling 
        Author:     J. Schaad,  
                    B. Ramsdell,
                    S. Turner
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    ietf@augustcellars.com, 
                    blaker@gmail.com, 
                    sean@sn3rd.com
        Pages:      29
        Characters: 63210
        Obsoletes:  RFC 5750

        I-D Tag:    draft-ietf-lamps-rfc5750-bis-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8550

        DOI:        10.17487/RFC8550

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
("Internet X.509 Public Key Infrastructure Certificate and                                    
Certificate Revocation List (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.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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