Re: [Bug 23] lock discovery vs shared locks

Proposed resolution for 
<http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=23>:

Section 6., para. 14:
OLD:

    A lock token is a type of state token, represented as a URI, which
    identifies a particular lock.  A lock token is returned in the Lock-
    Token header in the response to a successful LOCK operation.  The
    lock token also appears in the value of the lockdiscovery property,
    the value of which is returned in the body of the response to a
    successful LOCK operation (this property also includes the tokens of
    other current locks on the resource).  Finally, the lockdiscovery
    property can be queried using PROPFIND and the token can be
    discovered that way.  Each lock has only one unique lock token.

NEW:

    A lock token is a type of state token, represented as a URI, which
    identifies a particular lock.  Each lock has exactly one unique lock
    token, which is returned upon a successful LOCK creation operation in
    the "Lock-Token" response header defined in Section 9.6.


Best regards, Julian

--- draft-ietf-webdav-rfc2518bis-07.xml	2005-10-15 19:19:46.000000000 +0100
+++ rfc2518bis-08-bug23.xml	2005-10-15 19:48:16.000000000 +0100
@@ -616,17 +616,13 @@
   </section>
   
   <section title="Lock Tokens">
-    <t>
-   A lock token is a type of state token, represented as a URI, which 
-   identifies a particular lock.  A lock token is returned in the Lock-
-   Token header in the response to a successful LOCK operation. The 
-   lock token also appears in the value of the lockdiscovery property, 
-   the value of which is returned in the body of the response to a 
-   successful LOCK operation (this property also includes the tokens of 
-   other current locks on the resource).  Finally, the lockdiscovery 
-   property can be queried using PROPFIND and the token can be 
-   discovered that way. Each lock has only one unique lock token.  
-    </t>
+  <t>
+   A lock token is a type of state token, represented as a URI, which
+   identifies a particular lock.  Each lock has exactly one unique lock
+   token, which is returned upon a successful LOCK creation operation in
+   the "Lock-Token" response header defined in
+   <xref target="HEADER_Lock-Token"/>.
+  </t>
     <t>
    Lock token URIs MUST be unique across all resources for all time. 
    This uniqueness constraint allows lock tokens to be submitted across 
@@ -3337,7 +3333,7 @@
     </section>
   </section>
   
-  <section title="Lock-Token Header">
+  <section title="Lock-Token Header" anchor="HEADER_Lock-Token">
     <t>
    Lock-Token = "Lock-Token" ":" Coded-URL 
     </t>