- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 23 Apr 2010 16:52:41 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv2734
Modified Files:
wst.html wst.xml
Log Message:
just some overly anal reformatting
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -d -r1.114 -r1.115
--- wst.xml 23 Apr 2010 15:31:52 -0000 1.114
+++ wst.xml 23 Apr 2010 16:52:38 -0000 1.115
@@ -99,178 +99,176 @@
<div1 id="intro">
<head>Introduction</head>
+ <p>
+ This specification defines a mechanism for acquiring XML-based
+ representations of entities using the Web service infrastructure.
+ It defines two types of entities:
+ </p>
+
+ <ulist>
+ <item>
[...2328 lines suppressed...]
+ strong symmetric key provides sufficient accountability. However, in some
+ environments, strong PKI signatures are needed.
+ </p>
+ </item>
+ <item>
+ <p>
+ <emph>Availability</emph> - All reliable messaging services are
+ subject to a variety of availability attacks. Replay detection is a
+ common attack and it is RECOMMENDED that this be addressed by the
+ mechanisms described in WS-Security. Other attacks, such as network-level
+ denial of service attacks are harder to avoid and are outside the scope
+ of this specification. That said, care SHOULD be taken to ensure that
+ minimal state is saved prior to any authenticating sequences.
+ </p>
+ </item>
+ </ulist>
+ </div1>
<div1 id="metadata">
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- wst.html 23 Apr 2010 15:31:52 -0000 1.117
+++ wst.html 23 Apr 2010 16:52:38 -0000 1.118
@@ -83,89 +83,87 @@
client policy.
</p></div><div class="div1">
<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
- This specification defines a mechanism for acquiring XML-based
- representations of entities using the Web service infrastructure.
- It defines two types of entities:
+ This specification defines a mechanism for acquiring XML-based
+ representations of entities using the Web service infrastructure.
+ It defines two types of entities:
+ </p><ul><li><p>
+ Resources, which are entities addressable by an endpoint
[...1057 lines suppressed...]
- of this specification. That said, care SHOULD be taken to ensure that
- minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
+ </p></li><li><p><em>Authentication</em> - Authentication is established using
+ the mechanisms described in WS-Security and WS-Trust. Each message is
+ authenticated using the mechanisms described in WS-Security.
+ </p></li><li><p><em>Accountability</em> - Accountability is a function of the
+ type of and string of the key and algorithms being used. In many cases, a
+ strong symmetric key provides sufficient accountability. However, in some
+ environments, strong PKI signatures are needed.
+ </p></li><li><p><em>Availability</em> - All reliable messaging services are
+ subject to a variety of availability attacks. Replay detection is a
+ common attack and it is RECOMMENDED that this be addressed by the
+ mechanisms described in WS-Security. Other attacks, such as network-level
+ denial of service attacks are harder to avoid and are outside the scope
+ of this specification. That said, care SHOULD be taken to ensure that
+ minimal state is saved prior to any authenticating sequences.
+ </p></li></ul></div><div class="div1">
<h2><a name="metadata" id="metadata"/>8 WS-Transfer Metadata</h2><p>
An endpoint MAY indicate its support of WS-Transfer, or its features,
by including the WS-Transfer TransferResource or TransferResourceFactory
Received on Friday, 23 April 2010 16:52:42 UTC