RFC 7192 on Algorithms for Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types

rfc-editor@rfc-editor.org Fri, 04 April 2014 23:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013451A0339 for <ietf-announce@ietfa.amsl.com>; Fri, 4 Apr 2014 16:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 115UB6lCvTwO for <ietf-announce@ietfa.amsl.com>; Fri, 4 Apr 2014 16:57:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3491A0331 for <ietf-announce@ietf.org>; Fri, 4 Apr 2014 16:57:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 081A37FC3C1; Fri, 4 Apr 2014 16:56:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7192 on Algorithms for Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types
From: rfc-editor@rfc-editor.org
Message-Id: <20140404235659.081A37FC3C1@rfc-editor.org>
Date: Fri, 04 Apr 2014 16:56:58 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/zKxPYc2VmAGig3hxB4n_v3yEJ4g
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 23:57:16 -0000

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

        
        RFC 7192

        Title:      Algorithms for Cryptographic Message Syntax 
                    (CMS) Key Package Receipt and Error 
                    Content Types 
        Author:     S. Turner
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2014
        Mailbox:    turners@ieca.com
        Pages:      6
        Characters: 11255
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-turner-ct-keypackage-receipt-n-error-algs-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7192.txt

This document describes the conventions for using several
cryptographic algorithms with the Cryptographic Message Syntax (CMS)
key package receipt and error content types.  Specifically, it
includes conventions necessary to implement SignedData,
EnvelopedData, EncryptedData, and AuthEnvelopedData.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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