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

Re: BIND issue 3.1_uuids (action item)

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Fri, 14 Jan 2005 12:42:05 -0500
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "'WebDAV'" <w3c-dist-auth@w3.org>, w3c-dist-auth-request@w3.org
Message-ID: <OFEE43A949.1DA1EA1C-ON85256F89.006131A7-85256F89.0061394A@us.ibm.com>
Sounds good to me.

Cheers,
Geoff

Julian wrote on 01/14/2005 11:09:23 AM:

> 
> Hi,
> 
> see 
> <http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.
> html#rfc.issue.3.1_uuids>:
> 
> "Action item: if draft-mealling-uuid-urn gets accepted in time, consider 

> referencing it and using urn:uuid URIs instead of opaquelocktoken URIs. 
> See IETF I-D Tracker."
> 
> In fact, the draft *has* been approved (see 
> 
<https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9352
> >) 
> and now is in the RFC Editor's publication queue: 
> <http://rfc-editor.org/queue.html#mealling-uuid-urn>.
> 
> Thus, I'd propose to
> 
> a) to mention urn:uuid URIs in the description of DAV:resource-id,
> b) to use them in examples and
> c) add an informative reference to draft-mealling-uuid-urn
> 
> Feedback appreciated, Julian
> 
> 
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
> 
Received on Friday, 14 January 2005 17:42:29 GMT

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