Action Items 2005-08-23-02 and 2005-08-23-04: Propose text for Issue 405 and 429

["Martin Gudgin" <mgudgin@microsoft.com>]

I had two actions from the call last week to work with Corinna and the
editors to come up with text to address Issues 405 and 429. Here is such
text, but I would note that there is still disagreement between some of
the parties to the discussion as to whether this text is indeed what we
want. The disagreement centres around whether we should *require*
wsse:SecurityTokenReference/wsse11:TokenType. The text below only
requires it to have a specific value if it is present.

I post it at this time mainly because I will be unable to attend the
call on Tuesday and do not want to delay the TC from coming to a
decision.

Regards

Gudge


The proposal is that the text in line 1081-1-90 be re-written as
follows;

	"The <wsse:SecurityTokenReference> element MUST contain a
<wsse:KeyIdentifier> element. The wsse11:TokenType attribute on the
<wsse:SecurityTokenReference> element MUST be set to
http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-soap-message-sec
urity-1.1#EncryptedKey, if present. The EncodingType attribute on the
<wsse:KeyIdentifier> element SHOULD be set to #Base64Binary. Other
encoding types MAY be specified if agreed on by all parties.  The
identifier for a <xenc:EncryptedKey> token is defined as the SHA1 of the
raw (pre-base64 encoding) octets specified in the <xenc:CipherValue>
element of the referenced <xenc:EncryptedKey> token. This value is
encoded as indicated in the KeyIdentifier reference. The ValueType
attribute on the <wsse:KeyIdentifier> element MUST be set to
http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-soap-message-sec
urity-1.1#EncryptedKeySHA1."