Re: [Extra] Some comments on draft-ietf-extra-imap-64bit

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 18 September 2017 12:01 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF971321C9 for <extra@ietfa.amsl.com>; Mon, 18 Sep 2017 05:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8A0qRuVWXY1u for <extra@ietfa.amsl.com>; Mon, 18 Sep 2017 05:01:54 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 4A006132193 for <extra@ietf.org>; Mon, 18 Sep 2017 05:01:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1505736113; d=isode.com; s=june2016; i=@isode.com; bh=xAJnRxvdyVbqgQcI+aIBwhZmp9WeAIZRZJX0TzyOI4o=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ZldWHgbRunZjHVGKAOJ4w+Fw4ljt1WM77jG84MxirRrsk32kwvxxauYsQQgaTgZ2IbOZRh l37tliipgK8P3Q5g48jx89tqyxtkmjvUNDmAnH8u5OrZdPPT+yghZTOCGjzQc1088aAiab SMJCOVNMKza7xX4ZKzjxfj3GvllVr6o=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <Wb-1sABsZlaV@waldorf.isode.com>; Mon, 18 Sep 2017 13:01:53 +0100
To: Stephan Bosch <stephan@rename-it.nl>
Cc: extra@ietf.org
References: <0871fcf6-f0c5-a4b7-f1e4-7a535d78d776@rename-it.nl>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <23e24098-e6c2-cf67-e667-bc8cbcba7f33@isode.com>
Date: Mon, 18 Sep 2017 13:01:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
In-Reply-To: <0871fcf6-f0c5-a4b7-f1e4-7a535d78d776@rename-it.nl>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------D7F84FB6C434E61AB6C623F0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/MX8ep9jvInwGZdevL8SxQF5XTns>
Subject: Re: [Extra] Some comments on draft-ietf-extra-imap-64bit
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 12:01:56 -0000

Hi Stephan,


On 15/09/2017 17:06, Stephan Bosch wrote:
> Hi,
>
> I gave draft-ietf-extra-imap-64bit a quick look. I have a few comments 
> on the syntax specification.
>
> First of all, the elements fetch-att, msg-att-static, and search-key 
> are just copy-pasted from RFC 3501. Those are meant to have number64 
> instead.
Yes, fixed.

> I wonder whether it would be a good idea to have intermediary elements 
> called e.g. `msg-size = number64' and `msg-lines = number64', so that 
> future changes/extensions to the message size and line count syntax 
> aren't such a pain anymore.
Might be a good idea. If you send me the specific ABNF fragment, this 
will speed up the process.

> The "capability" syntax element is not extended (arguably not all 
> specifications do this).
This is typically done in prose.

> Finally, the following IMAP capabilities have syntax that is affected 
> by this extension:
>
> QUOTA - https://www.ietf.org/rfc/rfc2087.txt
Good point, I will have a look.
> BINARY - https://www.ietf.org/rfc/rfc3516.txt (not only literal8)

Looking at the ABNF:

    append         =/  "APPEND" SP mailbox [SP flag-list]
                       [SP date-time] SP literal8

    fetch-att      =/  "BINARY" [".PEEK"] section-binary [partial]
                       / "BINARY.SIZE" section-binary

    literal8       =   "~{" number "}" CRLF *OCTET
                       ; <number> represents the number of OCTETs
                       ; in the response string.

    msg-att-static =/  "BINARY" section-binary SP (nstring / literal8)
                       / "BINARY.SIZE" section-binary SP number

    partial        =   "<" number "." nz-number ">"

    resp-text-code =/  "UNKNOWN-CTE"

    section-binary =   "[" [section-part] "]"



I don't think we need 64bit section numbers, but I missed updating 
"partial".

> URL-PARTIAL - https://www.ietf.org/rfc/rfc5550.txt -> 
> https://www.ietf.org/rfc/rfc5092.txt (partial-range)
> APPENDLIMIT - https://www.rfc-editor.org/rfc/rfc7889.txt
Yes, these need to be looked at as well.

Best Regards,
Alexey