pem-dev
[Top] [All Lists]

re:Last Call

1995-05-03 16:54:00
At 8:26 PM 5/2/95, warwick (w.s.) ford wrote:
(1)  There is no indication of how a certificate or certificate chain can
accompany a moss-signed content type in the same message.  This is a
capability
provided by RFC 1421 which MOSS needs also to support.  In pem-dev discussions
on the previous draft, it was resolved that the way to achieve this was to
convey a mosskey-data item in the same message, prior to the moss-signed
item.
To make this clear in the draft, it would be adequate to add, in section 6, an
example showing this type of content type combination.  My understanding
is that
the I-D authors agreed to do this for the new draft.  However, this
example has
still not been included.  It needs to be added before the draft can
progress to
proposed standard.

Warwick,

I'll duck the second issue and let others deal with it.  As to the first
issue you raise (cited above), I'm not sure I understand the difficulty.
Isn't this capability inherent in MIME.  To be specific, MIME messages may
contain any number of parts, all gathered together as one body of type
multiplart/mixed.  To send a message that contains some protected material
and also contains a certificate chain, all that's necessary is to create
the protected material as a MIME object, created the certificate chain as a
separate MIME object, and then combine the two into a single MIME object.

Have I misunderstood your question?

Thanks,

Steve


--------------------
Steve Crocker
CyberCash, Inc., Suite 430                        Work: +1 703 620 4200
2100 Reston Parkway                               Fax:  +1 703 620 4215
Reston, VA 22091                                  
crocker(_at_)cybercash(_dot_)com



<Prev in Thread] Current Thread [Next in Thread>