- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 24 Jan 2007 04:33:06 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv28611
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Fixed a typo in A.2 Other References: "[IETF RFC 3023]IETF "RFC 2246:".
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -d -r1.83 -r1.84
--- ws-policy-attachment.xml 24 Jan 2007 04:10:41 -0000 1.83
+++ ws-policy-attachment.xml 24 Jan 2007 04:33:03 -0000 1.84
@@ -2523,7 +2523,7 @@
<head>Other References</head>
<blist>
- <bibl key="IETF RFC 3023"
+ <bibl key="IETF RFC 2246"
href="http://www.ietf.org/rfc/rfc2246.txt" id="RFC2246">IETF
"RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
1999.</bibl>
@@ -3244,7 +3244,13 @@
to section <specref ref="ws-policy-attachment-for-wsdl20"/>: added wsp prefix to <specref ref="table-wsdl20-effective-policy-example"/>
and all occurrences of <el>Policy</el> and <el>PolicyReference</el>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070123</td>
+ <td>ASV</td>
+ <td>Fixed a typo in <specref ref="Informative-References"/>: "[IETF RFC 3023]IETF "RFC 2246:".
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -d -r1.82 -r1.83
--- ws-policy-attachment.html 24 Jan 2007 04:10:41 -0000 1.82
+++ ws-policy-attachment.html 24 Jan 2007 04:33:03 -0000 1.83
@@ -1392,7 +1392,7 @@
digitally sign their <a title="" href="#policy_expression">policy expression</a> tModels or <a title="" href="#policy_expression">policy expression</a>
references in UDDI <span class="rfc2119">MUST</span> use the Schema-centric
canonicalization algorithm [<cite><a href="#SCC14N">SCC14N</a></cite>].</p></div></div><div class="div1">
-<h2><a name="SecurityConsiderations"></a>7. Security Considerations</h2><p>It is <span class="rfc2119">RECOMMENDED</span> that <a title="" href="#policy_attachment">policy attachments</a> be integrity protected to permit the detection of tampering. This can be done using a technology such as XML DSig [<cite><a href="#XML-Signature">XML-Signature</a></cite>], SSL/TLS [<cite><a href="#RFC2246">IETF RFC 3023</a></cite>], or WS-Security 2004 [<cite><a href="#WS-Security">WS-Security 2004</a></cite>]. This also provides a mechanism for
+<h2><a name="SecurityConsiderations"></a>7. Security Considerations</h2><p>It is <span class="rfc2119">RECOMMENDED</span> that <a title="" href="#policy_attachment">policy attachments</a> be integrity protected to permit the detection of tampering. This can be done using a technology such as XML DSig [<cite><a href="#XML-Signature">XML-Signature</a></cite>], SSL/TLS [<cite><a href="#RFC2246">IETF RFC 2246</a></cite>], or WS-Security 2004 [<cite><a href="#WS-Security">WS-Security 2004</a></cite>]. This also provides a mechanism for
authenticating <a title="" href="#policy_attachment">policy attachments</a> by determining if the signer has the
right to "speak for" the scope of the <a title="" href="#policy_attachment">policy attachment</a>.</p><p>Policies <span class="rfc2119">SHOULD NOT</span> be accepted unless they are
signed and have an associated security token to specify the signer has
@@ -1537,7 +1537,7 @@
Schema Part 1</a> is available at
http://www.w3.org/TR/xmlschema-1.
</dd></dl></div><div class="div2">
-<h3><a name="Informative-References"></a>A.2 Other References</h3><dl><dt class="label"><a name="RFC2246"></a>[IETF RFC 3023] </dt><dd>IETF
+<h3><a name="Informative-References"></a>A.2 Other References</h3><dl><dt class="label"><a name="RFC2246"></a>[IETF RFC 2246] </dt><dd>IETF
"RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
1999. (See <cite><a href="http://www.ietf.org/rfc/rfc2246.txt">http://www.ietf.org/rfc/rfc2246.txt</a></cite>.)</dd><dt class="label"><a name="WSDL11EI"></a>[WSDL11 ElementIds] </dt><dd>
<cite><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html">WSDL 1.1 Element Identifiers</a></cite>
@@ -1870,4 +1870,5 @@
issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4226">4226</a>)
to section <a href="#ws-policy-attachment-for-wsdl20"><b>5. WS-Policy Attachment for WSDL 2.0</b></a>: added wsp prefix to <a href="#table-wsdl20-effective-policy-example">Example 5-2</a>
and all occurrences of <code class="elt">Policy</code> and <code class="elt">PolicyReference</code> .
+ </td></tr><tr><td rowspan="1" colspan="1">20070123</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Fixed a typo in <a href="#Informative-References"><b>A.2 Other References</b></a>: "[IETF RFC 3023]IETF "RFC 2246:".
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 24 January 2007 04:33:13 UTC