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

[Bug 172] New: Whether to obsolete 'opaquelocktoken', keep it, or remove it

From: <bugzilla@soe.ucsc.edu>
Date: Mon, 24 Oct 2005 10:47:41 -0700
Message-Id: <200510241747.j9OHlf5O015740@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

           Summary: Whether to obsolete 'opaquelocktoken', keep it, or
                    remove it
           Product: WebDAV-RFC2518-bis
           Version: -07
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: lisa@osafoundation.org
        ReportedBy: lisa@osafoundation.org
         QAContact: w3c-dist-auth@w3.org


Now that the UUID RFC defines 'urn:uuid:' we don't need a separate scheme to use
for unique lock tokens.  I've sent mail to IANA so they can clarify what would
happen in their registry if we removed mention of 'opaquelocktoken' in
RFC2518bis or whether we can obsolete it.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Monday, 24 October 2005 17:47:54 GMT

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