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

Re: URI spec RFC2396 obsoleted by RFC3986

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 16 Nov 2005 09:31:45 +0100
Message-ID: <437AEE71.2090500@gmx.de>
To: Lisa Dusseault <lisa@osafoundation.org>
CC: WebDav WG <w3c-dist-auth@w3.org>

Lisa Dusseault wrote:
> 
> RFC 3986 obsoletes RFC2396  (http://www.ietf.org/rfc/rfc3986.txt).  If 
> 2518bis refers to 3986, this will cause some changes.
> 
> 1.  WebDAV uses definitions of "absoluteURI" from the URI spec in the 
> syntax of Destination and If headers:
> 
>      Destination = "Destination" ":" ( absoluteURI )
>      ...
>      Coded-URL = "<" absoluteURI ">"
> 
>   RFC2396 defines absolute-URI:
> 
>       absolute-URI  = scheme ":" hier-part [ "?" query ]
> 
>   RFC3986 instead defines absoluteURI:
> 
>       absoluteURI   = scheme ":" ( hier_part | opaque_part )

Yes.

> 2.  WebDAV uses the "path" definition from the URI spec in the 
> definition of Opaquelocktoken
> 
>   OpaqueLockToken-URI = "opaquelocktoken:" UUID [Extension]
>   Extension = path
> 
> Path has the same name in 3986 but its definition changed.

What did actually change?

> 3.  We have an example of what kind of illegal characters in URIs might 
> need to be escaped:
> 
>   "For example, it is illegal to use a space character or double-quote 
> in a URI"

That's not a problem.

> 4.  "DAV:" is now legal!
> 
> 5.  IPv6 addresses are legal...
> 
> 6.  Some new reserved characters: "!", "*", "'", "(", ")"
> 
> I believe the overall WebDAV spec is OK with the new RFC, but others 
> should check too.

Agreed.
Received on Wednesday, 16 November 2005 08:32:46 GMT

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