- From: Glen Daniels <gdaniels@macromedia.com>
- Date: Wed, 30 Jan 2002 00:17:31 -0500
- To: "'ohurley@iona.com'" <ohurley@iona.com>
- Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Hi Oisin! On today's (yesterday's?) TBTF concall I took an action to write up this brief resolution to XMLP issue #58 [1], which came up as a result of your email [2] cross-checking SOAP against the requirements list. Essentially the issue was to confirm that SOAP 1.2 does not preclude transport bindings which provide security. Proposed resolution : The TBTF has been explicitly using security as an anecdotal example when discussing binding "features" as described in the transport binding framework. As has been noted by Marwan, bindings to protocols such as HTTPS and S/MIME are possible with the framework, and we fully expect that such bindings may be specified in the future. We therefore believe that the issue has been resolved, and secure bindings (in particular bindings where the security semantic is communicated in a useful way to the application) are not precluded in SOAP 1.2. Thanks, and please let us know if you have issues with this resolution. --Glen [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x58 [2] http://lists.w3.org/Archives/Public/xml-dist-app/2001Jan/0148.html
Received on Wednesday, 30 January 2002 00:11:40 UTC