< draft-ietf-extra-quota-09.txt		draft-ietf-extra-quota-10.txt >
	Network Working Group A. Melnikov		Network Working Group A. Melnikov
	Internet-Draft Isode		Internet-Draft Isode
	Obsoletes: 2087 (if approved) 22 October 2021		Obsoletes: 2087 (if approved) 18 November 2021
	Intended status: Standards Track		Intended status: Standards Track
	Expires: 25 April 2022		Expires: 22 May 2022
	IMAP QUOTA Extension		IMAP QUOTA Extension
	draft-ietf-extra-quota-09		draft-ietf-extra-quota-10
	Abstract		Abstract
	This document defines a QUOTA extension of the Internet Message		This document defines a QUOTA extension of the Internet Message
	Access Protocol (RFC 3501/RFC 9051) that permits administrative		Access Protocol (RFC 3501/RFC 9051) that permits administrative
	limits on resource usage (quotas) to be manipulated through the IMAP		limits on resource usage (quotas) to be manipulated through the IMAP
	protocol.		protocol.
	This document obsoletes RFC 2087, but attempts to remain backwards		This document obsoletes RFC 2087, but attempts to remain backwards
	compatible whenever possible.		compatible whenever possible.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on 25 April 2022.		This Internet-Draft will expire on 22 May 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 3, line 4 ¶		skipping to change at page 3, line 4 ¶
	4.2.2. QUOTAROOT . . . . . . . . . . . . . . . . . . . . . . 10		4.2.2. QUOTAROOT . . . . . . . . . . . . . . . . . . . . . . 10
	4.3. Response Codes . . . . . . . . . . . . . . . . . . . . . 10		4.3. Response Codes . . . . . . . . . . . . . . . . . . . . . 10
	4.3.1. OVERQUOTA . . . . . . . . . . . . . . . . . . . . . . 11		4.3.1. OVERQUOTA . . . . . . . . . . . . . . . . . . . . . . 11
	5. Resource Type Definitions . . . . . . . . . . . . . . . . . . 12		5. Resource Type Definitions . . . . . . . . . . . . . . . . . . 12
	5.1. STORAGE . . . . . . . . . . . . . . . . . . . . . . . . . 12		5.1. STORAGE . . . . . . . . . . . . . . . . . . . . . . . . . 12
	5.2. MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . 13		5.2. MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . 13
	5.3. MAILBOX . . . . . . . . . . . . . . . . . . . . . . . . . 13		5.3. MAILBOX . . . . . . . . . . . . . . . . . . . . . . . . . 13
	5.4. ANNOTATION-STORAGE . . . . . . . . . . . . . . . . . . . 13		5.4. ANNOTATION-STORAGE . . . . . . . . . . . . . . . . . . . 13
	6. Interaction with IMAP ACL extension (RFC 4314) . . . . . . . 14		6. Interaction with IMAP ACL extension (RFC 4314) . . . . . . . 14
	7. Formal syntax . . . . . . . . . . . . . . . . . . . . . . . . 14		7. Formal syntax . . . . . . . . . . . . . . . . . . . . . . . . 14
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 17		8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	9.1. Changes/additions to the IMAP4 capabilities registry . . 17		9.1. Changes/additions to the IMAP4 capabilities registry . . 17
	9.2. IMAP quota resource type registry . . . . . . . . . . . . 18		9.2. IMAP quota resource type registry . . . . . . . . . . . . 17
	9.3. Registrations of IMAP Quota Resource Types . . . . . . . 18		9.3. Registrations of IMAP Quota Resource Types . . . . . . . 18
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19		10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
	12. Changes since RFC 2087 . . . . . . . . . . . . . . . . . . . 20		12. Changes since RFC 2087 . . . . . . . . . . . . . . . . . . . 20
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
	13.1. Normative References . . . . . . . . . . . . . . . . . . 20		13.1. Normative References . . . . . . . . . . . . . . . . . . 20
	13.2. Informative References . . . . . . . . . . . . . . . . . 21		13.2. Informative References . . . . . . . . . . . . . . . . . 21
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21
	1. Document Conventions		1. Document Conventions
	In protocol examples, this document uses a prefix of "C: " to denote		In protocol examples, this document uses a prefix of "C: " to denote
	lines sent by the client to the server, and "S: " for lines sent by		lines sent by the client to the server, and "S: " for lines sent by
	skipping to change at page 4, line 34 ¶		skipping to change at page 4, line 34 ¶
	3. Terms		3. Terms
	3.1. Resource		3.1. Resource
	A resource has a name, a formal definition.		A resource has a name, a formal definition.
	3.1.1. Name		3.1.1. Name
	The resource name is an atom, as defined in IMAP4rev1 [RFC3501].		The resource name is an atom, as defined in IMAP4rev1 [RFC3501].
	These MUST be registered with IANA. Implementation specific		These MUST be registered with IANA.
	resources begin with "V-" .
	Supported resource names MUST be advertised as a capability, by		Supported resource names MUST be advertised as a capability, by
	prepending the resource name with "QUOTA=RES-". A server compliant		prepending the resource name with "QUOTA=RES-". A server compliant
	with this specification is not required to support all reported		with this specification is not required to support all reported
	resource types on all quota roots.		resource types on all quota roots.
	3.1.2. Definition		3.1.2. Definition
	The resource definition or document containing it, while not visible		The resource definition or document containing it, while not visible
	through the protocol, SHOULD be registered with IANA.		through the protocol, SHOULD be registered with IANA.
	skipping to change at page 15, line 35 ¶		skipping to change at page 15, line 35 ¶
	")"		")"
	setquota-resource = resource-name SP resource-limit		setquota-resource = resource-name SP resource-limit
	quota-root-name = astring		quota-root-name = astring
	resource-limit = number64		resource-limit = number64
	resource-name = "STORAGE" / "MESSAGE" / "MAILBOX" /		resource-name = "STORAGE" / "MESSAGE" / "MAILBOX" /
	"ANNOTATION-STORAGE" / resource-name-vnd /		"ANNOTATION-STORAGE" / resource-name-ext
	resource-name-ext
	resource-name-vnd = "V-" atom
	;; Vendor specific, must be registered with IANA.
	;; The "V-" prefix should be followed by a domain
	name
	;; under vendor's control.
	resource-name-ext = atom		resource-name-ext = atom
	;; Not starting with V- and defined		;; Future resource registrations
	;; in an IETF Stream RFC
	resource-usage = number64		resource-usage = number64
	;; must be less than corresponding resource-limit		;; must be less than corresponding resource-limit
	capability-quota = capa-quota-res / "QUOTASET"		capability-quota = capa-quota-res / "QUOTASET"
	;; One or more capa-quota-res must be returned.		;; One or more capa-quota-res must be returned.
	;; Also "QUOTASET" can optionally be returned.		;; Also "QUOTASET" can optionally be returned.
End of changes. 10 change blocks.
	24 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/