draft-ietf-extra-imap-64bit-02.txt   draft-ietf-extra-imap-64bit-03.txt 
Network Working Group A. Melnikov Network Working Group A. Melnikov
Internet-Draft Isode Ltd Internet-Draft Isode Ltd
Updates: 2087, 3501, 4466, 5092, 5550, SB. Jayantheesh Updates: 2087, 3501, 4466, 5092, 5550, SB. Jayantheesh
7888, 7889 (if approved) Samsung Electronics America 7888, 7889 (if approved) Samsung Electronics America
Intended status: Standards Track October 28, 2017 Intended status: Standards Track March 4, 2018
Expires: May 1, 2018 Expires: September 5, 2018
64bit body part and message sizes in IMAP4 64bit body part and message sizes in IMAP4
draft-ietf-extra-imap-64bit-02.txt draft-ietf-extra-imap-64bit-03.txt
Abstract Abstract
This document defines an IMAPv4rev1 extension that extends the This document defines an IMAPv4rev1 extension that extends the
existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit. existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit.
Both the base IMAP specification (RFC 3501) and several extensions Both the base IMAP specification (RFC 3501) and several extensions
are updated. are updated.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 May 1, 2018. This Internet-Draft will expire on September 5, 2018.
Copyright Notice 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. 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 34 skipping to change at page 4, line 34
C: t2 ENABLE 64BIT C: t2 ENABLE 64BIT
S: * ENABLED 64BIT S: * ENABLED 64BIT
S: t2 OK foo S: t2 OK foo
6. Formal Syntax 6. Formal Syntax
The following syntax specification uses the Augmented Backus-Naur The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) notation as specified in [ABNF]. Form (ABNF) notation as specified in [ABNF].
Non-terminals referenced but not defined below are as defined by 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 All alphabetic characters are case-insensitive. The use of upper or
lower case characters to define token strings is for editorial lower case characters to define token strings is for editorial
clarity only. Implementations MUST accept these strings in a case- clarity only. Implementations MUST accept these strings in a case-
insensitive fashion. insensitive fashion.
[[Would it be helpful to split up ABNF by extension?]] [[Would it be helpful to split up ABNF by extension?]]
body-extension =/ number64 body-extension =/ number64
; Alexey: I am not sure if this change is absolutely needed!
body-fld-lines = number64 body-fld-lines = number64
body-fld-octets = number64 body-fld-octets = number64
capability =/ "APPENDLIMIT" ["=" number64] capability =/ "APPENDLIMIT" ["=" number64]
;; capability is defined in RFC 3501. ;; capability is defined in RFC 3501.
;; APPENDLIMIT capability is defined in RFC 7889. ;; APPENDLIMIT capability is defined in RFC 7889.
fetch-att =/ "BODY" section [partial] / fetch-att =/ "BODY" section [partial] /
"BODY.PEEK" section [partial] / "BODY.PEEK" section [partial] /
; When BINARY extension is supported: ; When BINARY extension is supported:
"BINARY" [".PEEK"] section-binary [partial] "BINARY" [".PEEK"] section-binary [partial]
literal = "{" number64 ["+"] "}" CRLF *CHAR8 literal = "{" number64 ["+"] "}" CRLF *CHAR8
; number64 represents the number of CHAR8s. ; number64 represents the number of CHAR8s.
; NOTE: "+" can only present when LITERAL+/LITERAL- ; NOTE: "+" can only present when LITERAL+/LITERAL-
skipping to change at page 6, line 4 skipping to change at page 5, line 50
; the first octet, followed by the number of octets ; the first octet, followed by the number of octets
; in the fragment. ; in the fragment.
quota_resource = atom SP resource-usage SP resource-limit quota_resource = atom SP resource-usage SP resource-limit
; Updates definition in RFC 2087. ; Updates definition in RFC 2087.
setquota_resource = atom SP resource-limit setquota_resource = atom SP resource-limit
; Updates definition in RFC 2087. ; Updates definition in RFC 2087.
resource-limit = number64 resource-limit = number64
resource-usage = number64
resource-usage = number64
search-key =/ "LARGER" SP number64 / "SMALLER" SP number64 search-key =/ "LARGER" SP number64 / "SMALLER" SP number64
status-att-val =/ "APPENDLIMIT" SP (number64 / nil) status-att-val =/ "APPENDLIMIT" SP (number64 / nil)
;; status-att-val is defined in RFC 4466 ;; status-att-val is defined in RFC 4466
;; APPENDLIMIT status data item is defined in RFC 7889. ;; APPENDLIMIT status data item is defined in RFC 7889.
CHAR8 = <defined in RFC 3501> CHAR8 = <defined in RFC 3501>
7. Security Considerations 7. Security Considerations
TBD. This document doesn't raise any new security concerns not already
This document doesn't raise any other security concerns not already
raised by [RFC3501]. raised by [RFC3501].
8. IANA Considerations 8. IANA Considerations
IANA is asked to add "64BIT" to the IMAP Capabilities registry, using IANA is asked to add "64BIT" to the IMAP Capabilities registry, using
this document as its reference. this document as its reference.
9. Acknowledgments 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 10. Normative References
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC2087] Myers, J., "IMAP4 QUOTA extension", RFC 2087, [RFC2087] Myers, J., "IMAP4 QUOTA extension", RFC 2087,
DOI 10.17487/RFC2087, January 1997, DOI 10.17487/RFC2087, January 1997,
<https://www.rfc-editor.org/info/rfc2087>. <https://www.rfc-editor.org/info/rfc2087>.
 End of changes. 11 change blocks. 
13 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/