| Network Working Group | A. Melnikov |
| Internet-Draft | Isode Ltd |
| Updates: 2087, 3501, 4466, 5092, 5550, | SB. Jayantheesh |
| 7888, 7889 (if approved) | Samsung Electronics America |
| Intended status: Standards Track | October 28, 2017 |
| Expires: May 1, 2018 |
64bit body part and message sizes in IMAP4
draft-ietf-extra-imap-64bit-02.txt
This document defines an IMAPv4rev1 extension that extends the existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit. Both the base IMAP specification (RFC 3501) and several extensions are updated.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
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 May 1, 2018.
Copyright (c) 2017 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 and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
IMAP [RFC3501] only allows body parts or message sizes which are 32 bit. This document introduces an IMAP extension that allows for message and body part sizes to be 63 bit. 63-bit values were chosen instead of 64-bit values in order to make implementations on various platforms (such as Java) easier.
The client wishing to use this extension MUST issue ENABLE 64BIT. Refer [RFC5161] for the usage of ENABLE command.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
In examples, "C:" and "S:" indicate lines sent by the client and server respectively. If a single "C:" or "S:" label applies to multiple lines, then the line breaks between those lines are for editorial clarity only and are not part of the actual protocol exchange.
An IMAP server that supports the 64bit extension advertises this by including the name 64BIT in its CAPABILITY list in the authenticated state. The server may also advertise this extension before the user has logged in. If this capability is omitted, no information is conveyed about the server's status of supporting this extension.
IMAP server should respond with BAD response for the 64bit message size messages sent by the IMAP client unless it issues "ENABLE 64BIT" and the server responds with untagged ENABLED response that contains 64BIT in the current connection.
This document updates various fields in IMAP [RFC3501] to allow for 63 bit message sizes and body part sizes. It also updates the following IMAP extensions: QUOTA [RFC2087], BINARY [RFC3516], URL-PARTIAL [RFC5550] and APPENDLIMIT [RFC7889]. This document also updates the IMAP URL specification [RFC5092] to allow use of such message sizes and offsets in URL.
These changes are described in more details below.
When an IMAP server implements both 64BIT and APPENDLIMIT [RFC7889] extensions, number64 values (see Section 6) are allowed after the "APPENDLIMIT=" capability and "APPENDLIMIT" status data item.
When an IMAP server implements both 64BIT and BINARY [RFC3516] extensions, number64 values (see Section 6) are allowed in "literal8" and "partial" ABNF non terminals.
When an IMAP server implements both 64BIT and URL-PARTIAL [RFC5550] extensions, number64 values (see Section 6) are allowed in the "partial-range" ABNF non terminal. The "partial-range" ABNF non terminal is defined in [RFC5092], so it also affects what is allowed in IMAP URLs.
When an IMAP server implements both 64BIT and QUOTA [RFC2087] extensions, number64 values (see Section 6) are allowed in resource usage and resource limit values.
C: t1 CAPABILITY
S: * CAPABILITY IMAP4rev1 ID 64BIT
S: t1 OK foo
C: t2 ENABLE 64BIT
S: * ENABLED 64BIT
S: t2 OK foo
The following syntax specification uses the Augmented Backus-Naur Form (ABNF) notation as specified in [ABNF].
Non-terminals referenced but not defined below are as defined by [RFC3501].
All alphabetic characters are case-insensitive. The use of upper or lower case characters to define token strings is for editorial clarity only. Implementations MUST accept these strings in a case- insensitive fashion.
[[Would it be helpful to split up ABNF by extension?]]
body-extension =/ number64
; Alexey: I am not sure if this change is absolutely needed!
body-fld-lines = number64
body-fld-octets = number64
capability =/ "APPENDLIMIT" ["=" number64]
;; capability is defined in RFC 3501.
;; APPENDLIMIT capability is defined in RFC 7889.
fetch-att =/ "BODY" section [partial] /
"BODY.PEEK" section [partial] /
; When BINARY extension is supported:
"BINARY" [".PEEK"] section-binary [partial]
literal = "{" number64 ["+"] "}" CRLF *CHAR8
; number64 represents the number of CHAR8s.
; NOTE: "+" can only present when LITERAL+/LITERAL-
; is also advertised
literal8 = "~{" number64 ["+"] "}" CRLF *OCTET
;; Updating RFC 4466 version.
;; A string that might contain NULs.
;; <number> represents the number of OCTETs
;; in the response string.
;; The "+" is only allowed when both LITERAL+/LITERAL-
;; and BINARY extensions are supported by the server
;; [RFC7888]
msg-att-static =/ "RFC822.SIZE" SP number64
number64 = 1*DIGIT
; Unsigned 63-bit integer
; (0 <= n <= 9,223,372,036,854,775,807)
nz-number64 = digit-nz *DIGIT
; Unsigned 63-bit integer
; (0 < n <= 9,223,372,036,854,775,807)
partial-range = number64 ["." nz-number64]
; Updates definition from RFC 5092 (IMAP URL).
; This also affect URL-PARTIAL (RFC 5550).
partial = "<" number64 "." nz-number64 ">"
; Partial FETCH request. 0-based offset of
; the first octet, followed by the number of octets
; in the fragment.
quota_resource = atom SP resource-usage SP resource-limit
; Updates definition in RFC 2087.
setquota_resource = atom SP resource-limit
; Updates definition in RFC 2087.
resource-limit = number64
resource-usage = number64
search-key =/ "LARGER" SP number64 / "SMALLER" SP number64
status-att-val =/ "APPENDLIMIT" SP (number64 / nil)
;; status-att-val is defined in RFC 4466
;; APPENDLIMIT status data item is defined in RFC 7889.
CHAR8 = <defined in RFC 3501>
TBD.
This document doesn't raise any other security concerns not already raised by [RFC3501].
IANA is asked to add "64BIT" to the IMAP Capabilities registry, using this document as its reference.
TBD.
| [ABNF] | Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. |
| [RFC2087] | Myers, J., "IMAP4 QUOTA extension", RFC 2087, DOI 10.17487/RFC2087, January 1997. |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC3501] | Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003. |
| [RFC3516] | Nerenberg, L., "IMAP4 Binary Content Extension", RFC 3516, DOI 10.17487/RFC3516, April 2003. |
| [RFC4466] | Melnikov, A. and C. Daboo, "Collected Extensions to IMAP4 ABNF", RFC 4466, DOI 10.17487/RFC4466, April 2006. |
| [RFC5092] | Melnikov, A. and C. Newman, "IMAP URL Scheme", RFC 5092, DOI 10.17487/RFC5092, November 2007. |
| [RFC5161] | Gulbrandsen, A. and A. Melnikov, "The IMAP ENABLE Extension", RFC 5161, DOI 10.17487/RFC5161, March 2008. |
| [RFC5550] | Cridland, D., Melnikov, A. and S. Maes, "The Internet Email to Support Diverse Service Environments (Lemonade) Profile", RFC 5550, DOI 10.17487/RFC5550, August 2009. |
| [RFC7888] | Melnikov, A., "IMAP4 Non-synchronizing Literals", RFC 7888, DOI 10.17487/RFC7888, May 2016. |
| [RFC7889] | SrimushnamBoovaraghamoorthy, J. and N. Bisht, "The IMAP APPENDLIMIT Extension", RFC 7889, DOI 10.17487/RFC7889, May 2016. |