Re: Content Type Attribute Question

Russ,

    Sorry about the delayed reply.  Been busy with other lives...

    I guess I'd still rather see an open ended field in the
encapsulatedContentType attribute, but the union of the existing attribute and
contentHints does address much of my concern.  Why do we have two attributes
to describe the encapsulated content rather than one?  If the semantics of
contentHint can be bent as far as MIME content types, then it seems like they
should be the same attribute.

Chris


_________________________

Russ Housley wrote:

> John:
>
> Thanks.  The contentType attribue is defined in CMS, and it already has an
> OID.
>
> I will assign an OID for the encapsulatedContentType attribute.  In fact,
> I'll do it now ... I assigned:
>
>     id-smime OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840)
>             rsadsi(113549) pkcs(1) pkcs-9(9) 16 }
>
>     id-aa   OBJECT IDENTIFIER ::= { id-smime 2 }
>
>     id-aa-encapContentType OBJECT IDENTIFIER ::= { id-aa 6 }
>
> Russ
>
> At 06:42 PM 1/30/98 -0500, John Pawling wrote:
> > Russ,
> >
> > ESS, Sec 1.3.4 already lists encapsulatedContentType as a separate
> > attribute.  This is needed to provide equivalent services as the ACP120
> > encapsulatedContentType.
> >
> > Please note that the ESS Open Issues (Appendix D) states that OIDs still
> > need to be defined for the contentType and encapsulatedContentType
> attributes.
> > - John Pawling