NEW Issue: It should be more clear as to which token is used by a protection assertion

["Tony Gullotta" <tony.gullotta@soa.com>]

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSION THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. 

The issues coordinators will notify the list when that has occurred.

Protocol:  ws-sp

http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/22530/ws-securitypolicy-1.2-spec-ed-02-r1-diff.pdf 

Artifact:  spec

Type:    editorial

Title:    It should be more clear as to which token is used by a protection assertion 

Description:

On the 2/13 call there was some debate about whether or not the tokens identified in a binding assertion would be used for SignedParts, SignedElements, EncryptedParts, EncryptedElements assertions attached to a message. As there is no other place to specify the tokens to use for these assertions (as opposed to supporting tokens assertions that embed these assertions directly), it should be very clear that the binding assertion must be used.

Related issues: 

Proposed Resolution:

Add to the text in the binding assertion section or the SignedParts, SignedElements, EncryptedParts, EncryptedElements assertions sections to make the connection more obvious.