[smime] draft-housley-ct-keypackage-receipt-n-error-00

Russ Housley <housley@vigilsec.com> Fri, 19 April 2013 16:21 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B8121F9609 for <smime@ietfa.amsl.com>; Fri, 19 Apr 2013 09:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-0DKjaXFEn9 for <smime@ietfa.amsl.com>; Fri, 19 Apr 2013 09:21:18 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5D71321F9608 for <smime@ietf.org>; Fri, 19 Apr 2013 09:21:18 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E2654F24078 for <smime@ietf.org>; Fri, 19 Apr 2013 12:21:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id oUBducwaPxCW for <smime@ietf.org>; Fri, 19 Apr 2013 12:21:13 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id ED9EFF2406E for <smime@ietf.org>; Fri, 19 Apr 2013 12:21:21 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Apr 2013 12:21:16 -0400
References: <20130418151254.13949.52367.idtracker@ietfa.amsl.com>
To: IETF SMIME <smime@ietf.org>
Message-Id: <50816A63-E208-449A-977A-9F31544C9222@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Subject: [smime] draft-housley-ct-keypackage-receipt-n-error-00
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 16:21:23 -0000

Since people that know about CMS hang out on this list, I am asking for review and comment of this Internet-Draft here.

Thanks,
  Russ



> From: internet-drafts@ietf.org
> Date: April 18, 2013 11:12:54 AM EDT
> To: housley@vigilsec.com
> Subject: New Version Notification for draft-housley-ct-keypackage-receipt-n-error-00.txt
> 
> 
> A new version of I-D, draft-housley-ct-keypackage-receipt-n-error-00.txt
> has been successfully submitted by Russ Housley and posted to the
> IETF repository.
> 
> Filename:	 draft-housley-ct-keypackage-receipt-n-error
> Revision:	 00
> Title:		 Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types
> Creation date:	 2013-04-17
> Group:		 Individual Submission
> Number of pages: 23
> URL:             http://www.ietf.org/internet-drafts/draft-housley-ct-keypackage-receipt-n-error-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-housley-ct-keypackage-receipt-n-error
> Htmlized:        http://tools.ietf.org/html/draft-housley-ct-keypackage-receipt-n-error-00
> 
> 
> Abstract:
>  This document defines the syntax for two Cryptographic Message Syntax
>  (CMS) content types, one for key package receipts, and another for
>  key package errors.  The key package receipt content type is used to
>  confirm receipt of an identified key package or collection of key
>  packages.  The key package error content type is used to indicate an
>  error occurred during the processing of a key package.  CMS can be
>  used to digitally sign, digest, authenticate, or encrypt these
>  content types.