Re: For your consideration: TAMP and CCC

[Stephen Farrell <stephen.farrell@xxxxxxxxx>]

Thanks Russ,

I think that those should provide excellent material to move
discussions on the list along. (Mind you, at 91 pages, it might
take a while to digest;-)

Cheers,
Stephen.

Russ Housley wrote:
> The Trust Anchor Management Protocol (TAMP) specification has been 
> submitted for your consideration.  The draft was developed primarily to 
> support trust anchor management for cryptographic modules with an 
> assumption that the module would manage a single trust anchor store.  As 
> such, there are some aspects of the specification that are out of 
> alignment with the direction that this group seems to be taking.  
> Specific items that are likely to change include the following:
>
> - Throughout the draft, the term "cryptographic module" can often be 
> read as "trust anchor store".  If I understand the direction of the 
> group, then a focus on the trust anchor store is more appropriate.
>
> - Messages are targeted using hardware-centric names.  I think this 
> approach is one that ought to be supported, but there are probably 
> others.  At a minimum we should consider multiple trust anchor stores on 
> the same device.
>
> - The mail list has discussed trust anchor types, but this draft defines 
> a structure for trust anchors that are used in the validation of  X.509 
> certification paths and signatures on CMS objects that are directly 
> signed by the trust anchor.    At a minimum, I think that it is 
> important to add a hook for other trust anchor types.
>
> Additionally, some changes are planned for the section that describes 
> the processing of TAMPUpdate messages.  Additional language describing 
> path processing in support of TAMP update processing will be added and 
> the CertPathControls feature will be subject to subordination rules.
>
> The TAMP draft is accompanied by another draft: Cryptographic Message 
> Syntax (CMS) Content Constraints X.509 Certificate Extension (CCC).  The 
> CCC draft defines a certificate extension to handle delegation of 
> privileges expressed in TAMP via the TrustAnchorUsage type.  This 
> certificate extension is used to determine whether the public key in an 
> X.509 public key certificate is appropriate to use in the processing of 
> a CMS-protected content.
>
> The drafts are available at these locations:
> http <http://www.ietf.org/internet-drafts/draft-housley-tamp-00.txt> 
> ://www.ietf.org/internet-drafts/draft-housley-tamp-00.txt 
> <http://www.ietf.org/internet-drafts/draft-housley-tamp-00.txt>
> http://www.ietf.org/internet-drafts/draft-housley-cms-content-constraints-extn-00.txt