64bit body part and message sizes in IMAP4
draft-ietf-extra-imap-64bit-02

Document Type Active Internet-Draft (extra WG)
Last updated 2017-10-28
Replaces draft-melnikov-imap-64bit
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
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

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

   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 Notice

   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

Melnikov & Jayantheesh     Expires May 1, 2018                  [Page 1]
Internet-Draft 64bit body part and message sizes in IMAP4   October 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   3
   3.  64bit Extension . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Changes to IMAP APPENDLIMIT extension . . . . . . . . . .   3
     4.2.  Changes to IMAP BINARY extension  . . . . . . . . . . . .   3
     4.3.  Changes to IMAP URL-PARTIAL extension and IMAP URL  . . .   4
     4.4.  Changes to IMAP QUOTA extension . . . . . . . . . . . . .   4
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   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.

Melnikov & Jayantheesh     Expires May 1, 2018                  [Page 2]
Internet-Draft 64bit body part and message sizes in IMAP4   October 2017

2.  Requirements Notation

   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
Show full document text