Re: [Extra] AD review of draft-ietf-extra-imap-status-size-01

"Chris Newman" <chris.newman@oracle.com> Thu, 10 May 2018 22:40 UTC

Return-Path: <chris.newman@oracle.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 4E7B112EBAD for <extra@ietfa.amsl.com>; Thu, 10 May 2018 15:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 dwnzJpnHmCex for <extra@ietfa.amsl.com>; Thu, 10 May 2018 15:40:47 -0700 (PDT)
Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76E1B12EB97 for <extra@ietf.org>; Thu, 10 May 2018 15:40:47 -0700 (PDT)
Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w4AMeeI2168811; Thu, 10 May 2018 22:40:40 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type : content-transfer-encoding; s=corp-2017-10-26; bh=RoR9bLDWMUlzR6Uv4zVnqL3Hm7xgtlPMoVW0cJKA/jY=; b=pFRb/yabzeja2p7uc0PcF2Rw+G1vnCzrjrKRF2M4H0sKDDOfPjuoTc41weZqwNWOPkiO TH4Q57KcKf1NK95i3o+pSVniwoQTE9tnFKuDbV6wJa1Dr4AlOnnpSS98/nIEK4KGNYXi JFXxR/yz/xZeg7w/682NqIDxf1Z7jnUpUurlwQ7l6iH6+DoNSi0i/JeOy3BlinImBq+A JhWO/wDRjUmgBFwM1FqU+surozt9GMTxsoTnD9e9JRYecNQsVCjv2BsiWMdMeWoKF2qf 2hPrcZ9OB/KbWnYc5HmuerT0YbTptHHLn798OZdjVkryMMmUDC/QHzuTg/fGDsoFoCbN kA==
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp2130.oracle.com with ESMTP id 2hvth99b7d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 10 May 2018 22:40:40 +0000
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w4AMeciM004464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 10 May 2018 22:40:39 GMT
Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w4AMec7n011551; Thu, 10 May 2018 22:40:38 GMT
Received: from [10.145.183.91] (/10.145.183.91) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 10 May 2018 15:40:38 -0700
From: Chris Newman <chris.newman@oracle.com>
To: Stephan Bosch <stephan.bosch@dovecot.fi>
Cc: extra@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>
Date: Thu, 10 May 2018 15:40:31 -0700
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <84D7D0C7-B12B-4DF2-B059-010CCE8F8271@oracle.com>
In-Reply-To: <9e94523e-d12d-e61c-d63b-e54dea7fd33e@dovecot.fi>
References: <5AE207FD.8020203@isode.com> <71D1116A-0D02-424B-9B22-58110DD8202D@oracle.com> <D6002572-B87C-47FA-98A1-D963F25F5B0E@oracle.com> <9e94523e-d12d-e61c-d63b-e54dea7fd33e@dovecot.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8889 signatures=668698
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805100208
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/5EUy839tCaQa01CGzbXQu0ZZgoY>
Subject: Re: [Extra] AD review of draft-ietf-extra-imap-status-size-01
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: Thu, 10 May 2018 22:40:49 -0000

On 10 May 2018, at 10:30, Stephan Bosch wrote:
> Op 05/05/2018 om 01:46 schreef Chris Newman:
>> On 4 May 2018, at 16:42, Chris Newman wrote:
>>
>>> I just noticed we implemented this in 2005 (under the "X-SUN-IMAP" 
>>> capability). Looking at the implementation, there's a significant 
>>> bug in the specification. Mailbox sizes can easily exceed 4GB; so 
>>> the ABNF for status-att-list needs to be replaced as follows:
>>>
>>>    status-att-list = status-att SP number63 *(SP status-att SP 
>>> number63)
>>>         ;; number63 is only permitted with extension status 
>>> attributes
>>>         ;; that explicitly allow it; such as SIZE
>>
>> Oh, just noticed RFC 4466 redefines that, so you instead need a 
>> normative reference to RFC 4466 and then do:
>>
>>    status-att-val /= "SIZE" SP number63
>
> A 4Gb mailbox is still quite huge these days, but you're right. The 
> QUOTA capability has the same problem: how did you address that?

Quota Storage partially dodges the problem by using 1K rather than 1 
byte units. However, the fact it doesn't allow 63-bit storage numbers is 
a specification bug (due to proof-by-example: the IMAP data model allows 
a mailbox with 4G messages each of 4G size). Implementations should 
ignore specification bugs like that (ours does). However, the 32-bit 
limit on UIDs, message size, and message sequence numbers is part of the 
fundamental IMAP data model. Changes to those values require an 
incompatible change to the IMAP data model that can break previously 
standards-compliant implementations. The IETF generally doesn't make 
that sort of change without a negotiated extension and implementations 
that ignore fundamental data models in the standards without negotiation 
are usually bad Internet citizens.

> That would have been solved by the 64BIT capability, but that one's on 
> hold now

There's no reason we can't have this spec use a 63-bit number at the 
time we write it. Clients won't get this data unless they ask for it and 
servers won't send it unless they've advertised it. This requires no 
change to the IMAP data model so no separate negotiation is needed to 
use 63-bit numbers here. It's just an extra line of ABNF and with no 
impact on data model and very little impact on implementations. A 
normative dependency on a draft that changes the IMAP data model is a 
change to SIZE that I would oppose. But use of a 32-bit integer is a bug 
in the SIZE draft (again via proof-by-example).

		- Chris

> Bron, Alexey, opinions?
>
> Regards,
>
> Stephan
>
>>
>>         - Chris
>>
>>>    number63  = 1*DIGIT
>>>                           ;; Positive 
>>> unsigned 63-bit integer
>>>                           ;; (0 <= n <= 
>>> 9,223,372,036,854,775,807).
>>>
>>>         - Chris
>>>
>>> On 26 Apr 2018, at 10:10, Alexey Melnikov wrote:
>>>
>>>> Hi,
>>>>
>>>> I've been following discussions on this document and it is ready 
>>>> for
>>>> IETF Last Call, which I just initiated.
>>>>
>>>> One nit: I believe the following reference is now Normative, due to
>>>> added SHOULD level requirement:
>>>>
>>>>  [QUOTA]
>>>>
>>>> Please update the document to reflect this next time the document 
>>>> is
>>>> revised.
>>>>
>>>> Best Regards,
>>>> Alexey, as AD.
>>>>
>>>> _______________________________________________
>>>> Extra mailing list
>>>> Extra@ietf.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=B73C8TOrpzVRz_O5v_4esOIRwnbdcZoZaulZWKyZwBY&s=Av_oW8rLHO6EMocPg9SJXED-Ta7xK6PRHohZ6tFZmmM&e=
>>>
>>> _______________________________________________
>>> Extra mailing list
>>> Extra@ietf.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=ErU-4WHaHwqAH1nltCBHaf7zbhatpz2gGlB_BH0n3uI&s=HPU9C98qqq9ZOoEpMPOpUKits0ILuqWjGwmCx6_ZCvo&e=
>>
>> _______________________________________________
>> Extra mailing list
>> Extra@ietf.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=5HJofT5ocTAB71bioSeN2ztVNEW92Tx14L2kdo_8_PQ&s=VsTTjiVSxN0fQkrv_AoqVm9VLp5Rw5qTjsqJJEODbT4&e=