draft-ietf-webdav-quota-04.txt		draft-ietf-webdav-quota-05.txt
	WWW Distributed Authoring and B. Korver		WWW Distributed Authoring and B. Korver
	Versioning (webdav) Xythos		Versioning (webdav) Xythos
	Internet-Draft L. Dusseault		Internet-Draft L. Dusseault
	Expires: April 22, 2005 OSAF		Expires: July 23, 2005 OSAF
	October 22, 2004		January 19, 2005
	Quota and Size Properties for DAV Collections		Quota and Size Properties for DAV Collections
	draft-ietf-webdav-quota-04		draft-ietf-webdav-quota-05
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is subject to all provisions		This document is an Internet-Draft and is subject to all provisions
	of section 3 of RFC 3667. By submitting this Internet-Draft, each		of Section 3 of RFC 3667. By submitting this Internet-Draft, each
	author represents that any applicable patent or other IPR claims of		author represents that any applicable patent or other IPR claims of
	which he or she is aware have been or will be disclosed, and any of		which he or she is aware have been or will be disclosed, and any of
	which he or she become aware will be disclosed, in accordance with		which he or she become aware will be disclosed, in accordance with
	RFC 3668.		RFC 3668.
	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		other groups may also distribute working documents as
	Internet-Drafts.		Internet-Drafts.
	skipping to change at page 1, line 37		skipping to change at page 1, line 37
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as 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.
	This Internet-Draft will expire on April 22, 2005.		This Internet-Draft will expire on July 23, 2005.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004).		Copyright (C) The Internet Society (2005).
	Abstract		Abstract
	WebDAV servers are frequently deployed with quota (size) limitations.		WebDAV servers are frequently deployed with quota (size) limitations.
	This Internet-Draft discusses the properties and minor behaviors		This document discusses the properties and minor behaviors needed for
	needed for clients to interoperate with quota implementations on		clients to interoperate with quota (size) implementations on WebDAV
	WebDAV repositories.		repositories.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1 Notational Conventions . . . . . . . . . . . . . . . . . . 3		1.1 Notational Conventions . . . . . . . . . . . . . . . . . . 3
	1.2 Requirement for quotas . . . . . . . . . . . . . . . . . . 3		1.2 Requirement for quotas . . . . . . . . . . . . . . . . . . 3
	2. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 3		2. Solution Overview . . . . . . . . . . . . . . . . . . . . . 3
	3. DAV:quota-available-bytes . . . . . . . . . . . . . . . . . . 4		3. DAV:quota-available-bytes . . . . . . . . . . . . . . . . . 4
	4. DAV:quota-used-bytes . . . . . . . . . . . . . . . . . . . . . 5		4. DAV:quota-used-bytes . . . . . . . . . . . . . . . . . . . . 5
	5. Example PROPFIND request and response . . . . . . . . . . . . 5		5. Example PROPFIND request and response . . . . . . . . . . . 6
	6. Error reporting . . . . . . . . . . . . . . . . . . . . . . . 6		6. Error reporting . . . . . . . . . . . . . . . . . . . . . . 6
	7. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7		7. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 8		8. Security Considerations . . . . . . . . . . . . . . . . . . 8
	9. Internationalization Considerations . . . . . . . . . . . . . 8		9. Internationalization Considerations . . . . . . . . . . . . 8
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 8		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 8
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	12.1 Normative References . . . . . . . . . . . . . . . . . . . . 9		12.1 Normative References . . . . . . . . . . . . . . . . . . 8
	12.2 Informative References . . . . . . . . . . . . . . . . . . . 9		12.2 Informative References . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 9
	Intellectual Property and Copyright Statements . . . . . . . . 10		Intellectual Property and Copyright Statements . . . . . . . 10
	1. Introduction		1. Introduction
	1.1 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 [RFC2119].		document are to be interpreted as described in [RFC2119].
	1.2 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 (see section 1.4.2 of [RFC3253] for the
			definition of 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.
	o Sometimes the storage service charges according to quota		o Sometimes the storage service charges according to quota
	o 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.example.com		service provider has limited storage space (e.g.
	and university-provided student accounts)		university-provided student accounts)
	o 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
	on collections. Further, client software should have some way of		DAV:quota-available-bytes on collections. Further, client software
	fairly reliably determining how much storage space is already counted		should have some way of fairly reliably determining how much storage
	towards that quota.		space is already counted towards that quota.
	In addition to displaying the quota-available and quota-used on
	collections, this specification does not forbid these properties on
	any resource.
	2. Solution Overview		2. Solution Overview
	The approach to meeting the requirements and scenarios outlined above		The approach to meeting the requirements and scenarios outlined above
	is to define three live properties. This specification can be met on		is to define two live properties. This specification can be met on a
	a server by implementing both quota-available and quota-used on		server by implementing both DAV:quota-available-bytes and
	collections only. Implementing both quota-available and quota- used		DAV:quota-used-bytes on collections only. Implementing both
	on all resources is RECOMMENDED.		DAV:quota-available-bytes and DAV:quota-used-bytes on all resources
			is RECOMMENDED.
	A <DAV:allprop> PROPFIND request SHOULD NOT return any of the		A <DAV:allprop> PROPFIND request SHOULD NOT return any of the
	properties defined by this document. However, these property names		properties defined by this document. 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 DAV:quota-available-bytes and DAV:quota-used-bytes definitions
	from the quota definitions in the NFS [RFC3010] specification.		below borrow heavily from the quota definitions in the NFS [RFC3530]
			specification.
	3. 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		Purpose: Indicates the maximum amount of additional storage available
	to be allocated to a resource.		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 resource before further
	further allocations will be refused. It is understood that this		allocations will be refused. It is understood that this space may be
	space may be consumed by allocations to other files or directories.		consumed by allocations to other resources.
	Support for this property is REQUIRED on collections, and OPTIONAL on		Support for this property is REQUIRED on collections, and OPTIONAL on
	other resources. A server SHOULD implement this property for each		other resources. A server SHOULD implement this property for 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 DAV:quota-available-bytes on a
	directory approaches 0, further allocations to that file or directory		resource approaches 0, further allocations to that resource may be
	may be refused. A value of 0 indicates that users will probably not		refused. A value of 0 indicates that users will probably not be able
	be able to perform operations that write additional information (e.g.		to perform operations that write additional information (e.g. a PUT
	a PUT inside a collection), but may be able to replace through		inside a collection), but may be able to replace through overwrite an
	overwrite an existing resource of equal size.		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
	available, the server is at liberty to choose any of those limits but		DAV:quota-available-bytes, the server is at liberty to choose any of
	SHOULD do so in a repeatable way. The rule may be configured per		those limits but SHOULD do so in a repeatable way. The rule may be
	repository, or may be "choose the smallest number".		configured per 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.
	The value of this property is protected. A 403 Forbidden response is		The value of this property is protected (see section 1.4.2 of
	RECOMMENDED for attempts to write a protected property.		[RFC3253] for the definition of protected properties). A 403
			Forbidden response is RECOMMENDED for attempts to write a protected
			property, and the server SHOULD include an XML error body as defined
			by DeltaV [RFC3253] with the <DAV:cannot-modify-protected-property/>
			precondition tag.
	4. 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 resource and possibly a number of
	number of other similar files or directories, where the set of		other similar files or directories, where the set of "similar" meets
	"similar" meets at least the criterion that allocating space to any		at least the criterion that allocating space to any resource in the
	file or directory in the set will count against the quota-available.		set will count against the DAV:quota-available-bytes. It MUST
	It MUST include the total count including usage derived from sub-		include the total count including usage derived from sub-resources if
	resources if appropriate. It SHOULD include metadata storage size if		appropriate. It SHOULD include metadata storage size if metadata
	metadata storage is counted against the quota-available.		storage is counted against the DAV:quota-available-bytes.
	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 DAV:quota-used-bytes is maintained
	files with a given owner", "all files with a given group owner",		(e.g. "all files with a given owner", "all files with a given group
	etc.). The server is at liberty to choose any of those sets but		owner", etc.). The server is at liberty to choose any of those sets
	SHOULD do so in a repeatable way. The rule may be configured per		but 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 on		Support for this property is REQUIRED on collections, and OPTIONAL on
	other resources. A server SHOULD implement this property for each		other resources. A server SHOULD implement this property for 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 their		Clients may not be able to calculate the value as accurately on their
	skipping to change at page 6, line 14		skipping to change at page 6, line 17
	Request:		Request:
	PROPFIND /~milele/public/ HTTP/1.1		PROPFIND /~milele/public/ HTTP/1.1
	Depth: 0		Depth: 0
	Host: www.example.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>		<D:href>http://www.example.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</D: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>
	6. Error reporting		6. 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) fails because it would exceed their
	their allotted quota. In order to differentiate the response from		allotted quota. In order to differentiate the response from other
	other storage problems, the server SHOULD include an XML error body		storage problems, the server SHOULD include an XML error body as
	as defined by DeltaV [RFC3253] with the <DAV:storage-quota-reached/>		defined by DeltaV [RFC3253] with the <DAV:quota-not-exceeded/>
	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: xxx
	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/>		<quota-not-exceeded/>
	</error>		</error>
	7. Notes		7. 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:
	o 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		used for metadata, others may choose to do so for better
	accounting.		accounting.
	skipping to change at page 8, line 5		skipping to change at page 8, line 5
	with 100% accuracy whether a given file will be allowed given the		with 100% accuracy whether a given file will be allowed given the
	storage quota.		storage quota.
	o Deleting or overwriting a resource may not free up the same amount		o Deleting or overwriting a resource may not free up the same 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		defined in [RFC2518] for the resource. If deleting a resource
	does not free up any space, the file may have been moved to a		does not free up any space, the file may have been moved to a
	"trash" folder or "recycle bin", or retained as in versioning		"trash" folder or "recycle bin", or retained as in versioning
	systems ([RFC3253]).		systems ([RFC3253]).
	o The total size of a collection, DAV:quota-used-bytes, is not		o The total size of a collection, DAV:quota-used-bytes, may not be a
	necessarily a sum of the DAV:getcontentlength properties for		sum of the DAV:getcontentlength properties for resources stored in
	resources stored in the collection.		the collection.
	o 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		the 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		unlimited. This allows the space used by /~milele/public/ to be
	as 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.
	8. Security Considerations		8. Security Considerations
	A hacker may prefer to store files in collections with a large quota.		A hacker may prefer to store files in collections with a large quota.
	This isn't strictly a security concern because it doesn't make it any		This isn't strictly a security concern because it doesn't make it any
	easier to store files. On the other hand, the DAV:quota-used-bytes		easier to store files. On the other hand, the DAV:quota-used-bytes
	property may make it easier to detect tampering or misuse.		property may make it easier to detect tampering or misuse.
	If a server chooses to make the DAV:quota-assigned-bytes writable by
	clients with sufficient authorization, then it is opening up a
	certain amount of near-administration functionality to clients.
	However, it is not required for the DAV:quota-assigned-bytes property
	to be writeable by any clients, so a server can easily avoid this
	consideration.
	9. Internationalization Considerations		9. 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.
	10. IANA Considerations		10. IANA Considerations
	There are no IANA considerations.		There are no IANA considerations.
	11. Acknowledgements		11. Acknowledgements
	Stefan Eissing, Jim Luther, Julian Reschke, and Jim Whitehead and		Stefan Eissing, Geoff Clemm, Jim Luther, Julian Reschke, Jim
	provided valuable comments on this document.		Whitehead, among others, have provided valuable comments on this
			document.
	12. References		12. References
	12.1 Normative References		12.1 Normative References
	[RFC2026] Bradner, S., "The Internet Standards Process - Revision
	3", RFC 2026, October 1996.
	[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.
	[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.		[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
	Jensen, "HTTP Extensions for Distributed Authoring --		Jensen, "HTTP Extensions for Distributed Authoring --
	WebDAV", RFC 2518, February 1999.		WebDAV", RFC 2518, February 1999.
	[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.		[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.
	Whitehead, "Versioning Extensions to WebDAV (Web		Whitehead, "Versioning Extensions to WebDAV (Web
	Distributed Authoring and Versioning)", RFC 3253, March		Distributed Authoring and Versioning)", RFC 3253, March
	2002.		2002.
	12.2 Informative References		12.2 Informative References
	[RFC3010] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R.,		[RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R.,
	Beame, C., Eisler, M. and D. Noveck, "NFS version 4		Beame, C., Eisler, M. and D. Noveck, "Network File System
	Protocol", RFC 3530, December 2000.		(NFS) version 4 Protocol", RFC 3530, April 2003.
	Authors' Addresses		Authors' Addresses
	Brian Korver		Brian Korver
	Xythos Software		Xythos Software
	One Bush Street		One Bush Street
	Suite 600		Suite 600
	San Francisco, CA 94104		San Francisco, CA 94104
	US		US
	Phone: +1 415 248-3800		Phone: +1 415 248-3800
	EMail: briank@xythos.com		Email: briank@xythos.com
	Lisa Dusseault		Lisa Dusseault
	Open Source Applications Foundation		Open Source Applications Foundation
	543 Howard Street		543 Howard Street
	5th Floor		5th Floor
	San Francisco, CA 94105		San Francisco, CA 94105
	US		US
	Phone: +1 415 946-3040		Phone: +1 415 946-3040
	EMail: lisa@osafoundation.org		Email: lisa@osafoundation.org
	Intellectual Property Statement		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 Rights or other rights that might be claimed to		Intellectual Property Rights 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; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	skipping to change at page 10, line 41		skipping to change at page 10, line 41
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2004). This document is subject		Copyright (C) The Internet Society (2005). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
	<x-flowed>
	</x-flowed>
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/