Re: [wss] Comments on WSS: SOAP Message Security

[Anthony Nadalin <drsecure@us.ibm.com>]

Thanks very much, all issues will be in the next update except for items listed below:

>#1: Lines 181-184: When will we figure out what to replace the "####"'s in the 2 namespaces? :)

When we get final approval on document

>#9: Line 524: Should there be a /wsse:UsernameToken/Username/{any}?

Any real need ? If so we should open an item for next version.

>#12: Line 586: Is there a "#HexBinary"??? If #Base64Binary is the default, what are the other options? :)

This was decided that #Base64Binary would be the only option

#13: Line 591: Should there be a /wsse:BinarySecurityToken/{any} as well

Any real need ? If so we should open an item for next version.

>#14: Line 748: Is there a "#HexBinary"??? If #Base64Binary is the default, what are the other options? :)

This was decided that #Base64Binary would be the only option

>#15: Line 752: Should there be a /wsse:SecurityTokenReference/KeyIdentifier/{any}?

This was decided that #Base64Binary would be the only option

>#45: Line 1278-1282: Should we add wsse:Nonce to the example? BTW, Where are Nonce's discussed in the spec? Appendix A just has wsu namespace stuff

We moved this over to the UsernameToken profile.

>#50: Line 1329-1343: Should we add wsse:Nonce to the example? BTW, Where are Nonce's discussed in the spec? Appendix A just has wsu namespace stuff

We moved this over to the UsernameToken profile.

Anthony Nadalin | work 512.436.9568 | cell 512.289.4122