[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: WSS text
Here's text, wrt Working Draft 16: Page 22, lines 722-723: s/Profiles must define what value is implied if a specific value is not specified/If no value is specified then the key identifier will be interpreted in an application-specific manner/ Page 25, lines 825-830 Page 26, lines 857-859 These seem to still strongly RECOMMEND exc-c14n. Page 27, line 927 s/XML security token/XML security token (e.g., a SAML assertion or a wsse:BinarySecurityToken element)/ Page 27, line 928 s/binary security token/raw binary security token; i.e., an octet stream/ Page 27, line 935 s/prefix x/prefix x, or else the prefix y if Ri uses x/ I will post some interop samples for this transform. Page 36, lines 1298-1300 wsse:KeyIdentifier is not a valid child of xenc:EncryptedKey; it must be wrapped in a ds:KeyInfo. Page 37, line 1373 s/name of the key/identifier of the key/ Page 42, line 1511 s/implementtaions/implementations/ merlin ----------------------------------------------------------------------------- The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Baltimore Technologies plc will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. This footnote confirms that this email message has been swept for Content Security threats, including computer viruses. http://www.baltimore.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]