changes to CEM message structure

Per the CEM draft review by the IETF area directors, the draft editors were
informed the need to modify the format of the digital certificate
distribution to the PKCS#7 SMIME certs-only media type since this is a well
established standard.

Based on this, the draft editors would like to modify the CEM message
structure to something like this:

Content-Type:  Multpart/related; type=”ediint-cert-exchange+xml”; 
  boundary=foo
   --foo
   Content-Type: Ediint-cert-exchange+xml
     [CEMRequest XML]
   --foo
   Content-Type: Application/pkcs7-mime; smime-type=certs-only
   Content-ID: <[email protected]>
     [end-entity cert being exchanged]
    --foo
   Content-Type: Application/pkcs7-mime; smime-type=certs-only
   Content-ID: <[email protected]>
     [CA cert to complete the trust chain on the end-entity]
    --foo--

The CEMRequest XML would be modified. The <ds:X509Data> element would be
replaced with a new element, say <Content-Id>, which would reference the
MIME Content-ID of the certificate in the multipart-related structure. No
other parts of the XML body would need to be altered.

The use of multipart/related is a natural choice since this was the future
direction of the profile exchange described in section 5 of the draft.

Does the list have comments on this suggestion? Are there other alternatives
we should consider? Unless there is reservations about this choice, the
draft editors will implement this multipart/related structure and resubmit
the updated draft both to the EDIINT list and the IETF area directors end of
next week.

Kyle Meadors
Program Manager
Drummond Group Inc.
615.384.5006


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004