--- 1/draft-ietf-extra-imap-64bit-02.txt 2018-03-04 10:14:20.540618673 -0800 +++ 2/draft-ietf-extra-imap-64bit-03.txt 2018-03-04 10:14:20.560619146 -0800 @@ -1,20 +1,20 @@ 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 +Intended status: Standards Track March 4, 2018 +Expires: September 5, 2018 64bit body part and message sizes in IMAP4 - draft-ietf-extra-imap-64bit-02.txt + draft-ietf-extra-imap-64bit-03.txt Abstract 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. Status of This Memo @@ -24,25 +24,25 @@ 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. + This Internet-Draft will expire on September 5, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 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 @@ -159,39 +159,37 @@ C: t2 ENABLE 64BIT S: * ENABLED 64BIT S: t2 OK foo 6. Formal Syntax 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]. + [RFC3501] or [RFC4466]. 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- @@ -225,45 +223,44 @@ ; 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 + 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 = 7. Security Considerations - TBD. - - This document doesn't raise any other security concerns not already + This document doesn't raise any new security concerns not already raised by [RFC3501]. 8. IANA Considerations IANA is asked to add "64BIT" to the IMAP Capabilities registry, using this document as its reference. 9. Acknowledgments - TBD. + Thank you to Stephan Bosch for pointing out which IMAP extensions + were not covered in earlier versions of this document. 10. Normative References [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, .