- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Mon, 14 Aug 2006 19:01:50 -0700
- To: WebDav WG <w3c-dist-auth@w3.org>
- Message-Id: <53365A60-0B00-409C-8F71-7F814157ABD0@osafoundation.org>
FYI --lisa Begin forwarded message: > From: The IESG <iesg-secretary@ietf.org> > Date: August 14, 2006 6:43:08 PM PDT > To: IETF-Announce <ietf-announce@ietf.org> > Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc- > editor@rfc-editor.org> > Subject: Document Action: 'Mounting Web Distributed Authoring and > Versioning (WebDAV) servers' to Informational RFC > > The IESG has approved the following document: > > - 'Mounting Web Distributed Authoring and Versioning (WebDAV) > servers ' > <draft-reschke-webdav-mount-05.txt> as an Informational RFC > > This document has been reviewed in the IETF but is not the product > of an > IETF Working Group. > > The IESG contact person is Lisa Dusseault. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-reschke-webdav-mount-05.txt > > Technical Summary > > This is a small, focused solution to the problem of advertising a > WebDAV > share, or mountable namespace, in a context where a WebDAV-capable > HTTP URL is > indistinguishable from other display-only HTTP URLs. For example, > in a Web > homepage constructed for students, a university could provide links > to launch a > WebDAV synch client together with the information to mount the > student's online > storage space. > > There was careful discussion including the W3C liaisons as to > whether this was the right approach, compared particularly to the > other common > approach (which doesn't require a Proposed Standard but is > discouraged by W3C > TAG) of defining a new scheme for a new kind of URI. > > > Working Group Summary > > Although this was discussed in the WebDAV WG and received some > support, this > is not a WG product. There was no dissent. > > Protocol Quality > > Lisa Dusseault reviewed this specification for the IESG. > > Note to RFC Editor > > Please update the security considerations with the text discussed > by the IESG. > > OLD: > When mount documents contain user names (using the <dm:username> > element defined in Section 3.4), servers hosting such documents (or > clients creating them) should pay attention to the public > readability > of the document and related privacy concerns. > > NEW: > The OPTIONAL <dm:username> element defined in Section 3.4 allows > the > inclusion of user names into mount documents. However in some > cases, > user name information is considered to be security sensitive. > Should > this be the case, parties generating mount documents are advised to > either not to include user names, or to use access control to > restrict access to the information as desired. > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce
Received on Tuesday, 15 August 2006 02:02:12 UTC