[smime] draft-housley-ct-keypackage-receipt-n-error-01.txt

Russ Housley <housley@vigilsec.com> Thu, 02 May 2013 14:13 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 5136A21F8BCC for <smime@ietfa.amsl.com>; Thu, 2 May 2013 07:13:00 -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 cfQ3s9wB3-75 for <smime@ietfa.amsl.com>; Thu, 2 May 2013 07:12:55 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 372C021F8B98 for <smime@ietf.org>; Thu, 2 May 2013 07:12:55 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D64389A412B for <smime@ietf.org>; Thu, 2 May 2013 10:12:55 -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 K-KOVWHLpA2P for <smime@ietf.org>; Thu, 2 May 2013 10:12:50 -0400 (EDT)
Received: from [192.168.2.102] (pool-96-241-221-210.washdc.fios.verizon.net [96.241.221.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id AE1FA9A4129 for <smime@ietf.org>; Thu, 2 May 2013 10:12:54 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 May 2013 10:12:52 -0400
References: <20130502141128.13257.9277.idtracker@ietfa.amsl.com>
To: IETF SMIME <smime@ietf.org>
Message-Id: <C7F9EA07-2FF7-4B43-9249-D9042BF1464F@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-01.txt
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: Thu, 02 May 2013 14:13:00 -0000

The -01 version addresses most, but not all, of the comments submitted by Jim Schaad.

Russ


> From: internet-drafts@ietf.org
> Date: May 2, 2013 10:11:28 AM EDT
> To: Russ Housley <housley@vigilsec.com>
> Subject: New Version Notification for draft-housley-ct-keypackage-receipt-n-error-01.txt
> 
> 
> A new version of I-D, draft-housley-ct-keypackage-receipt-n-error-01.txt
> has been successfully submitted by Russ Housley and posted to the
> IETF repository.
> 
> Filename:	 draft-housley-ct-keypackage-receipt-n-error
> Revision:	 01
> Title:		 Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types
> Creation date:	 2013-05-02
> Group:		 Individual Submission
> Number of pages: 25
> URL:             http://www.ietf.org/internet-drafts/draft-housley-ct-keypackage-receipt-n-error-01.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-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-housley-ct-keypackage-receipt-n-error-01
> 
> 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.