Re: [P1619-3] Question about using RFC3852
Hi Thomas,
within KEYPROV we support 2 key container formats, one based on XML
format and another one based on an ASN.1 format (building on CMS). Here
are the 2 documents:
http://www.ietf.org/internet-drafts/draft-ietf-keyprov-portable-symmetric-key-container-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-keyprov-symmetrickeyformat-02.txt
In addition to the encoding of the container there is the question of
what to carry inside these key containers (other than the obvious
stuff). Our folks have put a number of things in there (see
draft-ietf-keyprov-portable-symmetric-key-container-04.txt) but maybe
the 1619.3 group has different requirements. I wonder whether the
details of these attributes have been discussed in this group already.
Ciao
Hannes
Thomas Hardjono wrote:
> I was wondering if the 1619.3 groups has ever
> discussed the possible use of CMS (RFC3852) as the
> mechanism to wrap the actual keys. RFC3852 is a
> well-known and widely implemented standard, and
> has wide interoperability with existing PKI infra.
>
> http://www.ietf.org/rfc/rfc3852.txt
>
> Thus, for example, one way IEEE1619.3 could use it
> is as the blob in the KeyContents:
>
> <keyContents>
> <secretContents>CMS_BLOB</secretContents>
> </keyContents>
>
> This approach would save IEEE1619.3 from having to
> define its own key-wrapping syntax and having
> vendors implement a new standard.
>
> Thoughts?
>
> /thomas/
>
>
>
>