idnits 2.17.1 draft-ietf-extra-imap-64bit-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 2 characters in excess of 72. -- The draft header indicates that this document updates RFC5550, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC3501, but the abstract doesn't seem to directly say this. It does mention RFC3501 though, so this could be OK. -- The draft header indicates that this document updates RFC2087, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC5092, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC4466, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2087, updated by this document, for RFC5378 checks: 1995-12-14) -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 28, 2017) is 2371 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4466' is defined on line 283, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2087 (Obsoleted by RFC 9208) ** Obsolete normative reference: RFC 3501 (Obsoleted by RFC 9051) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Ltd 4 Updates: 2087, 3501, 4466, 5092, 5550, SB. Jayantheesh 5 7888, 7889 (if approved) Samsung Electronics America 6 Intended status: Standards Track October 28, 2017 7 Expires: May 1, 2018 9 64bit body part and message sizes in IMAP4 10 draft-ietf-extra-imap-64bit-02.txt 12 Abstract 14 This document defines an IMAPv4rev1 extension that extends the 15 existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit. 16 Both the base IMAP specification (RFC 3501) and several extensions 17 are updated. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on May 1, 2018. 36 Copyright Notice 38 Copyright (c) 2017 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 67 3. 64bit Extension . . . . . . . . . . . . . . . . . . . . . . . 3 68 4. IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . . 3 69 4.1. Changes to IMAP APPENDLIMIT extension . . . . . . . . . . 3 70 4.2. Changes to IMAP BINARY extension . . . . . . . . . . . . 3 71 4.3. Changes to IMAP URL-PARTIAL extension and IMAP URL . . . 4 72 4.4. Changes to IMAP QUOTA extension . . . . . . . . . . . . . 4 73 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 4 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 76 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 77 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 78 10. Normative References . . . . . . . . . . . . . . . . . . . . 6 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 81 1. Introduction 83 IMAP [RFC3501] only allows body parts or message sizes which are 32 84 bit. This document introduces an IMAP extension that allows for 85 message and body part sizes to be 63 bit. 63-bit values were chosen 86 instead of 64-bit values in order to make implementations on various 87 platforms (such as Java) easier. 89 The client wishing to use this extension MUST issue ENABLE 64BIT. 90 Refer [RFC5161] for the usage of ENABLE command. 92 2. Requirements Notation 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in [RFC2119]. 98 In examples, "C:" and "S:" indicate lines sent by the client and 99 server respectively. If a single "C:" or "S:" label applies to 100 multiple lines, then the line breaks between those lines are for 101 editorial clarity only and are not part of the actual protocol 102 exchange. 104 3. 64bit Extension 106 An IMAP server that supports the 64bit extension advertises this by 107 including the name 64BIT in its CAPABILITY list in the authenticated 108 state. The server may also advertise this extension before the user 109 has logged in. If this capability is omitted, no information is 110 conveyed about the server's status of supporting this extension. 112 IMAP server should respond with BAD response for the 64bit message 113 size messages sent by the IMAP client unless it issues "ENABLE 64BIT" 114 and the server responds with untagged ENABLED response that contains 115 64BIT in the current connection. 117 4. IMAP Protocol Changes 119 This document updates various fields in IMAP [RFC3501] to allow for 120 63 bit message sizes and body part sizes. It also updates the 121 following IMAP extensions: QUOTA [RFC2087], BINARY [RFC3516], URL- 122 PARTIAL [RFC5550] and APPENDLIMIT [RFC7889]. This document also 123 updates the IMAP URL specification [RFC5092] to allow use of such 124 message sizes and offsets in URL. 126 These changes are described in more details below. 128 4.1. Changes to IMAP APPENDLIMIT extension 130 When an IMAP server implements both 64BIT and APPENDLIMIT [RFC7889] 131 extensions, number64 values (see Section 6) are allowed after the 132 "APPENDLIMIT=" capability and "APPENDLIMIT" status data item. 134 4.2. Changes to IMAP BINARY extension 136 When an IMAP server implements both 64BIT and BINARY [RFC3516] 137 extensions, number64 values (see Section 6) are allowed in "literal8" 138 and "partial" ABNF non terminals. 140 4.3. Changes to IMAP URL-PARTIAL extension and IMAP URL 142 When an IMAP server implements both 64BIT and URL-PARTIAL [RFC5550] 143 extensions, number64 values (see Section 6) are allowed in the 144 "partial-range" ABNF non terminal. The "partial-range" ABNF non 145 terminal is defined in [RFC5092], so it also affects what is allowed 146 in IMAP URLs. 148 4.4. Changes to IMAP QUOTA extension 150 When an IMAP server implements both 64BIT and QUOTA [RFC2087] 151 extensions, number64 values (see Section 6) are allowed in resource 152 usage and resource limit values. 154 5. Examples 156 C: t1 CAPABILITY 157 S: * CAPABILITY IMAP4rev1 ID 64BIT 158 S: t1 OK foo 159 C: t2 ENABLE 64BIT 160 S: * ENABLED 64BIT 161 S: t2 OK foo 163 6. Formal Syntax 165 The following syntax specification uses the Augmented Backus-Naur 166 Form (ABNF) notation as specified in [ABNF]. 168 Non-terminals referenced but not defined below are as defined by 169 [RFC3501]. 171 All alphabetic characters are case-insensitive. The use of upper or 172 lower case characters to define token strings is for editorial 173 clarity only. Implementations MUST accept these strings in a case- 174 insensitive fashion. 176 [[Would it be helpful to split up ABNF by extension?]] 178 body-extension =/ number64 179 ; Alexey: I am not sure if this change is absolutely needed! 181 body-fld-lines = number64 183 body-fld-octets = number64 185 capability =/ "APPENDLIMIT" ["=" number64] 186 ;; capability is defined in RFC 3501. 188 ;; APPENDLIMIT capability is defined in RFC 7889. 190 fetch-att =/ "BODY" section [partial] / 191 "BODY.PEEK" section [partial] / 192 ; When BINARY extension is supported: 193 "BINARY" [".PEEK"] section-binary [partial] 195 literal = "{" number64 ["+"] "}" CRLF *CHAR8 196 ; number64 represents the number of CHAR8s. 197 ; NOTE: "+" can only present when LITERAL+/LITERAL- 198 ; is also advertised 200 literal8 = "~{" number64 ["+"] "}" CRLF *OCTET 201 ;; Updating RFC 4466 version. 202 ;; A string that might contain NULs. 203 ;; represents the number of OCTETs 204 ;; in the response string. 205 ;; The "+" is only allowed when both LITERAL+/LITERAL- 206 ;; and BINARY extensions are supported by the server 207 ;; [RFC7888] 209 msg-att-static =/ "RFC822.SIZE" SP number64 211 number64 = 1*DIGIT 212 ; Unsigned 63-bit integer 213 ; (0 <= n <= 9,223,372,036,854,775,807) 215 nz-number64 = digit-nz *DIGIT 216 ; Unsigned 63-bit integer 217 ; (0 < n <= 9,223,372,036,854,775,807) 219 partial-range = number64 ["." nz-number64] 220 ; Updates definition from RFC 5092 (IMAP URL). 221 ; This also affect URL-PARTIAL (RFC 5550). 223 partial = "<" number64 "." nz-number64 ">" 224 ; Partial FETCH request. 0-based offset of 225 ; the first octet, followed by the number of octets 226 ; in the fragment. 228 quota_resource = atom SP resource-usage SP resource-limit 229 ; Updates definition in RFC 2087. 231 setquota_resource = atom SP resource-limit 232 ; Updates definition in RFC 2087. 234 resource-limit = number64 235 resource-usage = number64 237 search-key =/ "LARGER" SP number64 / "SMALLER" SP number64 239 status-att-val =/ "APPENDLIMIT" SP (number64 / nil) 240 ;; status-att-val is defined in RFC 4466 241 ;; APPENDLIMIT status data item is defined in RFC 7889. 243 CHAR8 = 245 7. Security Considerations 247 TBD. 249 This document doesn't raise any other security concerns not already 250 raised by [RFC3501]. 252 8. IANA Considerations 254 IANA is asked to add "64BIT" to the IMAP Capabilities registry, using 255 this document as its reference. 257 9. Acknowledgments 259 TBD. 261 10. Normative References 263 [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax 264 Specifications: ABNF", STD 68, RFC 5234, January 2008. 266 [RFC2087] Myers, J., "IMAP4 QUOTA extension", RFC 2087, 267 DOI 10.17487/RFC2087, January 1997, 268 . 270 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 271 Requirement Levels", BCP 14, RFC 2119, 272 DOI 10.17487/RFC2119, March 1997, 273 . 275 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 276 4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003, 277 . 279 [RFC3516] Nerenberg, L., "IMAP4 Binary Content Extension", RFC 3516, 280 DOI 10.17487/RFC3516, April 2003, 281 . 283 [RFC4466] Melnikov, A. and C. Daboo, "Collected Extensions to IMAP4 284 ABNF", RFC 4466, DOI 10.17487/RFC4466, April 2006, 285 . 287 [RFC5092] Melnikov, A., Ed. and C. Newman, "IMAP URL Scheme", 288 RFC 5092, DOI 10.17487/RFC5092, November 2007, 289 . 291 [RFC5161] Gulbrandsen, A., Ed. and A. Melnikov, Ed., "The IMAP 292 ENABLE Extension", RFC 5161, DOI 10.17487/RFC5161, March 293 2008, . 295 [RFC5550] Cridland, D., Ed., Melnikov, A., Ed., and S. Maes, Ed., 296 "The Internet Email to Support Diverse Service 297 Environments (Lemonade) Profile", RFC 5550, 298 DOI 10.17487/RFC5550, August 2009, 299 . 301 [RFC7888] Melnikov, A., Ed., "IMAP4 Non-synchronizing Literals", 302 RFC 7888, DOI 10.17487/RFC7888, May 2016, 303 . 305 [RFC7889] SrimushnamBoovaraghamoorthy, J. and N. Bisht, "The IMAP 306 APPENDLIMIT Extension", RFC 7889, DOI 10.17487/RFC7889, 307 May 2016, . 309 Authors' Addresses 311 Alexey Melnikov 312 Isode Ltd 313 14 Castle Mews 314 Hampton, Middlesex TW12 2NP 315 UK 317 Email: Alexey.Melnikov@isode.com 319 Jayantheesh S B 320 Samsung Electronics America 321 685 US Highway 202/206 322 Bridgewater, New Jersey 08807 323 USA 325 Email: jayantheesh.sb@gmail.com