That was what draft -00 did. I changed it based on feed back from Peter^2.
At 12:42 PM 9/17/2004, Peter Gutmann wrote:
Russ Housley <housley(_at_)vigilsec(_dot_)com> writes:
>The application itself is not ready for release to the IETF, and it may
>be released to the IETF. However, please take a look at draft-housley-cms-
>fw-wrap. This has many properties in common with the application that
>yet ready for release. Basically, a content type is defined, and the use of
>CMS to protect that content type is specified. S/MIME is not used, only
If it's meant for use in fw-wrap, couldn't it just be specified as an extra
attribute in there, along with the other attributes that fw-wrap introduces?