RE: the mime issue in the ms draft

[Marc Breissinger <marcb@webmethods.com>]

> I don't understand what you mean by "breaking" transport independent
> packaging.
> I have personally tested the transport of ebXML messages over HTTP, SMTP and
> FTP without
> any difficulty or abnormal termination.

What Igor means is that the ebXML Envelope is structured differently depending on the transport, so the software that envelopes an
ebXMLHeader with a payload will need to be transport aware -- and accomplish its task differently depending on the transport.  In
other words, it is not a transport independent envelope specification.  No argues that you can make it work with HTTP, SMTP and FTP,
just that the ebXML envelope will be different for each.

> -----Original Message-----
> From: Dick Brooks [mailto:dick@8760.com]
> Sent: Wednesday, September 06, 2000 9:13 AM
> To: Igor Balabine; richard drummond; Ebxml Transport
> Cc: 'Ebxml-Poc
> Subject: RE: the mime issue in the ms draft
>
>
> Igor, see comments inline.
>
> > Besides breaking transport independent packaging (e.g. http vs. ftp) this
>
> I don't understand what you mean by "breaking" transport independent
> packaging.
> I have personally tested the transport of ebXML messages over HTTP, SMTP and
> FTP without
> any difficulty or abnormal termination.
>