[OASIS Issue Tracker] (EBXMLMSG-19) AS4 does not support external payloads

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EBXMLMSG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61798#comment-61798 ] 

Pim van der Eijk commented on EBXMLMSG-19:
------------------------------------------

It is useful to be able to express whether the feature is supported at all (in a profile and/or in a product).    For AS4, no support would be needed (though products may support it optionally).  Profiles that are based on AS4 would then inherit this constraint, meaning they would not support the feature unless they explicitly specify so. That clarifies the situation for current AS4 users and implementers.

The second step would be to define what the feature means, if used.    I think there are several aspects:
1)  Payload handling. Payloads are submitted to the MSH and delivered by the MSH.  They are not transported as ebMS3 payloads but made only referenced, the R-MSH must retrieve it using a separate (non-ebMS3) mechanism. 
2)  Security handling.  Here I would like to be more ambitious and require that the same security is applied to the external payloads, i.e. that they can be signed and encrypted.  Otherwise this feature would have very limited added value compared to just having some hyperlink in the business application.
3)  Semantics of receipt.  Does an R-MSH acknowledge receipt for the AS4 message or for the message including payloads, i.e. does a receipt mean the R-MSH successfully downloaded the external payloads. I think the latter.  We could define a separate signal to flag that the R-MSH got the AS4 message (meaning no retries are needed) but has not yet retrieved the payloads.  A bit like the EBMS:0060 error for the alternate MEP feature in Part 2, but rather than an obligation on the S-MSH more a promise by R-MSH that it will attempt to retrieve the payloads,


> AS4 does not support external payloads
> --------------------------------------
>
>                 Key: EBXMLMSG-19
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-19
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>            Reporter: Pim van der Eijk
>
> Add a clarification that AS4 does not require support for external payloads.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)