000f01c8fc3a$f04dea80$efe26550@VaioSX" type="cite">
Hello,
On 7.4, where you are saying
that The eb:PartyInfo section SHALL NOT be encrypted,
are you assuming that the AS4 user community would never want route
messages based on other eb:UserMessage elements like eb:Service?
(My interest is that I would like the
multihop profile to be composable with this profile, so that end user
communities can adopt either or both of these profile as fits their
requirements).
Pim
I'd like to make the
following profiling proposals for AS4 for Section 7 of the ebMS v3
Spec. Please comment and provide feedback.
7.2 Signing Messages
AS4 messages SHALL NOT use Enveloped Signatures. Only Detached
Signatures will be supported for signing user messages and signal
messages.
The entire eb:Messaging Container Element and the SOAP Body MUST be
included in the signature.
7.3 Signing SOAP with Attachments Messages
AS4 messages that are packaged using SOAP with Attachments SHALL NOT
use the Attachment-Complete transform. Only the
Attachment-Content-Only transform will be used.
The entire eb:Messaging Container Element and all MIME body parts MUST
be included in the signature.
7.4 Encrypting Messages
The eb:PartyInfo section SHALL NOT be encrypted.
The SOAP Body MUST be encrypted.
7.5 Encrypting SOAP with Attachments Messages
MIME body parts of included payloads MUST be encrypted.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php