Pim,
I think this document gives a good description of the options for
addressing response user messages. This helps to identify the
information that might be used for routing messages through the I-
cloud and therefor should be part of the addressing information to be
included in non user messages. I'm not sure if you propose so, but I
don't think here's a need for relating request and response user
messages on the intermediaries. Their only task is to route message
based on the address information contained in them. It the
responsibility of the endpoint MSH's to include all the needed address
information.
Sander
On 20 mei 2008, at 23:01, pvde@sonnenglanz.net wrote:
> The document named Routing and multihop.doc has been submitted by
> Mr. Pim
> van der Eijk to the OASIS ebXML Messaging Services TC document
> repository.
>
> Document Description:
> Discussion on routing and reverse routing.
> Routing criteria.
> Generating a "reverse" response header from a request user message
> header
>
> Pmodes and routing
>
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=28337
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/28337/Routing%20and%20multihop.doc
>
>
> PLEASE NOTE: If the above links do not work for you, your email
> application
> may be breaking the link into two pieces. You may be able to copy
> and paste
> the entire link address into the address field of your web browser.
>
> -OASIS Open Administration