2006/ws/policy ws-policy-framework.xml,1.81,1.82 ws-policy-framework.html,1.65,1.66

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv9871

Modified Files:
	ws-policy-framework.xml ws-policy-framework.html 
Log Message:
Re-formatted the example in 5.5 Denial of Service Threats.

Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -d -r1.81 -r1.82
--- ws-policy-framework.xml	2 Nov 2006 18:28:40 -0000	1.81
+++ ws-policy-framework.xml	3 Nov 2006 20:44:48 -0000	1.82
@@ -1399,30 +1399,30 @@
         <example id="ex-chained-policy-reference-elements">
             <head>Chained Policy Reference Elements</head>
             <eg xml:space="preserve" role="needs-numbering">&lt;Policy wsu:Id="p1"&gt;
-                &lt;PolicyReference URI="#p2"/ &gt;
-                &lt;PolicyReference URI="#p2"/&gt;
-                &lt;/Policy&gt;
+  &lt;PolicyReference URI="#p2"/ &gt;
+  &lt;PolicyReference URI="#p2"/&gt;
+&lt;/Policy&gt;
                 
-                &lt;Policy wsu:Id="p2" &gt;
-                &lt;PolicyReference URI="#p3"/&gt;
-                &lt;PolicyReference URI="#p3"/&gt;
-                &lt;/Policy&gt;
+&lt;Policy wsu:Id="p2" &gt;
+  &lt;PolicyReference URI="#p3"/&gt;
+  &lt;PolicyReference URI="#p3"/&gt;
+&lt;/Policy&gt;
                 
-                &lt;Policy wsu:Id="p3" &gt;
-                &lt;PolicyReference URI="#p4"/&gt;
-                &lt;PolicyReference URI="#p4"/&gt;
-                &lt;/Policy&gt;
+&lt;Policy wsu:Id="p3" &gt;
+  &lt;PolicyReference URI="#p4"/&gt;
+  &lt;PolicyReference URI="#p4"/&gt;
+&lt;/Policy&gt;
                 
-                &lt;!-- Policy/@wsu:Id p4 through p99 --&gt;
+&lt;!-- Policy/@wsu:Id p4 through p99 --&gt;
                 
-                &lt;Policy wsu:Id="p100" &gt;
-                &lt;PolicyReference URI="#p101"/&gt;
-                &lt;PolicyReference URI="#p101"/&gt;
-                &lt;/Policy&gt;
+&lt;Policy wsu:Id="p100" &gt;
+  &lt;PolicyReference URI="#p101"/&gt;
+  &lt;PolicyReference URI="#p101"/&gt;
+&lt;/Policy&gt;
                 
-                &lt;Policy wsu:Id="p101" &gt;
-                &lt;mtom:OptimizedMimeSerialization /&gt;
-                &lt;/Policy&gt;</eg>
+&lt;Policy wsu:Id="p101" &gt;
+  &lt;mtom:OptimizedMimeSerialization /&gt;
+&lt;/Policy&gt;</eg>
         </example>
         <p>Malicious providers may provide a policy expression that includes multiple
             PolicyReference elements that use a large number of different internet addresses. These
@@ -2090,7 +2090,13 @@
                         <td>ASV</td>
                         <td>Reset Section <specref ref="change-description"/>.
                         </td>
-                    </tr>                                        
+                    </tr>
+                    <tr>
+                        <td>20061103</td>
+                        <td>ASV</td>
+                        <td>Re-formatted the example in <specref ref="denial-of-service-threats"/>.
+                        </td>
+                    </tr>                                          
                 </tbody>
             </table>
         </inform-div1>

Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- ws-policy-framework.html	2 Nov 2006 18:28:40 -0000	1.65
+++ ws-policy-framework.html	3 Nov 2006 20:44:48 -0000	1.66
@@ -888,30 +888,30 @@
             anticipate these rogue providers and use a configurable bound with defaults on number of
             policy alternatives, number of assertions in an alternative, depth of nested policy
             expressions, etc.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="ex-chained-policy-reference-elements"></a><i><span>Example 5-1. </span>Chained Policy Reference Elements</i></p><div class="exampleInner"><pre>(01) &lt;Policy wsu:Id="p1"&gt;
-(02)                 &lt;PolicyReference URI="#p2"/ &gt;
-(03)                 &lt;PolicyReference URI="#p2"/&gt;
-(04)                 &lt;/Policy&gt;
+(02)   &lt;PolicyReference URI="#p2"/ &gt;
+(03)   &lt;PolicyReference URI="#p2"/&gt;
+(04) &lt;/Policy&gt;
 (05)                 
-(06)                 &lt;Policy wsu:Id="p2" &gt;
-(07)                 &lt;PolicyReference URI="#p3"/&gt;
-(08)                 &lt;PolicyReference URI="#p3"/&gt;
-(09)                 &lt;/Policy&gt;
+(06) &lt;Policy wsu:Id="p2" &gt;
+(07)   &lt;PolicyReference URI="#p3"/&gt;
+(08)   &lt;PolicyReference URI="#p3"/&gt;
+(09) &lt;/Policy&gt;
 (10)                 
-(11)                 &lt;Policy wsu:Id="p3" &gt;
-(12)                 &lt;PolicyReference URI="#p4"/&gt;
-(13)                 &lt;PolicyReference URI="#p4"/&gt;
-(14)                 &lt;/Policy&gt;
+(11) &lt;Policy wsu:Id="p3" &gt;
+(12)   &lt;PolicyReference URI="#p4"/&gt;
+(13)   &lt;PolicyReference URI="#p4"/&gt;
+(14) &lt;/Policy&gt;
 (15)                 
-(16)                 &lt;!-- Policy/@wsu:Id p4 through p99 --&gt;
+(16) &lt;!-- Policy/@wsu:Id p4 through p99 --&gt;
 (17)                 
-(18)                 &lt;Policy wsu:Id="p100" &gt;
-(19)                 &lt;PolicyReference URI="#p101"/&gt;
-(20)                 &lt;PolicyReference URI="#p101"/&gt;
-(21)                 &lt;/Policy&gt;
+(18) &lt;Policy wsu:Id="p100" &gt;
+(19)   &lt;PolicyReference URI="#p101"/&gt;
+(20)   &lt;PolicyReference URI="#p101"/&gt;
+(21) &lt;/Policy&gt;
 (22)                 
-(23)                 &lt;Policy wsu:Id="p101" &gt;
-(24)                 &lt;mtom:OptimizedMimeSerialization /&gt;
-(25)                 &lt;/Policy&gt;</pre></div></div><p>Malicious providers may provide a policy expression that includes multiple
+(23) &lt;Policy wsu:Id="p101" &gt;
+(24)   &lt;mtom:OptimizedMimeSerialization /&gt;
+(25) &lt;/Policy&gt;</pre></div></div><p>Malicious providers may provide a policy expression that includes multiple
             PolicyReference elements that use a large number of different internet addresses. These
             may require the consumers to establish a large number of TCP connections. Policy
             implementers need to anticipate such rogue providers and use a configurable bound with
@@ -1261,4 +1261,5 @@
                             <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Nov/0001.html">resolution</a> 
                             for Editors' Action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/12">12</a>.
                         </td></tr><tr><td rowspan="1" colspan="1">20061102</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Reset Section <a href="#change-description"><b>C. Changes in this Version of the Document</b></a>.
+                        </td></tr><tr><td rowspan="1" colspan="1">20061103</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Re-formatted the example in <a href="#denial-of-service-threats"><b>5.5 Denial of Service Threats</b></a>.
                         </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file

Received on Friday, 3 November 2006 20:44:59 UTC