OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [ebxml-dev] EbMS interopability: Content-type start parameternot matching content-id

Title: Re: [ebxml-dev] EbMS interopability: Content-type start parameter not matching  content-id
Hi Julien,

I think you’re right about that both the Lexicom product and the example in the ebMS v2 specification do not comply with RFC 2387. The cid given as the start id should exactly match the one used in the Content-Id MIME header. So in both cases the value of start parameter should be enclosed in “<“ and “>”.

I assume the value “SOAP” is here as an example and was not in the real message as “SOAP” does not comply with RFC 822 regarding the formatting of message id’s?


On 05/10/2009 14:13, "Julien R" <jurenit.jurenit@gmail.com> wrote:

Hi all,
We are testing the EbMS product Lexicom (Cleo communications) and found the following issue:
The Content-type start parameter value doesn't exactly match the content-id value: The < and > symbols are not present in the content-id. Example:
Content-Type: multipart/related; type="text/xml"; boundary="--------CLEOebXML.Boundary.1253712627668.yradnuoB.LMXbeOELC--------"; start=SOAP
First lines of body:
Content-Id: <SOAP>
Content-Type: text/xml

We think Lexicom doesn't follow RFC 2387 because the content-id and start parameter should match exactly.

We have also checked the EbMS v2.0 specification and it contains the following example in section 2.1.2 message package:
Content-Type: multipart/related; type="text/xml"; boundary="boundaryValue"; start=messagepackage-123@example.com
Content-ID: <messagepackage-123@example.com
<mailto:messagepackage-123@example.com> >
Here the start and content-id parameters also do not match. We believe this is a mistake in the EbMS specifications. Further in Appendix B there is an example where the start and content-id do match exactly.
I want to know how this should be implemented and how other EbMS products implement this.
Best regards,

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]