W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

[Bug 186] opaquelocktoken appendix

From: <bugzilla@soe.ucsc.edu>
Date: Fri, 9 Dec 2005 17:18:36 -0800
Message-Id: <200512100118.jBA1Iak4006359@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=186

lisa@osafoundation.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |ASSIGNED



------- Additional Comments From lisa@osafoundation.org  2005-12-09 17:18 -------
  The 'opaquelocktoken' URI scheme was defined in RFC2518 (and registered
    by IANA) in order
    to create syntactically correct and easy-to-generate URIs out of UUIDs,
    intended to be used as lock tokens and to be unique across all 
   resources for all time.
    
   An opaquelocktoken URI is constructed by concatenating the 'opaquelocktoken' 
   scheme with a UUID, along with an optional extension.  
   Servers can create new UUIDs for each new lock token.  If a server wishes to 
   reuse UUIDs the server MUST add an extension and
     the algorithm generating the extension MUST guarantee that the same 
     extension will never be used twice with the associated UUID. 



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Saturday, 10 December 2005 01:19:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:11 GMT