CORE-52 Proposal

[Pete Wenzel <pete.wenzel@Sun.COM>]

Section 7.4, Encrypting Messages

Issue: How can a containing element eb:Messaging be encrypted while a
contained element eb:PartyInfo is not?


Old:

An MSH Implementation may encrypt the eb:Messaging Container Element.
The eb:PartyInfo section may be used to aid in message routing before
decryption has occurred. It is RECOMMENDED that the eb:PartyInfo
section not be encrypted. To ensure the confidentiality of the user-
specified payload data  it is RECOMMENDED that the SOAP Body is
encrypted.

New:

An MSH Implementation may encrypt the eb:Messaging Container Element.
It may also encrypt select child elements of the eb:Messaging header,
leaving other elements unencrypted.  For example, the eb:PartyInfo
section may be used to aid in message routing before decryption of
other elements has occurred. Therefore, it is RECOMMENDED that the
eb:PartyInfo section not be encrypted. To ensure the confidentiality
of the user-specified payload data, it is RECOMMENDED that the SOAP
Body be encrypted.

--Pete
Pete Wenzel <pete.wenzel@sun.com>
Sun Microsystems, SOA & Business Integration
Standards & Product Strategy
+1 (626)471-6311, Sun x61311, US-Pacific TZ