draft-ietf-webdav-quota-00.txt   draft-ietf-webdav-quota-01.txt 
B. Korver
Xythos
L. Dusseault L. Dusseault
Xythos Xythos
Internet Draft C. Warner Internet Draft C. Warner
Document: draft-ietf-webdav-quota-00.txt Netezza Document: draft-ietf-webdav-quota-01.txt Netezza
Expires: April 2003 October 2002 Expires: September 2003 March 2003
Quota and Size Properties for DAV Collections Quota and Size Properties for DAV Collections
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
skipping to change at line 31 skipping to change at line 35
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
WebDAV servers are frequently deployed with collection quota (size) WebDAV servers are frequently deployed with quota (size)
limitations. This Internet-Draft discusses the two properties and limitations. This Internet-Draft discusses the properties and minor
minor behaviors needed for clients to interoperate with quota behaviors needed for clients to interoperate with quota
implementations on WebDAV repositories. implementations on WebDAV repositories.
Table of Contents Table of Contents
Status of this Memo................................................1
Abstract...........................................................1
Introduction.......................................................2 Introduction.......................................................2
Requirement for quotas.............................................2 DAV:quota-limit-bytes..............................................3
Solution Overview..................................................2 DAV:quota-used-bytes...............................................3
Error reporting....................................................5 DAV:quota-assigned-bytes...........................................4
Notes..............................................................5 Example PROPFIND request and response..............................5
Security Considerations............................................6 Error reporting....................................................6
Internationalization Considerations................................6 Notes..............................................................6
IANA Considerations................................................6 Security Considerations............................................7
Intellectual Property..............................................7 Internationalization Considerations................................7
References.........................................................8 IANA Considerations................................................7
Author's Addresses.................................................8
Dusseault Expires April 2003 1 Dusseault Expires March 2003 1
DAV Collection Size and Quota October 2002 DAV Collection Size and Quota January 2003
Intellectual Property..............................................7
Acknowledgements...................................................8
References.........................................................9
Author's Addresses.................................................9
Introduction Introduction
Notational Conventions Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
this document are to be interpreted as described in RFC 2119 document are to be interpreted as described in RFC 2119 [RFC2119].
[RFC2119].
Requirement for quotas Requirement for quotas
WebDAV servers based on [RFC2518] are being implemented and deployed WebDAV servers based on [RFC2518] have been implemented and deployed
with quota restrictions on collections, so it make sense to with quota restrictions on collections and users, so it makes sense
standardize this functionality to improve user experience and client to standardize this functionality to improve user experience and
interoperability. This specification requires WebDAV because it client interoperability. This specification requires WebDAV because
requires PROPFIND support and relies on the WebDAV definition of it requires PROPFIND support and relies on the WebDAV definition of
collections and properties, including the definitions for live and collections and properties, including the definitions for live and
protected properties. protected properties.
The reasons why WebDAV servers frequently have collection quotas The reasons why WebDAV servers frequently have quotas enforced are
enforced are the same reasons why any storage system comes with the same reasons why any storage system comes with quotas.
quotas.
- Sometimes the storage service charges according to quota - Sometimes the storage service charges according to quota
(XDrive.com and www.storeitonline.com have both operated under this
model)
- Sometimes the storage service is provided free, but the storage - Sometimes the storage service is provided free, but the storage
service provider has limited storage space (www.sharemation.com has service provider has limited storage space (e.g. www.sharemation.com
this limitation and university-provided student accounts often do as and university-provided student accounts)
well)
- Even in cases where the storage can be upgraded, the storage - Even in cases where the storage can be upgraded, the storage
managers may choose to impose quotas in order to encourage users to managers may choose to limit quota in order to encourage users to
limit the files they store on the system and to clean up obsolete limit the files they store on the system and to clean up obsolete
files. IT departments within corporations may put quotas on files. (e.g. IT departments within corporations).
storage used by employees.
In order to work best with repositories that support quotas, client In order to work best with repositories that support quotas, client
software should be able to determine and display the quota (limit) software should be able to determine and display the quota-limit on
on any collection. Further, client software should have some way of collections. Further, client software should have some way of
fairly reliably determining how much storage space is already fairly reliably determining how much storage space is already
counted towards the quota. counted towards that quota.
In addition to displaying the quota-limit and quota-used on
collections, this specification does not forbid these properties on
any resource.
Solution Overview Solution Overview
The approach to meeting the requirements and scenarios outlined The approach to meeting the requirements and scenarios outlined
above is simply to define two live properties. This specification above is to define three live properties. This specification can be
can be met on a server by implementing either or both of the
following two properties. Both are recommended.
Dusseault Expires April 2002 2 Korver Expires Jul 2003 2
DAV Collection Size and Quota October 2002 DAV Collection Size and Quota January 2003
Neither property need be returned in a <DAV:allprop> request though met on a server by implementing both quota-limit and quota-used on
the server may include either. However, these property names MUST collections only. Implementing both quota-limit and quota-used on
be returned in a <DAV:propname> request for a resource that supports all resources is recommended.
the properties.
DAV:quota-bytes None of these properties need be returned in a <DAV:allprop> request
though the server may include them. However, these property names
MUST be returned in a <DAV:propname> request for a resource that
supports the properties, except in the case of infinite limits which
are explained below.
Name: quota-bytes The definitions below for quota-limit and quota-used borrow heavily
Namespace: DAV: from the definition of quota in the NFS [RFC3010] specification.
Purpose: Contains the amount of storage space allocated to a
collection, measured in bytes.
DTD: <!ELEMENT quota-bytes (#PCDATA) >
The DAV:quota-bytes property value is the total amount of storage DAV:quota-limit-bytes
space allocated to a collection and all its descendants. The value
of this property will usually be protected, although a user with
sufficient privileges may be permitted to change the value. The
property is useful even if it is protected. A 403 Forbidden response
is recommended for attempts to write a protected property.
A value of 0 indicates that storage is limited to 0. Users will Name: quota-limit-bytes
probably not be able to add resources to the collection. Namespace: DAV:
Purpose: Indicates the total amount of storage potentially
allocated.
DTD: <!ELEMENT quota-limit-bytes (#PCDATA) >
If a collection has no quota enforced, it should not return this The DAV:quota-limit-bytes property value is the total amount of
property at all. A client cannot entirely assume that there is no storage space potentially allocated to this file or directory,
quota enforced on a collection that does not have this property, but measured in octets.
might as well act as if there is no quota.
If the quota on a collection is reduced, the server MUST NOT delete Support for this property is REQUIRED on collections, and OPTIONAL
excess files except as selected by an administrator. Thus, a on other resources. A server SHOULD implement this property for
collection may have more storage used than its quota allows. each resource that has the DAV:quota-used-bytes property.
Quota is not additive. A collection only has the quota assigned to A value of 0 indicates that storage is limited to 0. Users will
it, not (in addition) the quota assigned to sub collections or any probably not be able to perform operations that write additional
other collections. Sub-collections can have different quota values information (e.g. a PUT inside a collection), but may be able to
than parent collections. These ˘sub-quota÷s may act as additional replace through overwrite an existing resource of equal size.
constraints, or they may be under-constrained and have no effect.
This can allow the delegation of quota administration from root
administrators to collection owners.
Thus, if a collection A contains collection B, and both have quotas If a resource has no quota enforced or unlimited storage, the server
of 1,000,000 bytes, then collection A can contain up to 1,000,000 MAY choose not to return this property (404 Not Found response in
bytes including the bytes used by resources in B. Collection B, Multi-Status), although this specification RECOMMENDS that servers
then, can only truly contain 1,000,000 bytes of used storage if A is return some appropriate value (e.g. the amount of free disc space).
empty; it is likely under-constrained. A client cannot entirely assume that there is no quota enforced on a
resource that does not have this property, but might as well act as
if there is no quota.
This property is OPTIONAL on collections and SHOULD NOT exist on The value of this property is protected. A 403 Forbidden response
non-collection resources. When a new collection is created, it is is RECOMMENDED for attempts to write a protected property.
up to the server to initialize the value appropriately if it chooses
to.
DAV:quota-used-bytes DAV:quota-used-bytes
Dusseault Expires April 2002 3
DAV Collection Size and Quota October 2002
Name: quota-used-bytes Name: quota-used-bytes
Namespace: DAV: Namespace: DAV:
Purpose: Contains the amount of storage space used (possibly counted Purpose: Contains the amount of storage counted against the quota-
towards quota) by a collection, measured in bytes. limit of a resource.
DTD: <!ELEMENT quota-used-bytes (#PCDATA) > DTD: <!ELEMENT quota-used-bytes (#PCDATA) >
The DAV:quota-used-bytes value is calculated by the server to Korver Expires Jul 2003 3
indicate approximately how much storage space is already taken up by
this collection and all its descendants (in bytes). It MUST include
child collections and all resources inside those child collections.
It SHOULD include metadata storage size if metadata storage is
counted against quota limitations. Support for this property is
OPTIONAL on collections and SHOULD NOT exist on non-collection
resources. A server SHOULD implement this property to the best of
its ability if it implements the DAV:quota-bytes property.
The value SHOULD be an accurate account of how the server counts DAV Collection Size and Quota January 2003
what is stored against quota. Servers MUST NOT implement this
property unless the value is at least as accurate as the client The DAV:quota-used-bytes value is the value in octets representing
could calculate itself by summing values for ˘getcontentlength÷. the amount of space used by this file or directory and possibly a
number of other similar files or directories, where the set of
˘similar÷ meets at least the criterion that allocating space to any
file or directory in the set will count against the quota-limit. It
MUST include the total count including usage derived from sub-
resources if appropriate. It SHOULD include metadata storage size
if metadata storage is counted against the quota-limit.
Clients SHOULD expect that once the quota-used on a file or
directory meets or exceeds the quota-limit, further allocations to
that file or directory will be refused. A resource may show more
quota-used than its quota-limit or quota-assigned appears to allow.
Note that there may be a number of distinct but overlapping sets of
files or directories for which a quota-used is maintained (e.g. ˘all
files with a given owner÷, ˘all files with a given group owner÷,
etc.). The server is at liberty to choose any of those sets but
SHOULD do so in a repeatable way. The rule may be configured per
repository, or may be ˘choose the set with the smallest quota÷.
Support for this property is REQUIRED on collections, and OPTIONAL
on other resources. A server SHOULD implement this property for
each resource that has the DAV:quota-limit-bytes property.
Support for this property enhances the client experience, because Support for this property enhances the client experience, because
together with DAV:quota-bytes, the client can manage its files to together with DAV:quota-limit-bytes, the client has a chance of
avoid running out of allocated storage space. Clients may not be managing its files to avoid running out of allocated storage space.
able to calculate the value adequately on their own, depending on Clients may not be able to calculate the value as accurately on
how total space used is calculated by the server. their own, depending on how total space used is calculated by the
server.
Note that it is entirely possible for a server to support DAV:quota- DAV:quota-assigned-bytes
used-bytes without supporting DAV:quota-bytes or any kind of quota
system, in which case the value should represent the amount of space Name: quota-assigned-bytes
used in the collection and its descendants. Namespace: DAV:
Purpose: Indicates the amount of storage assigned.
DTD: <!ELEMENT quota-bytes (#PCDATA) >
The DAV:quota-assigned-bytes property value is the amount of storage
space potentially either assigned to or requested for this file or
directory, measured in octets.
The value of this property will usually be protected, although a
user with sufficient privileges may be permitted to change the
value. The property is useful even if it is protected. A 403
Forbidden response is RECOMMENDED for attempts to write a protected
property.
Support for this property is OPTIONAL.
Note that a resource may show more quota-used than its quota-
assigned appears to allow, and that quota-assigned MUST NOT be less
Korver Expires Jul 2003 4
DAV Collection Size and Quota January 2003
than the quota-limit. Servers which receive a request to change
quota-assigned to a value less than quota-limit MUST reduce quota-
limit to this value at the same time.
For many quota systems, quota-assigned is synonymous with quota-
limit. However, in any system, quota-limit is a hard limit. For
example, imagine a quota system where each collection may have a
quota assigned and where a resource contained in a collection is
subject to the quota constraints of all parent collections. Assume
the administrator creates a collection A and gives it a quota-
assigned of 1,000,000 bytes and then creates a sub-collections B
which is given quota-assigned of 10,000,000 bytes. In this case,
the quota-limit for B is 1,000,000 bytes.
Example PROPFIND request and response Example PROPFIND request and response
Request: Request:
PROPFIND /~milele/public/ HTTP/1.1 PROPFIND /~milele/public/ HTTP/1.1
Depth: 0 Depth: 0
Host: www.sharemation.com Host: www.sharemation.com
Content-Type: text/xml Content-Type: text/xml
Content-Length: 200 Content-Length: xxx
<?xml version="1.0" ?> <?xml version="1.0" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop><D:quota-bytes><D:quota-used-bytes></D:prop> <D:prop><D:quota-limit-bytes><D:quota-used-bytes></D:prop>
</D:propfind> </D:propfind>
Response: Response:
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Date: Tue, 16 Oct 2001 22:13:39 GMT Date: Tue, 16 Oct 2001 22:13:39 GMT
Content-Length: xxx Content-Length: xxx
Content-Type: text/xml; charset=UTF-8 Content-Type: text/xml; charset=UTF-8
Dusseault Expires April 2002 4
DAV Collection Size and Quota October2002
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.sharemation.com/~milele/public/</D:href> <D:href>http://www.sharemation.com/~milele/public/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:quota-bytes>1000000</D:quota-bytes> <D:quota-limit-bytes>1000000</D:quota-limit-bytes>
<D:quota-used-bytes>4403350</quota-used-bytes> <D:quota-used-bytes>403350</quota-used-bytes>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
Korver Expires Jul 2003 5
DAV Collection Size and Quota January 2003
Error reporting Error reporting
WebDAV (RFC2518) defines the status code 507 (Insufficient Storage). WebDAV (RFC2518) defines the status code 507 (Insufficient Storage).
This status code SHOULD be used when a client request (e.g. a PUT, This status code SHOULD be used when a client request (e.g. a PUT,
PROPFIND, MKCOL, MOVE or COPY) is forbidden because it would exceed PROPFIND, MKCOL, MOVE or COPY) is forbidden because it would exceed
their allotted quota. In order to differentiate the response from their allotted quota. In order to differentiate the response from
other storage problems, the server SHOULD include an XML error body other storage problems, the server SHOULD include an XML error body
as defined by DeltaV [RFC??] with the <DAV:storage-quota-reached/> as defined by DeltaV [RFC3253] with the <DAV:storage-quota-reached/>
precondition tag. precondition tag.
Example error response: Example error response:
HTTP/1.1 507 Insufficient Storage HTTP/1.1 507 Insufficient Storage
Content-Length: 100 Content-Length: 100
Content-Type: text/xml Content-Type: text/xml
<?xml version=÷1.0÷> <?xml version=÷1.0÷>
<error xmlns=÷DAV:÷> <error xmlns=÷DAV:÷>
<storage-quota-reached/> <storage-quota-reached/>
</error> </error>
Notes Notes
Server implementations store and account for their data in many Server implementations store and account for their data in many
different ways. Some of the challenges: different ways. Some of the challenges:
skipping to change at line 278 skipping to change at line 322
- Variants of one resource may exist with different content lengths - Variants of one resource may exist with different content lengths
- Content may be dynamically generated. - Content may be dynamically generated.
- Resource bodies can be compressed - Resource bodies can be compressed
- Some resources may be stored for ˘free÷, not counting against - Some resources may be stored for ˘free÷, not counting against
quota. quota.
Dusseault Expires April 2002 5
DAV Collection Size and Quota October 2002
Since server storage accounting can vary so much, clients should Since server storage accounting can vary so much, clients should
expect the following: expect the following:
- The size of a file on the clientĂs file system, or in a PUT - The size of a file on the clientĂs file system, or in a PUT
message, may not correspond to the amount of storage required by the message, may not correspond to the amount of storage required by the
server to store the resource. Thus, the client cannot predict with server to store the resource. Thus, the client cannot predict with
100% accuracy whether a given file will be allowed given the storage 100% accuracy whether a given file will be allowed given the storage
quota. quota.
- Deleting a resource may not free up the same amount of storage as - Deleting or overwriting a resource may not free up the same
indicated by the DAV:getcontentlength property defined in [RFC2518] amount of storage as indicated by the DAV:getcontentlength property
for the resource. If deleting a resource does not free up any defined in [RFC2518] for the resource. If deleting a resource does
space, the file has probably been moved to a ˘trash÷ folder or not free up any space, the file may have been moved to a ˘trash÷
˘recycle bin÷.
Korver Expires Jul 2003 6
DAV Collection Size and Quota January 2003
folder or ˘recycle bin÷, or retained as in versioning systems
[RFC3253].
- The total size of a collection, DAV:quota-used-bytes, is not - The total size of a collection, DAV:quota-used-bytes, is not
necessarily a sum of the DAV:getcontentlength properties for necessarily a sum of the DAV:getcontentlength properties for
resources stored in the collection. resources stored in the collection.
- A quota on a collection may be larger than the quota on a - On some systems where quota is counted by collection and not by
collection that contains it. For example, the quota on /~milele/ user, a quota on a sub-collection may be larger than the quota on
may be 100 MB, but the quota on /~milele/public/ may be unlimited. its parent collection that contains it. For example, the quota on
This allows the space used by /~milele/public/ to be as large as the /~milele/ may be 100 MB, but the quota on /~milele/public/ may be
quota on /~milele/ allows (depending on the other contents of unlimited. This allows the space used by /~milele/public/ to be as
/~milele/) even if the quota on /~milele/ is changed. Thus, even large as the quota on /~milele/ allows (depending on the other
when the quota on a parent collection is changed, it is not contents of /~milele/) even if the quota on /~milele/ is changed.
necessarily required to change the quota on every child or Thus, even when the quota on a parent collection is changed, it is
not necessarily required to change the quota on every child or
descendant collection. descendant collection.
Security Considerations Security Considerations
A hacker may prefer to store files on collections with a large A hacker may prefer to store files in collections with a large
quota. This isn't strictly a security concern because it doesn't quota. This isn't strictly a security concern because it doesn't
make it any easier to store files. On the other hand, the make it any easier to store files. On the other hand, the
DAV:quota-used-bytes property may make it easier to detect tampering DAV:quota-used-bytes property may make it easier to detect tampering
or misuse. or misuse.
If a server chooses to make the DAV:quota-bytes writable by clients If a server chooses to make the DAV:quota-assigned-bytes writable by
with sufficient authorization, then it is opening up a certain clients with sufficient authorization, then it is opening up a
amount of near-administration functionality to clients. However, it certain amount of near-administration functionality to clients.
is not required for the DAV:quota-bytes property to be writeable by However, it is not required for the DAV:quota-assigned-bytes
any clients, so a server can easily avoid this consideration. property to be writeable by any clients, so a server can easily
avoid this consideration.
Internationalization Considerations Internationalization Considerations
Quota is counted in Arabic numerals expressed in strings. There are Quota is counted in Arabic numerals expressed in strings. There are
no internationalization considerations. no internationalization considerations.
IANA Considerations IANA Considerations
There are no IANA considerations. There are no IANA considerations.
Dusseault Expires April 2002 6
DAV Collection Size and Quota October 2002
Intellectual Property Intellectual Property
The following notice is copied from [RFC2026], and describes the The following notice is copied from [RFC2026], and describes the
position of the IETF concerning intellectual property claims made position of the IETF concerning intellectual property claims made
against this document. against this document.
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
Korver Expires Jul 2003 7
DAV Collection Size and Quota January 2003
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Acknowledgements Acknowledgements
Jim Whitehead and Jim Luther provided valuable comments on this Jim Whitehead and Jim Luther provided valuable comments on this
document. document.
Dusseault Expires April 2002 7 Korver Expires Jul 2003 8
DAV Collection Size and Quota October 2002 DAV Collection Size and Quota January 2003
References References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2026] Bradner, S., ˘The Internet Standards Process ű Revision [RFC2026] Bradner, S., ˘The Internet Standards Process ű Revision
3÷, BCP 9, RFC2026, October 1996. 3÷, BCP 9, RFC2026, October 1996.
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and
Jensen, D., "HTTP Extensions for Distributed Authoring -- Jensen, D., "HTTP Extensions for Distributed Authoring --
WebDAV", RFC2518, February 1999. WebDAV", RFC2518, February 1999.
[RFC3253] Clemm, Geoff, Jim Amsden, Tim Ellison, Chris Kaler, Jim [RFC3010] Shepler S., B. Callaghan, D. Robinson, R. Thurlow, C.
Whitehead, "Versioning Extensions to WebDAV", RFC3253, October Beame, M. Eisler, D. Noveck, ˘NFS version 4 Protocol÷, RFC3010,
2001. December 2000.
Author's Addresses Author's Addresses
Brian Korver
Xythos Software, Inc.
77 Maiden Lane, Suite 200 Phone: 1-415-248-9033
San Francisco, CA, USA Email: briank@xythos.com
Lisa Dusseault Lisa Dusseault
Xythos Software, Inc. Xythos Software, Inc.
77 Maiden Lane, Suite 200 Phone: 1-415-248-9004 77 Maiden Lane, Suite 200 Phone: 1-415-248-9004
San Francisco, CA, USA Email: lisa@xythos.com San Francisco, CA, USA Email: lisa@xythos.com
Clark Warner Clark Warner
Netezza Corporation Netezza Corporation
200 Crossing Blvd, Phone: 1-508-665-6800 x889 200 Crossing Blvd. Phone: 1-508-665-6800 x889
Framingham, MA 01702 Email: webdav@thewarners.com Framingham, MA 01702 Email: webdav@thewarners.com
Dusseault Expires Jul 2002 8 Korver Expires Jul 2003 9
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/