--- 1/draft-ietf-extra-quota-09.txt	2021-11-18 05:13:14.432094180 -0800
+++ 2/draft-ietf-extra-quota-10.txt	2021-11-18 05:13:14.468095078 -0800
@@ -1,19 +1,19 @@
 
 Network Working Group                                        A. Melnikov
 Internet-Draft                                                     Isode
-Obsoletes: 2087 (if approved)                            22 October 2021
+Obsoletes: 2087 (if approved)                           18 November 2021
 Intended status: Standards Track
-Expires: 25 April 2022
+Expires: 22 May 2022
 
                           IMAP QUOTA Extension
-                       draft-ietf-extra-quota-09
+                       draft-ietf-extra-quota-10
 
 Abstract
 
    This document defines a QUOTA extension of the Internet Message
    Access Protocol (RFC 3501/RFC 9051) that permits administrative
    limits on resource usage (quotas) to be manipulated through the IMAP
    protocol.
 
    This document obsoletes RFC 2087, but attempts to remain backwards
    compatible whenever possible.
@@ -26,21 +26,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    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 (c) 2021 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents (https://trustee.ietf.org/
    license-info) in effect on the date of publication of this document.
    Please review these documents carefully, as they describe your rights
@@ -81,27 +81,27 @@
        4.2.2.  QUOTAROOT . . . . . . . . . . . . . . . . . . . . . .  10
      4.3.  Response Codes  . . . . . . . . . . . . . . . . . . . . .  10
        4.3.1.  OVERQUOTA . . . . . . . . . . . . . . . . . . . . . .  11
    5.  Resource Type Definitions . . . . . . . . . . . . . . . . . .  12
      5.1.  STORAGE . . . . . . . . . . . . . . . . . . . . . . . . .  12
      5.2.  MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . .  13
      5.3.  MAILBOX . . . . . . . . . . . . . . . . . . . . . . . . .  13
      5.4.  ANNOTATION-STORAGE  . . . . . . . . . . . . . . . . . . .  13
    6.  Interaction with IMAP ACL extension (RFC 4314)  . . . . . . .  14
    7.  Formal syntax . . . . . . . . . . . . . . . . . . . . . . . .  14
-   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
+   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
    9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  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
    10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  19
-   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  20
+   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  19
    12. Changes since RFC 2087  . . . . . . . . . . . . . . . . . . .  20
    13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
      13.1.  Normative References . . . . . . . . . . . . . . . . . .  20
      13.2.  Informative References . . . . . . . . . . . . . . . . .  21
    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21
 
 1.  Document Conventions
 
    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
@@ -159,22 +159,21 @@
 
 3.  Terms
 
 3.1.  Resource
 
    A resource has a name, a formal definition.
 
 3.1.1.  Name
 
    The resource name is an atom, as defined in IMAP4rev1 [RFC3501].
-   These MUST be registered with IANA.  Implementation specific
-   resources begin with "V-" .
+   These MUST be registered with IANA.
 
    Supported resource names MUST be advertised as a capability, by
    prepending the resource name with "QUOTA=RES-".  A server compliant
    with this specification is not required to support all reported
    resource types on all quota roots.
 
 3.1.2.  Definition
 
    The resource definition or document containing it, while not visible
    through the protocol, SHOULD be registered with IANA.
@@ -659,38 +658,25 @@
                        ")"
 
    setquota-resource =  resource-name SP resource-limit
 
    quota-root-name =   astring
 
    resource-limit =    number64
 
    resource-name =     "STORAGE" / "MESSAGE" / "MAILBOX" /
 
-                       "ANNOTATION-STORAGE" / resource-name-vnd /
-
-                       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.
+                       "ANNOTATION-STORAGE" / resource-name-ext
 
    resource-name-ext =  atom
 
-                       ;; Not starting with V- and defined
-
-                       ;; in an IETF Stream RFC
+                       ;; Future resource registrations
 
    resource-usage =    number64
 
                        ;; must be less than corresponding resource-limit
 
    capability-quota =  capa-quota-res / "QUOTASET"
 
                        ;; One or more capa-quota-res must be returned.
 
                        ;; Also "QUOTASET" can optionally be returned.