draft-ietf-webdav-quota-02.txt   draft-ietf-webdav-quota-03.txt 
WWW Distributed Authoring and B. Korver
B. Korver Versioning (webdav) Xythos
Xythos Internet-Draft L. Dusseault
L. Dusseault Expires: January 5, 2005 OSAF
Xythos July 7, 2004
Internet Draft C. Warner
Document: draft-ietf-webdav-quota-02.txt Netezza
Expires: January 2004 July 2003
Quota and Size Properties for DAV Collections Quota and Size Properties for DAV Collections
draft-ietf-webdav-quota-03
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. 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
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as time. It is inappropriate to use Internet-Drafts as reference
reference material or to cite them other than as "work in progress." 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 This Internet-Draft will expire on January 5, 2005.
WebDAV servers are frequently deployed with quota (size) Copyright Notice
limitations. This Internet-Draft discusses the properties and minor
behaviors needed for clients to interoperate with quota
implementations on WebDAV repositories.
Table of Contents Copyright (C) The Internet Society (2004). All Rights Reserved.
Introduction.......................................................2 Abstract
DAV:quota-available-bytes..........................................3
DAV:quota-used-bytes...............................................4
DAV:quota-assigned-bytes...........................................4
Example PROPFIND request and response..............................5
Error reporting....................................................6
Notes..............................................................6
Security Considerations............................................7
Internationalization Considerations................................7
IANA Considerations................................................7
Dusseault Expires July 2003 1 WebDAV servers are frequently deployed with quota (size) limitations.
This Internet-Draft discusses the properties and minor behaviors
needed for clients to interoperate with quota implementations on
WebDAV repositories.
DAV Collection Size and Quota July 2003 Table of Contents
Intellectual Property..............................................8 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
Acknowledgements...................................................8 1.1 Notational Conventions . . . . . . . . . . . . . . . . . . 3
References.........................................................9 1.2 Requirement for quotas . . . . . . . . . . . . . . . . . . 3
Author's Addresses.................................................9 2. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 3
3. DAV:quota-available-bytes . . . . . . . . . . . . . . . . . . 4
4. DAV:quota-used-bytes . . . . . . . . . . . . . . . . . . . . . 5
5. DAV:quota-assigned-bytes . . . . . . . . . . . . . . . . . . . 6
5.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Example PROPFIND request and response . . . . . . . . . . . . 7
7. Error reporting . . . . . . . . . . . . . . . . . . . . . . . 8
8. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
10. Internationalization Considerations . . . . . . . . . . . . 10
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
13.1 Normative References . . . . . . . . . . . . . . . . . . . . 11
13.2 Informative References . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 12
Introduction 1. Introduction
Notational Conventions 1.1 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 this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in [RFC2119].
Requirement for quotas 1.2 Requirement for quotas
WebDAV servers based on [RFC2518] have been implemented and deployed WebDAV servers based on [RFC2518] have been implemented and deployed
with quota restrictions on collections and users, so it makes sense with quota restrictions on collections and users, so it makes sense
to standardize this functionality to improve user experience and to standardize this functionality to improve user experience and
client interoperability. This specification requires WebDAV because client interoperability. This specification requires WebDAV because
it 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 quotas enforced are The reasons why WebDAV servers frequently have quotas enforced are
the same reasons why any storage system comes with quotas. the same reasons why any storage system comes with quotas.
- Sometimes the storage service charges according to quota o Sometimes the storage service charges according to quota
- Sometimes the storage service is provided free, but the storage o Sometimes the storage service is provided free, but the storage
service provider has limited storage space (e.g. www.sharemation.com service provider has limited storage space (e.g. www.example.com
and university-provided student accounts) and university-provided student accounts)
- Even in cases where the storage can be upgraded, the storage o Even in cases where the storage can be upgraded, the storage
managers may choose to limit quota 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. (e.g. IT departments within corporations). files. (e.g. IT departments within corporations)
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-available software should be able to determine and display the quota-available
on collections. Further, client software should have some way of on 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
counted towards that quota. towards that quota.
In addition to displaying the quota-available and quota-used on In addition to displaying the quota-available and quota-used on
collections, this specification does not forbid these properties on collections, this specification does not forbid these properties on
any resource. any resource.
Solution Overview 2. Solution Overview
The approach to meeting the requirements and scenarios outlined
above is to define three live properties. This specification can be
Korver Expires January 2004 2
DAV Collection Size and Quota July 2003
met on a server by implementing both quota-available and quota-used The approach to meeting the requirements and scenarios outlined above
on collections only. Implementing both quota-available and quota- is to define three live properties. This specification can be met on
used on all resources is RECOMMENDED. a server by implementing both quota-available and quota-used on
collections only. Implementing both quota-available and quota- used
on all resources is RECOMMENDED.
None of these properties need be returned in a <DAV:allprop> request None of these properties need be returned in a <DAV:allprop> request
though the server may include them. However, these property names though the server may include them. However, these property names
MUST be returned in a <DAV:propname> request for a resource that MUST be returned in a <DAV:propname> request for a resource that
supports the properties, except in the case of infinite limits which supports the properties, except in the case of infinite limits which
are explained below. are explained below.
The quota-available and quota-used definitions below borrow heavily The quota-available and quota-used definitions below borrow heavily
from the quota definitions in the NFS [RFC3010] specification. from the quota definitions in the NFS [RFC3010] specification.
DAV:quota-available-bytes 3. DAV:quota-available-bytes
Name: quota-available-bytes Name: quota-available-bytes
Namespace: DAV: Namespace: DAV:
Purpose: Indicates the maximum amount of additional storage
available to be allocated to a resource. Purpose: Indicates the maximum amount of additional storage available
to be allocated to a resource.
DTD: <!ELEMENT quota-available-bytes (#PCDATA) > DTD: <!ELEMENT quota-available-bytes (#PCDATA) >
The DAV:quota-available-bytes property value is the value in octets The DAV:quota-available-bytes property value is the value in octets
representing the amount of additional disk space beyond the current representing the amount of additional disk space beyond the current
allocation that can be allocated to this file or directory before allocation that can be allocated to this file or directory before
further allocations will be refused. It is understood that this further allocations will be refused. It is understood that this
space may be consumed by allocations to other files or directories. space may be consumed by allocations to other files or directories.
Support for this property is REQUIRED on collections, and OPTIONAL Support for this property is REQUIRED on collections, and OPTIONAL on
on other resources. A server SHOULD implement this property for other resources. A server SHOULD implement this property for each
each resource that has the DAV:quota-used-bytes property. resource that has the DAV:quota-used-bytes property.
Clients SHOULD expect that as the quota-available on a file or Clients SHOULD expect that as the quota-available on a file or
directory approaches 0, further allocations to that file or directory approaches 0, further allocations to that file or directory
directory may be refused. A value of 0 indicates that users will may be refused. A value of 0 indicates that users will probably not
probably not be able to perform operations that write additional be able to perform operations that write additional information (e.g.
information (e.g. a PUT inside a collection), but may be able to a PUT inside a collection), but may be able to replace through
replace through overwrite an existing resource of equal size. overwrite an existing resource of equal size.
Note that there may be a number of distinct but overlapping limits, Note that there may be a number of distinct but overlapping limits,
which may even include physical media limits. When reporting quota- which may even include physical media limits. When reporting quota-
available, the server is at liberty to choose any of those limits available, the server is at liberty to choose any of those limits but
but SHOULD do so in a repeatable way. The rule may be configured SHOULD do so in a repeatable way. The rule may be configured per
per repository, or may be Śchoose the smallest numberŽ. repository, or may be "choose the smallest number".
If a resource has no quota enforced or unlimited storage (Śinfinite If a resource has no quota enforced or unlimited storage ("infinite
limitsŽ), the server MAY choose not to return this property (404 Not limits"), the server MAY choose not to return this property (404 Not
Found response in Multi-Status), although this specification Found response in Multi-Status), although this specification
RECOMMENDS that servers return some appropriate value (e.g. the RECOMMENDS that servers return some appropriate value (e.g. the
amount of free disc space). A client cannot entirely assume that amount of free disc space). A client cannot entirely assume that
there is no quota enforced on a resource that does not have this 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. property, but might as well act as if there is no quota.
Korver Expires January 2004 3 The value of this property is protected. A 403 Forbidden response is
RECOMMENDED for attempts to write a protected property.
DAV Collection Size and Quota July 2003
The value of this property is protected. A 403 Forbidden response
is RECOMMENDED for attempts to write a protected property.
DAV:quota-used-bytes 4. DAV:quota-used-bytes
Name: quota-used-bytes Name: quota-used-bytes
Namespace: DAV: Namespace: DAV:
Purpose: Contains the amount of storage counted against the quota on Purpose: Contains the amount of storage counted against the quota on
a resource. a resource.
DTD: <!ELEMENT quota-used-bytes (#PCDATA) > DTD: <!ELEMENT quota-used-bytes (#PCDATA) >
The DAV:quota-used-bytes value is the value in octets representing The DAV:quota-used-bytes value is the value in octets representing
the amount of space used by this file or directory and possibly a the amount of space used by this file or directory and possibly a
number of other similar files or directories, where the set of number of other similar files or directories, where the set of
ŚsimilarŽ meets at least the criterion that allocating space to any "similar" meets at least the criterion that allocating space to any
file or directory in the set will count against the quota-available. file or directory in the set will count against the quota-available.
It MUST include the total count including usage derived from sub- It MUST include the total count including usage derived from sub-
resources if appropriate. It SHOULD include metadata storage size resources if appropriate. It SHOULD include metadata storage size if
if metadata storage is counted against the quota-available. metadata storage is counted against the quota-available.
Note that there may be a number of distinct but overlapping sets of 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 or directories for which a quota-used is maintained (e.g. "all
files with a given ownerŽ, Śall files with a given group ownerŽ, 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 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 SHOULD do so in a repeatable way. The rule may be configured per
repository. repository.
Support for this property is REQUIRED on collections, and OPTIONAL Support for this property is REQUIRED on collections, and OPTIONAL on
on other resources. A server SHOULD implement this property for other resources. A server SHOULD implement this property for each
each resource that has the DAV:quota-available-bytes property. resource that has the DAV:quota-available-bytes property.
Support for this property enhances the client experience, because Support for this property enhances the client experience, because
together with DAV:quota-available-bytes, the client has a chance of together with DAV:quota-available-bytes, the client has a chance of
managing its files to avoid running out of allocated storage space. managing its files to avoid running out of allocated storage space.
Clients may not be able to calculate the value as accurately on Clients may not be able to calculate the value as accurately on their
their own, depending on how total space used is calculated by the own, depending on how total space used is calculated by the server.
server.
DAV:quota-assigned-bytes 5. DAV:quota-assigned-bytes
Name: quota-assigned-bytes Name: quota-assigned-bytes
Namespace: DAV: Namespace: DAV:
Purpose: Indicates the amount of storage assigned. Purpose: Indicates the amount of storage assigned.
DTD: <!ELEMENT quota-bytes (#PCDATA) > DTD: <!ELEMENT quota-bytes (#PCDATA) >
The DAV:quota-assigned-bytes property value is the amount of storage The DAV:quota-assigned-bytes property value is the amount of storage
space potentially either assigned to or requested for this file or space potentially either assigned to or requested for this file or
directory, measured in octets. DAV:quota-assigned-bytes is primarily directory, measured in octets. DAV:quota-assigned-bytes is primarily
intended to support implementations that allow quota to be intended to support implementations that allow quota to be
PROPPATCHed or configured by some other means. PROPPATCHed or configured by some other means.
The value of this property will usually be protected, although a The value of this property will usually be protected, although a user
user with sufficient privileges may be permitted to change the with sufficient privileges may be permitted to change the value. The
property is useful even if it is protected. A 403 Forbidden response
Korver Expires January 2004 4 is RECOMMENDED for attempts to write a protected property. This
property will usually be read-only for instance because a user's
DAV Collection Size and Quota July 2003 quota should generally not configurable by other users.
value. The property is useful even if it is protected. A 403
Forbidden response is RECOMMENDED for attempts to write a protected
property. This property will usually be read-only for instance
because a userŤs quota should generally not configurable by other
users.
Support for this property is OPTIONAL. Support for this property is OPTIONAL.
Note that a resource may show more quota-used than its quota- Note that a resource may show more quota-used than its quota-
assigned appears to allow, and that quota-available MUST never be assigned appears to allow, and that quota-available MUST never be
greater than the value of quota-assigned. greater than the value of quota-assigned.
5.1 Example 1
As an example of quota-assigned, imagine a quota system where each As an example of quota-assigned, imagine a quota system where each
collection may have a quota assigned and where a resource contained collection may have a quota assigned and where a resource contained
in a collection is subject to the quota constraints of all parent in a collection is subject to only the quota constraints of the
collections. Assume the administrator creates a collection A and nearest collection which has a quota assigned. Assume the
gives it a quota-assigned of 500KB and then creates a sub- administrator creates a collection A and gives it a quota-assigned of
collections B which is given quota-assigned of 1000KB. In this 300KB and then creates a subcollection B which is given
quota-assigned of 8000KB. In this case, the initial quota-available
for B is 8000KB, not 3000KB, since the constraint on A is ignored in
favor of the constraint on B.
DAV:quota-assigned-bytes DAV:quota-available-bytes
/A 300KB 300KB
/A/B 8000KB 8000KB
Note that this is only one example quota system, and that other quota
systems are possible, such as one described in the example below.
5.2 Example 2
As another example of quota-assigned, 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 500KB and then creates a
subcollection B which is given quota-assigned of 1000KB. In this
case, the initial quota-available for B is 500KB, not 1000KB, since case, the initial quota-available for B is 500KB, not 1000KB, since
the constraint on A applies to B as well. the constraint on A applies to B as well.
DAV:quota-assigned-bytes DAV:quota-available-bytes DAV:quota-assigned-bytes DAV:quota-available-bytes
/A 500KB 500KB /A 500KB 500KB
/A/B 1000KB 500KB /A/B 1000KB 500KB
Note that this is only one example quota system, and that other 6. Example PROPFIND request and response
quota systems are possible.
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.example.com
Content-Type: text/xml Content-Type: text/xml
Content-Length: xxx 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-available-bytes><D:quota-used-bytes></D:prop> <D:prop><D:quota-available-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
<?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.example.com/~milele/public/</D:href>
Korver Expires January 2004 5
DAV Collection Size and Quota July 2003
<D:href>http://www.sharemation.com/~milele/public/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:quota-available-bytes>596650</D:quota-available-bytes> <D:quota-available-bytes>596650</D:quota-available-bytes>
<D:quota-used-bytes>403350</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>
Error reporting 7. 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 [RFC3253] 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 8. 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:
- Some server implementations find it prohibitive to count storage o Some server implementations find it prohibitive to count storage
used for metadata, others may choose to do so for better accounting. used for metadata, others may choose to do so for better
accounting.
- Older versions of resources may be stored as well. o Older versions of resources may be stored as well.
- Variants of one resource may exist with different content lengths o Variants of one resource may exist with different content lengths
- Content may be dynamically generated. o Content may be dynamically generated.
- Resource bodies can be compressed o Resource bodies can be compressed
- Some resources may be stored for ŚfreeŽ, not counting against o Some resources may be stored for "free", not counting against
quota. quota.
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:
Korver Expires January 2004 6 o 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
DAV Collection Size and Quota July 2003 the server to store the resource. Thus, the client cannot predict
with 100% accuracy whether a given file will be allowed given the
- The size of a file on the clientŤs file system, or in a PUT storage quota.
message, may not correspond to the amount of storage required by the
server to store the resource. Thus, the client cannot predict with
100% accuracy whether a given file will be allowed given the storage
quota.
- Deleting or overwriting a resource may not free up the same o Deleting or overwriting a resource may not free up the same amount
amount of storage as indicated by the DAV:getcontentlength property of storage as indicated by the DAV:getcontentlength property
defined in [RFC2518] for the resource. If deleting a resource does defined in [RFC2518] for the resource. If deleting a resource
not free up any space, the file may have been moved to a ŚtrashŽ does not free up any space, the file may have been moved to a
folder or Śrecycle binŽ, or retained as in versioning systems "trash" folder or "recycle bin", or retained as in versioning
[RFC3253]. systems ([RFC3253]).
- The total size of a collection, DAV:quota-used-bytes, is not o 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.
- On some systems where quota is counted by collection and not by o On some systems where quota is counted by collection and not by
user, a quota on a sub-collection may be larger than the quota on user, a quota on a sub-collection may be larger than the quota on
its parent collection that contains it. For example, the quota on its parent collection that contains it. For example, the quota on
/~milele/ may be 100 MB, but the quota on /~milele/public/ may be /~milele/ may be 100 MB, but the quota on /~milele/public/ may be
unlimited. This allows the space used by /~milele/public/ to be as unlimited. This allows the space used by /~milele/public/ to be
large as the quota on /~milele/ allows (depending on the other as large as the quota on /~milele/ allows (depending on the other
contents of /~milele/) even if the quota on /~milele/ is changed. contents of /~milele/) even if the quota on /~milele/ is changed.
Thus, even when the quota on a parent collection is changed, it is Thus, even when the quota on a parent collection is changed, it is
not necessarily required to change the quota on every child or not necessarily required to change the quota on every child or
descendant collection. descendant collection.
Security Considerations 9. Security Considerations
A hacker may prefer to store files in collections with a large A hacker may prefer to store files in collections with a large quota.
quota. This isn't strictly a security concern because it doesn't This isn't strictly a security concern because it doesn't make it any
make it any easier to store files. On the other hand, the easier to store files. On the other hand, the DAV:quota-used-bytes
DAV:quota-used-bytes property may make it easier to detect tampering property may make it easier to detect tampering or misuse.
or misuse.
If a server chooses to make the DAV:quota-assigned-bytes writable by If a server chooses to make the DAV:quota-assigned-bytes writable by
clients with sufficient authorization, then it is opening up a clients with sufficient authorization, then it is opening up a
certain amount of near-administration functionality to clients. certain amount of near-administration functionality to clients.
However, it is not required for the DAV:quota-assigned-bytes However, it is not required for the DAV:quota-assigned-bytes property
property to be writeable by any clients, so a server can easily to be writeable by any clients, so a server can easily avoid this
avoid this consideration. consideration.
Internationalization Considerations 10. 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 11. IANA Considerations
There are no IANA considerations. There are no IANA considerations.
Korver Expires January 2004 7 12. Acknowledgements
DAV Collection Size and Quota July 2003 Stefan Eissing, Jim Luther, Julian Reschke, and Jim Whitehead and
provided valuable comments on this document.
Intellectual Property 13. References
The following notice is copied from [RFC2026], and describes the 13.1 Normative References
position of the IETF concerning intellectual property claims made
against this document. [RFC2026] Bradner, S., "The Internet Standards Process - Revision
3", RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
Jensen, "HTTP Extensions for Distributed Authoring --
WebDAV", RFC 2518, February 1999.
[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.
Whitehead, "Versioning Extensions to WebDAV (Web
Distributed Authoring and Versioning)", RFC 3253, March
2002.
13.2 Informative References
[RFC3010] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R.,
Beame, C., Eisler, M. and D. Noveck, "NFS version 4
Protocol", RFC 3010, December 2000.
Authors' Addresses
Brian Korver
Xythos Software
One Bush Street
Suite 600
San Francisco, CA 94104
US
Phone: +1 415 248-3800
EMail: briank@xythos.com
Lisa Dusseault
Open Source Applications Foundation
543 Howard Street
5th Floor
San Francisco, CA 94105
US
Phone: +1 415 946-3040
EMail: lisa@osafoundation.org
Intellectual Property Statement
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
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
of licenses to be made available, or the result of an attempt made licenses to be made available, or the result of an attempt made to
to obtain a general license or permission for the use of such 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
can be obtained from the IETF Secretariat. 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 Full Copyright Statement
Stefan Eissing, Jim Luther, Julian Reschke, and Jim Whitehead and
provided valuable comments on this document.
Korver Expires January 2004 8
DAV Collection Size and Quota July 2003
References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2026] Bradner, S., ŚThe Internet Standards Process ± Revision
3Ž, BCP 9, RFC2026, October 1996.
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and
Jensen, D., "HTTP Extensions for Distributed Authoring --
WebDAV", RFC2518, February 1999.
[RFC3010] Shepler S., B. Callaghan, D. Robinson, R. Thurlow, C.
Beame, M. Eisler, D. Noveck, ŚNFS version 4 ProtocolŽ, RFC3010,
December 2000.
Author's Addresses Copyright (C) The Internet Society (2004). All Rights Reserved.
Brian Korver This document and translations of it may be copied and furnished to
Xythos Software, Inc. others, and derivative works that comment on or otherwise explain it
25 Maiden Lane, Suite 200 Phone: 1-415-248-9033 or assist in its implementation may be prepared, copied, published
San Francisco, CA, USA Email: briank@xythos.com and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
Lisa Dusseault The limited permissions granted above are perpetual and will not be
Xythos Software, Inc. revoked by the Internet Society or its successors or assignees.
25 Maiden Lane, Suite 200 Phone: 1-415-248-9004
San Francisco, CA, USA Email: lisa@xythos.com
Clark Warner This document and the information contained herein is provided on an
Netezza Corporation "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
200 Crossing Blvd. Phone: 1-508-665-6800 x889 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
Framingham, MA 01702 Email: webdav@thewarners.com BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Korver Expires January 2004 9 Acknowledgment
-brian Funding for the RFC Editor function is currently provided by the
briank@xythos.com Internet Society.
 End of changes. 

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