
From nobody Mon Feb  1 07:23:50 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5243A1218; Mon,  1 Feb 2021 07:23:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 07:23:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/So4EOBis74m8bmOKovqdDhktySE>
Subject: [Extra] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-extra-imap4rev2-26=3A_=28with_COMMENT=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 15:23:44 -0000

Ã‰ric Vyncke has entered the following ballot position for
draft-ietf-extra-imap4rev2-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document. Collecting and aggregating all
the previous updates is really useful. The numerous examples are really helpful.

I must admit though that "unpublished IMAP2bis protocols" makes me wonder why
it is mentioned if not public... Also, "network connection" is kind of weird
for an Internet based on connectionless IP layer... ;-)

Please find below some non-blocking COMMENT points (but replies would be
appreciated), and some nits.

I hope that this helps to improve the document,

Regards,

-Ã©ric

== COMMENTS ==

-- Section 2.3.2 --
Why two flags associated to "junk" but only one for "phishing" ?

-- Section 8 --
This example uses LOGIN method that is not recommended on plain text connection
(see 6.2.3). Perhaps worth saying that this example works over implicit TLS or
better use a AUTH method?

== NITS ==

-- Section 4.3 --
"synchonizing literal" ?

-- Section 6.3.12 --
The example contains "Content-Type: TEXT/PLAIN; CHARSET=US-ASCII" while in most
email headers that I have seen, the value is in lowercase... May I assume that
case is *not* relevant (because not part of the email message but part of IMAP)
? If so, this value reads lie SHOUTING to me ;-)

-- Section 6.4.4 --
The example dates are in 1994... perhaps worth updating ?  ;-) Other examples
are in 2006




From nobody Mon Feb  1 09:02:08 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 855343A12E5; Mon,  1 Feb 2021 09:02:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <161219892591.2230.16606034754432970648@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 09:02:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/-Gs7SXQwdO-b4tbp7XUE2rEdpKo>
Subject: [Extra] Robert Wilton's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 17:02:07 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-extra-imap4rev2-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for your work on this important update to IMAP, hopefully putting it
on a better footing for the future.

I'm balloting 'No Obj' in the sense that I'm trusting the ADs (and authors and
WG) and I doubt that my review of an update to a protocol that I don't know
would bring anything new or helpful to the standardization process.

I do have a meta-process question though: I suspect that there are other
protocols/RFCs that could potentially benefit from a similar treatment (DNS
springs to mind), where the old specs have many updates.  With the benefit of
hindsight, would the authors recommend doing this for other significant old
RFCs?  Or did this turn out to be significantly more effort than anticipated?

Regards,
Rob




From nobody Mon Feb  1 10:19:04 2021
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 E69A93A1386; Mon,  1 Feb 2021 10:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 puOU6m11q05P; Mon,  1 Feb 2021 10:18:56 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0856A3A1384; Mon,  1 Feb 2021 10:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612203535; d=isode.com; s=june2016; i=@isode.com; bh=LvG9rcXTSakVnBxVv5XJuWbARBdulIhLhSY0EWfVOCw=; 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=sbMZEtWWepYz5ASW4eai1R8QXHqBuK0wpRseAJQ/G4F8RT3NXVjq78RQO2dAom/iGXu2+T 0gCukmEHRp4MhyWAZ3XnWiJavPrmVJKTrNEpnxVg5Q3DE9BMLEmYm9+UbjQxy9eJZ9nyGv gQ7AZo3Uf4ZjDzcjrGypBnKV4lzetuY=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YBhGDgAqZlSH@statler.isode.com>; Mon, 1 Feb 2021 18:18:54 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: =?UTF-8?Q?=c3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
Message-ID: <d30bbdde-a98f-9b10-8293-86a37cd477a4@isode.com>
Date: Mon, 1 Feb 2021 18:18:54 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/toFxEXtJ5_pF4ecKmaIo0OkS6aE>
Subject: Re: [Extra]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-extra-imap4rev2-26=3A_=28with_COMMENT=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 18:18:59 -0000

Hi =C3=89ric,

Thank you for your review. Comments below.

On 01/02/2021 15:23, =C3=89ric Vyncke via Datatracker wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you for the work put into this document. Collecting and aggregating =
all
> the previous updates is really useful. The numerous examples are really he=
lpful.
>
> I must admit though that "unpublished IMAP2bis protocols" makes me wonder =
why
> it is mentioned if not public...
It was popular at the time and I believe there was a draft at some=20
point. This actually predates my participation in IETF.
>   Also, "network connection" is kind of weird
> for an Internet based on connectionless IP layer... ;-)
>
> Please find below some non-blocking COMMENT points (but replies would be
> appreciated), and some nits.
>
> I hope that this helps to improve the document,
>
> Regards,
>
> -=C3=A9ric
>
> =3D=3D COMMENTS =3D=3D
>
> -- Section 2.3.2 --
> Why two flags associated to "junk" but only one for "phishing" ?
> -- Section 8 --
> This example uses LOGIN method that is not recommended on plain text conne=
ction
> (see 6.2.3). Perhaps worth saying that this example works over implicit TL=
S or
> better use a AUTH method?
Yes, good idea. Apparently nobody looks at this except for IESG ;-).
> =3D=3D NITS =3D=3D
>
> -- Section 4.3 --
> "synchonizing literal" ?
Fixed, thank you :-).
> -- Section 6.3.12 --
> The example contains "Content-Type: TEXT/PLAIN; CHARSET=3DUS-ASCII" while =
in most
> email headers that I have seen, the value is in lowercase... May I assume =
that
> case is *not* relevant (because not part of the email message but part of =
IMAP)
> ? If so, this value reads lie SHOUTING to me ;-)

This is defined in RFC 2045, which defines Content-Type header field=20
syntax. Basically, all three: the media type ("TEXT/PLAIN"), parameter=20
name ("CHARSET") and charset parameter value ("US-ASCII") are all=20
defined to be case insensitive.

So no, this has nothing to do with IMAP.

As an editor, I do like to pick some examples demonstrating=20
case-insensitivity and other unusual conditions.

> -- Section 6.4.4 --
> The example dates are in 1994... perhaps worth updating ?  ;-) Other examp=
les
> are in 2006

This is a revision of RFC 3501, which is a revision of RFC 2060, etc.

We could update examples, but they are still valid. Changes would most=20
likely affect day-of-the-week, which might in turn change literal=20
sizes... So changes can introduce new bugs.

Best Regards,

Alexey


From nobody Mon Feb  1 13:52:36 2021
Return-Path: <evyncke@cisco.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 3D4C63A1507; Mon,  1 Feb 2021 13:52:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=YlcECN8a; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZB3fexFJ
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 RKZ0Pr8MJUQG; Mon,  1 Feb 2021 13:52:19 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64A6E3A1500; Mon,  1 Feb 2021 13:52:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4906; q=dns/txt; s=iport; t=1612216339; x=1613425939; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uOkZ0BZ4KWuWQObzktchMXux5G8ykrs/2zHdgHwm1ZI=; b=YlcECN8aD52KyRfc3ckmAChdVb2cWEQBoaiPkLnft3ITVCCNTFmblawo mL1NTo508INP1fbGmE8rssY90lFUR9DARrsC3Gw7X92gcINl9WD3/Qydy BfPQmROvQLBze6x6fhVKfJJTznKRXEM4/4m7LS2UToTKqm3npR08CaKTz 0=;
X-IPAS-Result: =?us-ascii?q?A0DYAgBmdRhgkIsNJK1cBhwBAQEBAQEHAQESAQEEBAEBQ?= =?us-ascii?q?IFPgVMpKIFXMjGEQINIA44JA5kZgUKBEQNUCwEBAQ0BAS0CBAEBhEoCF4FiA?= =?us-ascii?q?iU4EwIDAQEBAwIDAQEBAQUBAQECAQYEFAEBAQEBAYY4DYVzAQEBBCMRDAEBN?= =?us-ascii?q?wELBAIBCBEDAQIBAgISARMCAgIwFQUDCAIEAQ0FgyaCVgMuAaYIAooldoEyg?= =?us-ascii?q?wUBAQaFDBiCEgmBDiqCd4QFgjIdg3MmG4FBP4ERJxyBWH4+hAkBEgEREBcxA?= =?us-ascii?q?oJPNIIsgkQGZARDCBwbaVIoKg8pj1KDLYdmnE6BCgqCdpVChjsDH4Mvij2VJ?= =?us-ascii?q?4R2jzSCB59gAgICAgQFAg4BAQaBbSFpcHAVZQGCPlAXAg2LSIJZGh1uAQiCQ?= =?us-ascii?q?4pYdDcCBgEJAQEDCQF7iFUPF4IeAQE?=
IronPort-PHdr: =?us-ascii?q?9a23=3AjsKDSBDw7bCqTooICdXcUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qw00A3IRoLX5rRPjO+F+6zjWGlV55GHvThCdZFXTB?= =?us-ascii?q?YKhI0QmBBoG8+KD0D3bZuIJyw3FchPThlpqne8N0UGGd35a1CUqXq3vnYeHx?= =?us-ascii?q?zlPl9zIeL4UofZk8Ww0bW0/JveKwVFjTawe/V8NhKz+A7QrcIRx4BlL/U8?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,393,1602547200"; d="scan'208";a="638760744"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Feb 2021 21:52:17 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 111LqHo6006860 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Feb 2021 21:52:17 GMT
Received: from xfe-aln-004.cisco.com (173.37.135.124) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 1 Feb 2021 15:52:17 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xfe-aln-004.cisco.com (173.37.135.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.3; Mon, 1 Feb 2021 15:52:16 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 1 Feb 2021 15:52:16 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z15mL4Inc7wGEdRGMJtTs5DNMHq72ecDruZPpgTbKUVNz0sU7TV75UoDortp9DicAJc4WvcKMFnTO2BGISyHvGRqf/XQIv4J/NxzjRuvKCUeAUFHOKHJtdXtD9wljXZXicM3wnye/Hoh9xo50IyofaQbVUg5elpT/5DzghepfVugMZ+eCBHBpDNmhyNP/BMbV2LBVsGH7QNi7OMEO77fNJtPZ2Yu+eK4Oieww6h6aLgdPigX7kYnMvFDDpnysW3LF7lPaFXUjEMbi3Pa6NqBtbGoYB5LBBl+bYx+eXXzt1Jq9+WpQwF2BOmfmeLcnaBfrhnQkJperriSqotWt7KkbA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uOkZ0BZ4KWuWQObzktchMXux5G8ykrs/2zHdgHwm1ZI=; b=JsYYOsAP5IEmS5hYxZHW8000DMfyWtHfJHH5ZYdOxlTS/DOsZJAGkQuUK33jF1VkdlwzPnNhzaWjyL39/vA+5B8SMgh8LqzoDw5jBxdHmQULqJH62HtdzrrtEsHH9lFtrPDVEsotioLDgdB70gNpROHDMJdUPRXRh+MmWo7YdaV8U6k/sc3hHdelD0GEc7KaS34/carYTFI/baO2Hta/4BpveY5sIk9wx4AmFSPepQ0zpeYt80HfLM4vdFc5U05IEs05xBV6d3MZ5kNUib9DfTlUp7lttZq6722xhC9sLHlnkz2F0USKLWDqg91yXXbYcs4gTr0zC5LidPToRz7g5g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uOkZ0BZ4KWuWQObzktchMXux5G8ykrs/2zHdgHwm1ZI=; b=ZB3fexFJRV8cPrEMXQwVqr1ts3B5sDIfhVM4IN5sBWAgY5lkPeIVqVfec9HR2z8gBkjpu6qpmcUl0P2QliJPib1KkvtgNzS9o4sroRSBnMq1LRdOEN79wnj0/72NmJfikCnJLs9daBUdYKrLl09Y3Z9n5fX1gIulYB2TiCQKeig=
Received: from PH0PR11MB4966.namprd11.prod.outlook.com (2603:10b6:510:42::21) by PH0PR11MB4839.namprd11.prod.outlook.com (2603:10b6:510:42::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.17; Mon, 1 Feb 2021 21:52:14 +0000
Received: from PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::7d4c:6b05:89aa:85b]) by PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::7d4c:6b05:89aa:85b%3]) with mapi id 15.20.3805.025; Mon, 1 Feb 2021 21:52:14 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, The IESG <iesg@ietf.org>
CC: "extra@ietf.org" <extra@ietf.org>, "brong@fastmailteam.com" <brong@fastmailteam.com>, "draft-ietf-extra-imap4rev2@ietf.org" <draft-ietf-extra-imap4rev2@ietf.org>, "extra-chairs@ietf.org" <extra-chairs@ietf.org>
Thread-Topic: =?utf-8?B?W0V4dHJhXSDDiXJpYyBWeW5ja2UncyBObyBPYmplY3Rpb24gb24gZHJhZnQt?= =?utf-8?Q?ietf-extra-imap4rev2-26:_(with_COMMENT)?=
Thread-Index: AQHW+K5TTOaIL4oEHk+xWOjUGe+nxapDnAgAgABMXYA=
Date: Mon, 1 Feb 2021 21:52:14 +0000
Message-ID: <D3B34FEB-9A50-493E-93CC-8999FAD178DA@cisco.com>
References: <161219302403.27128.9041237679555543330@ietfa.amsl.com> <d30bbdde-a98f-9b10-8293-86a37cd477a4@isode.com>
In-Reply-To: <d30bbdde-a98f-9b10-8293-86a37cd477a4@isode.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: isode.com; dkim=none (message not signed) header.d=none;isode.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:c0c1:36:18f:6f26:c233:5c6f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0b638458-b5be-4355-70b1-08d8c6fba2f2
x-ms-traffictypediagnostic: PH0PR11MB4839:
x-microsoft-antispam-prvs: <PH0PR11MB48392F8CC3BD053929A3C319A9B69@PH0PR11MB4839.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: r1i9CDSUtLdmLCryUbz/6D5UnveU7UFbnPtcxpbVazWMNIecaNDAuNO7nh4DlGYmpgga9MI0VysVGRoKdps65tKaZMKfBBGGObAgwy7Oi6k1s7bAg/HSxTIMRxmAuuhsvtl66G1tyAtMrz026bV0zeEaiCtZgXx3riWTXFzLMhVQKJRxM9H3POWXkOSHddjKrL7qwiLQQ9RjkoPQwib08O1je1cJlzaewj1yXBtDujPBVYWoqksz1zVVL5rd7TxnQh3K+SnKJ9vPnjlRHj9u/jQrYwFfFDIU+3bw3ZyotnLJ/4dneJoghhBBVAX7LXp4B8WRLYMMmGkU/Nf8FPff/fgEZ+ixxSSmXl1Dwmh6687yb2CnIianvcw7hsYYKIzehafZdVeVPPn78EnLoiw/uBRsLVT0GYU9BqpftkAJVT01KPriFWXXuQ9Vm9HQAyqcvbghWZoWymhv+cKxwL04JsUlzuoGislNeG3Ev7Nv5u0yxiHYTg8BdCH9tNgJhxnnhu2//aosKOQrSJ9MFA1nu5KFXc8PXP5BF7WBoIoOivP/AQb+yjY8szAYmZyVB0322H7+zBv39AlTFuAOPT7oyg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:PH0PR11MB4966.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(376002)(346002)(366004)(136003)(396003)(66946007)(76116006)(2616005)(66476007)(6486002)(186003)(4326008)(71200400001)(66556008)(66446008)(64756008)(6506007)(53546011)(36756003)(33656002)(8936002)(5660300002)(110136005)(54906003)(2906002)(224303003)(86362001)(316002)(478600001)(6512007)(66574015)(91956017)(83380400001)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?djM1MTYvU0lIYUhtNHlBTXZPRTFOTS9YL1QySlFUcC9UOFAweWZTZndNcDJ6?= =?utf-8?B?Rm9kYlF0TmlybmhvVUh6Q2JKa3BMaStQdFJ4VWErSUxlOHcyVnE5UFdkUC80?= =?utf-8?B?UExVQkJnYnl4RUNTLzBBcmNXRVE0ODRJNnF5UWUzT0NVMGovUTRuNnNVdXZy?= =?utf-8?B?SGV2aDhJRUJsSFRmNjVqNVhGNHRWOERFN25BS0QxQ1gwYWZrbjBwQ09ndDhG?= =?utf-8?B?OXh2M0UraTNZQkJkZWVjZkxhby9RNm5OcFRlMnpXbitwUUl0Z2dGSzVDbTZh?= =?utf-8?B?ZHVEZ2hvZWNqYXdIemlNajlmOXhhd1E4cDVnSU5hazByc3k4YVM1VVJhaStv?= =?utf-8?B?djJGdHZQbE80VEZraWxheEhCMVA1dG43SEl0L1Y5SURtblg2ajhEY1BabFNw?= =?utf-8?B?V09zQVpGY3ZwT3haeU9ySWR0L0p1MDFUQisyMDJOT1NVQjk2d3FwT25zVDV0?= =?utf-8?B?eUhEdk5lTEdXSE5mcFRmZzJDTnJIMmIwS3JOcGlESVdtZmhpVmJkWitOd3U3?= =?utf-8?B?bExzZENpZFNQKzRCREFiTGxNWlZrS1VrNkNXMG5SRFZzL2d4bmJDN2VHbS9h?= =?utf-8?B?TkhKS1BPWU1PZTRoMzlmMjdEbW94OXVXK0JBMktqeElXQ3Q5UmFFaTBMc2JL?= =?utf-8?B?c3pYb1A5MFNXeFVyZExYYlR2NThRdUJvbXk3TEFuQnp6cWxuem9JRlEzLzh6?= =?utf-8?B?NlQ3Z0pseFdEUGNOQkMyNTcyMFlZbWxqYk4zdDFEaCsrUEpTYWd6RWpLZVJx?= =?utf-8?B?ZVZCcXI0UjJYT2ZuTFBlNkdQMmVaaUxDbngydTc0WThEeFZjQkkzdGV6UFN0?= =?utf-8?B?dVBvWEk0V045cm5xcHFHY0ZST3VQeGdOQVRoMTFxb3A3L1dEU0tWeGh1V3dL?= =?utf-8?B?VUYxQ25Rb3czbXdmdW5qclYwajVOMjA2c2V4UFBkdFc4QUw4bzdZUjVCcW9q?= =?utf-8?B?dWNYRDhuQ1N2aWw3U2tvckl2azBwK1hKTUZlcFBpSndZNjQ4cWxnZmRIOEM5?= =?utf-8?B?KzM2QzF0R0hDMXpZbEZ1cVpBbmVSWUxFaHNvOWNLMU9rSlNtSGVQMEFSVEFT?= =?utf-8?B?ajFhL1ZMS013UU91ekl0VzExakFIUk5Db3lIb3VUTzVtZzZtRVJiRUwwTVlL?= =?utf-8?B?bnY2MlN2c3hnejFKN2puM0ZUUzhsOUk0SklCWWt5V003bDh0c3hnUFpBZUJz?= =?utf-8?B?UGtUdy9jazdDNjBHZFRBclIrNUZtb04wMWhGMVB2R3ZlOGZWajZhZ0ZzbnZi?= =?utf-8?B?Yk9hcitwUDkzTFU5K1dBOENSZHFDWWU3bWRYU1FFOExZQmo1UkY1cmZQMGM1?= =?utf-8?B?a0JnNGMxcGdTWjE0KzZkbVd1NFJDNmNJRVJqU3ZtSGk3YUNBRmVLTkJwWWRO?= =?utf-8?B?US9iVkFwSWZXUFZIMjVBQStidlJ6WTdCY0svY2h5eVovNWZyV3VKZndFbDlK?= =?utf-8?B?aUE1NStvYjN1dmZhNWpGUlRQZEpuTkNub3dLN1RxQ3R0NVNCSXhuaGIzaUZX?= =?utf-8?Q?m5wCI8dVvcvUlcxNwP4nvhqUykw?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <230371CBE9AFB342AFC34E4D0D5FC404@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB4966.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0b638458-b5be-4355-70b1-08d8c6fba2f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2021 21:52:14.4539 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: T5061t/6b9Z7nxc0OiQurgsh9SCOuGgJve5Tz08Jnblrz8AS24Z/C9HCeeYmutArKVwGlXtfqwB9lQ49c9ISAw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB4839
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/R0qD7NVXDpvvNWidQE9pI2FB9xc>
Subject: Re: [Extra]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-extra-imap4rev2-26=3A_=28with_COMMENT=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 21:52:24 -0000

QWxleGV5DQoNCkkgYXBwcmVjaWF0ZSB5b3VyIHF1aWNrIHJldHVybiBhbmQgeW91ciBwYXJ0aWFs
IGFuc3dlcnMuDQoNCkkgc21pbGVkIHdoZW4gcmVhZGluZyAiQXMgYW4gZWRpdG9yLCBJIGRvIGxp
a2UgdG8gcGljayBzb21lIGV4YW1wbGVzIGRlbW9uc3RyYXRpbmcgY2FzZS1pbnNlbnNpdGl2aXR5
IGFuZCBvdGhlciB1bnVzdWFsIGNvbmRpdGlvbnMuIg0KDQotw6lyaWMNCg0K77u/LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEFsZXhleSBNZWxuaWtvdiA8YWxleGV5Lm1lbG5pa292
QGlzb2RlLmNvbT4NCkRhdGU6IE1vbmRheSwgMSBGZWJydWFyeSAyMDIxIGF0IDE5OjE5DQpUbzog
RXJpYyBWeW5ja2UgPGV2eW5ja2VAY2lzY28uY29tPiwgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+
DQpDYzogImV4dHJhQGlldGYub3JnIiA8ZXh0cmFAaWV0Zi5vcmc+LCAiYnJvbmdAZmFzdG1haWx0
ZWFtLmNvbSIgPGJyb25nQGZhc3RtYWlsdGVhbS5jb20+LCAiZHJhZnQtaWV0Zi1leHRyYS1pbWFw
NHJldjJAaWV0Zi5vcmciIDxkcmFmdC1pZXRmLWV4dHJhLWltYXA0cmV2MkBpZXRmLm9yZz4sICJl
eHRyYS1jaGFpcnNAaWV0Zi5vcmciIDxleHRyYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBS
ZTogW0V4dHJhXSDDiXJpYyBWeW5ja2UncyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1leHRy
YS1pbWFwNHJldjItMjY6ICh3aXRoIENPTU1FTlQpDQoNCiAgICBIaSDDiXJpYywNCg0KICAgIFRo
YW5rIHlvdSBmb3IgeW91ciByZXZpZXcuIENvbW1lbnRzIGJlbG93Lg0KDQogICAgT24gMDEvMDIv
MjAyMSAxNToyMywgw4lyaWMgVnluY2tlIHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCiAgICA+IC0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCiAgICA+IENPTU1FTlQ6DQogICAgPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogICAgPg0K
ICAgID4gVGhhbmsgeW91IGZvciB0aGUgd29yayBwdXQgaW50byB0aGlzIGRvY3VtZW50LiBDb2xs
ZWN0aW5nIGFuZCBhZ2dyZWdhdGluZyBhbGwNCiAgICA+IHRoZSBwcmV2aW91cyB1cGRhdGVzIGlz
IHJlYWxseSB1c2VmdWwuIFRoZSBudW1lcm91cyBleGFtcGxlcyBhcmUgcmVhbGx5IGhlbHBmdWwu
DQogICAgPg0KICAgID4gSSBtdXN0IGFkbWl0IHRob3VnaCB0aGF0ICJ1bnB1Ymxpc2hlZCBJTUFQ
MmJpcyBwcm90b2NvbHMiIG1ha2VzIG1lIHdvbmRlciB3aHkNCiAgICA+IGl0IGlzIG1lbnRpb25l
ZCBpZiBub3QgcHVibGljLi4uDQogICAgSXQgd2FzIHBvcHVsYXIgYXQgdGhlIHRpbWUgYW5kIEkg
YmVsaWV2ZSB0aGVyZSB3YXMgYSBkcmFmdCBhdCBzb21lIA0KICAgIHBvaW50LiBUaGlzIGFjdHVh
bGx5IHByZWRhdGVzIG15IHBhcnRpY2lwYXRpb24gaW4gSUVURi4NCiAgICA+ICAgQWxzbywgIm5l
dHdvcmsgY29ubmVjdGlvbiIgaXMga2luZCBvZiB3ZWlyZA0KICAgID4gZm9yIGFuIEludGVybmV0
IGJhc2VkIG9uIGNvbm5lY3Rpb25sZXNzIElQIGxheWVyLi4uIDstKQ0KICAgID4NCiAgICA+IFBs
ZWFzZSBmaW5kIGJlbG93IHNvbWUgbm9uLWJsb2NraW5nIENPTU1FTlQgcG9pbnRzIChidXQgcmVw
bGllcyB3b3VsZCBiZQ0KICAgID4gYXBwcmVjaWF0ZWQpLCBhbmQgc29tZSBuaXRzLg0KICAgID4N
CiAgICA+IEkgaG9wZSB0aGF0IHRoaXMgaGVscHMgdG8gaW1wcm92ZSB0aGUgZG9jdW1lbnQsDQog
ICAgPg0KICAgID4gUmVnYXJkcywNCiAgICA+DQogICAgPiAtw6lyaWMNCiAgICA+DQogICAgPiA9
PSBDT01NRU5UUyA9PQ0KICAgID4NCiAgICA+IC0tIFNlY3Rpb24gMi4zLjIgLS0NCiAgICA+IFdo
eSB0d28gZmxhZ3MgYXNzb2NpYXRlZCB0byAianVuayIgYnV0IG9ubHkgb25lIGZvciAicGhpc2hp
bmciID8NCiAgICA+IC0tIFNlY3Rpb24gOCAtLQ0KICAgID4gVGhpcyBleGFtcGxlIHVzZXMgTE9H
SU4gbWV0aG9kIHRoYXQgaXMgbm90IHJlY29tbWVuZGVkIG9uIHBsYWluIHRleHQgY29ubmVjdGlv
bg0KICAgID4gKHNlZSA2LjIuMykuIFBlcmhhcHMgd29ydGggc2F5aW5nIHRoYXQgdGhpcyBleGFt
cGxlIHdvcmtzIG92ZXIgaW1wbGljaXQgVExTIG9yDQogICAgPiBiZXR0ZXIgdXNlIGEgQVVUSCBt
ZXRob2Q/DQogICAgWWVzLCBnb29kIGlkZWEuIEFwcGFyZW50bHkgbm9ib2R5IGxvb2tzIGF0IHRo
aXMgZXhjZXB0IGZvciBJRVNHIDstKS4NCiAgICA+ID09IE5JVFMgPT0NCiAgICA+DQogICAgPiAt
LSBTZWN0aW9uIDQuMyAtLQ0KICAgID4gInN5bmNob25pemluZyBsaXRlcmFsIiA/DQogICAgRml4
ZWQsIHRoYW5rIHlvdSA6LSkuDQogICAgPiAtLSBTZWN0aW9uIDYuMy4xMiAtLQ0KICAgID4gVGhl
IGV4YW1wbGUgY29udGFpbnMgIkNvbnRlbnQtVHlwZTogVEVYVC9QTEFJTjsgQ0hBUlNFVD1VUy1B
U0NJSSIgd2hpbGUgaW4gbW9zdA0KICAgID4gZW1haWwgaGVhZGVycyB0aGF0IEkgaGF2ZSBzZWVu
LCB0aGUgdmFsdWUgaXMgaW4gbG93ZXJjYXNlLi4uIE1heSBJIGFzc3VtZSB0aGF0DQogICAgPiBj
YXNlIGlzICpub3QqIHJlbGV2YW50IChiZWNhdXNlIG5vdCBwYXJ0IG9mIHRoZSBlbWFpbCBtZXNz
YWdlIGJ1dCBwYXJ0IG9mIElNQVApDQogICAgPiA/IElmIHNvLCB0aGlzIHZhbHVlIHJlYWRzIGxp
ZSBTSE9VVElORyB0byBtZSA7LSkNCg0KICAgIFRoaXMgaXMgZGVmaW5lZCBpbiBSRkMgMjA0NSwg
d2hpY2ggZGVmaW5lcyBDb250ZW50LVR5cGUgaGVhZGVyIGZpZWxkIA0KICAgIHN5bnRheC4gQmFz
aWNhbGx5LCBhbGwgdGhyZWU6IHRoZSBtZWRpYSB0eXBlICgiVEVYVC9QTEFJTiIpLCBwYXJhbWV0
ZXIgDQogICAgbmFtZSAoIkNIQVJTRVQiKSBhbmQgY2hhcnNldCBwYXJhbWV0ZXIgdmFsdWUgKCJV
Uy1BU0NJSSIpIGFyZSBhbGwgDQogICAgZGVmaW5lZCB0byBiZSBjYXNlIGluc2Vuc2l0aXZlLg0K
DQogICAgU28gbm8sIHRoaXMgaGFzIG5vdGhpbmcgdG8gZG8gd2l0aCBJTUFQLg0KDQogICAgQXMg
YW4gZWRpdG9yLCBJIGRvIGxpa2UgdG8gcGljayBzb21lIGV4YW1wbGVzIGRlbW9uc3RyYXRpbmcg
DQogICAgY2FzZS1pbnNlbnNpdGl2aXR5IGFuZCBvdGhlciB1bnVzdWFsIGNvbmRpdGlvbnMuDQoN
CiAgICA+IC0tIFNlY3Rpb24gNi40LjQgLS0NCiAgICA+IFRoZSBleGFtcGxlIGRhdGVzIGFyZSBp
biAxOTk0Li4uIHBlcmhhcHMgd29ydGggdXBkYXRpbmcgPyAgOy0pIE90aGVyIGV4YW1wbGVzDQog
ICAgPiBhcmUgaW4gMjAwNg0KDQogICAgVGhpcyBpcyBhIHJldmlzaW9uIG9mIFJGQyAzNTAxLCB3
aGljaCBpcyBhIHJldmlzaW9uIG9mIFJGQyAyMDYwLCBldGMuDQoNCiAgICBXZSBjb3VsZCB1cGRh
dGUgZXhhbXBsZXMsIGJ1dCB0aGV5IGFyZSBzdGlsbCB2YWxpZC4gQ2hhbmdlcyB3b3VsZCBtb3N0
IA0KICAgIGxpa2VseSBhZmZlY3QgZGF5LW9mLXRoZS13ZWVrLCB3aGljaCBtaWdodCBpbiB0dXJu
IGNoYW5nZSBsaXRlcmFsIA0KICAgIHNpemVzLi4uIFNvIGNoYW5nZXMgY2FuIGludHJvZHVjZSBu
ZXcgYnVncy4NCg0KICAgIEJlc3QgUmVnYXJkcywNCg0KICAgIEFsZXhleQ0KDQoNCg==


From nobody Mon Feb  1 14:01:18 2021
Return-Path: <brong@fastmailteam.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 AAAF83A1513; Mon,  1 Feb 2021 14:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=sTaPAAkU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HmKdB1OY
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 3q7T_0lITASe; Mon,  1 Feb 2021 14:01:12 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 591443A1512; Mon,  1 Feb 2021 14:01:12 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id A785D5C011B; Mon,  1 Feb 2021 17:01:10 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Mon, 01 Feb 2021 17:01:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=+wj7 gTPuJPIJEaJwbtJo1eyRXwgE6v0vNncbBJmcPlc=; b=sTaPAAkUcxa6p66tF5t6 fEvnjroMZ3zBnTJGMXPdKG+vvqGdHvQoU7tqUA56FQKLV0876QX1JOuvcJYm2EjG vi0HIxgBDxSR4S4+l1GpcYPqT6SBajcaHEt+JE4nve4r0BvF8nyK4edC+CE6hkDH lCgKcaSEmblOtLRXheNlFETPYmlbT68rQ/WyFEOPN89vQmhiuFM6VRmOf+w6dHqA Gtn9Mf2RFnsFpYWt6GdJ6LfQd0EKHuAevercr2hEc66ylliGSxUg7/LNgHJ53Maz dqMYdCaGhkL03sNHwHtW+gdp0OM5GoimvkTxh3DMpnKyhn3U74FOyy/UpWRHq1Xa SA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=+wj7gT PuJPIJEaJwbtJo1eyRXwgE6v0vNncbBJmcPlc=; b=HmKdB1OYgQEY6QBp+hoQge ZtoJgBv3ipGgEZdI92QOXcyPvfb0Gg1ySd7k1F6FLO48AHcHEHHpDrAYe7Q3x0YM uSF2Q/fhBEGuF5FSyt9/QYAS/0OQH8Cygw6X/Vi7d3ELnJdFxQ4kgs6nRYD4J573 7969vND28rI8cDKlWMKIZ8hzEUHle/01Y5UgzkIkpDgsYZK96xmXp1w3HCSS94HY hI5DmkZDmGWSSMF9kI6+hBUME4BYMOov6d8U5Kt5t6fYeze5Y5wv5nnG6iFxzw42 YnfNsrK5xmNiqsAUg8+ObpV0gMo+Dd/3c6MDAB8uUeSl1GPgsbiMmvqDI+vjH+Gg ==
X-ME-Sender: <xms:JnoYYEwa1Uqa1UkF_5mQC99nKJC7rhGZvWlg2fDzWmwTaZLLeliLBQ> <xme:JnoYYISWYsA4HRb_qAg1Z5KWDvJose_5mcq0IlzlimQgYHJlh3XoCxXxYO9GeReh2 v3TMVYwj4I>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeekgdduhedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnheptedvjedvffduteelfeettefggeekffffgfekuefgieej iefhjeetffevtddvtddtnecuffhomhgrihhnpehirghnrgdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhm rghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:JnoYYGUGRa4xLKaJ0coixuPR2UxijdW0aY65O1-X1ZsJ33R6YHWTjQ> <xmx:JnoYYCjjIffyPwgOvA6SOIJdz09ERCYeUvsRf6ULA5svSbRwJ208vg> <xmx:JnoYYGBspwCuovmlO6tGx-O63Cvry2Wvc8MqJs7m34zdRtJqhrfyMw> <xmx:JnoYYJOljxjU1srL52V80Q_9Y_gnyx8ltMtR48gIx3PoGL9NeGJy1A>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1611336005C; Mon,  1 Feb 2021 17:01:10 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048
Mime-Version: 1.0
Message-Id: <1a9090d4-6c3f-4a71-8cf7-42b3d4b10244@dogfood.fastmail.com>
In-Reply-To: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
References: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
Date: Tue, 02 Feb 2021 09:00:49 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "'Eric Vyncke (evyncke)'" <evyncke@cisco.com>, "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org
Content-Type: multipart/alternative; boundary=0f8632b069d54831bcfecd8ee1be9773
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/7JmVZsU1-NEbB56kL1WgKflPtAs>
Subject: Re: [Extra]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-extra-imap4rev2-26=3A_=28with_COMMENT=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 22:01:17 -0000

--0f8632b069d54831bcfecd8ee1be9773
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Tue, Feb 2, 2021, at 02:23, =C3=89ric Vyncke via Datatracker wrote:
> -- Section 2.3.2 --
> Why two flags associated to "junk" but only one for "phishing" ?

I can answer this one :)  $Junk and $NotJunk are designed to be set by t=
he client in order to provide feedback to the server in order for it to =
update its engine (i.e. by feeding into a Bayes database). $Phishing is =
designed for the server to add an "I delivered this to your mailbox but =
since then I've learned that it's bad" - it's never set by clients.

This information is a direct copy of what's in the IANA registry already=
:

https://www.iana.org/assignments/imap-jmap-keywords/imap-jmap-keywords.x=
html

Cheers,

Bron.


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--0f8632b069d54831bcfecd8ee1be9773
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><div=
>On Tue, Feb 2, 2021, at 02:23, =C3=89ric Vyncke via Datatracker wrote:<=
br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"fo=
nt-family:Arial;">-- Section 2.3.2 --<br></div><div style=3D"font-family=
:Arial;">Why two flags associated to "junk" but only one for "phishing" =
?<br></div></blockquote><div style=3D"font-family:Arial;"><br></div><div=
 style=3D"font-family:Arial;">I can answer this one :)&nbsp; $Junk and $=
NotJunk are designed to be set by the client in order to provide feedbac=
k to the server in order for it to update its engine (i.e. by feeding in=
to a Bayes database). $Phishing is designed for the server to add an "I =
delivered this to your mailbox but since then I've learned that it's bad=
" - it's never set by clients.<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">This information is a dire=
ct copy of what's in the IANA registry already:<br></div><div style=3D"f=
ont-family:Arial;"><br></div><div style=3D"font-family:Arial;"><a href=3D=
"https://www.iana.org/assignments/imap-jmap-keywords/imap-jmap-keywords.=
xhtml">https://www.iana.org/assignments/imap-jmap-keywords/imap-jmap-key=
words.xhtml</a></div><div style=3D"font-family:Arial;"><br></div><div st=
yle=3D"font-family:Arial;">Cheers,<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">Bron.<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"><=
br></div><div id=3D"sig56629417"><div class=3D"signature">--<br></div><d=
iv class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></=
div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br></div><div=
 class=3D"signature"><br></div></div><div style=3D"font-family:Arial;"><=
br></div></body></html>
--0f8632b069d54831bcfecd8ee1be9773--


From nobody Mon Feb  1 22:15:42 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 698093A09EA; Mon,  1 Feb 2021 22:15:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <161224653474.4757.13952667336387949190@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 22:15:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/huWEDZrMZD2fZayA5SWtvRfEZu0>
Subject: [Extra] Erik Kline's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 06:15:36 -0000

Erik Kline has entered the following ballot position for
draft-ietf-extra-imap4rev2-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

[[ nits ]]

[ section 2.3.2 ]

* "This so that" -> "This is so that", perhaps




From nobody Tue Feb  2 07:15:32 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F26453A1205; Tue,  2 Feb 2021 07:15:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
Date: Tue, 02 Feb 2021 07:15:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/gK7shk1wc7qhPU5X0gaM-X6Znvg>
Subject: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 15:15:27 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-extra-imap4rev2-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

** Section 1.3.  What are the â€œunpublished IMAP2bis protocolsâ€�?  Even if there
were unpublished, is there any pointer/reference that can be provided, say like
https://tools.ietf.org/html/draft-ietf-imap-imap2bis-02?

** Section 2.3.1.1.  Step #4.  Should â€œIn particular, the internal date,
[RFC-5322] size, envelope, body structure, and message texts (all BODY[...]
fetch data items) must never change)â€�, use the normative â€œMUST never changeâ€�?

** Section 2.3.3.  The text for $Forwarded notes that â€œOnce set, the flag
SHOULD NOT be cleared.â€�  Should the same guidance apply to $MDNSent?

** Section 5.1.2.  Editorial.  s/manager to grant to their secretary access
rights/manager to grant to their administrative support staff access rights/

** Section 6.3.1.  Per â€œHowever, servers cannot send those unsolicited
responses (with the exception of response codes (see Section 7.1) included in
tagged or untagged OK/NO/BAD responses, which can always be sent) until they
know that the clients support such extensions and thus won't choke on the
extension response dataâ€�, what is the more precise definition of â€œchokeâ€� here. 
Is it that the client doesnâ€™t understand the extension or that it wonâ€™t be able
to process it?

** Section 6.3.9.3.  Step 3.  Per â€œAttributes returned in the same LIST
response must be treated additivelyâ€�, should this be a normative â€œMUSTâ€�?

** Section 6.3.12 and Section 8.  The examples here have a few â€œnon exampleâ€�
domains (e.g., @Blurdybloop.com, @owatagu.siam.edu, @cac.washington.edu)

** Section 6.4.4.4.  Editorial.  In this section the inline annotation of the
C: and S: examples are with a â€œ//â€�.  In Section 6.3.10, these annotations are
made via â€œ< â€¦ >â€�.  Iâ€™d recommend consistency.

** Section 7.1.  Other than a clear text connection, under what circumstances
would PRIVACYREQUIRED be returned?  I ask because the statement â€œThe operation
is not permitted due to a lack of privacyâ€� seems rather generic and might
benefit from tighter scoping of what â€œlack of privacyâ€� means.

** Section 7.1.4.  Per â€œFor this reason PREAUTH response SHOULD only be
returned by servers on connections that are protected by TLS (such as on
implicit TLS port [RFC8314]) or protected through other means such as IPSecâ€�,
what is the corner case in mind that motives a SHOULD (instead of a MUST)?

** Section 11.  There are both confidentiality and integrity issues with
sending of IMAP in the clear.

OLD
IMAP4rev2 protocol transactions, including electronic mail data, are
sent in the clear over the network unless protection from snooping is
negotiated.

NEW
IMAP4rev2 protocol transactions, including electronic mail data, are sent in
the clear over the network exposing them to possible eavesdropping and
manipulation unless protections are negotiated.

** Section 11.1.  Per â€œOther TLS cipher suites recommended in RFC 7525 are
RECOMMENDED â€¦â€�, seems as if RFC7525 needs to be an explicit reference.

** Section 11.2.  Per â€œFor this reason, IMAP4rev2 clients SHOULD try both ports
993 and 143 (and both IPv4 and IPv6) concurrently by default, unless overriden
[sic] by either user configuration or DNS SRV records [RFC6186]â€�, is there any
further guidance needed here to guide if say both 993 and 143 respond; or you
get responses across address families?

** In the spirit of inclusive language, consider something like the following:

-- Section 6.2.1.  s/to protect against man-in-the-middle attackers which
alter/to protect against an on-path attacker which could alter/

-- Section 11.1
OLD
â€¦ as presented in the server Certificate message, in order to prevent
man-in-the-middle attacks.

NEW
â€¦ as presented in the server Certificate message, in order to prevent on-path
attackers attempting to masquerade as the server.

-- Section 11.3.  s/(or a man-in-the-middle attacker)/ (or an on-path attacker)/

** Typos:
-- Section 11.2. s/overriden/overridden/

** From idnits:
  -- The draft header indicates that this document obsoletes RFC3501, but the
     abstract doesn't seem to mention this, which it should.

  -- There are a number of reference warnings which should be confirmed as not
  being problematic (not mentioned in the shepherd write-up)




From nobody Tue Feb  2 09:08:21 2021
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 0ECA43A0C5D; Tue,  2 Feb 2021 09:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 RTw-IpVo42mV; Tue,  2 Feb 2021 09:08:17 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 27E3F3A0C5B; Tue,  2 Feb 2021 09:08:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612285696; d=isode.com; s=june2016; i=@isode.com; bh=9xFoLONtL7qMhmncA8DQZxwJPf8pVTMGoi3baeSPWrU=; 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=kxzDwruvD4Km3qWyuw1DOzRd6WWWU7W7ha0iZYE5RNNqsi04KB6W65H2OmK+J2CGpdnlhQ mL7YXNy3GPxvGvnzTjPG8dv23YEHypktT0QfXXscPh8zGjTN7sr4JrEKLjDMkbaf0jOX1q gsKRku7lJV2TwFDGprZcqkMTW22yIHs=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YBmG=wAuQVkt@waldorf.isode.com>; Tue, 2 Feb 2021 17:08:16 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
Message-ID: <d11c48d6-bbe4-156f-30a8-d5206557d82d@isode.com>
Date: Tue, 2 Feb 2021 17:08:15 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/QQ469bP0D1Oz4o6XywYYS8LWbUA>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 17:08:19 -0000

Hi Roman,

Thank you for your comments. Replying to most of your comments (I will=20
reply to the rest separately):

On 02/02/2021 15:15, Roman Danyliw via Datatracker wrote:
> ** Section 1.3.  What are the =E2=80=9Cunpublished IMAP2bis protocols=E2=
=80=9D?  Even if there
> were unpublished, is there any pointer/reference that can be provided, say=
 like
> https://tools.ietf.org/html/draft-ietf-imap-imap2bis-02?
Yes, this looks like a reasonable informative reference.
> ** Section 2.3.1.1.  Step #4.  Should =E2=80=9CIn particular, the internal=
 date,
> [RFC-5322] size, envelope, body structure, and message texts (all BODY[...=
]
> fetch data items) must never change)=E2=80=9D, use the normative =E2=80=9C=
MUST never change=E2=80=9D?
Sure.
> ** Section 2.3.3.  The text for $Forwarded notes that =E2=80=9COnce set, t=
he flag
> SHOULD NOT be cleared.=E2=80=9D  Should the same guidance apply to $MDNSen=
t?
$MDNSet description points to RFC 3503, which states "MUST NOT be=20
cleared". I would rather not copy the text into this draft, if that is=20
Ok with you?
> ** Section 5.1.2.  Editorial.  s/manager to grant to their secretary acces=
s
> rights/manager to grant to their administrative support staff access right=
s/
Ok.
> ** Section 6.3.1.  Per =E2=80=9CHowever, servers cannot send those unsolic=
ited
> responses (with the exception of response codes (see Section 7.1) included=
 in
> tagged or untagged OK/NO/BAD responses, which can always be sent) until th=
ey
> know that the clients support such extensions and thus won't choke on the
> extension response data=E2=80=9D, what is the more precise definition of =
=E2=80=9Cchoke=E2=80=9D here.
> Is it that the client doesn=E2=80=99t understand the extension or that it =
won=E2=80=99t be able
> to process it?
The former. I think it was intended as a shortcut for "crash and=20
misbehave in other surprising ways".
> ** Section 6.3.9.3.  Step 3.  Per =E2=80=9CAttributes returned in the same=
 LIST
> response must be treated additively=E2=80=9D, should this be a normative =
=E2=80=9CMUST=E2=80=9D?
I think MUST is going to be a bit silly here, as the whole set is=20
specified in a single LIST response. I will change this to "are treated=20
additively".
> ** Section 6.3.12 and Section 8.  The examples here have a few =E2=80=9Cno=
n example=E2=80=9D
> domains (e.g., @Blurdybloop.com, @owatagu.siam.edu, @cac.washington.edu)
Yes, this comes from RFC 3501. I can change these if this is a big deal=20
to people, but this will cause literal size changes in various places,=20
so this is more work than just search & replace everywhere in the document.
> ** Section 6.4.4.4.  Editorial.  In this section the inline annotation of =
the
> C: and S: examples are with a =E2=80=9C//=E2=80=9D.  In Section 6.3.10, th=
ese annotations are
> made via =E2=80=9C< =E2=80=A6 >=E2=80=9D.  I=E2=80=99d recommend consisten=
cy.

Ok. Murray has pointed out the same thing. I will discuss with RFC=20
Editor about the best way of representing comments.

 =C2=A0[snip]

> ** Section 7.1.4.  Per =E2=80=9CFor this reason PREAUTH response SHOULD on=
ly be
> returned by servers on connections that are protected by TLS (such as on
> implicit TLS port [RFC8314]) or protected through other means such as IPSe=
c=E2=80=9D,
> what is the corner case in mind that motives a SHOULD (instead of a MUST)?
I was thinking about loopback interface or something like Unix domain=20
socket (the latter is technically out of scope for this document).
> ** Section 11.  There are both confidentiality and integrity issues with
> sending of IMAP in the clear.
>
> OLD
> IMAP4rev2 protocol transactions, including electronic mail data, are
> sent in the clear over the network unless protection from snooping is
> negotiated.
>
> NEW
> IMAP4rev2 protocol transactions, including electronic mail data, are sent =
in
> the clear over the network exposing them to possible eavesdropping and
> manipulation unless protections are negotiated.
I used your text, thank you.
> ** Section 11.1.  Per =E2=80=9COther TLS cipher suites recommended in RFC =
7525 are
> RECOMMENDED =E2=80=A6=E2=80=9D, seems as if RFC7525 needs to be an explici=
t reference.

Good point. Added.

 =C2=A0[snip]

> ** In the spirit of inclusive language, consider something like the follow=
ing:
>
> -- Section 6.2.1.  s/to protect against man-in-the-middle attackers which
> alter/to protect against an on-path attacker which could alter/
>
> -- Section 11.1
> OLD
> =E2=80=A6 as presented in the server Certificate message, in order to prev=
ent
> man-in-the-middle attacks.
>
> NEW
> =E2=80=A6 as presented in the server Certificate message, in order to prev=
ent on-path
> attackers attempting to masquerade as the server.
Changed, thank you.
> -- Section 11.3.  s/(or a man-in-the-middle attacker)/ (or an on-path atta=
cker)/
Changed.
> ** Typos:
> -- Section 11.2. s/overriden/overridden/
Fixed, thanks.
> ** From idnits:
>    -- The draft header indicates that this document obsoletes RFC3501, but=
 the
>       abstract doesn't seem to mention this, which it should.
>
>    -- There are a number of reference warnings which should be confirmed a=
s not
>    being problematic (not mentioned in the shepherd write-up)

Will do. I think all of them were covered by the IETF LC announcement,=20
but I will double check.

Best Regards,

Alexey



From nobody Tue Feb  2 09:26:49 2021
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 F1B4C3A0C8F; Tue,  2 Feb 2021 09:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ix1PyCPaGKHH; Tue,  2 Feb 2021 09:26:45 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 460753A0C9C; Tue,  2 Feb 2021 09:26:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612286804; d=isode.com; s=june2016; i=@isode.com; bh=HwQlhMqVfbu5fswdDWZkri0x00aiFekFKnhzgrb6gaY=; 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=ZGIyMkNdsn+0CLwgtO2iLzz6kd4eDJensuu9mjiig4g4x+/TDMnTnqquhNGBue7UH2tOo3 Czk2TGjWYEaPrme4nJJe+e0YJ/rfQ3qZEWWZWqMGjcgLPg7hspfn8N+czrPmVF/HgFNJOq xa6LZGWAJoWMigPQ6cbFaD1xzh7AAvc=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YBmLUwAuQZlC@waldorf.isode.com>; Tue, 2 Feb 2021 17:26:43 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
Message-ID: <5e926862-06e5-dfcf-0d73-83c44607f486@isode.com>
Date: Tue, 2 Feb 2021 17:26:43 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/_niV5zDGqWIA3ef9bASL3Fl1E3g>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 17:26:47 -0000

Hi Roman,

Replying to one more comment:

On 02/02/2021 15:15, Roman Danyliw via Datatracker wrote:
> ** Section 7.1.  Other than a clear text connection, under what circumstan=
ces
> would PRIVACYREQUIRED be returned?
That is it.
> I ask because the statement =E2=80=9CThe operation
> is not permitted due to a lack of privacy=E2=80=9D seems rather generic an=
d might
> benefit from tighter scoping of what =E2=80=9Clack of privacy=E2=80=9D mea=
ns.

I changed "privacy" to "data confidentiality". Do you think this is=20
clear enough now?

Best Regards,

Alexey



From nobody Tue Feb  2 09:54:00 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 701933A0CD9; Tue,  2 Feb 2021 09:53:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <161228843386.9750.10522178607825201429@ietfa.amsl.com>
Date: Tue, 02 Feb 2021 09:53:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/RSgnkZW_dmDsWCN6QUsh45lXkXk>
Subject: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 17:53:55 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-extra-imap4rev2-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for taking this on.

(1) Section 6.3.9 says:

"The LIST command SHOULD return its data quickly, without undue delay.
   For example, it SHOULD NOT go to excess trouble to calculate the
   \Marked or \Unmarked status or perform other processing"

The second sentence seems like it does not warrant normative language given
that it is giving an example (and what does it mean for a command to measure
whether trouble is excessive anyway?).

(2) There are some recurring example names -- owatagusiam, blurdybloop, etc. --
that could probably be replaced with names that are a little more
accessible/obvious to new readers. Also, there are a lot of examples with user
names from the same cultural/linguistic context -- smith, fred, eric, etc.
Neutralizing or diversifying those names would improve the document.




From nobody Tue Feb  2 09:55:11 2021
Return-Path: <alissa@cooperw.in>
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 C570B3A0CED; Tue,  2 Feb 2021 09:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level: 
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=0z+cM4uy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wfmPprsz
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 x9HWOK4J7c0d; Tue,  2 Feb 2021 09:55:02 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C7E63A0CE8; Tue,  2 Feb 2021 09:55:02 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0E9525C0310; Tue,  2 Feb 2021 12:55:01 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 02 Feb 2021 12:55:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=M Lg2VvvpPH1TIkCVz3401N2wHeDwyoVvbDYXZ7dS2fc=; b=0z+cM4uy8M9d+UdZv BXX49F5dxldY0nSDC1F841O+TXUxyZeNxq6twIDI9PzyRLS31Qfx616xj7uCqHh8 S9s6Dyjrec/yaQ4xCxoNaNLTunjWjQAwEBJ+HZx0zcFHOUqZDVaVb3Re7W1CBZnc WST/Lu7ZmahjE2pCO7dETB58Ffnj8EcezjWdObeY6ma1tV+ytD/sbBDVHdM6kc96 rc08/TEiBw5zGVIzuAPaQ0s4LobIqzGsmybAaOxfJVhnIJf8ZiiiZT3zu1qijpRL uPbmlcFo+bbFCD3sdqLbvhExodZd/l/50jvjkzznDT/QS4Vr4x9pgO1koRtVn/nJ LgKxg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=MLg2VvvpPH1TIkCVz3401N2wHeDwyoVvbDYXZ7dS2 fc=; b=wfmPprszSozhSh13e702jMt10CQh0M2D4f2D2yg66F4CobelfpiRPZQ5c gUf13o8SN1VSBH7Tkbip67mNyC8nh/DncqtLD2nB5POq2BZxTrqOv48cL/5eQIv4 5xJI7V6GyXzyGxa4D0X3PTWWkrC70gBI4kLuTZWSIIgeKhssjsN58tj3VSb+AEyR MOeEul+YAb0kZ3+AwDDar8qjEDgDfCpg/NVUJhSkL5n7nR6AZuheMnzBVCMDJ7jp QneOGlmtHnuh14CwZQuLlXaDyJSOImTqZsd0HkVkJwTTtfsnGy5ivtXSkOjwD+ho UT8rqb5UXd7j4dU0/J+INAWwxJdDg==
X-ME-Sender: <xms:9JEZYMxKHuWRmyZh8rsB-zxEqpUCME_k-g0Uo0iAB5hs0o7yHEMieg> <xme:9JEZYAQ9H-leOXT5PH3kSLO49VR_LVYbdZTtv94giFU2EXZ9u24GiP51K1gjKVDQG WDKu0r0ZxfLelQ9tg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgedtgddutdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucggtffrrg htthgvrhhnpeefudfhgfetgfetvddvffeiuddtkeffgedvjeejtdeiheefgfelfeeutdel vdfggfenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedrudduje drieehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep rghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:9JEZYOXqLgKpZ4Fens9fA9gN9el3u8VtAjrTzJ5zYCow1536ZtOfwg> <xmx:9JEZYKgtA3vsvnmUZEQAtTOeIwLHMvTctCnqd_dvzKfrLYpyDfdvXQ> <xmx:9JEZYOAkgz42pKe0DHwWsxcjSy9kALqBRbE1XMQaGWed3JyQALGkLA> <xmx:9ZEZYBPu-bP44lrzup7QEltH5X2Lykb8HKg-VVk16GcGkcbPn82Yfw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.65]) by mail.messagingengine.com (Postfix) with ESMTPA id 74EB3240057; Tue,  2 Feb 2021 12:55:00 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <161066213071.7885.5993845743529029815@ietfa.amsl.com>
Date: Tue, 2 Feb 2021 12:54:59 -0500
Cc: gen-art@ietf.org, extra@ietf.org, last-call@ietf.org, draft-ietf-extra-imap4rev2.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C33F2787-A345-49AF-A2DD-CF25A8411A08@cooperw.in>
References: <161066213071.7885.5993845743529029815@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/WZbUWUoJk1yMnJ3aZFd8pki0TQM>
Subject: Re: [Extra] [Gen-art] Genart last call review of draft-ietf-extra-imap4rev2-24
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 17:55:10 -0000

Robert, thanks for your review. I entered a No Objection ballot.

Alissa


> On Jan 14, 2021, at 5:08 PM, Robert Sparks via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Robert Sparks
> Review result: Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-extra-imap4rev2-24
> Reviewer: Robert Sparks
> Review Date: 2021-01-14
> IETF LC End Date: 2021-01-20
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready for publication as a Proposed Standard RFC
>=20
> I approached reviewing this document first by diffing it with RFC3501, =
then
> doing a linear read-through. Errata seem appropriately handled. This =
looks like
> it was a huge effort - it is very well done. I sent the few nits I =
could find
> directly to the editors.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Feb  2 10:13:08 2021
Return-Path: <barryleiba@gmail.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 C64FA3A0D27; Tue,  2 Feb 2021 10:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 B1XyZ2TJIEMC; Tue,  2 Feb 2021 10:13:05 -0800 (PST)
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F1143A0CFC; Tue,  2 Feb 2021 10:13:05 -0800 (PST)
Received: by mail-lf1-f41.google.com with SMTP id v24so29324556lfr.7; Tue, 02 Feb 2021 10:13:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JT0OjUtMTkqu/Jmu0+3/kDwSphmTVTe3OqJHjr1qAh8=; b=P/QpGhyc+mNy2pP9+1t6GK36iX5OzXbCJA+Apbz7swaeuftjoTXUWs7egt4u2j+utC 9YjNRxJ44p30yWfQFFdmeZI+Bm/uTifx4WdwRB5ZIY9NajYl5n4QkU4xLLB+SkUPNsgY 8J6JrHBljjb7hbj+oj/qw1Qp3k2rYNdWxz9LGgBNffhJLK3S/1eeY1YfPxmJNfepoeoh 268rsjv1LCzToiHlBxaz90Ky2kaIfU7d9hJDeTmZGD1X7I8CO4uoqlt+g6qhfOM8IAr0 RP3nwrmrLaWrM7DJYVColHV09G1yRFwxSN2QwMTb3+lu1zP7/7MBgacF3dfIfAO2Ubu6 +0Fg==
X-Gm-Message-State: AOAM5335Zn3x81hFKf6+KVvBEVSUqJC7jyBzvbAzg5YUluEAC7Mh2i+7 PhgYcLc0xQ9KH/0Wz3IlGq6iKYB3NNE3Dj1P/UY=
X-Google-Smtp-Source: ABdhPJwdwWqSdsgtTlHhfYgsGRq9bxQ4r0xgRcK8QAcUUisTa46WG7L/co0O0it/DmWhmm497BU9k3EiYWq4pPV+4wg=
X-Received: by 2002:a05:6512:31c1:: with SMTP id j1mr12128012lfe.313.1612289583170;  Tue, 02 Feb 2021 10:13:03 -0800 (PST)
MIME-Version: 1.0
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com>
In-Reply-To: <161228843386.9750.10522178607825201429@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 2 Feb 2021 13:12:51 -0500
Message-ID: <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org,  extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/D4zI55X6nQRRQQBsSGHDOJcwb-Q>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:13:07 -0000

> (1) Section 6.3.9 says:
>
> "The LIST command SHOULD return its data quickly, without undue delay.
>    For example, it SHOULD NOT go to excess trouble to calculate the
>    \Marked or \Unmarked status or perform other processing"
>
> The second sentence seems like it does not warrant normative language given
> that it is giving an example

Indeed; this slipped through from the original.  I agree that we don't
need the same BCP 14 statement twice.

> (2) There are some recurring example names -- owatagusiam, blurdybloop, etc. --
> that could probably be replaced with names that are a little more
> accessible/obvious to new readers. Also, there are a lot of examples with user
> names from the same cultural/linguistic context -- smith, fred, eric, etc.
> Neutralizing or diversifying those names would improve the document.

This harks back to older times and to the late Mark Crispin, who liked
those sorts of things.

I agree with you.

That said, there are two things:

1. As Alexey has pointed out with other comments, changing these often
involves carefully checking literal lengths, RFC822-SIZE values, and
other such, and has a high potential to introduce errors.

2. I have some thought toward keeping Mark's voice in here, and that
mostly shows up in the examples.  Part of me would rather not scrub it
out.

Alexey, thoughts?

Barry


From nobody Tue Feb  2 10:26:53 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFD23A0D50; Tue,  2 Feb 2021 10:26:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161229040845.9757.18088469232924779637@ietfa.amsl.com>
Date: Tue, 02 Feb 2021 10:26:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/arZUt23UczesrUDNnXQG1MRw1UE>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-27.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:26:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Internet Message Access Protocol (IMAP) - Version 4rev2
        Authors         : Alexey Melnikov
                          Barry Leiba
	Filename        : draft-ietf-extra-imap4rev2-27.txt
	Pages           : 168
	Date            : 2021-02-02

Abstract:
   The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2)
   allows a client to access and manipulate electronic mail messages on
   a server.  IMAP4rev2 permits manipulation of mailboxes (remote
   message folders) in a way that is functionally equivalent to local
   folders.  IMAP4rev2 also provides the capability for an offline
   client to resynchronize with the server.

   IMAP4rev2 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing,
   searching, and selective fetching of message attributes, texts, and
   portions thereof.  Messages in IMAP4rev2 are accessed by the use of
   numbers.  These numbers are either message sequence numbers or unique
   identifiers.

   IMAP4rev2 does not specify a means of posting mail; this function is
   handled by a mail submission protocol such as the one specified in
   RFC 6409.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-27
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-27

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-27


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue Feb  2 10:31:19 2021
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 E87FA3A0DF9 for <extra@ietfa.amsl.com>; Tue,  2 Feb 2021 10:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 EMPer9iNsMAr for <extra@ietfa.amsl.com>; Tue,  2 Feb 2021 10:31:09 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id D292B3A0D7C for <extra@ietf.org>; Tue,  2 Feb 2021 10:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612290668; d=isode.com; s=june2016; i=@isode.com; bh=xxD2jPmfAWTC3NA0tER13+ymZYBlzJv84jXAwKKovwA=; 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=AJowhMhTwDYSAbSHR1/YFLp7uHNRFYw/ARlLVc57YaNctStFutB514eFjfA3Y82h4dPYC1 BsrQzslsTqYinygkrEqMVUgFZa8RJDxIbdqr5ULPiM3xN7a34aOaPqpEAgClLuWEx9puMe whkvr72cJyiKidie7imthNEoDWDPyl8=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YBmaawAuQZWz@waldorf.isode.com>; Tue, 2 Feb 2021 18:31:07 +0000
To: extra@ietf.org
References: <161229040845.9757.18088469232924779637@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <212c829c-d154-b006-2b77-55c44992ce86@isode.com>
Date: Tue, 2 Feb 2021 18:31:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161229040845.9757.18088469232924779637@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/q796NlIqBM6Rd6NNA2V711-EIuc>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-27.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:31:17 -0000

On 02/02/2021 18:26, internet-drafts@ietf.org wrote:

> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-27
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-27
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-27

This version addresses most of comments from IESG reviews by Roman, 
Eric, Martin, Alissa and Erik.


From nobody Tue Feb  2 10:33:19 2021
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 6991B3A0D76; Tue,  2 Feb 2021 10:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 fw0EayVRAWOY; Tue,  2 Feb 2021 10:33:12 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 1C13E3A0D82; Tue,  2 Feb 2021 10:33:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612290790; d=isode.com; s=june2016; i=@isode.com; bh=q1siqX+xaO7O3ST5DwfBpvoWPP6NnmvR7rEDgHobTLI=; 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=fFpK4CTLl+BhMBlXj/GFjBzPXggddIpWW/Z2eROsMrlawh+qlpBzXNd7hcecqr1vWX8zTD 6K1LqlkS3gtW8OD0K6YDlEF8pD+3W2Nveu1W5utkkTb03GrQDT2J86ULuBhVGpjwUppSl+ FAdxoFFgr8Ml1YnN//Kat41/WxgDOaE=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YBma5gAuQRm1@waldorf.isode.com>; Tue, 2 Feb 2021 18:33:10 +0000
To: Barry Leiba <barryleiba@computer.org>, Alissa Cooper <alissa@cooperw.in>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <7735f3bc-48d8-dddb-2f97-da889b5f1a9a@isode.com>
Date: Tue, 2 Feb 2021 18:33:09 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/_JH2PMlkXykfl2J6piulEr2lw5A>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:33:14 -0000

On 02/02/2021 18:12, Barry Leiba wrote:

>> (1) Section 6.3.9 says:
>>
>> "The LIST command SHOULD return its data quickly, without undue delay.
>>     For example, it SHOULD NOT go to excess trouble to calculate the
>>     \Marked or \Unmarked status or perform other processing"
>>
>> The second sentence seems like it does not warrant normative language given
>> that it is giving an example
> Indeed; this slipped through from the original.  I agree that we don't
> need the same BCP 14 statement twice.
Right. I will fix.
>> (2) There are some recurring example names -- owatagusiam, blurdybloop, etc. --
>> that could probably be replaced with names that are a little more
>> accessible/obvious to new readers. Also, there are a lot of examples with user
>> names from the same cultural/linguistic context -- smith, fred, eric, etc.
>> Neutralizing or diversifying those names would improve the document.
> This harks back to older times and to the late Mark Crispin, who liked
> those sorts of things.
>
> I agree with you.
>
> That said, there are two things:
>
> 1. As Alexey has pointed out with other comments, changing these often
> involves carefully checking literal lengths, RFC822-SIZE values, and
> other such, and has a high potential to introduce errors.
>
> 2. I have some thought toward keeping Mark's voice in here, and that
> mostly shows up in the examples.  Part of me would rather not scrub it
> out.

Yes, I thought of #2 as well.

Happy to go with IESG consensus on this.

> Alexey, thoughts?
>
> Barry


From nobody Tue Feb  2 10:51:12 2021
Return-Path: <rdd@cert.org>
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 0537D3A1045; Tue,  2 Feb 2021 10:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 eZlbbTZmYLPO; Tue,  2 Feb 2021 10:51:09 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 0097A3A1044; Tue,  2 Feb 2021 10:51:08 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 112Ip5j6005542; Tue, 2 Feb 2021 13:51:05 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 112Ip5j6005542
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1612291865; bh=xv95EwIXT99oCVzogUi8An3dMtkx1eNNIAK5J/BaIc8=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=gL8tAkGlDb5FpXFfrT5bt53rJHXv9BFwyYslNDnGHILYimIlFWvyzzZRpCCNlqWPe 2DuMXibF7FjSV48K1DyQAoDiGZxbywXcfHdiWDuyDBMizPJQiETMBHkLW79x82p8ap rJ0shKVzoHW/C/JRsPSiZgZQwV850sWILcyMnyxI=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 112IouuH027922; Tue, 2 Feb 2021 13:50:56 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 2 Feb 2021 13:50:56 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Tue, 2 Feb 2021 13:50:56 -0500
From: Roman Danyliw <rdd@cert.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>, The IESG <iesg@ietf.org>
CC: "extra@ietf.org" <extra@ietf.org>, "brong@fastmailteam.com" <brong@fastmailteam.com>, "draft-ietf-extra-imap4rev2@ietf.org" <draft-ietf-extra-imap4rev2@ietf.org>, "extra-chairs@ietf.org" <extra-chairs@ietf.org>
Thread-Topic: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
Thread-Index: AQHW+YiWO7cNWLrnI02qa9YhuqUDh6pFNX4A
Date: Tue, 2 Feb 2021 18:50:54 +0000
Message-ID: <fae85b0ad594409cb7726d73a6c85af4@cert.org>
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com> <5e926862-06e5-dfcf-0d73-83c44607f486@isode.com>
In-Reply-To: <5e926862-06e5-dfcf-0d73-83c44607f486@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.236]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/rsNIa3_UgUcDT04LdBJgtKdbp20>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:51:11 -0000

SGkgQWxleGV5IQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEFsZXhl
eSBNZWxuaWtvdiA8YWxleGV5Lm1lbG5pa292QGlzb2RlLmNvbT4NCj4gU2VudDogVHVlc2RheSwg
RmVicnVhcnkgMiwgMjAyMSAxMjoyNyBQTQ0KPiBUbzogUm9tYW4gRGFueWxpdyA8cmRkQGNlcnQu
b3JnPjsgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+DQo+IENjOiBleHRyYUBpZXRmLm9yZzsgYnJv
bmdAZmFzdG1haWx0ZWFtLmNvbTsgZHJhZnQtaWV0Zi1leHRyYS0NCj4gaW1hcDRyZXYyQGlldGYu
b3JnOyBleHRyYS1jaGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtFeHRyYV0gUm9tYW4g
RGFueWxpdydzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLWV4dHJhLQ0KPiBpbWFwNHJldjIt
MjY6ICh3aXRoIENPTU1FTlQpDQo+IA0KPiBIaSBSb21hbiwNCj4gDQo+IFJlcGx5aW5nIHRvIG9u
ZSBtb3JlIGNvbW1lbnQ6DQo+IA0KPiBPbiAwMi8wMi8yMDIxIDE1OjE1LCBSb21hbiBEYW55bGl3
IHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCj4gPiAqKiBTZWN0aW9uIDcuMS4gIE90aGVyIHRoYW4g
YSBjbGVhciB0ZXh0IGNvbm5lY3Rpb24sIHVuZGVyIHdoYXQNCj4gPiBjaXJjdW1zdGFuY2VzIHdv
dWxkIFBSSVZBQ1lSRVFVSVJFRCBiZSByZXR1cm5lZD8NCj4gVGhhdCBpcyBpdC4NCj4gPiBJIGFz
ayBiZWNhdXNlIHRoZSBzdGF0ZW1lbnQg4oCcVGhlIG9wZXJhdGlvbiBpcyBub3QgcGVybWl0dGVk
IGR1ZSB0byBhDQo+ID4gbGFjayBvZiBwcml2YWN54oCdIHNlZW1zIHJhdGhlciBnZW5lcmljIGFu
ZCBtaWdodCBiZW5lZml0IGZyb20gdGlnaHRlcg0KPiA+IHNjb3Bpbmcgb2Ygd2hhdCDigJxsYWNr
IG9mIHByaXZhY3nigJ0gbWVhbnMuDQo+IA0KPiBJIGNoYW5nZWQgInByaXZhY3kiIHRvICJkYXRh
IGNvbmZpZGVudGlhbGl0eSIuIERvIHlvdSB0aGluayB0aGlzIGlzIGNsZWFyIGVub3VnaA0KPiBu
b3c/DQoNCkluZGVlZC4gIFRoYW5rcyBmb3IgbWFraW5nIHRoZSBjaGFuZ2UuDQoNClJvbWFuDQo=


From nobody Tue Feb  2 10:58:39 2021
Return-Path: <rdd@cert.org>
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 763C13A1056; Tue,  2 Feb 2021 10:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 rT76zGkAhcmH; Tue,  2 Feb 2021 10:58:32 -0800 (PST)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 C8CFC3A1052; Tue,  2 Feb 2021 10:58:31 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 112IwRgM015105; Tue, 2 Feb 2021 13:58:27 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 112IwRgM015105
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1612292308; bh=tWXu0Pey6hKedSV3UeQgd8uuNl90wVVc9GteOWBsnUw=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=Kc5StCSDiesB/WpqbJzXLGPBQY7hPUK0va4E8kZKKyGpcguw3jsOb6Bu5U7Z6T+/a VjFwWr13xEMCB5jStLUa5esObIgalp86yFoDgeIeCvxSTwReDoab/h0mTK9OIXZa7C 5CEe9L90u9ki2NRQ2h+pjN3WQxwAV1YOQGEAbh+Q=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 112IwPGH040625; Tue, 2 Feb 2021 13:58:25 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 2 Feb 2021 13:58:25 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Tue, 2 Feb 2021 13:58:25 -0500
From: Roman Danyliw <rdd@cert.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>, The IESG <iesg@ietf.org>
CC: "extra@ietf.org" <extra@ietf.org>, "brong@fastmailteam.com" <brong@fastmailteam.com>, "draft-ietf-extra-imap4rev2@ietf.org" <draft-ietf-extra-imap4rev2@ietf.org>, "extra-chairs@ietf.org" <extra-chairs@ietf.org>
Thread-Topic: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
Thread-Index: AQHW+XZCTrqolprXI0KoFo+FtpNglKpFbOKA///JYUA=
Date: Tue, 2 Feb 2021 18:58:24 +0000
Message-ID: <82d4aa2b83474756b664dd21a50f0058@cert.org>
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com> <d11c48d6-bbe4-156f-30a8-d5206557d82d@isode.com>
In-Reply-To: <d11c48d6-bbe4-156f-30a8-d5206557d82d@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.236]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/L7FxWjxnuoL6xUgL4q7xjxnv-XM>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 18:58:35 -0000

SGkgQWxleGV5IQ0KDQpUaGFua3MgZm9yIHRoZSBxdWljayB0dXJuIGFyb3VuZCB3aXRoIGFsbCBv
ZiB0aGUgZWRpdHMgYW5kIHRoZSBmZXcgcGxhY2VzIHdoZXJlIHlvdSBleHBsYWluZWQgdGhhdCBh
IGNoYW5nZWQgaXNuJ3QgYXBwcm9wcmlhdGUuICBBIGJpdCBtb3JlIGlubGluZSAuLi4NCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpZXNnIDxpZXNnLWJvdW5jZXNAaWV0
Zi5vcmc+IE9uIEJlaGFsZiBPZiBBbGV4ZXkgTWVsbmlrb3YNCj4gU2VudDogVHVlc2RheSwgRmVi
cnVhcnkgMiwgMjAyMSAxMjowOCBQTQ0KPiBUbzogUm9tYW4gRGFueWxpdyA8cmRkQGNlcnQub3Jn
PjsgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+DQo+IENjOiBleHRyYUBpZXRmLm9yZzsgYnJvbmdA
ZmFzdG1haWx0ZWFtLmNvbTsgZHJhZnQtaWV0Zi1leHRyYS0NCj4gaW1hcDRyZXYyQGlldGYub3Jn
OyBleHRyYS1jaGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtFeHRyYV0gUm9tYW4gRGFu
eWxpdydzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLWV4dHJhLQ0KPiBpbWFwNHJldjItMjY6
ICh3aXRoIENPTU1FTlQpDQo+IA0KPiBIaSBSb21hbiwNCj4gDQo+IFRoYW5rIHlvdSBmb3IgeW91
ciBjb21tZW50cy4gUmVwbHlpbmcgdG8gbW9zdCBvZiB5b3VyIGNvbW1lbnRzIChJIHdpbGwgcmVw
bHkNCj4gdG8gdGhlIHJlc3Qgc2VwYXJhdGVseSk6DQo+IA0KPiBPbiAwMi8wMi8yMDIxIDE1OjE1
LCBSb21hbiBEYW55bGl3IHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCj4gPiAqKiBTZWN0aW9uIDEu
My4gIFdoYXQgYXJlIHRoZSDigJx1bnB1Ymxpc2hlZCBJTUFQMmJpcyBwcm90b2NvbHPigJ0/ICBF
dmVuDQo+ID4gaWYgdGhlcmUgd2VyZSB1bnB1Ymxpc2hlZCwgaXMgdGhlcmUgYW55IHBvaW50ZXIv
cmVmZXJlbmNlIHRoYXQgY2FuIGJlDQo+ID4gcHJvdmlkZWQsIHNheSBsaWtlIGh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWltYXAtaW1hcDJiaXMtMDI/DQo+IFllcywgdGhp
cyBsb29rcyBsaWtlIGEgcmVhc29uYWJsZSBpbmZvcm1hdGl2ZSByZWZlcmVuY2UuDQo+ID4gKiog
U2VjdGlvbiAyLjMuMS4xLiAgU3RlcCAjNC4gIFNob3VsZCDigJxJbiBwYXJ0aWN1bGFyLCB0aGUg
aW50ZXJuYWwNCj4gPiBkYXRlLCBbUkZDLTUzMjJdIHNpemUsIGVudmVsb3BlLCBib2R5IHN0cnVj
dHVyZSwgYW5kIG1lc3NhZ2UgdGV4dHMNCj4gPiAoYWxsIEJPRFlbLi4uXSBmZXRjaCBkYXRhIGl0
ZW1zKSBtdXN0IG5ldmVyIGNoYW5nZSnigJ0sIHVzZSB0aGUgbm9ybWF0aXZlDQo+IOKAnE1VU1Qg
bmV2ZXIgY2hhbmdl4oCdPw0KPiBTdXJlLg0KDQpUaGFua3MuDQoNCj4gPiAqKiBTZWN0aW9uIDIu
My4zLiAgVGhlIHRleHQgZm9yICRGb3J3YXJkZWQgbm90ZXMgdGhhdCDigJxPbmNlIHNldCwgdGhl
DQo+ID4gZmxhZyBTSE9VTEQgTk9UIGJlIGNsZWFyZWQu4oCdICBTaG91bGQgdGhlIHNhbWUgZ3Vp
ZGFuY2UgYXBwbHkgdG8NCj4gJE1ETlNlbnQ/DQo+ICRNRE5TZXQgZGVzY3JpcHRpb24gcG9pbnRz
IHRvIFJGQyAzNTAzLCB3aGljaCBzdGF0ZXMgIk1VU1QgTk9UIGJlDQo+IGNsZWFyZWQiLiBJIHdv
dWxkIHJhdGhlciBub3QgY29weSB0aGUgdGV4dCBpbnRvIHRoaXMgZHJhZnQsIGlmIHRoYXQgaXMg
T2sgd2l0aCB5b3U/DQoNCkkgaGFkbid0IGFjdHVhbGx5IGNoZWNrZWQgUkZDMzUwMy4gIElmIHRo
YXQncyBpbiB0aGVyZSwgbm8gbmVlZCB0byByZXBlYXQgaGVyZS4NCg0KPiA+ICoqIFNlY3Rpb24g
NS4xLjIuICBFZGl0b3JpYWwuICBzL21hbmFnZXIgdG8gZ3JhbnQgdG8gdGhlaXIgc2VjcmV0YXJ5
DQo+ID4gYWNjZXNzIHJpZ2h0cy9tYW5hZ2VyIHRvIGdyYW50IHRvIHRoZWlyIGFkbWluaXN0cmF0
aXZlIHN1cHBvcnQgc3RhZmYNCj4gPiBhY2Nlc3MgcmlnaHRzLw0KPiBPay4NCj4gPiAqKiBTZWN0
aW9uIDYuMy4xLiAgUGVyIOKAnEhvd2V2ZXIsIHNlcnZlcnMgY2Fubm90IHNlbmQgdGhvc2UgdW5z
b2xpY2l0ZWQNCj4gPiByZXNwb25zZXMgKHdpdGggdGhlIGV4Y2VwdGlvbiBvZiByZXNwb25zZSBj
b2RlcyAoc2VlIFNlY3Rpb24gNy4xKQ0KPiA+IGluY2x1ZGVkIGluIHRhZ2dlZCBvciB1bnRhZ2dl
ZCBPSy9OTy9CQUQgcmVzcG9uc2VzLCB3aGljaCBjYW4gYWx3YXlzDQo+ID4gYmUgc2VudCkgdW50
aWwgdGhleSBrbm93IHRoYXQgdGhlIGNsaWVudHMgc3VwcG9ydCBzdWNoIGV4dGVuc2lvbnMgYW5k
DQo+ID4gdGh1cyB3b24ndCBjaG9rZSBvbiB0aGUgZXh0ZW5zaW9uIHJlc3BvbnNlIGRhdGHigJ0s
IHdoYXQgaXMgdGhlIG1vcmUgcHJlY2lzZQ0KPiBkZWZpbml0aW9uIG9mIOKAnGNob2tl4oCdIGhl
cmUuDQo+ID4gSXMgaXQgdGhhdCB0aGUgY2xpZW50IGRvZXNu4oCZdCB1bmRlcnN0YW5kIHRoZSBl
eHRlbnNpb24gb3IgdGhhdCBpdA0KPiA+IHdvbuKAmXQgYmUgYWJsZSB0byBwcm9jZXNzIGl0Pw0K
PiBUaGUgZm9ybWVyLiBJIHRoaW5rIGl0IHdhcyBpbnRlbmRlZCBhcyBhIHNob3J0Y3V0IGZvciAi
Y3Jhc2ggYW5kIG1pc2JlaGF2ZSBpbg0KPiBvdGhlciBzdXJwcmlzaW5nIHdheXMiLg0KDQpPay4N
Cg0KPiA+ICoqIFNlY3Rpb24gNi4zLjkuMy4gIFN0ZXAgMy4gIFBlciDigJxBdHRyaWJ1dGVzIHJl
dHVybmVkIGluIHRoZSBzYW1lDQo+ID4gTElTVCByZXNwb25zZSBtdXN0IGJlIHRyZWF0ZWQgYWRk
aXRpdmVseeKAnSwgc2hvdWxkIHRoaXMgYmUgYSBub3JtYXRpdmUNCj4g4oCcTVVTVOKAnT8NCj4g
SSB0aGluayBNVVNUIGlzIGdvaW5nIHRvIGJlIGEgYml0IHNpbGx5IGhlcmUsIGFzIHRoZSB3aG9s
ZSBzZXQgaXMgc3BlY2lmaWVkIGluIGENCj4gc2luZ2xlIExJU1QgcmVzcG9uc2UuIEkgd2lsbCBj
aGFuZ2UgdGhpcyB0byAiYXJlIHRyZWF0ZWQgYWRkaXRpdmVseSIuDQo+ID4gKiogU2VjdGlvbiA2
LjMuMTIgYW5kIFNlY3Rpb24gOC4gIFRoZSBleGFtcGxlcyBoZXJlIGhhdmUgYSBmZXcg4oCcbm9u
DQo+IGV4YW1wbGXigJ0NCj4gPiBkb21haW5zIChlLmcuLCBAQmx1cmR5Ymxvb3AuY29tLCBAb3dh
dGFndS5zaWFtLmVkdSwNCj4gPiBAY2FjLndhc2hpbmd0b24uZWR1KQ0KPiBZZXMsIHRoaXMgY29t
ZXMgZnJvbSBSRkMgMzUwMS4gSSBjYW4gY2hhbmdlIHRoZXNlIGlmIHRoaXMgaXMgYSBiaWcgZGVh
bCB0byBwZW9wbGUsDQo+IGJ1dCB0aGlzIHdpbGwgY2F1c2UgbGl0ZXJhbCBzaXplIGNoYW5nZXMg
aW4gdmFyaW91cyBwbGFjZXMsIHNvIHRoaXMgaXMgbW9yZSB3b3JrDQo+IHRoYW4ganVzdCBzZWFy
Y2ggJiByZXBsYWNlIGV2ZXJ5d2hlcmUgaW4gdGhlIGRvY3VtZW50Lg0KPiA+ICoqIFNlY3Rpb24g
Ni40LjQuNC4gIEVkaXRvcmlhbC4gIEluIHRoaXMgc2VjdGlvbiB0aGUgaW5saW5lIGFubm90YXRp
b24NCj4gPiBvZiB0aGUNCj4gPiBDOiBhbmQgUzogZXhhbXBsZXMgYXJlIHdpdGggYSDigJwvL+KA
nS4gIEluIFNlY3Rpb24gNi4zLjEwLCB0aGVzZQ0KPiA+IGFubm90YXRpb25zIGFyZSBtYWRlIHZp
YSDigJw8IOKApiA+4oCdLiAgSeKAmWQgcmVjb21tZW5kIGNvbnNpc3RlbmN5Lg0KPiANCj4gT2su
IE11cnJheSBoYXMgcG9pbnRlZCBvdXQgdGhlIHNhbWUgdGhpbmcuIEkgd2lsbCBkaXNjdXNzIHdp
dGggUkZDIEVkaXRvciBhYm91dA0KPiB0aGUgYmVzdCB3YXkgb2YgcmVwcmVzZW50aW5nIGNvbW1l
bnRzLg0KDQpPay4NCg0KPiAgwqBbc25pcF0NCj4gDQo+ID4gKiogU2VjdGlvbiA3LjEuNC4gIFBl
ciDigJxGb3IgdGhpcyByZWFzb24gUFJFQVVUSCByZXNwb25zZSBTSE9VTEQgb25seQ0KPiA+IGJl
IHJldHVybmVkIGJ5IHNlcnZlcnMgb24gY29ubmVjdGlvbnMgdGhhdCBhcmUgcHJvdGVjdGVkIGJ5
IFRMUyAoc3VjaA0KPiA+IGFzIG9uIGltcGxpY2l0IFRMUyBwb3J0IFtSRkM4MzE0XSkgb3IgcHJv
dGVjdGVkIHRocm91Z2ggb3RoZXIgbWVhbnMNCj4gPiBzdWNoIGFzIElQU2Vj4oCdLCB3aGF0IGlz
IHRoZSBjb3JuZXIgY2FzZSBpbiBtaW5kIHRoYXQgbW90aXZlcyBhIFNIT1VMRA0KPiAoaW5zdGVh
ZCBvZiBhIE1VU1QpPw0KPiBJIHdhcyB0aGlua2luZyBhYm91dCBsb29wYmFjayBpbnRlcmZhY2Ug
b3Igc29tZXRoaW5nIGxpa2UgVW5peCBkb21haW4gc29ja2V0DQo+ICh0aGUgbGF0dGVyIGlzIHRl
Y2huaWNhbGx5IG91dCBvZiBzY29wZSBmb3IgdGhpcyBkb2N1bWVudCkuDQo+ID4gKiogU2VjdGlv
biAxMS4gIFRoZXJlIGFyZSBib3RoIGNvbmZpZGVudGlhbGl0eSBhbmQgaW50ZWdyaXR5IGlzc3Vl
cw0KPiA+IHdpdGggc2VuZGluZyBvZiBJTUFQIGluIHRoZSBjbGVhci4NCj4gPg0KPiA+IE9MRA0K
PiA+IElNQVA0cmV2MiBwcm90b2NvbCB0cmFuc2FjdGlvbnMsIGluY2x1ZGluZyBlbGVjdHJvbmlj
IG1haWwgZGF0YSwgYXJlDQo+ID4gc2VudCBpbiB0aGUgY2xlYXIgb3ZlciB0aGUgbmV0d29yayB1
bmxlc3MgcHJvdGVjdGlvbiBmcm9tIHNub29waW5nIGlzDQo+ID4gbmVnb3RpYXRlZC4NCj4gPg0K
PiA+IE5FVw0KPiA+IElNQVA0cmV2MiBwcm90b2NvbCB0cmFuc2FjdGlvbnMsIGluY2x1ZGluZyBl
bGVjdHJvbmljIG1haWwgZGF0YSwgYXJlDQo+ID4gc2VudCBpbiB0aGUgY2xlYXIgb3ZlciB0aGUg
bmV0d29yayBleHBvc2luZyB0aGVtIHRvIHBvc3NpYmxlDQo+ID4gZWF2ZXNkcm9wcGluZyBhbmQg
bWFuaXB1bGF0aW9uIHVubGVzcyBwcm90ZWN0aW9ucyBhcmUgbmVnb3RpYXRlZC4NCj4gSSB1c2Vk
IHlvdXIgdGV4dCwgdGhhbmsgeW91Lg0KPiA+ICoqIFNlY3Rpb24gMTEuMS4gIFBlciDigJxPdGhl
ciBUTFMgY2lwaGVyIHN1aXRlcyByZWNvbW1lbmRlZCBpbiBSRkMgNzUyNQ0KPiA+IGFyZSBSRUNP
TU1FTkRFRCDigKbigJ0sIHNlZW1zIGFzIGlmIFJGQzc1MjUgbmVlZHMgdG8gYmUgYW4gZXhwbGlj
aXQNCj4gcmVmZXJlbmNlLg0KPiANCj4gR29vZCBwb2ludC4gQWRkZWQuDQo+IA0KPiAgwqBbc25p
cF0NCj4gDQo+ID4gKiogSW4gdGhlIHNwaXJpdCBvZiBpbmNsdXNpdmUgbGFuZ3VhZ2UsIGNvbnNp
ZGVyIHNvbWV0aGluZyBsaWtlIHRoZSBmb2xsb3dpbmc6DQo+ID4NCj4gPiAtLSBTZWN0aW9uIDYu
Mi4xLiAgcy90byBwcm90ZWN0IGFnYWluc3QgbWFuLWluLXRoZS1taWRkbGUgYXR0YWNrZXJzDQo+
ID4gd2hpY2ggYWx0ZXIvdG8gcHJvdGVjdCBhZ2FpbnN0IGFuIG9uLXBhdGggYXR0YWNrZXIgd2hp
Y2ggY291bGQgYWx0ZXIvDQo+ID4NCj4gPiAtLSBTZWN0aW9uIDExLjENCj4gPiBPTEQNCj4gPiDi
gKYgYXMgcHJlc2VudGVkIGluIHRoZSBzZXJ2ZXIgQ2VydGlmaWNhdGUgbWVzc2FnZSwgaW4gb3Jk
ZXIgdG8gcHJldmVudA0KPiA+IG1hbi1pbi10aGUtbWlkZGxlIGF0dGFja3MuDQo+ID4NCj4gPiBO
RVcNCj4gPiDigKYgYXMgcHJlc2VudGVkIGluIHRoZSBzZXJ2ZXIgQ2VydGlmaWNhdGUgbWVzc2Fn
ZSwgaW4gb3JkZXIgdG8gcHJldmVudA0KPiA+IG9uLXBhdGggYXR0YWNrZXJzIGF0dGVtcHRpbmcg
dG8gbWFzcXVlcmFkZSBhcyB0aGUgc2VydmVyLg0KPiBDaGFuZ2VkLCB0aGFuayB5b3UuDQo+ID4g
LS0gU2VjdGlvbiAxMS4zLiAgcy8ob3IgYSBtYW4taW4tdGhlLW1pZGRsZSBhdHRhY2tlcikvIChv
ciBhbiBvbi1wYXRoDQo+ID4gYXR0YWNrZXIpLw0KPiBDaGFuZ2VkLg0KPiA+ICoqIFR5cG9zOg0K
PiA+IC0tIFNlY3Rpb24gMTEuMi4gcy9vdmVycmlkZW4vb3ZlcnJpZGRlbi8NCj4gRml4ZWQsIHRo
YW5rcy4NCj4gPiAqKiBGcm9tIGlkbml0czoNCj4gPiAgICAtLSBUaGUgZHJhZnQgaGVhZGVyIGlu
ZGljYXRlcyB0aGF0IHRoaXMgZG9jdW1lbnQgb2Jzb2xldGVzIFJGQzM1MDEsIGJ1dCB0aGUNCj4g
PiAgICAgICBhYnN0cmFjdCBkb2Vzbid0IHNlZW0gdG8gbWVudGlvbiB0aGlzLCB3aGljaCBpdCBz
aG91bGQuDQo+ID4NCj4gPiAgICAtLSBUaGVyZSBhcmUgYSBudW1iZXIgb2YgcmVmZXJlbmNlIHdh
cm5pbmdzIHdoaWNoIHNob3VsZCBiZSBjb25maXJtZWQgYXMNCj4gbm90DQo+ID4gICAgYmVpbmcg
cHJvYmxlbWF0aWMgKG5vdCBtZW50aW9uZWQgaW4gdGhlIHNoZXBoZXJkIHdyaXRlLXVwKQ0KPiAN
Cj4gV2lsbCBkby4gSSB0aGluayBhbGwgb2YgdGhlbSB3ZXJlIGNvdmVyZWQgYnkgdGhlIElFVEYg
TEMgYW5ub3VuY2VtZW50LCBidXQgSQ0KPiB3aWxsIGRvdWJsZSBjaGVjay4NCg0KVGhhbmtzIGZv
ciBhbGwgb2YgdGhlIGFib3ZlIGNoYW5nZXMuDQoNClJlZ2FyZHMsDQpSb21hbg0KDQo+IEJlc3Qg
UmVnYXJkcywNCj4gDQo+IEFsZXhleQ0KPiANCg0K


From nobody Thu Feb  4 01:33:37 2021
Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A918C3A10F6; Thu,  4 Feb 2021 01:33:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
Date: Thu, 04 Feb 2021 01:33:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/UmJFoJmACulKSmRLYH2sShYM5Fs>
Subject: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 09:33:32 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-extra-imap4rev2-27: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

There are several places where we see a:

   Note: Since this document is restricted to 7-bit ASCII text, it is
   not possible to show actual UTF-8 data.  [...]

But this document is *not* restricted to 7-bit ASCII text!
(I guess the (not-quoted) bit about not being possible to show actual KOI8-R data is
still true, though.)  Showing actual non-ASCII text may not be as
helpful as the current formulation, though, so I'd suggest just a
modification to the disclaimer.

Section 1.3

   IMAP was originally developed for the older [RFC-822] standard, and
   as a consequence several fetch items in IMAP incorporate "RFC822" in
   their name.  In all cases, "RFC822" should be interpreted as a
   reference to the updated [RFC-5322] standard.

It looks like it's down to just one (not "several"), now -- RFC822.SIZE.

Section 2.2.1

      response, and reads another response from the server.  In all
      cases, the client MUST send a complete command (including
      receiving all command continuation request responses and command
      continuations for the command) before initiating a new command.

To check my understanding: the "command continuations for the command"
are things that the client sends, right?  Adding a word or two might
help clarify.

Section 2.3.1.1

                                         A good UIDVALIDITY value to use
   is a 32-bit representation of the current date/time when the value is
   assigned: this ensures that the value is unique and always increases.
   Another possible alternative is a global counter that gets
   incremented every time a mailbox is created.

In light of the discussion in draft-gont-numeric-ids-sec-considerations,
I wonder if these are truly the most recommended options, as either
option has potential to leak some information about rate or time of
mailbox creation.  Leaking the time of mailbox creation to the user who
created it is, of course, not an issue, but not all IMAP mailboxes are
single-user-access.  A 32-bit PRP (e.g., block cipher) applied to either
option would provide some level of obfuscation while preserving the
uniqueness properties.

Section 2.3.2

   $Junk  The user (or a delivery agent on behalf of the user) may
      choose to mark a message as definitely containing junk ($Junk; see
      also the related keyword $NotJunk).  The $Junk keyword can be used
      to mark (and potentially move/delete messages later), group or
      hide undesirable messages.  See [IMAP-KEYWORDS-REG] for more
      information.

I'm not entirely sure what additional information I'm supposed to get
from [IMAP-KEYWORDS-REG]; the registry page is fairly short on
commentary.  (Applies throughout.)

Section 3.2

   In the authenticated state, the client is authenticated and MUST
   select a mailbox to access before commands that affect messages will
   be permitted.  This state is entered when a pre-authenticated
   connection starts, when acceptable authentication credentials have
   been provided, after an error in selecting a mailbox, or after a
   successful CLOSE command.

I think after a successful UNSELECT as well, right?  Â§6.4.2 says
"returns the server to the authenticated state" about UNSELECT.

Section 3.4

            (6) CLOSE command, unsolicited CLOSED response code or
                failed SELECT or EXAMINE command

[UNSELECT here as well, if above.]

Section 5.1.2.2

   Previous version of this protocol does not define a default server
   namespace.  Two common namespace models have evolved:

nit: maybe "the previous version of this protocol did not define" or
"previous versions of this protocol did not define"

Section 6.1.1

   Other capability names refer to extensions, revisions, or amendments
   to this specification.  See the documentation of the CAPABILITY
   response in Section 7.2.2 for additional information.  No
   capabilities, beyond the base IMAP4rev2 set defined in this
   specification, are enabled without explicit client action to invoke
   the capability.

Should we also note here that even the base IMAP4rev2 set can require
explicit client action to enable (e.g., when IMAP4rev1 is also
advertised)?

Section 6.2

   Server implementations MAY allow access to certain mailboxes without
   establishing authentication.  This can be done by means of the
   ANONYMOUS [SASL] authenticator described in [ANONYMOUS].  [...]

To be clear, from the perspective of the state machine, this entails
entering the "authenticated" state but without actually authenticating
as a specific client identity?

Section 6.2.1

Do we really want the example to show use of LOGIN (which per Â§6.2.3 is
be considered a "last resort" and SHOULD NOT be used) even when
AUTH=PLAIN is available?

Section 6.2.2

   As with any other client response, this initial response MUST be
   encoded as BASE64.  It also MUST be transmitted outside of a quoted

nit: it looks like we added another paragraph or two between the
previous mention of "initial response" and here, so maybe s/this/the/ is
in order.

      authentication.  (Note that SASL framework allows creation of SASL
      mechanisms that support 2FA (2-factor authentication), however
      none are fully ready to be recommended by this document.)

(side note) With sasl/gssapi/kerberos it's possible to know that the
client used 2fa for its authentication exchange with the KDC even if it
only has the one (ticket) factor to present to the IMAP server.  But
this is probably more detail than we need to get into here...

               C: A01 AUTHENTICATE PLAIN dGVzdAB0ZXN0AHRlc3Q=
               S: A001 OK Success (tls protection)

(nit) A01 is reusing the client tag, and doesn't seem to match the
response ... typo?

Section 6.2.3

   Unless either the client is accessing IMAP service on Implicit TLS
   port [RFC8314], the STARTTLS command has been negotiated or some
   other mechanism that protects the session from password snooping has
   been provided, a server implementation MUST implement a configuration
   in which it advertises the LOGINDISABLED capability and does NOT
   permit the LOGIN command.  [...]

(editorial) Given that there are preconditions based on runtime
behavior, it's a little strange to have it be "MUST implement" in this
manner.  If it's mandatory to use, that's an easy fix, but I suspect
that the intent is only that the server must implement a configuration
where it advertises LOGINDISABLED unless the preconditions are mit,
which seems like a more complicated rewording.

Section 6.3.1

   In the following example, the client enables CONDSTORE:

Should we reference RFC 7162 here?

Section 6.3.2

   fails is attempted, no mailbox is selected.  When deselecting a
   selected mailbox, the server MUST return an untagged OK response with
   the "[CLOSED]" response code when the currently selected mailbox is
   closed (see Paragraph 10).

I'm not sure how to find Paragraph 10.

Section 6.3.5

It kind of looks like the "examples" contains two similar examples stuck
together (or some other client has (re)created some folders
mid-session).  I think in RFC 3501 the blank line separating examples
also crossed a page boundary, so it got missed when converting to XML(?)
for the new document.

Section 6.3.6

   If the server's hierarchy separator character appears in the name,
   the server SHOULD create any superior hierarchical names that are
   needed for the RENAME command to complete successfully.  In other

Is this specifically in the "new mailbox name"?

   the normalized new mailbox name (see Section 6.3.9.7).  This would
   allow the client to correlate supplied name with the normalized name.

nit: "the supplied name".

Section 6.3.9.8

   4:   In this example, we see more mailboxes that reside on another
        server.  This is similar to the command <RLIST "" "%">.

      C: A04 LIST (REMOTE) "" "%" RETURN (CHILDREN)
      S: * LIST (\Marked \NoInferiors) "/" "inbox"
      S: * LIST (\HasChildren) "/" "Fruit"
      S: * LIST (\HasNoChildren) "/" "Tofu"
      S: * LIST (\HasChildren) "/" "Vegetable"
      S: * LIST (\Remote) "/" "Bread"
      S: * LIST (\HasChildren \Remote) "/" "Meat"
      S: A04 OK done

Why does "Bread" not give \HasChildren or \HasNoChildren?
I thought Â§6.3.9.5 said that the server MUST return these attributes
(and the example does show \HasChildren returned for another \Remote
box).

In example 10, "also" doesn't exist and "also/jazz" is remote.  Can we say
anything a priori about whether "also" is remote (the example, of
course, shows that it is not remote)?

Section 6.4.4

   However all options specified above MUST result in a single ESEARCH
   response if used by themselves or in combination.  This guaranty
   simplifies processing in IMAP4rev2 clients.  Future SEARCH extensions

nit: s/guaranty/guarantee/

   MAY be supported.  Clients SHOULD use UTF-8.  Note that if "CHARSET"
   is not provided IMAP4rev2 server MUST assume UTF-8, so selecting

nit: "an IMAP4rev2 server".

Section 6.4.4.4

      Example 4:
               C: P282 SEARCH RETURN (SAVE) SINCE 1-Feb-1994
                   NOT FROM "Smith"
               S: P282 OK SEARCH completed
               C: P283 SEARCH CHARSET UTF-8 (OR $ 1,3000:3021) TEXT {8}
               C: YYYYYYYY

That snippet doesn't seem consistent with a synchronizing literal;
should it be a non-synchronizing literal instead?

Section 6.4.8

   Because of the similarity of MOVE to COPY, extensions that affect
   COPY affect MOVE in the same way.  Response codes listed in
   Section 7.1, as well as those defined by extensions, are sent as
   appropriate.

Who decides what is "appropriate"?  Will everyone come to the same
conclusion?

Section 6.5

   Server implementations MUST NOT send any added (not specified in this
   specification) untagged responses, unless the client requested it by
   issuing the associated experimental command or the ENABLE command
   (Section 6.3.1).

We don't really have much text remaining to describe what the
"associated experimental command" would be, now that the "X<atom>
Command" section is removed.

Section 7.1

   CAPABILITY

         Followed by a list of capabilities.  This can appear in the
         initial OK or PREAUTH response to transmit an initial
         capabilities list.  It can also appear in tagged responses to
         LOGIN or AUTHENTICATE commands.  This makes it unnecessary for
         a client to send a separate CAPABILITY command if it recognizes
         this response.

(and if the implicit capability list is sent in the same
authentication/security-mechanism context as subsequent commands)

   COPYUID

         Followed by the UIDVALIDITY of the destination mailbox, a UID
         set containing the UIDs of the message(s) in the source mailbox
         that were copied to the destination mailbox and containing the
         UIDs assigned to the copied message(s) in the destination
         mailbox, indicates that the message(s) have been copied to the
         destination mailbox with the stated UID(s).

(editorial) Is there one UID set in the response or two (one per
source/destination)?  The following paragraph suggests two, but this one
seems to just say one.

   NOPERM

         The access control system (e.g., Access Control List (ACL), see
         [RFC4314] does not permit this user to carry out an operation,
         such as selecting or creating a mailbox.

nit: missing close paren.

Section 7.1.3

The example doesn't seem to show the tagged BAD usage, and I'm having
trouble convincing myself whether "very long command line" should
qualify for the tagged form or not.

Section 7.2, 7.3

If the section headings are split into server and mailbox status,
respectively, why does the initial intro paragraph still list both
server and mailbox status data in both sections?

Section 7.2.2

   Other capability names indicate that the server supports an
   extension, revision, or amendment to the IMAP4rev2 protocol.  Server
   responses MUST conform to this document until the client issues a
   command that uses the associated capability.

(another instance) should we say anything about "MUST conform to this
document" not applying when the server also advertises IMAP4rev1?

   A server MAY send capabilities automatically, by using the CAPABILITY
   response code in the initial PREAUTH or OK responses, and by sending
   an updated CAPABILITY response code in the tagged OK response as part
   of a successful authentication.  It is unnecessary for a client to
   send a separate CAPABILITY command if it recognizes these automatic
   capabilities.

IIRC, the earlier mention of automatic capabilities said that an
explicit CAPABILITY is still needed for the case when (e.g.)
AUTHENTICATE enables a new security layer.

Section 7.3.4

   [[TBD: describe the most common search data pairs returned.]]

Is this still current?

Section 7.5.2

   ENVELOPE
         [...]
         An address structure is a parenthesized list that describes an
         electronic mail address.  The fields of an address structure
         are in the following order: personal name, [SMTP] at-domain-
         list (source route, obs-route), mailbox name, and host name.

The "obs-route" was not in RFC 3501, is not listed in any published
errata reports, and does not seem to be called out in the list of
changes from RFC 3501 in Appendix E.  This isn't the formal protocol
description, so I guess it's not a breaking change, but I still don't
understand why it's different (presumably just my ignorance...).

   If the server chooses to send unsolicited FETCH responses, they MUST
   include UID FETCH item.  Note that this is a new requirement when
   compared to RFC 3501.

      Example:    S: * 23 FETCH (FLAGS (\Seen) RFC822.SIZE 44827)

I guess this is intended to just be a generic FETCH example, but it's a
bit jarring to not see the UID FETCH item in the example right after the
text that mentions a requirement to send it, with no other commentary.

Section 8

   The following is a transcript of an IMAP4rev2 connection on a non TLS
   port.  A long line in this sample is broken for editorial clarity.

More than one line, now.

C:   A001 AUTHENTICATE SCRAM-SHA-256
      biwsbj11c2VyLHI9ck9wck5HZndFYmVSV2diTkVrcU8=
S:   + cj1yT3ByTkdmd0ViZVJXZ2JORWtxTyVodllEcFdVYTJSYVRDQWZ1eEZJbGopaE5s
     RiRrMCxzPVcyMlphSjBTTlk3c29Fc1VFamI2Z1E9PSxpPTQwOTYNCg==
C:   Yz1iaXdzLHI9ck9wck5HZndFYmVSV2diTkVrcU8laHZZRHBXVWEyUmFUQ0FmdXhG
     SWxqKWhObEYkazAscD1kSHpiWmFwV0lrNGpVaE4rVXRlOXl0YWc5empmTUhnc3Ft
     bWl6N0FuZFZRPQ==
S:   + dj02cnJpVFJCaTIzV3BSUi93dHVwK21NaFVaVW4vZEI1bkxUSlJzamw5NUc0PQ==

These correspond quite nicely to (base64'd copies of) the example in RFC
7677, with the exception of the first server line, that includes an
additional CRLF in the decoded data.

Section 9

  body-fld-enc    = (DQUOTE ("7BIT" / "8BIT" / "BINARY" / "BASE64"/
                    "QUOTED-PRINTABLE") DQUOTE) / string
                    ; Content-Transfer-Encoding header field value.
                    ; Defaults to "7BIT" (as per RFC 2045)
                    ; if not present in the body part.

Is this comment still accurate?

  capability      = ("AUTH=" auth-type) / atom
                      ; New capabilities MUST begin with "X" or be
                      ; registered with IANA in
                      ; a standards-track, an experimental
                      ; or an informational RFC.

Is this comment still accurate?

  capability-data = "CAPABILITY" *(SP capability) SP "IMAP4rev2"
                    *(SP capability)
                      ; Servers MUST implement the STARTTLS, AUTH=PLAIN,
                      ; and LOGINDISABLED capabilities.
                      ; Servers which offer RFC 1730 compatibility MUST
                      ; list "IMAP4" as the first capability.
                      ; Servers which offer RFC 3501 compatibility MUST
                      ; list "IMAP4rev1" as one of capabilities.

I don't remember us mentioning an "IMAP4" capability in the previous
text, and I definitely remember an assertion that the order in which
capabilities are listed does not have significance, which seems to
conflict with the comment about "IMAP4" as the first capability.

  command-any     = "CAPABILITY" / "LOGOUT" / "NOOP" / x-command
                      ; Valid in all states

Is x-command still valid?

  media-basic     = ((DQUOTE ("APPLICATION" / "AUDIO" / "IMAGE" /
                    "FONT" / "MESSAGE" / "MODEL" / "VIDEO" ) DQUOTE)
                    / string)
                    SP media-subtype
                      ; Defined in [MIME-IMT].
                      ; FONT defined in RFC 8081.

Why does only FONT get a comment?  I don't see "MODEL" in [MIME-IMT],
either.

When the namespace-command production is defined, it's spelled all in
lowercase, but it is spelled "Namespace-Command" when it appears in the
command-auth production.

The "partial-range" production doesn't seem to be used anywhere.

  return-option   =  "SUBSCRIBED" / "CHILDREN" / status-option /
                     option-extension

(nit) This seems to only be used in list-return-opts, so maybe the
generic name is not the best fit for it.

Section 11

It might be worth putting in some bromide about how while md5 is used
in the BODYSTRUCTURE response, the usage is not particularly security
relevant and so there is not a vulnerability due to its use.

There are also some forms of DoS attack that we don't say much about
(slowloris, many parallel connections, etc.), and the mitigations are
fairly well known.  It might be worth expounding on these a little bit
(though since in most cases both parties have authenticated in some
manner, the situation is not as bad as it sometimes is).

Section 11.3

      as well as any response codes other than CAPABILITY.  Client
      SHOULD ignore the ALERT response code until after TLS has been
      successfully negotiated (whether using STARTTLS or TLS negotiation
      on implicit TLS port).  Unless explicitly allowed by an IMAP

Up in Â§7.1 we said that this was "without TLS or SASL security layer
confidentiality", not limited to TLS.
(Also, nit: "Clients" plural.)

Section 11.6

   A server SHOULD report any authentication failure and analyze such
   authentication failure attempt with regard to a password brute force
   attack as well as a password spraying attack.  Accounts that match
   password spraying attacks MUST be blocked and request to change their
   passwords and only password with significant strength SHOULD be
   accepted.

I'm not 100% sure that "password spraying attack" is a well-known
concept.  It probably is, but it's hard to be sure.

Also, I assume that "accounts that match password spraying attacks"
means accounts where the password being tested succeeds at
authenticating, which could be worth clarifying with a wording tweak.

Section 13.1

It's not clear to me that [ANONYMOUS] is referenced in a manner that
requires classification as normative; likewise for [SCRAM-SHA-256].
Similarly, if we use a modified form of [UTF-7] that we describe in
whole ourselves, that does not seem to be normative.

Section 13.2

If we refer to RFC 3503 for more details on how the mechanism is used,
should that be a normative reference?

Appendix E

   29.  Revised IANA registration procedure for IMAP extensions and
        removed "X" convention.

Is that worth a BCP 178 reference?




From nobody Thu Feb  4 05:53:44 2021
Return-Path: <daniel.migault@ericsson.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 55E1D3A14BF; Thu,  4 Feb 2021 05:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 27-APiNaE-zM; Thu,  4 Feb 2021 05:53:40 -0800 (PST)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2042.outbound.protection.outlook.com [40.107.237.42]) (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 45A0C3A14BE; Thu,  4 Feb 2021 05:53:40 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RG9Dg/ZBM2WifD438fgmnd0l6pH9PvvDWohS34XfUV5GnQ8FwNCyE4Ns9alK0p0O5eR5o7EmauaK+3JzHAB0YVTi1vD8LGEWKvRl6VRsxSi1b0vYpMs4bpl1QVyOExA5x7Z7ogwSjrN/11+kweLtSkzBgxD5D66i3dxTFoMwNQtWD0ygrVoExw183cFDGaYLt0Rnyr5jg3Q/f4e1yI1iJAmhzASctJb7BrlyRjEgXwxbxWwTBPWYP9tz1v34y1QUI+t6aAF6J8x+0IJsuz5gplhXO20KSGHxbWVPGxncNk1e9njLzLOK0MaK0sGCVm62/X++RMG1714eAT3IHasWvg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SR4DGe/HAJ/ON3thiN08tmfSHgaDBWnhSbAukgYJFHo=; b=ZKWcY6o35KSbDlTQ/ryqoa81jMq2eU5q2k+tuLkdXKYAd3LU+WrLckjXWvOgbDx8JdpNCOZeWDAFH6rrucpjcX33m6Qe1uhYAw2nAfylM+0MPIgxCRN6tEmJlNIuwkFhr1bK8VSPPZrPQZuXkFjaWmMSqwA2PH3wz1YR6wKe6BVrsoSklPvTfcT4eCgPzt9NSqTFGeC8mOmZzMoa0JbKO+GzzL3M2s12liT3yX60krWdXCkfwxFXNTxiEWeFPAMZJn5RYpGfSSTGRl0QL9to86obz9FpG9Tj3ZPR/dtD5Umns7qJFGkr0jyHrpHBIG3nFL7N/pidrwszknH0y/M1yA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SR4DGe/HAJ/ON3thiN08tmfSHgaDBWnhSbAukgYJFHo=; b=AoUbvMiRsqOGjUDwEOZEYiGpisEnnuT2KNoe3NhjkC3ttY449UFaBbDWP/jFc0IgnUq506VAD7cC/sAyKdnfu13JNw1d0WiH8URZeIIRX8Iys6lr4BVSWv7EMn42P9Naca9mDLDGv0L1/oFaHmVWf2SNQSc40881pISp8vCCchM=
Received: from DM6PR15MB2379.namprd15.prod.outlook.com (2603:10b6:5:8a::16) by DM6PR15MB4005.namprd15.prod.outlook.com (2603:10b6:5:294::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.16; Thu, 4 Feb 2021 13:53:37 +0000
Received: from DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::a9f9:326f:8cfb:157b]) by DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::a9f9:326f:8cfb:157b%7]) with mapi id 15.20.3825.017; Thu, 4 Feb 2021 13:53:37 +0000
From: Daniel Migault <daniel.migault@ericsson.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-extra-imap4rev2.all@ietf.org" <draft-ietf-extra-imap4rev2.all@ietf.org>, "extra@ietf.org" <extra@ietf.org>,  "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Secdir last call review of draft-ietf-extra-imap4rev2-24
Thread-Index: AQHW8k+UrIvwWNQJJ0uPOXDv4tfXT6pID6Ww
Date: Thu, 4 Feb 2021 13:53:37 +0000
Message-ID: <DM6PR15MB2379DB80CAD119DAEF853C1AE3B39@DM6PR15MB2379.namprd15.prod.outlook.com>
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com>, <180cc9c6-f438-f05d-741c-f250024738db@isode.com>
In-Reply-To: <180cc9c6-f438-f05d-741c-f250024738db@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: isode.com; dkim=none (message not signed) header.d=none;isode.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [96.22.11.129]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c95d6b78-36d3-46fc-8daf-08d8c9144558
x-ms-traffictypediagnostic: DM6PR15MB4005:
x-microsoft-antispam-prvs: <DM6PR15MB40059EFCACED809BD782DA7CE3B39@DM6PR15MB4005.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: AY4buC4cEedvVee+Udt+Efhnqq3cmotCc5kWVJPzBlPPls2zsJdM3SrdEe66qx9BI9BfHQ/gXCFakSCmvrBobme/DdzsN00S20DIC+O8myex/aYi+CAoR3lWMYFW8O6fm9Ef6kf5sJeFwgiBSUggsdeUL8Xqw2T9JPK2DLlj2HxzLHSnHUHlI7iZJsk9V+wAwJ0HDUCm+4cpgn14vpZTIc1j2vJDHbKc3ZjhWJzc88EwdP/kSlZtKwo8PPR8spjE5myzxhRnsDUMf4lIUUNmYg3MAvvNPr5Vfw21wIeoZIU07cEdb7ETVYoIWLVAHWMH+kLhtl2unEgu+KpbvZbd91Pvbu3/hLVT1C4/h9lpXclOP82HB+BUrUT2QszgAPbz1AbPkjRa8OZbSqusq+zx2Z1YtWbca6TqWHXN0SOuIn2nf43VphjMEe177qld6/DVUe3UzCM2MSgA3O088PLLE99nRm4U8Lky5T3LvZvk7gQRODsyr5TQPyikjEsPxTijnx9LVQtmxiow9TR0+YzPiP4OdAQxhj5i/klrx6V/rNmiSPkA/mn7R4kedSFg2mSor0omSazc3PEmVEKMP7CcgA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR15MB2379.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(39850400004)(346002)(366004)(136003)(396003)(76116006)(8676002)(55016002)(91956017)(9686003)(66476007)(66946007)(66556008)(19627405001)(64756008)(66446008)(83380400001)(2906002)(478600001)(5660300002)(7696005)(4326008)(44832011)(6506007)(53546011)(26005)(71200400001)(316002)(186003)(54906003)(110136005)(86362001)(33656002)(52536014)(8936002)(554374003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?lQyHPmo4IngXvthwpacihDSnpwaziAMLOiQuBN5h4Nrohu65xJ3QGAD5qG?= =?iso-8859-1?Q?SyTNHge5WgenBronuAw44DKG/EGogF1eFbTaFh45Dli4RpOVCVUuTSrm2s?= =?iso-8859-1?Q?trrUsrhTi0geTAZ/kjJxBVSGeMiz76YM9RjPG5GI7BA0jiQbXy2+4Gm6bb?= =?iso-8859-1?Q?kIrYwspdcDv+dLwWr4Dek+OsmoQza+pLwyZ77e7Zj+3LMRJuWNSLUcP1jT?= =?iso-8859-1?Q?tAY2jqVx61YVVtNz7XWEZorrIen/IPqpCiXQkDRhC2qaaeEklcU8FJUIMO?= =?iso-8859-1?Q?P3amOnfJhOK7tIrajQfsyyv/idJDzIxpdKwsSSD5qnn6x5fEOTznHsPYf4?= =?iso-8859-1?Q?Kn/Ihxr95jWP36FOljXDKpgCmoKlm6EfpSv7BJWGP00dqBZ2yNBRcy+xue?= =?iso-8859-1?Q?DCWKjeb3RgQlWm4Ef25T3e/MBrXKCEP0nKmejbW/ShfCBtX+lBI5OkZDBk?= =?iso-8859-1?Q?cS6SZaKHCbAFbzQwvQJweeFhRmJsEj+Qz1CAVt3aycluIFQUNUzqw18y9I?= =?iso-8859-1?Q?F2VjmkVkL+qIgIgVaoIJMIZTqZXM0uitQcMEMUhc0ofcjwVHsm7HECrMZG?= =?iso-8859-1?Q?aw1pImC7MDZvW1KZufYivTKmCvp8+f1yTdcIn33COooMbLVMNFbRlommRt?= =?iso-8859-1?Q?4d8e5W+lxpGaag/UTOTBa/+pgKUHB77UiFkGXIgpnz4Ixc3go9RNSY3wnx?= =?iso-8859-1?Q?o9F+DejUKauluFf+ADk1QE56SOMSGZ/23d0Vp8ZaxlWy+mscwbdZgq5iMG?= =?iso-8859-1?Q?w4FJB3HXD5JvBBH/Wegbltzft5Ar0vN5CGcCm40d2sI3OyfrNDbN5rutkI?= =?iso-8859-1?Q?BYMCdHYbTsObPAswzbP+bjcMQZXSHVezGOqxxXQp61fJIOwvURXyBnUWuD?= =?iso-8859-1?Q?aPMMoCo2kocDoZaXW6y0Kzsan67Or9DY8dstIDm4zUYlXMHFZnEF6Fbrd4?= =?iso-8859-1?Q?BnNpP9NNMLcsfj/irMBayKnLGbS2qr0lTpGxwleClFbg6xp6OT44Is8o6p?= =?iso-8859-1?Q?Mgp0ktyqgA6dt61G8w24HjDrbEUN42C2BmZ0jTY2yDKESbGTksTgIACqFf?= =?iso-8859-1?Q?vd6GGgEN81pEAtN9xQ3Q6SQ=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR15MB2379DB80CAD119DAEF853C1AE3B39DM6PR15MB2379namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR15MB2379.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c95d6b78-36d3-46fc-8daf-08d8c9144558
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Feb 2021 13:53:37.1566 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: swX34LEgq0Z8ZVpSB+MhH/XZwVxfZK2i3OC6WLbDmeN2jUh+c0qBqRzfqkud39OvQcLjg0oNfoTK0FhZ9jIfXEqutfcwjPX52Q1cYxjYrOY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB4005
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/oZWU9QEsZBAbEzFhuUY61ifAssU>
Subject: Re: [Extra] Secdir last call review of draft-ietf-extra-imap4rev2-24
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 13:53:42 -0000

--_000_DM6PR15MB2379DB80CAD119DAEF853C1AE3B39DM6PR15MB2379namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I do see your point. My point here was more to point there exists some alte=
rnatives that worth being considered and might be developed in the future. =
I agree this might require more work than I am currently thinking of. I do =
not know how biased I am toward DANE, so I let you do what you think is bes=
t.

Yours,
Daniel



________________________________
From: Alexey Melnikov <alexey.melnikov@isode.com>
Sent: Sunday, January 24, 2021 7:50 AM
To: Daniel Migault <daniel.migault@ericsson.com>; secdir@ietf.org <secdir@i=
etf.org>
Cc: draft-ietf-extra-imap4rev2.all@ietf.org <draft-ietf-extra-imap4rev2.all=
@ietf.org>; extra@ietf.org <extra@ietf.org>; last-call@ietf.org <last-call@=
ietf.org>
Subject: Re: Secdir last call review of draft-ietf-extra-imap4rev2-24

Hi Daniel,

On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:

  [snip]

>     During the TLS negotiation [TLS-1.3][TLS-1.2], the client MUST check
>     its understanding of the server hostname against the server's
>     identity as presented in the server Certificate message, in order to
>     prevent man-in-the-middle attacks.  This procedure is described in
>     [RFC7817].
>
> <mglt>
> I think it would be good to mention DANE as
> well as certificate checks.

This came up before, but at this point there is no document describing
how to use DANE with email clients (an alternative/update to RFC 7817)
and I am not aware of any client implementations that use DANE
experimentally for this.

Best Regards,

Alexey


--_000_DM6PR15MB2379DB80CAD119DAEF853C1AE3B39DM6PR15MB2379namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Hi,&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
I do see your point. My point here was more to point there exists some alte=
rnatives that worth being considered and might be developed in the future. =
I agree this might require more work than I am currently thinking of. I do =
not know how biased I am toward
 DANE, so I let you do what you think is best.&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Yours,&nbsp;<br>
Daniel</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id=3D"appendonsend"></div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Alexey Melnikov &lt;a=
lexey.melnikov@isode.com&gt;<br>
<b>Sent:</b> Sunday, January 24, 2021 7:50 AM<br>
<b>To:</b> Daniel Migault &lt;daniel.migault@ericsson.com&gt;; secdir@ietf.=
org &lt;secdir@ietf.org&gt;<br>
<b>Cc:</b> draft-ietf-extra-imap4rev2.all@ietf.org &lt;draft-ietf-extra-ima=
p4rev2.all@ietf.org&gt;; extra@ietf.org &lt;extra@ietf.org&gt;; last-call@i=
etf.org &lt;last-call@ietf.org&gt;<br>
<b>Subject:</b> Re: Secdir last call review of draft-ietf-extra-imap4rev2-2=
4</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt"=
>
<div class=3D"PlainText">Hi Daniel,<br>
<br>
On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:<br>
<br>
&nbsp;&nbsp;[snip]<br>
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; During the TLS negotiation [TLS-1.3][TLS-1.2],=
 the client MUST check<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; its understanding of the server hostname again=
st the server's<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; identity as presented in the server Certificat=
e message, in order to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; prevent man-in-the-middle attacks.&nbsp; This =
procedure is described in<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; [RFC7817].<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; I think it would be good to mention DANE as<br>
&gt; well as certificate checks.<br>
<br>
This came up before, but at this point there is no document describing <br>
how to use DANE with email clients (an alternative/update to RFC 7817) <br>
and I am not aware of any client implementations that use DANE <br>
experimentally for this.<br>
<br>
Best Regards,<br>
<br>
Alexey<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_DM6PR15MB2379DB80CAD119DAEF853C1AE3B39DM6PR15MB2379namp_--


From nobody Thu Feb  4 06:34:21 2021
Return-Path: <barryleiba@gmail.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 9B1953A152C; Thu,  4 Feb 2021 06:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 e31Kw0Mibhoo; Thu,  4 Feb 2021 06:34:14 -0800 (PST)
Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D91463A15FB; Thu,  4 Feb 2021 06:33:26 -0800 (PST)
Received: by mail-lf1-f49.google.com with SMTP id v5so2629051lft.13; Thu, 04 Feb 2021 06:33:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WrIZmltovRMg58ATIW3ICA0bTMMID33IZrs8MHCwncs=; b=gNHpE7wzuNonJxg5soMIgmPHBEwx7QAuiCCTc3sG2UXrD1Cs5IPkZE6ePeOFhHShry dyn/IsFOd1d6LQk98LzlMQp4EkZNF05iwGFM9M2w1Kdvrcbdpvd+I5qjf0Rw4f8iagRD +7UKGAU+FxUBkMvwDwIgXjtAth6tCa0KQNa5ztTroGusslwxALAI6ekgE0ioSEh3Z//g lyOm2HeRECROQUhIWykRVRUE26z2Id/j0EomSu7qLz/CjWStioEtoN8H82NQ1rqsS7w0 razrkSCzNocgxBCx3/Egq5XcUTxc/suUnujvY5kQaErKS/tX6xB9OWltxbG21eC/5cFx 1XNQ==
X-Gm-Message-State: AOAM533RGFNrpKRufmZAVw+chkq3VPaiEmOOautEwLd1Xih94xS9Qwex AzEPfcnPpxYTNpyDLdqmGtKIA7suZTp+49YQJQE=
X-Google-Smtp-Source: ABdhPJzJESES6TV1FGEeTo92FBZxG+9tcu3Caju8SbUQe0rCJQTKs5bvANWx/y8i4Y20RRuqITX5fwHEoPrD8huAG5c=
X-Received: by 2002:a05:6512:31c1:: with SMTP id j1mr4943563lfe.313.1612449204743;  Thu, 04 Feb 2021 06:33:24 -0800 (PST)
MIME-Version: 1.0
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
In-Reply-To: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 4 Feb 2021 09:33:13 -0500
Message-ID: <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org,  extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/qGiygaaLOVSpyf58X-B1hzmElhM>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 14:34:16 -0000

Thanks, Ben, for the usual good comments.  Just responses on a couple here:

> Section 2.2.1
>
>       response, and reads another response from the server.  In all
>       cases, the client MUST send a complete command (including
>       receiving all command continuation request responses and command
>       continuations for the command) before initiating a new command.
>
> To check my understanding: the "command continuations for the command"
> are things that the client sends, right?  Adding a word or two might
> help clarify.

Yes, it should say "and sending command continuations"; the word
"sending" is missing.

> Section 2.3.1.1
>
>                                          A good UIDVALIDITY value to use
>    is a 32-bit representation of the current date/time when the value is
>    assigned: this ensures that the value is unique and always increases.
>    Another possible alternative is a global counter that gets
>    incremented every time a mailbox is created.
>
> In light of the discussion in draft-gont-numeric-ids-sec-considerations,
> I wonder if these are truly the most recommended options, as either
> option has potential to leak some information about rate or time of
> mailbox creation.  Leaking the time of mailbox creation to the user who
> created it is, of course, not an issue, but not all IMAP mailboxes are
> single-user-access.  A 32-bit PRP (e.g., block cipher) applied to either
> option would provide some level of obfuscation while preserving the
> uniqueness properties.

It would obfuscate and preserve uniqueness, but it would not preserve
the monotonicity: a new UIDVALIDITY must always be greater than the
previous ones.  Do you have a good suggestion for that, which still
takes care of the privacy leak?

> Section 2.3.2
>
>    $Junk  The user (or a delivery agent on behalf of the user) may
>       choose to mark a message as definitely containing junk ($Junk; see
>       also the related keyword $NotJunk).  The $Junk keyword can be used
>       to mark (and potentially move/delete messages later), group or
>       hide undesirable messages.  See [IMAP-KEYWORDS-REG] for more
>       information.
>
> I'm not entirely sure what additional information I'm supposed to get
> from [IMAP-KEYWORDS-REG]; the registry page is fairly short on
> commentary.  (Applies throughout.)

It's meant to send you to the reference doc, but, yes, the reader
already has that anyway.  It might simply be better to say that the
registration is recorded in IMAP-KEYWORDS-REG.

> Section 6.4.8
>
>    Because of the similarity of MOVE to COPY, extensions that affect
>    COPY affect MOVE in the same way.  Response codes listed in
>    Section 7.1, as well as those defined by extensions, are sent as
>    appropriate.
>
> Who decides what is "appropriate"?  Will everyone come to the same
> conclusion?

It means that the same responses are sent for MOVE as for COPY, under
the corresponding conditions.  Yes, we'd expect that to be evident.
We can try rephrasing it if you think that's unclear.  Is what I said
two sentences ago clearer?  Do you have other suggestions?

Barry


From nobody Thu Feb  4 06:42:03 2021
Return-Path: <timo@sirainen.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 7AA2A3A1543; Thu,  4 Feb 2021 06:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fdUqNOAYq1b5; Thu,  4 Feb 2021 06:41:56 -0800 (PST)
Received: from sirainen.com (mail.sirainen.com [94.237.26.55]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2563A1545; Thu,  4 Feb 2021 06:41:55 -0800 (PST)
Received: from [192.168.10.120] (unknown [213.114.248.18]) by sirainen.com (Postfix) with ESMTPSA id 958C42B3C7E; Thu,  4 Feb 2021 14:41:53 +0000 (UTC)
From: Timo Sirainen <timo@sirainen.com>
Message-Id: <5A095B75-3BB9-4558-A8DA-826C7C875B10@sirainen.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_05F9380A-A3CE-44FF-B04E-84D67F061C01"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Thu, 4 Feb 2021 15:41:53 +0100
In-Reply-To: <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>, draft-ietf-extra-imap4rev2@ietf.org, The IESG <iesg@ietf.org>, extra-chairs@ietf.org
To: Barry Leiba <barryleiba@computer.org>
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com> <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/OkRgKfA6Q3OqWxHTH7S6OYRYxo0>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 14:41:59 -0000

--Apple-Mail=_05F9380A-A3CE-44FF-B04E-84D67F061C01
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 4. Feb 2021, at 15.33, Barry Leiba <barryleiba@computer.org> wrote:
>=20
>> Section 2.3.1.1
>>=20
>>                                         A good UIDVALIDITY value to =
use
>>   is a 32-bit representation of the current date/time when the value =
is
>>   assigned: this ensures that the value is unique and always =
increases.
>>   Another possible alternative is a global counter that gets
>>   incremented every time a mailbox is created.
>>=20
>> In light of the discussion in =
draft-gont-numeric-ids-sec-considerations,
>> I wonder if these are truly the most recommended options, as either
>> option has potential to leak some information about rate or time of
>> mailbox creation.  Leaking the time of mailbox creation to the user =
who
>> created it is, of course, not an issue, but not all IMAP mailboxes =
are
>> single-user-access.  A 32-bit PRP (e.g., block cipher) applied to =
either
>> option would provide some level of obfuscation while preserving the
>> uniqueness properties.
>=20
> It would obfuscate and preserve uniqueness, but it would not preserve
> the monotonicity: a new UIDVALIDITY must always be greater than the
> previous ones.  Do you have a good suggestion for that, which still
> takes care of the privacy leak?

I wouldn't mind if that requirement was relaxed with rev2. It should be =
enough that the UIDVALIDITY is always different if a mailbox gets =
recreated. My guess is that all/most IMAP4rev1 clients would already =
work correctly.


--Apple-Mail=_05F9380A-A3CE-44FF-B04E-84D67F061C01
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
4. Feb 2021, at 15.33, Barry Leiba &lt;<a =
href=3D"mailto:barryleiba@computer.org" =
class=3D"">barryleiba@computer.org</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">Section 2.3.1.1<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A good UIDVALIDITY value to use<br =
class=3D"">&nbsp;&nbsp;is a 32-bit representation of the current =
date/time when the value is<br class=3D"">&nbsp;&nbsp;assigned: this =
ensures that the value is unique and always increases.<br =
class=3D"">&nbsp;&nbsp;Another possible alternative is a global counter =
that gets<br class=3D"">&nbsp;&nbsp;incremented every time a mailbox is =
created.<br class=3D""><br class=3D"">In light of the discussion in =
draft-gont-numeric-ids-sec-considerations,<br class=3D"">I wonder if =
these are truly the most recommended options, as either<br =
class=3D"">option has potential to leak some information about rate or =
time of<br class=3D"">mailbox creation. &nbsp;Leaking the time of =
mailbox creation to the user who<br class=3D"">created it is, of course, =
not an issue, but not all IMAP mailboxes are<br =
class=3D"">single-user-access. &nbsp;A 32-bit PRP (e.g., block cipher) =
applied to either<br class=3D"">option would provide some level of =
obfuscation while preserving the<br class=3D"">uniqueness properties.<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">It would obfuscate and preserve uniqueness, but it would not =
preserve</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">the =
monotonicity: a new UIDVALIDITY must always be greater than =
the</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">previous =
ones. &nbsp;Do you have a good suggestion for that, which =
still</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">takes care of =
the privacy leak?</span><br class=3D""></div></div></blockquote><br =
class=3D""></div><div>I wouldn't mind if that requirement was relaxed =
with rev2. It should be enough that the UIDVALIDITY is always different =
if a mailbox gets recreated. My guess is that all/most IMAP4rev1 clients =
would already work correctly.</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_05F9380A-A3CE-44FF-B04E-84D67F061C01--


From nobody Thu Feb  4 07:21:27 2021
Return-Path: <alissa@cooperw.in>
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 1384C3A15AD; Thu,  4 Feb 2021 07:21:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=NMVEDa7b; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BuRcpe4A
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 1WfV0D5pvy_W; Thu,  4 Feb 2021 07:21:20 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45A963A15AA; Thu,  4 Feb 2021 07:21:20 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 46DDFF51; Thu,  4 Feb 2021 10:21:19 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 04 Feb 2021 10:21:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=W 8D2O7Nzf0p3f8lx/SyR4CEjnPBJCjKXcKUGmX7lVnY=; b=NMVEDa7b+9t9NGz/C xmKQUYWveW4CHPfBahGPc3aAV4E0pv9NcIKb1d1PDIuz6piKNCfG7W/qcS8yA/b0 EWYvRoEmLXfq7cXNVIF6F9XWCMusrZoC1Ni3wk1yhg9/HBTT892bXLJh4BFmvIlK XHHH6FsSkaq9du86UGV/BwQRroD+9LppQ8GmFrOtj2FP14QeZbQTLS3JiBed8A/c zcR3w0q0q8HjRIeWPSReVxNptZwoZ9SY8qsV7YskjYrD1kk7D1d9JrhCx5xX7g1e Uuak4Am80aViTBXJGW7mLJSTs4cQYLgcXON3RK7ddffuXgCO/Os88ZZ9AGYYTOze VNiXA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=W8D2O7Nzf0p3f8lx/SyR4CEjnPBJCjKXcKUGmX7lV nY=; b=BuRcpe4Au20Q1lZnyP95QlpkCCpzDkYYNMzTJ6G6RitIofgCJhRTRF0N0 2z1IEC6HgwEMj3lINI7ZBwUXV0LS8exCmLEcdUyeLCFFoIVR6FtYqN8VN8OaghaU 23s7ZPp5N5uiR0FBZ/QoGQ8f+V0DQrFKfK/CaHYHI8xu6q7q2K0OJs9lgbl2xZAr Ih8K4+zNVC1hX/uS55ookwhzX/9QtVQ7JO5JGmSviQ51XOQnnewcdsuHEBTjr0xe c7MuGVHLGk6pUH/B+Adf1yul8weYJgIvZZMsvM2ZpV5LCPf+zv1QsQ0G6dRk+Wtl aHbLvVCmbQAqUzH5+B7HpeYNLlTjg==
X-ME-Sender: <xms:7RAcYLyXB0lcjM2IeAoMuthn1P9jc7ClIKKowksDxDjPQT1lUSh0EA> <xme:7RAcYDSf1BsYxY6Z1vbWVPscHkh8kXNOWGbdoW_AUh1R0dBLT_m9KK0MsS0qyd8lb -sDxpyBBBCP1eFEJQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeeggdeijecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhepjeefieelieeivddugeehudeiudfghffhjeejvdfftddvtddvieekudfhuedu ueeinecukfhppedujeefrdefkedruddujedrjedunecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:7RAcYFXZ4LPg1abe2t1_8Lp5rx0y5gatshhqlxon_Cm744sDqTc16w> <xmx:7RAcYFhTPu9U5RHLpfExxJz7vXc5zx_xYDwz1y8G3DEwogWykvuApw> <xmx:7RAcYNBQzj2iu9CowWUFmKgWiVtmXAGmBnKj7GYEo7Oid7hjzy8FEw> <xmx:7hAcYMNE0T7reNoLNkenFrNT7CCInLM2nt0SbTyVzGrwnNJkhWAp4w>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.71]) by mail.messagingengine.com (Postfix) with ESMTPA id 48CEE108005C; Thu,  4 Feb 2021 10:21:17 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com>
Date: Thu, 4 Feb 2021 10:21:16 -0500
Cc: IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in>
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/VCOcWSs02PAaMfxDaOJhRsnbpik>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 15:21:22 -0000

Hi Barry,

> On Feb 2, 2021, at 1:12 PM, Barry Leiba <barryleiba@computer.org> =
wrote:
>=20
>> (1) Section 6.3.9 says:
>>=20
>> "The LIST command SHOULD return its data quickly, without undue =
delay.
>>   For example, it SHOULD NOT go to excess trouble to calculate the
>>   \Marked or \Unmarked status or perform other processing"
>>=20
>> The second sentence seems like it does not warrant normative language =
given
>> that it is giving an example
>=20
> Indeed; this slipped through from the original.  I agree that we don't
> need the same BCP 14 statement twice.
>=20
>> (2) There are some recurring example names -- owatagusiam, =
blurdybloop, etc. --
>> that could probably be replaced with names that are a little more
>> accessible/obvious to new readers. Also, there are a lot of examples =
with user
>> names from the same cultural/linguistic context -- smith, fred, eric, =
etc.
>> Neutralizing or diversifying those names would improve the document.
>=20
> This harks back to older times and to the late Mark Crispin, who liked
> those sorts of things.
>=20
> I agree with you.
>=20
> That said, there are two things:
>=20
> 1. As Alexey has pointed out with other comments, changing these often
> involves carefully checking literal lengths, RFC822-SIZE values, and
> other such, and has a high potential to introduce errors.
>=20
> 2. I have some thought toward keeping Mark's voice in here, and that
> mostly shows up in the examples.  Part of me would rather not scrub it
> out.

The point of raising it in the first place was about perpetuating the =
biases of the earlier documents/authors. The base RFCs will remain in =
the archive for people to read.

Alissa
=20

>=20
> Alexey, thoughts?
>=20
> Barry


From nobody Thu Feb  4 07:32:24 2021
Return-Path: <barryleiba@gmail.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 8120E3A0CFC; Thu,  4 Feb 2021 07:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 XVmMumrVYKhb; Thu,  4 Feb 2021 07:32:18 -0800 (PST)
Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37C293A15B9; Thu,  4 Feb 2021 07:32:18 -0800 (PST)
Received: by mail-lj1-f176.google.com with SMTP id s18so3885703ljg.7; Thu, 04 Feb 2021 07:32:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iM1G8OeqMlt0keoNNwCJHo2vAcs6zwQV4avr+GMWrYM=; b=buX5wU20nKghyQLGscLNJIJKDNwCu3A5lZ0/mhqr46SgH99nltASnZRmcIF00NK+4Q Yxx/yRmzF5DgSWKaFKUWV10lwlmrO0jqCtdqRWgtMfHV7DgnvRXbLyVzyP8UXTLoqxkZ zotxQRDUsR0b8MxXrKbpbwsNMUiyDWUk+i2cxafG3s7O9SfR/roTVkEP0r9tg1OfZYxB tUF4D60goxCMQDS5c5f1rjrdNjPxgoZz15Jit/8aZc5wa94cR9HRW1LQBTKPh+C4XibW s0lE2CRwc0TIS+Sjko23p87bziGB2NA3CETK3KFQ/jiFBN7TRoO//w4SZDnCIsJxiyCJ IuVQ==
X-Gm-Message-State: AOAM530auFdf/uL+kEePbyQUhjdI7K0WdGRuzobudmsH2V0T9MDmWFlO kZQ/Yobl48rjsLq1h+ngOLg760TvyRJakHVukLeCwF1+GGE=
X-Google-Smtp-Source: ABdhPJxqoDfYce8nSFSyDPUjqtLy3kknA5vmPp+ZSdkFzJxoilPHySrZh70slgxsAHsEZbkebKOcHNGj5f4WtM6J+TI=
X-Received: by 2002:a2e:b5cd:: with SMTP id g13mr5117807ljn.248.1612452736276;  Thu, 04 Feb 2021 07:32:16 -0800 (PST)
MIME-Version: 1.0
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com> <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in>
In-Reply-To: <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 4 Feb 2021 10:32:03 -0500
Message-ID: <CALaySJLNnD0gJyjsMjQODC_vKLFQPJMf_oBnfp_hS2nrSD+2Tg@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org,  extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/LNySqpkGJfkg3IpsbrpwCYAhfG0>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 15:32:20 -0000

> > That said, there are two things:
> >
> > 1. As Alexey has pointed out with other comments, changing these often
> > involves carefully checking literal lengths, RFC822-SIZE values, and
> > other such, and has a high potential to introduce errors.
> >
> > 2. I have some thought toward keeping Mark's voice in here, and that
> > mostly shows up in the examples.  Part of me would rather not scrub it
> > out.
>
> The point of raising it in the first place was about perpetuating the biases of the earlier documents/authors.
> The base RFCs will remain in the archive for people to read.

Yes, true, and that takes care of point 2.  You're right.

Do you think it's worth the risk of introducing errors (point 1)?

Barry


From nobody Thu Feb  4 08:43:00 2021
Return-Path: <murch@fastmail.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 772D63A1657 for <extra@ietfa.amsl.com>; Thu,  4 Feb 2021 08:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=obLCJLzs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gl3LDHzF
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 dijg3econR0t for <extra@ietfa.amsl.com>; Thu,  4 Feb 2021 08:42:58 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E92C3A1659 for <extra@ietf.org>; Thu,  4 Feb 2021 08:42:58 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 50E435C0037; Thu,  4 Feb 2021 11:42:57 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 04 Feb 2021 11:42:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:cc:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=3 ovyZB3RlmLd5ngnnWPP+/w7GPPB8LzEPJUJQ397Z18=; b=obLCJLzsExQPJp5zw o0eBfQkyryAccJe/bSZn75/FCa0KGIwwqOoJCldr5QhOx/sqJBRfAwWnQsFUhN7H zrW3CXYFpxYnNV6MbvxMfc/YDtpjZmFVjucXQbE8EeIPpk7CQmxXNmsN5px0qu3S kKFZ25eJUQgBj5M6KiKjAWO/2ISJ45/8hI2v6PsX8ZKx8HLoDl7EDlfxvsOoEzhn 5GQKEXZ3wjikpT18k8VWDw1V1RV3GQUH0xiFX3gem22B/uxskN6XbjQ/t7YojgrN NjqaOy/H3QVohjDIvSFUByKTa1oY+dJl3UTZiKlABwf67yHF4+VVnW2xJKr+MCtD E3n3w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=3ovyZB3RlmLd5ngnnWPP+/w7GPPB8LzEPJUJQ397Z 18=; b=gl3LDHzFzSuGYW1/KA0tYnV2lQPacLf4SfXkxv8XjLq80Hj08VyfiLWcm J3MNAWndUcQXo0sCq3LwXTc+TErNBAswVBfgplawv8CjKr1XLsqaqIEKEuVuvejK ekriqI2xC9P//uVeTZaJdKaMmsj2/R0uktHfFSiQwBquUEQT37nkhUvDESBojz7v +HiS65GA/axwkdLPpCuY9MRrFEO9ht6nXAoRchdYn6rpO1YhHG8gltl3Zpfv6SAj Qc8W8oGtNe6coSrFRGbw2hcPbEEw25mU5mizOJKI2SDDkCf6sgaWOJ6xDV7X81mK wZZOXHvRWq6BmrD4Uw6oGPYsNj5tQ==
X-ME-Sender: <xms:ECQcYIWopiH3tGPwk5A0FP01SzDB3nOVlkxNRFuHlrVmMKryTqpjjg> <xme:ECQcYMla7wenqVTExC8aPnzOM8mx5af8S6MXcnQaYH0dOu-yDvmNwBLIK-GJCfBE8 93eS7dSi0KVcg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeeggdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeeiudelhfejhfeuheelgfeuteevhfdtffehteejfffgudffteevudetvdeu udduteenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:ECQcYMaVJmPNSi6d5cZFR6ZA8ng9XYYMC4HJg3Hfvwrtp4sFZSIHzQ> <xmx:ECQcYHUVae329hQiJ98Aq861EPbXrnLMcGr3tvvmFWy5Nq0A4LizHQ> <xmx:ECQcYCkFJfngy5hPHjQrqhONi8GmEUggVjYTKctrT23T3BKAbEgV8w> <xmx:ESQcYMS9DhWKC1-Mq1eqMobdF9Zaf_cg19tRt73YFrNGNCsOrqkZHA>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 473CD1080059; Thu,  4 Feb 2021 11:42:56 -0500 (EST)
To: extra@ietf.org
References: <160699437898.22145.8147510604103584689@ietfa.amsl.com>
Cc: Bron Gondwana <brong@fastmailteam.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <ed6a82f4-3c75-b914-3d23-80764f0a2e83@fastmail.com>
Date: Thu, 4 Feb 2021 11:42:55 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160699437898.22145.8147510604103584689@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/eOpJePsuJrRrNQBFyIkjSGzRWeM>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-mailboxid-06.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 16:43:00 -0000

I just noticed that the draft use :special-use as the tagged argument, 
but per RFC 8579, it is :specialuse.


On 12/3/20 6:19 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
>
>          Title           : Sieve Email Filtering: delivery by mailboxid
>          Author          : Bron Gondwana
> 	Filename        : draft-ietf-extra-sieve-mailboxid-06.txt
> 	Pages           : 10
> 	Date            : 2020-12-03
>
> Abstract:
>     The OBJECTID capability of the IMAP protocol (RFC8474) allows clients
>     to identify mailboxes by a unique identifier which survives rename.
>
>     This document extends the Sieve mail filtering language (RFC5228) to
>     allow using that same unique identifier as a target for fileinto
>     rules, and for testing the existance of mailboxes.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-extra-sieve-mailboxid-06.html
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-mailboxid-06
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Thu Feb  4 09:02:29 2021
Return-Path: <alissa@cooperw.in>
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 1EB563A1685; Thu,  4 Feb 2021 09:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=pa9aAQyi; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=C/FZOGum
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 7EWHLkLo2w1M; Thu,  4 Feb 2021 09:02:26 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4775D3A166C; Thu,  4 Feb 2021 09:02:26 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 2C6C1D0F; Thu,  4 Feb 2021 12:02:25 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 04 Feb 2021 12:02:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=Q 4YyOFG+ky0jBnl+PXhzIxr6tfconoIJ0tC1hXjwzrg=; b=pa9aAQyie11AZRrRC V9jw2vUxE36Hg/2DKpq/ror67xK1ePHSS5O6F43MgboONzT5UisiAISK67vB1p74 skYg1TqHKaiONQ3hZW93rH8sbc9rytrbUxaAoMznHXNpIanpcWvIYyI14GrjFWcC 40wPbvI3Yzk1ms6GsZwu2ayqOxEKYPXC7MvZa1PmwGYoYy5Txdw5q+AfMpO7nfZL 2M/l4iKqDWST/krtR6dy+mC1GEuK8fytVsnjMv0fBJDH1BkZCFaVHix07X55UL4Z +un4CzXacBxd45kxCJ8MQLbP0ebt5c20MCqdad8Ml1ZVMVudoJN2vkxxAi3i3lzY 6jKDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Q4YyOFG+ky0jBnl+PXhzIxr6tfconoIJ0tC1hXjwz rg=; b=C/FZOGumtfMxUC6L4owlVrJyAowCydHBr+ScIaM6jj9LaC2eE/WK/csJh YIz/a4J7Zk5HhLpczKeizvMJylpNIGehw8uWWAqqRjr+yWV5CjU/suKRxRucubng 22N/MbvfR+S6BSAt5D8rC2HyCsK5E0hMh1pw7xCANgZuvaysgJeNGW39tHSZDVGz 58EXGY5qV+7aiZOFRQBnGHyyO54371oGmU8W39hHft7gp34lVUQUgfSDyq/K8MyK 7xjSRhII8Z1SNXfwG2F+cauTaWnsip6OgYR4U2DZ/g+XKr/IoTvfmNnpMxQvXdDg yfxb43oVSFjbbWT2/J7uxheX+qXrA==
X-ME-Sender: <xms:oCgcYKRxs2CvG-kOIB6z-4bwx1RrBoosCJaUKpKJfxVkLYbFIAnQ4w> <xme:oCgcYFdJyRRQpPeqqW6FpCebzWyMFeajIM7D_87E7CBs6NSWSe9MfcmQz9sIVFb8q Vdork3WD96fJ0_C2g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeeggdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhephfeiueffjeevteeijeehhfdtgfejieefgfeggefhfeejvdehleevvdfgfeff lefgnecukfhppedujeefrdefkedruddujedrjedunecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:oCgcYJB2JQWxElBUWPm_SAX_J0R-_LuH473b_8xvsigDFHRzPoi6VQ> <xmx:oCgcYD0VuU2Y4-efxX2dOSI4qRCTqUvTyrnqbKRlDP6f6zS4GVeTDA> <xmx:oCgcYJQe-p0U8esvnpqZXljGF5FEllHHMxoSAETfardnwN_VwvtpRg> <xmx:oCgcYAP4VLJekoqaHBKWxluuq1QMunZxwZxF1NQmMGV-4R3rWs2K0g>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.71]) by mail.messagingengine.com (Postfix) with ESMTPA id E94BB108005B; Thu,  4 Feb 2021 12:02:23 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CALaySJLNnD0gJyjsMjQODC_vKLFQPJMf_oBnfp_hS2nrSD+2Tg@mail.gmail.com>
Date: Thu, 4 Feb 2021 12:02:23 -0500
Cc: IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <470EB1D6-0D84-4DC2-A483-56F9B9C76DA3@cooperw.in>
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com> <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in> <CALaySJLNnD0gJyjsMjQODC_vKLFQPJMf_oBnfp_hS2nrSD+2Tg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/i1UcHAlakiVVEVZoS9ypzMU2kT8>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 17:02:28 -0000

> On Feb 4, 2021, at 10:32 AM, Barry Leiba <barryleiba@computer.org> =
wrote:
>=20
>>> That said, there are two things:
>>>=20
>>> 1. As Alexey has pointed out with other comments, changing these =
often
>>> involves carefully checking literal lengths, RFC822-SIZE values, and
>>> other such, and has a high potential to introduce errors.
>>>=20
>>> 2. I have some thought toward keeping Mark's voice in here, and that
>>> mostly shows up in the examples.  Part of me would rather not scrub =
it
>>> out.
>>=20
>> The point of raising it in the first place was about perpetuating the =
biases of the earlier documents/authors.
>> The base RFCs will remain in the archive for people to read.
>=20
> Yes, true, and that takes care of point 2.  You're right.
>=20
> Do you think it's worth the risk of introducing errors (point 1)?

I=E2=80=99m not sure I understand it well enough. If you substitute =
values that are the same length in characters as the old values, is this =
still a problem? I.e., if you padded examples with numbers =
("example123456=E2=80=9D) or something along those lines, does that =
help?

Thanks,
Alissa

>=20
> Barry


From nobody Thu Feb  4 09:03:18 2021
Return-Path: <murch@fastmail.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 046A23A1685 for <extra@ietfa.amsl.com>; Thu,  4 Feb 2021 09:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=BVvGrPNG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dPB0jtZh
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 TvIZtwb_ySUX for <extra@ietfa.amsl.com>; Thu,  4 Feb 2021 09:03:14 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB8BA3A1684 for <extra@ietf.org>; Thu,  4 Feb 2021 09:03:14 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DEBC65C0233 for <extra@ietf.org>; Thu,  4 Feb 2021 12:03:13 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 04 Feb 2021 12:03:13 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=x +ZoAiLFG6l+A4ZBn69gzaVjt+gN8nmDCMZA6qULm+w=; b=BVvGrPNGUZZTlJZgO duARxeBfs0wekkcBv3IQcZFIa05Io+dR9FK1xXYOtUi+KMnQ3LNSl7drxy/6FrHM igANtZSXzp+cZgKKIsZ7MiAMLLamrLH3J2bFTv2J8Y4+QU/IFla75+Q0A1r6CI42 r6frUAibRPPVWaLtZFpJi0lMecDRLR/II5aeDqzLSX0X/K+6ONr9Mi8mroUSOx96 i+XWD+7H/EFlaMbZpEWabu6xAi/h2uSD60xCsCKqRQpakHER1WwRNcOtRL4N2Kb0 0uwK22OR/KuT1bRDfiK07ey5yWZJ4+uH3G8lzF7JclSA/3HedacqPOvmg3lLxakO ova8Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=x+ZoAiLFG6l+A4ZBn69gzaVjt+gN8nmDCMZA6qULm +w=; b=dPB0jtZhGZYbONfYVO259T5rjiidF+n+fev/NyNtSfQWdlwDydzX1u1k6 0Qw/7M5W7VW91LNSTNOsn+jGe3rMhftPtnmqZWbPYNnSiTp6XHnLAf04QqrOLbPO TUmwGYn6BPIA+98rGhzI99ZrF0XlVCNDjYuIjYT963vqGgmW8XhPtgOeil5/PSnm Vfp21E8uBc35T9vucUfd5m7DccJcCs+TDxUr/ah4AzKMWiyipVsJs01697fUf8Av NYx7frVDzIqPtQsxSWyhiHjXm6/cdnGHa+hoJKq20Ila9w7ojnl/UekV+ty0cS9B kwKFp/NfTG8skM5kp4mzKiaSILuDA==
X-ME-Sender: <xms:0SgcYCf9PXVMse5EiqLlbSzlF4Rq28SKEeCOhD5Hnglw55cWqp3oSA> <xme:0SgcYEbkO5HqE4Aw0Gcbn3IDA3RzlNpcEefw-VLm42casV0ZHvQ6ZWxRJyTvQS5Pp 8NVpR_Mb2k15g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeeggdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvnhcuofhurhgthhhishhonhcuoehmuhhrtghhsehfrghs thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepvdeutedugeeiffeitedvhfeiud etvdegjeekkedutedvvddvudetjeevgffhvdeknecuffhomhgrihhnpehivghtfhdrohhr ghenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:0SgcYPHXmVNlk66QFi15SjcKyjWkM3lKlyXWCL48MTePgvWbHLLEVA> <xmx:0SgcYKn9J0MAGmOBW07NscM7NIJB__BoyXqXDuiCAOTJ6borHrNdow> <xmx:0SgcYKcaB-NejXOjjMhKsqWFECkyhco1ZYS03Z7IDwdSzOFhUVeqvQ> <xmx:0SgcYLeZTOU-A_4ykn7XegV0KxqZkx0bWwr5TLET8GzDKO6HaECUTA>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 207E71080067 for <extra@ietf.org>; Thu,  4 Feb 2021 12:03:13 -0500 (EST)
To: extra@ietf.org
References: <159705787314.11834.3190103463887221194@ietfa.amsl.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <4649502f-077d-4ebe-b599-92f727f17ccd@fastmail.com>
Date: Thu, 4 Feb 2021 12:03:12 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <159705787314.11834.3190103463887221194@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/8L9uaK-yJg_MtFCjkvQqbR76Q8I>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-snooze-00.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 17:03:17 -0000

I'm updating this draft per our discussions at IETF 109.Â  I want to 
confirm that we decided on the following:

- Register the \Snoozed IMAP Special-Use Attribute

- Specify that the ONLY way to implement snooze is via a \Snoozed 
mailbox.Â  Or did we want to just eliminate SMTP Future Delivery and 
require that the message be stored in a special mailbox (IMAP or 
otherwise) until its awakened?


On 8/10/20 7:11 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
>
>          Title           : Sieve Email Filtering: Snooze Extension
>          Authors         : Kenneth Murchison
>                            Ricardo Signes
>                            Neil Jenkins
> 	Filename        : draft-ietf-extra-sieve-snooze-00.txt
> 	Pages           : 12
> 	Date            : 2020-08-07
>
> Abstract:
>     This document describes the "snooze" extension to the Sieve email
>     filtering language.  The "snooze" extension gives Sieve the ability
>     to postpone the filing of an incoming into a target mailbox until a
>     later point in time.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-snooze/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-sieve-snooze-00
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-sieve-snooze-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>


From nobody Thu Feb  4 09:24:30 2021
Return-Path: <kaduk@mit.edu>
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 158A43A16A7; Thu,  4 Feb 2021 09:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 IhL3A0q1By0B; Thu,  4 Feb 2021 09:24:23 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 729DA3A16A6; Thu,  4 Feb 2021 09:24:22 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 114HOC0S030861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 4 Feb 2021 12:24:17 -0500
Date: Thu, 4 Feb 2021 09:24:11 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Message-ID: <20210204172411.GC21@kduck.mit.edu>
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com> <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ylEX6PCuH_Y_FZ0kk3jIfRNpTog>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 17:24:25 -0000

Hi Barry,

On Thu, Feb 04, 2021 at 09:33:13AM -0500, Barry Leiba wrote:
> Thanks, Ben, for the usual good comments.  Just responses on a couple here:
> 
> > Section 2.2.1
> >
> >       response, and reads another response from the server.  In all
> >       cases, the client MUST send a complete command (including
> >       receiving all command continuation request responses and command
> >       continuations for the command) before initiating a new command.
> >
> > To check my understanding: the "command continuations for the command"
> > are things that the client sends, right?  Adding a word or two might
> > help clarify.
> 
> Yes, it should say "and sending command continuations"; the word
> "sending" is missing.
> 
> > Section 2.3.1.1
> >
> >                                          A good UIDVALIDITY value to use
> >    is a 32-bit representation of the current date/time when the value is
> >    assigned: this ensures that the value is unique and always increases.
> >    Another possible alternative is a global counter that gets
> >    incremented every time a mailbox is created.
> >
> > In light of the discussion in draft-gont-numeric-ids-sec-considerations,
> > I wonder if these are truly the most recommended options, as either
> > option has potential to leak some information about rate or time of
> > mailbox creation.  Leaking the time of mailbox creation to the user who
> > created it is, of course, not an issue, but not all IMAP mailboxes are
> > single-user-access.  A 32-bit PRP (e.g., block cipher) applied to either
> > option would provide some level of obfuscation while preserving the
> > uniqueness properties.
> 
> It would obfuscate and preserve uniqueness, but it would not preserve
> the monotonicity: a new UIDVALIDITY must always be greater than the
> previous ones.  Do you have a good suggestion for that, which still
> takes care of the privacy leak?

Oops, I missed the one line about UIDVALIDITY also needing to be monotonic
(written out as "unique identifier validity" it is easy to skip over the
"validity" word and just think read it as a UID).  No immediate
suggestions, then, though as the follow-up from Timo notes, it's unclear
what value the monotonicity of UIDVALIDITY adds -- the semantics seem to
just be "exact match required" for everything I noticed.

> > Section 2.3.2
> >
> >    $Junk  The user (or a delivery agent on behalf of the user) may
> >       choose to mark a message as definitely containing junk ($Junk; see
> >       also the related keyword $NotJunk).  The $Junk keyword can be used
> >       to mark (and potentially move/delete messages later), group or
> >       hide undesirable messages.  See [IMAP-KEYWORDS-REG] for more
> >       information.
> >
> > I'm not entirely sure what additional information I'm supposed to get
> > from [IMAP-KEYWORDS-REG]; the registry page is fairly short on
> > commentary.  (Applies throughout.)
> 
> It's meant to send you to the reference doc, but, yes, the reader
> already has that anyway.  It might simply be better to say that the
> registration is recorded in IMAP-KEYWORDS-REG.

Okay.

> > Section 6.4.8
> >
> >    Because of the similarity of MOVE to COPY, extensions that affect
> >    COPY affect MOVE in the same way.  Response codes listed in
> >    Section 7.1, as well as those defined by extensions, are sent as
> >    appropriate.
> >
> > Who decides what is "appropriate"?  Will everyone come to the same
> > conclusion?
> 
> It means that the same responses are sent for MOVE as for COPY, under
> the corresponding conditions.  Yes, we'd expect that to be evident.
> We can try rephrasing it if you think that's unclear.  Is what I said
> two sentences ago clearer?  Do you have other suggestions?

Maybe "as indicated for COPY" (assuming I correctly remembered the context
about which way the analogy is going).

Thanks,

Ben


From nobody Thu Feb  4 09:38:27 2021
Return-Path: <barryleiba@gmail.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 9E2813A0C23; Thu,  4 Feb 2021 09:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 5Zru2fdxsrfs; Thu,  4 Feb 2021 09:38:21 -0800 (PST)
Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DC3A3A0BED; Thu,  4 Feb 2021 09:38:21 -0800 (PST)
Received: by mail-lj1-f181.google.com with SMTP id e18so4361379lja.12; Thu, 04 Feb 2021 09:38:21 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=GQMsmmbqWosChudZxnX6nxB2cYy1Wp5xU44MBiee2P8=; b=ki/IaX1sJlwxjuegoy3fryxOyAEAnkDzewO9up/PtCjfK3TUxRieicDtSqfHU61oKo fySVUD/KjK5nFEecSTBRmy+iqoRcl8YOwa1fvKwt/r3v5HFKDNGyENiLfsrlZrWGBV+Z b7IrKRN5DY7A7lvg/RzMR9irdiDdlQrYxChQe4kCdKSuGViG/jucPaNhEpeMEk2tNNoo XOEH/LQgqGdj9M+2lBPM/6YBNXLRISzSj/6VwebKKtmKE1hScif59tM9RDlnY6HfVExz RrZqnJGt3puZHxm+LpS1C9qq8JKO7E4WFlz5di4v6pcq+VOggZ6Zipjsl6ZqDdjJB+IE 9izA==
X-Gm-Message-State: AOAM5312v91kP8Vib1DOizhbqaWA/lG+bsq1HCQLWnLsy7uUyzrAR4Iy FLc7RK0mrneFRk+DmfaWKspLdfbbCP7wRmD08Bo=
X-Google-Smtp-Source: ABdhPJz39Xeck0DoUkQ7URa6p4MNGDG6nSaOnO21JtdKypOR5bW+rkBi+PaMUcR/eID22WgogbVdB/ZxkoMj7xTCqRY=
X-Received: by 2002:a2e:959a:: with SMTP id w26mr261748ljh.113.1612460299130;  Thu, 04 Feb 2021 09:38:19 -0800 (PST)
MIME-Version: 1.0
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com> <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in> <CALaySJLNnD0gJyjsMjQODC_vKLFQPJMf_oBnfp_hS2nrSD+2Tg@mail.gmail.com> <470EB1D6-0D84-4DC2-A483-56F9B9C76DA3@cooperw.in>
In-Reply-To: <470EB1D6-0D84-4DC2-A483-56F9B9C76DA3@cooperw.in>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 4 Feb 2021 12:38:06 -0500
Message-ID: <CALaySJKms8fXb=skNfXNCVf1o0uwaQZ10Aj1a+sdyZuN4-eV_Q@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org,  extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/3Y6jzbs3YTmI577LmAvQST2Q-ZA>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 17:38:23 -0000

> > Do you think it's worth the risk of introducing errors (point 1)?
>
> I=E2=80=99m not sure I understand it well enough. If you substitute value=
s that are the same length in
> characters as the old values, is this still a problem? I.e., if you padde=
d examples with numbers
> ("example123456=E2=80=9D) or something along those lines, does that help?

That sounds workable; I don't think we have any digital signatures,
which would still break, but I don't think we need to worry about
that.  Let me talk it over with Alexey.

Thanks, Alissa.

Barry


From nobody Sun Feb  7 20:30:56 2021
Return-Path: <brong@fastmailteam.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 6F80C3A1070; Sun,  7 Feb 2021 20:30:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=goCQ57Qn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=bLJf4Ygk
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 TGz7VADma9qW; Sun,  7 Feb 2021 20:30:48 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 378DE3A1071; Sun,  7 Feb 2021 20:30:48 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 938065C00FB; Sun,  7 Feb 2021 23:30:45 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 07 Feb 2021 23:30:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=g+wO 62/oP6Fx9sg2YANE/G6cVAVgA9MptukvlUyuV1E=; b=goCQ57Qnp8/YGJXQBkpE GKe2lJ0WYtDHaJTKwfghTHjsFqQrjQsbTYMWeSEM+4GAKdYKhSSerux5LhV3qKT9 5EyTsi2+68KLL1k6mitxLj0kIEdzgMGsGqhoEFVl4F7sV47gbO59tFaYT0Yc4U5A eIEDU/KYEHfIvcocNdzSn6/wqvkqaIviwawoJ7Te/8GDgOHq5ad9PqJ6MhvdGXNO nCj9n8/YRc69v3RLb7exKCOZhfPS/M/qliumA2rinrNKDD0HhBZ8AWfQCb+qvc1Q bOGb6IMaH/44xFaUmnZ/w8DgTLEDdgicY6GVOaGeQdiFx0E9YneKFV0rhMR6dWTp yA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=g+wO62 /oP6Fx9sg2YANE/G6cVAVgA9MptukvlUyuV1E=; b=bLJf4Ygk9cXe3X4joLt/U2 9f4+CKIr3XwHLFwnRUy5d7YEX/k41YXtt6T26TMzuQohYRPLfm9EZfRDw0LQ2wlZ 9O1BMmVYILhk9Jzb6/rjzSCZ1OqTwjNyPMAP2hFxcBhpZZafkIFlv5vMO76OxeD/ 4N5cpB4Md5dBjVLlS+zd/ZwmdhYau1hWsKkfGboY6ad/R06lC7uxWiVQ2bYyzF2v ZfsDxWimvzgAUzN+0HL16sN3N01t1X1v/eE+xDpPhaDxS50pdLOKNH5s4TmAenfm xC/bqctHGizblI4kbrI8ZuL7MLqVSrBQGHjw7sUxXo6WjV/5Krubjaa9c8OJZ8mA ==
X-ME-Sender: <xms:dL4gYKCYvCPpPX2H4UDtgcJ4QOkacmwE79iymUPyXpFQQ4Ox3lZNKA> <xme:dL4gYEjY4mNr9soniUeiVRvwTrn8WDUBi605RO28bUvwc5-TvpdFaBi5URqBOGxDq LiIVsn9HPc>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrhedvgdejtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeffvdekfeegleeiueettddtffehveevffefkeduvddttdek iefgjeduvdfhvdduleenucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:dL4gYNkepx-dDAUdyizWdweXWASX1ZOZgWhYFahokrCn-NlSCfmwmA> <xmx:dL4gYIyEzoIZg9WgG2RYKX3kHEE1FFdp_sMuatsRlY8HhSbU9j5lAA> <xmx:dL4gYPT7VxK7Q7bfh3bKrrurb25jZhsoMyPyLWguS0Dhfz51kRQlJQ> <xmx:db4gYJdxSnRMLf6YPLXZvtGEqcJnKOv2ZjojIjk1_d6eFPQTC_NDlA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E32A236005C; Sun,  7 Feb 2021 23:30:43 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048
Mime-Version: 1.0
Message-Id: <26c6cdb3-d697-4bb5-9748-bf75c4ad109e@beta.fastmail.com>
In-Reply-To: <160804212198.17646.8123862646316973469@ietfa.amsl.com>
References: <160804212198.17646.8123862646316973469@ietfa.amsl.com>
Date: Mon, 08 Feb 2021 15:30:23 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-sieve-mailboxid@ietf.org, extra-chairs@ietf.org, extra@ietf.org, "Jiankang Yao" <yaojk@cnnic.cn>
Content-Type: multipart/alternative; boundary=509ca42c9a574eefa01d74b11eade0a5
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/VzjjSrsngkUAExhbvYkWM6Pp-MM>
Subject: Re: [Extra]  =?utf-8?q?Magnus_Westerlund=27s_Discuss_on_draft-ietf-ex?= =?utf-8?q?tra-sieve-mailboxid-06=3A_=28with_DISCUSS=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2021 04:30:51 -0000

--509ca42c9a574eefa01d74b11eade0a5
Content-Type: text/plain

On Wed, Dec 16, 2020, at 01:22, Magnus Westerlund via Datatracker wrote:
> Magnus Westerlund has entered the following ballot position for
> draft-ietf-extra-sieve-mailboxid-06: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/
> 

Hi Magnus,

Sorry for the lack of response on this - I missed it somehow at the time!

> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> First part is a formality discuss that likely is fairly easy to resolve
> 
> So this document uses formal syntax, however it does not explicitly reference
> which. So I noticed RFC 5228 that do reference RFC 4234 which is now obsolete,
> and the current in force version of ABNF is RFC 5234. Also as no WSP are
> included in the rules, this document appears to use ABNF to express RFC 5228
> grammar and not parsing syntax. So please clarify prior to the usages what the
> formal language is and what it represents.
> 
> So this needs to be done prior to Section 5. But, can you please check that you
> actually have the same level of  formal syntax in Section 5 that goes through
> RFC 8580 as what is in Section 8. Otherwise please clarify both.

I'm happy to drop the formal language section entirely.  I just checked RFC8579 which describes a very similar extension and it has no formal ABNF section.  Would you be satisfied with having the ABNF dropped entirely and using prose and descriptions similar to what's in RFC8579?

> Secondly, I do consider the defining text first paragraph of in Section 4.1 so
> hard to interpret that it must be fixed prior to publication. So although you
> already are going to address it based on discussion of Martin Duke's comment, I
> want to hold a discuss on this.

I will wordsmith that and post a new draft.

Thanks,

Bron.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--509ca42c9a574eefa01d74b11eade0a5
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">On Wed, Dec 16, 2020, at 01:22, Magnus Westerlund via Data=
tracker wrote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><=
div style=3D"font-family:Arial;">Magnus Westerlund has entered the follo=
wing ballot position for<br></div><div style=3D"font-family:Arial;">draf=
t-ietf-extra-sieve-mailboxid-06: Discuss<br></div><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;">When responding,=
 please keep the subject line intact and reply to all<br></div><div styl=
e=3D"font-family:Arial;">email addresses included in the To and CC lines=
. (Feel free to cut this<br></div><div style=3D"font-family:Arial;">intr=
oductory paragraph, however.)<br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fon=
t-family:Arial;">Please refer to&nbsp;<a href=3D"https://www.ietf.org/ie=
sg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/=
discuss-criteria.html</a><br></div><div style=3D"font-family:Arial;">for=
 more information about IESG DISCUSS and COMMENT positions.<br></div><di=
v style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial=
;"><br></div><div style=3D"font-family:Arial;">The document, along with =
other ballot positions, can be found here:<br></div><div style=3D"font-f=
amily:Arial;"><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-ext=
ra-sieve-mailboxid/">https://datatracker.ietf.org/doc/draft-ietf-extra-s=
ieve-mailboxid/</a><br></div><div style=3D"font-family:Arial;"><br></div=
></blockquote><div style=3D"font-family:Arial;"><br></div><div style=3D"=
font-family:Arial;">Hi Magnus,<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">Sorry for the lack of resp=
onse on this - I missed it somehow at the time!<br></div><div style=3D"f=
ont-family:Arial;"><br></div><blockquote type=3D"cite" id=3D"qt" style=3D=
""><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family=
:Arial;">---------------------------------------------------------------=
-------<br></div><div style=3D"font-family:Arial;">DISCUSS:<br></div><di=
v style=3D"font-family:Arial;">-----------------------------------------=
-----------------------------<br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;">First part is a formality d=
iscuss that likely is fairly easy to resolve<br></div><div style=3D"font=
-family:Arial;"><br></div><div style=3D"font-family:Arial;">So this docu=
ment uses formal syntax, however it does not explicitly reference<br></d=
iv><div style=3D"font-family:Arial;">which. So I noticed RFC 5228 that d=
o reference RFC 4234 which is now obsolete,<br></div><div style=3D"font-=
family:Arial;">and the current in force version of ABNF is RFC 5234. Als=
o as no WSP are<br></div><div style=3D"font-family:Arial;">included in t=
he rules, this document appears to use ABNF to express RFC 5228<br></div=
><div style=3D"font-family:Arial;">grammar and not parsing syntax. So pl=
ease clarify prior to the usages what the<br></div><div style=3D"font-fa=
mily:Arial;">formal language is and what it represents.<br></div><div st=
yle=3D"font-family:Arial;"><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">So this needs to be done prior to Secti=
on 5. But, can you please check that you<br></div><div style=3D"font-fam=
ily:Arial;">actually have the same level of&nbsp; formal syntax in Secti=
on 5 that goes through<br></div><div style=3D"font-family:Arial;">RFC 85=
80 as what is in Section 8. Otherwise please clarify both.<br></div></di=
v></blockquote><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">I'm happy to drop the formal language section entir=
ely.&nbsp; I just checked RFC8579 which describes a very similar extensi=
on and it has no formal ABNF section.&nbsp; Would you be satisfied with =
having the ABNF dropped entirely and using prose and descriptions simila=
r to what's in RFC8579?<br></div><div style=3D"font-family:Arial;"><br><=
/div><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-f=
amily:Arial;">Secondly, I do consider the defining text first paragraph =
of in Section 4.1 so<br></div><div style=3D"font-family:Arial;">hard to =
interpret that it must be fixed prior to publication. So although you<br=
></div><div style=3D"font-family:Arial;">already are going to address it=
 based on discussion of Martin Duke's comment, I<br></div><div style=3D"=
font-family:Arial;">want to hold a discuss on this.<br></div></blockquot=
e><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:=
Arial;">I will wordsmith that and post a new draft.<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Thanks,=
<br></div><div style=3D"font-family:Arial;"><br>Bron.<br></div><div styl=
e=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"><div class=3D=
"signature">--<br></div><div class=3D"signature">&nbsp; Bron Gondwana, C=
EO, Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; brong@fast=
mailteam.com<br></div><div class=3D"signature"><br></div></div><div styl=
e=3D"font-family:Arial;"><br></div></body></html>
--509ca42c9a574eefa01d74b11eade0a5--


From nobody Sun Feb  7 20:59:54 2021
Return-Path: <brong@fastmailteam.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 757223A10C1 for <extra@ietfa.amsl.com>; Sun,  7 Feb 2021 20:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=C4ZhIRgB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Io3VhclQ
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 f3ChFWdKW2bO for <extra@ietfa.amsl.com>; Sun,  7 Feb 2021 20:59:51 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7F6B3A10C0 for <extra@ietf.org>; Sun,  7 Feb 2021 20:59:51 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id C5CAC5C01E3 for <extra@ietf.org>; Sun,  7 Feb 2021 23:59:50 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 07 Feb 2021 23:59:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=fYb1vxN qEx+kWXN6JrpEaK1HOKPcUV7+zxvnNJAZmmE=; b=C4ZhIRgBoh8Ue7/l4aCDkP5 2K53EbE6tPD7hvYLAH47eq0FqrITWuDi+DmNGMeH4pAD6CiNrF1aA0AstPFyzcV4 DbJ9TndkZPmQVUdK2/4vLTmcHPwpMCktBugcHldL3sg4QjCTnwsc6xPqTwYj/+oG Qvd00At8gl0U0LkoeH4qmHj1i1xQQvTNWHd6z9bw+3qz0m65aj5ojnHaksj0VZho HzgDAP0VJeYEsd7RIOenjl1tv0iVC9yOB9kSGlzhEWf5cvwsYFz0MNb+i7Tr+Dxc wLJV2iJ9PVWjnGiYEAuDBSshxCPIpWvYuOHhEXjjmQE/DphGLR6iRc/Pn6wkrng= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=fYb1vx NqEx+kWXN6JrpEaK1HOKPcUV7+zxvnNJAZmmE=; b=Io3VhclQoafENhNSIIIm9F mjtxGikTaRbVcvicvOZ2/FUTQvP4lgE88YbqmJsYYFlWO8lHU917PsRYMSLM4LPq Olj/fjH/UC2kxnVf2eH+HdWRxRyC47PQUmbCvrGDlQ+JoYg6lrvHbePiIaQbRt/o uOlnXv/RCE2ckJnnASbsaDzY3UJLkGHJvVLXyYh0Azvnnk//cAwTQmOm4jnNUZX4 dheaumpsk9xiFsSxhheoTTADifGkYyOn26+nU/rFM3HhMmOZcCcfTUs355SSoUq4 gzluaLDdkgeDp49JrDf1Uc5C45QSAAEllFHaquVYMHTzcLprESmzpJ5ikwbN1p+w ==
X-ME-Sender: <xms:RsUgYLXvdIyyHnhuX3Y1lWsPRebStCUO_jgtr-y804kAvyf5e2Vjyw> <xme:RsUgYDnK-BWSxtjsyoDzJgzDmc_AuJlLTMfJ5g0_wPPYjg0WbbaVRJ43dvhmDrLiH NtLXYJOy54>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrhedvgdejiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepffevfeeigfejve etheehleegteelteevgeeutdfhhefghfdtjefhvdehhfdtkefgnecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:RsUgYHaoibJ81A-DMQZIn9RfG4EUEqwym_OMDaAdihr1b3cCkavwDQ> <xmx:RsUgYGUqopemkS5Ye_c_T1qwKO-CxC9NhdTgdloChstum9zuwIJu-Q> <xmx:RsUgYFmPgilOA30pCzB_ZNrs-fX69X8uaRW_oq68gSmI9_F2rl1pVA> <xmx:RsUgYBy8bVjS-zxP5xUTkQGQprPSZ2AzKRH9-L4h-Yi18SZAqDKxmA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4F52936005C; Sun,  7 Feb 2021 23:59:50 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048
Mime-Version: 1.0
Message-Id: <7f4641a1-10b5-4713-a516-0cf7202f2427@beta.fastmail.com>
In-Reply-To: <ed6a82f4-3c75-b914-3d23-80764f0a2e83@fastmail.com>
References: <160699437898.22145.8147510604103584689@ietfa.amsl.com> <ed6a82f4-3c75-b914-3d23-80764f0a2e83@fastmail.com>
Date: Mon, 08 Feb 2021 15:59:30 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary=862db2fc303f494abce90f0864a80278
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/jQutCiWQOnvp4gv2Za2-fDMrFgE>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-mailboxid-06.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2021 04:59:53 -0000

--862db2fc303f494abce90f0864a80278
Content-Type: text/plain

Thanks Ken - I have addressed this in -07.

Cheers,

Bron.

On Fri, Feb 5, 2021, at 03:42, Ken Murchison wrote:
> I just noticed that the draft use :special-use as the tagged argument, 
> but per RFC 8579, it is :specialuse.
> 
> 
> On 12/3/20 6:19 AM, internet-drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
> >
> >          Title           : Sieve Email Filtering: delivery by mailboxid
> >          Author          : Bron Gondwana
> > Filename        : draft-ietf-extra-sieve-mailboxid-06.txt
> > Pages           : 10
> > Date            : 2020-12-03
> >
> > Abstract:
> >     The OBJECTID capability of the IMAP protocol (RFC8474) allows clients
> >     to identify mailboxes by a unique identifier which survives rename.
> >
> >     This document extends the Sieve mail filtering language (RFC5228) to
> >     allow using that same unique identifier as a target for fileinto
> >     rules, and for testing the existance of mailboxes.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-extra-sieve-mailboxid-06.html
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-mailboxid-06
> >
> >
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> -- 
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--862db2fc303f494abce90f0864a80278
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Thanks Ken - I have addressed this in -07.<br></div><div s=
tyle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">=
Cheers,<br></div><div style=3D"font-family:Arial;"><br>Bron.<br></div><d=
iv style=3D"font-family:Arial;"><br></div><div>On Fri, Feb 5, 2021, at 0=
3:42, Ken Murchison wrote:<br></div><blockquote type=3D"cite" id=3D"qt" =
style=3D""><div style=3D"font-family:Arial;">I just noticed that the dra=
ft use :special-use as the tagged argument,&nbsp;<br></div><div style=3D=
"font-family:Arial;">but per RFC 8579, it is :specialuse.<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;">On 12/3/20 6:19 AM,&nbsp;<a=
 href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> w=
rote:<br></div><div style=3D"font-family:Arial;">&gt; A New Internet-Dra=
ft is available from the on-line Internet-Drafts directories.<br></div><=
div style=3D"font-family:Arial;">&gt; This draft is a work item of the E=
mail mailstore and eXtensions To Revise or Amend WG of the IETF.<br></di=
v><div style=3D"font-family:Arial;">&gt;<br></div><div style=3D"font-fam=
ily:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; T=
itle&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Sieve=
 Email Filtering: delivery by mailboxid<br></div><div style=3D"font-fami=
ly:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Au=
thor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Bron Gondwa=
na<br></div><div style=3D"font-family:Arial;">&gt; 	Filename&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-extra-sieve-mailboxid-06.txt=
<br></div><div style=3D"font-family:Arial;">&gt; 	Pages&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 10<br></div><div style=3D"=
font-family:Arial;">&gt; 	Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; : 2020-12-03<br></div><div style=3D"font-family=
:Arial;">&gt;<br></div><div style=3D"font-family:Arial;">&gt; Abstract:<=
br></div><div style=3D"font-family:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
The OBJECTID capability of the IMAP protocol (RFC8474) allows clients<br=
></div><div style=3D"font-family:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp; to=
 identify mailboxes by a unique identifier which survives rename.<br></d=
iv><div style=3D"font-family:Arial;">&gt;<br></div><div style=3D"font-fa=
mily:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp; This document extends the Siev=
e mail filtering language (RFC5228) to<br></div><div style=3D"font-famil=
y:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp; allow using that same unique iden=
tifier as a target for fileinto<br></div><div style=3D"font-family:Arial=
;">&gt;&nbsp;&nbsp;&nbsp;&nbsp; rules, and for testing the existance of =
mailboxes.<br></div><div style=3D"font-family:Arial;">&gt;<br></div><div=
 style=3D"font-family:Arial;">&gt;<br></div><div style=3D"font-family:Ar=
ial;">&gt; The IETF datatracker status page for this draft is:<br></div>=
<div style=3D"font-family:Arial;">&gt;&nbsp;<a href=3D"https://datatrack=
er.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/">https://datatracker.i=
etf.org/doc/draft-ietf-extra-sieve-mailboxid/</a><br></div><div style=3D=
"font-family:Arial;">&gt;<br></div><div style=3D"font-family:Arial;">&gt=
; There is also an HTML version available at:<br></div><div style=3D"fon=
t-family:Arial;">&gt;&nbsp;<a href=3D"https://www.ietf.org/archive/id/dr=
aft-ietf-extra-sieve-mailboxid-06.html">https://www.ietf.org/archive/id/=
draft-ietf-extra-sieve-mailboxid-06.html</a><br></div><div style=3D"font=
-family:Arial;">&gt;<br></div><div style=3D"font-family:Arial;">&gt; A d=
iff from the previous version is available at:<br></div><div style=3D"fo=
nt-family:Arial;">&gt;&nbsp;<a href=3D"https://www.ietf.org/rfcdiff?url2=
=3Ddraft-ietf-extra-sieve-mailboxid-06">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-extra-sieve-mailboxid-06</a><br></div><div style=3D"font-=
family:Arial;">&gt;<br></div><div style=3D"font-family:Arial;">&gt;<br><=
/div><div style=3D"font-family:Arial;">&gt; Please note that it may take=
 a couple of minutes from the time of submission<br></div><div style=3D"=
font-family:Arial;">&gt; until the htmlized version and diff are availab=
le at tools.ietf.org.<br></div><div style=3D"font-family:Arial;">&gt;<br=
></div><div style=3D"font-family:Arial;">&gt; Internet-Drafts are also a=
vailable by anonymous FTP at:<br></div><div style=3D"font-family:Arial;"=
>&gt;&nbsp;<a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.iet=
f.org/internet-drafts/</a><br></div><div style=3D"font-family:Arial;">&g=
t;<br></div><div style=3D"font-family:Arial;">&gt;<br></div><div style=3D=
"font-family:Arial;">--&nbsp;<br></div><div style=3D"font-family:Arial;"=
>Kenneth Murchison<br></div><div style=3D"font-family:Arial;">Senior Sof=
tware Developer<br></div><div style=3D"font-family:Arial;">Fastmail US L=
LC<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fo=
nt-family:Arial;">_______________________________________________<br></d=
iv><div style=3D"font-family:Arial;">Extra mailing list<br></div><div st=
yle=3D"font-family:Arial;"><a href=3D"mailto:Extra@ietf.org">Extra@ietf.=
org</a><br></div><div style=3D"font-family:Arial;"><a href=3D"https://ww=
w.ietf.org/mailman/listinfo/extra">https://www.ietf.org/mailman/listinfo=
/extra</a><br></div><div style=3D"font-family:Arial;"><br></div></blockq=
uote><div style=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"=
><div class=3D"signature">--<br></div><div class=3D"signature">&nbsp; Br=
on Gondwana, CEO, Fastmail Pty Ltd<br></div><div class=3D"signature">&nb=
sp; brong@fastmailteam.com<br></div><div class=3D"signature"><br></div><=
/div><div style=3D"font-family:Arial;"><br></div></body></html>
--862db2fc303f494abce90f0864a80278--


From nobody Sun Feb  7 21:01:54 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2143A10C5; Sun,  7 Feb 2021 21:01:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161276051214.13506.8297756058473714921@ietfa.amsl.com>
Date: Sun, 07 Feb 2021 21:01:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/6MLQmAe8TqReJuz4VgveKElSfAI>
Subject: [Extra] I-D Action: draft-ietf-extra-sieve-mailboxid-07.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2021 05:01:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Sieve Email Filtering: delivery by mailboxid
        Author          : Bron Gondwana
	Filename        : draft-ietf-extra-sieve-mailboxid-07.txt
	Pages           : 10
	Date            : 2021-02-07

Abstract:
   The OBJECTID capability of the IMAP protocol (RFC8474) allows clients
   to identify mailboxes by a unique identifier which survives rename.

   This document extends the Sieve mail filtering language (RFC5228) to
   allow using that same unique identifier as a target for fileinto
   rules, and for testing the existance of mailboxes.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-extra-sieve-mailboxid-07.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-mailboxid-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Sun Feb  7 21:04:24 2021
Return-Path: <brong@fastmailteam.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 2A7E63A10CF for <extra@ietfa.amsl.com>; Sun,  7 Feb 2021 21:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=DMiRZYs1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=V3lsC8dq
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 ucGb9lBQdu2C for <extra@ietfa.amsl.com>; Sun,  7 Feb 2021 21:04:21 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 196D43A10CB for <extra@ietf.org>; Sun,  7 Feb 2021 21:04:21 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7B2815C0196 for <extra@ietf.org>; Mon,  8 Feb 2021 00:04:19 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Mon, 08 Feb 2021 00:04:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=WV/dU0g zSSOMqgSdQTPJnuecEEDyhyHT0XiEJQH5+7M=; b=DMiRZYs1y7jG+JQr+OWbwjc QffMBpc+muNXK0oCe4a/Syx1zgrlQ5HG07ofrkjo5CZt4mfnpRH1GEibvRIMyjGy 2cmG9tp84VyVG5aIqCXj7CXp5Ag69P6iUu/dtwVSKGQX9BEIGlsaBLUACqbU4RI0 VPQ47IWy0AhvXz1cWvOI4+8bsiG9UvanlU2aE7gkg67dqL98TtwADYR+fzjcvFsL zeAk95QcLm1pZeK5QVhmTSBgQ/68LtN+bYUAv+XAPWypVWr3pfG9Ut1DNXSMX1ge FoCwsixBeFO5LAKGzmPO7GKhTH42G4HcQaRgIda9aXX2O2zeWJR2X3Q1wBAB4ug= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=WV/dU0 gzSSOMqgSdQTPJnuecEEDyhyHT0XiEJQH5+7M=; b=V3lsC8dqV5yKHUwW001vDq MHh6bW3N/iZskvb7aRVT8mYpWtRhbWlezEKg5FLf6IegpX8vgebCQims7q7tSHIZ s7LgbqE5xXAoyVDM/z9mybtA8fSnYNQMKu5cT/l+M057j7/UZ+ThXVGPDSCiOdRb zCjSDI5ky2bofY5jD1mty8iWBT4eJVICinW9FOstBCih7HbXDexAfacF37HjacJK ZRjSK6wFBtk/+cjB0k4qTaWSFKDsY2g8ZI0nY1h38xBBvXg+UQv/MOwLbcSgpmjt y2bcwnnPiRsmdWwe1zyvq8lyR4WL1HgjQAf5fy4R4dLN/dELPhhUCsDs2o2tkBfw ==
X-ME-Sender: <xms:U8YgYMN01GbFcCuyDnLYUXUge_p2kAOWDaz4xNgt-Z9qA5xdo-BR-g> <xme:U8YgYC8FF6-eEx9TOhdBug-REM93392XgmMZk-QORvqyYY0VkP2WA9VfS2EfZQzyD Qbvl2Alqek>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrhedvgdejjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepffdvkeefgeelie eutedttdffheevvefffeekuddvtddtkeeigfejuddvhfdvudelnecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:U8YgYDTHKbyGAkRPG22LL4CyOlugrhpjcBb0LwKrZY-dkKhYqBgykA> <xmx:U8YgYEv1laetVnI7ga3H7LWy77PVBCul9sLz0UoDd0-jP4kuQ8InsA> <xmx:U8YgYEeXonyyt654kW4g0qoouQpuuArmvAxta1ogeXbN7hyBqX2ljQ> <xmx:U8YgYOqUZ78S1B6trktTdXO9JXGCoV5TfFyiE-3GhZZRqMOFDBx5sA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 02B0136005C; Mon,  8 Feb 2021 00:04:19 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048
Mime-Version: 1.0
Message-Id: <5fb12f5a-c39d-471a-bbd3-524049eab7c0@dogfood.fastmail.com>
In-Reply-To: <26c6cdb3-d697-4bb5-9748-bf75c4ad109e@beta.fastmail.com>
References: <160804212198.17646.8123862646316973469@ietfa.amsl.com> <26c6cdb3-d697-4bb5-9748-bf75c4ad109e@beta.fastmail.com>
Date: Mon, 08 Feb 2021 16:03:57 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary=575bb89680154a229e1395a5ca45942b
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/-i473PxxXS9oaR_kmTUECf6sI_w>
Subject: Re: [Extra]  =?utf-8?q?Magnus_Westerlund=27s_Discuss_on_draft-ietf-ex?= =?utf-8?q?tra-sieve-mailboxid-06=3A_=28with_DISCUSS=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2021 05:04:23 -0000

--575bb89680154a229e1395a5ca45942b
Content-Type: text/plain

I have posted -07 which has the following text:

   For servers which also support the [RFC5490] mailbox extension, if
   both the ":create" and ":mailboxid" arguments are provided to a
   "fileinto" command and no matching mailbox is found, then a new
   mailbox will be created.

   This new mailbox will have the name specified by the positional
   mailbox argument ([RFC5228] section 4.1), however it will get a
   different mailboxid (chosen by the server) rather than the one
   specified by the ":mailboxid" argument to fileinto.

If that's still not clear enough I would love some help describing this.

-07 also removes the attempt to provide formal language definitions, as it appears that other sieve extensions have not, so this brings it into alignment with the others.

Thanks,

Bron


On Mon, Feb 8, 2021, at 15:30, Bron Gondwana wrote:
> On Wed, Dec 16, 2020, at 01:22, Magnus Westerlund via Datatracker wrote:
>> Magnus Westerlund has entered the following ballot position for
>> draft-ietf-extra-sieve-mailboxid-06: Discuss
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/
>> 
> 
> Hi Magnus,
> 
> Sorry for the lack of response on this - I missed it somehow at the time!
> 
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> First part is a formality discuss that likely is fairly easy to resolve
>> 
>> So this document uses formal syntax, however it does not explicitly reference
>> which. So I noticed RFC 5228 that do reference RFC 4234 which is now obsolete,
>> and the current in force version of ABNF is RFC 5234. Also as no WSP are
>> included in the rules, this document appears to use ABNF to express RFC 5228
>> grammar and not parsing syntax. So please clarify prior to the usages what the
>> formal language is and what it represents.
>> 
>> So this needs to be done prior to Section 5. But, can you please check that you
>> actually have the same level of  formal syntax in Section 5 that goes through
>> RFC 8580 as what is in Section 8. Otherwise please clarify both.
> 
> I'm happy to drop the formal language section entirely.  I just checked RFC8579 which describes a very similar extension and it has no formal ABNF section.  Would you be satisfied with having the ABNF dropped entirely and using prose and descriptions similar to what's in RFC8579?
> 
>> Secondly, I do consider the defining text first paragraph of in Section 4.1 so
>> hard to interpret that it must be fixed prior to publication. So although you
>> already are going to address it based on discussion of Martin Duke's comment, I
>> want to hold a discuss on this.
> 
> I will wordsmith that and post a new draft.
> 
> Thanks,
> 
> Bron.
> 
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
> 
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--575bb89680154a229e1395a5ca45942b
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"f=
ont-family:Arial;">I have posted -07 which has the following text:<br></=
div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-famil=
y:Arial;"><span class=3D"font" style=3D"font-family:menlo, consolas, mon=
ospace, sans-serif;">&nbsp;&nbsp; For servers which also support the [RF=
C5490] mailbox extension, if</span><span class=3D"font" style=3D"font-fa=
mily:menlo, consolas, monospace, sans-serif;"><br></span></div><div styl=
e=3D"font-family:Arial;"><span class=3D"font" style=3D"font-family:menlo=
, consolas, monospace, sans-serif;">&nbsp;&nbsp; both the ":create" and =
":mailboxid" arguments are provided to a</span><span class=3D"font" styl=
e=3D"font-family:menlo, consolas, monospace, sans-serif;"><br></span></d=
iv><div style=3D"font-family:Arial;"><span class=3D"font" style=3D"font-=
family:menlo, consolas, monospace, sans-serif;">&nbsp;&nbsp; "fileinto" =
command and no matching mailbox is found, then a new</span><span class=3D=
"font" style=3D"font-family:menlo, consolas, monospace, sans-serif;"><br=
></span></div><div style=3D"font-family:Arial;"><span class=3D"font" sty=
le=3D"font-family:menlo, consolas, monospace, sans-serif;">&nbsp;&nbsp; =
mailbox will be created.</span><span class=3D"font" style=3D"font-family=
:menlo, consolas, monospace, sans-serif;"><br></span></div><div style=3D=
"font-family:Arial;"><span class=3D"font" style=3D"font-family:menlo, co=
nsolas, monospace, sans-serif;"><br></span></div><div style=3D"font-fami=
ly:Arial;"><span class=3D"font" style=3D"font-family:menlo, consolas, mo=
nospace, sans-serif;">&nbsp;&nbsp; This new mailbox will have the name s=
pecified by the positional</span><span class=3D"font" style=3D"font-fami=
ly:menlo, consolas, monospace, sans-serif;"><br></span></div><div style=3D=
"font-family:Arial;"><span class=3D"font" style=3D"font-family:menlo, co=
nsolas, monospace, sans-serif;">&nbsp;&nbsp; mailbox argument ([RFC5228]=
 section 4.1), however it will get a</span><span class=3D"font" style=3D=
"font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><=
div style=3D"font-family:Arial;"><span class=3D"font" style=3D"font-fami=
ly:menlo, consolas, monospace, sans-serif;">&nbsp;&nbsp; different mailb=
oxid (chosen by the server) rather than the one</span><span class=3D"fon=
t" style=3D"font-family:menlo, consolas, monospace, sans-serif;"><br></s=
pan></div><div style=3D"font-family:Arial;"><span class=3D"font" style=3D=
"font-family:menlo, consolas, monospace, sans-serif;">&nbsp;&nbsp; speci=
fied by the ":mailboxid" argument to fileinto.</span><span class=3D"font=
" style=3D"font-family:menlo, consolas, monospace, sans-serif;"><br></sp=
an></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-=
family:Arial;">If that's still not clear enough I would love some help d=
escribing this.<br></div><div style=3D"font-family:Arial;"><br></div><di=
v style=3D"font-family:Arial;">-07 also removes the attempt to provide f=
ormal language definitions, as it appears that other sieve extensions ha=
ve not, so this brings it into alignment with the others.<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>Thanks,<br></div><div style=3D"font-family:Arial;"><br></div><div style=
=3D"font-family:Arial;">Bron<br></div><div style=3D"font-family:Arial;">=
<br></div><div style=3D"font-family:Arial;"><br></div><div>On Mon, Feb 8=
, 2021, at 15:30, Bron Gondwana wrote:<br></div><blockquote type=3D"cite=
" id=3D"qt" style=3D""><div style=3D"font-family:Arial;">On Wed, Dec 16,=
 2020, at 01:22, Magnus Westerlund via Datatracker wrote:<br></div><bloc=
kquote type=3D"cite" id=3D"qt-qt" style=3D""><div style=3D"font-family:A=
rial;">Magnus Westerlund has entered the following ballot position for<b=
r></div><div style=3D"font-family:Arial;">draft-ietf-extra-sieve-mailbox=
id-06: Discuss<br></div><div style=3D"font-family:Arial;"><br></div><div=
 style=3D"font-family:Arial;">When responding, please keep the subject l=
ine intact and reply to all<br></div><div style=3D"font-family:Arial;">e=
mail addresses included in the To and CC lines. (Feel free to cut this<b=
r></div><div style=3D"font-family:Arial;">introductory paragraph, howeve=
r.)<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"f=
ont-family:Arial;"><br></div><div style=3D"font-family:Arial;">Please re=
fer to&nbsp;<a href=3D"https://www.ietf.org/iesg/statement/discuss-crite=
ria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><=
br></div><div style=3D"font-family:Arial;">for more information about IE=
SG DISCUSS and COMMENT positions.<br></div><div style=3D"font-family:Ari=
al;"><br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">The document, along with other ballot positions, ca=
n be found here:<br></div><div style=3D"font-family:Arial;"><a href=3D"h=
ttps://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/">https=
://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/</a><br></d=
iv><div style=3D"font-family:Arial;"><br></div></blockquote><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Hi Magn=
us,<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"f=
ont-family:Arial;">Sorry for the lack of response on this - I missed it =
somehow at the time!<br></div><div style=3D"font-family:Arial;"><br></di=
v><blockquote type=3D"cite" id=3D"qt-qt" style=3D""><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;">--------------=
--------------------------------------------------------<br></div><div s=
tyle=3D"font-family:Arial;">DISCUSS:<br></div><div style=3D"font-family:=
Arial;">----------------------------------------------------------------=
------<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">First part is a formality discuss that likely is fa=
irly easy to resolve<br></div><div style=3D"font-family:Arial;"><br></di=
v><div style=3D"font-family:Arial;">So this document uses formal syntax,=
 however it does not explicitly reference<br></div><div style=3D"font-fa=
mily:Arial;">which. So I noticed RFC 5228 that do reference RFC 4234 whi=
ch is now obsolete,<br></div><div style=3D"font-family:Arial;">and the c=
urrent in force version of ABNF is RFC 5234. Also as no WSP are<br></div=
><div style=3D"font-family:Arial;">included in the rules, this document =
appears to use ABNF to express RFC 5228<br></div><div style=3D"font-fami=
ly:Arial;">grammar and not parsing syntax. So please clarify prior to th=
e usages what the<br></div><div style=3D"font-family:Arial;">formal lang=
uage is and what it represents.<br></div><div style=3D"font-family:Arial=
;"><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family=
:Arial;">So this needs to be done prior to Section 5. But, can you pleas=
e check that you<br></div><div style=3D"font-family:Arial;">actually hav=
e the same level of&nbsp; formal syntax in Section 5 that goes through<b=
r></div><div style=3D"font-family:Arial;">RFC 8580 as what is in Section=
 8. Otherwise please clarify both.<br></div></div></blockquote><div styl=
e=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I'm=
 happy to drop the formal language section entirely.&nbsp; I just checke=
d RFC8579 which describes a very similar extension and it has no formal =
ABNF section.&nbsp; Would you be satisfied with having the ABNF dropped =
entirely and using prose and descriptions similar to what's in RFC8579?<=
br></div><div style=3D"font-family:Arial;"><br></div><blockquote type=3D=
"cite" id=3D"qt-qt" style=3D""><div style=3D"font-family:Arial;">Secondl=
y, I do consider the defining text first paragraph of in Section 4.1 so<=
br></div><div style=3D"font-family:Arial;">hard to interpret that it mus=
t be fixed prior to publication. So although you<br></div><div style=3D"=
font-family:Arial;">already are going to address it based on discussion =
of Martin Duke's comment, I<br></div><div style=3D"font-family:Arial;">w=
ant to hold a discuss on this.<br></div></blockquote><div style=3D"font-=
family:Arial;"><br></div><div style=3D"font-family:Arial;">I will wordsm=
ith that and post a new draft.<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">Thanks,<br></div><div styl=
e=3D"font-family:Arial;"><div><br></div><div>Bron.<br></div></div><div s=
tyle=3D"font-family:Arial;"><br></div><div id=3D"qt-sig56629417"><div cl=
ass=3D"qt-signature">--<br></div><div class=3D"qt-signature">&nbsp; Bron=
 Gondwana, CEO, Fastmail Pty Ltd<br></div><div class=3D"qt-signature">&n=
bsp; brong@fastmailteam.com<br></div><div class=3D"qt-signature"><br></d=
iv></div><div style=3D"font-family:Arial;"><br></div><div>______________=
_________________________________<br></div><div>Extra mailing list<br></=
div><div><a href=3D"mailto:Extra@ietf.org">Extra@ietf.org</a><br></div><=
div><a href=3D"https://www.ietf.org/mailman/listinfo/extra">https://www.=
ietf.org/mailman/listinfo/extra</a><br></div><div><br></div></blockquote=
><div style=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"><di=
v class=3D"signature">--<br></div><div class=3D"signature">&nbsp; Bron G=
ondwana, CEO, Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; =
brong@fastmailteam.com<br></div><div class=3D"signature"><br></div></div=
><div style=3D"font-family:Arial;"><br></div></body></html>
--575bb89680154a229e1395a5ca45942b--


From nobody Mon Feb  8 02:19:45 2021
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 168343A1591; Mon,  8 Feb 2021 02:19:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yTDmjkrTjsny; Mon,  8 Feb 2021 02:19:42 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 85D8B3A158F; Mon,  8 Feb 2021 02:19:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612779580; d=isode.com; s=june2016; i=@isode.com; bh=k6lm+qfqkp1jil3fUusaQ1idPyPgJjE7vxt50Yn+CHg=; 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=l79jlR841Rgv4UI88ahfcqSsw7ARfGSc9nD4R0cNb0u+hxu7ES8ojAporqv7kRUwt4+sJL 1juhK6WQ6djTKuOpxJDugUHha1Ii9vFRZLUCzTAEIUKYL+yb9kv8bYREYWulB9uecv5QqZ Z3WCkk6cYj3DRtopdWCOzfw55NiSU7Q=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YCEQOgAqZhb3@statler.isode.com>; Mon, 8 Feb 2021 10:19:39 +0000
To: Barry Leiba <barryleiba@computer.org>, Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com> <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <9e4a3a46-72b1-f8ba-a2f1-7a373d6ccb13@isode.com>
Date: Mon, 8 Feb 2021 10:19:31 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <CALaySJL4c2BQVf3eU57k+51EUHYGmbL-inhJNy=Xtt_SyWzHtg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ky4G2kVnti747y0o_k8LW6DKJLg>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2021 10:19:44 -0000

Hi all,

On 04/02/2021 14:33, Barry Leiba wrote:
> Thanks, Ben, for the usual good comments.  Just responses on a couple here=
:
>
>> Section 2.2.1
>>
>>        response, and reads another response from the server.  In all
>>        cases, the client MUST send a complete command (including
>>        receiving all command continuation request responses and command
>>        continuations for the command) before initiating a new command.
>>
>> To check my understanding: the "command continuations for the command"
>> are things that the client sends, right?  Adding a word or two might
>> help clarify.
> Yes, it should say "and sending command continuations"; the word
> "sending" is missing.

Changed, thank you.

 =C2=A0[snip]
>> Section 2.3.2
>>
>>     $Junk  The user (or a delivery agent on behalf of the user) may
>>        choose to mark a message as definitely containing junk ($Junk; see
>>        also the related keyword $NotJunk).  The $Junk keyword can be used
>>        to mark (and potentially move/delete messages later), group or
>>        hide undesirable messages.  See [IMAP-KEYWORDS-REG] for more
>>        information.
>>
>> I'm not entirely sure what additional information I'm supposed to get
>> from [IMAP-KEYWORDS-REG]; the registry page is fairly short on
>> commentary.  (Applies throughout.)
> It's meant to send you to the reference doc, but, yes, the reader
> already has that anyway.  It might simply be better to say that the
> registration is recorded in IMAP-KEYWORDS-REG.

Actually, there is more information about $Junk in the registration=20
template=20
<https://www.iana.org/assignments/imap-jmap-keywords/junk/junk-template>=20
referenced from the registry.

But I see your point and will adjust wording about these references=20
where appropriate.

>> Section 6.4.8
>>
>>     Because of the similarity of MOVE to COPY, extensions that affect
>>     COPY affect MOVE in the same way.  Response codes listed in
>>     Section 7.1, as well as those defined by extensions, are sent as
>>     appropriate.
>>
>> Who decides what is "appropriate"?  Will everyone come to the same
>> conclusion?
> It means that the same responses are sent for MOVE as for COPY, under
> the corresponding conditions.
Indeed.
> Yes, we'd expect that to be evident.
> We can try rephrasing it if you think that's unclear.  Is what I said
> two sentences ago clearer?  Do you have other suggestions?
>
> Barry


From nobody Wed Feb 10 03:40:31 2021
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 522B53A0D79; Wed, 10 Feb 2021 03:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 5VmH_0MY8tSZ; Wed, 10 Feb 2021 03:40:20 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 3137A3A0D76; Wed, 10 Feb 2021 03:40:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612957217; d=isode.com; s=june2016; i=@isode.com; bh=Oc+2poum+fdL4eZVM29dJV9P16fB9LqqIQrO29Hc0DY=; 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=F5TVU3BV3buaisGL/LAywRap36xIj70qttL83Zbep9uK7VMsfUnZfMDKUN2ExpUuFVu1Ld 6H0/Ic/lKO0a4jztP6UI74vzaPowdbs0b9dRlvpZskxp1/9hgTCsgac4Alzi+uBy9oCw+r 7HwLsSoWlB+NduVoZmlXVONrprprbJA=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCPGIAAuQVDE@waldorf.isode.com>; Wed, 10 Feb 2021 11:40:16 +0000
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <0f2042e9-33be-01f6-8321-15fdc74fb4f1@isode.com>
Date: Wed, 10 Feb 2021 11:40:17 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------42EE5B26B67D7D286CE10DAE"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/pzfzMZC5S59DsLjwTa2WzFsIPqM>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 11:40:25 -0000

--------------42EE5B26B67D7D286CE10DAE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: quoted-printable

Hi Ben,

Thank you for your extensive comments! My comments/replies below:

On 04/02/2021 09:33, Benjamin Kaduk via Datatracker wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> There are several places where we see a:
>
>     Note: Since this document is restricted to 7-bit ASCII text, it is
>     not possible to show actual UTF-8 data.  [...]
>
> But this document is *not* restricted to 7-bit ASCII text!
> (I guess the (not-quoted) bit about not being possible to show actual KOI8=
-R data is
> still true, though.)  Showing actual non-ASCII text may not be as
> helpful as the current formulation, though, so I'd suggest just a
> modification to the disclaimer.
Ok.
> Section 1.3
>
>     IMAP was originally developed for the older [RFC-822] standard, and
>     as a consequence several fetch items in IMAP incorporate "RFC822" in
>     their name.  In all cases, "RFC822" should be interpreted as a
>     reference to the updated [RFC-5322] standard.
>
> It looks like it's down to just one (not "several"), now -- RFC822.SIZE.
I reworded, thank you.

 =C2=A0[snip]

> Section 3.2
>
>     In the authenticated state, the client is authenticated and MUST
>     select a mailbox to access before commands that affect messages will
>     be permitted.  This state is entered when a pre-authenticated
>     connection starts, when acceptable authentication credentials have
>     been provided, after an error in selecting a mailbox, or after a
>     successful CLOSE command.
>
> I think after a successful UNSELECT as well, right?  =C2=A76.4.2 says
> "returns the server to the authenticated state" about UNSELECT.
Thanks for spotting this. Added.
> Section 3.4
>
>              (6) CLOSE command, unsolicited CLOSED response code or
>                  failed SELECT or EXAMINE command
>
> [UNSELECT here as well, if above.]
Right.
> Section 5.1.2.2
>
>     Previous version of this protocol does not define a default server
>     namespace.  Two common namespace models have evolved:
>
> nit: maybe "the previous version of this protocol did not define" or
> "previous versions of this protocol did not define"
Ok.
> Section 6.1.1
>
>     Other capability names refer to extensions, revisions, or amendments
>     to this specification.  See the documentation of the CAPABILITY
>     response in Section 7.2.2 for additional information.  No
>     capabilities, beyond the base IMAP4rev2 set defined in this
>     specification, are enabled without explicit client action to invoke
>     the capability.
>
> Should we also note here that even the base IMAP4rev2 set can require
> explicit client action to enable (e.g., when IMAP4rev1 is also
> advertised)?
Yes.
> Section 6.2
>
>     Server implementations MAY allow access to certain mailboxes without
>     establishing authentication.  This can be done by means of the
>     ANONYMOUS [SASL] authenticator described in [ANONYMOUS].  [...]
>
> To be clear, from the perspective of the state machine, this entails
> entering the "authenticated" state but without actually authenticating
> as a specific client identity?
Yes. The assumed identity is a special anonymous identity, typically=20
with fewer privileges.

> Section 6.2.1
>
> Do we really want the example to show use of LOGIN (which per =C2=A76.2.3 =
is
> be considered a "last resort" and SHOULD NOT be used) even when
> AUTH=3DPLAIN is available?
Good point. Changed.
> Section 6.2.2
>
>     As with any other client response, this initial response MUST be
>     encoded as BASE64.  It also MUST be transmitted outside of a quoted
>
> nit: it looks like we added another paragraph or two between the
> previous mention of "initial response" and here, so maybe s/this/the/ is
> in order.
Ok.
>        authentication.  (Note that SASL framework allows creation of SASL
>        mechanisms that support 2FA (2-factor authentication), however
>        none are fully ready to be recommended by this document.)
>
> (side note) With sasl/gssapi/kerberos it's possible to know that the
> client used 2fa for its authentication exchange with the KDC even if it
> only has the one (ticket) factor to present to the IMAP server.  But
> this is probably more detail than we need to get into here...
Ok. The point of the added text was to handwavy point out that 2FA and=20
SASL are compatible.
>                 C: A01 AUTHENTICATE PLAIN dGVzdAB0ZXN0AHRlc3Q=3D
>                 S: A001 OK Success (tls protection)
>
> (nit) A01 is reusing the client tag, and doesn't seem to match the
> response ... typo?

Good catch. Fixed.

 =C2=A0[snip]

> Section 6.3.1
>
>     In the following example, the client enables CONDSTORE:
>
> Should we reference RFC 7162 here?
Added.
> Section 6.3.2
>
>     fails is attempted, no mailbox is selected.  When deselecting a
>     selected mailbox, the server MUST return an untagged OK response with
>     the "[CLOSED]" response code when the currently selected mailbox is
>     closed (see Paragraph 10).
>
> I'm not sure how to find Paragraph 10.
This is an xml2rfc referencing problem. I will talk to RFC Editor about=20
this.
> Section 6.3.5
>
> It kind of looks like the "examples" contains two similar examples stuck
> together (or some other client has (re)created some folders
> mid-session).  I think in RFC 3501 the blank line separating examples
> also crossed a page boundary, so it got missed when converting to XML(?)
> for the new document.
Yes, a very good point.
> Section 6.3.6
>
>     If the server's hierarchy separator character appears in the name,
>     the server SHOULD create any superior hierarchical names that are
>     needed for the RENAME command to complete successfully.  In other
>
> Is this specifically in the "new mailbox name"?
Yes.
>     the normalized new mailbox name (see Section 6.3.9.7).  This would
>     allow the client to correlate supplied name with the normalized name.
>
> nit: "the supplied name".

Fixed, thanks.

 =C2=A0[snip]

> Section 6.4.4
>
>     However all options specified above MUST result in a single ESEARCH
>     response if used by themselves or in combination.  This guaranty
>     simplifies processing in IMAP4rev2 clients.  Future SEARCH extensions
>
> nit: s/guaranty/guarantee/
>
>     MAY be supported.  Clients SHOULD use UTF-8.  Note that if "CHARSET"
>     is not provided IMAP4rev2 server MUST assume UTF-8, so selecting
>
> nit: "an IMAP4rev2 server".
Both fixed, thanks.
> Section 6.4.4.4
>
>        Example 4:
>                 C: P282 SEARCH RETURN (SAVE) SINCE 1-Feb-1994
>                     NOT FROM "Smith"
>                 S: P282 OK SEARCH completed
>                 C: P283 SEARCH CHARSET UTF-8 (OR $ 1,3000:3021) TEXT {8}
>                 C: YYYYYYYY
>
> That snippet doesn't seem consistent with a synchronizing literal;
> should it be a non-synchronizing literal instead?

Yes, good catch.

 =C2=A0 [snip]

> Section 6.5
>
>     Server implementations MUST NOT send any added (not specified in this
>     specification) untagged responses, unless the client requested it by
>     issuing the associated experimental command or the ENABLE command
>     (Section 6.3.1).
>
> We don't really have much text remaining to describe what the
> "associated experimental command" would be, now that the "X<atom>
> Command" section is removed.
I've added "(specified=C2=A0in=C2=A0an=C2=A0extension=C2=A0document)" after =
"experimental=20
command". I hope this is clearer.
> Section 7.1
>
>     CAPABILITY
>
>           Followed by a list of capabilities.  This can appear in the
>           initial OK or PREAUTH response to transmit an initial
>           capabilities list.  It can also appear in tagged responses to
>           LOGIN or AUTHENTICATE commands.  This makes it unnecessary for
>           a client to send a separate CAPABILITY command if it recognizes
>           this response.
>
> (and if the implicit capability list is sent in the same
> authentication/security-mechanism context as subsequent commands)
Good point. I added=20
"and=C2=A0there=C2=A0was=C2=A0no=C2=A0change=C2=A0to=C2=A0the=C2=A0TLS=C2=A0=
and/or=C2=A0authentication=20
state=C2=A0since=C2=A0it=C2=A0was=C2=A0received" to the end of the last sent=
ence.
>     COPYUID
>
>           Followed by the UIDVALIDITY of the destination mailbox, a UID
>           set containing the UIDs of the message(s) in the source mailbox
>           that were copied to the destination mailbox and containing the
>           UIDs assigned to the copied message(s) in the destination
>           mailbox, indicates that the message(s) have been copied to the
>           destination mailbox with the stated UID(s).
>
> (editorial) Is there one UID set in the response or two (one per
> source/destination)?  The following paragraph suggests two, but this one
> seems to just say one.
Yes, 2 sets. I will clarify.
>     NOPERM
>
>           The access control system (e.g., Access Control List (ACL), see
>           [RFC4314] does not permit this user to carry out an operation,
>           such as selecting or creating a mailbox.
>
> nit: missing close paren.
>
> Section 7.1.3
>
> The example doesn't seem to show the tagged BAD usage, and I'm having
> trouble convincing myself whether "very long command line" should
> qualify for the tagged form or not.

Either. I think it depends on how the parser is written./*
*/

[snip]
> /**/Section 7.2.2
 =C2=A0[snip]
>     A server MAY send capabilities automatically, by using the CAPABILITY
>     response code in the initial PREAUTH or OK responses, and by sending
>     an updated CAPABILITY response code in the tagged OK response as part
>     of a successful authentication.  It is unnecessary for a client to
>     send a separate CAPABILITY command if it recognizes these automatic
>     capabilities.
>
> IIRC, the earlier mention of automatic capabilities said that an
> explicit CAPABILITY is still needed for the case when (e.g.)
> AUTHENTICATE enables a new security layer.
I added similar text here.
> Section 7.3.4
>
>     [[TBD: describe the most common search data pairs returned.]]
>
> Is this still current?
I pretty much need to cut and paste text from another section. Doing it now.
> Section 7.5.2
>
>     ENVELOPE
>           [...]
>           An address structure is a parenthesized list that describes an
>           electronic mail address.  The fields of an address structure
>           are in the following order: personal name, [SMTP] at-domain-
>           list (source route, obs-route), mailbox name, and host name.
>
> The "obs-route" was not in RFC 3501, is not listed in any published
> errata reports, and does not seem to be called out in the list of
> changes from RFC 3501 in Appendix E.  This isn't the formal protocol
> description, so I guess it's not a breaking change, but I still don't
> understand why it's different (presumably just my ignorance...).
"obs-route" is defined in RFC 5322. I will clarify.
>
>     If the server chooses to send unsolicited FETCH responses, they MUST
>     include UID FETCH item.  Note that this is a new requirement when
>     compared to RFC 3501.
>
>        Example:    S: * 23 FETCH (FLAGS (\Seen) RFC822.SIZE 44827)
>
> I guess this is intended to just be a generic FETCH example, but it's a
> bit jarring to not see the UID FETCH item in the example right after the
> text that mentions a requirement to send it, with no other commentary.
Yes, good point :-). Fixed.
> Section 8
>
>     The following is a transcript of an IMAP4rev2 connection on a non TLS
>     port.  A long line in this sample is broken for editorial clarity.
>
> More than one line, now.
>
> C:   A001 AUTHENTICATE SCRAM-SHA-256
>        biwsbj11c2VyLHI9ck9wck5HZndFYmVSV2diTkVrcU8=3D
> S:   + cj1yT3ByTkdmd0ViZVJXZ2JORWtxTyVodllEcFdVYTJSYVRDQWZ1eEZJbGopaE5s
>       RiRrMCxzPVcyMlphSjBTTlk3c29Fc1VFamI2Z1E9PSxpPTQwOTYNCg=3D=3D
> C:   Yz1iaXdzLHI9ck9wck5HZndFYmVSV2diTkVrcU8laHZZRHBXVWEyUmFUQ0FmdXhG
>       SWxqKWhObEYkazAscD1kSHpiWmFwV0lrNGpVaE4rVXRlOXl0YWc5empmTUhnc3Ft
>       bWl6N0FuZFZRPQ=3D=3D
> S:   + dj02cnJpVFJCaTIzV3BSUi93dHVwK21NaFVaVW4vZEI1bkxUSlJzamw5NUc0PQ=3D=
=3D
>
> These correspond quite nicely to (base64'd copies of) the example in RFC
> 7677, with the exception of the first server line, that includes an
> additional CRLF in the decoded data.
Ok, I will double check and correct.
> Section 9
>
>    body-fld-enc    =3D (DQUOTE ("7BIT" / "8BIT" / "BINARY" / "BASE64"/
>                      "QUOTED-PRINTABLE") DQUOTE) / string
>                      ; Content-Transfer-Encoding header field value.
>                      ; Defaults to "7BIT" (as per RFC 2045)
>                      ; if not present in the body part.
>
> Is this comment still accurate?
Yes.
>    capability      =3D ("AUTH=3D" auth-type) / atom
>                        ; New capabilities MUST begin with "X" or be
>                        ; registered with IANA in
>                        ; a standards-track, an experimental
>                        ; or an informational RFC.
>
> Is this comment still accurate?
Good catch. I fixed in my copy.
>    capability-data =3D "CAPABILITY" *(SP capability) SP "IMAP4rev2"
>                      *(SP capability)
>                        ; Servers MUST implement the STARTTLS, AUTH=3DPLAIN=
,
>                        ; and LOGINDISABLED capabilities.
>                        ; Servers which offer RFC 1730 compatibility MUST
>                        ; list "IMAP4" as the first capability.
>                        ; Servers which offer RFC 3501 compatibility MUST
>                        ; list "IMAP4rev1" as one of capabilities.
>
> I don't remember us mentioning an "IMAP4" capability in the previous
> text, and I definitely remember an assertion that the order in which
> capabilities are listed does not have significance, which seems to
> conflict with the comment about "IMAP4" as the first capability.
"IMAP4" capability is described in RFC 1730, which required it to be the=20
first. All subsequent versions don't require specific position, so they=20
can remain backward compatible with "IMAP4", if needed.
>    command-any     =3D "CAPABILITY" / "LOGOUT" / "NOOP" / x-command
>                        ; Valid in all states
>
> Is x-command still valid?
Good point. Removed.
>    media-basic     =3D ((DQUOTE ("APPLICATION" / "AUDIO" / "IMAGE" /
>                      "FONT" / "MESSAGE" / "MODEL" / "VIDEO" ) DQUOTE)
>                      / string)
>                      SP media-subtype
>                        ; Defined in [MIME-IMT].
>                        ; FONT defined in RFC 8081.
>
> Why does only FONT get a comment?  I don't see "MODEL" in [MIME-IMT],
> either.
Yes, I think adding a reference for MODEL (RFC=C2=A02077) is a good idea. Th=
e=20
rest should be covered.
> When the namespace-command production is defined, it's spelled all in
> lowercase, but it is spelled "Namespace-Command" when it appears in the
> command-auth production.
Production names are case-insensitive. I checked.
> The "partial-range" production doesn't seem to be used anywhere.

It was originally defined in RFC=C2=A05092 (IMAP URL). If that document gets=
=20
updated, it would be good to point to this document.

>    return-option   =3D  "SUBSCRIBED" / "CHILDREN" / status-option /
>                       option-extension
>
> (nit) This seems to only be used in list-return-opts, so maybe the
> generic name is not the best fit for it.

I almost renamed it to list-return-opt, but then realised that several=20
other RFCs extend it.

I added "list-return-opt =3D return-option" with a comment.

> Section 11
>
> It might be worth putting in some bromide about how while md5 is used
> in the BODYSTRUCTURE response, the usage is not particularly security
> relevant and so there is not a vulnerability due to its use.
If you can suggest some text on this, that would be great.
> There are also some forms of DoS attack that we don't say much about
> (slowloris, many parallel connections, etc.), and the mitigations are
> fairly well known.  It might be worth expounding on these a little bit
>=20(though since in most cases both parties have authenticated in some
> manner, the situation is not as bad as it sometimes is).
>
> Section 11.3
>
>        as well as any response codes other than CAPABILITY.  Client
>        SHOULD ignore the ALERT response code until after TLS has been
>        successfully negotiated (whether using STARTTLS or TLS negotiation
>        on implicit TLS port).  Unless explicitly allowed by an IMAP
>
> Up in =C2=A77.1 we said that this was "without TLS or SASL security layer
> confidentiality", not limited to TLS.
> (Also, nit: "Clients" plural.)
Changed, thanks.
> Section 11.6
>
>     A server SHOULD report any authentication failure and analyze such
>     authentication failure attempt with regard to a password brute force
>     attack as well as a password spraying attack.  Accounts that match
>     password spraying attacks MUST be blocked and request to change their
>     passwords and only password with significant strength SHOULD be
>     accepted.
>
> I'm not 100% sure that "password spraying attack" is a well-known
> concept.  It probably is, but it's hard to be sure.
Ok, I will see if I can add a reference.
> Also, I assume that "accounts that match password spraying attacks"
> means accounts where the password being tested succeeds at
> authenticating, which could be worth clarifying with a wording tweak.
Done.
> Section 13.1
>
> It's not clear to me that [ANONYMOUS] is referenced in a manner that
> requires classification as normative; likewise for [SCRAM-SHA-256].
> Similarly, if we use a modified form of [UTF-7] that we describe in
> whole ourselves, that does not seem to be normative.
I will review.
> Section 13.2
>
> If we refer to RFC 3503 for more details on how the mechanism is used,
> should that be a normative reference?
Good point. Moved to normative references.
> Appendix E
>
>     29.  Revised IANA registration procedure for IMAP extensions and
>          removed "X" convention.
>
> Is that worth a BCP 178 reference?

Added.

Best Regards,

Alexey



--------------42EE5B26B67D7D286CE10DAE
Content-Type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8"=
>
  </head>
  <body>
    <p>Hi Ben,</p>
    <p>Thank you for your extensive comments! My comments/replies below:<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/02/2021 09:33, Benjamin Kaduk via
      Datatracker wrote:
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">-------------------------------=
---------------------------------------
COMMENT:
----------------------------------------------------------------------

There are several places where we see a:

   Note: Since this document is restricted to 7-bit ASCII text, it is
   not possible to show actual UTF-8 data.  [...]

But this document is *not* restricted to 7-bit ASCII text!
(I guess the (not-quoted) bit about not being possible to show actual KOI8-R=
 data is
still true, though.)  Showing actual non-ASCII text may not be as
helpful as the current formulation, though, so I'd suggest just a
modification to the disclaimer.</pre>
    </blockquote>
    Ok.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 1.3

   IMAP was originally developed for the older [RFC-822] standard, and
   as a consequence several fetch items in IMAP incorporate "RFC822" in
   their name.  In all cases, "RFC822" should be interpreted as a
   reference to the updated [RFC-5322] standard.

It looks like it's down to just one (not "several"), now -- RFC822.SIZE.</pr=
e>
    </blockquote>
    I reworded, thank you.<br>
    <p>=C2=A0[snip]<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 3.2

   In the authenticated state, the client is authenticated and MUST
   select a mailbox to access before commands that affect messages will
   be permitted.  This state is entered when a pre-authenticated
   connection starts, when acceptable authentication credentials have
   been provided, after an error in selecting a mailbox, or after a
   successful CLOSE command.

I think after a successful UNSELECT as well, right?  =C2=A76.4.2 says
"returns the server to the authenticated state" about UNSELECT.</pre>
    </blockquote>
    Thanks for spotting this. Added.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 3.4

            (6) CLOSE command, unsolicited CLOSED response code or
                failed SELECT or EXAMINE command

[UNSELECT here as well, if above.]</pre>
    </blockquote>
    Right.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 5.1.2.2

   Previous version of this protocol does not define a default server
   namespace.  Two common namespace models have evolved:

nit: maybe "the previous version of this protocol did not define" or
"previous versions of this protocol did not define"</pre>
    </blockquote>
    Ok.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.1.1

   Other capability names refer to extensions, revisions, or amendments
   to this specification.  See the documentation of the CAPABILITY
   response in Section 7.2.2 for additional information.  No
   capabilities, beyond the base IMAP4rev2 set defined in this
   specification, are enabled without explicit client action to invoke
   the capability.

Should we also note here that even the base IMAP4rev2 set can require
explicit client action to enable (e.g., when IMAP4rev1 is also
advertised)?</pre>
    </blockquote>
    Yes.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.2

   Server implementations MAY allow access to certain mailboxes without
   establishing authentication.  This can be done by means of the
   ANONYMOUS [SASL] authenticator described in [ANONYMOUS].  [...]

To be clear, from the perspective of the state machine, this entails
entering the "authenticated" state but without actually authenticating
as a specific client identity?</pre>
    </blockquote>
    Yes. The assumed identity is a special anonymous identity, typically
    with fewer privileges.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.2.1

Do we really want the example to show use of LOGIN (which per =C2=A76.2.3 is
be considered a "last resort" and SHOULD NOT be used) even when
AUTH=3DPLAIN is available?</pre>
    </blockquote>
    Good point. Changed.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.2.2

   As with any other client response, this initial response MUST be
   encoded as BASE64.  It also MUST be transmitted outside of a quoted

nit: it looks like we added another paragraph or two between the
previous mention of "initial response" and here, so maybe s/this/the/ is
in order.</pre>
    </blockquote>
    Ok.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">      authentication.  (Note th=
at SASL framework allows creation of SASL
      mechanisms that support 2FA (2-factor authentication), however
      none are fully ready to be recommended by this document.)

(side note) With sasl/gssapi/kerberos it's possible to know that the
client used 2fa for its authentication exchange with the KDC even if it
only has the one (ticket) factor to present to the IMAP server.  But
this is probably more detail than we need to get into here...</pre>
    </blockquote>
    Ok. The point of the added text was to handwavy point out that 2FA
    and SASL are compatible.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">               C: A01 AUTHENTIC=
ATE PLAIN dGVzdAB0ZXN0AHRlc3Q=3D
               S: A001 OK Success (tls protection)

(nit) A01 is reusing the client tag, and doesn't seem to match the
response ... typo?</pre>
    </blockquote>
    <p>Good catch. Fixed.</p>
    <p>=C2=A0[snip]<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.3.1

   In the following example, the client enables CONDSTORE:

Should we reference RFC 7162 here?</pre>
    </blockquote>
    Added.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.3.2

   fails is attempted, no mailbox is selected.  When deselecting a
   selected mailbox, the server MUST return an untagged OK response with
   the "[CLOSED]" response code when the currently selected mailbox is
   closed (see Paragraph 10).

I'm not sure how to find Paragraph 10.</pre>
    </blockquote>
    This is an xml2rfc referencing problem. I will talk to RFC Editor
    about this.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.3.5

It kind of looks like the "examples" contains two similar examples stuck
together (or some other client has (re)created some folders
mid-session).  I think in RFC 3501 the blank line separating examples
also crossed a page boundary, so it got missed when converting to XML(?)
for the new document.</pre>
    </blockquote>
    Yes, a very good point.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.3.6

   If the server's hierarchy separator character appears in the name,
   the server SHOULD create any superior hierarchical names that are
   needed for the RENAME command to complete successfully.  In other

Is this specifically in the "new mailbox name"?</pre>
    </blockquote>
    Yes.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">   the normalized new mailbox n=
ame (see Section 6.3.9.7).  This would
   allow the client to correlate supplied name with the normalized name.

nit: "the supplied name".</pre>
    </blockquote>
    <p>Fixed, thanks.</p>
    <p>=C2=A0[snip]<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.4.4

   However all options specified above MUST result in a single ESEARCH
   response if used by themselves or in combination.  This guaranty
   simplifies processing in IMAP4rev2 clients.  Future SEARCH extensions

nit: s/guaranty/guarantee/

   MAY be supported.  Clients SHOULD use UTF-8.  Note that if "CHARSET"
   is not provided IMAP4rev2 server MUST assume UTF-8, so selecting

nit: "an IMAP4rev2 server".</pre>
    </blockquote>
    Both fixed, thanks.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.4.4.4

      Example 4:
               C: P282 SEARCH RETURN (SAVE) SINCE 1-Feb-1994
                   NOT FROM "Smith"
               S: P282 OK SEARCH completed
               C: P283 SEARCH CHARSET UTF-8 (OR $ 1,3000:3021) TEXT {8}
               C: YYYYYYYY

That snippet doesn't seem consistent with a synchronizing literal;
should it be a non-synchronizing literal instead?</pre>
    </blockquote>
    <p>Yes, good catch.</p>
    <p>=C2=A0 [snip]
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 6.5

   Server implementations MUST NOT send any added (not specified in this
   specification) untagged responses, unless the client requested it by
   issuing the associated experimental command or the ENABLE command
   (Section 6.3.1).

We don't really have much text remaining to describe what the
"associated experimental command" would be, now that the "X&lt;atom&gt;
Command" section is removed.</pre>
    </blockquote>
    I've added "(specified=C2=A0in=C2=A0an=C2=A0extension=C2=A0document)" af=
ter
    "experimental command". I hope this is clearer.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 7.1

   CAPABILITY

         Followed by a list of capabilities.  This can appear in the
         initial OK or PREAUTH response to transmit an initial
         capabilities list.  It can also appear in tagged responses to
         LOGIN or AUTHENTICATE commands.  This makes it unnecessary for
         a client to send a separate CAPABILITY command if it recognizes
         this response.

(and if the implicit capability list is sent in the same
authentication/security-mechanism context as subsequent commands)</pre>
    </blockquote>
    Good point. I added
    "and=C2=A0there=C2=A0was=C2=A0no=C2=A0change=C2=A0to=C2=A0the=C2=A0TLS=
=C2=A0and/or=C2=A0authentication
    state=C2=A0since=C2=A0it=C2=A0was=C2=A0received" to the end of the last =
sentence.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">   COPYUID

         Followed by the UIDVALIDITY of the destination mailbox, a UID
         set containing the UIDs of the message(s) in the source mailbox
         that were copied to the destination mailbox and containing the
         UIDs assigned to the copied message(s) in the destination
         mailbox, indicates that the message(s) have been copied to the
         destination mailbox with the stated UID(s).

(editorial) Is there one UID set in the response or two (one per
source/destination)?  The following paragraph suggests two, but this one
seems to just say one.</pre>
    </blockquote>
    Yes, 2 sets. I will clarify.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">   NOPERM

         The access control system (e.g., Access Control List (ACL), see
         [RFC4314] does not permit this user to carry out an operation,
         such as selecting or creating a mailbox.

nit: missing close paren.

Section 7.1.3

The example doesn't seem to show the tagged BAD usage, and I'm having
trouble convincing myself whether "very long command line" should
qualify for the tagged form or not.</pre>
    </blockquote>
    <p>Either. I think it depends on how the parser is written.<i><b><br>
        </b></i></p>
    [snip]<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D""><i><b>
</b></i>Section 7.2.2</pre>
    </blockquote>
    =C2=A0[snip]
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">   A server MAY send capabiliti=
es automatically, by using the CAPABILITY
   response code in the initial PREAUTH or OK responses, and by sending
   an updated CAPABILITY response code in the tagged OK response as part
   of a successful authentication.  It is unnecessary for a client to
   send a separate CAPABILITY command if it recognizes these automatic
   capabilities.

IIRC, the earlier mention of automatic capabilities said that an
explicit CAPABILITY is still needed for the case when (e.g.)
AUTHENTICATE enables a new security layer.</pre>
    </blockquote>
    I added similar text here.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 7.3.4

   [[TBD: describe the most common search data pairs returned.]]

Is this still current?</pre>
    </blockquote>
    I pretty much need to cut and paste text from another section. Doing
    it now.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 7.5.2

   ENVELOPE
         [...]
         An address structure is a parenthesized list that describes an
         electronic mail address.  The fields of an address structure
         are in the following order: personal name, [SMTP] at-domain-
         list (source route, obs-route), mailbox name, and host name.

The "obs-route" was not in RFC 3501, is not listed in any published
errata reports, and does not seem to be called out in the list of
changes from RFC 3501 in Appendix E.  This isn't the formal protocol
description, so I guess it's not a breaking change, but I still don't
understand why it's different (presumably just my ignorance...).</pre>
    </blockquote>
    "obs-route" is defined in RFC 5322. I will clarify.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">

   If the server chooses to send unsolicited FETCH responses, they MUST
   include UID FETCH item.  Note that this is a new requirement when
   compared to RFC 3501.

      Example:    S: * 23 FETCH (FLAGS (\Seen) RFC822.SIZE 44827)

I guess this is intended to just be a generic FETCH example, but it's a
bit jarring to not see the UID FETCH item in the example right after the
text that mentions a requirement to send it, with no other commentary.</pre>
    </blockquote>
    Yes, good point :-). Fixed.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 8

   The following is a transcript of an IMAP4rev2 connection on a non TLS
   port.  A long line in this sample is broken for editorial clarity.

More than one line, now.

C:   A001 AUTHENTICATE SCRAM-SHA-256
      biwsbj11c2VyLHI9ck9wck5HZndFYmVSV2diTkVrcU8=3D
S:   + cj1yT3ByTkdmd0ViZVJXZ2JORWtxTyVodllEcFdVYTJSYVRDQWZ1eEZJbGopaE5s
     RiRrMCxzPVcyMlphSjBTTlk3c29Fc1VFamI2Z1E9PSxpPTQwOTYNCg=3D=3D
C:   Yz1iaXdzLHI9ck9wck5HZndFYmVSV2diTkVrcU8laHZZRHBXVWEyUmFUQ0FmdXhG
     SWxqKWhObEYkazAscD1kSHpiWmFwV0lrNGpVaE4rVXRlOXl0YWc5empmTUhnc3Ft
     bWl6N0FuZFZRPQ=3D=3D
S:   + dj02cnJpVFJCaTIzV3BSUi93dHVwK21NaFVaVW4vZEI1bkxUSlJzamw5NUc0PQ=3D=3D

These correspond quite nicely to (base64'd copies of) the example in RFC
7677, with the exception of the first server line, that includes an
additional CRLF in the decoded data.</pre>
    </blockquote>
    Ok, I will double check and correct.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">
Section 9

  body-fld-enc    =3D (DQUOTE ("7BIT" / "8BIT" / "BINARY" / "BASE64"/
                    "QUOTED-PRINTABLE") DQUOTE) / string
                    ; Content-Transfer-Encoding header field value.
                    ; Defaults to "7BIT" (as per RFC 2045)
                    ; if not present in the body part.

Is this comment still accurate?</pre>
    </blockquote>
    Yes.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">  capability      =3D ("AUTH=3D=
" auth-type) / atom
                      ; New capabilities MUST begin with "X" or be
                      ; registered with IANA in
                      ; a standards-track, an experimental
                      ; or an informational RFC.

Is this comment still accurate?</pre>
    </blockquote>
    Good catch. I fixed in my copy.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">  capability-data =3D "CAPABILI=
TY" *(SP capability) SP "IMAP4rev2"
                    *(SP capability)
                      ; Servers MUST implement the STARTTLS, AUTH=3DPLAIN,
                      ; and LOGINDISABLED capabilities.
                      ; Servers which offer RFC 1730 compatibility MUST
                      ; list "IMAP4" as the first capability.
                      ; Servers which offer RFC 3501 compatibility MUST
                      ; list "IMAP4rev1" as one of capabilities.

I don't remember us mentioning an "IMAP4" capability in the previous
text, and I definitely remember an assertion that the order in which
capabilities are listed does not have significance, which seems to
conflict with the comment about "IMAP4" as the first capability.</pre>
    </blockquote>
    "IMAP4" capability is described in RFC 1730, which required it to be
    the first. All subsequent versions don't require specific position,
    so they can remain backward compatible with "IMAP4", if needed.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">  command-any     =3D "CAPABILI=
TY" / "LOGOUT" / "NOOP" / x-command
                      ; Valid in all states

Is x-command still valid?</pre>
    </blockquote>
    Good point. Removed.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">  media-basic     =3D ((DQUOTE =
("APPLICATION" / "AUDIO" / "IMAGE" /
                    "FONT" / "MESSAGE" / "MODEL" / "VIDEO" ) DQUOTE)
                    / string)
                    SP media-subtype
                      ; Defined in [MIME-IMT].
                      ; FONT defined in RFC 8081.

Why does only FONT get a comment?  I don't see "MODEL" in [MIME-IMT],
either.</pre>
    </blockquote>
    Yes, I think adding a reference for MODEL (RFC=C2=A02077) is a good idea=
.
    The rest should be covered.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">When the namespace-command prod=
uction is defined, it's spelled all in
lowercase, but it is spelled "Namespace-Command" when it appears in the
command-auth production.</pre>
    </blockquote>
    Production names are case-insensitive. I checked.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">The "partial-range" production =
doesn't seem to be used anywhere.</pre>
    </blockquote>
    <p>It was originally defined in RFC=C2=A05092 (IMAP URL). If that
      document gets updated, it would be good to point to this document.</p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">  return-option   =3D  "SUBSCRI=
BED" / "CHILDREN" / status-option /
                     option-extension

(nit) This seems to only be used in list-return-opts, so maybe the
generic name is not the best fit for it.</pre>
    </blockquote>
    <p>I almost renamed it to list-return-opt, but then realised that
      several other RFCs extend it.</p>
    <p>I added "list-return-opt =3D return-option" with a comment.
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 11

It might be worth putting in some bromide about how while md5 is used
in the BODYSTRUCTURE response, the usage is not particularly security
relevant and so there is not a vulnerability due to its use.</pre>
    </blockquote>
    If you can suggest some text on this, that would be great.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">There are also some forms of Do=
S attack that we don't say much about
(slowloris, many parallel connections, etc.), and the mitigations are
fairly well known.  It might be worth expounding on these a little bit
(though since in most cases both parties have authenticated in some
manner, the situation is not as bad as it sometimes is).

Section 11.3

      as well as any response codes other than CAPABILITY.  Client
      SHOULD ignore the ALERT response code until after TLS has been
      successfully negotiated (whether using STARTTLS or TLS negotiation
      on implicit TLS port).  Unless explicitly allowed by an IMAP

Up in =C2=A77.1 we said that this was "without TLS or SASL security layer
confidentiality", not limited to TLS.
(Also, nit: "Clients" plural.)</pre>
    </blockquote>
    Changed, thanks.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 11.6

   A server SHOULD report any authentication failure and analyze such
   authentication failure attempt with regard to a password brute force
   attack as well as a password spraying attack.  Accounts that match
   password spraying attacks MUST be blocked and request to change their
   passwords and only password with significant strength SHOULD be
   accepted.

I'm not 100% sure that "password spraying attack" is a well-known
concept.  It probably is, but it's hard to be sure.</pre>
    </blockquote>
    Ok, I will see if I can add a reference.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Also, I assume that "accounts t=
hat match password spraying attacks"
means accounts where the password being tested succeeds at
authenticating, which could be worth clarifying with a wording tweak.</pre>
    </blockquote>
    Done.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 13.1

It's not clear to me that [ANONYMOUS] is referenced in a manner that
requires classification as normative; likewise for [SCRAM-SHA-256].
Similarly, if we use a modified form of [UTF-7] that we describe in
whole ourselves, that does not seem to be normative.</pre>
    </blockquote>
    I will review.
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Section 13.2

If we refer to RFC 3503 for more details on how the mechanism is used,
should that be a normative reference?</pre>
    </blockquote>
    Good point. Moved to normative references.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:161243121159.6909.2386107317688674630@ietfa.amsl.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">Appendix E

   29.  Revised IANA registration procedure for IMAP extensions and
        removed "X" convention.

Is that worth a BCP 178 reference?</pre>
    </blockquote>
    <p>Added.</p>
    <p>Best Regards,</p>
    <p>Alexey</p>
    <p><br>
    </p>
  </body>
</html>

--------------42EE5B26B67D7D286CE10DAE--


From nobody Wed Feb 10 06:54:50 2021
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 B3C163A0CE2; Wed, 10 Feb 2021 06:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 NnppTP3BaU6r; Wed, 10 Feb 2021 06:54:47 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 03C423A0CDD; Wed, 10 Feb 2021 06:54:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612968885; d=isode.com; s=june2016; i=@isode.com; bh=5QHEX3kLwP+W9BleNdd0FYqpA3TWCLlOCq402GMMA/8=; 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=i8auxO2q9yzJErtZqUrsiR7R0PpVy3y1Y5OE4q/cVu297FNVe45rzllAIwa97EORxwfKpQ sHosgjdHsfsszBFpj17Sz3L8UNchP0tOvRbtjhRA1d+3z6mMXcH+KCNvpvEDlWz50QP99s y5yvtNTr9hICnxKw/kZglxTvuYlBlMU=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YCPztQAqZgMo@statler.isode.com>; Wed, 10 Feb 2021 14:54:45 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
Message-ID: <5e61d5c9-c2a6-0d08-b3a0-63f9ae204e68@isode.com>
Date: Wed, 10 Feb 2021 14:54:46 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/3YbR9u7rAe7x3J1KhRfp0SaDjIY>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 14:54:49 -0000

Hi Ben,

Replying to a few more of your comments:

On 04/02/2021 09:33, Benjamin Kaduk via Datatracker wrote:
> There are several places where we see a:
>
>     Note: Since this document is restricted to 7-bit ASCII text, it is
>     not possible to show actual UTF-8 data.  [...]
>
> But this document is *not* restricted to 7-bit ASCII text!
> (I guess the (not-quoted) bit about not being possible to show actual KOI8=
-R data is
> still true, though.)  Showing actual non-ASCII text may not be as
> helpful as the current formulation, though, so I'd suggest just a
> modification to the disclaimer.
Ok.
> Section 6.1.1
>
>     Other capability names refer to extensions, revisions, or amendments
>     to this specification.  See the documentation of the CAPABILITY
>     response in Section 7.2.2 for additional information.  No
>     capabilities, beyond the base IMAP4rev2 set defined in this
>     specification, are enabled without explicit client action to invoke
>     the capability.
>
> Should we also note here that even the base IMAP4rev2 set can require
> explicit client action to enable (e.g., when IMAP4rev1 is also
> advertised)?

You have a point. I replaced the last sentence with 2 sentences:

If=C2=A0IMAP4rev1=C2=A0capability=C2=A0is=C2=A0not=C2=A0advertised,=C2=A0no=
=C2=A0capabilities,=C2=A0beyond=C2=A0the=C2=A0base=C2=A0IMAP4rev2=C2=A0set=
=20

defined=C2=A0in=C2=A0this=C2=A0specification,=C2=A0are=C2=A0enabled=C2=A0wit=
hout=C2=A0explicit=C2=A0client=C2=A0action=C2=A0to=C2=A0invoke=C2=A0the=C2=
=A0capability.
If=C2=A0both=C2=A0IMAP4rev1=C2=A0and=C2=A0IMAP4rev1=C2=A0capabilities=C2=A0a=
re=C2=A0advertised,=C2=A0no=C2=A0capabilities,=20
beyond
the=C2=A0base=C2=A0IMAP4rev1=C2=A0set=C2=A0specified=C2=A0in=C2=A0RFC=C2=A03=
501,=C2=A0are=C2=A0enabled=C2=A0without=C2=A0explicit=20
client=C2=A0action
 =C2=A0=C2=A0=C2=A0 to=C2=A0invoke=C2=A0the=C2=A0capability.
> Section 6.3.9.8
>
>     4:   In this example, we see more mailboxes that reside on another
>          server.  This is similar to the command <RLIST "" "%">.
>
>        C: A04 LIST (REMOTE) "" "%" RETURN (CHILDREN)
>        S: * LIST (\Marked \NoInferiors) "/" "inbox"
>        S: * LIST (\HasChildren) "/" "Fruit"
>        S: * LIST (\HasNoChildren) "/" "Tofu"
>        S: * LIST (\HasChildren) "/" "Vegetable"
>        S: * LIST (\Remote) "/" "Bread"
>        S: * LIST (\HasChildren \Remote) "/" "Meat"
>        S: A04 OK done
>
> Why does "Bread" not give \HasChildren or \HasNoChildren?
> I thought =C2=A76.3.9.5 said that the server MUST return these attributes
> (and the example does show \HasChildren returned for another \Remote
> box).
Agreed. I added \HasNoChildren for it.
> In example 10, "also" doesn't exist and "also/jazz" is remote.  Can we say
> anything a priori about whether "also" is remote (the example, of
> course, shows that it is not remote)?
It doesn't matter, because it doesn't exist.

 =C2=A0 [snip]

> Section 7.1.3
>
> The example doesn't seem to show the tagged BAD usage, and I'm having
> trouble convincing myself whether "very long command line" should
> qualify for the tagged form or not.

Either. I think it depends on how the parser is written.

Would you like me to add an example of a command issued in a wrong state=20
(that would result in tagged BAD)?

> Section 7.2, 7.3
>
> If the section headings are split into server and mailbox status,
> respectively, why does the initial intro paragraph still list both
> server and mailbox status data in both sections?
They were initially part of the same section, which was split up. I=20
fixed description now.
> Section 7.2.2
>
>     Other capability names indicate that the server supports an
>     extension, revision, or amendment to the IMAP4rev2 protocol.  Server
>     responses MUST conform to this document until the client issues a
>     command that uses the associated capability.
>
> (another instance) should we say anything about "MUST conform to this
> document" not applying when the server also advertises IMAP4rev1?
I've made a similar update here to the above.

Best Regards,

Alexey


From nobody Wed Feb 10 07:44:49 2021
Return-Path: <kaduk@mit.edu>
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 97F1E3A0E27; Wed, 10 Feb 2021 07:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 2rg-5Oi2njLr; Wed, 10 Feb 2021 07:44:45 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 138213A0E31; Wed, 10 Feb 2021 07:44:44 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 11AFiZ65018173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Feb 2021 10:44:39 -0500
Date: Wed, 10 Feb 2021 07:44:34 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: The IESG <iesg@ietf.org>, extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
Message-ID: <20210210154434.GM21@kduck.mit.edu>
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com> <5e61d5c9-c2a6-0d08-b3a0-63f9ae204e68@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5e61d5c9-c2a6-0d08-b3a0-63f9ae204e68@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/TwK96gQxpr60E_TtI3-cXRAY7sk>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 15:44:48 -0000

Hi Alexey,

This all sounds good; just one answer to your question inline.

On Wed, Feb 10, 2021 at 02:54:46PM +0000, Alexey Melnikov wrote:
> Hi Ben,
> 
> Replying to a few more of your comments:
> 
> On 04/02/2021 09:33, Benjamin Kaduk via Datatracker wrote:
> > There are several places where we see a:
> >
> >     Note: Since this document is restricted to 7-bit ASCII text, it is
> >     not possible to show actual UTF-8 data.  [...]
> >
> > But this document is *not* restricted to 7-bit ASCII text!
> > (I guess the (not-quoted) bit about not being possible to show actual KOI8-R data is
> > still true, though.)  Showing actual non-ASCII text may not be as
> > helpful as the current formulation, though, so I'd suggest just a
> > modification to the disclaimer.
> Ok.
> > Section 6.1.1
> >
> >     Other capability names refer to extensions, revisions, or amendments
> >     to this specification.  See the documentation of the CAPABILITY
> >     response in Section 7.2.2 for additional information.  No
> >     capabilities, beyond the base IMAP4rev2 set defined in this
> >     specification, are enabled without explicit client action to invoke
> >     the capability.
> >
> > Should we also note here that even the base IMAP4rev2 set can require
> > explicit client action to enable (e.g., when IMAP4rev1 is also
> > advertised)?
> 
> You have a point. I replaced the last sentence with 2 sentences:
> 
> If IMAP4rev1 capability is not advertised, no capabilities, beyond the base IMAP4rev2 set 
> 
> defined in this specification, are enabled without explicit client action to invoke the capability.
> If both IMAP4rev1 and IMAP4rev1 capabilities are advertised, no capabilities, 
> beyond
> the base IMAP4rev1 set specified in RFC 3501, are enabled without explicit 
> client action
>      to invoke the capability.
> > Section 6.3.9.8
> >
> >     4:   In this example, we see more mailboxes that reside on another
> >          server.  This is similar to the command <RLIST "" "%">.
> >
> >        C: A04 LIST (REMOTE) "" "%" RETURN (CHILDREN)
> >        S: * LIST (\Marked \NoInferiors) "/" "inbox"
> >        S: * LIST (\HasChildren) "/" "Fruit"
> >        S: * LIST (\HasNoChildren) "/" "Tofu"
> >        S: * LIST (\HasChildren) "/" "Vegetable"
> >        S: * LIST (\Remote) "/" "Bread"
> >        S: * LIST (\HasChildren \Remote) "/" "Meat"
> >        S: A04 OK done
> >
> > Why does "Bread" not give \HasChildren or \HasNoChildren?
> > I thought §6.3.9.5 said that the server MUST return these attributes
> > (and the example does show \HasChildren returned for another \Remote
> > box).
> Agreed. I added \HasNoChildren for it.
> > In example 10, "also" doesn't exist and "also/jazz" is remote.  Can we say
> > anything a priori about whether "also" is remote (the example, of
> > course, shows that it is not remote)?
> It doesn't matter, because it doesn't exist.
> 
>    [snip]
> 
> > Section 7.1.3
> >
> > The example doesn't seem to show the tagged BAD usage, and I'm having
> > trouble convincing myself whether "very long command line" should
> > qualify for the tagged form or not.
> 
> Either. I think it depends on how the parser is written.
> 
> Would you like me to add an example of a command issued in a wrong state 
> (that would result in tagged BAD)?

It would feel more complete to me with such an example, but it's not a big
deal and it will be fine to just leave it as-is.

Thanks for all the updates,

Ben

> > Section 7.2, 7.3
> >
> > If the section headings are split into server and mailbox status,
> > respectively, why does the initial intro paragraph still list both
> > server and mailbox status data in both sections?
> They were initially part of the same section, which was split up. I 
> fixed description now.
> > Section 7.2.2
> >
> >     Other capability names indicate that the server supports an
> >     extension, revision, or amendment to the IMAP4rev2 protocol.  Server
> >     responses MUST conform to this document until the client issues a
> >     command that uses the associated capability.
> >
> > (another instance) should we say anything about "MUST conform to this
> > document" not applying when the server also advertises IMAP4rev1?
> I've made a similar update here to the above.
> 
> Best Regards,
> 
> Alexey
> 


From nobody Wed Feb 10 09:48:59 2021
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 74BDF3A10F5; Wed, 10 Feb 2021 09:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JlKbq3yotQQ0; Wed, 10 Feb 2021 09:48:51 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 961623A110A; Wed, 10 Feb 2021 09:48:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612979329; d=isode.com; s=june2016; i=@isode.com; bh=P99iK21PBx2OKUtzbU61xKuIwnGpOwDBaHftDV+Dmu8=; 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=q3VZHRCCLwK++eQxPK0+aA+WnjeD+4HV+mQyfwz/7bptwzUKPLsDYwcPR0ASxHVrypEj2a XgXnwP4Ns2Jx3eeYVIV4rpST10a0bMl4SfGKvyLlwATpM8YstMisTYxEWouuF+XiJESzbR 7Kulul1+oCc9usJQZMT5tBOLGnFRgT4=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCQcgAAuQSNd@waldorf.isode.com>; Wed, 10 Feb 2021 17:48:49 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
Message-ID: <9c21efd1-e1c3-a8de-fc33-aafb6df85a7b@isode.com>
Date: Wed, 10 Feb 2021 17:48:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <161227892696.22043.1613107216198518224@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/zEYY4fzRepozrFnBoF81XTqcK7w>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 17:48:54 -0000

Hi Roman,

Replying to to the rest of your comments:

On 02/02/2021 15:15, Roman Danyliw via Datatracker wrote:
> ** Section 11.2.  Per =E2=80=9CFor this reason, IMAP4rev2 clients SHOULD t=
ry both ports
> 993 and 143 (and both IPv4 and IPv6) concurrently by default, unless overr=
iden
> [sic] by either user configuration or DNS SRV records [RFC6186]=E2=80=9D, =
is there any
> further guidance needed here to guide if say both 993 and 143 respond; or =
you
> get responses across address families?

I think I would like to stick the Happy Eyeballs reference here: RFC=20
8305 (Happy Eyeballs Version 2: Better Connectivity Using Concurrency).


Best Regards,
Alexey


From nobody Wed Feb 10 10:05:58 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C5E83A1125; Wed, 10 Feb 2021 10:05:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161298035345.8531.2111143217090410633@ietfa.amsl.com>
Date: Wed, 10 Feb 2021 10:05:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/x8ABjsaQK2GgTyUjrLaWVbgFD_g>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-28.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 18:05:54 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Internet Message Access Protocol (IMAP) - Version 4rev2
        Authors         : Alexey Melnikov
                          Barry Leiba
	Filename        : draft-ietf-extra-imap4rev2-28.txt
	Pages           : 169
	Date            : 2021-02-10

Abstract:
   The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2)
   allows a client to access and manipulate electronic mail messages on
   a server.  IMAP4rev2 permits manipulation of mailboxes (remote
   message folders) in a way that is functionally equivalent to local
   folders.  IMAP4rev2 also provides the capability for an offline
   client to resynchronize with the server.

   IMAP4rev2 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing,
   searching, and selective fetching of message attributes, texts, and
   portions thereof.  Messages in IMAP4rev2 are accessed by the use of
   numbers.  These numbers are either message sequence numbers or unique
   identifiers.

   IMAP4rev2 does not specify a means of posting mail; this function is
   handled by a mail submission protocol such as the one specified in
   RFC 6409.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-28
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-28

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-28


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Feb 10 10:14:15 2021
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 BB5B53A1234 for <extra@ietfa.amsl.com>; Wed, 10 Feb 2021 10:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6Ai32sr5QwUK for <extra@ietfa.amsl.com>; Wed, 10 Feb 2021 10:14:12 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 10B0B3A1232 for <extra@ietf.org>; Wed, 10 Feb 2021 10:14:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612980851; d=isode.com; s=june2016; i=@isode.com; bh=IUyyRZn0Hya90JAodLBvKVLxvJEwHnywrByqIHTK82w=; 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=nctqsU6NwMnogc9OpBCvuKW6lZkmK4HF5lh1KhTlGtTyfn2Jmao5g0EZYTxyAeSgMxykot WHoNKr1aWiStRvvCW/He1cIJvmNYb9+iHhoUL47aSAucHuxaiHB5TEF0re+6px4RNgdrSH bMWQvtIPhnDTBSEvHo9PjaRV9rAR4dk=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCQicgAuQZZ3@waldorf.isode.com>; Wed, 10 Feb 2021 18:14:11 +0000
To: extra@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
References: <161298035345.8531.2111143217090410633@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <d1a0352a-6649-4dec-d49b-8facc1f536ea@isode.com>
Date: Wed, 10 Feb 2021 18:14:11 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <161298035345.8531.2111143217090410633@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/dva6U9iZ4kbFJxfFx64kTxFBokA>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-28.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 18:14:14 -0000

On 10/02/2021 18:05, internet-drafts@ietf.org wrote:

> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-28
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-28
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-28

This version addressed most of comments from Ben's IESG review and also 
changed domain names in one APPEND example as per Alissa's IESG review 
comment.

I am planning to do another smaller revision to address remaining 
comments from Ben. At this point I think we will be done :-)!



From nobody Wed Feb 10 10:19:07 2021
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 66FAD3A1281; Wed, 10 Feb 2021 10:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 315rQgRTCGaM; Wed, 10 Feb 2021 10:19:04 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 21D633A1273; Wed, 10 Feb 2021 10:19:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612981143; d=isode.com; s=june2016; i=@isode.com; bh=BG98ospEs4HY95Awaz0paYO1xfXzNWH9KNMyPywwyaU=; 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=S8DwoSrGl59GfegldlUH2nTeh4G9g0pnbPwBqo0u/NeeA4iQu75DZS97/41yX4CCqyLM5L KZDPXphHChmb47+0CkLCNoXMkGG+JpBMoj6gRhO2NMJzSC805uk0gNZ+Rx6tTT66pHQSjS HW59x4NZbHMi75O5g3WwFvdg87Q3wNQ=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCQjlgAuQRt8@waldorf.isode.com>; Wed, 10 Feb 2021 18:19:03 +0000
To: Barry Leiba <barryleiba@computer.org>, Alissa Cooper <alissa@cooperw.in>
Cc: extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>, draft-ietf-extra-imap4rev2@ietf.org, IESG <iesg@ietf.org>, extra-chairs@ietf.org
References: <161228843386.9750.10522178607825201429@ietfa.amsl.com> <CALaySJJqMMR4er0Qz+pccOEKe0+F+ABiBSijifOyc3dK7ZqvhA@mail.gmail.com> <9D024588-53BA-47AD-9AFD-46E2E9C350BD@cooperw.in> <CALaySJLNnD0gJyjsMjQODC_vKLFQPJMf_oBnfp_hS2nrSD+2Tg@mail.gmail.com> <470EB1D6-0D84-4DC2-A483-56F9B9C76DA3@cooperw.in> <CALaySJKms8fXb=skNfXNCVf1o0uwaQZ10Aj1a+sdyZuN4-eV_Q@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <a709f4bc-95b7-d85f-6de8-52f695256310@isode.com>
Date: Wed, 10 Feb 2021 18:19:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <CALaySJKms8fXb=skNfXNCVf1o0uwaQZ10Aj1a+sdyZuN4-eV_Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/Sp8CaAcjJSxOom0mX4AJ93OujYU>
Subject: Re: [Extra] Alissa Cooper's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 18:19:06 -0000

Hi all,

On 04/02/2021 17:38, Barry Leiba wrote:
>>> Do you think it's worth the risk of introducing errors (point 1)?
>> I=E2=80=99m not sure I understand it well enough. If you substitute value=
s that are the same length in
>> characters as the old values, is this still a problem? I.e., if you padde=
d examples with numbers
>> ("example123456=E2=80=9D) or something along those lines, does that help?
> That sounds workable; I don't think we have any digital signatures,
> which would still break, but I don't think we need to worry about
> that.  Let me talk it over with Alexey.

I changed example domains to end with .example. I think this both=20
preserves Mark's original intent and also uses example domains. It=20
turned out that there was only one example that needed recalculating=20
literal length.

Best Regards,

Alexey


From nobody Thu Feb 11 06:12:57 2021
Return-Path: <rdd@cert.org>
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 0E65D3A1622; Thu, 11 Feb 2021 06:12:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 c_3mTe9AsUBF; Thu, 11 Feb 2021 06:12:54 -0800 (PST)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 BFFB33A1623; Thu, 11 Feb 2021 06:12:54 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 11BECjBU006713; Thu, 11 Feb 2021 09:12:45 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 11BECjBU006713
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1613052765; bh=50tFrF04H3H3mXigLFthIXN246SgJgwh/FDRIeqUotk=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=XdkqtbqIxlGJf9u1ti7y//9cPaemmVk+dmclDC/Ad2MrAQE5+lyN2qw/VcMPjNiXC Dm0MrRLIn/6Pku5aBF6NrI+5xL3/n6hyetwHhe6A/w/jwNS0ZpN9S/LzR47lRqeugH vRcHSmGkoGabbaak3NVOD8NLlC45X7T7UOhFD5F4=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 11BECgFV033271; Thu, 11 Feb 2021 09:12:42 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 11 Feb 2021 09:12:41 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Thu, 11 Feb 2021 09:12:41 -0500
From: Roman Danyliw <rdd@cert.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
CC: "extra@ietf.org" <extra@ietf.org>, "brong@fastmailteam.com" <brong@fastmailteam.com>, "draft-ietf-extra-imap4rev2@ietf.org" <draft-ietf-extra-imap4rev2@ietf.org>, "extra-chairs@ietf.org" <extra-chairs@ietf.org>
Thread-Topic: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
Thread-Index: AQHW/9UAtIyMg1OcRkeucfzshDC8JqpTAAvw
Date: Thu, 11 Feb 2021 14:12:40 +0000
Message-ID: <d1f9c166fddd4db4a96ad18f48849941@cert.org>
References: <161227892696.22043.1613107216198518224@ietfa.amsl.com> <9c21efd1-e1c3-a8de-fc33-aafb6df85a7b@isode.com>
In-Reply-To: <9c21efd1-e1c3-a8de-fc33-aafb6df85a7b@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.203.134]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/7EUDJSV-7p6_aX-LoxomtsoRwjI>
Subject: Re: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Feb 2021 14:12:56 -0000

SGkgQWxleGV5IQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEFsZXhl
eSBNZWxuaWtvdiA8YWxleGV5Lm1lbG5pa292QGlzb2RlLmNvbT4NCj4gU2VudDogV2VkbmVzZGF5
LCBGZWJydWFyeSAxMCwgMjAyMSAxMjo0OSBQTQ0KPiBUbzogUm9tYW4gRGFueWxpdyA8cmRkQGNl
cnQub3JnPjsgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+DQo+IENjOiBleHRyYUBpZXRmLm9yZzsg
YnJvbmdAZmFzdG1haWx0ZWFtLmNvbTsgZHJhZnQtaWV0Zi1leHRyYS0NCj4gaW1hcDRyZXYyQGll
dGYub3JnOyBleHRyYS1jaGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtFeHRyYV0gUm9t
YW4gRGFueWxpdydzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLWV4dHJhLQ0KPiBpbWFwNHJl
djItMjY6ICh3aXRoIENPTU1FTlQpDQo+IA0KPiBIaSBSb21hbiwNCj4gDQo+IFJlcGx5aW5nIHRv
IHRvIHRoZSByZXN0IG9mIHlvdXIgY29tbWVudHM6DQo+IA0KPiBPbiAwMi8wMi8yMDIxIDE1OjE1
LCBSb21hbiBEYW55bGl3IHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCj4gPiAqKiBTZWN0aW9uIDEx
LjIuICBQZXIg4oCcRm9yIHRoaXMgcmVhc29uLCBJTUFQNHJldjIgY2xpZW50cyBTSE9VTEQgdHJ5
DQo+ID4gYm90aCBwb3J0cw0KPiA+IDk5MyBhbmQgMTQzIChhbmQgYm90aCBJUHY0IGFuZCBJUHY2
KSBjb25jdXJyZW50bHkgYnkgZGVmYXVsdCwgdW5sZXNzDQo+ID4gb3ZlcnJpZGVuIFtzaWNdIGJ5
IGVpdGhlciB1c2VyIGNvbmZpZ3VyYXRpb24gb3IgRE5TIFNSViByZWNvcmRzDQo+ID4gW1JGQzYx
ODZd4oCdLCBpcyB0aGVyZSBhbnkgZnVydGhlciBndWlkYW5jZSBuZWVkZWQgaGVyZSB0byBndWlk
ZSBpZiBzYXkNCj4gPiBib3RoIDk5MyBhbmQgMTQzIHJlc3BvbmQ7IG9yIHlvdSBnZXQgcmVzcG9u
c2VzIGFjcm9zcyBhZGRyZXNzIGZhbWlsaWVzPw0KPiANCj4gSSB0aGluayBJIHdvdWxkIGxpa2Ug
dG8gc3RpY2sgdGhlIEhhcHB5IEV5ZWJhbGxzIHJlZmVyZW5jZSBoZXJlOiBSRkMNCj4gODMwNSAo
SGFwcHkgRXllYmFsbHMgVmVyc2lvbiAyOiBCZXR0ZXIgQ29ubmVjdGl2aXR5IFVzaW5nIENvbmN1
cnJlbmN5KS4NCg0KTWFrZXMgc2Vuc2UgdG8gbWUuDQoNClJlZ2FyZHMsDQpSb21hbg0K


From nobody Fri Feb 12 16:35:21 2021
Return-Path: <agenda@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 506C93A11C3; Fri, 12 Feb 2021 16:33:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <brong@fastmailteam.com>, <extra-chairs@ietf.org>
Cc: barryleiba@computer.org, extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161317640231.31337.781584336784081125@ietfa.amsl.com>
Date: Fri, 12 Feb 2021 16:33:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/-jX7Xb_c6umEb72ySjwR3c244k8>
Subject: [Extra] extra - Requested session has been scheduled for IETF 110
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 13 Feb 2021 00:33:31 -0000

Dear Bron Gondwana,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    extra Session 1 (1:00 requested)
    Friday, 12 March 2021, Session II 1530-1630
    Room Name: Room 1 size: 501
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/110/sessions/extra.ics

Request Information:


---------------------------------------------------------
Working Group Name: Email mailstore and eXtensions To Revise or Amend
Area Name: Applications and Real-Time Area
Session Requester: Bron Gondwana


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 15
Conflicts to Avoid: 
 Chair Conflict: jmap calext dispatch
 Technology Overlap: emailcore dmarc






People who must be present:
  Alexey Melnikov
  Barry Leiba
  Bron Gondwana
  Jiankang Yao

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Sat Feb 13 08:41:46 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 247033A0E22; Sat, 13 Feb 2021 08:41:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161323450499.28425.9810173656801622840@ietfa.amsl.com>
Date: Sat, 13 Feb 2021 08:41:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/bLk7gDP55Y3C2ENRGhOCoVROkPc>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 13 Feb 2021 16:41:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Internet Message Access Protocol (IMAP) - Version 4rev2
        Authors         : Alexey Melnikov
                          Barry Leiba
	Filename        : draft-ietf-extra-imap4rev2-29.txt
	Pages           : 174
	Date            : 2021-02-13

Abstract:
   The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2)
   allows a client to access and manipulate electronic mail messages on
   a server.  IMAP4rev2 permits manipulation of mailboxes (remote
   message folders) in a way that is functionally equivalent to local
   folders.  IMAP4rev2 also provides the capability for an offline
   client to resynchronize with the server.

   IMAP4rev2 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing,
   searching, and selective fetching of message attributes, texts, and
   portions thereof.  Messages in IMAP4rev2 are accessed by the use of
   numbers.  These numbers are either message sequence numbers or unique
   identifiers.

   IMAP4rev2 does not specify a means of posting mail; this function is
   handled by a mail submission protocol such as the one specified in
   RFC 6409.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-29
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-29

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-29


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Sat Feb 13 08:46:57 2021
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 0DC393A0E2D for <extra@ietfa.amsl.com>; Sat, 13 Feb 2021 08:46:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 PA3akE-fxtnd for <extra@ietfa.amsl.com>; Sat, 13 Feb 2021 08:46:53 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id B98293A0E2A for <extra@ietf.org>; Sat, 13 Feb 2021 08:46:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613234811; d=isode.com; s=june2016; i=@isode.com; bh=teUjj1OUp47wPCTrVAwHWoY5ZwkYgo+bnD5Er9/aJlU=; 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=uZL6Sie/jR1mQpLLlZpEzo9u586UsmYOMN5dMDAeke4eS1teEmFdsOm+jlGY3OYvtnvkU0 ps3BSH7WztmGLFmCFncwqsO8GHwAYymeAqPfVOUYOS0QQ6v766S6+/SKct+7xiV+w3nM3i huPdTp4YWJPdUZbcWRexvx8M+kpCWYU=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCgCewAuQVUQ@waldorf.isode.com>; Sat, 13 Feb 2021 16:46:51 +0000
To: extra@ietf.org
References: <161323450499.28425.9810173656801622840@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com>
Date: Sat, 13 Feb 2021 16:46:51 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161323450499.28425.9810173656801622840@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/2KwX852trRPbCSdfktkXkWTBwEk>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 13 Feb 2021 16:46:55 -0000

On 13/02/2021 16:41, internet-drafts@ietf.org wrote:

> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-29
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-29
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-29

This version addresses almost all remaining comments from Ben's IESG 
review. It also cleans up language about which capabilities are required 
on cleartext and which are required on implicit TLS port. And finally I 
updated a NAMESPACE related example to show use of special-use mailbox 
attributes to determine what mailbox names to create for sent and 
deleted mail.



From nobody Sat Feb 13 08:50:03 2021
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 6F38E3A0E2E; Sat, 13 Feb 2021 08:50:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Hvgo0IPyzIb1; Sat, 13 Feb 2021 08:50:00 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 166523A0E2A; Sat, 13 Feb 2021 08:50:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613234999; d=isode.com; s=june2016; i=@isode.com; bh=WsTXl+N+97ebBmBGaYH8CGEh14HtyUtz+BnhRPWD/nw=; 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=CucuPGHkiCY8nM6v6OLeptlnkYo5Xx3nyIH83R3KFsXAlLjQB0+9aSqdcsAE9bBwe5vk28 WmsCDWFMI0FDEsC5g1h9tPe8JlsG37BalTVPAihflXIYxsGlC7QIo0QF4Jrux51CU0/hmN nNp07/ceosH6KuQyn0fPzi5RIn23GnU=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCgDNgAuQY0S@waldorf.isode.com>; Sat, 13 Feb 2021 16:49:59 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
Message-ID: <85dae5da-0606-83b0-5e2d-629f3477d35e@isode.com>
Date: Sat, 13 Feb 2021 16:49:58 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161243121159.6909.2386107317688674630@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/Juj6NmGHDgaR0zQTM4cnT8ebjYU>
Subject: Re: [Extra] Benjamin Kaduk's No Objection on draft-ietf-extra-imap4rev2-27: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 13 Feb 2021 16:50:02 -0000

Hi Ben,

Thank you again for your extensive comments! Replying to a few more of 
your comments below:

On 04/02/2021 09:33, Benjamin Kaduk via Datatracker wrote:

> Section 8
>
>     The following is a transcript of an IMAP4rev2 connection on a non TLS
>     port.  A long line in this sample is broken for editorial clarity.
>
> More than one line, now.
>
> C:   A001 AUTHENTICATE SCRAM-SHA-256
>        biwsbj11c2VyLHI9ck9wck5HZndFYmVSV2diTkVrcU8=
> S:   + cj1yT3ByTkdmd0ViZVJXZ2JORWtxTyVodllEcFdVYTJSYVRDQWZ1eEZJbGopaE5s
>       RiRrMCxzPVcyMlphSjBTTlk3c29Fc1VFamI2Z1E9PSxpPTQwOTYNCg==
> C:   Yz1iaXdzLHI9ck9wck5HZndFYmVSV2diTkVrcU8laHZZRHBXVWEyUmFUQ0FmdXhG
>       SWxqKWhObEYkazAscD1kSHpiWmFwV0lrNGpVaE4rVXRlOXl0YWc5empmTUhnc3Ft
>       bWl6N0FuZFZRPQ==
> S:   + dj02cnJpVFJCaTIzV3BSUi93dHVwK21NaFVaVW4vZEI1bkxUSlJzamw5NUc0PQ==
>
> These correspond quite nicely to (base64'd copies of) the example in RFC
> 7677, with the exception of the first server line, that includes an
> additional CRLF in the decoded data.
Well spotted :-). Fixed.
> Section 11
>
> It might be worth putting in some bromide about how while md5 is used
> in the BODYSTRUCTURE response, the usage is not particularly security
> relevant and so there is not a vulnerability due to its use.
You suggested some text and I used a version of it. Thank you.
> Section 13.1
>
> It's not clear to me that [ANONYMOUS] is referenced in a manner that
> requires classification as normative; likewise for [SCRAM-SHA-256].

SCRAM has a SHOULD level requirement, even if conditional. I don't think 
it matters that much.

But I agree about ANONYMOUS.

> Similarly, if we use a modified form of [UTF-7] that we describe in
> whole ourselves, that does not seem to be normative.



From nobody Mon Feb 15 04:16:29 2021
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 E50773A125D for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 04:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YHFOrQEioX9G for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 04:16:16 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8B83A1287 for <extra@ietf.org>; Mon, 15 Feb 2021 04:16:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613391373; d=isode.com; s=june2016; i=@isode.com; bh=hy+Mu1LEvN2R949uRBmW11Bt/QnD3lsZwzjeOcihZyE=; 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=C79Yo6X9fTSVsyKEXyXK56gaiz7b6wE/8rRHn4iKx+pYwB7+Q9KqDEi3QvFoy/NOdAuoZK WgNGWZMRrCfdyo0gp2YReroUBB8NnBJOEdEz3L8/sDbKE1U+vEk+OsXAJPcH/Ol773K/cU PWQr2NMpf9bKujgJGnsYuEQiiINKPhw=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCpmDQAuQRcJ@waldorf.isode.com>; Mon, 15 Feb 2021 12:16:13 +0000
To: extra@ietf.org
References: <161116825043.14636.11363330782678240238@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5d2d644d-115b-a21b-203b-7c2bc3259b39@isode.com>
Date: Mon, 15 Feb 2021 12:16:12 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161116825043.14636.11363330782678240238@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/e-O76-39Vfj4QQMZg0CK2X6API4>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-25.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2021 12:16:28 -0000

Hi all,

On 20/01/2021 18:44, internet-drafts@ietf.org wrote:

> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-25
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-25
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-25

I know I am doing this out of the order, but I missed summarizing 
changes in this revision, which are pretty significant:

1) Clarified that the list of capabilities can change after STARTTLS, 
AUTHENTICATE, LOGIN.

2) Added prohibition to use ALERT before STARTTLS/SASL security layer, 
as this can be used by MITM attackers against clients.

3) Added a new requirements on clients that require TLS when they see 
PREAUTH on a cleartext port. As PREAUTH response forces the client to 
bypass STARTTLS command, such clients are required to close the connection.

4) Added a new Security Consideration subsection talking about 
unsolicited responses received in wrong states and that clients must 
ignore them. For example, LIST received before autentication must be 
ignored. Similar EXISTS/FLAGS/FETCH received when there is no mailbox 
selected.

5) Added new requirement that servers MUST implement implicit TLS port 
handling (993) and SHOULD implement cleartext port with STARTTLS. 
(Clients MUST implement both.) This seems to match what many ISPs are doing.

6) Added missing IANA registrations.

7) Some minor ABNF clarifications (added pointers for some ABNF 
productions imported from other documents).

8) Some minor wording changes for clarity.

Best Regards,

Alexey


From nobody Mon Feb 15 05:11:28 2021
Return-Path: <timo@sirainen.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 1D4243A0922 for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tC7Hg-BhNkJ1 for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:11:25 -0800 (PST)
Received: from sirainen.com (mail.sirainen.com [94.237.26.55]) by ietfa.amsl.com (Postfix) with ESMTP id 3613E3A091C for <extra@ietf.org>; Mon, 15 Feb 2021 05:11:24 -0800 (PST)
Received: from [192.168.10.120] (unknown [213.114.248.18]) by sirainen.com (Postfix) with ESMTPSA id CF5B82B3C7D; Mon, 15 Feb 2021 13:11:21 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Timo Sirainen <timo@sirainen.com>
In-Reply-To: <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com>
Date: Mon, 15 Feb 2021 14:11:21 +0100
Cc: extra@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7C420EC-068A-422F-9F6C-F76646701E55@sirainen.com>
References: <161323450499.28425.9810173656801622840@ietfa.amsl.com> <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/VfdTz0U08AGMS0Ht-BvNZSajnCc>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2021 13:11:27 -0000

On 13. Feb 2021, at 17.46, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:
>=20
> On 13/02/2021 16:41, internet-drafts@ietf.org wrote:
>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>>=20
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-29
>> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-29
>>=20
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-extra-imap4rev2-29
>=20
> This version addresses almost all remaining comments from Ben's IESG =
review. It also cleans up language about which capabilities are required =
on cleartext and which are required on implicit TLS port. And finally I =
updated a NAMESPACE related example to show use of special-use mailbox =
attributes to determine what mailbox names to create for sent and =
deleted mail.

This is a bit confusing:

>    The client is configured to save a copy of all mail sent by the =
user
>    into a mailbox with the \Sent attribute.  Furthermore, after a
>    message is deleted from a mailbox, the client is configured to move
>    that message to a mailbox with the \Trash attribute.  The server
>    signals specific mailbox names that should be used for these =
purposed
>    by returning LIST responses with \NonExistent attribute.  I.e. the
>    server is hinting to the client which mailbox names to use for sent
>    and deleted messages.

Especially the sentence "The server signals specific mailbox names that =
should be used for these purposed by returning LIST responses with =
\NonExistent attribute" was very confusing to me. It should rather say =
something that the \NonExistent signals that the folders don't exist =
yet, and that it's possible to create any one of them and then they =
could be used for the \Sent or \Trash purposes. After they are created =
the \NonExistent would drop away.

Although I've a feeling many clients won't be able to handle this kind =
of multiple namespaces properly anyway. And I've a feeling that even =
seeing (\NonExistent \Trash) LIST reply is going to confuse them.


From nobody Mon Feb 15 05:16:42 2021
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 518693A0930 for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YPbO38XJxkRV for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:16:40 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id CDB3B3A0927 for <extra@ietf.org>; Mon, 15 Feb 2021 05:16:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613394998; d=isode.com; s=june2016; i=@isode.com; bh=9ndFBOUVb38Qm5/gcg7fz66qnjLgocVA8vu2WPuwTYk=; 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=O4XOtT+S+4NvQs9kpxj/daQt1IWbsnnnHLAK1j5uWE/j+ajPuOkW/IhkLFnIkyr5h59V0z 5LVd5UxIv2MWX3WfYeAIbv/Zr1aHOtY7p3Voo0D/PpFSUuhgITLSvaqJOXzIw79QT26Z5W 3hpIA9uQOupM1xqcPuzYvhXaYPZ+naU=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCp0NQAuQRGy@waldorf.isode.com>; Mon, 15 Feb 2021 13:16:38 +0000
To: Timo Sirainen <timo@sirainen.com>
Cc: extra@ietf.org
References: <161323450499.28425.9810173656801622840@ietfa.amsl.com> <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com> <A7C420EC-068A-422F-9F6C-F76646701E55@sirainen.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <aa74727b-4342-e625-33a6-b0861b4b2e61@isode.com>
Date: Mon, 15 Feb 2021 13:16:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <A7C420EC-068A-422F-9F6C-F76646701E55@sirainen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/RsWA-Ptr1bfUmZrOY2rg47Bk6Qc>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2021 13:16:41 -0000

Hi Timo,

On 15/02/2021 13:11, Timo Sirainen wrote:

> On 13. Feb 2021, at 17.46, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
>> On 13/02/2021 16:41, internet-drafts@ietf.org wrote:
>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-29
>>> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-29
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-29
>> This version addresses almost all remaining comments from Ben's IESG review. It also cleans up language about which capabilities are required on cleartext and which are required on implicit TLS port. And finally I updated a NAMESPACE related example to show use of special-use mailbox attributes to determine what mailbox names to create for sent and deleted mail.
> This is a bit confusing:
>
>>     The client is configured to save a copy of all mail sent by the user
>>     into a mailbox with the \Sent attribute.  Furthermore, after a
>>     message is deleted from a mailbox, the client is configured to move
>>     that message to a mailbox with the \Trash attribute.  The server
>>     signals specific mailbox names that should be used for these purposed
>>     by returning LIST responses with \NonExistent attribute.  I.e. the
>>     server is hinting to the client which mailbox names to use for sent
>>     and deleted messages.
> Especially the sentence "The server signals specific mailbox names that should be used for these purposed by returning LIST responses with \NonExistent attribute" was very confusing to me. It should rather say something that the \NonExistent signals that the folders don't exist yet, and that it's possible to create any one of them and then they could be used for the \Sent or \Trash purposes. After they are created the \NonExistent would drop away.
Fine, I can reword as you suggest.
> Although I've a feeling many clients won't be able to handle this kind of multiple namespaces properly anyway.
This is probably true and I am not sure much can be done about that.
> And I've a feeling that even seeing (\NonExistent \Trash) LIST reply is going to confuse them.

This is not really a new problem for IMAP4rev2. I suspect clients that 
want to support this, but don't at the moment, would need to be updated.

I coded this in our client, because this is the only way to announce 
special use mailbox names, when the server doesn't support special use 
mailbox creation.

Best Regards,

Alexey


From nobody Mon Feb 15 05:23:42 2021
Return-Path: <timo@sirainen.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 ACB4B3A0990 for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IP1QyRP7TAtm for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:23:37 -0800 (PST)
Received: from sirainen.com (mail.sirainen.com [94.237.26.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9477E3A098C for <extra@ietf.org>; Mon, 15 Feb 2021 05:23:37 -0800 (PST)
Received: from [192.168.10.120] (unknown [213.114.248.18]) by sirainen.com (Postfix) with ESMTPSA id B6F622B3C7D; Mon, 15 Feb 2021 13:23:36 +0000 (UTC)
From: Timo Sirainen <timo@sirainen.com>
Message-Id: <731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D15E061B-5E01-47B1-B458-F85AD42F08AD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Mon, 15 Feb 2021 14:23:36 +0100
In-Reply-To: <aa74727b-4342-e625-33a6-b0861b4b2e61@isode.com>
Cc: extra@ietf.org
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <161323450499.28425.9810173656801622840@ietfa.amsl.com> <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com> <A7C420EC-068A-422F-9F6C-F76646701E55@sirainen.com> <aa74727b-4342-e625-33a6-b0861b4b2e61@isode.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/OQ4D--2sQheQfaxc2_YV_2DAawA>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2021 13:23:41 -0000

--Apple-Mail=_D15E061B-5E01-47B1-B458-F85AD42F08AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 15. Feb 2021, at 14.16, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:
>=20
>> And I've a feeling that even seeing (\NonExistent \Trash) LIST reply =
is going to confuse them.
>=20
> This is not really a new problem for IMAP4rev2. I suspect clients that =
want to support this, but don't at the moment, would need to be updated.
>=20
> I coded this in our client, because this is the only way to announce =
special use mailbox names, when the server doesn't support special use =
mailbox creation.

I'm not sure what you mean by this. When server doesn't support =
CREATE-SPECIAL-USE? Dovecot only returns special-use for existing =
mailboxes. So you can configure it to e.g. use Trash folder for \Trash, =
but LIST returns it only when Trash actually exists. The more common =
configuration also sets the special-use folders to be autocreated, so =
LIST always returns them as if they already exist. I'm not sure what =
benefit there would be for having a configuration that returns them in =
LIST reply as \NonExistent, except for this kind of a multi-namespace =
setup that is likely gone with the UW-IMAP server (although Dovecot can =
be configured that way as well, but I don't see why anyone would).


--Apple-Mail=_D15E061B-5E01-47B1-B458-F85AD42F08AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
15. Feb 2021, at 14.16, Alexey Melnikov &lt;<a =
href=3D"mailto:alexey.melnikov@isode.com" =
class=3D"">alexey.melnikov@isode.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">And I've a feeling that even seeing =
(\NonExistent \Trash) LIST reply is going to confuse them.<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">This is not really a new problem for IMAP4rev2. I suspect =
clients that want to support this, but don't at the moment, would need =
to be updated.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I coded this in our client, because this is the only way to =
announce special use mailbox names, when the server doesn't support =
special use mailbox creation.</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">I'm not sure what you mean by this. When =
server doesn't support CREATE-SPECIAL-USE? Dovecot only returns =
special-use for existing mailboxes. So you can configure it to e.g. use =
Trash folder for \Trash, but LIST returns it only when Trash actually =
exists. The more common configuration also sets the special-use folders =
to be autocreated, so LIST always returns them as if they already exist. =
I'm not sure what benefit there would be for having a configuration that =
returns them in LIST reply as \NonExistent, except for this kind of a =
multi-namespace setup that is likely gone with the UW-IMAP server =
(although Dovecot can be configured that way as well, but I don't see =
why anyone would).</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_D15E061B-5E01-47B1-B458-F85AD42F08AD--


From nobody Mon Feb 15 05:33:57 2021
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 575C73A084A for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 K_v1nQbVZBlt for <extra@ietfa.amsl.com>; Mon, 15 Feb 2021 05:33:53 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4B13A09B5 for <extra@ietf.org>; Mon, 15 Feb 2021 05:33:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613396032; d=isode.com; s=june2016; i=@isode.com; bh=BDiDQ1xwCU5Au1wWmtg6gDWxNdyYFCa5gyx1wKpKn8U=; 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=SzInEahV/L5LBI0h/jShE0zY5XVwU1e7+Qz1wExJFgfakMH7d8PCpIfS85YsyVvf2G1udb v4zgpSjALEZqWNQwbhxx8obpJ70eBlaidXN+e7x1HZ4g0Co8tNX7QuZbwwTQ6yIDEnwAnE 1dKvk+ayF+58kQt/UsuW9wAEkjmmkos=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YCp4PwAuQabW@waldorf.isode.com>; Mon, 15 Feb 2021 13:33:52 +0000
To: Timo Sirainen <timo@sirainen.com>
Cc: extra@ietf.org
References: <161323450499.28425.9810173656801622840@ietfa.amsl.com> <5b878cb0-5aa7-e388-2f6b-3171782b98be@isode.com> <A7C420EC-068A-422F-9F6C-F76646701E55@sirainen.com> <aa74727b-4342-e625-33a6-b0861b4b2e61@isode.com> <731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <538041af-1a8b-8011-ee07-95f8f151a508@isode.com>
Date: Mon, 15 Feb 2021 13:33:51 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------E0DAF790C49DECFEDB8CFA7B"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/koHzS09BrV826vxImAp89Pr-mHQ>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-29.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2021 13:33:55 -0000

This is a multi-part message in MIME format.
--------------E0DAF790C49DECFEDB8CFA7B
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 15/02/2021 13:23, Timo Sirainen wrote:

> On 15. Feb 2021, at 14.16, Alexey Melnikov <alexey.melnikov@isode.com 
> <mailto:alexey.melnikov@isode.com>> wrote:
>>
>>> And I've a feeling that even seeing (\NonExistent \Trash) LIST reply 
>>> is going to confuse them.
>>
>> This is not really a new problem for IMAP4rev2. I suspect clients 
>> that want to support this, but don't at the moment, would need to be 
>> updated.
>>
>> I coded this in our client, because this is the only way to announce 
>> special use mailbox names, when the server doesn't support special 
>> use mailbox creation.
>
> I'm not sure what you mean by this. When server doesn't support 
> CREATE-SPECIAL-USE?
Yes.
> Dovecot only returns special-use for existing mailboxes. So you can 
> configure it to e.g. use Trash folder for \Trash, but LIST returns it 
> only when Trash actually exists.
In M-Box names are globally configured, so advertised automatically for 
all users.
> The more common configuration also sets the special-use folders to be 
> autocreated, so LIST always returns them as if they already exist.
Well, that is another way of doing the same thing.
> I'm not sure what benefit there would be for having a configuration 
> that returns them in LIST reply as \NonExistent, except for this kind 
> of a multi-namespace setup that is likely gone with the UW-IMAP server 
> (although Dovecot can be configured that way as well, but I don't see 
> why anyone would).

I don't think presence of multiple namespaces actually matters for this. 
I mean special use attributes are generic useful even if a single 
namespace exists.

Best Regard,

Alexey


--------------E0DAF790C49DECFEDB8CFA7B
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>On 15/02/2021 13:23, Timo Sirainen wrote:<br>
    </p>
    <blockquote type="cite"
      cite="mid:731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      On 15. Feb 2021, at 14.16, Alexey Melnikov &lt;<a
        href="mailto:alexey.melnikov@isode.com" class=""
        moz-do-not-send="true">alexey.melnikov@isode.com</a>&gt; wrote:<br
        class="">
      <div>
        <blockquote type="cite" class=""><br
            class="Apple-interchange-newline">
          <div class="">
            <meta charset="UTF-8" class="">
            <blockquote type="cite" style="font-family: Helvetica;
              font-size: 12px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-size-adjust: auto;
              -webkit-text-stroke-width: 0px; text-decoration: none;"
              class="">And I've a feeling that even seeing (\NonExistent
              \Trash) LIST reply is going to confuse them.<br class="">
            </blockquote>
            <br style="caret-color: rgb(0, 0, 0); font-family:
              Helvetica; font-size: 12px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              text-decoration: none;" class="">
            <span style="caret-color: rgb(0, 0, 0); font-family:
              Helvetica; font-size: 12px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              text-decoration: none; float: none; display: inline
              !important;" class="">This is not really a new problem for
              IMAP4rev2. I suspect clients that want to support this,
              but don't at the moment, would need to be updated.</span><br
              style="caret-color: rgb(0, 0, 0); font-family: Helvetica;
              font-size: 12px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; text-decoration: none;"
              class="">
            <br style="caret-color: rgb(0, 0, 0); font-family:
              Helvetica; font-size: 12px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              text-decoration: none;" class="">
            <span style="caret-color: rgb(0, 0, 0); font-family:
              Helvetica; font-size: 12px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              text-decoration: none; float: none; display: inline
              !important;" class="">I coded this in our client, because
              this is the only way to announce special use mailbox
              names, when the server doesn't support special use mailbox
              creation.</span><br style="caret-color: rgb(0, 0, 0);
              font-family: Helvetica; font-size: 12px; font-style:
              normal; font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              text-decoration: none;" class="">
          </div>
        </blockquote>
      </div>
      <br class="">
      <div class="">I'm not sure what you mean by this. When server
        doesn't support CREATE-SPECIAL-USE?</div>
    </blockquote>
    Yes.<br>
    <blockquote type="cite"
      cite="mid:731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com">
      <div class="">Dovecot only returns special-use for existing
        mailboxes. So you can configure it to e.g. use Trash folder for
        \Trash, but LIST returns it only when Trash actually exists.</div>
    </blockquote>
    In M-Box names are globally configured, so advertised automatically
    for all users.<br>
    <blockquote type="cite"
      cite="mid:731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com">
      <div class="">The more common configuration also sets the
        special-use folders to be autocreated, so LIST always returns
        them as if they already exist.</div>
    </blockquote>
    Well, that is another way of doing the same thing.<br>
    <blockquote type="cite"
      cite="mid:731FA067-6C1E-4417-A993-8CA5623CAF4A@sirainen.com">
      <div class="">I'm not sure what benefit there would be for having
        a configuration that returns them in LIST reply as \NonExistent,
        except for this kind of a multi-namespace setup that is likely
        gone with the UW-IMAP server (although Dovecot can be configured
        that way as well, but I don't see why anyone would).</div>
    </blockquote>
    <p>I don't think presence of multiple namespaces actually matters
      for this. I mean special use attributes are generic useful even if
      a single namespace exists.<br>
    </p>
    <p>Best Regard,</p>
    <p>Alexey<br>
    </p>
  </body>
</html>

--------------E0DAF790C49DECFEDB8CFA7B--


From nobody Tue Feb 16 06:20:07 2021
Return-Path: <magnus.westerlund@ericsson.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 60F2E3A0D50; Tue, 16 Feb 2021 06:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 EFwfuTwtaXle; Tue, 16 Feb 2021 06:19:55 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140051.outbound.protection.outlook.com [40.107.14.51]) (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 416143A0D62; Tue, 16 Feb 2021 06:19:55 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OTkUD8LZ5icSdG6q+ZYwGLaCSdlp27EvSU6S+lctBYBpkz779bb2XElrODDA64kQ0Ug+rxr5+A1IUca4PdeoxuKnB20wpnZoXc9mTIm/Jde4kllVOxhctkaIqa358ymV9aS5usKslP2RJNJgCBnDz7Ahd6BETW+zII4QDY0pwi89wwgGzlXTh2O9HcgXNc8hWY9SzbXDsS/+zpls6hld+h9lq09SZXIb+m23Rne9tcXD4e1RBj6Sw02Cojxvh/pF2VR+4/q6bNegRIKa4fTjUqBZgIAck2vABoM1GeBq0Uitf8Ukjiuln4TwzfAdbVwY7WpVssqBcQi4AWzJHAVsAg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=f3JjW79gVOkK0daxo7oPCDuUF/8traQ5bTBZHAdxr9k=; b=QDQ+kg9eyE9fvOk6WxJ8s7vJYyu/S98XPV9MLMs4qpkff1bHQGNMI8WtZmGr0osUMzuPBa7Ti/v13Un8iufMrUP96lmb0auF8YTRBPzJkqtr9xdP33aEi3btGn6sZAQ2UwMDY+lg0xYqh1w6h0YgwRBAOpdSss35Fp5d2yoclGZeHXhYON+dH/grOpa3SqY7uR/+8839Z0t1f/WIligWxkfa6GX+9z79g/i8bQQpv+aBcnWmdiDKz5tWNrr2sb9KyRS4ZBnLud/xDeWeull86/yz+kxaGzeLDO1Qlte4H3iyD0TGWFAbGpb9gA0RHaZbeBirtwqZA1ej2EK5agS6bw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=f3JjW79gVOkK0daxo7oPCDuUF/8traQ5bTBZHAdxr9k=; b=nm0izp42RN0OtrV1S4E3Sp/YHtKDeMBtl1bhSOQIH4kJWjmR9JvJ4WDT1HRx8R6mPGG+pRRpTK3O5K0/gY0OwPDwA9/Z/p+3HwyNTbnlNBdB9DKoX2BfSteJU4BiFKSQ1KiSeXGUcVlUlD3kgdy8WI0cejHyenSycBXATx2XeLE=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (2603:10a6:7:8e::14) by HE1PR0702MB3770.eurprd07.prod.outlook.com (2603:10a6:7:84::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.19; Tue, 16 Feb 2021 14:19:49 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::910d:a18f:b2ad:7976]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::910d:a18f:b2ad:7976%5]) with mapi id 15.20.3868.020; Tue, 16 Feb 2021 14:19:49 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "brong@fastmailteam.com" <brong@fastmailteam.com>, "iesg@ietf.org" <iesg@ietf.org>
CC: "draft-ietf-extra-sieve-mailboxid@ietf.org" <draft-ietf-extra-sieve-mailboxid@ietf.org>, "extra-chairs@ietf.org" <extra-chairs@ietf.org>, "extra@ietf.org" <extra@ietf.org>, "yaojk@cnnic.cn" <yaojk@cnnic.cn>
Thread-Topic: Magnus Westerlund's Discuss on draft-ietf-extra-sieve-mailboxid-06: (with DISCUSS)
Thread-Index: AQHW0u3EMnbyRoU8okCEGHlU7jTMTKpOAF+AgA0w+bA=
Date: Tue, 16 Feb 2021 14:19:49 +0000
Message-ID: <HE1PR0702MB37724844E64224D944EC6D9095879@HE1PR0702MB3772.eurprd07.prod.outlook.com>
References: <160804212198.17646.8123862646316973469@ietfa.amsl.com> <26c6cdb3-d697-4bb5-9748-bf75c4ad109e@beta.fastmail.com>
In-Reply-To: <26c6cdb3-d697-4bb5-9748-bf75c4ad109e@beta.fastmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: fastmailteam.com; dkim=none (message not signed) header.d=none;fastmailteam.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.130.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4eb05059-5699-424f-3d85-08d8d285eb59
x-ms-traffictypediagnostic: HE1PR0702MB3770:
x-microsoft-antispam-prvs: <HE1PR0702MB3770C1B53DB0D13A0276DC1195879@HE1PR0702MB3770.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0mG0+66GNptcBD+bxq5Zkccz6aseibKmZSAdbBurHGRrloT9OtDjL4mgvgKHBtm3mM8At0aII/w1KfI10+92/zkYKFaczIcCTqvBPfeFm0Mvx5XRZuDTw4pI07k8obW4MCnwi5C3puYXIuBQl+9bEm4FVuqa+Q/dbq/doHht4cuQCRlfJ9lz9zvEzQ/VAAYJSRrrFYLR1i2Nw6Am7icbajz5EtOoOE/x5Pnpb1ojJatMDJNhpPTU6jdszfXYayjjYxhMSPczmEcK/F5RN/ere7lLqZw3lFARZXDrQxnZraPFgeONtqZqBUYHjXvTXun6UjePydq++BKR1Iz287pAYAOXGFXzkWN3qCefzZxQKJrDsEn3bRObmGM3pgQEAAWI5R0y9hRFTDtcpZ+DekDr72mtcI+Bc+3iPjAPnZT3d87pFS1gCWd3O8uB5RlbT6gcX9QLEL41+u32t2iBcWK1eJakoAXzufKlYRmCbg4UBbp1JM4K5FWWrTqCNF/qUquNEuh7HbLmVGfto26H3qF7WjDgls1tAWRhLVacOa+drIk0ktcaLjjhwuFgWGIv9mIDyV4RcUKyK+BDxC4wRwVjldcolH7WavUOgP3b6kcK/ns=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(366004)(376002)(136003)(396003)(346002)(99936003)(2906002)(52536014)(33656002)(166002)(26005)(6506007)(7696005)(5660300002)(966005)(9686003)(53546011)(66946007)(83380400001)(21615005)(478600001)(66616009)(76116006)(316002)(110136005)(54906003)(66556008)(4326008)(71200400001)(8936002)(8676002)(86362001)(66446008)(64756008)(66476007)(15650500001)(44832011)(55016002)(186003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?b3oNEWlw//YFkLZZ5echoy/mYw5G579x9TiJOpYCDAw1n15tcm6NIjt7Id9w?= =?us-ascii?Q?AC/inQNxM3O++xYyTux3NJLTCsXoeandqpJ55st02BG0MPGe4WAOtI5ww+yQ?= =?us-ascii?Q?dMwkO/18CQkFnu0+SwUj6O0oi7Gbgecg5zsCDaMqXUB6eSxTgbZu+13HehaK?= =?us-ascii?Q?oed9L7BeTpnCJybJqKMt8FJX5iU5GVLM5wzaUk8q34hNURnObQbVT6k+D8h8?= =?us-ascii?Q?6WZfL66oYFP6kgOoQTXcUAEL7PEpzR1AwOKbZqsbB5cowNfkKzF7mLZr+8gd?= =?us-ascii?Q?BgjgKQgE8YHkrEvbriYcxt8X7kTYhxvAh/NUyy99XcntuD3Ex75VCfI9IZ5U?= =?us-ascii?Q?Tv4CVLylfvrHDFEpolbWqmx8SegfUWF+vqBTRtCyy7jVoUNgTm1tq2wDrioU?= =?us-ascii?Q?zUdU+m2njBK09pQ92+4l3lQGQ4NacvIOoYJ8FAjEKI+Iho5NV67TVDNR6P5q?= =?us-ascii?Q?wAsijei3hmWgK6sl9+z9R/GoTzijgyrP6DwAqGQxai2kxQVaJNdUnHjeKlvc?= =?us-ascii?Q?gC8DZL0Hu1dguXY6IdeuoDG+rhwtJ3ATQuE1HIzERtxxhCtpTTXe1/KJf28S?= =?us-ascii?Q?9mhRVFpq0tD4GQwcd03Rf9t4+j8oz9Ho/DMamQ2Pczt/shk73a6L6UpwAZvt?= =?us-ascii?Q?f7BoEu7U/dYle5UI8MjBIdnVOih4yjVaA8hml/+WCMjEbAa4ZfXAsPCylXCr?= =?us-ascii?Q?U2w1wSnylFKPoOZzBbR5EUD5cyCBOtlWX2j3a9Up23CDLq1QOv5UngjAWPOh?= =?us-ascii?Q?rOtr0wZBNB/RFfWgqBkErIRczgZTAWXPsOxEpaA0M3WGx6nn+qqW5QKefZpS?= =?us-ascii?Q?8ujOrb0h3Tk7WMLQJ80A/rkCartkBOS6yreiNQpli/eCqmQoh3NF3rfME4t2?= =?us-ascii?Q?L4Z2bvEb6A9efwQUdbNEPyD+uu9WKzlR1GBq4lOZSUXI487AnF/d8TPhp/f1?= =?us-ascii?Q?WVjuSQe2Nkdiuu/WTdWuPyjUyjsQUvX1SyhzjDbZ9gyMuxte/4qVpD0oICjM?= =?us-ascii?Q?JkDIxasdaY06V6iFFKjhhjg/eFTYx94P+rv8TruqlhdVVQEYcyGOY9+6HA7v?= =?us-ascii?Q?2i3LdLElm2LIgBhgpkGNppu89+R9TV0pwL8j5A2g74CVOnWpRRGQrYw89tKT?= =?us-ascii?Q?hmhThprr0bFz2/n5ucnh+0ZlqyWjMq79HoxRO7hyXuyOz/id9jlAUbyltQj5?= =?us-ascii?Q?q+1ihSU5WpbQ72fGItQsbB585bUxiBoYG47UVaXohPafH7V8EZZD7ooSbw7V?= =?us-ascii?Q?XXfHJy6/zOOhPaqIXGW2IO1zwfsU4JI7BPdQG0wmSTIR5rw2nPv9TacS4KwW?= =?us-ascii?Q?OHEHxTJo0O+Z1HlfCJxrGwco?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_002E_01D70477.29D9ADF0"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3772.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4eb05059-5699-424f-3d85-08d8d285eb59
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2021 14:19:49.2993 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ayTtbpStEVmKOP1/6v/bwpj3J2nhaf6w8ReRiNRtO9qbvHYgYdn8WT7dzNvqpKezctzKFU+dkl+3szG83Rd2Py7yolSIgYNc/R5EuSvq1hQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3770
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/9Ezdou80jp3kWHSt4CMuzeHlujU>
Subject: Re: [Extra] Magnus Westerlund's Discuss on draft-ietf-extra-sieve-mailboxid-06: (with DISCUSS)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 16 Feb 2021 14:20:01 -0000

------=_NextPart_000_002E_01D70477.29D9ADF0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_002F_01D70477.29D9ADF0"


------=_NextPart_001_002F_01D70477.29D9ADF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

I was unfortunately sick last week so I didn't managed to respond before you
done the work. 

 

>From my perspective adding the references would have been better as formal
syntax if correct are very useful. I don't know enough about sieve
specifications to know if removing the formal language here is good enough
or making the specification a bit worse. My discuss was only to ensure
things was clear, and though some small wording additions and correct
references would have resolved things.

 

WG and Barry, what are your opinion on this change?

 

Cheers

 

Magnus Westerlund

 

 

 

From: Bron Gondwana <brong@fastmailteam.com> 
Sent: den 8 februari 2021 05:30
To: Magnus Westerlund <magnus.westerlund@ericsson.com>; The IESG
<iesg@ietf.org>
Cc: draft-ietf-extra-sieve-mailboxid@ietf.org; extra-chairs@ietf.org;
extra@ietf.org; Jiankang Yao <yaojk@cnnic.cn>
Subject: Re: Magnus Westerlund's Discuss on
draft-ietf-extra-sieve-mailboxid-06: (with DISCUSS)

 

On Wed, Dec 16, 2020, at 01:22, Magnus Westerlund via Datatracker wrote:

Magnus Westerlund has entered the following ballot position for

draft-ietf-extra-sieve-mailboxid-06: Discuss

 

When responding, please keep the subject line intact and reply to all

email addresses included in the To and CC lines. (Feel free to cut this

introductory paragraph, however.)

 

 

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html

for more information about IESG DISCUSS and COMMENT positions.

 

 

The document, along with other ballot positions, can be found here:

https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/

 

 

Hi Magnus,

 

Sorry for the lack of response on this - I missed it somehow at the time!

 

 

----------------------------------------------------------------------

DISCUSS:

----------------------------------------------------------------------

 

First part is a formality discuss that likely is fairly easy to resolve

 

So this document uses formal syntax, however it does not explicitly
reference

which. So I noticed RFC 5228 that do reference RFC 4234 which is now
obsolete,

and the current in force version of ABNF is RFC 5234. Also as no WSP are

included in the rules, this document appears to use ABNF to express RFC 5228

grammar and not parsing syntax. So please clarify prior to the usages what
the

formal language is and what it represents.

 

So this needs to be done prior to Section 5. But, can you please check that
you

actually have the same level of  formal syntax in Section 5 that goes
through

RFC 8580 as what is in Section 8. Otherwise please clarify both.

 

I'm happy to drop the formal language section entirely.  I just checked
RFC8579 which describes a very similar extension and it has no formal ABNF
section.  Would you be satisfied with having the ABNF dropped entirely and
using prose and descriptions similar to what's in RFC8579?

 

Secondly, I do consider the defining text first paragraph of in Section 4.1
so

hard to interpret that it must be fixed prior to publication. So although
you

already are going to address it based on discussion of Martin Duke's
comment, I

want to hold a discuss on this.

 

I will wordsmith that and post a new draft.

 

Thanks,


Bron.

 

--

  Bron Gondwana, CEO, Fastmail Pty Ltd

  brong@fastmailteam.com <mailto:brong@fastmailteam.com> 

 

 


------=_NextPart_001_002F_01D70477.29D9ADF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DSV link=3Dblue =
vlink=3Dpurple style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>I was unfortunately sick last week =
so I didn&#8217;t managed to respond before you done the work. =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>From my perspective adding the =
references would have been better as formal syntax if correct are very =
useful. I don&#8217;t know enough about sieve specifications to know if =
removing the formal language here is good enough or making the =
specification a bit worse. My discuss was only to ensure things was =
clear, and though some small wording additions and correct references =
would have resolved things.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>WG and Barry, what are your opinion =
on this change?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>Cheers<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>Magnus =
Westerlund<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US>From:</span></b><span lang=3DEN-US> Bron Gondwana =
&lt;brong@fastmailteam.com&gt; <br><b>Sent:</b> den 8 februari 2021 =
05:30<br><b>To:</b> Magnus Westerlund =
&lt;magnus.westerlund@ericsson.com&gt;; The IESG =
&lt;iesg@ietf.org&gt;<br><b>Cc:</b> =
draft-ietf-extra-sieve-mailboxid@ietf.org; extra-chairs@ietf.org; =
extra@ietf.org; Jiankang Yao &lt;yaojk@cnnic.cn&gt;<br><b>Subject:</b> =
Re: Magnus Westerlund's Discuss on draft-ietf-extra-sieve-mailboxid-06: =
(with DISCUSS)<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>On Wed, Dec 16, 2020, at 01:22, =
Magnus Westerlund via Datatracker =
wrote:<o:p></o:p></span></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt' id=3Dqt><div><p =
class=3DMsoNormal><span style=3D'font-family:"Arial",sans-serif'>Magnus =
Westerlund has entered the following ballot position =
for<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>draft-ietf-extra-sieve-mailboxid=
-06: Discuss<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>When responding, please keep =
the subject line intact and reply to =
all<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>email addresses included in the =
To and CC lines. (Feel free to cut =
this<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>introductory paragraph, =
however.)<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Please refer to&nbsp;<a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html">https:=
//www.ietf.org/iesg/statement/discuss-criteria.html</a><o:p></o:p></span>=
</p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>for more information about IESG =
DISCUSS and COMMENT positions.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>The document, along with other =
ballot positions, can be found here:<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-family:"Arial",sans-serif'><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid=
/">https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-mailboxid/</a>=
<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v></blockquote><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Hi =
Magnus,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Sorry for the lack of response =
on this - I missed it somehow at the =
time!<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt' =
id=3Dqt><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>--------------------------------=
--------------------------------------<o:p></o:p></span></p></div><div><p=
 class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>DISCUSS:<o:p></o:p></span></p></=
div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>--------------------------------=
--------------------------------------<o:p></o:p></span></p></div><div><p=
 class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>First part is a formality =
discuss that likely is fairly easy to =
resolve<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>So this document uses formal =
syntax, however it does not explicitly =
reference<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>which. So I noticed RFC 5228 =
that do reference RFC 4234 which is now =
obsolete,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>and the current in force =
version of ABNF is RFC 5234. Also as no WSP =
are<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>included in the rules, this =
document appears to use ABNF to express RFC =
5228<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>grammar and not parsing syntax. =
So please clarify prior to the usages what =
the<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>formal language is and what it =
represents.<o:p></o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>So this needs to be done prior =
to Section 5. But, can you please check that =
you<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>actually have the same level =
of&nbsp; formal syntax in Section 5 that goes =
through<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>RFC 8580 as what is in Section =
8. Otherwise please clarify =
both.<o:p></o:p></span></p></div></div></blockquote><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>I'm happy to drop the formal =
language section entirely.&nbsp; I just checked RFC8579 which describes =
a very similar extension and it has no formal ABNF section.&nbsp; Would =
you be satisfied with having the ABNF dropped entirely and using prose =
and descriptions similar to what's in =
RFC8579?<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt' =
id=3Dqt><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Secondly, I do consider the =
defining text first paragraph of in Section 4.1 =
so<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>hard to interpret that it must =
be fixed prior to publication. So although =
you<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>already are going to address it =
based on discussion of Martin Duke's comment, =
I<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>want to hold a discuss on =
this.<o:p></o:p></span></p></div></blockquote><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>I will wordsmith that and post =
a new draft.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Thanks,<o:p></o:p></span></p></d=
iv><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><br>Bron.<o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div id=3Dsig56629417><div><p =
class=3DMsoNormal>--<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp; Bron Gondwana, CEO, Fastmail Pty =
Ltd<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; <a =
href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a><o:p></o=
:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v></div></div></body></html>
------=_NextPart_001_002F_01D70477.29D9ADF0--

------=_NextPart_000_002E_01D70477.29D9ADF0
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVYzCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIF9DCCA9ygAwIBAgIP
AXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzAeFw0yMDEyMTEw
OTU4NDlaFw0yMzEyMTIwOTU4NDlaMF4xETAPBgNVBAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdu
dXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24u
Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiE+lPXXVKVAhK8iANu8bRfFrEQCH
3OYwWr37tDhg5sCE2GEQ9j2jBHRCviOHas9H+sXAqw5wZNl4/icY4WkZKkwInyWYpmvVhNiaCP7q
vFLEthyVpYbKQMCsdaLAEYLUYjI0WWcsn4kWS24Fx1mKZ07d4vULLl/7qPaGRVqQwm2XnuCJfbpX
bFHLgS2cdj8mbwbwvCglGgV7GV+m8Fe4bLEVZ/gYBQrhInryTMdJIU0VYYvYKDm8buSZeOEbcG2T
WAdVBNSM0VhGcPm93BL14kIz5dnt8rTGUpocviGipo8REujg4roedSgHJj2X2SGl9nY5g++mBovh
E5p2/F5t3QIDAQABo4IBxDCCAcAwHwYDVR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwHQYD
VR0OBBYEFCAjv/PE9BELxFJufh1bf3fTJvmfMA4GA1UdDwEB/wQEAwIFoDBVBgNVHSAETjBMMEoG
DCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVs
aWFzb25lcmEuY29tL0NQUzApBgNVHREEIjAggR5tYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5j
b20wSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25u
bGluZGl2aWR1YWxjYXYzLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjMuY2VyMA0GCSqGSIb3DQEBCwUAA4ICAQDUWV0MvpVFve7mi7gKTosZwyi6VKM/jf+T
sHf/YpZZm8UAxGNf6T7OCiUr8PPKfhd25js2/ny1DWujIv9k8PNxcxFZjt0asyrXGviPRg6UUPKF
i+4a1DyaDWnInUmS5gD+C+JMByIbxjV+H9XP6AeHwJD/8WbAAMWIu5ysXVwNp/yjFjZHs8gfQUrA
/GTkuKVlPFGmY3ea9H86jOc0G1OBD6h2vIxTEjM9VK2FzyisZehOFgN0xMNaC43JYtDVhkB8kPty
oe33usz6F3y3f9hEI69qO+rLIKKndldTMeU0R3VMsYyDDxDlWKb3HqzVAYRAZGjkPRboGHDITHPA
Re50GavobC/0+4nYOIBNrBHzXSvUQX/xFR9dBjK5m2nak8nM7Q9YFC93VUMYpOEwjMSHLbfV6rUx
h2jHsGS0AF6f7B1pVP75s/W63Ls2EPWFXeYU3p3RjFMhoVj1fyr8aLijys3axnhKlEAngcFoEAEk
DTq6U8zCcGQFf1sNxMUAox735b1EM1blNLAugBFZIKjAEyF0uoeq4yy99aY7diVfOF0YxeWn2JHE
SB07K7XKFnhbTrvxqWTYbavrXXtEL55ErI3MzFlNICpNIVwZl8BBlIprg1av1r69Jq9fHfZigOsT
zUDn5/1S+Qll2tdTrTo4/FrE8t11KcienXPWe9k5ijCCBsIwggSqoAMCAQICEFO4foPhnJkok7Cb
SRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMMFlRl
bGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUxMDI3MTIxNjQ2WjBHMQsw
CQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDs8t8AALhQ8qe72FS3
xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfSTm+7meisbhkqUXkL7fFzoe4iIZCh/VuY
UaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbXILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxz
wCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfpVdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkao
P9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2
Ot1menJpFp4zJVSfdKVgtoWqg5t2H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZ
aEIFu+hO+s0Nm8sOUMa4TlG4rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0Fd
QDEzQlnF/h1L4AK1MOkX1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA
+yrrplCh/kYvSBjvZibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUr
rvijPDaGK5FNVSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQw
gYoGCCsGAQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25l
cmEuY29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAETjBM
MEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3Qu
dGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1c3Qu
dGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsGAQUF
BwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7GZ6XnHasID3Y3OORauPb
LaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBCwUAA4ICAQBQ
WGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDUJQEPRs5QtaZiObNHCZ7mmSNMVek4
lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHGvw5RY6vRlZrj0uKvdASzYL4KMaB7m3Nw
urNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYnnl2t3D3oBX2NZCQysshUcqRdUbkS13HTCICh
MuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwfixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAq
RHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ85AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP
6Kp14/Y9XFbR/WuDj84bYNKXe4HdDc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0R
LCi+4d4/47Zs3DC3PUNOxdOEEHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZf
AFM4HoHz8K2BZRaHKWhd3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqG
ahxlHYzl/QyEG/dujp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGC
Av8wggL7AgEBMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxF
cmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwCQYFKw4DAhoFAKCC
AXowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjEwMjE2MTQxOTQ4
WjAjBgkqhkiG9w0BCQQxFgQUBOJQ88jAM/LPwVAV6VwvRN55ZUcwQwYJKoZIhvcNAQkPMTYwNDAK
BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAhowaQYJKwYB
BAGCNxAEMVwwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVy
aWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF2UT0idhk5guXXMZ6ngjBrBgsqhkiG9w0BCRAC
CzFcoFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwDQYJKoZIhvcNAQEBBQAEggEA
fw/9xV7jHTA7ts3mmtsFFjN0DEqxiWY0AgbX/dCjgSB/qBbCzN+qf9X7sa34H9lKya7s/Y8icswf
wafVCdLHrmtT5ZzF9HEcaUHACJF1nr8Z2e+QFaPs46wuXWCaPFhgl5cqLX/wtBY3Ms6ic2mm9nMp
x6/DrTqE89BAALSOfxCFtSxqXW5OveMZQKiRlt9NksZ2QhXUVimoJv+UN4KsbgAdxiDtN2bxFAu7
mfrccyV6hyFGWlPNB3O3ypIph7NfdgiXdgdc5G4z6HfhcsXHDvhufTFd/WKhjueuVDk7iZEpNp9+
S88guzMxsE0cHPNrY/JFJHi2I7nJmOxqPZOKcQAAAAAAAA==

------=_NextPart_000_002E_01D70477.29D9ADF0--


From nobody Tue Feb 16 08:30:21 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CBDFC3A0AF8; Tue, 16 Feb 2021 08:30:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161349301672.23485.2572101648354353092@ietfa.amsl.com>
Date: Tue, 16 Feb 2021 08:30:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/uwdzvHe8ZtGL0zGUSFnIeoZwfL4>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-30.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 16 Feb 2021 16:30:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Internet Message Access Protocol (IMAP) - Version 4rev2
        Authors         : Alexey Melnikov
                          Barry Leiba
	Filename        : draft-ietf-extra-imap4rev2-30.txt
	Pages           : 174
	Date            : 2021-02-16

Abstract:
   The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2)
   allows a client to access and manipulate electronic mail messages on
   a server.  IMAP4rev2 permits manipulation of mailboxes (remote
   message folders) in a way that is functionally equivalent to local
   folders.  IMAP4rev2 also provides the capability for an offline
   client to resynchronize with the server.

   IMAP4rev2 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing,
   searching, and selective fetching of message attributes, texts, and
   portions thereof.  Messages in IMAP4rev2 are accessed by the use of
   numbers.  These numbers are either message sequence numbers or unique
   identifiers.

   IMAP4rev2 does not specify a means of posting mail; this function is
   handled by a mail submission protocol such as the one specified in
   RFC 6409.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-30
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-30

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-30


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Feb 17 11:18:04 2021
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C3B3A1CDF; Wed, 17 Feb 2021 11:17:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161358947389.28071.15313172784661569764@ietfa.amsl.com>
Date: Wed, 17 Feb 2021 11:17:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/V20QiNSem3qHP1l4DJAa7-UYqSc>
Subject: [Extra] Protocol Action: 'Internet Message Access Protocol (IMAP) - Version 4rev2' to Proposed Standard (draft-ietf-extra-imap4rev2-30.txt)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Feb 2021 19:18:00 -0000

The IESG has approved the following document:
- 'Internet Message Access Protocol (IMAP) - Version 4rev2'
  (draft-ietf-extra-imap4rev2-30.txt) as Proposed Standard

This document is the product of the Email mailstore and eXtensions To Revise
or Amend Working Group.

The IESG contact persons are Murray Kucherawy and Barry Leiba.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/





Technical Summary

   The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2)
   allows a client to access and manipulate electronic mail messages on
   a server.  IMAP4rev2 permits manipulation of mailboxes (remote
   message folders) in a way that is functionally equivalent to local
   folders.  IMAP4rev2 also provides the capability for an offline
   client to resynchronize with the server.

   IMAP4rev2 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing,
   searching, and selective fetching of message attributes, texts, and
   portions thereof.  Messages in IMAP4rev2 are accessed by the use of
   numbers.  These numbers are either message sequence numbers or unique
   identifiers.

   IMAP4rev2 does not specify a means of posting mail; this function is
   handled by a mail submission protocol such as the one specified in
   RFC 6409.

Working Group Summary

  This document is very long and complex and there was a lot of discussion
  about specific points.  The discussion involved developers from many of
  the largest IMAP4 servers, as well as client authors.

  While there are tradeoffs that had to be made, there's nobody in the
  working group who has expressed unhappiness or concerns about the
  content of this document.

Document Quality

   IMAP is a widely deployed email client protocol.  This document
   presents a revision based on a consensus of extensions and clarifications
   that have become common since the previous revision was posted as
   RFC 3501 in 2003.

   The document has been closely reviewed by many expert IMAP server
   implementers.  No particular directorate or expert reviews beyond the current
   contributors and reviewers are mandated.

Personnel

   Bron Gondwana is the Document Shepherd for this document.
   Murray Kucherawy is the  Responsible Area Director.


From nobody Mon Feb 22 02:43:47 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 364213A12C3; Mon, 22 Feb 2021 02:43:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161399062511.23907.4939428912391653917@ietfa.amsl.com>
Date: Mon, 22 Feb 2021 02:43:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/LeyPs27tjspS_sHxqQr0SuTzJoE>
Subject: [Extra] I-D Action: draft-ietf-extra-quota-04.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 10:43:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : IMAP QUOTA Extension
        Author          : Alexey Melnikov
	Filename        : draft-ietf-extra-quota-04.txt
	Pages           : 18
	Date            : 2021-02-22

Abstract:
   The QUOTA extension of the Internet Message Access Protocol (RFC
   3501) permits administrative limits on resource usage (quotas) to be
   manipulated through the IMAP protocol.

   This memo obsoletes RFC 2087, but attempts to remain backwards
   compatible whenever possible.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-quota/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-quota-04
https://datatracker.ietf.org/doc/html/draft-ietf-extra-quota-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-quota-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Feb 22 03:53:26 2021
Return-Path: <timo@sirainen.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 101603A14BF for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 03:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 lLZ-iVvm778i for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 03:53:17 -0800 (PST)
Received: from sirainen.com (mail.sirainen.com [94.237.26.55]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECBF3A1471 for <extra@ietf.org>; Mon, 22 Feb 2021 03:53:11 -0800 (PST)
Received: from [192.168.10.120] (unknown [213.114.248.18]) by sirainen.com (Postfix) with ESMTPSA id 5DE0A2B3C7D for <extra@ietf.org>; Mon, 22 Feb 2021 11:53:10 +0000 (UTC)
From: Timo Sirainen <timo@sirainen.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Mon, 22 Feb 2021 12:53:09 +0100
References: <161399062511.23907.4939428912391653917@ietfa.amsl.com>
To: extra@ietf.org
In-Reply-To: <161399062511.23907.4939428912391653917@ietfa.amsl.com>
Message-Id: <7BD8AE0C-56A2-445C-8D5F-4A4566BDDFF6@sirainen.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/szUEulAo_fSAv3HCtD-CNBHjNMI>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-quota-04.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 11:53:26 -0000

On 22. Feb 2021, at 11.43, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Email mailstore and eXtensions To =
Revise or Amend WG of the IETF.
>=20
>        Title           : IMAP QUOTA Extension
>        Author          : Alexey Melnikov
> 	Filename        : draft-ietf-extra-quota-04.txt
> 	Pages           : 18
> 	Date            : 2021-02-22

This </t> looks like a bug:

                S: A003 NO [OVERQUOTA] APPEND Failed</t>

Also it's not very clear to me what clients should do about soft quota. =
If they receive untagged OVERQUOTA response, should they do something?


From nobody Mon Feb 22 05:35:07 2021
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 E0D073A09E1 for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 05:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 eoZtlN7Th5Wk for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 05:35:04 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id AACE33A09E7 for <extra@ietf.org>; Mon, 22 Feb 2021 05:35:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1614000903; d=isode.com; s=june2016; i=@isode.com; bh=bzUgGZ/h737KENwdoMO9bkwLN0VA/iAVrlXqgJEtSME=; 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=KRb+N+A1m9RO+JezuqeuOvsqF7r4yuPnFbPcL94eQKWrGmQ4EPpqgpONsFoCFHXO9cJlvE v6zSosZa4DqvHNTy2sY1vnLChL/dwYUVCGOmpNYtXbt4QVxpFRzXoal5T/C/ZxxNa/TA1e COuv5ZnebKP4R+UpvJUR9p8C2gfXAro=;
Received: from [192.168.1.222] (host31-49-142-74.range31-49.btcentralplus.com [31.49.142.74])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YDOzBgAqZsLZ@statler.isode.com>; Mon, 22 Feb 2021 13:35:03 +0000
To: Timo Sirainen <timo@sirainen.com>, extra@ietf.org
References: <161399062511.23907.4939428912391653917@ietfa.amsl.com> <7BD8AE0C-56A2-445C-8D5F-4A4566BDDFF6@sirainen.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c5c35b0b-d247-1be3-77be-95a855519666@isode.com>
Date: Mon, 22 Feb 2021 13:35:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
In-Reply-To: <7BD8AE0C-56A2-445C-8D5F-4A4566BDDFF6@sirainen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/wRv4Koktd5xe1K7GV1ikVjrozPY>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-quota-04.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 13:35:06 -0000

Hi Timo,

On 22/02/2021 11:53, Timo Sirainen wrote:

> On 22. Feb 2021, at 11.43, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
>>
>>         Title           : IMAP QUOTA Extension
>>         Author          : Alexey Melnikov
>> 	Filename        : draft-ietf-extra-quota-04.txt
>> 	Pages           : 18
>> 	Date            : 2021-02-22
> This </t> looks like a bug:
>
>                  S: A003 NO [OVERQUOTA] APPEND Failed</t>
Thanks, I've noticed that after I posted it. I will fix in the next update.
> Also it's not very clear to me what clients should do about soft quota. If they receive untagged OVERQUOTA response, should they do something?

I think they should check the current usage and display it with a 
warning (different text, colour, icon).

Best Regards,

Alexey


From nobody Mon Feb 22 07:50:22 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA66F3A1DF2; Mon, 22 Feb 2021 07:50:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161400900986.13873.11248030576228073367@ietfa.amsl.com>
Date: Mon, 22 Feb 2021 07:50:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/f47-7BNFH_AkrgwbtuJxktN-0bk>
Subject: [Extra] I-D Action: draft-ietf-extra-sieve-snooze-01.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 15:50:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.

        Title           : Sieve Email Filtering: Snooze Extension
        Authors         : Kenneth Murchison
                          Ricardo Signes
                          Neil Jenkins
	Filename        : draft-ietf-extra-sieve-snooze-01.txt
	Pages           : 13
	Date            : 2021-02-22

Abstract:
   This document describes the "snooze" extension to the Sieve email
   filtering language.  The "snooze" extension gives Sieve the ability
   to postpone the delivery of an incoming into a target mailbox until a
   later point in time.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-snooze/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-extra-sieve-snooze-01
https://datatracker.ietf.org/doc/html/draft-ietf-extra-sieve-snooze-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-snooze-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Feb 22 07:53:19 2021
Return-Path: <murch@fastmail.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 509913A1DB7 for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 07:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=LKCxKA1S; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZbZj8neQ
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 3pLtUpBO8SAM for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 07:53:09 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E5383A1D6B for <extra@ietf.org>; Mon, 22 Feb 2021 07:53:04 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 8A5D8C32 for <extra@ietf.org>; Mon, 22 Feb 2021 10:53:02 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 22 Feb 2021 10:53:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=7 xvCZgx2H2lPSKmoIiyQ02MS1z57ELbLHuDtGnBfaOk=; b=LKCxKA1SPJx/UmNuC FgcAfFiSmgGP6WzAfhUmi8iVMMzZh1EJAfqHN6d3/4rU1gxwRksML3CuL7n6oob2 pekEeBTjT/qREYN7+Mn/aJzD5cusTeKFdX3DmaM2bEpdpN3Um8GzK/5KzyxnK5Xy IsMxNFqBohaNEwK1xTouIhduewfPEaDsH6ffmSFmGd4i9Sa22SI3KiZKTDyL4fNz 1TRFyYA432UV20i6+jS8i6gV0+TMDXlGQ8U4P6D7/Jb3pdEUSYUzS4w9TAy4ktrj Ec9BL5xHY9yasRRBpDsU5bdRrAnFssSjfU66vC0clofeu/5blT9J55cLOklzvjQ7 eejeg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=7xvCZgx2H2lPSKmoIiyQ02MS1z57ELbLHuDtGnBfa Ok=; b=ZbZj8neQZU1nbudBfCZR5e173wAydzDO4RpgMwHryE9pIedBKHixVEDJU bIfAXya2tFHMjBvLpsyDYOB7KO/aRQkKBMxK1wJg2lakv2DfpmCd4lCu8QSBIx0h jiUJXdRIB8zHUhuqoyWhx3+LYf0JZzy9N4Vv6mcu8mNyyaQruPDRCBfDU4OpXHc5 WIn8wucgdgGIcrHwIHqrMFETkM+5/OjYzi/vb7JNgR1YqqsuKMuuBTVrAxzRcBpB we53ag8QLVsbVjz4Ho6EHvcnW54OabaRu9eF9PbN0eExOOOqPDCkdUzT9eAYZTxj CjbPSfkMA/eWzvydXoDT7atq/P7Uw==
X-ME-Sender: <xms:XtMzYJJKq9Qv9bfVTmB5Luk5eCidHjcMgHSsFz6vGFXRRMTUWkxkCA> <xme:XtMzYFIIfBRbL8tvux2v4SCNtEH-5bPWctnuzZ6byd_Kb-ctNDM60UKB0_tu7g2qT KbonW9i2aKd3A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeefgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvnhcuofhurhgthhhishhonhcuoehmuhhrtghhsehfrghs thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepvdeutedugeeiffeitedvhfeiud etvdegjeekkedutedvvddvudetjeevgffhvdeknecuffhomhgrihhnpehivghtfhdrohhr ghenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:XtMzYBuPQefylESaKfE15Jo5Qm-7kdZWDqSdHsWHZvPTOOHqzgRhRQ> <xmx:XtMzYKacQ_nRF37NTwHqhGbuuGnIzdcrDI0hQzESsNWdSl4y52Wgqg> <xmx:XtMzYAab0nk8gIOnsiXmKmaVXr3zsCQ3N5Ky3KtvB9ULtZbUEcKOig> <xmx:XtMzYJm1z84irGMgGXA5Mmm70IHHAAkPHU4C6rZ1vMB-nga8yJcX0Q>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 001AA240066 for <extra@ietf.org>; Mon, 22 Feb 2021 10:53:01 -0500 (EST)
To: extra@ietf.org
References: <161400900986.13873.11248030576228073367@ietfa.amsl.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <a07a9cf3-0dfe-b34b-b14f-5273668ddbb0@fastmail.com>
Date: Mon, 22 Feb 2021 10:53:01 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <161400900986.13873.11248030576228073367@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/yRPepsjHg_izmgEk3RbmRc1VfFM>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-snooze-01.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 15:53:18 -0000

This addresses issues that were discussed at IETF 109.Â  It probably 
needs more work around the implementation guidance (suggested text 
welcome), but I wanted to submit this before the blackout period.


On 2/22/21 10:50 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
>
>          Title           : Sieve Email Filtering: Snooze Extension
>          Authors         : Kenneth Murchison
>                            Ricardo Signes
>                            Neil Jenkins
> 	Filename        : draft-ietf-extra-sieve-snooze-01.txt
> 	Pages           : 13
> 	Date            : 2021-02-22
>
> Abstract:
>     This document describes the "snooze" extension to the Sieve email
>     filtering language.  The "snooze" extension gives Sieve the ability
>     to postpone the delivery of an incoming into a target mailbox until a
>     later point in time.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-snooze/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-extra-sieve-snooze-01
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-sieve-snooze-01
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-snooze-01
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Mon Feb 22 19:14:13 2021
Return-Path: <brong@fastmailteam.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 52C473A2392 for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 19:14:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=RtL9FGdy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Cw86PXXJ
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 RX7PMZls3en5 for <extra@ietfa.amsl.com>; Mon, 22 Feb 2021 19:14:10 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABF503A24F3 for <extra@ietf.org>; Mon, 22 Feb 2021 19:14:10 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id E023A5C01DD; Mon, 22 Feb 2021 22:14:09 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Mon, 22 Feb 2021 22:14:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm2; bh=3tj7 9zqLwrqrtp0WMoCxhMALBbgTJELICHLW9CUheE0=; b=RtL9FGdyjO4DXz2F5RC3 LOyHuDJ77VW8FFME2Kyf1vYH4FFPJt8bi3UB4H+FOrDR8lSlX/DtFMrYGFJmTms8 JNfQ1Y4gdfwmcu44JpMdPfgRD5yd2a7tnOj7ZRtPPKRanihd0PAG66T/FFgEmrpa 1+toREBD7oRmaNtt5ATBLuVFSQDhme2tplM+ak+Q3vI5c8QmyY82g7PTxX7SRPoF JR/H6AliuhpCv/p6vG4SJ84AU+nMQ6eUQxKVgTEi7vIvT3p8DPXRTGv3zhY0SzYm siBZ3mJViXw5cDIxG9C4w6TLptD42ptOq/5NyY1/UFNy63va4g9Syeqjdz91ZhfL KA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=3tj79z qLwrqrtp0WMoCxhMALBbgTJELICHLW9CUheE0=; b=Cw86PXXJ+HLw+PwJHT5UeX /cPgmq/+bQGqMN5WCiIV3bY+lGEgF3m9CGQTdAuwf0qBYenVrRCBh553ywm44VNM M6RVSm0s0bPmpoaePFVmT4AQgI38DuVL9gpBtfduMRSPughN/jTz66mUHKPsz6br 6CIQ8pCe5KcaqGxeiCmR0vUrVR7UmjYlzC2fxToYJ9SQMhfsLyumyhYKMFeuhkEm h1BDGQkeKA6OE8MxtfQ26TMTOxbuYoFIXVIOv2EttktES+8jmjd6wrrW5RdTJuBY VE3UEo6GR5X/Jba1O2va2gK14L5uLT8Jq22W5QgQ4mYHS/+UoBTzxzHyW3bN4O9A ==
X-ME-Sender: <xms:AXM0YF0PMFzoCJ3Guz3Qoy3xCvrEW87EuhX-jteytIkPDta1zFAxPQ> <xme:AXM0YME09oVuQWs7bpT9q1gEFmk9cMan4psCUW700gN7l-StJT3OLmv2Skho031PV fdf7nxzvH0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeeggdehjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeffveefiefgjeevteehheelgeetleetveeguedthfehgffh tdejhfdvhefhtdekgfenucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:AXM0YF40hjRhBV4jUG9HzSVzp3wpvra8xEIhcQ3utHxNJUvEQQALUg> <xmx:AXM0YC0svP9iAyDiSBCGyfdGHlLJi6Lqg6QLcVdPdNuHk5F449td7g> <xmx:AXM0YIEBj-5nF6UjcL7J-YR0L_Aqzb1y2ZBm6W_q9L2X0SvLnegdig> <xmx:AXM0YDM_tjuoBA_XIrfUlnG1T9lD8bu13nzwwdM4t7ETqNYLL61lJA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 054FD36047D; Mon, 22 Feb 2021 22:14:09 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <ba3226ac-b233-4ac8-b0dc-e38a98d686ce@beta.fastmail.com>
In-Reply-To: <c5c35b0b-d247-1be3-77be-95a855519666@isode.com>
References: <161399062511.23907.4939428912391653917@ietfa.amsl.com> <7BD8AE0C-56A2-445C-8D5F-4A4566BDDFF6@sirainen.com> <c5c35b0b-d247-1be3-77be-95a855519666@isode.com>
Date: Tue, 23 Feb 2021 14:13:47 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Cc: "Alexey Melnikov" <alexey.melnikov@isode.com>, "Timo Sirainen" <timo@sirainen.com>
Content-Type: multipart/alternative; boundary=fe932f532afc484583d281be762f5fe2
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/nSCNnp0jpyP30u67D1jYPYsOR3s>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-quota-04.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Feb 2021 03:14:12 -0000

--fe932f532afc484583d281be762f5fe2
Content-Type: text/plain

Thanks Alexey,

Other than the syntax error there, we've already had a working group last call on this document, and there's been no other feedback.

Do you need to add some "advice for clients" to capture your response to Timo in the draft?

I guess you won't be uploading the updated draft until IETF110 starts, so we can chat then about submitting it for publication then.

Cheers,

Bron.

On Tue, Feb 23, 2021, at 00:35, Alexey Melnikov wrote:
> Hi Timo,
> 
> On 22/02/2021 11:53, Timo Sirainen wrote:
> 
> > On 22. Feb 2021, at 11.43, internet-drafts@ietf.org wrote:
> >> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >> This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF.
> >>
> >>         Title           : IMAP QUOTA Extension
> >>         Author          : Alexey Melnikov
> >> Filename        : draft-ietf-extra-quota-04.txt
> >> Pages           : 18
> >> Date            : 2021-02-22
> > This </t> looks like a bug:
> >
> >                  S: A003 NO [OVERQUOTA] APPEND Failed</t>
> Thanks, I've noticed that after I posted it. I will fix in the next update.
> > Also it's not very clear to me what clients should do about soft quota. If they receive untagged OVERQUOTA response, should they do something?
> 
> I think they should check the current usage and display it with a 
> warning (different text, colour, icon).
> 
> Best Regards,
> 
> Alexey
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--fe932f532afc484583d281be762f5fe2
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Thanks Alexey,<br></div><div style=3D"font-family:Arial;">=
<br></div><div style=3D"font-family:Arial;">Other than the syntax error =
there, we've already had a working group last call on this document, and=
 there's been no other feedback.<br></div><div style=3D"font-family:Aria=
l;"><br></div><div style=3D"font-family:Arial;">Do you need to add some =
"advice for clients" to capture your response to Timo in the draft?<br><=
/div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fami=
ly:Arial;">I guess you won't be uploading the updated draft until IETF11=
0 starts, so we can chat then about submitting it for publication then.<=
br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-=
family:Arial;">Cheers,<br></div><div style=3D"font-family:Arial;"><br>Br=
on.<br></div><div style=3D"font-family:Arial;"><br></div><div>On Tue, Fe=
b 23, 2021, at 00:35, Alexey Melnikov wrote:<br></div><blockquote type=3D=
"cite" id=3D"qt" style=3D""><div style=3D"font-family:Arial;">Hi Timo,<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;">On 22/02/2021 11:53, Timo Sirainen wrote:<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">&=
gt; On 22. Feb 2021, at 11.43,&nbsp;<a href=3D"mailto:internet-drafts@ie=
tf.org">internet-drafts@ietf.org</a> wrote:<br></div><div style=3D"font-=
family:Arial;">&gt;&gt; A New Internet-Draft is available from the on-li=
ne Internet-Drafts directories.<br></div><div style=3D"font-family:Arial=
;">&gt;&gt; This draft is a work item of the Email mailstore and eXtensi=
ons To Revise or Amend WG of the IETF.<br></div><div style=3D"font-famil=
y:Arial;">&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : IMAP QUOTA Extension<br></div=
><div style=3D"font-family:Arial;">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Author&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; : Alexey Melnikov<br></div><div style=3D"font-family:Arial;">&g=
t;&gt; 	Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-=
extra-quota-04.txt<br></div><div style=3D"font-family:Arial;">&gt;&gt; 	=
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 18<b=
r></div><div style=3D"font-family:Arial;">&gt;&gt; 	Date&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2021-02-22<br></div=
><div style=3D"font-family:Arial;">&gt; This &lt;/t&gt; looks like a bug=
:<br></div><div style=3D"font-family:Arial;">&gt;<br></div><div style=3D=
"font-family:Arial;">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: A003 NO [OVER=
QUOTA] APPEND Failed&lt;/t&gt;<br></div><div style=3D"font-family:Arial;=
">Thanks, I've noticed that after I posted it. I will fix in the next up=
date.<br></div><div style=3D"font-family:Arial;">&gt; Also it's not very=
 clear to me what clients should do about soft quota. If they receive un=
tagged OVERQUOTA response, should they do something?<br></div><div style=
=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I th=
ink they should check the current usage and display it with a&nbsp;<br><=
/div><div style=3D"font-family:Arial;">warning (different text, colour, =
icon).<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">Best Regards,<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">Alexey<br></div><div s=
tyle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">=
_______________________________________________<br></div><div style=3D"f=
ont-family:Arial;">Extra mailing list<br></div><div style=3D"font-family=
:Arial;"><a href=3D"mailto:Extra@ietf.org">Extra@ietf.org</a><br></div><=
div style=3D"font-family:Arial;"><a href=3D"https://www.ietf.org/mailman=
/listinfo/extra">https://www.ietf.org/mailman/listinfo/extra</a><br></di=
v><div style=3D"font-family:Arial;"><br></div></blockquote><div style=3D=
"font-family:Arial;"><br></div><div id=3D"sig56629417"><div class=3D"sig=
nature">--<br></div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, =
Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; brong@fastmail=
team.com<br></div><div class=3D"signature"><br></div></div><div style=3D=
"font-family:Arial;"><br></div></body></html>
--fe932f532afc484583d281be762f5fe2--

