
From nobody Sun Jan  3 14:37:23 2021
Return-Path: <session-request@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 944F43A1392; Sun,  3 Jan 2021 14:37:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: barryleiba@computer.org, brong@fastmailteam.com, extra-chairs@ietf.org, extra@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160971344153.32363.13110864280460465481@ietfa.amsl.com>
Date: Sun, 03 Jan 2021 14:37:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ezKhH8MbCSabwjSGWKrE0kz4s44>
Subject: [Extra] extra - New Meeting Session Request 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: Sun, 03 Jan 2021 22:37:22 -0000

A new meeting session request has just been submitted by Bron Gondwana, a Chair of the extra working group.


---------------------------------------------------------
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:
  Barry Leiba
  Alexey Melnikov
  Jiankang Yao
  Bron Gondwana

Resources Requested:

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



From nobody Sun Jan  3 14:42:43 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 870B23A13C3 for <extra@ietfa.amsl.com>; Sun,  3 Jan 2021 14:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.218
X-Spam-Level: 
X-Spam-Status: No, score=-0.218 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, 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=fastmailteam.com header.b=jX+1A/cG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JPk2MUAo
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 qfxnsxxOcQwz for <extra@ietfa.amsl.com>; Sun,  3 Jan 2021 14:42:40 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05D23A13C1 for <extra@ietf.org>; Sun,  3 Jan 2021 14:42:39 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 5D70B5C00B8 for <extra@ietf.org>; Sun,  3 Jan 2021 17:42:38 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 03 Jan 2021 17:42:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:subject :content-type; s=fm1; bh=FwlTAnJGsUwQZhSAWGFM9nsFMaLSG6FjdDDu+7Q 88IU=; b=jX+1A/cG/g7ouD38Cpl10g01PiEEBTg0fVeLN6Ra8D9BnkobZDX/f53 XmvXR954yW/awB99qQj0ZKPq48IrHxPSKNZkSDmyb/BBW8LLkrJjdeI6o7tlVbzu XPOeXzjfGiL40hmURFiEgsYd6Q40y6dryDCg8c+ueAB8by3Ykyh0X+jZIMb6AG0L f3dk3U+79Bk+KuP22cr4ERl6tpGm8OF31iFmklhgTXXIuYjc9X94VWmDj8+nJT4B WB4L55XsMSfz3hM7DtEysz6qd0AVevJjtfGsQhg14ymkKdybTWyjKYiZLMlcVppN Iv+ZBstOgji9+9RkrCgGZkorUcgUoCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=FwlTAnJGsUwQZhSAWGFM9nsFMaLSG 6FjdDDu+7Q88IU=; b=JPk2MUAo89jHBTxfs01rZhDgw4AMpMC7PjQPcdU5zRZZu dToeJOams2ERGsM4Edi1kFtbQzmrWaESqGeEo06WIRuAHE3uXaxskwcWOz4y8PVX r1Igj1sUa4d+vaj5wNr8Y7N0m+dJ0J1CB7272UZbCynV/I4+wVWTzsQBbrX87XNR fJwDeMhpqJwFWkcV4+kZPMk1hBVNGL4Thxa4CgJeMdFk2AiXgaNKdnp6bFZ584ww DWD+gLyJ9QA6rTbYTcmRk4g4kpdATGvJdrQTq0muVsoeIBxeU1IyN0mLU8ZD7nN/ zG7ho324cekFnd+HqxCzEDKBL4wBPXp1657w+OMZg==
X-ME-Sender: <xms:XEjyX-zGrkaGd8ApS9XVdnLPZTyQ7MLz8p_3Dys_oxgVPF3swdBJ0A> <xme:XEjyX6TWqHCHnoNEHq8zBg1QsT3tbx7BLoOgpt0JsNSIkyg3JsdMFrobyH-Vxeg0r 8BIUjX-tAk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdefvddgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsegrtderre erredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpedvteetieeviefhge eitdegiefgudevleehgfffleegleeuhefhiedtleegtdffgeenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrghilh htvggrmhdrtghomh
X-ME-Proxy: <xmx:XEjyXwUUS7eFPo8AJiMjvG3N3Hrr4g-P7UULsWCatA0xSgaEAVCKnQ> <xmx:XEjyX0hwc45T2DGFL-5p57XY7PdaqDKXuL5hzAODt0lCv_T-Ua3alA> <xmx:XEjyXwBDq4zHJJvTS90kd3y_qJ6gMYORLd8O2ckNt0F4YtCTPdbYpA> <xmx:XkjyXzOjgIqKQD9idcr3TTvbSU2jBLUA3JGZj9_Fh3-q_hMmkmRqRA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 86D8D180242; Sun,  3 Jan 2021 17:42:36 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.1-61-gb52c239-fm-20201210.001-gb52c2396
Mime-Version: 1.0
x-forwarded-message-id: <160971344153.32363.13110864280460465481@ietfa.amsl.com>
Message-Id: <fe8d4363-25da-4acc-bfc5-6bc860b899c4@dogfood.fastmail.com>
Date: Mon, 04 Jan 2021 09:42:16 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary=830b8c431cd74047b067a6b146510b48
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/c9qgyTsnC5zYUrPRud6BN_l8ToE>
Subject: [Extra] Fwd: extra - New Meeting Session Request for IETF 110
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: Sun, 03 Jan 2021 22:42:42 -0000

--830b8c431cd74047b067a6b146510b48
Content-Type: text/plain

I've put this in just in case, but I expect we'll probably cancel it.  Our only working doc right now is sieve-snooze (and quota, but that's going to be submitted as soon as Alexey uploads a revision that addresses the last-call comments)

Bron.

----- Original message -----
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: session-request@ietf.org
Cc: barryleiba@computer.org, brong@fastmailteam.com, extra-chairs@ietf.org, extra@ietf.org
Subject: extra - New Meeting Session Request for IETF 110
Date: Monday, January 04, 2021 09:37



A new meeting session request has just been submitted by Bron Gondwana, a Chair of the extra working group.


---------------------------------------------------------
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:
  Barry Leiba
  Alexey Melnikov
  Jiankang Yao
  Bron Gondwana

Resources Requested:

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




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


--830b8c431cd74047b067a6b146510b48
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;">I've put this in just in case, but I expect we'll probably=
 cancel it.&nbsp; Our only working doc right now is sieve-snooze (and qu=
ota, but that's going to be submitted as soon as Alexey uploads a revisi=
on that addresses the last-call comments)<br></div><div style=3D"font-fa=
mily:Arial;"><br></div><div style=3D"font-family:Arial;">Bron.<br></div>=
<div style=3D"font-family:Arial;"><br></div><div>----- Original message =
-----<br></div><div>From: IETF Meeting Session Request Tool &lt;<a href=3D=
"mailto:session-request@ietf.org">session-request@ietf.org</a>&gt;<br></=
div><div>To:&nbsp;<a href=3D"mailto:session-request@ietf.org">session-re=
quest@ietf.org</a><br></div><div>Cc:&nbsp;<a href=3D"mailto:barryleiba@c=
omputer.org">barryleiba@computer.org</a>,&nbsp;<a href=3D"mailto:brong@f=
astmailteam.com">brong@fastmailteam.com</a>,&nbsp;<a href=3D"mailto:extr=
a-chairs@ietf.org">extra-chairs@ietf.org</a>,&nbsp;<a href=3D"mailto:ext=
ra@ietf.org">extra@ietf.org</a><br></div><div>Subject: extra - New Meeti=
ng Session Request for IETF 110<br></div><div>Date: Monday, January 04, =
2021 09:37<br></div><div><br></div><div 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;">A new meeting sessi=
on request has just been submitted by Bron Gondwana, a Chair of the extr=
a working group.<br></div><div style=3D"font-family:Arial;"><br></div><d=
iv style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Aria=
l;">---------------------------------------------------------<br></div><=
div style=3D"font-family:Arial;">Working Group Name: Email mailstore and=
 eXtensions To Revise or Amend<br></div><div style=3D"font-family:Arial;=
">Area Name: Applications and Real-Time Area<br></div><div style=3D"font=
-family:Arial;">Session Requester: Bron Gondwana<br></div><div style=3D"=
font-family:Arial;"><br></div><div style=3D"font-family:Arial;"><br></di=
v><div style=3D"font-family:Arial;">Number of Sessions: 1<br></div><div =
style=3D"font-family:Arial;">Length of Session(s):&nbsp; 1 Hour<br></div=
><div style=3D"font-family:Arial;">Number of Attendees: 15<br></div><div=
 style=3D"font-family:Arial;">Conflicts to Avoid:&nbsp;<br></div><div st=
yle=3D"font-family:Arial;">Chair Conflict: jmap calext dispatch<br></div=
><div style=3D"font-family:Arial;">Technology Overlap: emailcore dmarc<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><div=
 style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fo=
nt-family:Arial;">People who must be present:<br></div><div style=3D"fon=
t-family:Arial;">&nbsp; Barry Leiba<br></div><div style=3D"font-family:A=
rial;">&nbsp; Alexey Melnikov<br></div><div style=3D"font-family:Arial;"=
>&nbsp; Jiankang Yao<br></div><div style=3D"font-family:Arial;">&nbsp; B=
ron Gondwana<br></div><div style=3D"font-family:Arial;"><br></div><div s=
tyle=3D"font-family:Arial;">Resources Requested:<br></div><div style=3D"=
font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Special =
Requests:<br></div><div style=3D"font-family:Arial;">&nbsp;&nbsp;<br></d=
iv><div style=3D"font-family:Arial;">-----------------------------------=
----------------------<br></div><div style=3D"font-family:Arial;"><br></=
div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-famil=
y:Arial;"><br></div></div><div style=3D"font-family:Arial;"><br></div><d=
iv id=3D"sig56629417"><div class=3D"signature">--<br></div><div class=3D=
"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></div><div cl=
ass=3D"signature">&nbsp; brong@fastmailteam.com<br></div><div class=3D"s=
ignature"><br></div></div><div style=3D"font-family:Arial;"><br></div></=
body></html>
--830b8c431cd74047b067a6b146510b48--


From nobody Mon Jan  4 00:19:03 2021
Return-Path: <superuser@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 23F2A3A0127 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 00:19:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.311
X-Spam-Level: 
X-Spam-Status: No, score=0.311 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, THIS_AD=0.498, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fpky17xj8-Q8 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 00:18:59 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (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 CBE1F3A0121 for <extra@ietf.org>; Mon,  4 Jan 2021 00:18:58 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id p128so5978188vkf.12 for <extra@ietf.org>; Mon, 04 Jan 2021 00:18:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=9vLC5WTtcLbboPvVHItRzQ/ZZ4hOOMiAu0RPFCbSd4M=; b=Je4/SOQd98jVfWlSpKlyC0c6ELLjAzWBm6OwFwuisJ7s5CDGWE7/N+50WIp4X9/0Pb afTlc39OQEM+C3H/wzwLbQPWOnZ3ZTdGDG/KhWQyU898goTWcDNUD8eE5gVx9EG/CMK3 +tz8HcC+NSkdh6ULNZnJJBZHOBa3S3xjYnCK97z358lhwad47eSyTkomR77RzXOEQSB9 F0q6+a13+WHc/l5nnhTyKV+nCnyE+s0JtfV9Ecu8JrLR9UHJMJvIbQQS0sJ1VawKlhBZ XVqEHPaaXjuZfood5kqOkzqSdSi5wOoIwacM10g+2VLT5LeWnv4hUVcF7O0U56Bizj5m dIMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9vLC5WTtcLbboPvVHItRzQ/ZZ4hOOMiAu0RPFCbSd4M=; b=qtAsVqcwYNEytDvtX+SaNUfM0wRp2Yhhk3iKkdyRwazmQi+HKKE38a9G88iFhCdv+Q +rDmijG1bIQmm9TlVSh5NIDaCWgjCBQfPnFN0NsjE4dFVPUNzSbLXGDzgw7HNE9xRNs5 nq1iUSS8mlfQsuhmI/iKm4wf81qWrpiK1U9kM99yXCPh58mLXNCMoKE7NpS/rvGlYqUV uUqciikB8Wc9tWcYOElrkEXcqIx0+PhjykuENBctBjUYAIZqRBM7MKy/3z1rybtjU22p vuxNJ96v9W7sEjzBU8yHYmfyPQiIzWTjvTZgJ0vzG9IghifMMwtoSGHJQecPTEKn3dua xMZw==
X-Gm-Message-State: AOAM530KHLtBVSXkdOi/ZJMemx0IsjuXN1omsGjoo+Rbf2FQbIytB8dl 2kQ/ZOtei3dCea1EliTuk3s51oq08yh8E5yRslpdR5dzqyy6xw==
X-Google-Smtp-Source: ABdhPJylbayMYAUVy62Uvj3JGdiNXvbwi71G7u5igPLwxHhWMowOZnPBvdMnU9S/96tgY6sEdkzCXXkfVAvcheYAGN4=
X-Received: by 2002:a1f:30cd:: with SMTP id w196mr44929946vkw.13.1609748337042;  Mon, 04 Jan 2021 00:18:57 -0800 (PST)
MIME-Version: 1.0
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 4 Jan 2021 00:18:46 -0800
Message-ID: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cea78a05b80ebd11"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/hVCavR4AYimfDkf2iwjXdWw8H2A>
Subject: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 08:19:02 -0000

--000000000000cea78a05b80ebd11
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

At long last. Thanks for your patience. This is a lot of material to sift
through!

This AD review is based on -22.  I=E2=80=99m coming at this as someone who =
has made
almost no direct use of IMAP as a user and certainly never implemented it,
so expect some neophyte-style feedback here.  I also (briefly) reviewed the
diff between RFC 3501 and this version.


Away we go...

Section 1.2

Should the =E2=80=9CC:=E2=80=9D and =E2=80=9CS:=E2=80=9D paragraph also men=
tion that CRLF termination is
implicit in examples?  I realize Section 2.2 makes it clear that=E2=80=99s =
the
protocol anyway, so maybe this isn=E2=80=99t necessary, but I=E2=80=99ve se=
en it made
explicit in other documents so I thought I=E2=80=99d mention it.

Section 2.2.1

  Clients MUST follow the syntax outlined in this specification

   strictly.  It is a syntax error to send a command with missing or

   extraneous spaces or arguments.

It seems unnecessary to say this in a standards track document.  There=E2=
=80=99s a
similar paragraph in Section 2.2.2.

Section 2.2.2

   In the case of certain server data, the data MUST be recorded.

This seems misplaced; the MUST should be in the descriptions for the
specific cases where this requirement exists.

Section 2.3

Most of the subsections below here start with a clause that defines the
term, but it=E2=80=99s not a sentence.  This may be personal preference, bu=
t I
suggest adjusting them slightly so they=E2=80=99re sentences.  I=E2=80=99ve=
 included an
example below where I have an adjacent suggestion and thus fixed the whole
paragraph.

Section 2.3.1.1


=E2=80=9CSTRONGLY ENCOURAGES=E2=80=9D in all caps seems awkward.  I=E2=80=
=99m tempted to say
something about it not being valid BCP 14, etc.

Section 2.3.2

The opening sentence isn=E2=80=99t a sentence.  Also later, =E2=80=9CKeywor=
d=E2=80=9D is introduced
without indicating that it=E2=80=99s one of the two possible flag types (wh=
ich I
believe to be the case).  I suggest:

  A message has associated with it a list of zero or more named tokens,

   known as =E2=80=9Cflags=E2=80=9D. A flag is set by its addition to this =
list, and is
cleared by its

   removal.  There are two types of flags in IMAP4rev2: system flags, and
keywords.

   A flag of either type can also be permanent or session-only.

Second paragraph: s/begin/begins/

s/in used in/in use in/

The text surrounding $Phishing goes further into human factors work than
other working groups have felt appropriate.  (DKIM and DMARC come to
mind.)  Are we sure that belongs here?

It seems strange to oblige a client detecting both $Junk and $NotJunk being
set to deal with that condition by fixing it.  The advice to ignore them is
fine, however.

It=E2=80=99s also curious to put a normative SHOULD on registering keywords=
, as
IANA activity is outside of the protocol.  It=E2=80=99s more typical to say=
 you
SHOULD ignore keywords you don=E2=80=99t recognize, and then make a referen=
ce to
the registry.

Should this section mention whether the system flags are permanent?  \Seen,
for example, is clearly a system flag, but it could also be a session flag.

Section 2.3.3

All the SHOULDs in here make me wonder when an implementor might
legitimately choose to do something different.  Or maybe instead of =E2=80=
=9CSHOULD
be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?

Section 4.3

4th paragraph: s/alternate/alternative/

Section 5.1

There=E2=80=99s a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which c=
ould probably benefit
from a section number reference as well.  This is actually something I=E2=
=80=99d
thought about many times earlier in the document up to this point, but I=E2=
=80=99m
finally saying something here; some of them were clear references like
this, while others were references to commands or flags that are =E2=80=9Cd=
escribed
elsewhere in this document=E2=80=9D.

Section 5.1.2.1

Although both =E2=80=9CImplementer=E2=80=9D and =E2=80=9CImplementor=E2=80=
=9D appear to be correct, you use
the latter everywhere in the document except here.  (Actually, Google docs
suggests the former.)

Section 5.2

=E2=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D  This isn=E2=80=99t=
 a specific normative
statement, so I=E2=80=99d use the lowercase version here, and use BCP 14 la=
nguage
when you=E2=80=99re presenting specific cases.

Section 5.3

Maybe my understanding is wrong, but if you do a non-blocking write while
you don=E2=80=99t have enough buffer space available, won=E2=80=99t some of=
 what you write
be lost, resulting in gibberish at the other end?  Maybe this needs to
mention retries of stuff that couldn=E2=80=99t be sent (if any) when a non-=
blocking
write returns?

I=E2=80=99m tempted to suggest just removing this.  This is something you d=
eal with
at the socket layer, and IMHO isn=E2=80=99t really part of IMAP itself.

Section 6.1.1

Is the stuff about XBLURDYBLOOP still appropriate given BCP 178?

Section 6.1.2


This section says NOOP can be used to reset the autologout timer (which
seems definite), but Section 5.1.4 says any command only SHOULD reset the
timer.  Do these line up?

Section 6.2

s/alternate/alternative/

Section 6.2.3


I think there=E2=80=99s an =E2=80=9Cor=E2=80=9D missing in the last paragra=
ph.

Section 6.3.1

There=E2=80=99s another =E2=80=9CX=E2=80=9D reference here (BCP 178).

This section should make it more explicit, up front, that the response
names the extensions that were successfully enabled.  Right now the lede is
buried in about the 7th paragraph.

Section 6.3.2

Where is =E2=80=9CParagraph 10=E2=80=9D?

Section 6.3.4

The all-caps =E2=80=9CUNLESS=E2=80=9D should probably be lowercase-ized.

Section 6.3.5

Same remark about =E2=80=9CUNLESS=E2=80=9D.

Section 6.3.6

Same remark about =E2=80=9CUNLESS=E2=80=9D.

It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D fol=
lowed immediately by
=E2=80=9Csome servers don=E2=80=99t let you do this=E2=80=9D.  Which is the=
 standard for this
version of IMAP?  If it=E2=80=99s an implementation choice, I think that=E2=
=80=99s what
this should say.

Section 6.3.9

   The LIST command returns a subset of names from the complete set of

   all names available to the client.

Names of what?

   Clients SHOULD use the empty reference

   argument.

Why might I not do this?

    For example, here are some examples =E2=80=A6

You can probably drop =E2=80=9CFor example,=E2=80=9D.

Section 6.3.9.2

This section (and the previous) require that \Subscribed be computed
accurately before the response is generated.  How does this square with the
text in Section 6.3.9 that insists replies come quickly?

Section 6.3.9.5


A grammar nit, which I encountered here but it=E2=80=99s not the first: =E2=
=80=9Cwhether or
not=E2=80=9D should usually just be =E2=80=9Cwhether=E2=80=9D; the =E2=80=
=9Cor not=E2=80=9D is implied.

The second paragraph also gets into the presentation of the reply.  This is
human factors stuff the IETF tends to avoid.  Are we sure it belongs here?

Section 6.3.9.6

    Servers SHOULD ONLY return =E2=80=A6

I think =E2=80=9CONLY=E2=80=9D should be lowercase here (confusion with BCP=
 14).

Section 6.3.9.7

   another user renaming of deleting the

s/of/or/

Section 6.3.9.8

Another grammar nit: I keep running into sentences or clauses that end with
=E2=80=9Csubscribed to=E2=80=9D, which should really be =E2=80=9Cto which t=
he user is subscribed=E2=80=9D,
or maybe just =E2=80=9Csubscribed=E2=80=9D.

Sadly I must also point out that in example 8, contrary to my earlier
point, this use of =E2=80=9Cwhether or not=E2=80=9D is correct as-is.  But =
the prose later
on in example 8 refers to =E2=80=9Csubscribed children=E2=80=9D, which is a=
 good example of
avoiding the problem I just mentioned above.  (Whee, English.)

Section 6.3.10

   The NAMESPACE command causes a single ungagged NAMESPACE =E2=80=A6

You probably meant =E2=80=9Cuntagged=E2=80=9D, unless NAMESPACE is generall=
y noisy.

  In this example, a server supports 2 Personal Namespaces.  =E2=80=A6

s/2/two/

There=E2=80=99s a reference to X-PARAM in here that probably needs updating=
 in
light of BCP 178.

      refer to sections Section 7
<https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-22#section-7>,

      Section 7.3.1
<https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-22#section-7.3.1>
for more information about =E2=80=A6

Remove =E2=80=9Csections=E2=80=9D and stick an =E2=80=9Cand=E2=80=9D betwee=
n them.

Section 6.3.12

I=E2=80=99m not sure that 310 is the correct length for the first example. =
 I get
312.  Am I misunderstanding how this gets determined?  I get this by adding
the length of each line (including the empty ones) plus two for each line
representing the terminating CRLF.

Using that method, the second example also appears to be off by two.

Section 6.3.13

  Without the IDLE command a client requires to poll the server for

s/requires/needs/ (or maybe =E2=80=9Cwould need=E2=80=9D)

  responses at any time.  If the server choose to send unsolicited

s/choose/chooses/

The specific advice about reissuing IDLE every 29 minutes presumes the
auto-logout timeout is fixed at 30 minutes.  Since I think I read higher up
that this could be some other time limit, it might be a good thing to
negotiate somehow via a capability, or the continuation reply to IDLE, or
something like that.

Section 6.4.2

   The UNSELECT command frees server's resources associated with the

   selected mailbox and returns the server to the authenticated state.

I suggest changing =E2=80=9Cserver=E2=80=99s=E2=80=9D to =E2=80=9Csession=
=E2=80=99s=E2=80=9D.  As written here, it could be
read to say you=E2=80=99re deleting the selected mailbox.

Section 6.4.4

The use of =E2=80=9C(*)=E2=80=9D to make a footnote that=E2=80=99s actually=
 just the next paragraph
can probably be eliminated by just merging the paragraphs.


OLD:

  Individual options may contain parameters enclosed in

   parentheses (*).  If an option has parameters, they consist of atoms

   and/or strings and/or lists in a specific order.  Any options not

   defined by extensions that the server supports must be rejected with

   a BAD response.

   (*) - if an option has a mandatory parameter, which can always be

   represented as a number or a sequence-set, the option parameter does

   not need the enclosing ().  See the ABNF for more details.

NEW:

Individual options may contain parameters enclosed in parentheses.
(However, if an option has a mandatory parameter, which can always be
represented as a number or a sequence-set, the option parameter does not
need the enclosing parentheses.  See the ABNF for more details).  If an
option has parameters, they consist of atoms and/or strings and/or lists in
a specific order.  Any options not defined by extensions that the server
supports MUST be rejected with a BAD response.


(END)

In =E2=80=9CReturn number of the messages=E2=80=9D, I think it should be =
=E2=80=9CReturn the number
of messages=E2=80=9D.

The definitions of several search keys should be reviewed to ensure use of
the terms =E2=80=9Cheader field=E2=80=9D (not simply =E2=80=9Cheader=E2=80=
=9D) and =E2=80=9Cheader field value=E2=80=9D
appropriately, matching current convention.

Does TEXT matching ignore line breaks?  For instance, does searching for
=E2=80=9Cfoo bar=E2=80=9D match =E2=80=9Cfoo<newline>bar=E2=80=9D?  Given t=
he text about flexible matching,
I was wondering.

Section 6.4.4.2

=E2=80=9Cas described in by Section 5.5
<https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-22#section-5.5>.=E2=
=80=9D
-- s/in by/in/

Section 6.4.4.4

I think the inline comments in the various examples don=E2=80=99t really ne=
ed to be
inline.  They could just as easily be prose below each example.

Section 6.4.7

There=E2=80=99s a lot of SHOULD and SHOULD NOT here that make me think a di=
scussion
of why one might do otherwise would be helpful.  There are otherwise too
many different ways in which this command could legitimately behave.

Section 6.5

Is this appropriate in light of BCP 178?

Section 7.1

Why would CONTACTADMIN be returned as part of an OK message, such as in the
example given?  I read that as =E2=80=9CYour login was successful, but you =
should
contact your help desk.=E2=80=9D

Section 7.2.2

The stuff about capability names starting with =E2=80=9CX=E2=80=9D should b=
e reviewed in
light of BCP 178.

Section 7.2 and its subsections

A fair bit of this text is repeated verbatim from earlier sections and
should probably be consolidated.  I really noticed this when I hit Section
7.2.3 where, for instance, \HasChildren is defined both here and in Section
6.3.9.5, with the paragraphs in both sections being identical.  However,
now that I look earlier in 7.2.2, I see the same issue.

Section 7.4.2


In the ENVELOPE section, there are references to =E2=80=9Cheader=E2=80=9D t=
hat should be
=E2=80=9Cheader field=E2=80=9D.

Section 13.1


RFCs 2152 and 2180 are normative downrefs; please make sure the shepherd
writeup calls this out.

-MSK

--000000000000cea78a05b80ebd11
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0=
pt;margin-bottom:0pt" id=3D"gmail-docs-internal-guid-c926fa8b-7fff-bbc3-8c1=
9-78e7de5a6dfc"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb=
(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pr=
e-wrap">At long last.  Thanks for your patience.  This is a lot of material=
 to sift through!<br><br>This AD review is based on -22.=C2=A0 I=E2=80=99m =
coming at this as someone who has made almost no direct use of IMAP as a us=
er and certainly never implemented it, so expect some neophyte-style feedba=
ck here.=C2=A0 I also (briefly) reviewed the diff between RFC 3501 and this=
 version.</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-=
top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant:normal;text-decoration:none;vertical-align:baseline;whi=
te-space:pre-wrap"><br></span></font></p><p style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap">Away we go...<br></span></font></p><font size=3D"2"><b=
r></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"=
>Section 1.2</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">Should the =E2=80=9CC:=E2=
=80=9D and =E2=80=9CS:=E2=80=9D paragraph also mention that CRLF terminatio=
n is implicit in examples?=C2=A0 I realize Section 2.2 makes it clear that=
=E2=80=99s the protocol anyway, so maybe this isn=E2=80=99t necessary, but =
I=E2=80=99ve seen it made explicit in other documents so I thought I=E2=80=
=99d mention it.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D=
"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">Section 2.2.1</span><=
span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpare=
nt;font-weight:400;font-style:normal;font-variant:normal;text-decoration:no=
ne;vertical-align:baseline;white-space:pre-wrap"><br></span><span style=3D"=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-al=
ign:baseline;white-space:pre-wrap"><br></span><span style=3D"font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap"> =C2=A0 Clients MUST follow the syntax outlined in thi=
s specification</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax e=
rror to send a command with missing or</span></font></p><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><s=
pan style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparen=
t;font-weight:400;font-style:normal;font-variant:normal;text-decoration:non=
e;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0extraneou=
s spaces or arguments.</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">It seems unnec=
essary to say this in a standards track document.=C2=A0 There=E2=80=99s a s=
imilar paragraph in Section 2.2.2.</span></font></p><font size=3D"2"><br></=
font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 2.2.2</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><s=
pan style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparen=
t;font-weight:400;font-style:normal;font-variant:normal;text-decoration:non=
e;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0In=C2=A0t=
he case of certain server data, the data MUST be recorded.</span></font></p=
><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap">This seems misplaced; the MUST should be in the descri=
ptions for the specific cases where this requirement exists.</span></font><=
/p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">Section 2.3</span></font></p><font size=3D"2"><br></=
font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Mos=
t of the subsections below here start with a clause that defines the term, =
but it=E2=80=99s not a sentence.=C2=A0 This may be personal preference, but=
 I suggest adjusting them slightly so they=E2=80=99re sentences.=C2=A0 I=E2=
=80=99ve included an example below where I have an adjacent suggestion and =
thus fixed the whole paragraph.</span></font></p><font size=3D"2"><br></fon=
t><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt=
"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);backgr=
ound-color:transparent;font-weight:400;font-style:normal;font-variant:norma=
l;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sectio=
n 2.3.1.1</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-=
top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant:normal;text-decoration:none;vertical-align:baseline;whi=
te-space:pre-wrap"><br></span><span style=3D"font-family:Arial;color:rgb(0,=
0,0);background-color:transparent;font-weight:400;font-style:normal;font-va=
riant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-w=
rap">=E2=80=9CSTRONGLY ENCOURAGES=E2=80=9D in all caps seems awkward.=C2=A0=
 I=E2=80=99m tempted to say something about it not being valid BCP 14, etc.=
</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap">Section 2.3.2</span></font></p><font=
 size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">The opening sentence isn=E2=80=99t a sentence.=C2=A0 Also la=
ter, =E2=80=9CKeyword=E2=80=9D is introduced without indicating that it=E2=
=80=99s one of the two possible flag types (which I believe to be the case)=
.=C2=A0 I suggest:</span><span style=3D"font-family:Arial;color:rgb(0,0,0);=
background-color:transparent;font-weight:400;font-style:normal;font-variant=
:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=
<br></span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap"><br></span><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap"> =C2=A0 A message has associ=
ated with it a list of zero or more named tokens,</span></font></p><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=
=C2=A0known as =E2=80=9Cflags=E2=80=9D. A flag is set by its addition to th=
is list, and is cleared by its</span></font></p><p dir=3D"ltr" style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span styl=
e=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-w=
eight:400;font-style:normal;font-variant:normal;text-decoration:none;vertic=
al-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0removal.=C2=A0 Th=
ere are two types of flags in IMAP4rev2: system flags, and keywords.</span>=
</font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,=
0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wra=
p">=C2=A0=C2=A0=C2=A0A flag of either type can also be permanent or session=
-only.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span =
style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;fo=
nt-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ve=
rtical-align:baseline;white-space:pre-wrap">Second paragraph: s/begin/begin=
s/</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span styl=
e=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-w=
eight:400;font-style:normal;font-variant:normal;text-decoration:none;vertic=
al-align:baseline;white-space:pre-wrap">s/in used in/in use in/</span></fon=
t></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-fami=
ly:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font=
-style:normal;font-variant:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap">The text surrounding $Phishing goes further into =
human factors work than other working groups have felt appropriate.=C2=A0 (=
DKIM and DMARC come to mind.)=C2=A0 Are we sure that belongs here?</span></=
font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">It seems strange to oblige a client detecting =
both $Junk and $NotJunk being set to deal with that condition by fixing it.=
=C2=A0 The advice to ignore them is fine, however.</span></font></p><font s=
ize=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap">It=E2=80=99s also curious to put a normative SHOULD on registe=
ring keywords, as IANA activity is outside of the protocol.=C2=A0 It=E2=80=
=99s more typical to say you SHOULD ignore keywords you don=E2=80=99t recog=
nize, and then make a reference to the registry.</span></font></p><font siz=
e=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:=
rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;f=
ont-variant:normal;text-decoration:none;vertical-align:baseline;white-space=
:pre-wrap">Should this section mention whether the system flags are permane=
nt?=C2=A0 \Seen, for example, is clearly a system flag, but it could also b=
e a session flag.</span></font></p><font size=3D"2"><br></font><p dir=3D"lt=
r" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=
=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:t=
ransparent;font-weight:400;font-style:normal;font-variant:normal;text-decor=
ation:none;vertical-align:baseline;white-space:pre-wrap">Section 2.3.3</spa=
n></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">All the SHOULDs in here make me wonder whe=
n an implementor might legitimately choose to do something different.=C2=A0=
 Or maybe instead of =E2=80=9CSHOULD be=E2=80=9D, just say =E2=80=9Cis=E2=
=80=9D?</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap">Section 4.3</span></font></p=
><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap">4th paragraph: s/alternate/alternative/</span></font><=
/p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">Section 5.1</span></font></p><font size=3D"2"><br></=
font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
re=E2=80=99s a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which coul=
d probably benefit from a section number reference as well.=C2=A0 This is a=
ctually something I=E2=80=99d thought about many times earlier in the docum=
ent up to this point, but I=E2=80=99m finally saying something here; some o=
f them were clear references like this, while others were references to com=
mands or flags that are =E2=80=9Cdescribed elsewhere in this document=E2=80=
=9D.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span st=
yle=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font=
-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vert=
ical-align:baseline;white-space:pre-wrap">Section 5.1.2.1</span></font></p>=
<font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style=
:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;wh=
ite-space:pre-wrap">Although both =E2=80=9CImplementer=E2=80=9D and =E2=80=
=9CImplementor=E2=80=9D appear to be correct, you use the latter everywhere=
 in the document except here.=C2=A0 (Actually, Google docs suggests the for=
mer.)</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"=
line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span s=
tyle=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;fon=
t-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ver=
tical-align:baseline;white-space:pre-wrap">Section 5.2</span></font></p><fo=
nt size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;=
color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:no=
rmal;font-variant:normal;text-decoration:none;vertical-align:baseline;white=
-space:pre-wrap">=E2=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D=C2=
=A0 This isn=E2=80=99t a specific normative statement, so I=E2=80=99d use t=
he lowercase version here, and use BCP 14 language when you=E2=80=99re pres=
enting specific cases.</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">Section 5.3</s=
pan></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-al=
ign:baseline;white-space:pre-wrap">Maybe my understanding is wrong, but if =
you do a non-blocking write while you don=E2=80=99t have enough buffer spac=
e available, won=E2=80=99t some of what you write be lost, resulting in gib=
berish at the other end?=C2=A0 Maybe this needs to mention retries of stuff=
 that couldn=E2=80=99t be sent (if any) when a non-blocking write returns?<=
/span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap">I=E2=80=99m tempted to suggest just =
removing this.=C2=A0 This is something you deal with at the socket layer, a=
nd IMHO isn=E2=80=99t really part of IMAP itself.</span></font></p><font si=
ze=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">Section 6.1.1</span></font></p><font size=3D"2"><br></font><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">Is the stuff=
 about XBLURDYBLOOP still appropriate given BCP 178?</span></font></p><font=
 size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">Section 6.1.2</span></font></p><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap"><br></span><span style=3D"font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">This section says NOOP can be used to reset the au=
tologout timer (which seems definite), but Section 5.1.4 says any command o=
nly SHOULD reset the timer.=C2=A0 Do these line up?</span></font></p><font =
size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0=
pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;col=
or:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norma=
l;font-variant:normal;text-decoration:none;vertical-align:baseline;white-sp=
ace:pre-wrap">Section 6.2</span></font></p><font size=3D"2"><br></font><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/alternate/=
alternative/</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">Section 6.2.3</span></fon=
t></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><b=
r></span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color=
:transparent;font-weight:400;font-style:normal;font-variant:normal;text-dec=
oration:none;vertical-align:baseline;white-space:pre-wrap">I think there=E2=
=80=99s an =E2=80=9Cor=E2=80=9D missing in the last paragraph.</span></font=
></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">Section 6.3.1</span></font></p><font size=3D"2"><b=
r></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"=
>There=E2=80=99s another =E2=80=9CX=E2=80=9D reference here (BCP 178).</spa=
n></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">This section should make it more explicit,=
 up front, that the response names the extensions that were successfully en=
abled.=C2=A0 Right now the lede is buried in about the 7th paragraph.</span=
></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">Section 6.3.2</span></font></p><font size=
=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">Where is =E2=80=9CParagraph 10=E2=80=9D?</span><span style=3D"fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap"><br><br></span></font></p><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">Section 6.3.4</span></fon=
t></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-fami=
ly:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font=
-style:normal;font-variant:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap">The all-caps =E2=80=9CUNLESS=E2=80=9D should prob=
ably be lowercase-ized.</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">Section 6.3.5<=
/span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap">Same remark about =E2=80=9CUNLESS=E2=
=80=9D.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap">Section 6.3.6</span></font><=
/p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">Same remark about =E2=80=9CUNLESS=E2=80=9D.</span></=
font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">It=E2=80=99s weird to say =E2=80=9Crenaming IN=
BOX is permitted=E2=80=9D followed immediately by =E2=80=9Csome servers don=
=E2=80=99t let you do this=E2=80=9D.=C2=A0 Which is the standard for this v=
ersion of IMAP?=C2=A0 If it=E2=80=99s an implementation choice, I think tha=
t=E2=80=99s what this should say.</span></font></p><font size=3D"2"><br></f=
ont><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);back=
ground-color:transparent;font-weight:400;font-style:normal;font-variant:nor=
mal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sect=
ion 6.3.9</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0The LIST c=
ommand returns a subset of names from the complete set of</span></font></p>=
<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=
<font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);backgrou=
nd-color:transparent;font-weight:400;font-style:normal;font-variant:normal;=
text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0=
=C2=A0=C2=A0all names available to the client.</span></font></p><font size=
=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">Names of what?</span></font></p><font size=3D"2"><br></font><p di=
r=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font=
 size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-co=
lor:transparent;font-weight:400;font-style:normal;font-variant:normal;text-=
decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=
=C2=A0Clients SHOULD use the empty reference</span></font></p><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D=
"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0arg=
ument.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span =
style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;fo=
nt-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ve=
rtical-align:baseline;white-space:pre-wrap">Why might I not do this?</span>=
</font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:=
1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font=
-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400=
;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:=
baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0=C2=A0For example, here ar=
e some examples =E2=80=A6</span></font></p><font size=3D"2"><br></font><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">You can prob=
ably drop =E2=80=9CFor example,=E2=80=9D.</span></font></p><font size=3D"2"=
><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">Section 6.3.9.2</span></font></p><font size=3D"2"><br></font><p dir=3D"=
ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=
=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:t=
ransparent;font-weight:400;font-style:normal;font-variant:normal;text-decor=
ation:none;vertical-align:baseline;white-space:pre-wrap">This section (and =
the previous) require that \Subscribed be computed accurately before the re=
sponse is generated.=C2=A0 How does this square with the text in Section 6.=
3.9 that insists replies come quickly?</span></font></p><font size=3D"2"><b=
r></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"=
>Section 6.3.9.5</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-fami=
ly:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font=
-style:normal;font-variant:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap"><br></span><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">A grammar nit, which I encountered here but it=E2=80=99s not th=
e first: =E2=80=9Cwhether or not=E2=80=9D should usually just be =E2=80=9Cw=
hether=E2=80=9D; the =E2=80=9Cor not=E2=80=9D is implied.</span></font></p>=
<font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style=
:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;wh=
ite-space:pre-wrap">The second paragraph also gets into the presentation of=
 the reply.=C2=A0 This is human factors stuff the IETF tends to avoid.=C2=
=A0 Are we sure it belongs here?</span></font></p><font size=3D"2"><br></fo=
nt><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);backg=
round-color:transparent;font-weight:400;font-style:normal;font-variant:norm=
al;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Secti=
on 6.3.9.6</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><s=
pan style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparen=
t;font-weight:400;font-style:normal;font-variant:normal;text-decoration:non=
e;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0=C2=A0Ser=
vers SHOULD ONLY return =E2=80=A6</span></font></p><font size=3D"2"><br></f=
ont><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);back=
ground-color:transparent;font-weight:400;font-style:normal;font-variant:nor=
mal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I th=
ink =E2=80=9CONLY=E2=80=9D should be lowercase here (confusion with BCP 14)=
.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap">Section 6.3.9.7</span></font></p><fo=
nt size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;=
color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:no=
rmal;font-variant:normal;text-decoration:none;vertical-align:baseline;white=
-space:pre-wrap">=C2=A0=C2=A0=C2=A0another user renaming of deleting the</s=
pan></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-al=
ign:baseline;white-space:pre-wrap">s/of/or/</span></font></p><font size=3D"=
2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0=
,0,0);background-color:transparent;font-weight:400;font-style:normal;font-v=
ariant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-=
wrap">Section 6.3.9.8</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">Another gramma=
r nit: I keep running into sentences or clauses that end with =E2=80=9Csubs=
cribed to=E2=80=9D, which should really be =E2=80=9Cto which the user is su=
bscribed=E2=80=9D, or maybe just =E2=80=9Csubscribed=E2=80=9D.</span></font=
></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">Sadly I must also point out that in example 8, con=
trary to my earlier point, this use of =E2=80=9Cwhether or not=E2=80=9D is =
correct as-is.=C2=A0 But the prose later on in example 8 refers to =E2=80=
=9Csubscribed children=E2=80=9D, which is=C2=A0a good example of avoiding t=
he problem I just mentioned above.=C2=A0 (Whee, English.)</span></font></p>=
<font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style=
:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;wh=
ite-space:pre-wrap">Section 6.3.10</span></font></p><font size=3D"2"><br></=
font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0The NAMESPACE command causes a single ungagged NAMESPACE =E2=
=80=A6</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span =
style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;fo=
nt-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ve=
rtical-align:baseline;white-space:pre-wrap">You probably meant =E2=80=9Cunt=
agged=E2=80=9D, unless NAMESPACE is generally noisy.</span></font></p><font=
 size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">=C2=A0=C2=A0In this example, a server supports 2 Personal Na=
mespaces.=C2=A0 =E2=80=A6</span></font></p><font size=3D"2"><br></font><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/2/two/</sp=
an></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:=
400;font-style:normal;font-variant:normal;text-decoration:none;vertical-ali=
gn:baseline;white-space:pre-wrap">There=E2=80=99s a reference to X-PARAM in=
 here that probably needs updating in light of BCP 178.</span></font></p><f=
ont size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-t=
op:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial=
;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:n=
ormal;font-variant:normal;text-decoration:none;vertical-align:baseline;whit=
e-space:pre-wrap">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0refer to sections</sp=
an><a href=3D"https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-22#sec=
tion-7" style=3D"text-decoration:none"><span style=3D"font-family:Arial;col=
or:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norma=
l;font-variant:normal;text-decoration:none;vertical-align:baseline;white-sp=
ace:pre-wrap"> </span><span style=3D"font-family:Arial;color:rgb(17,85,204)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-=
wrap">Section 7</span></a><span style=3D"font-family:Arial;color:rgb(0,0,0)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"=
>,</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</span><a href=3D"https://tools.i=
etf.org/html/draft-ietf-extra-imap4rev2-22#section-7.3.1" style=3D"text-dec=
oration:none"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0</spa=
n><span style=3D"font-family:Arial;color:rgb(17,85,204);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decora=
tion:underline;vertical-align:baseline;white-space:pre-wrap">Section 7.3.1<=
/span></a><span style=3D"font-family:Arial;color:rgb(0,0,0);background-colo=
r:transparent;font-weight:400;font-style:normal;font-variant:normal;text-de=
coration:none;vertical-align:baseline;white-space:pre-wrap"> for more infor=
mation about =E2=80=A6</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">Remove =E2=80=
=9Csections=E2=80=9D and stick an =E2=80=9Cand=E2=80=9D between them.</span=
></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">Section 6.3.12</span></font></p><font size=
=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">I=E2=80=99m not sure that 310 is the correct length for the first=
 example.=C2=A0 I get 312.=C2=A0 Am I misunderstanding how this gets determ=
ined?=C2=A0 I get this by adding the length of each line (including the emp=
ty ones) plus two for each line representing the terminating CRLF.</span></=
font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">Using that method, the second example also app=
ears to be off by two.</span></font></p><font size=3D"2"><br></font><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">Section 6.3.13=
</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0Without the IDLE command=
 a client requires to poll the server for</span></font></p><font size=3D"2"=
><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">s/requires/needs/ (or maybe =E2=80=9Cwould need=E2=80=9D)</span></font>=
</p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap">=C2=A0=C2=A0responses at any time.=C2=A0 If the ser=
ver choose to send unsolicited</span></font></p><font size=3D"2"><br></font=
><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"=
><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-weight:400;font-style:normal;font-variant:normal=
;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/choos=
e/chooses/</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><s=
pan style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparen=
t;font-weight:400;font-style:normal;font-variant:normal;text-decoration:non=
e;vertical-align:baseline;white-space:pre-wrap">The specific advice about r=
eissuing IDLE every 29 minutes presumes the auto-logout timeout is fixed at=
 30 minutes.=C2=A0 Since I think I read higher up that this could be some o=
ther time limit, it might be a good thing to negotiate somehow via a capabi=
lity, or the continuation reply to IDLE, or something like that.</span></fo=
nt></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-fam=
ily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;fon=
t-style:normal;font-variant:normal;text-decoration:none;vertical-align:base=
line;white-space:pre-wrap">Section 6.4.2</span></font></p><font size=3D"2">=
<br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,=
0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wra=
p">=C2=A0=C2=A0=C2=A0The UNSELECT command frees server&#39;s resources asso=
ciated with the</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0selected mailbox and returns the=
 server to the authenticated state.</span></font></p><font size=3D"2"><br><=
/font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I =
suggest changing =E2=80=9Cserver=E2=80=99s=E2=80=9D to =E2=80=9Csession=E2=
=80=99s=E2=80=9D.=C2=A0 As written here, it could be read to say you=E2=80=
=99re deleting the selected mailbox.</span></font></p><font size=3D"2"><br>=
</font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-botto=
m:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:=
normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">S=
ection 6.4.4</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">The use of =E2=80=9C(*)=
=E2=80=9D to make a footnote that=E2=80=99s actually just the next paragrap=
h can probably be eliminated by just merging the paragraphs.</span></font><=
/p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);backg=
round-color:transparent;font-weight:400;font-style:normal;font-variant:norm=
al;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><br><=
/span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decora=
tion:none;vertical-align:baseline;white-space:pre-wrap">OLD:</span><span st=
yle=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font=
-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vert=
ical-align:baseline;white-space:pre-wrap"><br></span><span style=3D"font-fa=
mily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;fo=
nt-style:normal;font-variant:normal;text-decoration:none;vertical-align:bas=
eline;white-space:pre-wrap"><br></span><span style=3D"font-family:Arial;col=
or:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norma=
l;font-variant:normal;text-decoration:none;vertical-align:baseline;white-sp=
ace:pre-wrap"> =C2=A0 Individual options may contain parameters enclosed in=
</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">=C2=A0=C2=A0=C2=A0parentheses (*).=C2=A0 If an option has paramet=
ers, they consist of atoms</span></font></p><p dir=3D"ltr" style=3D"line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D=
"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weigh=
t:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0and/or strings and/or=
 lists in a specific order.=C2=A0 Any options not</span></font></p><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font =
size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=
=C2=A0defined by extensions that the server supports must be rejected with<=
/span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fon=
t-variant:normal;text-decoration:none;vertical-align:baseline;white-space:p=
re-wrap">=C2=A0=C2=A0=C2=A0a BAD response.</span></font></p><font size=3D"2=
"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin=
-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,=
0,0);background-color:transparent;font-weight:400;font-style:normal;font-va=
riant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-w=
rap">=C2=A0=C2=A0=C2=A0(*) - if an option has a mandatory parameter, which =
can always be</span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0represented as a number or a seque=
nce-set, the option parameter does</span></font></p><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span =
style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;fo=
nt-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ve=
rtical-align:baseline;white-space:pre-wrap">=C2=A0=C2=A0=C2=A0not need the =
enclosing ().=C2=A0 See the ABNF for more details.</span></font></p><font s=
ize=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap">NEW:</span><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:=
normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><=
br></span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-colo=
r:transparent;font-weight:400;font-style:normal;font-variant:normal;text-de=
coration:none;vertical-align:baseline;white-space:pre-wrap"><br></span><spa=
n style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;=
font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;=
vertical-align:baseline;white-space:pre-wrap">Individual options may contai=
n parameters enclosed in parentheses.=C2=A0 (However, if an option has a ma=
ndatory parameter, which can always be represented as a number or a sequenc=
e-set, the option parameter does not need the enclosing parentheses.=C2=A0 =
See the ABNF for more details).=C2=A0 If an option has parameters, they con=
sist of atoms and/or strings and/or lists in a specific order.=C2=A0 Any op=
tions not defined by extensions that the server supports MUST be rejected w=
ith a BAD response.</span></font></p><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap"><br></span><span style=3D"font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">(END)</span><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
"><br><br></span></font></p><p dir=3D"ltr" style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style=
:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;wh=
ite-space:pre-wrap">In =E2=80=9CReturn number of the messages=E2=80=9D, I t=
hink it should be =E2=80=9CReturn the number of messages=E2=80=9D.</span></=
font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">The definitions of several search keys should =
be reviewed to ensure use of the terms =E2=80=9Cheader field=E2=80=9D (not =
simply =E2=80=9Cheader=E2=80=9D) and =E2=80=9Cheader field value=E2=80=9D a=
ppropriately, matching current convention.</span></font></p><font size=3D"2=
"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin=
-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,=
0,0);background-color:transparent;font-weight:400;font-style:normal;font-va=
riant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-w=
rap">Does TEXT matching ignore line breaks?=C2=A0 For instance, does search=
ing for =E2=80=9Cfoo bar=E2=80=9D match =E2=80=9Cfoo&lt;newline&gt;bar=E2=
=80=9D?=C2=A0 Given the text about flexible matching, I was wondering.</spa=
n></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">Section 6.4.4.2</span></font></p><font siz=
e=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:=
rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;f=
ont-variant:normal;text-decoration:none;vertical-align:baseline;white-space=
:pre-wrap">=E2=80=9Cas described in by</span><a href=3D"https://tools.ietf.=
org/html/draft-ietf-extra-imap4rev2-22#section-5.5" style=3D"text-decoratio=
n:none"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:=
transparent;font-weight:400;font-style:normal;font-variant:normal;text-deco=
ration:none;vertical-align:baseline;white-space:pre-wrap"> </span><span sty=
le=3D"font-family:Arial;color:rgb(17,85,204);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant:normal;text-decoration:underl=
ine;vertical-align:baseline;white-space:pre-wrap">Section 5.5</span></a><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap">.=E2=80=9D -- s/in by/in/</s=
pan></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-al=
ign:baseline;white-space:pre-wrap">Section 6.4.4.4</span></font></p><font s=
ize=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap">I think the inline comments in the various examples don=E2=80=
=99t really need to be inline.=C2=A0 They could just as easily be prose bel=
ow each example.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D=
"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">Section 6.4.7</span><=
/font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1=
.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-=
family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;=
font-style:normal;font-variant:normal;text-decoration:none;vertical-align:b=
aseline;white-space:pre-wrap">There=E2=80=99s a lot of SHOULD and SHOULD NO=
T here that make me think a discussion of why one might do otherwise would =
be helpful.=C2=A0 There are otherwise too many different ways in which this=
 command could legitimately behave.</span></font></p><font size=3D"2"><br><=
/font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Se=
ction 6.5</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap">Is this appropriate in light=
 of BCP 178?</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">Section 7.1</span></font>=
</p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap">Why would CONTACTADMIN be returned as part of an OK=
 message, such as in the example given?=C2=A0 I read that as =E2=80=9CYour =
login was successful, but you should contact your help desk.=E2=80=9D</span=
></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">Section 7.2.2</span></font></p><font size=
=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">The stuff about capability names starting with =E2=80=9CX=E2=80=
=9D should be reviewed in light of BCP 178.</span></font></p><font size=3D"=
2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0=
,0,0);background-color:transparent;font-weight:400;font-style:normal;font-v=
ariant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-=
wrap">Section 7.2 and its subsections</span></font></p><font size=3D"2"><br=
></font><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bott=
om:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);=
background-color:transparent;font-weight:400;font-style:normal;font-variant=
:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=
A fair bit of this text is repeated verbatim from earlier sections and shou=
ld probably be consolidated.=C2=A0 I really noticed this when I hit Section=
 7.2.3 where, for instance, \HasChildren is defined both here and in Sectio=
n 6.3.9.5, with the paragraphs in both sections being identical.=C2=A0 Howe=
ver, now that I look earlier in 7.2.2, I see the same issue.</span></font><=
/p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">Section 7.4.2</span></font></p><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><sp=
an style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent=
;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none=
;vertical-align:baseline;white-space:pre-wrap"><br></span><span style=3D"fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">In the ENVELOPE section, there are referen=
ces to =E2=80=9Cheader=E2=80=9D that should be =E2=80=9Cheader field=E2=80=
=9D.</span></font></p><font size=3D"2"><br></font><p dir=3D"ltr" style=3D"l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt"><font size=3D"2"><span st=
yle=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font=
-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vert=
ical-align:baseline;white-space:pre-wrap">Section 13.1</span></font></p><p =
dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fo=
nt size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap"><br></span>=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">RFCs 2152 and 2180 are no=
rmative downrefs; please make sure the shepherd writeup calls this out.</sp=
an></font></p><font size=3D"2"><br></font></div><font size=3D"2">-MSK<br></=
font><div><font size=3D"2"><br></font></div></div>

--000000000000cea78a05b80ebd11--


From nobody Mon Jan  4 05:50:59 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 26DB63A0D32; Mon,  4 Jan 2021 05:50:58 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <160976825803.12012.250270064054300375@ietfa.amsl.com>
Date: Mon, 04 Jan 2021 05:50:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/N_Kjoi92OPdju48HzNpyzjUTBvA>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-23.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, 04 Jan 2021 13:50:58 -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-23.txt
	Pages           : 163
	Date            : 2021-01-04

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-23
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-23

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


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 Jan  4 05:56:02 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 2F6FF3A0CC5 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 05:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.461
X-Spam-Level: 
X-Spam-Status: No, score=-0.461 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.262, 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 uLzg5UNXlQLr for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 05:55:59 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id AB8E33A0D3D for <extra@ietf.org>; Mon,  4 Jan 2021 05:55:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609768558; d=isode.com; s=june2016; i=@isode.com; bh=ZsfmWqtv1jmPWdGOjA96TjbtA8AWYkKKAvjfb4qwJ+U=; 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=pRGLVD6Z7dz9239uxhZybI4VK2LMlf+QB+Y4NQoMVqW5KgvVq6kNssu1FLJPgVRxYdareQ KSGBollf1/x+P9+PUwMWpZIHzuY23M68Ti+YyxBk4O05wx24VsMrns+9qoN5TE5NRFeAWC Xj0NWV02QVewxVcj4DcTxEYm4gq851M=;
Received: from [192.168.1.222] (host31-49-142-65.range31-49.btcentralplus.com [31.49.142.65])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <X=MebgAuQTF0@waldorf.isode.com>; Mon, 4 Jan 2021 13:55:58 +0000
To: extra@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
References: <160976825803.12012.250270064054300375@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5522e027-4875-ac1d-5d1f-6eeac70afee1@isode.com>
Date: Mon, 4 Jan 2021 13:55:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <160976825803.12012.250270064054300375@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/LWMimtJ8V2nCYAa44wb8wjAFwc0>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-23.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, 04 Jan 2021 13:56:01 -0000

Happy New Year everyone,

On 04/01/2021 13:50, 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-23
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-23
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-23

This version addresses most of editorial comments from Murray's AD 
review. I will send a separate email replying to the AD review.

Best Regards,

Alexey


From nobody Mon Jan  4 06:05:27 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 D45793A0D5D for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 06:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.45
X-Spam-Level: 
X-Spam-Status: No, score=-0.45 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.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 X4P80WzMQomL for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 06:05:22 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 4C02B3A0D50 for <extra@ietf.org>; Mon,  4 Jan 2021 06:05:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609769121; d=isode.com; s=june2016; i=@isode.com; bh=lw7+eGp/aq/aauN2mUw5EY2spJvCnyIjuqGy1xqHIfY=; 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=LQrNNANyk7mHEJqRLQhZ0XQEf2TNYcazOWYn7P7Z+C1P8HRW54Utd1uORCPVJrTAfYxNbA Vjw0P3m0n3S4eIL3FtIejQ9ZCy5xd8wCnbOy8ZLXOF+GhVwLSpdftSn3uuo9ZAFwFquMXi wq8Q6bdgOaSkWslCg9gRdtIlBMMC530=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=MgnwBqmjXa@statler.isode.com>; Mon, 4 Jan 2021 14:05:19 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
Message-ID: <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com>
Date: Mon, 4 Jan 2021 14:05:18 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------5E1CD11D2713ED3CA11A10A7"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/HqbE5a61SSAq5Ol10tdvz8vWUYw>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 14:05:26 -0000

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

Hi Murray,

Thank you for your detailed review! Below I removed some comments I=20
still need to act upon/investigate. Detailed replies below:

On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>
> At long last. Thanks for your patience. This is a lot of material to=20
> sift through! This AD review is based on -22.=C2=A0 I=E2=80=99m coming at =
this as=20
> someone who has made almost no direct use of IMAP as a user and=20
> certainly never implemented it, so expect some neophyte-style feedback=20
> here.=C2=A0 I also (briefly) reviewed the diff between RFC 3501 and this=
=20
> version.
>
> Away we go...
>
>
> Section 1.2
>
>
> Should the =E2=80=9CC:=E2=80=9D and =E2=80=9CS:=E2=80=9D paragraph also me=
ntion that CRLF termination=20
> is implicit in examples?=C2=A0 I realize Section 2.2 makes it clear that=
=E2=80=99s=20
> the protocol anyway, so maybe this isn=E2=80=99t necessary, but I=E2=80=99=
ve seen it=20
> made explicit in other documents so I thought I=E2=80=99d mention it.
>
CRLF is implied by use of term "line" (which is defined later in the=20
document), but I clarified this here.
>
> Section 2.2.1
>
> =C2=A0 Clients MUST follow the syntax outlined in this specification
>
> =C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send a command w=
ith missing or
>
> =C2=A0=C2=A0=C2=A0extraneous spaces or arguments.
>
>
> It seems unnecessary to say this in a standards track document.=C2=A0=20
> There=E2=80=99s a similar paragraph in Section 2.2.2.
>
I think the text is there due to various bugs in implementations, so I=20
would rather keep it as is.

> Section 2.2.2
>
> =C2=A0=C2=A0=C2=A0In=C2=A0the case of certain server data, the data MUST b=
e recorded.
>
>
> This seems misplaced; the MUST should be in the descriptions for the=20
> specific cases where this requirement exists.
>
I think this text is actually Ok where it is, as it warns/requires the=20
client to implement proper cashing. It is more a statement of intent.

If you think use of RFC 2119 language here is not right, we can discuss=20
that.

>
> Section 2.3
>
>
> Most of the subsections below here start with a clause that defines=20
> the term, but it=E2=80=99s not a sentence.=C2=A0 This may be personal pref=
erence,=20
> but I suggest adjusting them slightly so they=E2=80=99re sentences.=C2=A0 =
I=E2=80=99ve=20
> included an example below where I have an adjacent suggestion and thus=20
> fixed the whole paragraph.
>
I think I fixed these.
>
> Section 2.3.1.1
>
> =E2=80=9CSTRONGLY ENCOURAGES=E2=80=9D in all caps seems awkward.=C2=A0 I=
=E2=80=99m tempted to say=20
> something about it not being valid BCP 14, etc.
>
Changed.
>
> Section 2.3.2
>
>
> The opening sentence isn=E2=80=99t a sentence.=C2=A0 Also later, =E2=80=9C=
Keyword=E2=80=9D is=20
> introduced without indicating that it=E2=80=99s one of the two possible fl=
ag=20
> types (which I believe to be the case).=C2=A0 I suggest:
>
> =C2=A0 A message has associated with it a list of zero or more named token=
s,
>
> =C2=A0=C2=A0=C2=A0known as =E2=80=9Cflags=E2=80=9D. A flag is set by its a=
ddition to this list, and=20
> is cleared by its
>
> =C2=A0=C2=A0=C2=A0removal. There are two types of flags in IMAP4rev2: syst=
em flags,=20
> and keywords.
>
> =C2=A0=C2=A0=C2=A0A flag of either type can also be permanent or session-o=
nly.
>
This is much better. Thank you.
>
> Second paragraph: s/begin/begins/
>
>
> s/in used in/in use in/
>
Applied, thanks
>
> The text surrounding $Phishing goes further into human factors work=20
> than other working groups have felt appropriate.=C2=A0 (DKIM and DMARC com=
e=20
> to mind.)=C2=A0 Are we sure that belongs here?
>
Yes, considering this is a security consideration, a good example of UI=20
is necessary here.
>
> It seems strange to oblige a client detecting both $Junk and $NotJunk=20
> being set to deal with that condition by fixing it.=C2=A0 The advice to=20
> ignore them is fine, however.
>
This is how they were defined when they were registered. I appreciate=20
that this might be strange, but changing semantics at this point is not=20
going to work.

If you suggest changing the description without changing the semantics,=20
we should consider this.

> It=E2=80=99s also curious to put a normative SHOULD on registering keyword=
s,=20
> as IANA activity is outside of the protocol.
>
I've seen this done in other RFCs. This is a requirement on=20
implementors, which might look odd, but I think this is still a=20
legitimate use of RFC 2119 keyword.
>
> It=E2=80=99s more typical to say you SHOULD ignore keywords you don=E2=80=
=99t=20
> recognize, and then make a reference to the registry.
>
>
> Should this section mention whether the system flags are permanent?=C2=A0=
=20
> \Seen, for example, is clearly a system flag, but it could also be a=20
> session flag.
>
No, implementations differ and sometimes even \Seen is not permanent.=20
(The last sentence of the first paragraph already says "A flag of either=20
type can also be permanent or session-only.")


> Section 2.3.3
>
>
> All the SHOULDs in here make me wonder when an implementor might=20
> legitimately choose to do something different.=C2=A0 Or maybe instead of=
=20
> =E2=80=9CSHOULD be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?
>
I think for delivery by SMTP, I agree. For COPY/MOVE there is actually a=20
posibility that some mailstores wouldn't preserve original values, so=20
this is asking them to really think hard about preserving it.

And for APPEND, this is a similar requirement on MUAs to preserve this=20
information. (Some don't and it is very awkward.)

So I prefer to keep the last 2 SHOULDs.

> Section 4.3
>
> 4th paragraph: s/alternate/alternative/
>
 =C2=A0[snip]
>
> Section 5.1.2.1
>
>
> Although both =E2=80=9CImplementer=E2=80=9D and =E2=80=9CImplementor=E2=80=
=9D appear to be correct,=20
> you use the latter everywhere in the document except here.=C2=A0 (Actually=
,=20
> Google docs suggests the former.)
>
I changed it to implementors and I am happy for RFC Editor to tell me=20
which one they prefer ;-)
>
> Section 5.2
>
>
> =E2=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D=C2=A0 This isn=E2=
=80=99t a specific=20
> normative statement, so I=E2=80=99d use the lowercase version here, and us=
e=20
> BCP 14 language when you=E2=80=99re presenting specific cases.
>
I agree. Changed.

 =C2=A0[snip]
>
> Section 6.1.2
>
>
> This section says NOOP can be used to reset the autologout timer=20
> (which seems definite), but Section 5.1.4 says any command only SHOULD=20
> reset the timer.=C2=A0 Do these line up?
>
(I assume you meant 5.4)

Well spotted. I changed text in 5.4 to readL

 =C2=A0The receipt of any command from the client during that interval reset=
s=20
the autologout timer.

>
> Section 6.2
>
>
> s/alternate/alternative/
>
Changed.
>
> Section 6.2.3
>
> I think there=E2=80=99s an =E2=80=9Cor=E2=80=9D missing in the last paragr=
aph.
>
This looks Ok to me. Can you elaborate?

 =C2=A0[snip]

> This section should make it more explicit, up front, that the response=20
> names the extensions that were successfully enabled.=C2=A0 Right now the=
=20
> lede is buried in about the 7th paragraph.
I didn't move the paragraph that talks about ENABLED response, but I=20
clarified it.
>
> Section 6.3.2
>
>
> Where is =E2=80=9CParagraph 10=E2=80=9D?
>
This is pointing to paragraph 10 within Section 7.1. (Server Responses -=20
Status Responses). I.e. this is pointing to the CLOSED response code=20
definition.


This looks like an xml2rfc glitch and I added a note in XML for RFC=20
Editor to look at it.

>
> Section 6.3.4
>
>
> The all-caps =E2=80=9CUNLESS=E2=80=9D should probably be lowercase-ized.
>
>
> Section 6.3.5
>
>
> Same remark about =E2=80=9CUNLESS=E2=80=9D.
>
>
> Section 6.3.6
>
>
> Same remark about =E2=80=9CUNLESS=E2=80=9D.
>
Changed all 3.
>
> It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D
>
This is saying that the server wouldn't return "BAD" to it.
>
> followed immediately by =E2=80=9Csome servers don=E2=80=99t let you do thi=
s=E2=80=9D.
>
But this is saying that the server can still return "NO".
>
> Which is the standard for this version of IMAP?=C2=A0 If it=E2=80=99s an=
=20
> implementation choice, I think that=E2=80=99s what this should say.
>
Yes, it is.
>
> Section 6.3.9
>
>
> =C2=A0=C2=A0=C2=A0The LIST command returns a subset of names from the comp=
lete set of
>
> =C2=A0=C2=A0=C2=A0all names available to the client.
>
>
> Names of what?
>
Mailbox names. I will clarify.
>
> =C2=A0=C2=A0=C2=A0Clients SHOULD use the empty reference
>
> =C2=A0=C2=A0=C2=A0argument.
>
>
> Why might I not do this?
>
If you want "change directory" kind of behaviour (where the directory is=20
the reference name argument).
>
> =C2=A0=C2=A0=C2=A0=C2=A0For example, here are some examples =E2=80=A6
>
>
> You can probably drop =E2=80=9CFor example,=E2=80=9D.
>
Done.
>
> Section 6.3.9.2
>
>
> This section (and the previous) require that \Subscribed be computed=20
> accurately before the response is generated.=C2=A0 How does this square=20
> with the text in Section 6.3.9 that insists replies come quickly?
>
You have to comply with both :-). It is quite important for \Subscribed=20
to be accurate, so implementations need to do that while maintaining=20
reasonable performance.


 =C2=A0[snip]

>
> The second paragraph also gets into the presentation of the reply.=C2=A0=
=20
> This is human factors stuff the IETF tends to avoid.=C2=A0 Are we sure it=
=20
> belongs here?
>
This is copy of the text from another RFC and I personally found this=20
text to be useful when implementing.
>
> Section 6.3.9.6
>
>
> =C2=A0=C2=A0=C2=A0=C2=A0Servers SHOULD ONLY return =E2=80=A6
>
>
> I think =E2=80=9CONLY=E2=80=9D should be lowercase here (confusion with BC=
P 14).
>
Changed.
>
> Section 6.3.9.7
>
>
> =C2=A0=C2=A0=C2=A0another user renaming of deleting the
>
>
> s/of/or/
>
Fixed, thank you.


 =C2=A0[snip]

>
> Section 6.3.10
>
>
> =C2=A0=C2=A0=C2=A0The NAMESPACE command causes a single ungagged NAMESPACE=
 =E2=80=A6
>
>
> You probably meant =E2=80=9Cuntagged=E2=80=9D, unless NAMESPACE is general=
ly noisy.
>
Thank you :-)
>
> =C2=A0=C2=A0In this example, a server supports 2 Personal Namespaces.=C2=
=A0 =E2=80=A6
>
>
> s/2/two/
>
>
> There=E2=80=99s a reference to X-PARAM in here that probably needs updatin=
g in=20
> light of BCP 178.
>
>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0refer to sectionsSection 7,
>
> =C2=A0Section 7.3.1 for more information about =E2=80=A6
>
>
> Remove =E2=80=9Csections=E2=80=9D and stick an =E2=80=9Cand=E2=80=9D betwe=
en them.
>
Changed.
>
> Section 6.3.12
>
>
> I=E2=80=99m not sure that 310 is the correct length for the first example.=
=C2=A0 I=20
> get 312.
>
I just checked and I got 310.
>
> Am I misunderstanding how this gets determined?=C2=A0 I get this by adding=
=20
> the length of each line (including the empty ones) plus two for each=20
> line representing the terminating CRLF.
>
Correct. But note that the CRLF at the end of the command (it appears as=20
an empty line) doesn't count, because it is part of the command line,=20
not the literal itself.
>
> Using that method, the second example also appears to be off by two.
>
>
> Section 6.3.13
>
>
> =C2=A0=C2=A0Without the IDLE command a client requires to poll the server =
for
>
>
> s/requires/needs/ (or maybe =E2=80=9Cwould need=E2=80=9D)
>
>
> =C2=A0=C2=A0responses at any time.=C2=A0 If the server choose to send unso=
licited
>
>
> s/choose/chooses/
>
Fixed.
>
> The specific advice about reissuing IDLE every 29 minutes presumes the=20
> auto-logout timeout is fixed at 30 minutes.=C2=A0 Since I think I read=20
> higher up that this could be some other time limit, it might be a good=20
> thing to negotiate somehow via a capability, or the continuation reply=20
> to IDLE, or something like that.
>
The limit can't be smaller than 30 minutes, without violating IMAP4rev2.=20
So 29 limit is a safe default that should work in all cases.

Unfortunately there is no way to advertise the limit at the moment.

> Section 6.4.2
>
>
> =C2=A0=C2=A0=C2=A0The UNSELECT command frees server's resources associated=
 with the
>
> =C2=A0=C2=A0=C2=A0selected mailbox and returns the server to the authentic=
ated state.
>
>
> I suggest changing =E2=80=9Cserver=E2=80=99s=E2=80=9D to =E2=80=9Csession=
=E2=80=99s=E2=80=9D.=C2=A0 As written here, it=20
> could be read to say you=E2=80=99re deleting the selected mailbox.
>
Ok.
>
> Section 6.4.4
>
>
> The use of =E2=80=9C(*)=E2=80=9D to make a footnote that=E2=80=99s actuall=
y just the next=20
> paragraph can probably be eliminated by just merging the paragraphs.
>
>
> OLD:
>
> =C2=A0 Individual options may contain parameters enclosed in
>
> =C2=A0=C2=A0=C2=A0parentheses (*).=C2=A0 If an option has parameters, they=
 consist of atoms
>
> =C2=A0=C2=A0=C2=A0and/or strings and/or lists in a specific order.=C2=A0 A=
ny options not
>
> =C2=A0=C2=A0=C2=A0defined by extensions that the server supports must be r=
ejected with
>
> =C2=A0=C2=A0=C2=A0a BAD response.
>
>
> =C2=A0=C2=A0=C2=A0(*) - if an option has a mandatory parameter, which can =
always be
>
> =C2=A0=C2=A0=C2=A0represented as a number or a sequence-set, the option pa=
rameter does
>
> =C2=A0=C2=A0=C2=A0not need the enclosing ().=C2=A0 See the ABNF for more d=
etails.
>
>
> NEW:
>
> Individual options may contain parameters enclosed in parentheses.=C2=A0=
=20
> (However, if an option has a mandatory parameter, which can always be=20
> represented as a number or a sequence-set, the option parameter does=20
> not need the enclosing parentheses.=C2=A0 See the ABNF for more details).=
=C2=A0=20
> If an option has parameters, they consist of atoms and/or strings=20
> and/or lists in a specific order.=C2=A0 Any options not defined by=20
> extensions that the server supports MUST be rejected with a BAD response.
>
>
> (END)
>
I used your text. Thank you.
>
> In =E2=80=9CReturn number of the messages=E2=80=9D, I think it should be =
=E2=80=9CReturn the=20
> number of messages=E2=80=9D.
>
Changed.
>
> The definitions of several search keys should be reviewed to ensure=20
> use of the terms =E2=80=9Cheader field=E2=80=9D (not simply =E2=80=9Cheade=
r=E2=80=9D) and =E2=80=9Cheader=20
> field value=E2=80=9D appropriately, matching current convention.
>
Ok, I think I found all cases. If you find anything I miss, please let=20
me know.
>
> Does TEXT matching ignore line breaks?=C2=A0 For instance, does searching=
=20
> for =E2=80=9Cfoo bar=E2=80=9D match =E2=80=9Cfoo<newline>bar=E2=80=9D? Giv=
en the text about flexible=20
> matching, I was wondering.
>
It might. Some implementations canonicalize whitespace, so that would=20
match. This is implementation specific.
>
> Section 6.4.4.2
>
>
> =E2=80=9Cas described in by Section 5.5.=E2=80=9D -- s/in by/in/
>
Fixed.

 =C2=A0[snip]

> Section 7.1
>
>
> Why would CONTACTADMIN be returned as part of an OK message, such as=20
> in the example given?=C2=A0 I read that as =E2=80=9CYour login was success=
ful, but=20
> you should contact your help desk.=E2=80=9D
>
You are right, using CONTACTADMIN with NO is more useful. So I've=20
updated the example.

[snip]


> Section 7.4.2
>
> In the ENVELOPE section, there are references to =E2=80=9Cheader=E2=80=9D =
that should=20
> be =E2=80=9Cheader field=E2=80=9D.
>
I hope I caught most of these as well.
>
> Section 13.1
>
> RFCs 2152 and 2180 are normative downrefs; please make sure the=20
> shepherd writeup calls this out.
>
>
> -MSK

--------------5E1CD11D2713ED3CA11A10A7
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 Murray,</p>
    <p>Thank you for your detailed review! Below I removed some comments
      I still need to act upon/investigate. Detailed replies below:<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"
            id=3D"gmail-docs-internal-guid-c926fa8b-7fff-bbc3-8c19-78e7de5a6=
dfc"><font
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">At =
long last.  Thanks for your patience.  This is a lot of material to sift thr=
ough!

This AD review is based on -22.=C2=A0 I=E2=80=99m coming at this as someone =
who has made almost no direct use of IMAP as a user and certainly never impl=
emented it, so expect some neophyte-style feedback here.=C2=A0 I also (brief=
ly) reviewed the diff between RFC 3501 and this version.</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">
</span></font></p>
          <p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fo=
nt
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Awa=
y we go...
</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            1.2</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Shou=
ld
            the =E2=80=9CC:=E2=80=9D and =E2=80=9CS:=E2=80=9D paragraph also=
 mention that CRLF
            termination is implicit in examples?=C2=A0 I realize Section 2.2
            makes it clear that=E2=80=99s the protocol anyway, so maybe this
            isn=E2=80=99t necessary, but I=E2=80=99ve seen it made explicit =
in other
            documents so I thought I=E2=80=99d mention it.</p>
        </div>
      </div>
    </blockquote>
    CRLF is implied by use of term "line" (which is defined later in the
    document), but I clarified this here.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            2.2.1<br>
            <br>
            =C2=A0 Clients MUST follow the syntax outlined in this
            specification</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send a command with m=
issing or</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0extraneous spaces or arguments.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">It =
seems unnecessary to say this in a standards track document.=C2=A0 There=E2=
=80=99s a similar paragraph in Section 2.2.2.</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">I think the text is there due to various bugs in
        implementations, so I would rather keep it as is.</font></p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>Section 2.2.2<br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0In=C2=A0the
            case of certain server data, the data MUST be recorded.</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">This
            seems misplaced; the MUST should be in the descriptions for
            the specific cases where this requirement exists.</p>
        </div>
      </div>
    </blockquote>
    <p>I think this text is actually Ok where it is, as it
      warns/requires the client to implement proper cashing. It is more
      a statement of intent.<br>
    </p>
    <p>If you think use of RFC 2119 language here is not right, we can
      discuss that.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            2.3</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Most
            of the subsections below here start with a clause that
            defines the term, but it=E2=80=99s not a sentence.=C2=A0 This ma=
y be
            personal preference, but I suggest adjusting them slightly
            so they=E2=80=99re sentences.=C2=A0 I=E2=80=99ve included an exa=
mple below where
            I have an adjacent suggestion and thus fixed the whole
            paragraph.</p>
        </div>
      </div>
    </blockquote>
    I think I fixed these.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            2.3.1.1</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">
</span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decorat=
ion:none;vertical-align:baseline;white-space:pre-wrap">=E2=80=9CSTRONGLY ENC=
OURAGES=E2=80=9D in all caps seems awkward.=C2=A0 I=E2=80=99m tempted to say=
 something about it not being valid BCP 14, etc.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Changed.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 2.3.2</span></font></p>
          <font size=3D"2"><br>
          </font>
    =20     <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
 opening sentence isn=E2=80=99t </span></font>a
            sentence.=C2=A0 Also later, =E2=80=9CKeyword=E2=80=9D is introdu=
ced without
            indicating that it=E2=80=99s one of the two possible flag types
            (which I believe to be the case).=C2=A0 I suggest:<br>
            <br>
            =C2=A0 A message has associated with it a list of zero or more
            named tokens,</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0known
            as =E2=80=9Cflags=E2=80=9D. A flag is set by its addition to thi=
s list, and
            is cleared by its</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0removal.=C2=A0
            There are two types of flags in IMAP4rev2: system flags, and
            keywords.</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0A
            flag of either type can also be permanent or session-only.</p>
        </div>
      </div>
    </blockquote>
    This is much better. Thank you.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Seco=
nd
            paragraph: s/begin/begins/</p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/i=
n used in/in use in/</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">A</font>pplied, thanks<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">The
            text surrounding $Phishing goes further into human factors
            work than other working groups have felt appropriate.=C2=A0 (DKI=
M
            and DMARC come to mind.)=C2=A0 Are we sure that belongs here?</p=
>
        </div>
      </div>
    </blockquote>
    Yes, considering this is a security consideration, a good example of
    UI is necessary here.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">It
            seems strange to oblige a client detecting both $Junk and
            $NotJunk being set to deal with that condition by fixing
            it.=C2=A0 The advice to ignore them is fine, however.</p>
        </div>
      </div>
    </blockquote>
    <p>This is how they were defined when they were registered. I
      appreciate that this might be strange, but changing semantics at
      this point is not going to work.</p>
    <p>If you suggest changing the description without changing the
      semantics, we should consider this.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">It=
=E2=80=99s
            also curious to put a normative SHOULD on registering
            keywords, as IANA activity is outside of the protocol.</p>
        </div>
      </div>
    </blockquote>
    I've seen this done in other RFCs. This is a requirement on
    implementors, which might look odd, but I think this is still a
    legitimate use of RFC 2119 keyword.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">It=
=E2=80=99s
            more typical to say you SHOULD ignore keywords you don=E2=80=99t
            recognize, and then make a reference to the registry.</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Shou=
ld
            this section mention whether the system flags are
            permanent?=C2=A0 \Seen, for example, is clearly a system flag,
            but it could also be a session flag.</p>
        </div>
      </div>
    </blockquote>
    <p>No, implementations differ and sometimes even \Seen is not
      permanent. (The last sentence of the first paragraph already says
      "A flag of either type can also be permanent or session-only.")</p>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            2.3.3</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">All
            the SHOULDs in here make me wonder when an implementor might
            legitimately choose to do something different.=C2=A0 Or maybe
            instead of =E2=80=9CSHOULD be=E2=80=9D, just say =E2=80=9Cis=E2=
=80=9D?</p>
        </div>
      </div>
    </blockquote>
    <p>I think for delivery by SMTP, I agree. For COPY/MOVE there is
      actually a posibility that some mailstores wouldn't preserve
      original values, so this is asking them to really think hard about
      preserving it.</p>
    <p>And for APPEND, this is a similar requirement on MUAs to preserve
      this information. (Some don't and it is very awkward.)</p>
    <p>So I prefer to keep the last 2 SHOULDs.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 4.3</span></font><font
            size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">4th
            paragraph: s/alternate/alternative/</p>
        </div>
      </div>
    </blockquote>
    =C2=A0[snip]<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div> <font size=3D"2"></font><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 5.1.2.1</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Alt=
hough both =E2=80=9CImplementer=E2=80=9D and =E2=80=9CImplementor=E2=80=9D a=
ppear to be correct, you use the latter everywhere in the document except he=
re.=C2=A0 (Actually, Google docs suggests the former.)</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">I changed it to implementors and I am happy for RFC
      Editor to tell me which one they prefer ;-)</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 5.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=E2=
=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D=C2=A0 This isn=E2=80=99=
t a specific normative statement, so I=E2=80=99d use the lowercase version h=
ere, and use BCP 14 language when you=E2=80=99re presenting specific cases.<=
/span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">I agree. Changed.</font></p>
    =C2=A0[snip]<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.1.2</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
            This section says NOOP can be used to reset the autologout
            timer (which seems definite), but Section 5.1.4 says any
            command only SHOULD reset the timer.=C2=A0 Do these line up?</p>
        </div>
      </div>
    </blockquote>
    <p>(I assume you meant 5.4)</p>
    <p>Well spotted. I changed text in 5.4 to readL</p>
    <p>=C2=A0The receipt of any command from the client during that interval
      resets the autologout timer.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/a=
lternate/alternative/</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Changed.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.2.3</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">
</span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decorat=
ion:none;vertical-align:baseline;white-space:pre-wrap">I think there=E2=80=
=99s an =E2=80=9Cor=E2=80=9D missing in the last paragraph.</span></font></p=
>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">This looks Ok to me. Can you elaborate?<br>
      </font></p>
    <p><font size=3D"2">=C2=A0[snip]<br>
      </font></p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr"><font size=3D"2"></font>This section should make it
        more explicit, up front, that the response names the extensions
        that were successfully enabled.=C2=A0 Right now the lede is buried i=
n
        about the 7th paragraph.
        <div> </div>
      </div>
    </blockquote>
    I didn't move the paragraph that talks about ENABLED response, but I
    clarified it.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.3.2</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Wher=
e
            is =E2=80=9CParagraph 10=E2=80=9D?<br>
          </p>
        </div>
      </div>
    </blockquote>
    <p>This is pointing to paragraph 10 within Section 7.1. (Server
      Responses - Status Responses). I.e. this is pointing to the CLOSED
      response code definition.<br>
    </p>
    <p><br>
    </p>
    <p>This looks like an xml2rfc glitch and I added a note in XML for
      RFC Editor to look at it.</p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.3.4</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
 all-caps =E2=80=9CUNLESS=E2=80=9D should probably be lowercase-ized.</span>=
</font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.5</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sam=
e remark about =E2=80=9CUNLESS=E2=80=9D.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.6</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sam=
e remark about =E2=80=9CUNLESS=E2=80=9D.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Changed all 3.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">It=
=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D</span>=
</font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">This is saying that the server wouldn't return "BAD"
      to it.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">foll=
owed
            immediately by =E2=80=9Csome servers don=E2=80=99t let you do th=
is=E2=80=9D.</p>
        </div>
      </div>
    </blockquote>
    But this is saying that the server can still return "NO".<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Whic=
h
            is the standard for this version of IMAP?=C2=A0 If it=E2=80=99s =
an
            implementation choice, I think that=E2=80=99s what this should s=
ay.</p>
        </div>
      </div>
    </blockquote>
    Yes, it is.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.3.9</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0The LIST command returns a subset of names from the complete =
set of</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0all names available to the client.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Nam=
es of what?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Mailbox names. I will clarify.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0Clients SHOULD use the empty reference</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0argument.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Why=
 might I not do this?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">If you want "change directory" kind of behaviour
      (where the directory is the reference name argument).</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0=C2=A0For example, here are some examples =E2=80=A6</span></f=
ont></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">You=
 can probably drop =E2=80=9CFor example,=E2=80=9D.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Done.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.9.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Thi=
s section (and the previous) require that \Subscribed be computed accurately=
 before the response is generated.=C2=A0 How does this square with the text =
in Section 6.3.9 that insists replies come quickly?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">You have to comply with both :-). It is quite
      important for \Subscribed to be accurate, so implementations need
      to do that while maintaining reasonable performance.</font><br>
    <p><br>
    </p>
    <p><font size=3D"2">=C2=A0[snip]</font><br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"></font><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
 second paragraph also gets into the presentation of the reply.=C2=A0 This i=
s human factors stuff the IETF tends to avoid.=C2=A0 Are we sure it belongs =
here?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">This is copy of the text from another RFC and I
      personally found this text to be useful when implementing.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.9.6</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0=C2=A0Servers SHOULD ONLY return =E2=80=A6</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I t=
hink =E2=80=9CONLY=E2=80=9D should be lowercase here (confusion with BCP 14)=
.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Changed.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.9.7</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0another user renaming of deleting the</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/o=
f/or/</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Fixed, thank you.</font><br>
    <p><br>
    </p>
    <p><font size=3D"2">=C2=A0[snip]</font><br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"></font><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.10</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0The NAMESPACE command causes a single ungagged NAMESPACE =E2=
=80=A6</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">You=
 probably meant =E2=80=9Cuntagged=E2=80=9D, unless NAMESPACE is generally no=
isy.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Thank you :-)</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0In this example, a server supports 2 Personal Namespaces.=C2=A0 =E2=
=80=A6</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">s/2/=
two/</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Ther=
e=E2=80=99s
            a reference to X-PARAM in here that probably needs updating
            in light of BCP 178.</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0refer
            to sections<span style=3D"text-decoration:none"> Section 7</span=
>,</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0<span
              style=3D"text-decoration:none">=C2=A0Section 7.3.1</span> for
            more information about =E2=80=A6</p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Rem=
ove =E2=80=9Csections=E2=80=9D and stick an =E2=80=9Cand=E2=80=9D between th=
em.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Changed.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3</span></font>.12</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">I=E2=
=80=99m
            not sure that 310 is the correct length for the first
            example.=C2=A0 I get 312. <br>
          </p>
        </div>
      </div>
    </blockquote>
    I just checked and I got 310.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Am
            I misunderstanding how this gets determined?=C2=A0 I get this by
            adding the length of each line (including the empty ones)
            plus two for each line representing the terminating CRLF.</p>
        </div>
      </div>
    </blockquote>
    Correct. But note that the CRLF at the end of the command (it
    appears as an empty line) doesn't count, because it is part of the
    command line, not the literal itself.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Usin=
g
            that method, the second example also appears to be off by
            two.</p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.3.13</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0Without the IDLE command a client requires to poll the server for</=
span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/r=
equires/needs/ (or maybe =E2=80=9Cwould need=E2=80=9D)</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0responses at any time.=C2=A0 If the server choose to send unsolicit=
ed</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">s/c=
hoose/chooses/</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Fixed.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
 specific advice about reissuing IDLE every 29 minutes presumes the auto-log=
out timeout is fixed at 30 minutes.=C2=A0 Since I think I read higher up tha=
t this could be some other time limit, it might be a good thing to negotiate=
 somehow via a capability, or the continuation reply to IDLE, or something l=
ike that.</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">The limit can't be smaller than 30 minutes,
        without violating IMAP4rev2. So 29 limit is a safe default that
        should work in all cases.</font></p>
    <p><font size=3D"2">Unfortunately there is no way to advertise the
        limit at the moment.</font><br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.4.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0The UNSELECT command frees server's resources associated with=
 the</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=C2=
=A0=C2=A0=C2=A0selected mailbox and returns the server to the authenticated =
state.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I s=
uggest changing =E2=80=9Cserver=E2=80=99s=E2=80=9D to =E2=80=9Csession=E2=80=
=99s=E2=80=9D.=C2=A0 As written here, it could be read to say you=E2=80=99re=
 deleting the selected mailbox.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Ok.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 6.4.4</span></font></p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">The
            use of =E2=80=9C(*)=E2=80=9D to make a footnote that=E2=80=99s a=
ctually just the
            next paragraph can probably be eliminated by just merging
            the paragraphs.</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
            OLD:<br>
            <br>
            =C2=A0 Individual options may contain parameters enclosed in</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0parentheses
            (*).=C2=A0 If an option has parameters, they consist of atoms</p=
>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0and/or
            strings and/or lists in a specific order.=C2=A0 Any options not<=
/p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0defined
            by extensions that the server supports must be rejected with</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0a
            BAD response.</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0(*)
            - if an option has a mandatory parameter, which can always
            be</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0represented
            as a number or a sequence-set, the option parameter does</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0=C2=A0not
            need the enclosing ().=C2=A0 See the ABNF for more details.</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">NEW:=
<br>
            <br>
            Individual options may contain parameters enclosed in
            parentheses.=C2=A0 (However, if an option has a mandatory
            parameter, which can always be represented as a number or a
            sequence-set, the option parameter does not need the
            enclosing parentheses.=C2=A0 See the ABNF for more details).=C2=
=A0 If
            an option has parameters, they consist of atoms and/or
            strings and/or lists in a specific order.=C2=A0 Any options not
            defined by extensions that the server supports MUST be
            rejected with a BAD response.</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
            (END)<br>
          </p>
        </div>
      </div>
    </blockquote>
    I used your text. Thank you.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">
</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">In =
=E2=80=9CReturn number of the messages=E2=80=9D, I think it should be =E2=80=
=9CReturn the number of messages=E2=80=9D.</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">C</font>hanged.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">The
            definitions of several search keys should be reviewed to
            ensure use of the terms =E2=80=9Cheader field=E2=80=9D (not simp=
ly =E2=80=9Cheader=E2=80=9D)
            and =E2=80=9Cheader field value=E2=80=9D appropriately, matching=
 current
            convention.</p>
        </div>
      </div>
    </blockquote>
    Ok, I think I found all cases. If you find anything I miss, please
    let me know.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Does
            TEXT matching ignore line breaks?=C2=A0 For instance, does
            searching for =E2=80=9Cfoo bar=E2=80=9D match =E2=80=9Cfoo&lt;ne=
wline&gt;bar=E2=80=9D?=C2=A0
            Given the text about flexible matching, I was wondering.</p>
        </div>
      </div>
    </blockquote>
    It might. Some implementations canonicalize whitespace, so that
    would match. This is implementation specific.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.4.4.2</p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=E2=
=80=9Cas described in </span></font>by
            Section 5.5.=E2=80=9D -- s/i<font size=3D"2"><span style=3D"font=
-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;=
font-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">n by/in/</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Fixed.</font><br>
    <p>=C2=A0[snip]<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            7.1</p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Why=
 would CONTACTADMIN be returned as part of an OK message, such as in the exa=
mple given?=C2=A0 I read that as =E2=80=9CYour login was successful, but you=
 should contact your help desk.=E2=80=9D</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">You are right, using </font><font size=3D"2"><span s=
tyle=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font=
-weight:400;font-style:normal;font-variant:normal;text-decoration:none;verti=
cal-align:baseline;white-space:pre-wrap">CONTACTADMIN with NO is more useful=
. So I've updated the example.</span></font><font
        size=3D"2"><br>
      </font></p>
    <p><font size=3D"2">[snip]<br>
      </font></p>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"> </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 7.4.2</span></font></p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">
</span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decorat=
ion:none;vertical-align:baseline;white-space:pre-wrap">In the E</span></font=
>NVELOPE
            section, there are references to =E2=80=9Cheader=E2=80=9D that s=
hould be
            =E2=80=9Cheader field=E2=80=9D.</p>
        </div>
      </div>
    </blockquote>
    I hope I caught most of these as well.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            13.1</p>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">
            RFCs 2152 and 2180 are normative downrefs; please make sure
            the shepherd writeup calls this out.</p>
          <br>
        </div>
        -MSK</div>
    </blockquote>
  </body>
</html>

--------------5E1CD11D2713ED3CA11A10A7--


From nobody Mon Jan  4 07:39: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 643B53A0E0A for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 07:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.459
X-Spam-Level: 
X-Spam-Status: No, score=-0.459 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.262, 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 58TsIPuMkFRR for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 07:39:12 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4773A0E07 for <extra@ietf.org>; Mon,  4 Jan 2021 07:39:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609774746; d=isode.com; s=june2016; i=@isode.com; bh=OuT3k9Qf85Pc8P3jI+uud0/wCme0LbFBcq6mnADLO80=; 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=t3iH/3LbIdw2fpavRwMYPDE9o5aTo4diB4NhGXsroU8mMiBDJ+z9h0FYuxOjzbrhCbBwa8 o5XcrDh/uylE6o/trhEzaPkdWYxH8jxAVA1bcS5eSOE9PO8E/J2i0//m/Zt1e41gMS5Dma l29qlQO4l8bnys9So9o88YNVyLfDze4=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=M2mQBqmqay@statler.isode.com>; Mon, 4 Jan 2021 15:39:05 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
Message-ID: <ae15071e-3ab5-2ad0-953b-05856991b287@isode.com>
Date: Mon, 4 Jan 2021 15:39:05 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------94E21C5BA11781724E9EC24A"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/4hvAdNszEeLrg6VArFHOk44wIWA>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 15:39:13 -0000

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

Hi Murray,

Replying to some remaining editorial comments:

On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>
> Section 5.1
>
>
> There=E2=80=99s a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which =
could probably=20
> benefit from a section number reference as well.=C2=A0 This is actually=20
> something I=E2=80=99d thought about many times earlier in the document up =
to=20
> this point, but I=E2=80=99m finally saying something here; some of them we=
re=20
> clear references like this, while others were references to commands=20
> or flags that are =E2=80=9Cdescribed elsewhere in this document=E2=80=9D.
>
I fixed several cases of missing references. If you find anything else I=20
missed, please let me know.

> Section 6.4.4.4
>
>
> I think the inline comments in the various examples don=E2=80=99t really n=
eed=20
> to be inline.=C2=A0 They could just as easily be prose below each example.
>
For some examples this might be more involved than for others. Are you=20
happy for this to be addressed directly with RFC Editor via an XML comment?

> Section 7.2 and its subsections
>
>
> A fair bit of this text is repeated verbatim from earlier sections and=20
> should probably be consolidated.=C2=A0 I really noticed this when I hit=20
> Section 7.2.3 where, for instance, \HasChildren is defined both here=20
> and in Section 6.3.9.5, with the paragraphs in both sections being=20
> identical. However, now that I look earlier in 7.2.2, I see the same=20
> issue.
>
I struggled with some of this, as initially not all mailbox attributes=20
were listed in Section 7.2.3 (LIST Response). In other sections it is=20
had to talk about some options without introducing the corresponding=20
mailbox attribute(s) first. So it would really help to have some=20
specific suggestions on where you think text can be dropped.

Best Regards,

Alexey




--------------94E21C5BA11781724E9EC24A
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 Murray,</p>
    <p>Replying to some remaining editorial comments:<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            5.1</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Ther=
e=E2=80=99s
            a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which could =
probably
            benefit from a section number reference as well.=C2=A0 This is
            actually something I=E2=80=99d thought about many times earlier =
in
            the document up to this point, but I=E2=80=99m finally saying
            something here; some of them were clear references like
            this, while others were references to commands or flags that
            are =E2=80=9Cdescribed elsewhere in this document=E2=80=9D.</p>
        </div>
      </div>
    </blockquote>
    <p> I fixed several cases of missing references. If you find
      anything else I missed, please let me know.</p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.4.4.4</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">I
            think the inline comments in the various examples don=E2=80=99t
            really need to be inline.=C2=A0 They could just as easily be
            prose below each example.</p>
        </div>
      </div>
    </blockquote>
    For some examples this might be more involved than for others. Are
    you happy for this to be addressed directly with RFC Editor via an
    XML comment?<br>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            7.2 and its subsections</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">A
            fair bit of this text is repeated verbatim from earlier
            sections and should probably be consolidated.=C2=A0 I really
            noticed this when I hit Section 7.2.3 where, for instance,
            \HasChildren is defined both here and in Section 6.3.9.5,
            with the paragraphs in both sections being identical.=C2=A0
            However, now that I look earlier in 7.2.2, I see the same
            issue.</p>
        </div>
      </div>
    </blockquote>
    <p>I struggled with some of this, as initially not all mailbox
      attributes were listed in Section 7.2.3 (LIST Response). In other
      sections it is had to talk about some options without introducing
      the corresponding mailbox attribute(s) first. So it would really
      help to have some specific suggestions on where you think text can
      be dropped.</p>
    <p>Best Regards,</p>
    <p>Alexey</p>
    <p><br>
    </p>
    <br>
  </body>
</html>

--------------94E21C5BA11781724E9EC24A--


From nobody Mon Jan  4 09:06:52 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 3FF173A0E9B for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level: 
X-Spam-Status: No, score=-0.188 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 kjIaqpFt3C16 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:06:49 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id B3D973A0E97 for <extra@ietf.org>; Mon,  4 Jan 2021 09:06:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609780008; d=isode.com; s=june2016; i=@isode.com; bh=gjhoZj6r7z+Ji0O4uIiU3mWukDHMOFvy8zqhnsOcy+g=; 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=X+VbkBf+pYJcS1HLCUAiakAUwIlF8lGvEq0ZsKD/mm0oXD1B6DWPC4lG3yf3Yxm0IcNW+n +oxlS9bmiO/VsYheIXNdvhoatZl8KhEwF2EwQ9pS9WsLCiTXoGH5BIk9ohJpDbhYVihyRx S1/LTX413aylXV/ZoCsTG1V7GUMFJlU=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=NLKABqml1u@statler.isode.com>; Mon, 4 Jan 2021 17:06:48 +0000
To: "Murray S. Kucherawy" <superuser@gmail.com>, extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <72a2b1dc-1a9f-07ab-23aa-48dd2048b06e@isode.com>
Date: Mon, 4 Jan 2021 17:06:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------8760C196CF555FE6077B8C47"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/_b5c9aNcxV45UB6BSIhNcBaqF_0>
Subject: [Extra] Response when no Command in Progress (was AD Review of draft-ietf-extra-imap4rev2)
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, 04 Jan 2021 17:06:51 -0000

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

Hi Murray,

I've changed subject for this issue, so that it doesn't get lost in=20
myriad of other replies.

On 04/01/2021 08:18, Murray S. Kucherawy wrote:

> Section 5.3
>
>
> Maybe my understanding is wrong, but if you do a non-blocking write=20
> while you don=E2=80=99t have enough buffer space available, won=E2=80=99t =
some of what=20
> you write be lost, resulting in gibberish at the other end?
>
All the API I've seen tell you how much (possibly 0 octets) were=20
written, so a properly written application will not send gibberish.=20
Because IMAP is line oriented and, in some cases, octet counted (like=20
literals), a partial write is never a problem on the receiving side.
>
> Maybe this needs to mention retries of stuff that couldn=E2=80=99t be sent=
 (if=20
> any) when a non-blocking write returns?
>
Possibly. Can you suggest some text on this point?
>
> I=E2=80=99m tempted to suggest just removing this.=C2=A0 This is something=
 you deal=20
> with at the socket layer, and IMHO isn=E2=80=99t really part of IMAP itsel=
f.
>
Personally, I found warning in this section useful. If it is removed, it=20
is not going to change my implementation ;-).

But seriously: I think I would like WG's feedback on this one.

Thank you,

Alexey


--------------8760C196CF555FE6077B8C47
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 Murray,</p>
    <p>I've changed subject for this issue, so that it doesn't get lost
      in myriad of other replies.<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Sec=
tion 5.3</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">May=
be my understanding is wrong, but if you do a non-blocking write while you d=
on=E2=80=99t have enough buffer space available, won=E2=80=99t some of what =
you write be lost, resulting in gibberish at the other end?</span></font></p=
>
        </div>
      </div>
    </blockquote>
    All the API I've seen tell you how much (possibly 0 octets) were
    written, so a properly written application will not send gibberish.
    Because IMAP is line oriented and, in some cases, octet counted
    (like literals), a partial write is never a problem on the receiving
    side.
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">May=
be this needs to mention retries of stuff that couldn=E2=80=99t be sent (if =
any) when a non-blocking write returns?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">Possibly. Can you suggest some text on this point?</fon=
t><br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">I=
=E2=80=99m tempted to suggest just removing this.=C2=A0 This is something yo=
u deal with at the socket layer, and IMHO isn=E2=80=99t really part of IMAP =
itself.</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">Personally, I fo</font>und warning in this section
      useful. If it is removed, it is not going to change my
      implementation ;-).</p>
    <p>But seriously: I think I would like WG's feedback on this one.</p>
    <p>Thank you,</p>
    <p>Alexey<br>
    </p>
  </body>
</html>

--------------8760C196CF555FE6077B8C47--


From nobody Mon Jan  4 09:18: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 3C4243A0E9F for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level: 
X-Spam-Status: No, score=-0.188 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 Oa3aU5EI3V7P for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:18:53 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 73B543A10D2 for <extra@ietf.org>; Mon,  4 Jan 2021 09:18:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609780715; d=isode.com; s=june2016; i=@isode.com; bh=horZKLizTTUUP1f26QfaVYr9Y8izdrDyMdFynLwShaE=; 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=LrmJdTikwAG1wW/XdSB5qKOQKKsay4CboMlit8mMk2IPkkqZqqaHCfNXi8rT5+5FMWaRVy wlgSybKWbAkxVKAtw2Gx5o5/t0XilIh9X9VjhiE34Uy2UqdRNHM9vxSY0aVofjus9LUK7+ DQLeNkGQ49wLzJWtJzCDkzN92PaQ/w4=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=NN6wBqmiyA@statler.isode.com>; Mon, 4 Jan 2021 17:18:35 +0000
To: "Murray S. Kucherawy" <superuser@gmail.com>, extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <95d4d040-ef4f-8c41-71a4-375b711cf840@isode.com>
Date: Mon, 4 Jan 2021 17:18:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------61E4F683057BCE1932A5FA47"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/S9PhK3HbvcaMFJ_OOcOCvEN0X0U>
Subject: [Extra] Use of SHOULD when describing COPY Command (was AD Review of draft-ietf-extra-imap4rev2)
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, 04 Jan 2021 17:18:55 -0000

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

Hi Murray,

I extracted this issue into another message as well:

On 04/01/2021 08:18, Murray S. Kucherawy wrote:
> Section 6.4.7
>
> There=E2=80=99s a lot of SHOULD and SHOULD NOT here that make me think a=
=20
> discussion of why one might do otherwise would be helpful.=C2=A0 There are=
=20
> otherwise too many different ways in which this command could=20
> legitimately behave.
>

Ok, so below I quote the whole section and try to explain each use of=20
SHOULD/SHOULD NOT:

> =C2=A0=C2=A0 The COPY command copies the specified message(s) to the end o=
f the
> =C2=A0=C2=A0 specified destination mailbox.=C2=A0 The flags and internal d=
ate of the
> =C2=A0=C2=A0 message(s) SHOULD be preserved in the copy.
This use of SHOULD is that some mailstores are less capable and can't=20
preserve this data.
>
> =C2=A0=C2=A0 If the destination mailbox does not exist, a server SHOULD re=
turn an
> =C2=A0=C2=A0 error.
I don't really know the origin of this SHOULD. (Maybe some mailstores=20
can't report back whether a destination mailbox doesn't exist?) This=20
sounds like a MUST to me.
> It SHOULD NOT automatically create the mailbox.
Again, sounds like a MUST NOT.
> Unless it is
> =C2=A0=C2=A0 certain that the destination mailbox can not be created, the =
server
> =C2=A0=C2=A0 MUST send the response code "[TRYCREATE]" as the prefix of th=
e text
> =C2=A0=C2=A0 of the tagged NO response.=C2=A0 This gives a hint to the cli=
ent that it
> =C2=A0=C2=A0 can attempt a CREATE command and retry the COPY if the CREATE=
 is
> =C2=A0=C2=A0 successful.
>
> =C2=A0=C2=A0 If the COPY command is unsuccessful for any reason, server
> =C2=A0=C2=A0 implementations MUST restore the destination mailbox to its s=
tate
> =C2=A0=C2=A0 before the COPY attempt.
>
> =C2=A0=C2=A0 On successful completion of a COPY, the server SHOULD return =
a
> =C2=A0=C2=A0 COPYUID response code (see Section 7.1).
COPYUID was added in an extension, thus the SHOULD. Also see a couple of=20
examples given the the following 2 paragraphs:
> =C2=A0=C2=A0 In the case of a mailbox that has permissions set so that the=
 client
> =C2=A0=C2=A0 can COPY to the mailbox, but not SELECT or EXAMINE it, the se=
rver
> =C2=A0=C2=A0 SHOULD NOT send an COPYUID response code as it would disclose
> =C2=A0=C2=A0 information about the mailbox.
I would be Ok with "MUST NOT" here.
>
> =C2=A0=C2=A0 In the case of a mailbox that has UIDNOTSTICKY status (see
> =C2=A0=C2=A0 Section 7.1), the server MAY omit the COPYUID response code a=
s it is
> =C2=A0=C2=A0 not meaningful.
>
> =C2=A0=C2=A0 If the server does not return the COPYUID response code, the =
client
> =C2=A0=C2=A0 can discover this information by selecting the destination ma=
ilbox.
> =C2=A0=C2=A0 The location of messages placed in the destination mailbox by=
 COPY
> =C2=A0=C2=A0 can be determined by using FETCH and/or SEARCH commands (e.g.=
, for
> =C2=A0=C2=A0 Message-ID).

Best Regards,

Alexey



--------------61E4F683057BCE1932A5FA47
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 Murray,</p>
    <p>I extracted this issue into another message as well:<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div dir=3D"ltr">
        <div><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 6.4.7</span></font><font
            size=3D"2"><br>
          </font>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fon=
t
              size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The=
re=E2=80=99s a lot of SHOULD and SHOULD NOT here that make me think a discus=
sion of why one might do otherwise would be helpful.=C2=A0 There are otherwi=
se too many different ways in which this command could legitimately behave.<=
/span></font></p>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Ok, so below I quote the whole section and try to explain each
      use of SHOULD/SHOULD NOT:</p>
    <p>
      <blockquote type=3D"cite">=C2=A0=C2=A0 The COPY command copies the spe=
cified
        message(s) to the end of the<br>
        =C2=A0=C2=A0 specified destination mailbox.=C2=A0 The flags and inte=
rnal date
        of the<br>
        =C2=A0=C2=A0 message(s) SHOULD be preserved in the copy.<br>
      </blockquote>
      This use of SHOULD is that some mailstores are less capable and
      can't preserve this data.<br>
      <blockquote type=3D"cite"><br>
        =C2=A0=C2=A0 If the destination mailbox does not exist, a server SHO=
ULD
        return an<br>
        =C2=A0=C2=A0 error.</blockquote>
      I don't really know the origin of this SHOULD. (Maybe some
      mailstores can't report back whether a destination mailbox doesn't
      exist?) This sounds like a MUST to me.<br>
      <blockquote type=3D"cite">It SHOULD NOT automatically create the
        mailbox.</blockquote>
      Again, sounds like a MUST NOT.<br>
      <blockquote type=3D"cite">Unless it is<br>
        =C2=A0=C2=A0 certain that the destination mailbox can not be created=
, the
        server<br>
        =C2=A0=C2=A0 MUST send the response code "[TRYCREATE]" as the prefix=
 of
        the text<br>
        =C2=A0=C2=A0 of the tagged NO response.=C2=A0 This gives a hint to t=
he client
        that it<br>
        =C2=A0=C2=A0 can attempt a CREATE command and retry the COPY if the =
CREATE
        is<br>
        =C2=A0=C2=A0 successful.<br>
        <br>
        =C2=A0=C2=A0 If the COPY command is unsuccessful for any reason, ser=
ver<br>
        =C2=A0=C2=A0 implementations MUST restore the destination mailbox to=
 its
        state<br>
        =C2=A0=C2=A0 before the COPY attempt.<br>
        <br>
        =C2=A0=C2=A0 On successful completion of a COPY, the server SHOULD r=
eturn
        a<br>
        =C2=A0=C2=A0 COPYUID response code (see Section 7.1).<br>
      </blockquote>
      COPYUID was added in an extension, thus the SHOULD. Also see a
      couple of examples given the the following 2 paragraphs:<br>
      <blockquote type=3D"cite">=C2=A0=C2=A0 In the case of a mailbox that h=
as
        permissions set so that the client<br>
        =C2=A0=C2=A0 can COPY to the mailbox, but not SELECT or EXAMINE it, =
the
        server<br>
        =C2=A0=C2=A0 SHOULD NOT send an COPYUID response code as it would di=
sclose<br>
        =C2=A0=C2=A0 information about the mailbox.<br>
      </blockquote>
      I would be Ok with "MUST NOT" here.<br>
      <blockquote type=3D"cite"><br>
        =C2=A0=C2=A0 In the case of a mailbox that has UIDNOTSTICKY status (=
see<br>
        =C2=A0=C2=A0 Section 7.1), the server MAY omit the COPYUID response =
code
        as it is<br>
        =C2=A0=C2=A0 not meaningful.<br>
        <br>
        =C2=A0=C2=A0 If the server does not return the COPYUID response code=
, the
        client<br>
        =C2=A0=C2=A0 can discover this information by selecting the destinat=
ion
        mailbox.<br>
        =C2=A0=C2=A0 The location of messages placed in the destination mail=
box by
        COPY<br>
        =C2=A0=C2=A0 can be determined by using FETCH and/or SEARCH commands
        (e.g., for<br>
        =C2=A0=C2=A0 Message-ID).</blockquote>
    </p>
    <p>Best Regards,</p>
    <p>Alexey</p>
    <p><br>
    </p>
  </body>
</html>

--------------61E4F683057BCE1932A5FA47--


From nobody Mon Jan  4 09:21:31 2021
Return-Path: <superuser@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 2E88C3A0EA7 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level: 
X-Spam-Status: No, score=-0.188 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dm5sZmLAa2Bj for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:21:28 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 041053A0EB9 for <extra@ietf.org>; Mon,  4 Jan 2021 09:21:28 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id e15so14926960vsa.0 for <extra@ietf.org>; Mon, 04 Jan 2021 09:21:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NBD9Fk1z18lAtG2p6+meHjPj1lXlacJ/ExjbvxvVSXc=; b=ALcEVrvLManpFAxdHyWCotettFzxs66iBBckdDx/k930caen5tDpMtxhqJq5n/yqBI vxPqzhHchL73SowJeM0cq3atgowlrpZwqcVC/yuUiu/a6ZTRXiXYRsQdXSNZ2HBwdJmM HFEQYnznyyILcooOpvNcQWIuZ+ZonGwU92kNt06z3WTxliyMOZdhI8wHouAfVqICwDdK 3xBbdwZGKj2+eMu+IFSAJuyVjwZNEA+q+PQB+CsnbetKo9bh6tvrT2PYUE5yN1eJtoDa nB1o4w447t4zcC0+BamsK92FokxzxiYBGMUutPLVLqDd3x1gUM1QfGSWCsghtZPZbPlJ Thiw==
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=NBD9Fk1z18lAtG2p6+meHjPj1lXlacJ/ExjbvxvVSXc=; b=MlXkOD+YYd+Y0SHZVd81brEc9ZcHZTMVzLFFc1Juhexve6MQxGIEoHXRD6Hlllo2AW TpgvRiS37iLIwl4zhvKGmQ2bPmj+rXJRZB0llp4VIMv1JUhYVthPGVomggCOBp/fhYmg RJhU/T2hRgjXdA3Wkp76KI8yiHTb7RCqlCqJnSB+YhX1sLON93g9dPg7tNMzkn+9UE4J 1/omN4ZqDuZKCDZW7T+uxjBEUlvJvXD9Bkd4i5V8iWeQUAUco72zcCFz8L9QMNnQYaG/ aycvNyndY21nHmUiYCSUxMe6xp/1ObcJ9JOu4hNhP7YGlYZ1Qhyeysm7DV6JH27oT3AX /KxA==
X-Gm-Message-State: AOAM531NrukoDL9JcwxqNdpOfm6mVxHkVVky1Zd38KqVx86QmOYbQSum 5gUgS3r03SRJw5hLmGbWTlWSnurk3sPTriAg09w=
X-Google-Smtp-Source: ABdhPJwuu5DvLVsAqh2yqjU2VSrGCjnp8yYqYbKlR97ixElHY2PuDgjQHzWYh+310s9b7gEm3dDHsTC2obro53MeqTY=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr44628416vsy.54.1609780886742;  Mon, 04 Jan 2021 09:21:26 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com>
In-Reply-To: <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 4 Jan 2021 09:21:15 -0800
Message-ID: <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ebb65705b816518a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ZVgL89ZnJwYXZEuhiHXxiDm0hQI>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 17:21:30 -0000

--000000000000ebb65705b816518a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

>
> Section 2.2.1
>
>   Clients MUST follow the syntax outlined in this specification
>
>    strictly.  It is a syntax error to send a command with missing or
>
>    extraneous spaces or arguments.
>
> It seems unnecessary to say this in a standards track document.  There=E2=
=80=99s a
> similar paragraph in Section 2.2.2.
>
> I think the text is there due to various bugs in implementations, so I
> would rather keep it as is.
>
I would use "need to" instead of "MUST" here.  It's otherwise a bit
hand-wavy for use of BCP 14 language.  But I'll leave this to the WG.

Section 2.2.2
>
>    In the case of certain server data, the data MUST be recorded.
>
> This seems misplaced; the MUST should be in the descriptions for the
> specific cases where this requirement exists.
>
> I think this text is actually Ok where it is, as it warns/requires the
> client to implement proper cashing. It is more a statement of intent.
>
> If you think use of RFC 2119 language here is not right, we can discuss
> that.
>
Similar to the previous case, I suggest "needs to" here, and then wherever
you talk about certain server data, that's where the BCP 14 language should
go.

I also didn't think you meant caching when you said "recorded"; I took that
to refer to logging.  Possibly something else to clarify.

>
>
> The text surrounding $Phishing goes further into human factors work than
> other working groups have felt appropriate.  (DKIM and DMARC come to
> mind.)  Are we sure that belongs here?
>
> Yes, considering this is a security consideration, a good example of UI i=
s
> necessary here.
>

I'm curious to see if anyone else raises this given how much energy those
other WGs used in the past to resist providing any UI advice at all.

>
> It seems strange to oblige a client detecting both $Junk and $NotJunk
> being set to deal with that condition by fixing it.  The advice to ignore
> them is fine, however.
>
> This is how they were defined when they were registered. I appreciate tha=
t
> this might be strange, but changing semantics at this point is not going =
to
> work.
>

Fair enough.

If you suggest changing the description without changing the semantics, we
> should consider this.
>

No, it's the semantics I found odd, but I realize you're not doing
something new here.

It=E2=80=99s also curious to put a normative SHOULD on registering keywords=
, as
> IANA activity is outside of the protocol.
>
> I've seen this done in other RFCs.
>

Doesn't mean they're right.  :-)

Should this section mention whether the system flags are permanent?  \Seen,
> for example, is clearly a system flag, but it could also be a session fla=
g.
>
> No, implementations differ and sometimes even \Seen is not permanent. (Th=
e
> last sentence of the first paragraph already says "A flag of either type
> can also be permanent or session-only.")
>
Yep, that's what caused me to make the comment.


> Section 2.3.3
>
> All the SHOULDs in here make me wonder when an implementor might
> legitimately choose to do something different.  Or maybe instead of =E2=
=80=9CSHOULD
> be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?
>
> I think for delivery by SMTP, I agree. For COPY/MOVE there is actually a
> posibility that some mailstores wouldn't preserve original values, so thi=
s
> is asking them to really think hard about preserving it.
>
> And for APPEND, this is a similar requirement on MUAs to preserve this
> information. (Some don't and it is very awkward.)
>
> So I prefer to keep the last 2 SHOULDs.
>
I guess I'm wondering if those implementations chose not to for some reason
you think is valid, or was it purely an oversight on their part and you're
using SHOULD to grandfather them in?  Would it be fine to say MUST here and
just say that an implementation not doing this is therefore not compliant
with rev2?


>
> Section 5.1.2.1
>
> Although both =E2=80=9CImplementer=E2=80=9D and =E2=80=9CImplementor=E2=
=80=9D appear to be correct, you
> use the latter everywhere in the document except here.  (Actually, Google
> docs suggests the former.)
>
> I changed it to implementors and I am happy for RFC Editor to tell me
> which one they prefer ;-)
>

Yeah, I'm fine with either.  I just wanted internal consistency.


>
> Section 5.2
>
> =E2=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D  This isn=E2=80=
=99t a specific normative
> statement, so I=E2=80=99d use the lowercase version here, and use BCP 14 =
language
> when you=E2=80=99re presenting specific cases.
>
> I agree. Changed.
>  [snip]
>
>
> Section 6.1.2
>
>
> This section says NOOP can be used to reset the autologout timer (which
> seems definite), but Section 5.1.4 says any command only SHOULD reset the
> timer.  Do these line up?
>
> (I assume you meant 5.4)
>
> Well spotted. I changed text in 5.4 to readL
>
>  The receipt of any command from the client during that interval resets
> the autologout timer.
>
Why would a command deviate from the SHOULD and not reset the timer?

> Section 6.2.3
>
> I think there=E2=80=99s an =E2=80=9Cor=E2=80=9D missing in the last parag=
raph.
>
> This looks Ok to me. Can you elaborate?
>
Uh, no, I can't. Ignore this one.  It was very late.

>  [snip]
>
> This section should make it more explicit, up front, that the response
> names the extensions that were successfully enabled.  Right now the lede =
is
> buried in about the 7th paragraph.
>
> I didn't move the paragraph that talks about ENABLED response, but I
> clarified it.
>

It seems like a pretty important aspect of the response, so I thought it
was strange that it wasn't presented until so late in the section.  Your
call though.


>
> It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D
>
> This is saying that the server wouldn't return "BAD" to it.
>
> followed immediately by =E2=80=9Csome servers don=E2=80=99t let you do th=
is=E2=80=9D.
>
> But this is saying that the server can still return "NO".
>
> Which is the standard for this version of IMAP?  If it=E2=80=99s an imple=
mentation
> choice, I think that=E2=80=99s what this should say.
>
> Yes, it is.
>

That's fine, then, if this is clarified.  I just found that bit to be
self-contradicting as written in -22.


>
>    Clients SHOULD use the empty reference
>
>    argument.
>
> Why might I not do this?
>
> If you want "change directory" kind of behaviour (where the directory is
> the reference name argument).
>

Ah, yes.  Then this could use a bit of clarification.


>
> Section 6.3.9.2
>
> This section (and the previous) require that \Subscribed be computed
> accurately before the response is generated.  How does this square with t=
he
> text in Section 6.3.9 that insists replies come quickly?
>
> You have to comply with both :-). It is quite important for \Subscribed t=
o
> be accurate, so implementations need to do that while maintaining
> reasonable performance.
>

OK.  I just wanted to make sure the reader isn't getting "You MUST be
fast!" from one direction while also doing "You MUST do all this expensive
stuff!" from the other with no guidance about how to resolve this.

>
>
>  [snip]
>
>
> The second paragraph also gets into the presentation of the reply.  This
> is human factors stuff the IETF tends to avoid.  Are we sure it belongs
> here?
>
> This is copy of the text from another RFC and I personally found this tex=
t
> to be useful when implementing.
>

You might consider putting these presentation advice paragraphs into an
appendix too.

-MSK

--000000000000ebb65705b816518a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 4, 2021 at 6:05 AM Alexey=
 Melnikov &lt;<a href=3D"mailto:alexey.melnikov@isode.com">alexey.melnikov@=
isode.com</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div><blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            2.2.1<br>
            <br>
            =C2=A0 Clients MUST follow the syntax outlined in this
            specification</p>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">=C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send a command =
with missing or</span></font></p>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">=C2=A0=C2=A0=C2=A0extraneous spaces or arguments.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">It seems unnecessary to say this in a standards track document.=C2=A0 The=
re=E2=80=99s a similar paragraph in Section 2.2.2.</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">I think the text is there due to various bugs in
        implementations, so I would rather keep it as is.</font></p></div><=
/blockquote><div>I would use &quot;need to&quot; instead of &quot;MUST&quot=
; here.=C2=A0 It&#39;s otherwise a bit hand-wavy for use of BCP 14 language=
.=C2=A0 But I&#39;ll leave this to the WG.</div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>Section 2.2.2<br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">=C2=A0=C2=A0=C2=A0In=C2=A0the
            case of certain server data, the data MUST be recorded.</p>
          <br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">This
            seems misplaced; the MUST should be in the descriptions for
            the specific cases where this requirement exists.</p>
        </div>
      </div>
    </blockquote>
    <p>I think this text is actually Ok where it is, as it
      warns/requires the client to implement proper cashing. It is more
      a statement of intent.<br>
    </p>
    <p>If you think use of RFC 2119 language here is not right, we can
      discuss that.<br></p></div></blockquote><div>Similar to the previous =
case, I suggest &quot;needs to&quot; here, and then wherever you talk about=
 certain server data, that&#39;s where the BCP 14 language should go.</div>=
<div><br></div><div>I also didn&#39;t think you meant caching when you said=
 &quot;recorded&quot;; I took that to refer to logging.=C2=A0 Possibly some=
thing else to clarify.<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div><p>
    </p>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">The
            text surrounding $Phishing goes further into human factors
            work than other working groups have felt appropriate.=C2=A0 (DK=
IM
            and DMARC come to mind.)=C2=A0 Are we sure that belongs here?</=
p>
        </div>
      </div>
    </blockquote>
    Yes, considering this is a security consideration, a good example of
    UI is necessary here.<br></div></blockquote><div><br></div><div>I&#39;m=
 curious to see if anyone else raises this given how much energy those othe=
r WGs used in the past to resist providing any UI advice at all.<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">It
            seems strange to oblige a client detecting both $Junk and
            $NotJunk being set to deal with that condition by fixing
            it.=C2=A0 The advice to ignore them is fine, however.</p>
        </div>
      </div>
    </blockquote>
    <p>This is how they were defined when they were registered. I
      appreciate that this might be strange, but changing semantics at
      this point is not going to work.</p></div></blockquote><div><br></div=
><div>Fair enough.</div><div> <br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div>
    <p>If you suggest changing the description without changing the
      semantics, we should consider this.<br></p></div></blockquote><div><b=
r></div><div>No, it&#39;s the semantics I found odd, but I realize you&#39;=
re not doing something new here.</div><div> <br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div><p>
    </p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">It=E2=80=99s
            also curious to put a normative SHOULD on registering
            keywords, as IANA activity is outside of the protocol.</p>
        </div>
      </div>
    </blockquote>
    I&#39;ve seen this done in other RFCs.</div></blockquote><div><br></div=
><div>Doesn&#39;t mean they&#39;re right.=C2=A0 :-)</div><br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div><blockquote type=3D"cite"><div dir=
=3D"ltr"><div><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt">Should
            this section mention whether the system flags are
            permanent?=C2=A0 \Seen, for example, is clearly a system flag,
            but it could also be a session flag.</p>
        </div>
      </div>
    </blockquote>
    <p>No, implementations differ and sometimes even \Seen is not
      permanent. (The last sentence of the first paragraph already says
      &quot;A flag of either type can also be permanent or session-only.&qu=
ot;)</p></div></blockquote><div>Yep, that&#39;s what caused me to make the =
comment.</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            2.3.3</p>
          <br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">All
            the SHOULDs in here make me wonder when an implementor might
            legitimately choose to do something different.=C2=A0 Or maybe
            instead of =E2=80=9CSHOULD be=E2=80=9D, just say =E2=80=9Cis=E2=
=80=9D?</p>
        </div>
      </div>
    </blockquote>
    <p>I think for delivery by SMTP, I agree. For COPY/MOVE there is
      actually a posibility that some mailstores wouldn&#39;t preserve
      original values, so this is asking them to really think hard about
      preserving it.</p>
    <p>And for APPEND, this is a similar requirement on MUAs to preserve
      this information. (Some don&#39;t and it is very awkward.)</p>
    <p>So I prefer to keep the last 2 SHOULDs.<br></p></div></blockquote><d=
iv>I guess I&#39;m wondering if those implementations chose not to for some=
 reason you think is valid, or was it purely an oversight on their part and=
 you&#39;re using SHOULD to grandfather them in?=C2=A0 Would it be fine to =
say MUST here and just say that an implementation not doing this is therefo=
re not compliant with rev2?</div><div><br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div><p>
    </p><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div> <font size=3D"2"></font><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 5.1.2.1</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Although both =E2=80=9CImplementer=E2=80=9D and =E2=80=9CImplementor=E2=
=80=9D appear to be correct, you use the latter everywhere in the document =
except here.=C2=A0 (Actually, Google docs suggests the former.)</span></fon=
t></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">I changed it to implementors and I am happy for RFC
      Editor to tell me which one they prefer ;-)</font></div></blockquote>=
<div><br></div><div>Yeah, I&#39;m fine with either.=C2=A0 I just wanted int=
ernal consistency.</div><div> <br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 5.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">=E2=80=9CSometimes, such behavior is REQUIRED.=E2=80=9D=C2=A0 This isn=E2=
=80=99t a specific normative statement, so I=E2=80=99d use the lowercase ve=
rsion here, and use BCP 14 language when you=E2=80=99re presenting specific=
 cases.</span></font></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">I agree. Changed.</font></p>
    =C2=A0[snip]<br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            6.1.2</p>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><br>
            This section says NOOP can be used to reset the autologout
            timer (which seems definite), but Section 5.1.4 says any
            command only SHOULD reset the timer.=C2=A0 Do these line up?</p=
>
        </div>
      </div>
    </blockquote>
    <p>(I assume you meant 5.4)</p>
    <p>Well spotted. I changed text in 5.4 to readL</p>
    <p>=C2=A0The receipt of any command from the client during that interva=
l
      resets the autologout timer.<br></p></div></blockquote><div>Why would=
 a command deviate from the SHOULD and not reset the timer?</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 6.2.3</span></font></p>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">
</span><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:t=
ransparent;font-weight:400;font-style:normal;font-variant:normal;text-decor=
ation:none;vertical-align:baseline;white-space:pre-wrap">I think there=E2=
=80=99s an =E2=80=9Cor=E2=80=9D missing in the last paragraph.</span></font=
></p>
        </div>
      </div>
    </blockquote>
    <p><font size=3D"2">This looks Ok to me. Can you elaborate?<br></font><=
/p></div></blockquote><div>Uh, no, I can&#39;t. Ignore this one.=C2=A0 It w=
as very late. <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div><p><font size=3D"2">
      </font></p>
    <p><font size=3D"2">=C2=A0[snip]<br>
      </font></p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr"><font size=3D"2"></font>This section should make it
        more explicit, up front, that the response names the extensions
        that were successfully enabled.=C2=A0 Right now the lede is buried =
in
        about the 7th paragraph.
        <div> </div>
      </div>
    </blockquote>
    I didn&#39;t move the paragraph that talks about ENABLED response, but =
I
    clarified it.<br></div></blockquote><div><br></div><div>It seems like a=
 pretty important aspect of the response, so I thought it was strange that =
it wasn&#39;t presented until so late in the section.=C2=A0 Your call thoug=
h. <br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div>
    <br><blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D</=
span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">This is saying that the server wouldn&#39;t return &qu=
ot;BAD&quot;
      to it.</font><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">followed
            immediately by =E2=80=9Csome servers don=E2=80=99t let you do t=
his=E2=80=9D.</p>
        </div>
      </div>
    </blockquote>
    But this is saying that the server can still return &quot;NO&quot;.<br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Which
            is the standard for this version of IMAP?=C2=A0 If it=E2=80=99s=
 an
            implementation choice, I think that=E2=80=99s what this should =
say.</p>
        </div>
      </div>
    </blockquote>
    Yes, it is.<br></div></blockquote><div><br></div><div>That&#39;s fine, =
then, if this is clarified.=C2=A0 I just found that bit to be self-contradi=
cting as written in -22.</div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div>
    <br><blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">=C2=A0=C2=A0=C2=A0Clients SHOULD use the empty reference</span></font></p=
>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">=C2=A0=C2=A0=C2=A0argument.</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Why might I not do this?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">If you want &quot;change directory&quot; kind of behav=
iour
      (where the directory is the reference name argument).</font></div></b=
lockquote><div><br></div><div>Ah, yes.=C2=A0 Then this could use a bit of c=
larification.</div><div> <br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">Section 6.3.9.2</span></font></p>
          <font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">This section (and the previous) require that \Subscribed be computed accu=
rately before the response is generated.=C2=A0 How does this square with th=
e text in Section 6.3.9 that insists replies come quickly?</span></font></p=
>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">You have to comply with both :-). It is quite
      important for \Subscribed to be accurate, so implementations need
      to do that while maintaining reasonable performance.</font></div></bl=
ockquote><div><br></div><div>OK.=C2=A0 I just wanted to make sure the reade=
r isn&#39;t getting &quot;You MUST be fast!&quot; from one direction while =
also doing &quot;You MUST do all this expensive stuff!&quot; from the other=
 with no guidance about how to resolve this. <br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div><br>
    <p><br>
    </p>
    <p><font size=3D"2">=C2=A0[snip]</font><br>
    </p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><font size=3D"2"></font><font size=3D"2"><br>
          </font>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">The second paragraph also gets into the presentation of the reply.=C2=A0 =
This is human factors stuff the IETF tends to avoid.=C2=A0 Are we sure it b=
elongs here?</span></font></p>
        </div>
      </div>
    </blockquote>
    <font size=3D"2">This is copy of the text from another RFC and I
      personally found this text to be useful when implementing.</font></di=
v></blockquote><div><br></div><div>You might consider putting these present=
ation advice paragraphs into an appendix too.</div><div><br></div><div>-MSK=
<br></div></div></div>

--000000000000ebb65705b816518a--


From nobody Mon Jan  4 09:29:48 2021
Return-Path: <superuser@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 EFA4A3A0F4D for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level: 
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 IsgJ9a_HA_U2 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 09:29:38 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (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 5D21B3A0FEE for <extra@ietf.org>; Mon,  4 Jan 2021 09:29:31 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id k9so6342435vke.4 for <extra@ietf.org>; Mon, 04 Jan 2021 09:29:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GGIsHJlOeZ8wCPoOWSclvAs41LdtKF1N3afTLnPr6R4=; b=ZPDnb8itRXFIacBL8zS47zD+4NnG2ZOXqcJ1dXxg07mBNprjJ1m28LyntzYVBV8oXy kHAZwGQoM36d0TkEglFzahlSbIIYFfsncgIMh59nVtvTujCJ9FcRTdKJJoyPtp6sYYhR KQrJv28Np98AinpofMPwgTty+u6AdpeFCcJgKB23ge2TPelu0Rw9lr3HpAXHHNq2D9do MUplSfi9SoVopf0zaIaPnIUOglJZWtc1e22+RJosWuxBDqc9yvkUZJ4qZVK4KMHrcjkL es1fx8QutB3iryHaKajdXDS7hNKZiABQw5WEvXOEwY/lFgCVrrlcWAWro/0tCVi8W9CR cOSg==
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=GGIsHJlOeZ8wCPoOWSclvAs41LdtKF1N3afTLnPr6R4=; b=SRaM5gFc9G1om5MqIMhpBda6KWLc+eC+B4DlxM+qy+plGVwLZfXE2i0LLOep6voDem hoPBtu+Kxo+Gkt2yGUB5sEZodmeLnmmGKT/OjV/kQoFSTcMGgoDDhuip8mWpLjT+ooqy jpWU/3CXP5ng1DepF0sd0IxhHXKDgGo64IqBzWtDJ7ihET7CrWk5ki2DRHuhnhMOtT3F 5KDgkZCTF6VHjeAD52sUF1eAnWfA9q5S+deuUR+GPwkS4E+cuODQp1xQ5GWX+DqATz3H VseJf/tnUCx2pDx0tXv3X96JGb2HUwQDRRyFwkRlrqA0OmvvG0e0xagrb03vfcW7Azdu bghQ==
X-Gm-Message-State: AOAM532SG1cV8MUah+XAobvCV3lTPRf91KoMqtJIUrYOu9HTwVIYP/hI GULcz/xm+zATDG/w8rHU2eWyYBDAdUp2cDPPrV8=
X-Google-Smtp-Source: ABdhPJyLO9uLpkFDAfuHAo/pCJ8/S9RiAyQZeDqKE9zNFZ1m8inAHH+gHmMhp3N3dnCwXrELFZ3ypsjyTfgEgGx+JQM=
X-Received: by 2002:ac5:cc75:: with SMTP id w21mr45177700vkm.14.1609781370165;  Mon, 04 Jan 2021 09:29:30 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <ae15071e-3ab5-2ad0-953b-05856991b287@isode.com>
In-Reply-To: <ae15071e-3ab5-2ad0-953b-05856991b287@isode.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 4 Jan 2021 09:29:19 -0800
Message-ID: <CAL0qLwZ9=iPwCBYJjgnPudFaiq8C60s2jDrKU2_=rzn7ghf1cg@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bc1eac05b8166edc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/hm2MwrzD4__xhluuaLzepGc4xkc>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 17:29:46 -0000

--000000000000bc1eac05b8166edc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 4, 2021 at 7:39 AM Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> Hi Murray,
>
> Replying to some remaining editorial comments:
> On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>
> Section 5.1
>
> There=E2=80=99s a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which=
 could probably benefit
> from a section number reference as well.  This is actually something I=E2=
=80=99d
> thought about many times earlier in the document up to this point, but I=
=E2=80=99m
> finally saying something here; some of them were clear references like
> this, while others were references to commands or flags that are =E2=80=
=9Cdescribed
> elsewhere in this document=E2=80=9D.
>
> I fixed several cases of missing references. If you find anything else I
> missed, please let me know.
>

I'll check out -23.

Section 6.4.4.4
>
> I think the inline comments in the various examples don=E2=80=99t really =
need to
> be inline.  They could just as easily be prose below each example.
>
> For some examples this might be more involved than for others. Are you
> happy for this to be addressed directly with RFC Editor via an XML commen=
t?
>

Sure.  I just found the inline comments caused the whole example to appear
a bit cluttered, and it didn't seem necessary to have them inline.  It's
more of a presentation thing.

>
> Section 7.2 and its subsections
>
> A fair bit of this text is repeated verbatim from earlier sections and
> should probably be consolidated.  I really noticed this when I hit Sectio=
n
> 7.2.3 where, for instance, \HasChildren is defined both here and in Secti=
on
> 6.3.9.5, with the paragraphs in both sections being identical.  However,
> now that I look earlier in 7.2.2, I see the same issue.
>
> I struggled with some of this, as initially not all mailbox attributes
> were listed in Section 7.2.3 (LIST Response). In other sections it is had
> to talk about some options without introducing the corresponding mailbox
> attribute(s) first. So it would really help to have some specific
> suggestions on where you think text can be dropped.
>

Basically anything that's a verbatim copy from one section to the next
should be common factored someplace.  For a first suggestion, maybe a
section early on enumerating known mailbox attributes, to which later
sections can then refer?

You could also constrain Section 6 to discuss only the syntax and semantics
of the commands themselves and their options, and leave discussion of the
responses until their Section 7 counterparts.  To cite one particular
example, Section 6.3.9.5, the first paragraph is all you need because it
describes the modification to the LIST request in general prose; it can
then refer to the piece of Section 7 that gives details about the reply.
So 6.3.9.5 is reduced to something like:

   The CHILDREN return option is simply an indication that the client
   wants information about whether or not mailboxes contain children
   mailboxes; a server MAY provide it even if the option is not
   specified.

   This will cause the reply to contain \HasChildren or \HasNoChildren

   attributes on the responses to LIST.  These are described in Section

   7.x.y where the LIST response is defined.

-MSK

--000000000000bc1eac05b8166edc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 4, 2021 at 7:39 AM Alexey Mel=
nikov &lt;<a href=3D"mailto:alexey.melnikov@isode.com">alexey.melnikov@isod=
e.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>Hi Murray,</p>
    <p>Replying to some remaining editorial comments:<br>
    </p>
    <div>On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            5.1</p>
          <br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">There=E2=80=99s
            a reference =E2=80=9Csee the Formal Syntax=E2=80=9D which could=
 probably
            benefit from a section number reference as well.=C2=A0 This is
            actually something I=E2=80=99d thought about many times earlier=
 in
            the document up to this point, but I=E2=80=99m finally saying
            something here; some of them were clear references like
            this, while others were references to commands or flags that
            are =E2=80=9Cdescribed elsewhere in this document=E2=80=9D.</p>
        </div>
      </div>
    </blockquote>
    <p> I fixed several cases of missing references. If you find
      anything else I missed, please let me know.</p></div></blockquote><di=
v><br></div><div>I&#39;ll check out -23.</div><div> <br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            6.4.4.4</p>
          <br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">I
            think the inline comments in the various examples don=E2=80=99t
            really need to be inline.=C2=A0 They could just as easily be
            prose below each example.</p>
        </div>
      </div>
    </blockquote>
    For some examples this might be more involved than for others. Are
    you happy for this to be addressed directly with RFC Editor via an
    XML comment?<br></div></blockquote><div><br></div><div>Sure.=C2=A0 I ju=
st found the inline comments caused the whole example to appear a bit clutt=
ered, and it didn&#39;t seem necessary to have them inline.=C2=A0 It&#39;s =
more of a presentation thing.<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">Section
            7.2 and its subsections</p>
          <br>
          <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt">A
            fair bit of this text is repeated verbatim from earlier
            sections and should probably be consolidated.=C2=A0 I really
            noticed this when I hit Section 7.2.3 where, for instance,
            \HasChildren is defined both here and in Section 6.3.9.5,
            with the paragraphs in both sections being identical.=C2=A0
            However, now that I look earlier in 7.2.2, I see the same
            issue.</p>
        </div>
      </div>
    </blockquote>
    <p>I struggled with some of this, as initially not all mailbox
      attributes were listed in Section 7.2.3 (LIST Response). In other
      sections it is had to talk about some options without introducing
      the corresponding mailbox attribute(s) first. So it would really
      help to have some specific suggestions on where you think text can
      be dropped.</p></div></blockquote><div><br></div><div>Basically anyth=
ing that&#39;s a verbatim copy from one section to the next should be commo=
n factored someplace.=C2=A0 For a first suggestion, maybe a section early o=
n enumerating known mailbox attributes, to which later sections can then re=
fer?</div><div><br></div><div>You could also constrain Section 6 to discuss=
 only the syntax and semantics of the commands themselves and their options=
, and leave discussion of the responses until their Section 7 counterparts.=
=C2=A0 To cite one particular example, Section 6.3.9.5, the first paragraph=
 is all you need because it describes the modification to the LIST request =
in general prose; it can then refer to the piece of Section 7 that gives de=
tails about the reply.=C2=A0 So 6.3.9.5 is reduced to something like:</div>=
<div><br></div><div><pre class=3D"gmail-newpage">   The CHILDREN return opt=
ion is simply an indication that the client
   wants information about whether or not mailboxes contain children
   mailboxes; a server MAY provide it even if the option is not
   specified.
<br></pre><pre class=3D"gmail-newpage">   This will cause the reply to cont=
ain \HasChildren or \HasNoChildren<br></pre><pre class=3D"gmail-newpage">  =
 attributes on the responses to LIST.  These are described in Section<br></=
pre><pre class=3D"gmail-newpage">   7.x.y where the LIST response is define=
d.<br><br></pre><pre class=3D"gmail-newpage"><span style=3D"font-family:ari=
al,sans-serif">-MSK<br></span></pre></div></div></div>

--000000000000bc1eac05b8166edc--


From nobody Mon Jan  4 10:11:15 2021
Return-Path: <barryleiba.mailing.lists@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 0125F3A0EE1 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.498
X-Spam-Level: 
X-Spam-Status: No, score=0.498 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, 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 duzOJ9ygAeCW for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:11:12 -0800 (PST)
Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) (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 EE6B23A0EDF for <extra@ietf.org>; Mon,  4 Jan 2021 10:11:11 -0800 (PST)
Received: by mail-oi1-f169.google.com with SMTP id l207so33087382oib.4 for <extra@ietf.org>; Mon, 04 Jan 2021 10:11:11 -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=8WaeXQiPCpoA1Baq5ZGKC3N/6MXiaxIl8B+jbv647ns=; b=HZpuk7LklHBEapMqO3vJyZNeq9E6zpn41FSxh5sAByJa3ZaysPek4sn0rlbfMDuAlU 32Bxq4q4Cs2I2hTodvd4u2bmMnU2KeGUgez/AbH43gI/cALP0XlKB8lADbonhZCR9Xom iTNs+ghCfWYH74aChvLI+hrdAGAoLpAYzp55xyHKJdiZIUyKk2tFuqnCJgazTJZNxlFa ZBsgHUs4vrYKADLhH9cuLsl2faPjKPHrfl7BmtVQZzmLGcc1HvylwdPLN0DI1aJHb1Xc NJfTDcPmgjKQuxqqbqZ8LaC6VE2qkpxq7/57GDMbqzVbCc5DR9UGiqr1lq5RxNaFJvok Lrkg==
X-Gm-Message-State: AOAM531qa7pED0G+LAbF5yGfs56E7od7MhMHe16xCQ0y7guX2IkO0vPY 9wjg/yZwqo3GppvhwlhxqPFyVvw5SVQe0xxlvtk=
X-Google-Smtp-Source: ABdhPJzov++ypDSnGoGqiDiuqTSMNCjvzvGXvhTE3osfVXwE4/NFrp8FuL2lo6iHzdhqaRqEMPmtFfrtfw6pvyGxhH0=
X-Received: by 2002:aca:3145:: with SMTP id x66mr94531oix.29.1609783871121; Mon, 04 Jan 2021 10:11:11 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
In-Reply-To: <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 4 Jan 2021 13:11:00 -0500
Message-ID: <CAC4RtVDfkid_-r=ug7gUDhXYZuS3giwiMgWXTzc8w97-gLho_A@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, extra@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/yW4meaqTkdyZwP8BK3N25qTN1FY>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 18:11:13 -0000

>>> Section 2.2.1
>>>
>>>   Clients MUST follow the syntax outlined in this specification
>>>    strictly.  It is a syntax error to send a command with missing or
>>>    extraneous spaces or arguments.
>>>
>>> It seems unnecessary to say this in a standards track document.  There=
=E2=80=99s a similar paragraph in Section 2.2.2.
>>
>> I think the text is there due to various bugs in implementations, so I w=
ould rather keep it as is.
>
> I would use "need to" instead of "MUST" here.  It's otherwise a bit hand-=
wavy for use of BCP 14 language.

Over the years, we have seen a LOT of implementations that mess this
up, thinking that because IMAP command streams are "readable", they
can add spaces to "improve readability", and then they complain that
things break.  Because of that, I think it's important to have this
text, and I think it's important to use BCP 14 language (it's a *real*
interoperability issue).  I feel pretty strongly about this, as
someone who's many times had to help people fix their implementations
because they weren't warned explicitly about it.

Barry


From nobody Mon Jan  4 10:26:39 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 6A0013A0EF6 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 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, 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 nn7r5Ozlo6Ib for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:26:37 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id BDC6B3A0FCA for <extra@ietf.org>; Mon,  4 Jan 2021 10:26:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609784794; d=isode.com; s=june2016; i=@isode.com; bh=BFEa+md6o2XSPQwCbuN9mRQhyoSXFjz51GECgIslxeE=; 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=TeN+s3y9o3rs3DQLn1z8OBiuFshSLNSbo8ruLemHws2Nnfnb/0/v+crU2qchDEmjvy6j2T TrtK8yuL5nuaNlRDGUMVC6CJz9xSSwnRNvlXdXCNYrYifumAdNI6OKdMbi2Ne9q0hH7Rnc RxFjsPIRFD5aCOR788PLgx9Rva/F0CI=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=Nd2gBqmiE4@statler.isode.com>; Mon, 4 Jan 2021 18:26:34 +0000
To: "Murray S. Kucherawy" <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: extra@ietf.org
Message-ID: <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com>
Date: Mon, 4 Jan 2021 18:26:33 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------99A16D5A82CD2AE521AAE51C"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/zqeqfWBcyhwrc9-V4spRvHp35g4>
Subject: [Extra] BCP 178/X- convention (was AD Review of draft-ietf-extra-imap4rev2)
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, 04 Jan 2021 18:26:38 -0000

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

Hi Murray/Barry,

I've extracted all of your comments related to BCP 178 ("X- convention=20
considered harmful):

On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>
> Section 6.1.1
>
>
> Is the stuff about XBLURDYBLOOP still appropriate given BCP 178?
>
I deleted this text, as it really belongs to future revision of RFC 4422=20
(SASL), if at all.

> Section 6.3.1
>
> There=E2=80=99s another =E2=80=9CX=E2=80=9D reference here (BCP 178).
>
>
This is section defines the ENABLE command. The example is using=20
X-GOOD-IDEA as an example of a fictitious capability that can be=20
enabled. Use of X-GOOD-IDEA in the example is not critical, but it makes=20
it more explicit that this is not registered. I can change the example.

> =C2=A0=C2=A0In this example, a server supports 2 Personal Namespaces.=C2=
=A0 =E2=80=A6
>
>
> There=E2=80=99s a reference to X-PARAM in here that probably needs updatin=
g in=20
> light of BCP 178.
>
Here, I think we need to use an unregistered parameter. It doesn't have=20
to be X-PARAM, but X-PARAM seems a bit more obvious due to old usage,=20
even if it is considered wrong these days.


> Section 6.5
>
> Is this appropriate in light of BCP 178?
>
So this section is titled "Client Commands - Experimental/Expansion" and=20
talks in general terms about implementation specific commands (that were=20
required to start with "X" in RFC 3501) and some generic requirements on=20
clients/servers in regards to extensions. I can extract useful text=20
about the latter and drop the former.
>
> Section 7.2.2
>
>
> The stuff about capability names starting with =E2=80=9CX=E2=80=9D should =
be reviewed=20
> in light of BCP 178.
>
This section is titled "CAPABILITY Response". Below is the offending text:

 =C2=A0=C2=A0 Capability names MUST either begin with "X" or be informationa=
l,
 =C2=A0=C2=A0 experimental or standards-track IMAP4rev2 extensions, revision=
s, or
 =C2=A0=C2=A0 amendments registered with IANA.

Dropping "X" from the above list would be fine with me. But this raises=20
a related question: should this document allow Experimental RFCs outside=20
of IETF stream in order to encourage people to document their private=20
extensions?

 =C2=A0=C2=A0 A server SHOULD NOT offer
 =C2=A0=C2=A0 unregistered or non-standard capability names, unless such nam=
es are
 =C2=A0=C2=A0 prefixed with an "X".

This probably should be dropped.

Best Regards,

Alexey



--------------99A16D5A82CD2AE521AAE51C
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 Murray/Barry,</p>
    <p>I've extracted all of your comments related to BCP 178 ("X-
      convention considered harmful):<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 08:18, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            6.1.1</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Is
            the stuff about XBLURDYBLOOP still appropriate given BCP
            178?</p>
        </div>
      </div>
    </blockquote>
    I deleted this text, as it really belongs to future revision of RFC
    4422 (SASL), if at all.<br>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>Section 6.3.1</div>
      </div>
    </blockquote>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Ther=
e=E2=80=99s
            another =E2=80=9CX=E2=80=9D reference here (BCP 178).</p>
          <br>
        </div>
      </div>
    </blockquote>
    <p>This is section defines the ENABLE command. The example is using
      X-GOOD-IDEA as an example of a fictitious capability that can be
      enabled. Use of X-GOOD-IDEA in the example is not critical, but it
      makes it more explicit that this is not registered. I can change
      the example.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=C2=
=A0=C2=A0In
            this example, a server supports 2 Personal Namespaces.=C2=A0 =E2=
=80=A6</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Ther=
e=E2=80=99s
            a reference to X-PARAM in here that probably needs updating
            in light of BCP 178.</p>
        </div>
      </div>
    </blockquote>
    Here, I think we need to use an unregistered parameter. It doesn't
    have to be X-PARAM, but X-PARAM seems a bit more obvious due to old
    usage, even if it is considered wrong these days.<br>
    <p><br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div>Section 6.5<br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Is
            this appropriate in light of BCP 178?</p>
        </div>
      </div>
    </blockquote>
    So this section is titled "Client Commands - Experimental/Expansion"
    and talks in general terms about implementation specific commands
    (that were required to start with "X" in RFC 3501) and some generic
    requirements on clients/servers in regards to extensions. I can
    extract useful text about the latter and drop the former.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.c=
om">
      <div dir=3D"ltr">
        <div><br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">Sect=
ion
            7.2.2</p>
          <br>
          <p dir=3D"ltr"
            style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">The
            stuff about capability names starting with =E2=80=9CX=E2=80=9D s=
hould be
            reviewed in light of BCP 178.</p>
        </div>
      </div>
    </blockquote>
    <p>This section is titled "CAPABILITY Response". Below is the
      offending text:<br>
      <br>
      =C2=A0=C2=A0 Capability names MUST either begin with "X" or be
      informational,<br>
      =C2=A0=C2=A0 experimental or standards-track IMAP4rev2 extensions,
      revisions, or<br>
      =C2=A0=C2=A0 amendments registered with IANA.</p>
    <p>Dropping "X" from the above list would be fine with me. But this
      raises a related question: should this document allow Experimental
      RFCs outside of IETF stream in order to encourage people to
      document their private extensions?<br>
    </p>
    <p>=C2=A0=C2=A0 A server SHOULD NOT offer<br>
      =C2=A0=C2=A0 unregistered or non-standard capability names, unless suc=
h
      names are<br>
      =C2=A0=C2=A0 prefixed with an "X".<br>
    </p>
    <p>This probably should be dropped.</p>
    <p>Best Regards,</p>
    <p>Alexey</p>
    <p><br>
    </p>
  </body>
</html>

--------------99A16D5A82CD2AE521AAE51C--


From nobody Mon Jan  4 10:48:25 2021
Return-Path: <superuser@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 D1ED43A0F3A for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:48:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level: 
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 rbRMkV4OMTzJ for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:48:21 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 41D563A0E98 for <extra@ietf.org>; Mon,  4 Jan 2021 10:48:21 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id s2so15082829vsk.2 for <extra@ietf.org>; Mon, 04 Jan 2021 10:48:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l3F06PRJWs6fBgZpDj/Z1VyZ/7SxuL/5EFN6mrEKBSU=; b=rMMEzrd7rVRGR9aeHVn1aTaLZ6KI7ecyb+NWzsFOnFjKlBFPPTOHwvNbif2kI79dVE D0qkUPhPhc2eLcdwGCjmYaTzn6SvrNj+mSZZY3BMdc1eFues2R46C9MylkBTFWrL+lnr dJxTGyjFvKkdZlF/evqsb/JS807jegttjTO7mXotdN8f2r+ULvsp0ICDJWxQKTP3SJEW uoPNKC+K/zcuhEjQKu+DuCDJajLHod8KGs3eQBErdaQ9F0QErmfqVT7Q3r+euhH6WZSe 2zDvYh53TzJvURUkql9j8HFrKuo+JHORm9mFpUGk3UxtxVmhgNirw2XlEDE0y38sebkY gAwA==
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=l3F06PRJWs6fBgZpDj/Z1VyZ/7SxuL/5EFN6mrEKBSU=; b=Z/gbg67wWEyBnVGghKH1ZiCNUycyDIb2LSZ6YQJrgstiv1h1qw6ORQWAufEL06i9gh I8G20xC3OB4LNnGEwi5z47tkNawyZHAWctXta5T+QXRguJXFGaxFkzqPWZ/FcVROyi0j kCNjOKRt/kK5VJx0vvv/fWK3oqyXmi63AhjzQNzAsFiOfMpsNGTSDCA/z/PoY7S7+UX2 +KhZeRVAGxz/nhleE2e0fY1YOKuGcHUs+7KuK+RGGa1IJHYlfAxExkdT4cWhQ6hzpxFg q1xBkehabkGp+pJTDxJEFYHgi67HcL0549UyTvzDJ9DQgJgaJ1KsOX0+2PsMqeilywjr XMgQ==
X-Gm-Message-State: AOAM532Kgwp1EshhFkrUwOfRo02756U5O2bQ0uVGK0j+WjgvyWoomthy SnqnKJ63oWmEAcBH6KStLJro3nVXgQG1vErW364=
X-Google-Smtp-Source: ABdhPJx3E2xSIUUnBFJwcXD/8jBesGti6dqt8Ub6twomzn9//WPWdN7HYjxMiwKFYZkg98WG77mp/P9Y8hGKTP7ePIU=
X-Received: by 2002:a67:2bc2:: with SMTP id r185mr44294252vsr.15.1609786100105;  Mon, 04 Jan 2021 10:48:20 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com> <CAC4RtVDfkid_-r=ug7gUDhXYZuS3giwiMgWXTzc8w97-gLho_A@mail.gmail.com>
In-Reply-To: <CAC4RtVDfkid_-r=ug7gUDhXYZuS3giwiMgWXTzc8w97-gLho_A@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 4 Jan 2021 10:48:09 -0800
Message-ID: <CAL0qLwaJfMVUrN6rzsf2stLCM2HcTeHRg_qA-Hbf-8xZaf4DmA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, extra@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a9471905b817887a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/YlxkMROz1Xn_K0P8YY6JS6xYkkI>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 04 Jan 2021 18:48:23 -0000

--000000000000a9471905b817887a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 4, 2021 at 10:11 AM Barry Leiba <barryleiba@computer.org> wrote=
:

> >>> Section 2.2.1
> >>>
> >>>   Clients MUST follow the syntax outlined in this specification
> >>>    strictly.  It is a syntax error to send a command with missing or
> >>>    extraneous spaces or arguments.
> >>>
> >>> It seems unnecessary to say this in a standards track document.
> There=E2=80=99s a similar paragraph in Section 2.2.2.
> >>
> >> I think the text is there due to various bugs in implementations, so I
> would rather keep it as is.
> >
> > I would use "need to" instead of "MUST" here.  It's otherwise a bit
> hand-wavy for use of BCP 14 language.
>
> Over the years, we have seen a LOT of implementations that mess this
> up, thinking that because IMAP command streams are "readable", they
> can add spaces to "improve readability", and then they complain that
> things break.  Because of that, I think it's important to have this
> text, and I think it's important to use BCP 14 language (it's a *real*
> interoperability issue).  I feel pretty strongly about this, as
> someone who's many times had to help people fix their implementations
> because they weren't warned explicitly about it.
>

OK, I'm done pushing on this one.  Just wanted to make sure.  :-)

-MSK

--000000000000a9471905b817887a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 4, 2021 at 10:11 AM Barry Lei=
ba &lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</=
a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">&gt;&gt;&gt; Section 2.2.1<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0Clients MUST follow the syntax outlined in this sp=
ecification<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 strictly.=C2=A0 It is a syntax error to send a co=
mmand with missing or<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 extraneous spaces or arguments.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems unnecessary to say this in a standards track document=
.=C2=A0 There=E2=80=99s a similar paragraph in Section 2.2.2.<br>
&gt;&gt;<br>
&gt;&gt; I think the text is there due to various bugs in implementations, =
so I would rather keep it as is.<br>
&gt;<br>
&gt; I would use &quot;need to&quot; instead of &quot;MUST&quot; here.=C2=
=A0 It&#39;s otherwise a bit hand-wavy for use of BCP 14 language.<br>
<br>
Over the years, we have seen a LOT of implementations that mess this<br>
up, thinking that because IMAP command streams are &quot;readable&quot;, th=
ey<br>
can add spaces to &quot;improve readability&quot;, and then they complain t=
hat<br>
things break.=C2=A0 Because of that, I think it&#39;s important to have thi=
s<br>
text, and I think it&#39;s important to use BCP 14 language (it&#39;s a *re=
al*<br>
interoperability issue).=C2=A0 I feel pretty strongly about this, as<br>
someone who&#39;s many times had to help people fix their implementations<b=
r>
because they weren&#39;t warned explicitly about it.<br></blockquote><div><=
br></div><div>OK, I&#39;m done pushing on this one.=C2=A0 Just wanted to ma=
ke sure.=C2=A0 :-)</div><div><br></div><div>-MSK<br></div></div></div>

--000000000000a9471905b817887a--


From nobody Mon Jan  4 10:55:05 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 884993A0FC4 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.498
X-Spam-Level: 
X-Spam-Status: No, score=0.498 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 B-r96thp90DQ for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 10:55:02 -0800 (PST)
Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (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 0C49E3A0FC3 for <extra@ietf.org>; Mon,  4 Jan 2021 10:55:02 -0800 (PST)
Received: by mail-lf1-f48.google.com with SMTP id o13so66864860lfr.3 for <extra@ietf.org>; Mon, 04 Jan 2021 10:55:01 -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=dQjnuUr0AU9pjgPhuS6xeKPw/ovoTJPOZbuvueMmKSU=; b=KRK+EmY6ybGcjb0ndLIRF7i5HGe86tmK41lbUxQLQ66wM1can8qHzxm5btIWYIOqbz VhR9xIQQeVbVuEq86P4wSkbYM2vZ03ceZMxnHWSQy10hWMNiReOYBLqAWwk7IF7SA2AJ +13EDEoqRP8942OEyk0rJVcStYn/6GcJDA49IRzOO8hW2lNX6yGc+kfigQkYJLrTD46g G/L7si0RZDEnJtnRC5IJ1MyBcOdqWz3NB+WvjaPtX/IROnsKmricJqgs3lhiSkB+R/+t kGEI+YlMURDY8oJUGCd+7wzCT6+3SGN2Er3CFsDDEkYSIFvdzz4+JvUWiwMXBgAfIFZc LFdw==
X-Gm-Message-State: AOAM530UaAYX0HNfhLRUcvlkuxO7wzfs1C2eQ7ztlVN03n2vqidM93Cg 07ekzawobbWaFIOnxg2JKki9jL3S4VZConpWoxQ=
X-Google-Smtp-Source: ABdhPJwpY+GWRG1PoBuZWABY6PzZnBgouydn+k2EMc9+EH6XDOluxcID1bYAGB9vZQjyus604g1GdXAF/vJiow7dHVk=
X-Received: by 2002:a05:651c:316:: with SMTP id a22mr34344367ljp.473.1609786499891;  Mon, 04 Jan 2021 10:54:59 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com>
In-Reply-To: <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 4 Jan 2021 13:54:48 -0500
Message-ID: <CALaySJ+pZNBfc9D3Auh+Z2XF6T7p5JzBfNtUTH45YBCNQrE5rg@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, extra@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/b1hrTwK7u6rSYPtxnxTlm9BeTho>
Subject: Re: [Extra] BCP 178/X- convention (was AD Review of draft-ietf-extra-imap4rev2)
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, 04 Jan 2021 18:55:04 -0000

For what it's worth, I don't think that BCP 178 means to say that you
should never use things that start with "X".  It says that you should
not specifically use "X"-prefixed stuff to make a distinction between
registered and unregistered things when you lay out registries.

Therefore, I think it's fine to use examples that start with "X".
They're only examples.

For the other cases, such as these:

   Capability names MUST either begin with "X" or be informational,
   experimental or standards-track IMAP4rev2 extensions, revisions, or
   amendments registered with IANA.

   A server SHOULD NOT offer
   unregistered or non-standard capability names, unless such names are
   prefixed with an "X".

...well, they clearly fall under BCP 178 and we should fix those.

Barry

On Mon, Jan 4, 2021 at 1:26 PM Alexey Melnikov
<alexey.melnikov@isode.com> wrote:
>
> Hi Murray/Barry,
>
> I've extracted all of your comments related to BCP 178 ("X- convention co=
nsidered harmful):
>
> On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>
> Section 6.1.1
>
>
> Is the stuff about XBLURDYBLOOP still appropriate given BCP 178?
>
> I deleted this text, as it really belongs to future revision of RFC 4422 =
(SASL), if at all.
>
> Section 6.3.1
>
>
> There=E2=80=99s another =E2=80=9CX=E2=80=9D reference here (BCP 178).
>
>
> This is section defines the ENABLE command. The example is using X-GOOD-I=
DEA as an example of a fictitious capability that can be enabled. Use of X-=
GOOD-IDEA in the example is not critical, but it makes it more explicit tha=
t this is not registered. I can change the example.
>
>   In this example, a server supports 2 Personal Namespaces.  =E2=80=A6
>
>
> There=E2=80=99s a reference to X-PARAM in here that probably needs updati=
ng in light of BCP 178.
>
> Here, I think we need to use an unregistered parameter. It doesn't have t=
o be X-PARAM, but X-PARAM seems a bit more obvious due to old usage, even i=
f it is considered wrong these days.
>
>
> Section 6.5
>
> Is this appropriate in light of BCP 178?
>
> So this section is titled "Client Commands - Experimental/Expansion" and =
talks in general terms about implementation specific commands (that were re=
quired to start with "X" in RFC 3501) and some generic requirements on clie=
nts/servers in regards to extensions. I can extract useful text about the l=
atter and drop the former.
>
>
> Section 7.2.2
>
>
> The stuff about capability names starting with =E2=80=9CX=E2=80=9D should=
 be reviewed in light of BCP 178.
>
> This section is titled "CAPABILITY Response". Below is the offending text=
:
>
>    Capability names MUST either begin with "X" or be informational,
>    experimental or standards-track IMAP4rev2 extensions, revisions, or
>    amendments registered with IANA.
>
> Dropping "X" from the above list would be fine with me. But this raises a=
 related question: should this document allow Experimental RFCs outside of =
IETF stream in order to encourage people to document their private extensio=
ns?
>
>    A server SHOULD NOT offer
>    unregistered or non-standard capability names, unless such names are
>    prefixed with an "X".
>
> This probably should be dropped.
>
> Best Regards,
>
> Alexey
>
>


From nobody Mon Jan  4 12:59:01 2021
Return-Path: <michael@linuxmagic.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 966743A10C1 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 12:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.261
X-Spam-Level: 
X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[NICE_REPLY_A=-0.262, SPF_HELO_NONE=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 iIWWbJ9noMv3 for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 12:58:59 -0800 (PST)
Received: from mail-ob3.cityemail.com (mail-ob3.cityemail.com [104.128.152.20]) by ietfa.amsl.com (Postfix) with ESMTP id 072C13A10BE for <extra@ietf.org>; Mon,  4 Jan 2021 12:58:58 -0800 (PST)
Received: (qmail 11537 invoked from network); 4 Jan 2021 20:58:58 -0000
Received: from riddle.wizard.ca (HELO [192.168.1.55]) (michael@wizard.ca@104.128.144.8) by fe3.cityemail.com with (DHE-RSA-AES128-SHA encrypted) SMTP (aa11e4fe-4ecf-11eb-bcf9-936cbf18b1ac); Mon, 04 Jan 2021 12:58:58 -0800
To: extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com> <CALaySJ+pZNBfc9D3Auh+Z2XF6T7p5JzBfNtUTH45YBCNQrE5rg@mail.gmail.com>
From: Michael Peddemors <michael@linuxmagic.com>
Organization: LinuxMagic Inc.
Message-ID: <d8fd9618-7f29-417b-0255-3c677c3f69f8@linuxmagic.com>
Date: Mon, 4 Jan 2021 12:58:58 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+pZNBfc9D3Auh+Z2XF6T7p5JzBfNtUTH45YBCNQrE5rg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-MagicMail-OS: Linux 3.11 and newer
X-MagicMail-UUID: aa11e4fe-4ecf-11eb-bcf9-936cbf18b1ac
X-MagicMail-Authenticated: michael@wizard.ca
X-MagicMail-SourceIP: 104.128.144.8
X-MagicMail-RegexMatch: 0
X-MagicMail-EnvelopeFrom: <michael@linuxmagic.com>
X-Archive: Yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/k-CVLTqLXRJBCBz7gCkXbGIwJqw>
Subject: Re: [Extra] BCP 178/X- convention (was AD Review of draft-ietf-extra-imap4rev2)
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, 04 Jan 2021 20:59:01 -0000

Lets' talk some real world examples, and what the consensus is..

X-Archive
X-Attachment-Id
X-Auth-ID
X-Authority-Analysis
X-Auto-Response-Suppress
X-BeenThere
X-CampTrackID
X-Classification-ID
X-CL-ID
X-CMAE-Envelope
X-Contact-Form-Submission
X-CTCH
X-FE-Policy-ID-smtp.fortinet.com
X-Footer
X-Forwarded-Message-Id
X-Gmail-Original-Message-ID
X-Gm-Message-State
X-Gm-Phishy
X-Gm-Spam
X-GOOD-IDEA as an example of a fictitious capability that can be=20
X-Google-DKIM-Signature
X-Google-Original-From
X-Google-Passthru
X-Google-Smtp-Source
X-Headerized
X-LinkedIn-Class
X-LinkedIn-fbl
X-LinkedIn-Id
X-LinkedIn-Template
X-MagicMail-Quarantine
X-MagicMail-SourceIP
X-Mailbox-Line
X-Mailer
X-Mailman-Approved-At
X-Mailman-Version
X-MDID
X-MessageID-Signature
X-Microsoft-Antispam-Mailbox-Delivery
X-Microsoft-Antispam-Message-Info
X-MS-Exchange-CrossTenant-AuthAs
X-MS-Exchange-CrossTenant-AuthSource
X-MS-Exchange-CrossTenant-fromentityheader
X-MS-Exchange-CrossTenant-id
X-MS-Exchange-CrossTenant-mailboxtype
X-MS-Exchange-CrossTenant-Network-Message-Id
X-MS-Exchange-CrossTenant-originalarrivaltime
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg
X-MS-Exchange-CrossTenant-userprincipalname
X-MS-Exchange-Organization-AuthSource
X-MS-Exchange-Organization-Network-Message-Id
X-MS-Exchange-Organization-RecordReviewCfmType
X-MS-Exchange-Transport-CrossTenantHeadersStamped
X-MS-Has-Attach
X-MS-TNEF-Correlator
X-No-Archive
X-OriginalArrivalTime
X-Original-To
X-Originating-IP
X-OriginatorOrg
X-PPP-Message-ID
X-PPP-Vhost
X-Priority
X-RADICALE-NAME
X-Received
X-SES-Outgoing
X-Spam-Flag
X-Spam-Level
X-Spam-Score
X-Spam-Status
X-Telus-Authed
X-Time-IN
X-Virus-Scanned

Many of these are now semi-permanent, and it is doubtful they will be 
deprecated any time soon in many cases..

What are we suggesting here? And in some cases the headers are placed by 
a receiving MTA, and only meant for local decision making, and aren't 
expected to be seen in MTA->MTA traffic..



On 2021-01-04 10:54 a.m., Barry Leiba wrote:
> For what it's worth, I don't think that BCP 178 means to say that you
> should never use things that start with "X".  It says that you should
> not specifically use "X"-prefixed stuff to make a distinction between
> registered and unregistered things when you lay out registries.
> 
> Therefore, I think it's fine to use examples that start with "X".
> They're only examples.
> 
> For the other cases, such as these:
> 
>     Capability names MUST either begin with "X" or be informational,
>     experimental or standards-track IMAP4rev2 extensions, revisions, or
>     amendments registered with IANA.
> 
>     A server SHOULD NOT offer
>     unregistered or non-standard capability names, unless such names are
>     prefixed with an "X".
> 
> ...well, they clearly fall under BCP 178 and we should fix those.
> 
> Barry
> 
> On Mon, Jan 4, 2021 at 1:26 PM Alexey Melnikov
> <alexey.melnikov@isode.com> wrote:
>>
>> Hi Murray/Barry,
>>
>> I've extracted all of your comments related to BCP 178 ("X- convention considered harmful):
>>
>> On 04/01/2021 08:18, Murray S. Kucherawy wrote:
>>
>> Section 6.1.1
>>
>>
>> Is the stuff about XBLURDYBLOOP still appropriate given BCP 178?
>>
>> I deleted this text, as it really belongs to future revision of RFC 4422 (SASL), if at all.
>>
>> Section 6.3.1
>>
>>
>> There’s another “X” reference here (BCP 178).
>>
>>
>> This is section defines the ENABLE command. The example is using X-GOOD-IDEA as an example of a fictitious capability that can be enabled. Use of X-GOOD-IDEA in the example is not critical, but it makes it more explicit that this is not registered. I can change the example.
>>
>>    In this example, a server supports 2 Personal Namespaces.  …
>>
>>
>> There’s a reference to X-PARAM in here that probably needs updating in light of BCP 178.
>>
>> Here, I think we need to use an unregistered parameter. It doesn't have to be X-PARAM, but X-PARAM seems a bit more obvious due to old usage, even if it is considered wrong these days.
>>
>>
>> Section 6.5
>>
>> Is this appropriate in light of BCP 178?
>>
>> So this section is titled "Client Commands - Experimental/Expansion" and talks in general terms about implementation specific commands (that were required to start with "X" in RFC 3501) and some generic requirements on clients/servers in regards to extensions. I can extract useful text about the latter and drop the former.
>>
>>
>> Section 7.2.2
>>
>>
>> The stuff about capability names starting with “X” should be reviewed in light of BCP 178.
>>
>> This section is titled "CAPABILITY Response". Below is the offending text:
>>
>>     Capability names MUST either begin with "X" or be informational,
>>     experimental or standards-track IMAP4rev2 extensions, revisions, or
>>     amendments registered with IANA.
>>
>> Dropping "X" from the above list would be fine with me. But this raises a related question: should this document allow Experimental RFCs outside of IETF stream in order to encourage people to document their private extensions?
>>
>>     A server SHOULD NOT offer
>>     unregistered or non-standard capability names, unless such names are
>>     prefixed with an "X".
>>
>> This probably should be dropped.
>>
>> Best Regards,
>>
>> Alexey
>>
>>
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 



-- 
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.


From nobody Mon Jan  4 16:39:23 2021
Return-Path: <superuser@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 43E963A0C0E for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 16:39:21 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 hh0w6w8C-ZgQ for <extra@ietfa.amsl.com>; Mon,  4 Jan 2021 16:39:20 -0800 (PST)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (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 E55FC3A0C0D for <extra@ietf.org>; Mon,  4 Jan 2021 16:39:19 -0800 (PST)
Received: by mail-ua1-x929.google.com with SMTP id 17so9722335uaq.4 for <extra@ietf.org>; Mon, 04 Jan 2021 16:39:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=a78jupA4ihRjw1udaMQgEJl8yymPkHZkcGZ3mfPEIyk=; b=Oa+zVrYTpUlLko5hVPT2/GHJbD5fjZCgCSzfkjM2YD3alXz5mMH1mpae1PDNxppTII StGotM7sdGIzye9jGwoLbqUGWLW+J+WYE6KZVw1vp95uXVoCXM2cDhp/hPP5dMs1k3R4 17nQwhhmoKBB05F0gO+F+33fha5dQbTf9qpA87YTAk5TaoVhbA2mf1AOWCy58YWeXp4/ tShPeMvTgis+6lzeY/teZvCxVLyhycE/Qt0RxjN17S3VvoLIJKcFGVHMtY03QKJuWtRV bgY93C8gAfOPW/pAG5Fbhz/5mwor5lUAycCgxIGxtpEmFvekLCcZ/BfpW/MuEe11+ZYe s/+g==
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=a78jupA4ihRjw1udaMQgEJl8yymPkHZkcGZ3mfPEIyk=; b=taIrYPZnaJ7OQQNA0bTEUKSUmDHhvSQAhhAl40fjTraAsngkK+8wQAyAa+fjQIDL24 ljSyW0VH3kgw4emCOYcmq0cIorSJ77272KWLU2e1pLkkxVkVUjJ37yRoo0jOESTEWD9X Cj7U0BwphJw1J8UER+dAmxrjLwwN+9+JRy9Ar0NF8LP9u/dFMOeKij5wauspmyHDE10D EJGMpFseMiqlZbjQ/5SNxfhXhXdGwgps4KCOjJ6VFzjY+hR9a3KffQcrUQW208Rg3+Zz 2sftEOTLU8XgJxiqI0pJtXu1BWhEEnPFFyhm2Ubp54TQ6uT8a0f0zm6KBVL2CFVZV92n 0pLA==
X-Gm-Message-State: AOAM530G9iaJw2BNZmaRqnVkFtMOkpG7I1FrHfM3QphGTofiAdvKK9BH NwteKRtHnhyyk3toghcU0CpF7IO88coULM56h0U=
X-Google-Smtp-Source: ABdhPJyGaj9AFDsAO7h1rqPSlCYjxCUJquDzg6UcEkpOUNqLDvllgRlyc+wRd9szeDxd5Os/bn0ReIaUhN0HAF9EkSM=
X-Received: by 2002:ab0:614d:: with SMTP id w13mr23755343uan.67.1609807158706;  Mon, 04 Jan 2021 16:39:18 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com> <CALaySJ+pZNBfc9D3Auh+Z2XF6T7p5JzBfNtUTH45YBCNQrE5rg@mail.gmail.com> <d8fd9618-7f29-417b-0255-3c677c3f69f8@linuxmagic.com>
In-Reply-To: <d8fd9618-7f29-417b-0255-3c677c3f69f8@linuxmagic.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 4 Jan 2021 16:39:07 -0800
Message-ID: <CAL0qLwaroU-vQLu5F5O3z61jiOAtsCEQp-pohDM4L=5duRCvEw@mail.gmail.com>
To: Michael Peddemors <michael@linuxmagic.com>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="000000000000da07a005b81c6f38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/3X71t-IfcNuoO0udjFso5_xu0II>
Subject: Re: [Extra] BCP 178/X- convention (was AD Review of draft-ietf-extra-imap4rev2)
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, 05 Jan 2021 00:39:21 -0000

--000000000000da07a005b81c6f38
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 4, 2021 at 12:59 PM Michael Peddemors <michael@linuxmagic.com>
wrote:

> Lets' talk some real world examples, and what the consensus is..
>
> X-Archive
> X-Attachment-Id
> X-Auth-ID
> X-Authority-Analysis
> X-Auto-Response-Suppress
> [...]
>

BCP 178 discourages standards track documents from establishing practices
where an "X-" prefix means "experimental", because in reality once that
name is out there, it never changes.  Indeed, as you point out, they're
unlikely to change anytime soon, so this document shouldn't make the
problem worse.

The point I'm making in this comment is that this document shouldn't do
that with capability names.  Barry's correct that the ones starting with
"X" in examples are just examples and don't violate the BCP; I agree, but
there's enough similarity to that deprecated practice that I suggest
(though less urgently) avoiding it in those cases as well.

-MSK

--000000000000da07a005b81c6f38
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 4, 2021 at 12:59 PM Michael P=
eddemors &lt;<a href=3D"mailto:michael@linuxmagic.com">michael@linuxmagic.c=
om</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">Lets&#39; talk some real world examples, and w=
hat the consensus is..<br>
<br>
X-Archive<br>
X-Attachment-Id<br>
X-Auth-ID<br>
X-Authority-Analysis<br>
X-Auto-Response-Suppress <br>[...]<br></blockquote><div>=C2=A0</div><div>BC=
P 178 discourages standards track documents from establishing practices whe=
re an &quot;X-&quot; prefix means &quot;experimental&quot;, because in real=
ity once that name is out there, it never changes.=C2=A0 Indeed, as you poi=
nt out, they&#39;re unlikely to change anytime soon, so this document shoul=
dn&#39;t make the problem worse.</div><div><br></div><div>The point I&#39;m=
 making in this comment is that this document shouldn&#39;t do that with ca=
pability names.=C2=A0 Barry&#39;s correct that the ones starting with &quot=
;X&quot; in examples are just examples and don&#39;t violate the BCP; I agr=
ee, but there&#39;s enough similarity to that deprecated practice that I su=
ggest (though less urgently) avoiding it in those cases as well.<br></div><=
div><br></div><div>-MSK<br></div></div></div>

--000000000000da07a005b81c6f38--


From nobody Tue Jan  5 01:51:37 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 5336F3A0907 for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 01:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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.262, 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 npFaf0zzIyFo for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 01:51:34 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id E8B2C3A08FA for <extra@ietf.org>; Tue,  5 Jan 2021 01:51:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609840293; d=isode.com; s=june2016; i=@isode.com; bh=BvMPyrdm7WuFri6rMTRT64haMzgsBrbF4PoBZGcn0vE=; 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=JIjomLnEo+n93cF9kD+yXtjef+mJ9LA3GukSwdGf2xgeqBcz6AqJFBEGLaxxuDYy7dsAId XxNqwQeviHA/lD0J43L+uvGd9vf8py2j82dQWCQb2zrbud9Ghpo8Am61zYe/xr5Ys/qfSi /N26yWGCqGJbk1hSG3IpkLPLjtK9oEE=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=Q2pABqmkFq@statler.isode.com>; Tue, 5 Jan 2021 09:51:32 +0000
To: Michael Peddemors <michael@linuxmagic.com>
Cc: extra@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <82bda3f6-4629-42ea-bfa5-94551b7a721f@isode.com> <CALaySJ+pZNBfc9D3Auh+Z2XF6T7p5JzBfNtUTH45YBCNQrE5rg@mail.gmail.com> <d8fd9618-7f29-417b-0255-3c677c3f69f8@linuxmagic.com> <CAL0qLwaroU-vQLu5F5O3z61jiOAtsCEQp-pohDM4L=5duRCvEw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <25d78ea7-33ae-5d9e-8e5a-fc0cefa7169c@isode.com>
Date: Tue, 5 Jan 2021 09:51:31 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwaroU-vQLu5F5O3z61jiOAtsCEQp-pohDM4L=5duRCvEw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------7280C9331B3CCF924ADC9C9B"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/Lgq8-FCOJeAqefMjLHjR2leZW60>
Subject: Re: [Extra] BCP 178/X- convention (was AD Review of draft-ietf-extra-imap4rev2)
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, 05 Jan 2021 09:51:35 -0000

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

On 05/01/2021 00:39, Murray S. Kucherawy wrote:

> On Mon, Jan 4, 2021 at 12:59 PM Michael Peddemors=20
> <michael@linuxmagic.com <mailto:michael@linuxmagic.com>> wrote:
>
>     Lets' talk some real world examples, and what the consensus is..
>
>     X-Archive
>     X-Attachment-Id
>     X-Auth-ID
>     X-Authority-Analysis
>     X-Auto-Response-Suppress
>     [...]
>
> BCP 178 discourages standards track documents from establishing=20
> practices where an "X-" prefix means "experimental", because in=20
> reality once that name is out there, it never changes.=C2=A0 Indeed, as yo=
u=20
> point out, they're unlikely to change anytime soon, so this document=20
> shouldn't make the problem worse.
To add to this: before BCP 178 none of the above could be registered,=20
but now they are treated as any other header field and thus can be=20
registered.
>
> The point I'm making in this comment is that this document shouldn't=20
> do that with capability names.=C2=A0 Barry's correct that the ones startin=
g=20
> with "X" in examples are just examples and don't violate the BCP; I=20
> agree, but there's enough similarity to that deprecated practice that=20
> I suggest (though less urgently) avoiding it in those cases as well.

--------------7280C9331B3CCF924ADC9C9B
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>On 05/01/2021 00:39, Murray S. Kucherawy wrote:<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaroU-vQLu5F5O3z61jiOAtsCEQp-pohDM4L=3D5duRCvEw@mail.gmail=
.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 4, 2021 at 12:59 PM Michael Peddemors
          &lt;<a href=3D"mailto:michael@linuxmagic.com"
            moz-do-not-send=3D"true">michael@linuxmagic.com</a>&gt; wrote:<b=
r>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">Lets' talk some real
            world examples, and what the consensus is..<br>
            <br>
            X-Archive<br>
            X-Attachment-Id<br>
            X-Auth-ID<br>
            X-Authority-Analysis<br>
            X-Auto-Response-Suppress <br>
            [...]<br>
          </blockquote>
          <div>=C2=A0</div>
          <div>BCP 178 discourages standards track documents from
            establishing practices where an "X-" prefix means
            "experimental", because in reality once that name is out
            there, it never changes.=C2=A0 Indeed, as you point out, they're
            unlikely to change anytime soon, so this document shouldn't
            make the problem worse.</div>
        </div>
      </div>
    </blockquote>
    To add to this: before BCP 178 none of the above could be
    registered, but now they are treated as any other header field and
    thus can be registered. <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwaroU-vQLu5F5O3z61jiOAtsCEQp-pohDM4L=3D5duRCvEw@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div><br>
          </div>
          <div>The point I'm making in this comment is that this
            document shouldn't do that with capability names.=C2=A0 Barry's
            correct that the ones starting with "X" in examples are just
            examples and don't violate the BCP; I agree, but there's
            enough similarity to that deprecated practice that I suggest
            (though less urgently) avoiding it in those cases as well.<br>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>

--------------7280C9331B3CCF924ADC9C9B--


From nobody Tue Jan  5 05:56:20 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 D11D43A0EC4 for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 05:56:18 -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, 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.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 4KREdqexBaLV for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 05:56:16 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3133A0EDA for <extra@ietf.org>; Tue,  5 Jan 2021 05:56:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609854975; d=isode.com; s=june2016; i=@isode.com; bh=tRk6DNxWtYB2bb9K51xJvypOhIhToOIWhJfCqZc1e38=; 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=M7kWJfXwfkL+9JGFMYgvonrGg/Mw68xjHIxMYRjIOOA5X8WVHK0qWQhH/fVNGqYh583JuF QxnuQViVBNLVT/ngNsOZcLX7LLbmbRX6rOVOIHoBtEPKeKw2MjXB773404+/f47kiqhZ+k R0J38vj+c8n0qpbeonC0B/G1DpSdlWQ=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=Rv=gBqmsNd@statler.isode.com>; Tue, 5 Jan 2021 13:56:15 +0000
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5bd4c4e9-4414-e9b5-48f4-520f3185239b@isode.com>
Date: Tue, 5 Jan 2021 13:56:14 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------E2DEF9962040B409C0E811F1"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/60JNwzTvB7doaKiGJtLLhn8O_yY>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 05 Jan 2021 13:56:19 -0000

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

Hi Murray,

On 04/01/2021 17:21, Murray S. Kucherawy wrote:
> On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov=20
> <alexey.melnikov@isode.com <mailto:alexey.melnikov@isode.com>> wrote:
>
>>
>>     Section 2.2.1
>>
>>     =C2=A0 Clients MUST follow the syntax outlined in this specification
>>
>>     =C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send a comm=
and with missing or
>>
>>     =C2=A0=C2=A0=C2=A0extraneous spaces or arguments.
>>
>>
>>     It seems unnecessary to say this in a standards track document.=C2=A0
>>     There=E2=80=99s a similar paragraph in Section 2.2.2.
>>
>     I think the text is there due to various bugs in implementations,
>     so I would rather keep it as is.
>
> I would use "need to" instead of "MUST" here.=C2=A0 It's otherwise a bit=
=20
> hand-wavy for use of BCP 14 language.=C2=A0 But I'll leave this to the WG.
Barry replied to this and I think you are Ok with MUST staying as is.
>
>>     Section 2.2.2
>>
>>     =C2=A0=C2=A0=C2=A0In=C2=A0the case of certain server data, the data M=
UST be recorded.
>>
>>
>>     This seems misplaced; the MUST should be in the descriptions for
>>     the specific cases where this requirement exists.
>>
>     I think this text is actually Ok where it is, as it warns/requires
>     the client to implement proper cashing. It is more a statement of
>     intent.
>
>     If you think use of RFC 2119 language here is not right, we can
>     discuss that.
>
> Similar to the previous case, I suggest "needs to" here, and then=20
> wherever you talk about certain server data, that's where the BCP 14=20
> language should go.
The latter would be difficult, because there are several responses like=20
EXISTS and EXPUNGE that needs to be remembered by clients, but this list=20
is not exhaustive.
>
> I also didn't think you meant caching when you said "recorded"; I took=20
> that to refer to logging.=C2=A0 Possibly something else to clarify.

So this paragraph says:

 =C2=A0=C2=A0 Server data SHOULD
 =C2=A0=C2=A0 be recorded, so that the client can reference its recorded cop=
y
 =C2=A0=C2=A0 rather than sending a command to the server to request the dat=
a.=C2=A0 In
 =C2=A0=C2=A0 the case of certain server data, the data MUST be recorded.

I think caching is intended here. Is "remembered" better that "recorded"=20
above?

>>
>>     The text surrounding $Phishing goes further into human factors
>>     work than other working groups have felt appropriate.=C2=A0 (DKIM and
>>     DMARC come to mind.)=C2=A0 Are we sure that belongs here?
>>
>     Yes, considering this is a security consideration, a good example
>     of UI is necessary here.
>
>
> I'm curious to see if anyone else raises this given how much energy=20
> those other WGs used in the past to resist providing any UI advice at all.
There are obvious counter examples in recent history, like TLS and OAUTH WG.

>>     Should this section mention whether the system flags are
>>     permanent?=C2=A0 \Seen, for example, is clearly a system flag, but it
>>     could also be a session flag.
>>
>     No, implementations differ and sometimes even \Seen is not
>     permanent. (The last sentence of the first paragraph already says
>     "A flag of either type can also be permanent or session-only.")
>
> Yep, that's what caused me to make the comment.
Basically I don't think we can say anything useful about system flags in=20
this respect. They may or may not be permanent, same as keywords. So I=20
think no change for this one.
>
>
>>     Section 2.3.3
>>
>>
>>     All the SHOULDs in here make me wonder when an implementor might
>>     legitimately choose to do something different.=C2=A0 Or maybe instead
>>     of =E2=80=9CSHOULD be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?
>>
>     I think for delivery by SMTP, I agree. For COPY/MOVE there is
>     actually a posibility that some mailstores wouldn't preserve
>     original values, so this is asking them to really think hard about
>     preserving it.
>
>     And for APPEND, this is a similar requirement on MUAs to preserve
>     this information. (Some don't and it is very awkward.)
>
>     So I prefer to keep the last 2 SHOULDs.
>
> I guess I'm wondering if those implementations chose not to for some=20
> reason you think is valid, or was it purely an oversight on their part=20
> and you're using SHOULD to grandfather them in?=C2=A0 Would it be fine to=
=20
> say MUST here and just say that an implementation not doing this is=20
> therefore not compliant with rev2?

I think I already gave an example of limited mailstores that are not=20
able to preserve some information on COPY/MOVE. (For example they might=20
be gatewaying data to other more restrictive formats). I don't think we=20
want to make them non compliant at this time.

In regards to clients preserving internaldates on APPEND. If they use=20
APPEND to migrate/copy data between 2 different IMAP servers or between=20
a local and remote mailstore, they must preserve it. But APPEND can also=20
be used for other creating modifications, so again I think SHOULD is=20
fine as is.

>>
>>     Section 6.1.2
>>
>>
>>     This section says NOOP can be used to reset the autologout timer
>>     (which seems definite), but Section 5.1.4 says any command only
>>     SHOULD reset the timer.=C2=A0 Do these line up?
>>
>     (I assume you meant 5.4)
>
>     Well spotted. I changed text in 5.4 to readL
>
>     =C2=A0The receipt of any command from the client during that interval
>     resets the autologout timer.
>
> Why would a command deviate from the SHOULD and not reset the timer?
There is no reason I can think of, so the new text I suggested above no=20
longer uses "SHOULD". I think that addresses your issue. Do you disagree?

>     =C2=A0[snip]
>
>>     This section should make it more explicit, up front, that the
>>     response names the extensions that were successfully enabled.=C2=A0
>>     Right now the lede is buried in about the 7th paragraph.
>     I didn't move the paragraph that talks about ENABLED response, but
>     I clarified it.
>
>
> It seems like a pretty important aspect of the response, so I thought=20
> it was strange that it wasn't presented until so late in the section.=C2=
=A0=20
> Your call though.
I think the new text is clear, as it explains what appears in the=20
ENABLED response the first time ENABLED response is mentioned. So have a=20
look at -23 and let me know.
>
>>
>>     It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=
=9D
>>
>     This is saying that the server wouldn't return "BAD" to it.
>>
>>     followed immediately by =E2=80=9Csome servers don=E2=80=99t let you d=
o this=E2=80=9D.
>>
>     But this is saying that the server can still return "NO".
>>
>>     Which is the standard for this version of IMAP?=C2=A0 If it=E2=80=99s=
 an
>>     implementation choice, I think that=E2=80=99s what this should say.
>>
>     Yes, it is.
>
>
> That's fine, then, if this is clarified.=C2=A0 I just found that bit to be=
=20
> self-contradicting as written in -22.

I think IMAP is a bit subtle in places, as NO and BAD have very=20
different semantics. "BAD" means that the client shouldn't have tried=20
this. "NO" means some other reason why this fails, which can be entirely=20
server specific.

Anyway, I clarified this.


Best Regards,

Alexey



--------------E2DEF9962040B409C0E811F1
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 Murray,<br>
    </p>
    <div class=3D"moz-cite-prefix">On 04/01/2021 17:21, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov
          &lt;<a href=3D"mailto:alexey.melnikov@isode.com"
            moz-do-not-send=3D"true">alexey.melnikov@isode.com</a>&gt;
          wrote:</div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">Section
                      2.2.1<br>
                      <br>
                      =C2=A0 Clients MUST follow the syntax outlined in this
                      specification</p>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">=C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send a comm=
and with missing or</span></font></p>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">=C2=A0=C2=A0=C2=A0extraneous spaces or arguments.</span></font></p>
                    <br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">It
                      seems unnecessary to say this in a standards track
                      document.=C2=A0 There=E2=80=99s a similar paragraph in=
 Section
                      2.2.2.</p>
                  </div>
                </div>
              </blockquote>
              <p>I think the text is there due to various bugs in
                implementations, so I would rather keep it as is.</p>
            </div>
          </blockquote>
          <div>I would use "need to" instead of "MUST" here.=C2=A0 It's
            otherwise a bit hand-wavy for use of BCP 14 language.=C2=A0 But
            I'll leave this to the WG.</div>
        </div>
      </div>
    </blockquote>
    Barry replied to this and I think you are Ok with MUST staying as
    is.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>Section 2.2.2<br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">=C2=A0=C2=A0=C2=A0In=C2=A0the
                      case of certain server data, the data MUST be
                      recorded.</p>
                    <br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">This
                      seems misplaced; the MUST should be in the
                      descriptions for the specific cases where this
                      requirement exists.</p>
                  </div>
                </div>
              </blockquote>
              <p>I think this text is actually Ok where it is, as it
                warns/requires the client to implement proper cashing.
                It is more a statement of intent.<br>
              </p>
              <p>If you think use of RFC 2119 language here is not
                right, we can discuss that.<br>
              </p>
            </div>
          </blockquote>
          <div>Similar to the previous case, I suggest "needs to" here,
            and then wherever you talk about certain server data, that's
            where the BCP 14 language should go.</div>
        </div>
      </div>
    </blockquote>
    The latter would be difficult, because there are several responses
    like EXISTS and EXPUNGE that needs to be remembered by clients, but
    this list is not exhaustive. <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div><br>
          </div>
          <div>I also didn't think you meant caching when you said
            "recorded"; I took that to refer to logging.=C2=A0 Possibly
            something else to clarify.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>So this paragraph says:</p>
    <p>=C2=A0=C2=A0 Server data SHOULD<br>
      =C2=A0=C2=A0 be recorded, so that the client can reference its recorde=
d copy<br>
      =C2=A0=C2=A0 rather than sending a command to the server to request th=
e
      data.=C2=A0 In<br>
      =C2=A0=C2=A0 the case of certain server data, the data MUST be recorde=
d.<br>
    </p>
    <p>I think caching is intended here. Is "remembered" better that
      "recorded" above?<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p> </p>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">The
                      text surrounding $Phishing goes further into human
                      factors work than other working groups have felt
                      appropriate.=C2=A0 (DKIM and DMARC come to mind.)=C2=
=A0 Are
                      we sure that belongs here?</p>
                  </div>
                </div>
              </blockquote>
              Yes, considering this is a security consideration, a good
              example of UI is necessary here.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>I'm curious to see if anyone else raises this given how
            much energy those other WGs used in the past to resist
            providing any UI advice at all.<br>
          </div>
        </div>
      </div>
    </blockquote>
    There are obvious counter examples in recent history, like TLS and
    OAUTH WG.<br>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">Should
                      this section mention whether the system flags are
                      permanent?=C2=A0 \Seen, for example, is clearly a
                      system flag, but it could also be a session flag.</p>
       =20          </div>
                </div>
              </blockquote>
              <p>No, implementations differ and sometimes even \Seen is
                not permanent. (The last sentence of the first paragraph
                already says "A flag of either type can also be
                permanent or session-only.")</p>
            </div>
          </blockquote>
          <div>Yep, that's what caused me to make the comment.</div>
        </div>
      </div>
    </blockquote>
    Basically I don't think we can say anything useful about system
    flags in this respect. They may or may not be permanent, same as
    keywords. So I think no change for this one.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div> <br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">Section
                      2.3.3</p>
                    <br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">All
                      the SHOULDs in here make me wonder when an
                      implementor might legitimately choose to do
                      something different.=C2=A0 Or maybe instead of =E2=80=
=9CSHOULD
                      be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?</p>
                  </div>
                </div>
              </blockquote>
              <p>I think for delivery by SMTP, I agree. For COPY/MOVE
                there is actually a posibility that some mailstores
                wouldn't preserve original values, so this is asking
                them to really think hard about preserving it.</p>
              <p>And for APPEND, this is a similar requirement on MUAs
                to preserve this information. (Some don't and it is very
                awkward.)</p>
              <p>So I prefer to keep the last 2 SHOULDs.<br>
              </p>
            </div>
          </blockquote>
          <div>I guess I'm wondering if those implementations chose not
            to for some reason you think is valid, or was it purely an
            oversight on their part and you're using SHOULD to
            grandfather them in?=C2=A0 Would it be fine to say MUST here and
            just say that an implementation not doing this is therefore
            not compliant with rev2?</div>
        </div>
      </div>
    </blockquote>
    <p>I think I already gave an example of limited mailstores that are
      not able to preserve some information on COPY/MOVE. (For example
      they might be gatewaying data to other more restrictive formats).
      I don't think we want to make them non compliant at this time.</p>
    <p>In regards to clients preserving internaldates on APPEND. If they
      use APPEND to migrate/copy data between 2 different IMAP servers
      or between a local and remote mailstore, they must preserve it.
      But APPEND can also be used for other creating modifications, so
      again I think SHOULD is fine as is.<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">Section
                      6.1.2</p>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><br>
                      This section says NOOP can be used to reset the
                      autologout timer (which seems definite), but
                      Section 5.1.4 says any command only SHOULD reset
                      the timer.=C2=A0 Do these line up?</p>
                  </div>
                </div>
              </blockquote>
              <p>(I assume you meant 5.4)</p>
              <p>Well spotted. I changed text in 5.4 to readL</p>
              <p>=C2=A0The receipt of any command from the client during tha=
t
                interval resets the autologout timer.<br>
              </p>
            </div>
          </blockquote>
          <div>Why would a command deviate from the SHOULD and not reset
            the timer?</div>
        </div>
      </div>
    </blockquote>
    There is no reason I can think of, so the new text I suggested above
    no longer uses "SHOULD". I think that addresses your issue. Do you
    disagree?<br>
    <br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p><font size=3D"2"> </font></p>
              <p><font size=3D"2">=C2=A0[snip]<br>
                </font></p>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">This section should make it more
                  explicit, up front, that the response names the
                  extensions that were successfully enabled.=C2=A0 Right now
                  the lede is buried in about the 7th paragraph.
                  <div> </div>
                </div>
              </blockquote>
              I didn't move the paragraph that talks about ENABLED
              response, but I clarified it.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>It seems like a pretty important aspect of the response,
            so I thought it was strange that it wasn't presented until
            so late in the section.=C2=A0 Your call though. <br>
          </div>
        </div>
      </div>
    </blockquote>
    I think the new text is clear, as it explains what appears in the
    ENABLED response the first time ENABLED response is mentioned. So
    have a look at -23 and let me know.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=
=9D</span></font></p>
                  </div>
                </div>
              </blockquote>
              <font size=3D"2">This is saying that the server wouldn't
                return "BAD" to it.</font><br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">followed
                      immediately by =E2=80=9Csome servers don=E2=80=99t let=
 you do
                      this=E2=80=9D.</p>
                  </div>
                </div>
           =20  </blockquote>
              But this is saying that the server can still return "NO".<br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt">Which
                      is the standard for this version of IMAP?=C2=A0 If it=
=E2=80=99s
                      an implementation choice, I think that=E2=80=99s what =
this
                      should say.</p>
                  </div>
                </div>
              </blockquote>
              Yes, it is.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That's fine, then, if this is clarified.=C2=A0 I just found
            that bit to be self-contradicting as written in -22.</div>
        </div>
      </div>
    </blockquote>
    <p>I think IMAP is a bit subtle in places, as NO and BAD have very
      different semantics. "BAD" means that the client shouldn't have
      tried this. "NO" means some other reason why this fails, which can
      be entirely server specific.</p>
    <p>Anyway, I clarified this.<br>
    </p>
    <p><br>
    </p>
    <p><font size=3D"2">Best Regards,</font></p>
    <p><font size=3D"2">Alexey</font></p>
    <p><font size=3D"2"></font><br>
    </p>
  </body>
</html>

--------------E2DEF9962040B409C0E811F1--


From nobody Tue Jan  5 06:01:17 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 93EBD3A0EC4; Tue,  5 Jan 2021 06:01:15 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <160985527555.13110.11420354171329038535@ietfa.amsl.com>
Date: Tue, 05 Jan 2021 06:01:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/N9r2skmxac_kPCnwQACjCFDPqPQ>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-24.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, 05 Jan 2021 14:01:16 -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-24.txt
	Pages           : 164
	Date            : 2021-01-05

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-24
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-24

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


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 Jan  5 06:15:53 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 CEC963A0F09 for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 06:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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.262, 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 fR62gUj8AcDi for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 06:15:50 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 8D18D3A0F0B for <extra@ietf.org>; Tue,  5 Jan 2021 06:15:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609856149; d=isode.com; s=june2016; i=@isode.com; bh=3iDmKYYfkiodZGVutPzkn4Daq5zytGy/uAKAoSv8ou0=; 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=iYXnFRyd1HkdN5duFMv0sJgaYD+2P/ItxQBoudkPckNieDAGcBOZzFzx5FcFNp1rDn8giU juTl/z2MMBReoLegy07EBynMAzVJLloactXR3U1It+eQIelDLrR3b+Z8ihx5uJjhi/hlwi G0FPaM+kScBVrRdeKtT3oWCtu8pJDGg=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=R0lQBqmlOP@statler.isode.com>; Tue, 5 Jan 2021 14:15:49 +0000
To: extra@ietf.org
References: <160985527555.13110.11420354171329038535@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <f533ccee-e475-e016-f2e6-eb59bf2cdf98@isode.com>
Date: Tue, 5 Jan 2021 14:15:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <160985527555.13110.11420354171329038535@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/p36mnyf9rmHxLD-oxQ8dl3TV6PY>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap4rev2-24.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, 05 Jan 2021 14:15:52 -0000

Hi all,

On 05/01/2021 14:01, 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-24
> https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-24
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-24

This version adds lots of cross references, addresses (I hope) BCP 178 
related issues (please check!) and clarifies Capability command/response 
and their relationship to extensibility.

Best Regards,

Alexey



From nobody Tue Jan  5 06:17:45 2021
Return-Path: <arnt@gulbrandsen.priv.no>
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 E802D3A0CC7 for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 06:17:43 -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, SPF_HELO_NONE=0.001, SPF_NONE=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=gulbrandsen.priv.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 16FunwOxXBx6 for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 06:17:41 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1CFD3A0C6C for <extra@ietf.org>; Tue,  5 Jan 2021 06:17:40 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 38A8EC00EF; Tue,  5 Jan 2021 14:24:33 +0000 (GMT)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=arnt@gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1609856673; bh=4VXaTujq1PvnV0+9yVpABi4uTfPWmRZrFe7qzjJqVhk=; h=From:To:Subject:Date:From; b=P2PxE7a0+9pyLoH0Fh6/Ud5syaTEWaZE4YqFFEsK+ru4GoVFhzgf4RZ6nBI0jGPjy wrGSYWlTsNaKOB7K5y9ieOAOkRMmPKZGbPJy6YIOIAg6sqyg6wtuo96bfcyQZy0DA+ DD897VxKdhteeHAGi1KVLwP0uxGC09FTpcxsRCFg=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1609856672-21413-21411/9/8; Tue, 5 Jan 2021 14:24:32 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org
Date: Tue, 5 Jan 2021 15:27:09 +0100
Mime-Version: 1.0
Message-Id: <3d8e35d4-f701-45fd-a5a0-553e1cfd2adb@gulbrandsen.priv.no>
User-Agent: Trojita/0.7; Qt/5.11.3; xcb; Linux; Devuan GNU/Linux 3 (beowulf)
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/JjElF-To38OjAqPHJAa4zmQmiKA>
Subject: [Extra] 8474
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, 05 Jan 2021 14:17:44 -0000

Hi,

8474 suggests that a future extension could add 'x EID FETCH 4782394=20
BODY.PEEK=E2=80=A6' or perhaps 'x UID FETCH EMAILID 34723894 BODY.PEEK[=E2=
=80=A6'. Why was=20
this not done in 8474 itself? There's no rationale in the RFC.

I'm afraid I missed that discussion, my fault, I'm sure.

Arnt


From nobody Tue Jan  5 07:19:38 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 2DF933A0FEC for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 07:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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.262, 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 Rqoi2fIlgCuV for <extra@ietfa.amsl.com>; Tue,  5 Jan 2021 07:19:35 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4C23A0FE7 for <extra@ietf.org>; Tue,  5 Jan 2021 07:19:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609859974; d=isode.com; s=june2016; i=@isode.com; bh=GJerkITToaOKPNiFCnmUnm2epoQIJkydM93dVCGkPwo=; 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=hXL12J3xePTYYeJXynvtgnGRv4ubdzHIHdcrN1MW4WjZMFONVXZDUGyHDeg8TSRQLmziNS JtaY0JEeG8RaZRkxuaf1RiLDxYr6ygtvezdVIoCm7xszrvw8TLN/m2QcTci2EtOY2mbA+G vo9YKgDu7hUbfDP6Jxa5k/VMq5/g3zE=;
Received: from [172.27.255.49] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=SDhQBqmmlK@statler.isode.com>; Tue, 5 Jan 2021 15:19:33 +0000
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, extra@ietf.org
References: <3d8e35d4-f701-45fd-a5a0-553e1cfd2adb@gulbrandsen.priv.no>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c0559713-2b4d-765a-0cbb-008242f78bfe@isode.com>
Date: Tue, 5 Jan 2021 15:19:32 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <3d8e35d4-f701-45fd-a5a0-553e1cfd2adb@gulbrandsen.priv.no>
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/Hr6yPpfiOBd43RatICZYctliaIQ>
Subject: Re: [Extra] 8474
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, 05 Jan 2021 15:19:36 -0000

On 05/01/2021 14:27, Arnt Gulbrandsen wrote:

> Hi,
>
> 8474 suggests that a future extension could add 'x EID FETCH 4782394=20
> BODY.PEEK=E2=80=A6' or perhaps 'x UID FETCH EMAILID 34723894 BODY.PEEK[=E2=
=80=A6'. Why=20
> was this not done in 8474 itself? There's no rationale in the RFC.
>
> I'm afraid I missed that discussion, my fault, I'm sure.
>


From nobody Wed Jan  6 14:53:52 2021
Return-Path: <superuser@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 E14A73A134C for <extra@ietfa.amsl.com>; Wed,  6 Jan 2021 14:53:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fgO3qiWvnFmq for <extra@ietfa.amsl.com>; Wed,  6 Jan 2021 14:53:48 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 3E6903A0C18 for <extra@ietf.org>; Wed,  6 Jan 2021 14:53:48 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id e15so2684231vsa.0 for <extra@ietf.org>; Wed, 06 Jan 2021 14:53:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/3A3I2FlocyFgb/ZcrY0M/vxNPJcIQoq8Q8PD/1LLuA=; b=HpD9WIE/q9wnNsmDWMEbXGeTCDQQu9LCOD3a6/8qYA/QcwAwmBiu3Iin94tDQCzMpS WDrrIC2FTVGX3vis53m55utMh5jO0Xf5iP3vD+5oGCtXsM1DBnhsDez55kH4pBVxPjQW Mad5+k9js+jSbQVaGU/7cbe/dSPtSVKrkOg69Y8XsdkJ9EVim7IwiC3lBCzhrz3+y00A B/Tbxtfx3q2ovTOKdfXoRn4h3Adlv3FBqCnesPuRjYUDLKhml8Rts9r3OUwvPTjkYCjh W/a19o/zyArku6HwPGVeJz5rliDsicTZVjLRg8NrvzHaTeG7atWElLCwUhFe4D8EE7so Y1rA==
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=/3A3I2FlocyFgb/ZcrY0M/vxNPJcIQoq8Q8PD/1LLuA=; b=bRk3kPXd/+jn63YpN8P1boteqoIxHpAXCL0RKdTlEUFImwiU4jCSQLi7dodbPnuF22 849vvpKbn0tpulZzKZIrTb/O2M9y/SgEvhmRXUP7bbv8QRpme70a58SXydkb5XHehNCL uVY7ZtzSA5WmvKZNeaRxMYlb8HXgFTraADJ+aMr8FMcUNpFk8Gm03y6SujrcwXSKAhkY TTz6Xh+SYxnXyARilmdXOvFSlT77oIM+KhI3ucjNYkeJU9zxs/ruW0KL5n25dPWUBjf1 CResfhwHy1fW4vyhYqs/WwLRGkdaQJk0nsD9RUs2ORTPekP0ywedts7irKDTUA54ToBD jMiA==
X-Gm-Message-State: AOAM531p2C74lcjuK81Mjcya/zlLSskj5Dp5Y9OetV4XOujpJo0C4JmA xcjZGG+UVsxC8ESkuwgy6C8AbpshtRtOSdROu8EZZaQpx/o=
X-Google-Smtp-Source: ABdhPJyfgQ/7tPzZHO5bQPF1kxN+BXrAjliTWEaZOFaReQV9XS2NpFP7MmPVVP7ZaWEIImgG1zeWrDf78bdsPCQe72I=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr4946214vsy.54.1609973627100;  Wed, 06 Jan 2021 14:53:47 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com> <5bd4c4e9-4414-e9b5-48f4-520f3185239b@isode.com>
In-Reply-To: <5bd4c4e9-4414-e9b5-48f4-520f3185239b@isode.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 6 Jan 2021 14:53:35 -0800
Message-ID: <CAL0qLwYXqj577yxiHuQBR1E70uik4fpQuizYaBFqa2DaXCmbmw@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002421f205b84332ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/H7c5qfw6lnpw9Tp3DTbPZ9xNUmY>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 06 Jan 2021 22:53:51 -0000

--0000000000002421f205b84332ff
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 5, 2021 at 5:56 AM Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> Hi Murray,
> On 04/01/2021 17:21, Murray S. Kucherawy wrote:
>
> On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov <alexey.melnikov@isode.com=
>
> wrote:
>
>>
>> Section 2.2.1
>>
>>   Clients MUST follow the syntax outlined in this specification
>>
>>    strictly.  It is a syntax error to send a command with missing or
>>
>>    extraneous spaces or arguments.
>>
>> It seems unnecessary to say this in a standards track document.  There=
=E2=80=99s
>> a similar paragraph in Section 2.2.2.
>>
>> I think the text is there due to various bugs in implementations, so I
>> would rather keep it as is.
>>
> I would use "need to" instead of "MUST" here.  It's otherwise a bit
> hand-wavy for use of BCP 14 language.  But I'll leave this to the WG.
>
> Barry replied to this and I think you are Ok with MUST staying as is.
>

Yep, I just wanted to have the discussion.  Thanks for indulging.

Section 2.2.2
>>
>>    In the case of certain server data, the data MUST be recorded.
>>
>> This seems misplaced; the MUST should be in the descriptions for the
>> specific cases where this requirement exists.
>>
>> I think this text is actually Ok where it is, as it warns/requires the
>> client to implement proper cashing. It is more a statement of intent.
>>
>> If you think use of RFC 2119 language here is not right, we can discuss
>> that.
>>
> Similar to the previous case, I suggest "needs to" here, and then whereve=
r
> you talk about certain server data, that's where the BCP 14 language shou=
ld
> go.
>
> The latter would be difficult, because there are several responses like
> EXISTS and EXPUNGE that needs to be remembered by clients, but this list =
is
> not exhaustive.
>

I hear you.  The thing that I was hoping to solve for is that it's not very
crisp.  Which server data MUST be cached, and which server data is OK to
toss?  You can't tell just from that sentence.  If it's specified more
clearly later on, then this isn't needed.


> I also didn't think you meant caching when you said "recorded"; I took
> that to refer to logging.  Possibly something else to clarify.
>
> So this paragraph says:
>
>    Server data SHOULD
>    be recorded, so that the client can reference its recorded copy
>    rather than sending a command to the server to request the data.  In
>    the case of certain server data, the data MUST be recorded.
>
> I think caching is intended here. Is "remembered" better that "recorded"
> above?
>
Somehow when I read it the first time I didn't realize that was simply
caching; it seemed to be describing something more elaborate.  Anyway, yes,
this is fine.


>
>> The text surrounding $Phishing goes further into human factors work than
>> other working groups have felt appropriate.  (DKIM and DMARC come to
>> mind.)  Are we sure that belongs here?
>>
>> Yes, considering this is a security consideration, a good example of UI
>> is necessary here.
>>
>
> I'm curious to see if anyone else raises this given how much energy those
> other WGs used in the past to resist providing any UI advice at all.
>
> There are obvious counter examples in recent history, like TLS and OAUTH
> WG.
>

Huh.  OK.  I learned something today.  :-)


> Should this section mention whether the system flags are permanent?
>> \Seen, for example, is clearly a system flag, but it could also be a
>> session flag.
>>
>> No, implementations differ and sometimes even \Seen is not permanent.
>> (The last sentence of the first paragraph already says "A flag of either
>> type can also be permanent or session-only.")
>>
> Yep, that's what caused me to make the comment.
>
> Basically I don't think we can say anything useful about system flags in
> this respect. They may or may not be permanent, same as keywords. So I
> think no change for this one.
>

OK.


>> Section 2.3.3
>>
>> All the SHOULDs in here make me wonder when an implementor might
>> legitimately choose to do something different.  Or maybe instead of =E2=
=80=9CSHOULD
>> be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?
>>
>> I think for delivery by SMTP, I agree. For COPY/MOVE there is actually a
>> posibility that some mailstores wouldn't preserve original values, so th=
is
>> is asking them to really think hard about preserving it.
>>
>> And for APPEND, this is a similar requirement on MUAs to preserve this
>> information. (Some don't and it is very awkward.)
>>
>> So I prefer to keep the last 2 SHOULDs.
>>
> I guess I'm wondering if those implementations chose not to for some
> reason you think is valid, or was it purely an oversight on their part an=
d
> you're using SHOULD to grandfather them in?  Would it be fine to say MUST
> here and just say that an implementation not doing this is therefore not
> compliant with rev2?
>
> I think I already gave an example of limited mailstores that are not able
> to preserve some information on COPY/MOVE. (For example they might be
> gatewaying data to other more restrictive formats). I don't think we want
> to make them non compliant at this time.
>
> In regards to clients preserving internaldates on APPEND. If they use
> APPEND to migrate/copy data between 2 different IMAP servers or between a
> local and remote mailstore, they must preserve it. But APPEND can also be
> used for other creating modifications, so again I think SHOULD is fine as
> is.
>
OK, thanks for explaining.  I don't have any particular remedy in mind now
that I know what's going on behind this.


>> Section 6.1.2
>>
>>
>> This section says NOOP can be used to reset the autologout timer (which
>> seems definite), but Section 5.1.4 says any command only SHOULD reset th=
e
>> timer.  Do these line up?
>>
>> (I assume you meant 5.4)
>>
>> Well spotted. I changed text in 5.4 to readL
>>
>>  The receipt of any command from the client during that interval resets
>> the autologout timer.
>>
> Why would a command deviate from the SHOULD and not reset the timer?
>
> There is no reason I can think of, so the new text I suggested above no
> longer uses "SHOULD". I think that addresses your issue. Do you disagree?
>

Nope, we're good here.


>  [snip]
>>
>> This section should make it more explicit, up front, that the response
>> names the extensions that were successfully enabled.  Right now the lede=
 is
>> buried in about the 7th paragraph.
>>
>> I didn't move the paragraph that talks about ENABLED response, but I
>> clarified it.
>>
>
> It seems like a pretty important aspect of the response, so I thought it
> was strange that it wasn't presented until so late in the section.  Your
> call though.
>
> I think the new text is clear, as it explains what appears in the ENABLED
> response the first time ENABLED response is mentioned. So have a look at
> -23 and let me know.
>

Good to go.

>
>> It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D
>>
>> This is saying that the server wouldn't return "BAD" to it.
>>
>> followed immediately by =E2=80=9Csome servers don=E2=80=99t let you do t=
his=E2=80=9D.
>>
>> But this is saying that the server can still return "NO".
>>
>> Which is the standard for this version of IMAP?  If it=E2=80=99s an
>> implementation choice, I think that=E2=80=99s what this should say.
>>
>> Yes, it is.
>>
>
> That's fine, then, if this is clarified.  I just found that bit to be
> self-contradicting as written in -22.
>
> I think IMAP is a bit subtle in places, as NO and BAD have very different
> semantics. "BAD" means that the client shouldn't have tried this. "NO"
> means some other reason why this fails, which can be entirely server
> specific.
>
> Anyway, I clarified this.
>

Thanks!

-24 covers all of the major stuff except the text duplication (nice
work!).  Did we figure out how you'd like to deal with that?  That's not a
Last Call blocker for me -- I'll send -24 if you think it's ready -- but I
wouldn't be surprised if some downstream reviewer or AD makes the same
observation.

-MSK

--0000000000002421f205b84332ff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 5, 2021 at 5:56 AM Alexey Mel=
nikov &lt;<a href=3D"mailto:alexey.melnikov@isode.com">alexey.melnikov@isod=
e.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>Hi Murray,<br>
    </p>
    <div>On 04/01/2021 17:21, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov
          &lt;<a href=3D"mailto:alexey.melnikov@isode.com" target=3D"_blank=
">alexey.melnikov@isode.com</a>&gt;
          wrote:</div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">Section
                      2.2.1<br>
                      <br>
                      =C2=A0 Clients MUST follow the syntax outlined in thi=
s
                      specification</p>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">=C2=A0=C2=A0=C2=A0strictly.=C2=A0 It is a syntax error to send =
a command with missing or</span></font></p>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">=C2=A0=C2=A0=C2=A0extraneous spaces or arguments.</span></font>=
</p>
                    <br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">It
                      seems unnecessary to say this in a standards track
                      document.=C2=A0 There=E2=80=99s a similar paragraph i=
n Section
                      2.2.2.</p>
                  </div>
                </div>
              </blockquote>
              <p>I think the text is there due to various bugs in
                implementations, so I would rather keep it as is.</p>
            </div>
          </blockquote>
          <div>I would use &quot;need to&quot; instead of &quot;MUST&quot; =
here.=C2=A0 It&#39;s
            otherwise a bit hand-wavy for use of BCP 14 language.=C2=A0 But
            I&#39;ll leave this to the WG.</div>
        </div>
      </div>
    </blockquote>
    Barry replied to this and I think you are Ok with MUST staying as
    is.<br></div></blockquote><div><br></div><div>Yep, I just wanted to hav=
e the discussion.=C2=A0 Thanks for indulging.</div><div> <br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>Section 2.2.2<br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">=C2=A0=C2=A0=C2=A0In=C2=A0the
                      case of certain server data, the data MUST be
                      recorded.</p>
                    <br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">This
                      seems misplaced; the MUST should be in the
                      descriptions for the specific cases where this
                      requirement exists.</p>
                  </div>
                </div>
              </blockquote>
              <p>I think this text is actually Ok where it is, as it
                warns/requires the client to implement proper cashing.
                It is more a statement of intent.<br>
              </p>
              <p>If you think use of RFC 2119 language here is not
                right, we can discuss that.<br>
              </p>
            </div>
          </blockquote>
          <div>Similar to the previous case, I suggest &quot;needs to&quot;=
 here,
            and then wherever you talk about certain server data, that&#39;=
s
            where the BCP 14 language should go.</div>
        </div>
      </div>
    </blockquote>
    The latter would be difficult, because there are several responses
    like EXISTS and EXPUNGE that needs to be remembered by clients, but
    this list is not exhaustive.<br></div></blockquote><div><br></div><div>=
I hear you.=C2=A0 The thing that I was hoping to solve for is that it&#39;s=
 not very crisp.=C2=A0 Which server data MUST be cached, and which server d=
ata is OK to toss?=C2=A0 You can&#39;t tell just from that sentence.=C2=A0 =
If it&#39;s specified more clearly later on, then this isn&#39;t needed.<br=
></div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div><br>
          </div>
          <div>I also didn&#39;t think you meant caching when you said
            &quot;recorded&quot;; I took that to refer to logging.=C2=A0 Po=
ssibly
            something else to clarify.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>So this paragraph says:</p>
    <p>=C2=A0=C2=A0 Server data SHOULD<br>
      =C2=A0=C2=A0 be recorded, so that the client can reference its record=
ed copy<br>
      =C2=A0=C2=A0 rather than sending a command to the server to request t=
he
      data.=C2=A0 In<br>
      =C2=A0=C2=A0 the case of certain server data, the data MUST be record=
ed.<br>
    </p>
    <p>I think caching is intended here. Is &quot;remembered&quot; better t=
hat
      &quot;recorded&quot; above?<br></p></div></blockquote><div>Somehow wh=
en I read it the first time I didn&#39;t realize that was simply caching; i=
t seemed to be describing something more elaborate.=C2=A0 Anyway, yes, this=
 is fine.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div><p>
    </p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <p> </p>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">The
                      text surrounding $Phishing goes further into human
                      factors work than other working groups have felt
                      appropriate.=C2=A0 (DKIM and DMARC come to mind.)=C2=
=A0 Are
                      we sure that belongs here?</p>
                  </div>
                </div>
              </blockquote>
              Yes, considering this is a security consideration, a good
              example of UI is necessary here.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>I&#39;m curious to see if anyone else raises this given how
            much energy those other WGs used in the past to resist
            providing any UI advice at all.<br>
          </div>
        </div>
      </div>
    </blockquote>
    There are obvious counter examples in recent history, like TLS and
    OAUTH WG.<br></div></blockquote><div><br></div><div>Huh.=C2=A0 OK.=C2=
=A0 I learned something today.=C2=A0 :-)</div><div> <br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">Should
                      this section mention whether the system flags are
                      permanent?=C2=A0 \Seen, for example, is clearly a
                      system flag, but it could also be a session flag.</p>
                  </div>
                </div>
              </blockquote>
              <p>No, implementations differ and sometimes even \Seen is
                not permanent. (The last sentence of the first paragraph
                already says &quot;A flag of either type can also be
                permanent or session-only.&quot;)</p>
            </div>
          </blockquote>
          <div>Yep, that&#39;s what caused me to make the comment.</div>
        </div>
      </div>
    </blockquote>
    Basically I don&#39;t think we can say anything useful about system
    flags in this respect. They may or may not be permanent, same as
    keywords. So I think no change for this one.<br></div></blockquote><div=
><br></div><div>OK.</div><div> <br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div> <br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">Section
                      2.3.3</p>
                    <br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">All
                      the SHOULDs in here make me wonder when an
                      implementor might legitimately choose to do
                      something different.=C2=A0 Or maybe instead of =E2=80=
=9CSHOULD
                      be=E2=80=9D, just say =E2=80=9Cis=E2=80=9D?</p>
                  </div>
                </div>
              </blockquote>
              <p>I think for delivery by SMTP, I agree. For COPY/MOVE
                there is actually a posibility that some mailstores
                wouldn&#39;t preserve original values, so this is asking
                them to really think hard about preserving it.</p>
              <p>And for APPEND, this is a similar requirement on MUAs
                to preserve this information. (Some don&#39;t and it is ver=
y
                awkward.)</p>
              <p>So I prefer to keep the last 2 SHOULDs.<br>
              </p>
            </div>
          </blockquote>
          <div>I guess I&#39;m wondering if those implementations chose not
            to for some reason you think is valid, or was it purely an
            oversight on their part and you&#39;re using SHOULD to
            grandfather them in?=C2=A0 Would it be fine to say MUST here an=
d
            just say that an implementation not doing this is therefore
            not compliant with rev2?</div>
        </div>
      </div>
    </blockquote>
    <p>I think I already gave an example of limited mailstores that are
      not able to preserve some information on COPY/MOVE. (For example
      they might be gatewaying data to other more restrictive formats).
      I don&#39;t think we want to make them non compliant at this time.</p=
>
    <p>In regards to clients preserving internaldates on APPEND. If they
      use APPEND to migrate/copy data between 2 different IMAP servers
      or between a local and remote mailstore, they must preserve it.
      But APPEND can also be used for other creating modifications, so
      again I think SHOULD is fine as is.<br></p></div></blockquote><div>OK=
, thanks for explaining.=C2=A0 I don&#39;t have any particular remedy in mi=
nd now that I know what&#39;s going on behind this.<br></div><div> <br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
    </p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">Section
                      6.1.2</p>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><br>
                      This section says NOOP can be used to reset the
                      autologout timer (which seems definite), but
                      Section 5.1.4 says any command only SHOULD reset
                      the timer.=C2=A0 Do these line up?</p>
                  </div>
                </div>
              </blockquote>
              <p>(I assume you meant 5.4)</p>
              <p>Well spotted. I changed text in 5.4 to readL</p>
              <p>=C2=A0The receipt of any command from the client during th=
at
                interval resets the autologout timer.<br>
              </p>
            </div>
          </blockquote>
          <div>Why would a command deviate from the SHOULD and not reset
            the timer?</div>
        </div>
      </div>
    </blockquote>
    There is no reason I can think of, so the new text I suggested above
    no longer uses &quot;SHOULD&quot;. I think that addresses your issue. D=
o you
    disagree?<br></div></blockquote><div><br></div><div>Nope, we&#39;re goo=
d here.</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <p><font size=3D"2"> </font></p>
              <p><font size=3D"2">=C2=A0[snip]<br>
                </font></p>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">This section should make it more
                  explicit, up front, that the response names the
                  extensions that were successfully enabled.=C2=A0 Right no=
w
                  the lede is buried in about the 7th paragraph.
                  <div> </div>
                </div>
              </blockquote>
              I didn&#39;t move the paragraph that talks about ENABLED
              response, but I clarified it.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>It seems like a pretty important aspect of the response,
            so I thought it was strange that it wasn&#39;t presented until
            so late in the section.=C2=A0 Your call though. <br>
          </div>
        </div>
      </div>
    </blockquote>
    I think the new text is clear, as it explains what appears in the
    ENABLED response the first time ENABLED response is mentioned. So
    have a look at -23 and let me know.<br></div></blockquote><div><br></di=
v><div>Good to go. <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap">It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=
=E2=80=9D</span></font></p>
                  </div>
                </div>
              </blockquote>
              <font size=3D"2">This is saying that the server wouldn&#39;t
                return &quot;BAD&quot; to it.</font><br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">followed
                      immediately by =E2=80=9Csome servers don=E2=80=99t le=
t you do
                      this=E2=80=9D.</p>
                  </div>
                </div>
              </blockquote>
              But this is saying that the server can still return &quot;NO&=
quot;.<br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt">Which
                      is the standard for this version of IMAP?=C2=A0 If it=
=E2=80=99s
                      an implementation choice, I think that=E2=80=99s what=
 this
                      should say.</p>
                  </div>
                </div>
              </blockquote>
              Yes, it is.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That&#39;s fine, then, if this is clarified.=C2=A0 I just fo=
und
            that bit to be self-contradicting as written in -22.</div>
        </div>
      </div>
    </blockquote>
    <p>I think IMAP is a bit subtle in places, as NO and BAD have very
      different semantics. &quot;BAD&quot; means that the client shouldn&#3=
9;t have
      tried this. &quot;NO&quot; means some other reason why this fails, wh=
ich can
      be entirely server specific.</p>
    <p>Anyway, I clarified this.<br></p></div></blockquote><div><br></div><=
div>Thanks!</div></div><div class=3D"gmail_quote"><br></div><div class=3D"g=
mail_quote">-24 covers all of the major stuff except the text duplication (=
nice work!).=C2=A0 Did we figure out how you&#39;d like to deal with that?=
=C2=A0 That&#39;s not a Last Call blocker for me -- I&#39;ll send -24 if yo=
u think it&#39;s ready -- but I wouldn&#39;t be surprised if some downstrea=
m reviewer or AD makes the same observation.</div><div class=3D"gmail_quote=
"><br></div><div class=3D"gmail_quote">-MSK<br></div></div>

--0000000000002421f205b84332ff--


From nobody Wed Jan  6 15:06:10 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 0BAE33A0AFA for <extra@ietfa.amsl.com>; Wed,  6 Jan 2021 15:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 TRpakkuRdUrI for <extra@ietfa.amsl.com>; Wed,  6 Jan 2021 15:06:07 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 6303E3A09E9 for <extra@ietf.org>; Wed,  6 Jan 2021 15:06:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609974366; d=isode.com; s=june2016; i=@isode.com; bh=MO/i4nKy3G+vko4NAhqdNdhe/pxFAU9yWKjf2F8aP6Q=; 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=pzEnprB67IafNsM/ybO6WfsNlMyQHAjhYjhC3vgA5GeY+QxDLTuK3A23ps5yT3+IK4gJH/ LbBzqO9z3pSbpFSCDtFoaBAAR4H5g7ArVsXGJonShPABoNttaMWEdgLOHv0wO0Dt0mqTRn INEZIsW1txqr5CY23EqPnejzKYivkpM=;
Received: from [192.168.0.2] ((unknown) [176.252.130.164])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <X=ZCXQBqmr2O@statler.isode.com>; Wed, 6 Jan 2021 23:06:06 +0000
X-SMTP-Protocol-Errors: NORDNS
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (16G102)
In-Reply-To: <CAL0qLwYXqj577yxiHuQBR1E70uik4fpQuizYaBFqa2DaXCmbmw@mail.gmail.com>
Date: Wed, 6 Jan 2021 23:06:04 +0000
Cc: extra@ietf.org
Message-Id: <A8EBAAED-3DCE-4101-8A4C-44A42A1DDB6E@isode.com>
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com> <5bd4c4e9-4414-e9b5-48f4-520f3185239b@isode.com> <CAL0qLwYXqj577yxiHuQBR1E70uik4fpQuizYaBFqa2DaXCmbmw@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=Apple-Mail-41249058-1ECC-4792-9170-11234A5E65EB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/v9cPDpRs84Xb_2_qRS26QI1sKR4>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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, 06 Jan 2021 23:06:09 -0000

--Apple-Mail-41249058-1ECC-4792-9170-11234A5E65EB
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Murray,

> On 6 Jan 2021, at 22:53, Murray S. Kucherawy <superuser@gmail.com> wrote:
>=20
>> On Tue, Jan 5, 2021 at 5:56 AM Alexey Melnikov <alexey.melnikov@isode.com=
> wrote:


>>>>>=20
>>>>>  It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=9D=

>>>> This is saying that the server wouldn't return "BAD" to it.
>>>>> followed immediately by =E2=80=9Csome servers don=E2=80=99t let you do=
 this=E2=80=9D.
>>>> But this is saying that the server can still return "NO".
>>>>> Which is the standard for this version of IMAP?  If it=E2=80=99s an im=
plementation choice, I think that=E2=80=99s what this should say.
>>>> Yes, it is.
>>>=20
>>> That's fine, then, if this is clarified.  I just found that bit to be se=
lf-contradicting as written in -22.
>> I think IMAP is a bit subtle in places, as NO and BAD have very different=
 semantics. "BAD" means that the client shouldn't have tried this. "NO" mean=
s some other reason why this fails, which can be entirely server specific.
>>=20
>> Anyway, I clarified this.
>>=20
>=20
> Thanks!
>=20
> -24 covers all of the major stuff except the text duplication (nice work!)=
.  Did we figure out how you'd like to deal with that?  That's not a Last Ca=
ll blocker for me -- I'll send -24 if you think it's ready -- but I wouldn't=
 be surprised if some downstream reviewer or AD makes the same observation.

Yes, please start IETF LC on -24 and I fix the rest in -25.

Thank you,
Alexey=

--Apple-Mail-41249058-1ECC-4792-9170-11234A5E65EB
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=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Hi M=
urray,</div><div dir=3D"ltr"><br>On 6 Jan 2021, at 22:53, Murray S. Kucheraw=
y &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&gt; wro=
te:<br><br></div><blockquote type=3D"cite"><div dir=3D"ltr"><div dir=3D"ltr"=
><div dir=3D"ltr">On Tue, Jan 5, 2021 at 5:56 AM Alexey Melnikov &lt;<a href=
=3D"mailto:alexey.melnikov@isode.com">alexey.melnikov@isode.com</a>&gt; wrot=
e:</div></div></div></blockquote><div><br></div><br><blockquote type=3D"cite=
"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><font size=3D"2"><span style=3D"font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fon=
t-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pr=
e-wrap">It=E2=80=99s weird to say =E2=80=9Crenaming INBOX is permitted=E2=80=
=9D</span></font></p>
                  </div>
                </div>
              </blockquote>
              <font size=3D"2">This is saying that the server wouldn't
                return "BAD" to it.</font><br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt">followed
                      immediately by =E2=80=9Csome servers don=E2=80=99t let=
 you do
                      this=E2=80=9D.</p>
                  </div>
                </div>
              </blockquote>
              But this is saying that the server can still return "NO".<br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt">Which
                      is the standard for this version of IMAP?&nbsp; If it=E2=
=80=99s
                      an implementation choice, I think that=E2=80=99s what t=
his
                      should say.</p>
                  </div>
                </div>
              </blockquote>
              Yes, it is.<br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That's fine, then, if this is clarified.&nbsp; I just found
            that bit to be self-contradicting as written in -22.</div>
        </div>
      </div>
    </blockquote>
    <p>I think IMAP is a bit subtle in places, as NO and BAD have very
      different semantics. "BAD" means that the client shouldn't have
      tried this. "NO" means some other reason why this fails, which can
      be entirely server specific.</p>
    <p>Anyway, I clarified this.<br></p></div></blockquote><div><br></div><d=
iv>Thanks!</div></div><div class=3D"gmail_quote"><br></div><div class=3D"gma=
il_quote">-24 covers all of the major stuff except the text duplication (nic=
e work!).&nbsp; Did we figure out how you'd like to deal with that?&nbsp; Th=
at's not a Last Call blocker for me -- I'll send -24 if you think it's ready=
 -- but I wouldn't be surprised if some downstream reviewer or AD makes the s=
ame observation.</div></div></div></blockquote><div><br></div>Yes, please st=
art IETF LC on -24 and I fix the rest in -25.<br><div><br></div><div>Thank y=
ou,</div><div>Alexey</div></body></html>=

--Apple-Mail-41249058-1ECC-4792-9170-11234A5E65EB--


From nobody Wed Jan  6 15:20:40 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 9FC383A1392; Wed,  6 Jan 2021 15:20:38 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, superuser@gmail.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160997523804.29238.17203589124221532366@ietfa.amsl.com>
Date: Wed, 06 Jan 2021 15:20:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/427uQqmU2s64fN2CwpeTW8ruYSE>
Subject: [Extra] Last Call: <draft-ietf-extra-imap4rev2-24.txt> (Internet Message Access Protocol (IMAP) - Version 4rev2) to Proposed Standard
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, 06 Jan 2021 23:20:39 -0000

The IESG has received a request from the Email mailstore and eXtensions To
Revise or Amend WG (extra) to consider the following document: - 'Internet
Message Access Protocol (IMAP) - Version 4rev2'
  <draft-ietf-extra-imap4rev2-24.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-01-20. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc2152: UTF-7 A Mail-Safe Transformation Format of Unicode (Informational - Legacy stream)
    rfc2180: IMAP4 Multi-Accessed Mailbox Practice (Informational - Legacy stream)
    rfc1733: Distributed Electronic Mail Models in IMAP4 (Informational - IETF stream)
    rfc4549: Synchronization Operations for Disconnected IMAP4 Clients (Informational - IETF stream)
    rfc3348: The Internet Message Action Protocol (IMAP4) Child Mailbox Extension (Informational - IETF stream)
    rfc2061: IMAP4 Compatibility with IMAP2bis (Informational - Legacy stream)
    rfc1732: IMAP4 Compatibility with IMAP2 and IMAP2bis (Informational - IETF stream)
    rfc2062: Internet Message Access Protocol - Obsolete Syntax (Informational - Legacy stream)
    rfc1176: Interactive Mail Access Protocol: Version 2 (Experimental - Legacy stream)





From nobody Thu Jan 14 14:08:52 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 C9D653A16F8; Thu, 14 Jan 2021 14:08:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-extra-imap4rev2.all@ietf.org, extra@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161066213071.7885.5993845743529029815@ietfa.amsl.com>
Reply-To: Robert Sparks <rjsparks@nostrum.com>
Date: Thu, 14 Jan 2021 14:08:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/HgLH77NqWN-0mEKFy2IwvkyY-s8>
Subject: [Extra] Genart last call review of draft-ietf-extra-imap4rev2-24
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, 14 Jan 2021 22:08:51 -0000

Reviewer: Robert Sparks
Review result: Ready

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.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

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

Summary: Ready for publication as a Proposed Standard RFC

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.



From nobody Thu Jan 14 14:11:49 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 E22453A1700; Thu, 14 Jan 2021 14:11:47 -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.248, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 db0vo9cpldsP; Thu, 14 Jan 2021 14:11:46 -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 6110F3A1493; Thu, 14 Jan 2021 14:11:43 -0800 (PST)
Received: by mail-lj1-f176.google.com with SMTP id m13so8197439ljo.11; Thu, 14 Jan 2021 14:11:43 -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=wyRLAF4V+1lHLS8rMQ2Le3zJiESzx+Co6Lvi6c4gIWQ=; b=MyVXCWpIlEwxDLQHMAq2xrWzQzxiW0SkCHVWXoafG6Whs3tK/dHBruvb/bsG51DaXK yg4Tf8khroYEJ4JZAtWge3rv3TQSreeJZJrS6voVcE1rEXjFY49n/AXZ27Xkh8CdhhuS Qi0Xm+32sBG9X5oHNBK6J1oIzwF4Fdo+h7YyNAZBEvEXHFeG7/YcC1xgZZbrDWC2Fenm lklKsAiWMqHnzGKaf7NI6yGNQScot/9z9KoHnRIadlF67gImLmxKibGYfr+2rzgp+YBH +NE1syMpj9cNwaBODFe+hnXEqyJ74/Xbo5OLKMzbs8kGIPx81bnFgtPTZIzyD1QiHX0+ YYeg==
X-Gm-Message-State: AOAM530EJ3+O77v/IEJTfAdnorl3dNoM45myVfkPOPk6VJtqYFWxxNwT 9VU5sH1qfWk7zfMtj2/Jc56nNd+AIvZZiY9l0yw=
X-Google-Smtp-Source: ABdhPJwQ5BsIq/J4to7PgqiUtwoaRoVspddl8151GWMAD7MnuXE6rpc8zqs7dSH0Y6KyDjO+d3xG275m5ZGguJF4ReI=
X-Received: by 2002:a2e:8014:: with SMTP id j20mr4006314ljg.248.1610662301280;  Thu, 14 Jan 2021 14:11:41 -0800 (PST)
MIME-Version: 1.0
References: <161066213071.7885.5993845743529029815@ietfa.amsl.com>
In-Reply-To: <161066213071.7885.5993845743529029815@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 14 Jan 2021 17:11:30 -0500
Message-ID: <CALaySJ+kZi_TdMNePLHLp7MVV00pdDwhfgcQms6-ZEcV-9MyCA@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-extra-imap4rev2.all@ietf.org,  extra@ietf.org, last-call@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/3W_BajSF3vv2HL-hmY2gjZU6p9k>
Subject: Re: [Extra] 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: Thu, 14 Jan 2021 22:11:48 -0000

Thanks for the review, Robert -- I know this one was heavy to lift,
and I particularly appreciate the time and effort.

Barry

On Thu, Jan 14, 2021 at 5:09 PM Robert Sparks via Datatracker
<noreply@ietf.org> wrote:
>
> Reviewer: Robert Sparks
> Review result: Ready
>
> 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.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> 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
>
> Summary: Ready for publication as a Proposed Standard RFC
>
> 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.
>
>


From nobody Fri Jan 15 01:55: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 05FE53A00D9; Fri, 15 Jan 2021 01:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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.262, 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 Xc28fn6ds_tx; Fri, 15 Jan 2021 01:55:00 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFA13A0100; Fri, 15 Jan 2021 01:55:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1610704499; d=isode.com; s=june2016; i=@isode.com; bh=CiFWErPvOCV6YkNdNmnThyom4rp7VQkgA9JgUkScp8w=; 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=Uwdo86PnZ9af/k0FXdiJIJbYSF/H/G1uPOsDBWrNEmfEosdSKK/NDh0IXoWRZF2lEbzM5K 72pBUg6iOcveX0sT/RY+bDN5Y7mzrWhpc+A9cLlKCrrtwMt1X1A5Pko3nmnJOCjBkhVE0n lC5giFzhinQulvicRLieIpgB6oO2m/4=;
Received: from [172.27.249.250] (connect.isode.net [172.20.0.72])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YAFmcgAuQbT-@waldorf.isode.com>; Fri, 15 Jan 2021 09:54:59 +0000
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Barry Leiba <barryleiba@computer.org>, extra@ietf.org, last-call@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-extra-imap4rev2.all@ietf.org
References: <161066213071.7885.5993845743529029815@ietfa.amsl.com> <CALaySJ+kZi_TdMNePLHLp7MVV00pdDwhfgcQms6-ZEcV-9MyCA@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <afe7520f-2506-9e96-d841-f77d47a1ff0a@isode.com>
Date: Fri, 15 Jan 2021 09:54:39 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <CALaySJ+kZi_TdMNePLHLp7MVV00pdDwhfgcQms6-ZEcV-9MyCA@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/H-_2pwBxf97S1z3lYw441uExIII>
Subject: Re: [Extra] [Last-Call] 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: Fri, 15 Jan 2021 09:55:02 -0000

On 14/01/2021 22:11, Barry Leiba wrote:

> Thanks for the review, Robert -- I know this one was heavy to lift,
> and I particularly appreciate the time and effort.
And the same from me: thank you very much!
>
> Barry
>
> On Thu, Jan 14, 2021 at 5:09 PM Robert Sparks via Datatracker
> <noreply@ietf.org> wrote:
>> Reviewer: Robert Sparks
>> Review result: Ready
>>
>> 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.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> 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
>>
>> Summary: Ready for publication as a Proposed Standard RFC
>>
>> 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.
>>
>>


From nobody Tue Jan 19 06:52:15 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 E07413A1574; Tue, 19 Jan 2021 06:52:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Daniel Migault via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: draft-ietf-extra-imap4rev2.all@ietf.org, extra@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161106792581.26552.4563982290675643872@ietfa.amsl.com>
Reply-To: Daniel Migault <daniel.migault@ericsson.com>
Date: Tue, 19 Jan 2021 06:52:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/y43RVsax34FpA5layL73hUuOFEs>
Subject: [Extra] Secdir last call review of draft-ietf-extra-imap4rev2-24
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, 19 Jan 2021 14:52:06 -0000

Reviewer: Daniel Migault
Review result: Has Nits

Hi, 

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

The summary of the review is: Ready though I found some nits in 
the security consideration.  

Please find my comments/ questions below.

Yours, 
Daniel


 


       Internet Message Access Protocol (IMAP) - Version 4rev2
                     draft-ietf-extra-imap4rev2-24


[ ... ]

   $Phishing  The $Phishing keyword can be used by a delivery agent to
      mark a message as highly likely to be a phishing email.  An email
      that's determined to be a phishing email by the delivery agent
      should also be considered a junk email and have the appropriate
      junk filtering applied, including setting the $Junk flag and
      placing in the \Junk special-use mailbox (see Section 7.2.3) if
      available.
      If both the $Phishing flag and the $Junk flag are set, the user
      agent should display an additional warning message to the user.
      User agents should not use the term "phishing" in their warning
      message as most users do not understand this term.  Phrasing of
      the form "this message may be trying to steal your personal
      information" is recommended.  Additionally the user agent may
      display a warning when clicking on any hyperlinks within the
      message.

<mglt>
I tend to believe that phishing is now
(unfortunately) known by most users. 
I have the impression that UI is always a
difficult problem, and I am wondering if such
recommendations are still valid or if that is
a legacy statement. I do not have strong
feeling about what to do, so I leave it to
you, but is interested in your opinion.  


</mglt>

[ ... ]

6.2.3.  LOGIN Command

   Arguments:  user name
               password

   Responses:  no specific responses for this command

   Result:     OK - login completed, now in authenticated state
               NO - login failure: user name or password rejected
               BAD - command unknown or arguments invalid

   The LOGIN command identifies the client to the server and carries the
   plaintext password authenticating this user.

   A server MAY include a CAPABILITY response code in the tagged OK
   response to a successful LOGIN command in order to send capabilities
   automatically.  It is unnecessary for a client to send a separate
   CAPABILITY command if it recognizes these automatic capabilities.



Melnikov & Leiba          Expires July 9, 2021                 [Page 32]

Internet-Draft                  IMAP4rev2                   January 2021


      Example:    C: a001 LOGIN SMITH SESAME
                  S: a001 OK LOGIN completed

   Note: Use of the LOGIN command over an insecure network (such as the
   Internet) is a security risk, because anyone monitoring network
   traffic can obtain plaintext passwords.  The LOGIN command SHOULD NOT
   be used except as a last resort, and it is recommended that client
   implementations have a means to disable any automatic use of the
   LOGIN command.

<mglt>
For my personal information.  It is unclear
to me why the LOGIN command is SHOULD NOT and
not MUST NOT. I am mostly likely missing
something, but my impression was so far that
STARTTLS was mandatory. I suppose that "a
configuration" means that it is not always
the case, but then it becomes unclear to me
why we would have STARTTLS in one
configuration but not the other. This sounds
to me that we are sort of allowing a
vulnerable configuration as long the server
may be accessed with a secure configuration.
I think I am missing some dots.   

</mglt>

   Unless either the client is accessing IMAP service on IMAPS 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.  Server sites SHOULD NOT use any configuration
   which permits the LOGIN command without such a protection mechanism
   against password snooping.  A client implementation MUST NOT send a
   LOGIN command if the LOGINDISABLED capability is advertised.

[... ]

11.  Security Considerations

   IMAP4rev2 protocol transactions, including electronic mail data, are
   sent in the clear over the network unless protection from snooping is
   negotiated.  This can be accomplished either by the use of IMAPS
   service, STARTTLS command, negotiated privacy protection in the
   AUTHENTICATE command, or some other protection mechanism.

11.1.  STARTTLS Security Considerations

   IMAP client and server implementations MUST comply with relevant TLS
   recommendations from [RFC8314].





Melnikov & Leiba          Expires July 9, 2021                [Page 143]

Internet-Draft                  IMAP4rev2                   January 2021


   Clients and servers MUST implement TLS 1.2 [TLS-1.2] or newer.  Use
   of TLS 1.3 [TLS-1.3] is RECOMMENDED.  TLS 1.2 may be used only in
   cases where the other party has not yet implemented TLS 1.3.
   Additionally, when using TLS 1.2, IMAP implementations MUST implement
   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher suite, and SHOULD
   implement the TLS_RSA_WITH_AES_128_CBC_SHA [TLS-1.2] cipher suite.

<mglt>
I suspect there is an issue and that
TLS_RSA_WITH_AES_128_CBC_SHA  is instead
TLS_RSA_WITH_AES_128_CBC_SHA256.

However, these suites are not set as
"recommended" on the IANA registry.  Note
that the term recommended may be misleading
as it does not necessarily means the cipher
is weak. It means instead that the cipher
suite has not been through a standard
process.  This could mean, for example, the
cipher suite may correspond to a specific use
case. If that is the case, I believe that
should be mentioned.  However, I believe that
in this case, the motivation for the
community is that RSA authentication suffers
from a significant number of attacks - [1],
no forward secrecy - and I tend to believe
its support may not be recommended. RFC7525
for example mentions it as SHOULD NOT. 

[1] https://www.usenix.org/conference/usenixsecurity18/presentation/bock



In order to defer the cryptographic
recommendations to RFC8447, and ensure these
recommendations to be update to date, I would
reference that the TLS client and server are
expected to follow RFC8447 for their
cryptographic recommendations. Currently
RFC8847 sets a cipher suite as recommended
when it has received a wide support from the
community and it intend is as far as I think
to remove ciphers that will become weak.

RFC8447 works for TLS 1.2 and 1.3  keeps the
number of cipher suites relatively low, so if
the motivation to mandate
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and
LS_RSA_WITH_AES_128_CBC_SHA256 was to keep
the number of cipher suites low. If that is
the case,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 may
be a better fit at least in my opinion. 

</mglt>

   This is important as it assures that any two compliant
   implementations can be configured to interoperate.  Other TLS cipher
   suites recommended in RFC 7525 are RECOMMENDED:
   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
   TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and
   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.  All other cipher suites are
   OPTIONAL.  Note that this is a change from section 2.1 of [IMAP-TLS].

<mglt>
I believe this is good to mention RFC7525 for
TLS 1.2. There might small overlap concerning
cipher recommendations with RFC8447, but
RFC7525 recommendations go beyond and is not
limited to cipher suites recommendations. 

Regarding the RSA versus ECDSA it seems to me
that RSA is a bit behind. [1] mentions ECDSA
and RSA in their intermediate profile with
ECDSA recommended. I would maybe avoid
explicitly recommend these cipher suites, and
if that is needed, I would explain why these
are recommended.  

[1] https://wiki.mozilla.org/Security/Server_Side_TLS

</mglt>

   The list of mandatory-to-implement TLS 1.3 cipher suites is described
   in Section 9.1 of [TLS-1.3].


   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.  

In addition, when TLS 1.3 is used, the client
and the server MAY also enabled the
ticket_pinning extension [RFC8672] to further
prevent and detect man-in-the-middle attacks.
The ticket_pinning extensions provides
evidence that after an initial TLS session,
the subsequent TLS sessions are performed
with the same TLS server, as well as - when
such attacks occurs - detect them on both
client or server side. For full disclosure I am 
co-authoring identity pinning. 

</mglt>

   Both the client and server MUST check the result of the STARTTLS
   command and subsequent TLS ([TLS-1.3][TLS-1.2]) negotiation to see
   whether acceptable authentication and/or privacy was achieved.

<mglt>
This is a bit unclear to me as I do not
expect to have a server / client accepting
cipher_suites, or being configured to
establish a TLS session that does not achieve
what we expect. In other word, I understand
the paragraph as saying after the
session establishment, we recheck that
parameters chosen are appropriated. I suppose
I am missing something, but if not I would
have expected it to be the other way around.

</mglt>

11.2.  COPYUID and APPENDUID response codes

   The COPYUID and APPENDUID response codes return information about the
   mailbox, which may be considered sensitive if the mailbox has
   permissions set that permit the client to COPY or APPEND to the
   mailbox, but not SELECT or EXAMINE it.

   Consequently, these response codes SHOULD NOT be issued if the client
   does not have access to SELECT or EXAMINE the mailbox.

11.3.  LIST command and Other Users' namespace

   In response to a LIST command containing an argument of the Other
   Users' Namespace prefix, a server SHOULD NOT list users that have not
   granted list access to their personal mailboxes to the currently
   authenticated user.  Providing such a list, could compromise security
   by potentially disclosing confidential information of who is located
   on the server, or providing a starting point of a list of user
   accounts to attack.





Melnikov & Leiba          Expires July 9, 2021                [Page 144]

Internet-Draft                  IMAP4rev2                   January 2021


11.4.  Other Security Considerations

   A server error message for an AUTHENTICATE command which fails due to
   invalid credentials SHOULD NOT detail why the credentials are
   invalid.

   Use of the LOGIN command sends passwords in the clear.  This can be
   avoided by using the AUTHENTICATE command with a [SASL] mechanism
   that does not use plaintext passwords, by first negotiating
   encryption via STARTTLS or some other protection mechanism.

   A server implementation MUST implement a configuration that, at the
   time of authentication, requires:
   (1) The STARTTLS command has been negotiated.
   OR
   (2) Some other mechanism that protects the session from password
   snooping has been provided.
   OR
   (3) The following measures are in place:
   (a) The LOGINDISABLED capability is advertised, and [SASL] mechanisms
   (such as PLAIN) using plaintext passwords are NOT advertised in the
   CAPABILITY list.
   AND
   (b) The LOGIN command returns an error even if the password is
   correct.
   AND
   (c) The AUTHENTICATE command returns an error with all [SASL]
   mechanisms that use plaintext passwords, even if the password is
   correct.

   A server error message for a failing LOGIN command SHOULD NOT specify
   that the user name, as opposed to the password, is invalid.

   A server SHOULD have mechanisms in place to limit or delay failed
   AUTHENTICATE/LOGIN attempts.

   Additional security considerations are discussed in the section
   discussing the AUTHENTICATE (see Section 6.2.2) and LOGIN (see
   Section 6.2.3) commands.

<mglt>
Another concern regarding
authentication with IMAP is user have usually
one account and one login/password for a
cloud account as well as an IMAP account. In
many cases, the cloud account provides 2FA
which makes possession of the login password
not sufficient to gain access. However, IMAP
authentication hardly provide 2FA, and mail
may not benefit from the same protection and
could be used to escape 2FA. I believe this
could be mentioned as well as known
mechanisms to provide 2FA with IMAP - if 
there are some.  

Note that 2FA may not necessarily prevent to
guess the correspondence between login and
password.  

The section mentions that repeated attempts
for a password associated is detected,
somehow prevented. It may also worth
mentioning that with a large number of login
(known or guessed),
an attacker may try to guess a login
associated to a small number of commonly
known weak passwords ( password
spraying). I believe it might worth being
mentioned, that correlating failed attempts
worth also being mentioned.  
Maybe that goes a bit too far in the purpose
of recommendations, but it might may sense to
recommend strong random passwords used in
conjunction of passwords wallets or the use
of mutually authenticate TLS. 

</mglt>


<mglt>
One question I would have - and with very
little opinion on it - is how vulnerable IMAP
parsing is to injection. I usually see the
use of JSON as a big advantage toward 
this, but I would be happy to known 
your opinion on it. 

I also have the impression that injections
can be performed via the web interface, so a
web front end should be carefully considered
and IMAP server may not believe they are
always immune behind a web front end and
still require to follow the best practises.  

</mglt>



From nobody Tue Jan 19 09:46:20 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 ED8ED3A0C94; Tue, 19 Jan 2021 09:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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.262, 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 3YhHrRVAnQFd; Tue, 19 Jan 2021 09:46:11 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id E81C43A0C01; Tue, 19 Jan 2021 09:46:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611078370; d=isode.com; s=june2016; i=@isode.com; bh=DWOsnrEG2NC9YHA14olWazW99fCroSLtvUaLrUOuJ1w=; 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=snOQyPfIybGTjJLYW/rBAsu/sQFBCcTlHOuwWlIvBrtLUDSEI/FpCrub+WXXYRFke+7CMv M/rIZsBC9T+NVE10m4/XVzLQrjlqHzw7TxLOP9OQJyMSyg9l6EbTdmK9E8kQU91WHBCNL/ qkDNSMnx1kCdEn6Dikh73m67BDLo5B8=;
Received: from [172.27.250.167] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YAca4QBqmjsw@statler.isode.com>; Tue, 19 Jan 2021 17:46:09 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Daniel Migault <daniel.migault@ericsson.com>, secdir@ietf.org
Cc: draft-ietf-extra-imap4rev2.all@ietf.org, extra@ietf.org, last-call@ietf.org
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com>
Message-ID: <99082ebc-318b-5c4d-a9e6-b3893ab99c0d@isode.com>
Date: Tue, 19 Jan 2021 17:46:08 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <161106792581.26552.4563982290675643872@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/8TW5D8BmdYA17fmR2RLEU2rFX1I>
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: Tue, 19 Jan 2021 17:46:14 -0000

Hi Daniel,

Thank you for your review. My replies below. I removed some of your=20
comments that I need to think a bit more and will reply to them separately.

On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:
> Reviewer: Daniel Migault
> Review result: Has Nits
>
> Hi,
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> The summary of the review is: Ready though I found some nits in
> the security consideration.
>
> Please find my comments/ questions below.
>
> Yours,
> Daniel
>
>
>  =20
>
>
>         Internet Message Access Protocol (IMAP) - Version 4rev2
>                       draft-ietf-extra-imap4rev2-24
>
>
> [ ... ]
>
>     $Phishing  The $Phishing keyword can be used by a delivery agent to
>        mark a message as highly likely to be a phishing email.  An email
>        that's determined to be a phishing email by the delivery agent
>        should also be considered a junk email and have the appropriate
>        junk filtering applied, including setting the $Junk flag and
>        placing in the \Junk special-use mailbox (see Section 7.2.3) if
>        available.
>        If both the $Phishing flag and the $Junk flag are set, the user
>        agent should display an additional warning message to the user.
>        User agents should not use the term "phishing" in their warning
>        message as most users do not understand this term.  Phrasing of
>        the form "this message may be trying to steal your personal
>        information" is recommended.  Additionally the user agent may
>        display a warning when clicking on any hyperlinks within the
>        message.
>
> <mglt>
> I tend to believe that phishing is now
> (unfortunately) known by most users.
> I have the impression that UI is always a
> difficult problem, and I am wondering if such
> recommendations are still valid or if that is
> a legacy statement. I do not have strong
> feeling about what to do, so I leave it to
> you, but is interested in your opinion.
This text matches the original registration of the $Phishing keyword. I=20
have seen some modern email clients still following this advice, so I=20
think it is useful. Which part of it do you find outdated?
> </mglt>
>
> [ ... ]
>
> 6.2.3.  LOGIN Command
>
>     Arguments:  user name
>                 password
>
>     Responses:  no specific responses for this command
>
>     Result:     OK - login completed, now in authenticated state
>                 NO - login failure: user name or password rejected
>                 BAD - command unknown or arguments invalid
>
>     The LOGIN command identifies the client to the server and carries the
>     plaintext password authenticating this user.
>
>     A server MAY include a CAPABILITY response code in the tagged OK
>     response to a successful LOGIN command in order to send capabilities
>     automatically.  It is unnecessary for a client to send a separate
>     CAPABILITY command if it recognizes these automatic capabilities.
>
>
>
> Melnikov & Leiba          Expires July 9, 2021                 [Page 32]
> =0C
> Internet-Draft                  IMAP4rev2                   January 2021
>
>
>        Example:    C: a001 LOGIN SMITH SESAME
>                    S: a001 OK LOGIN completed
>
>     Note: Use of the LOGIN command over an insecure network (such as the
>     Internet) is a security risk, because anyone monitoring network
>     traffic can obtain plaintext passwords.  The LOGIN command SHOULD NOT
>     be used except as a last resort, and it is recommended that client
>     implementations have a means to disable any automatic use of the
>     LOGIN command.
>
> <mglt>
> For my personal information.  It is unclear
> to me why the LOGIN command is SHOULD NOT and
> not MUST NOT. I am mostly likely missing
> something, but my impression was so far that
> STARTTLS was mandatory. I suppose that "a
> configuration" means that it is not always
> the case, but then it becomes unclear to me
> why we would have STARTTLS in one
> configuration but not the other. This sounds
> to me that we are sort of allowing a
> vulnerable configuration as long the server
> may be accessed with a secure configuration.
> I think I am missing some dots.

Thank you for drawing my attention to this. I agree that the text is=20
wrong. I think the intent was to allow LOGIN on "secure networks" and=20
disallow it otherwise. After rereading this the quoted paragraph is not=20
saying that. I will fix.

> </mglt>
>
>     Unless either the client is accessing IMAP service on IMAPS 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.  Server sites SHOULD NOT use any configuration
>     which permits the LOGIN command without such a protection mechanism
>     against password snooping.  A client implementation MUST NOT send a
>     LOGIN command if the LOGINDISABLED capability is advertised.
>
> [... ]
>
> 11.  Security Considerations
>
>     IMAP4rev2 protocol transactions, including electronic mail data, are
>     sent in the clear over the network unless protection from snooping is
>     negotiated.  This can be accomplished either by the use of IMAPS
>     service, STARTTLS command, negotiated privacy protection in the
>     AUTHENTICATE command, or some other protection mechanism.
>
> 11.1.  STARTTLS Security Considerations
>
>     IMAP client and server implementations MUST comply with relevant TLS
>     recommendations from [RFC8314].
>
>
>
>
>
> Melnikov & Leiba          Expires July 9, 2021                [Page 143]
> =0C
> Internet-Draft                  IMAP4rev2                   January 2021
>
>
>     Clients and servers MUST implement TLS 1.2 [TLS-1.2] or newer.  Use
>     of TLS 1.3 [TLS-1.3] is RECOMMENDED.  TLS 1.2 may be used only in
>     cases where the other party has not yet implemented TLS 1.3.
>     Additionally, when using TLS 1.2, IMAP implementations MUST implement
>     TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher suite, and SHOULD
>     implement the TLS_RSA_WITH_AES_128_CBC_SHA [TLS-1.2] cipher suite.
>
> <mglt>
> I suspect there is an issue and that
> TLS_RSA_WITH_AES_128_CBC_SHA  is instead
> TLS_RSA_WITH_AES_128_CBC_SHA256.
>
> However, these suites are not set as
> "recommended" on the IANA registry.  Note
> that the term recommended may be misleading
> as it does not necessarily means the cipher
> is weak. It means instead that the cipher
> suite has not been through a standard
> process.  This could mean, for example, the
> cipher suite may correspond to a specific use
> case. If that is the case, I believe that
> should be mentioned.  However, I believe that
> in this case, the motivation for the
> community is that RSA authentication suffers
> from a significant number of attacks - [1],
> no forward secrecy - and I tend to believe
> its support may not be recommended. RFC7525
> for example mentions it as SHOULD NOT.
Good point. I will remove TLS_RSA_WITH_AES_128_CBC_SHA from the document.
> [1]https://www.usenix.org/conference/usenixsecurity18/presentation/bock
>
>
>
> In order to defer the cryptographic
> recommendations to RFC8447, and ensure these
> recommendations to be update to date, I would
> reference that the TLS client and server are
> expected to follow RFC8447 for their
> cryptographic recommendations. Currently
> RFC8847 sets a cipher suite as recommended
> when it has received a wide support from the
> community and it intend is as far as I think
> to remove ciphers that will become weak.
>
> RFC8447 works for TLS 1.2 and 1.3  keeps the
> number of cipher suites relatively low, so if
> the motivation to mandate
> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and
> LS_RSA_WITH_AES_128_CBC_SHA256 was to keep
> the number of cipher suites low. If that is
> the case,
> TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 may
> be a better fit at least in my opinion.
Ok.
> </mglt>
>
>     This is important as it assures that any two compliant
>     implementations can be configured to interoperate.  Other TLS cipher
>     suites recommended in RFC 7525 are RECOMMENDED:
>     TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
>     TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and
>     TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.  All other cipher suites are
>     OPTIONAL.  Note that this is a change from section 2.1 of [IMAP-TLS].
>
> <mglt>
> I believe this is good to mention RFC7525 for
> TLS 1.2. There might small overlap concerning
> cipher recommendations with RFC8447, but
> RFC7525 recommendations go beyond and is not
> limited to cipher suites recommendations.
>
> Regarding the RSA versus ECDSA it seems to me
> that RSA is a bit behind. [1] mentions ECDSA
> and RSA in their intermediate profile with
> ECDSA recommended. I would maybe avoid
> explicitly recommend these cipher suites, and
> if that is needed, I would explain why these
> are recommended.
>
> [1]https://wiki.mozilla.org/Security/Server_Side_TLS
Thank you for the link, I will review.
> </mglt>
>
>     The list of mandatory-to-implement TLS 1.3 cipher suites is described
>     in Section 9.1 of [TLS-1.3].
>
 =C2=A0[snip]
>     Both the client and server MUST check the result of the STARTTLS
>     command and subsequent TLS ([TLS-1.3][TLS-1.2]) negotiation to see
>     whether acceptable authentication and/or privacy was achieved.
>
> <mglt>
> This is a bit unclear to me as I do not
> expect to have a server / client accepting
> cipher_suites, or being configured to
> establish a TLS session that does not achieve
> what we expect. In other word, I understand
> the paragraph as saying after the
> session establishment, we recheck that
> parameters chosen are appropriated. I suppose
> I am missing something, but if not I would
> have expected it to be the other way around.

I don't think all implementations control cipher suites to be used=20
before negotiation starts (this might be API and/or implementation=20
limitation), so this is encouraging to check whether negotiated=20
ciphersuite matches policy after negotiation completes.

> </mglt>
>
 =C2=A0[snip]
> 11.4.  Other Security Considerations
>
>     A server error message for an AUTHENTICATE command which fails due to
>     invalid credentials SHOULD NOT detail why the credentials are
>     invalid.
>
>     Use of the LOGIN command sends passwords in the clear.  This can be
>     avoided by using the AUTHENTICATE command with a [SASL] mechanism
>     that does not use plaintext passwords, by first negotiating
>     encryption via STARTTLS or some other protection mechanism.
>
>     A server implementation MUST implement a configuration that, at the
>     time of authentication, requires:
>     (1) The STARTTLS command has been negotiated.
>     OR
>     (2) Some other mechanism that protects the session from password
>     snooping has been provided.
>     OR
>     (3) The following measures are in place:
>     (a) The LOGINDISABLED capability is advertised, and [SASL] mechanisms
>     (such as PLAIN) using plaintext passwords are NOT advertised in the
>     CAPABILITY list.
>     AND
>     (b) The LOGIN command returns an error even if the password is
>     correct.
>     AND
>     (c) The AUTHENTICATE command returns an error with all [SASL]
>     mechanisms that use plaintext passwords, even if the password is
>     correct.
>
>     A server error message for a failing LOGIN command SHOULD NOT specify
>     that the user name, as opposed to the password, is invalid.
>
>     A server SHOULD have mechanisms in place to limit or delay failed
>     AUTHENTICATE/LOGIN attempts.
>
>     Additional security considerations are discussed in the section
>     discussing the AUTHENTICATE (see Section 6.2.2) and LOGIN (see
>     Section 6.2.3) commands.
>
> <mglt>
> Another concern regarding
> authentication with IMAP is user have usually
> one account and one login/password for a
> cloud account as well as an IMAP account. In
> many cases, the cloud account provides 2FA
> which makes possession of the login password
> not sufficient to gain access. However, IMAP
> authentication hardly provide 2FA, and mail
> may not benefit from the same protection and
> could be used to escape 2FA. I believe this
> could be mentioned as well as known
> mechanisms to provide 2FA with IMAP - if
> there are some.
There are some drafts adding 2FA to SASL authentication that are likely=20
to be discussed in the KITTEN WG. But at this point there is nothing=20
that can be referenced normatively. I will think what can be said about=20
that.
> Note that 2FA may not necessarily prevent to
> guess the correspondence between login and
> password.
>
> The section mentions that repeated attempts
> for a password associated is detected,
> somehow prevented. It may also worth
> mentioning that with a large number of login
> (known or guessed),
> an attacker may try to guess a login
> associated to a small number of commonly
> known weak passwords ( password
> spraying). I believe it might worth being
> mentioned, that correlating failed attempts
> worth also being mentioned.
Fair enough. Can you suggest some text?
> Maybe that goes a bit too far in the purpose
> of recommendations, but it might may sense to
> recommend strong random passwords used in
> conjunction of passwords wallets or the use
> of mutually authenticate TLS.
>
> </mglt>
>
>
> <mglt>
> One question I would have - and with very
> little opinion on it - is how vulnerable IMAP
> parsing is to injection. I usually see the
> use of JSON as a big advantage toward
> this, but I would be happy to known
> your opinion on it.
Can you give me an example, as I am not sure what do you mean by=20
injection in this case?
> I also have the impression that injections
> can be performed via the web interface, so a
> web front end should be carefully considered
> and IMAP server may not believe they are
> always immune behind a web front end and
> still require to follow the best practises.
>
> </mglt>

Best Regards,

Alexey


From nobody Tue Jan 19 12:46:57 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 2A4D73A0ABB; Tue, 19 Jan 2021 12:46:48 -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 EscpjHllVbhY; Tue, 19 Jan 2021 12:46:44 -0800 (PST)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2085.outbound.protection.outlook.com [40.107.237.85]) (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 B040F3A0AA7; Tue, 19 Jan 2021 12:46:40 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Qnk0ALELhnwEj0GiN/9+TWhY9A7vk5gybKd914XmONcyYVpdShcQjcZgFh2uXWF2tE2lttRtxYvv49CL+Vtu2YR6wMCx1ZEEUrpdinkPrk6kdBuIoIgMAzXdrP4ZwOeDk4xrGLg8H57tMlMjwp3knAPN95E9RS60uKvmoda91XXKfvXTBWF1VfhZsrq6kztlBKs6dtnu7MSMkIkQkJsPAU9Y9dwB9O4Mh1W+0hOApz8Ndnwz6u2ZJepXzDX3WmJ0IxAzpytlmfOPykzDXjtIVWO2Lw2gUkoN+I16SlwlguY4F/NUoHPNFVqxx3Mku6CbaZbOR9ME9Ms7eAXRh/l0mQ==
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=gMklTcF1itVMTUcmOv4t6Mv4hEffMxmVqdrxxcQAs/M=; b=e/qftYS1jGm9o+GpZ6/UDN+AaG0OzYRZx8HyPqKWHTerkwDx/E1/WlNBXMvPm1xJdtDd30yB7Ij62xk3V4D4AZmpL9Uz+wuZytZ2FJKhRun5wzPNz1mIfEUy+amfCCnc+7vsjdtqTsYiu5TxFQvwFNg3UFHqy8JBkvbLw+5qx4oEkUvApU6zZ71hJInWaHz1yKhnOQX3CL4UJyWFfcZwEbbzZCBlbtzmKGNA0B0bmieQ1eBuXH0UuOWmtDUIVkMXdUaIInbnAHRA3VRDayT29KckgIrFtvIFdQRNw41tQxeJ/WLQSP9k0fDOWHVjHBQlEA5oLBHMzDFwE/MrMVrFgA==
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=gMklTcF1itVMTUcmOv4t6Mv4hEffMxmVqdrxxcQAs/M=; b=vMhBnWVDF6K+c0OuC4Oy1pxQjxHNDcqI9ccaBdikjvy3DBPWfzi9QmmftiwLAIPRY8edhQMvTl7M5mARudgQN9+Z2Lu7UwchY8DhHWTpB4tdQCvyT2cacyqdusK2Y6ubXwt5kA0ayInag/OzfEB5zamBZ1+tM6IIYO8HBbqmad0=
Received: from DM6PR15MB2379.namprd15.prod.outlook.com (2603:10b6:5:8a::16) by DM6PR15MB2666.namprd15.prod.outlook.com (2603:10b6:5:1a8::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Tue, 19 Jan 2021 20:46: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.3763.014; Tue, 19 Jan 2021 20:46: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: AQHW7osBCZRYcejh/kaFOg7r/oDlOqovTFtx
Date: Tue, 19 Jan 2021 20:46:37 +0000
Message-ID: <DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.prod.outlook.com>
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com>, <99082ebc-318b-5c4d-a9e6-b3893ab99c0d@isode.com>
In-Reply-To: <99082ebc-318b-5c4d-a9e6-b3893ab99c0d@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: 3007eb55-b530-4a2e-8c23-08d8bcbb50fc
x-ms-traffictypediagnostic: DM6PR15MB2666:
x-microsoft-antispam-prvs: <DM6PR15MB2666A513834BB800245F72A0E3A30@DM6PR15MB2666.namprd15.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: Rl0kw/RP7cly449tjtC8Lan+IIobuE73xAXU4gMhBikwQny+keD1EV1FYKwOEPtEztSy39CRFScxsXflAv34BoFLhmHRj/hsdBWEG73mln5MQlTl3QZeJSxTG5wnl6Nsnzfifz5MiH4kKXxAjHLCe2QreN8cT9YCCwUuNgyQ6hbbkNBzWXdt7jggkmYNh6lAYd+2qO60mIeE0wySV+l81uX4eYeJI3U7zVavS5vA//CZY0XUX8xSpLb3FPb4GlQl+LeHz1uD1ci+YKtei3+Lma0R+3NZguTQ+y8iesPFwpV9P7dsr/B9WbtcsLZA/nIN6jzUo8HUJAV4NjFjkumcaudRgmslTJvFGrlMqYt0MssW19xJUliKihgCgwQGrtIbmCCC+zBCJckh3WR4V0tvAUSsVL8ePy+7MO3djUliMxAS3zL2QUY4fM7AOrRghBDFuHY3bJ+MyUqCcDscfGcUxQ==
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)(346002)(366004)(396003)(39860400002)(136003)(33656002)(8676002)(44832011)(71200400001)(66446008)(4326008)(19627405001)(26005)(55016002)(86362001)(7696005)(9686003)(8936002)(54906003)(83380400001)(66946007)(66476007)(91956017)(186003)(478600001)(52536014)(30864003)(316002)(76116006)(5660300002)(64756008)(66574015)(53546011)(110136005)(2906002)(66556008)(6506007); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?nsWV6bFMK+32yt1Qbzg/MpP9BRcmjWQ92QdjHWbGDr4tPrvJZIP2dL/Wan?= =?iso-8859-1?Q?Auhk+n59OGSMLkpTOTUEnFFVvY1y6iGjfji46wahNScr2iUaZXauXfCegG?= =?iso-8859-1?Q?P5d60j913BeyffVUmUbHx6ntbTNmczewZ3Jdw8Teu5EP670CqUJzUQvEwY?= =?iso-8859-1?Q?C2igx8EkbZzvaI5+3wtyTRcmyhlf5JmFFkFNeWY/Qh1M63bBiZ0FdzhamG?= =?iso-8859-1?Q?vbBbvhUJ9VtGZq+e2D7svrUf+Tt2+lxX/qvgBdYbY9leoob8qx5I8UsTLi?= =?iso-8859-1?Q?kM56oUi6T1A+88LNBvW2YQX0uSTXBiYJ1wg52yPO0InGYMU+el0e07pVC9?= =?iso-8859-1?Q?iO7pGqd5K3rTWmrBCLEWz/bNcohHZ1zgITC21GuLEI1/mS8y/kCZx0rPx6?= =?iso-8859-1?Q?UmZWcIjvw57nS6KIz6X8ggEqYozXAAh77RPgs9fliDKH1YG5Uqs4Ph3cOe?= =?iso-8859-1?Q?ZBgAEphP9Qs0Y/J08NDf5G6UM4iQZrvA9Z/KsS9WBB1FGtW15VBGj+ESC9?= =?iso-8859-1?Q?VY0a/hjbYDYFQXhHUIEEOM8wxaTNWMdd6GzlDY4eT7RBt5pvxlhdvRECVN?= =?iso-8859-1?Q?LHsBufXp+8/IEKCTun74rTcv1B49fJmlOy8BkZctmKkuhJkMGtUHVjnJFA?= =?iso-8859-1?Q?vhrblhIuvQMXwEe9wXyfBV3RdnFrES5BnbLn0N88zLifivy9QCdGBUg3Z7?= =?iso-8859-1?Q?p0X4Gl8aXu+CTuIHAKDnJaw9WFZmiR81yOdtOJmrAcY06azDnDFecCVhg2?= =?iso-8859-1?Q?nQ8gpHG9b6g5jHqzfIVLPCWrK5wNBaoWsDlRoWlhPeRPy+LrKfxqmyC68U?= =?iso-8859-1?Q?a7P7IfvqYClaATO6FvVKtsMyilpQV9YYLR5vAOCQ23peN1AeHvg8ptrBsY?= =?iso-8859-1?Q?myw/fP6mhl9gmpOf19+grGu9g0ZEsHzbM15CsDi4YmYpFNv5TQ+mh+z5Ih?= =?iso-8859-1?Q?ohkhtDwvpQsoAIE7gLJQSkLGhQ1mUy8ypgCyijNMc4mpbVR9bTg0zB/ngr?= =?iso-8859-1?Q?88PTEkNGz+EuhG2zo=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR15MB2379AD34B141FD5015D25E86E3A30DM6PR15MB2379namp_"
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: 3007eb55-b530-4a2e-8c23-08d8bcbb50fc
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jan 2021 20:46:37.5930 (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: ceXGFQLZj3OsK/qvC/Oynse3BSplqVBGSSFwhOsAAfiqmCAxhxq5wX9rR7L4w3SpJq+F0b3ludSd7vJyaxhBDitOuaDM52Z1aTt6B5WLA2g=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB2666
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/baf848MEjDyzr2LdWwCvuMfHlPo>
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: Tue, 19 Jan 2021 20:46:48 -0000

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

Hi Alexey,

Thanks for your response. Please find some clarifications/responses.

Yours,
Daniel

________________________________
From: Alexey Melnikov <alexey.melnikov@isode.com>
Sent: Tuesday, January 19, 2021 12:46 PM
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,

Thank you for your review. My replies below. I removed some of your
comments that I need to think a bit more and will reply to them separately.

On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:
> Reviewer: Daniel Migault
> Review result: Has Nits
>
> Hi,
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> The summary of the review is: Ready though I found some nits in
> the security consideration.
>
> Please find my comments/ questions below.
>
> Yours,
> Daniel
>
>
>
>
>
>         Internet Message Access Protocol (IMAP) - Version 4rev2
>                       draft-ietf-extra-imap4rev2-24
>
>
> [ ... ]
>
>     $Phishing  The $Phishing keyword can be used by a delivery agent to
>        mark a message as highly likely to be a phishing email.  An email
>        that's determined to be a phishing email by the delivery agent
>        should also be considered a junk email and have the appropriate
>        junk filtering applied, including setting the $Junk flag and
>        placing in the \Junk special-use mailbox (see Section 7.2.3) if
>        available.
>        If both the $Phishing flag and the $Junk flag are set, the user
>        agent should display an additional warning message to the user.
>        User agents should not use the term "phishing" in their warning
>        message as most users do not understand this term.  Phrasing of
>        the form "this message may be trying to steal your personal
>        information" is recommended.  Additionally the user agent may
>        display a warning when clicking on any hyperlinks within the
>        message.
>
> <mglt>
> I tend to believe that phishing is now
> (unfortunately) known by most users.
> I have the impression that UI is always a
> difficult problem, and I am wondering if such
> recommendations are still valid or if that is
> a legacy statement. I do not have strong
> feeling about what to do, so I leave it to
> you, but is interested in your opinion.
This text matches the original registration of the $Phishing keyword. I
have seen some modern email clients still following this advice, so I
think it is useful. Which part of it do you find outdated?

<mglt>

Just to be clear that was just a comment. In the following sentence,
"""
User agents should not use the term "phishing" in their warning
message as most users do not understand this term.
"""
I was questioning  "as most users do not understand this term" and tend to =
believe that most users have heard what phishing means. So I am wondering i=
f the user the message is being shown does not translate to itself: "Oh yea=
h they mean phishing".  Again just some random thoughts from my part.

</mglt>
> </mglt>
>
> [ ... ]
>
> 6.2.3.  LOGIN Command
>
>     Arguments:  user name
>                 password
>
>     Responses:  no specific responses for this command
>
>     Result:     OK - login completed, now in authenticated state
>                 NO - login failure: user name or password rejected
>                 BAD - command unknown or arguments invalid
>
>     The LOGIN command identifies the client to the server and carries the
>     plaintext password authenticating this user.
>
>     A server MAY include a CAPABILITY response code in the tagged OK
>     response to a successful LOGIN command in order to send capabilities
>     automatically.  It is unnecessary for a client to send a separate
>     CAPABILITY command if it recognizes these automatic capabilities.
>
>
>
> Melnikov & Leiba          Expires July 9, 2021                 [Page 32]
>
> Internet-Draft                  IMAP4rev2                   January 2021
>
>
>        Example:    C: a001 LOGIN SMITH SESAME
>                    S: a001 OK LOGIN completed
>
>     Note: Use of the LOGIN command over an insecure network (such as the
>     Internet) is a security risk, because anyone monitoring network
>     traffic can obtain plaintext passwords.  The LOGIN command SHOULD NOT
>     be used except as a last resort, and it is recommended that client
>     implementations have a means to disable any automatic use of the
>     LOGIN command.
>
> <mglt>
> For my personal information.  It is unclear
> to me why the LOGIN command is SHOULD NOT and
> not MUST NOT. I am mostly likely missing
> something, but my impression was so far that
> STARTTLS was mandatory. I suppose that "a
> configuration" means that it is not always
> the case, but then it becomes unclear to me
> why we would have STARTTLS in one
> configuration but not the other. This sounds
> to me that we are sort of allowing a
> vulnerable configuration as long the server
> may be accessed with a secure configuration.
> I think I am missing some dots.

Thank you for drawing my attention to this. I agree that the text is
wrong. I think the intent was to allow LOGIN on "secure networks" and
disallow it otherwise. After rereading this the quoted paragraph is not
saying that. I will fix.

> </mglt>
>
>     Unless either the client is accessing IMAP service on IMAPS 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.  Server sites SHOULD NOT use any configuration
>     which permits the LOGIN command without such a protection mechanism
>     against password snooping.  A client implementation MUST NOT send a
>     LOGIN command if the LOGINDISABLED capability is advertised.
>
> [... ]
>
> 11.  Security Considerations
>
>     IMAP4rev2 protocol transactions, including electronic mail data, are
>     sent in the clear over the network unless protection from snooping is
>     negotiated.  This can be accomplished either by the use of IMAPS
>     service, STARTTLS command, negotiated privacy protection in the
>     AUTHENTICATE command, or some other protection mechanism.
>
> 11.1.  STARTTLS Security Considerations
>
>     IMAP client and server implementations MUST comply with relevant TLS
>     recommendations from [RFC8314].
>
>
>
>
>
> Melnikov & Leiba          Expires July 9, 2021                [Page 143]
>
> Internet-Draft                  IMAP4rev2                   January 2021
>
>
>     Clients and servers MUST implement TLS 1.2 [TLS-1.2] or newer.  Use
>     of TLS 1.3 [TLS-1.3] is RECOMMENDED.  TLS 1.2 may be used only in
>     cases where the other party has not yet implemented TLS 1.3.
>     Additionally, when using TLS 1.2, IMAP implementations MUST implement
>     TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher suite, and SHOULD
>     implement the TLS_RSA_WITH_AES_128_CBC_SHA [TLS-1.2] cipher suite.
>
> <mglt>
> I suspect there is an issue and that
> TLS_RSA_WITH_AES_128_CBC_SHA  is instead
> TLS_RSA_WITH_AES_128_CBC_SHA256.
>
> However, these suites are not set as
> "recommended" on the IANA registry.  Note
> that the term recommended may be misleading
> as it does not necessarily means the cipher
> is weak. It means instead that the cipher
> suite has not been through a standard
> process.  This could mean, for example, the
> cipher suite may correspond to a specific use
> case. If that is the case, I believe that
> should be mentioned.  However, I believe that
> in this case, the motivation for the
> community is that RSA authentication suffers
> from a significant number of attacks - [1],
> no forward secrecy - and I tend to believe
> its support may not be recommended. RFC7525
> for example mentions it as SHOULD NOT.
Good point. I will remove TLS_RSA_WITH_AES_128_CBC_SHA from the document.
> [1]https://www.usenix.org/conference/usenixsecurity18/presentation/bock
>
>
>
> In order to defer the cryptographic
> recommendations to RFC8447, and ensure these
> recommendations to be update to date, I would
> reference that the TLS client and server are
> expected to follow RFC8447 for their
> cryptographic recommendations. Currently
> RFC8847 sets a cipher suite as recommended
> when it has received a wide support from the
> community and it intend is as far as I think
> to remove ciphers that will become weak.
>
> RFC8447 works for TLS 1.2 and 1.3  keeps the
> number of cipher suites relatively low, so if
> the motivation to mandate
> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and
> LS_RSA_WITH_AES_128_CBC_SHA256 was to keep
> the number of cipher suites low. If that is
> the case,
> TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 may
> be a better fit at least in my opinion.
Ok.
> </mglt>
>
>     This is important as it assures that any two compliant
>     implementations can be configured to interoperate.  Other TLS cipher
>     suites recommended in RFC 7525 are RECOMMENDED:
>     TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
>     TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and
>     TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.  All other cipher suites are
>     OPTIONAL.  Note that this is a change from section 2.1 of [IMAP-TLS].
>
> <mglt>
> I believe this is good to mention RFC7525 for
> TLS 1.2. There might small overlap concerning
> cipher recommendations with RFC8447, but
> RFC7525 recommendations go beyond and is not
> limited to cipher suites recommendations.
>
> Regarding the RSA versus ECDSA it seems to me
> that RSA is a bit behind. [1] mentions ECDSA
> and RSA in their intermediate profile with
> ECDSA recommended. I would maybe avoid
> explicitly recommend these cipher suites, and
> if that is needed, I would explain why these
> are recommended.
>
> [1]https://wiki.mozilla.org/Security/Server_Side_TLS
Thank you for the link, I will review.
> </mglt>
>
>     The list of mandatory-to-implement TLS 1.3 cipher suites is described
>     in Section 9.1 of [TLS-1.3].
>
  [snip]
>     Both the client and server MUST check the result of the STARTTLS
>     command and subsequent TLS ([TLS-1.3][TLS-1.2]) negotiation to see
>     whether acceptable authentication and/or privacy was achieved.
>
> <mglt>
> This is a bit unclear to me as I do not
> expect to have a server / client accepting
> cipher_suites, or being configured to
> establish a TLS session that does not achieve
> what we expect. In other word, I understand
> the paragraph as saying after the
> session establishment, we recheck that
> parameters chosen are appropriated. I suppose
> I am missing something, but if not I would
> have expected it to be the other way around.

I don't think all implementations control cipher suites to be used
before negotiation starts (this might be API and/or implementation
limitation), so this is encouraging to check whether negotiated
ciphersuite matches policy after negotiation completes.

<mglt>
ok, I agree this maybe the case for the client, but I expect the server to =
have its library being "specifically" configured.

</mglt>

> </mglt>
>
  [snip]
> 11.4.  Other Security Considerations
>
>     A server error message for an AUTHENTICATE command which fails due to
>     invalid credentials SHOULD NOT detail why the credentials are
>     invalid.
>
>     Use of the LOGIN command sends passwords in the clear.  This can be
>     avoided by using the AUTHENTICATE command with a [SASL] mechanism
>     that does not use plaintext passwords, by first negotiating
>     encryption via STARTTLS or some other protection mechanism.
>
>     A server implementation MUST implement a configuration that, at the
>     time of authentication, requires:
>     (1) The STARTTLS command has been negotiated.
>     OR
>     (2) Some other mechanism that protects the session from password
>     snooping has been provided.
>     OR
>     (3) The following measures are in place:
>     (a) The LOGINDISABLED capability is advertised, and [SASL] mechanisms
>     (such as PLAIN) using plaintext passwords are NOT advertised in the
>     CAPABILITY list.
>     AND
>     (b) The LOGIN command returns an error even if the password is
>     correct.
>     AND
>     (c) The AUTHENTICATE command returns an error with all [SASL]
>     mechanisms that use plaintext passwords, even if the password is
>     correct.
>
>     A server error message for a failing LOGIN command SHOULD NOT specify
>     that the user name, as opposed to the password, is invalid.
>
>     A server SHOULD have mechanisms in place to limit or delay failed
>     AUTHENTICATE/LOGIN attempts.
>
>     Additional security considerations are discussed in the section
>     discussing the AUTHENTICATE (see Section 6.2.2) and LOGIN (see
>     Section 6.2.3) commands.
>
> <mglt>
> Another concern regarding
> authentication with IMAP is user have usually
> one account and one login/password for a
> cloud account as well as an IMAP account. In
> many cases, the cloud account provides 2FA
> which makes possession of the login password
> not sufficient to gain access. However, IMAP
> authentication hardly provide 2FA, and mail
> may not benefit from the same protection and
> could be used to escape 2FA. I believe this
> could be mentioned as well as known
> mechanisms to provide 2FA with IMAP - if
> there are some.
There are some drafts adding 2FA to SASL authentication that are likely
to be discussed in the KITTEN WG. But at this point there is nothing
that can be referenced normatively. I will think what can be said about
that.
> Note that 2FA may not necessarily prevent to
> guess the correspondence between login and
> password.
>
> The section mentions that repeated attempts
> for a password associated is detected,
> somehow prevented. It may also worth
> mentioning that with a large number of login
> (known or guessed),
> an attacker may try to guess a login
> associated to a small number of commonly
> known weak passwords ( password
> spraying). I believe it might worth being
> mentioned, that correlating failed attempts
> worth also being mentioned.
Fair enough. Can you suggest some text?

<mglt>
Maybe something around these lines:

An IMAP server SHOULD report any authentication failure and analyze the att=
empt with regard to a password brute force attack as well as a password spr=
aying attack. Accounts that matching password spraying attacks MUST be bloc=
ked and request to change their passwords and only password with significan=
t strength SHOULD be accepted.
</mglt>

> Maybe that goes a bit too far in the purpose
> of recommendations, but it might may sense to
> recommend strong random passwords used in
> conjunction of passwords wallets or the use
> of mutually authenticate TLS.
>
> </mglt>
>
>
> <mglt>
> One question I would have - and with very
> little opinion on it - is how vulnerable IMAP
> parsing is to injection. I usually see the
> use of JSON as a big advantage toward
> this, but I would be happy to known
> your opinion on it.
Can you give me an example, as I am not sure what do you mean by
injection in this case?

<mglt>
I do not have specific example in mind. My question was if there are known =
ways to inject some commands in a specific field or if some parsers checks =
have been relaxed to enable interoperability.

</mglt>

> I also have the impression that injections
> can be performed via the web interface, so a
> web front end should be carefully considered
> and IMAP server may not believe they are
> always immune behind a web front end and
> still require to follow the best practises.
>
> </mglt>

Best Regards,

Alexey


--_000_DM6PR15MB2379AD34B141FD5015D25E86E3A30DM6PR15MB2379namp_
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 Alexey,&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);">
Thanks for your response. Please find some clarifications/responses.&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 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> Tuesday, January 19, 2021 12:46 PM<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>
Thank you for your review. My replies below. I removed some of your <br>
comments that I need to think a bit more and will reply to them separately.=
<br>
<br>
On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:<br>
&gt; Reviewer: Daniel Migault<br>
&gt; Review result: Has Nits<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; I have reviewed this document as part of the security directorate's<br=
>
&gt; ongoing effort to review all IETF documents being processed by the<br>
&gt; IESG.&nbsp; These comments were written primarily for the benefit of t=
he<br>
&gt; security area directors.&nbsp; Document editors and WG chairs should t=
reat<br>
&gt; these comments just like any other last call comments.<br>
&gt;<br>
&gt; The summary of the review is: Ready though I found some nits in<br>
&gt; the security consideration.<br>
&gt;<br>
&gt; Please find my comments/ questions below.<br>
&gt;<br>
&gt; Yours,<br>
&gt; Daniel<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; <br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet Message Acces=
s Protocol (IMAP) - Version 4rev2<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-ex=
tra-imap4rev2-24<br>
&gt;<br>
&gt;<br>
&gt; [ ... ]<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; $Phishing&nbsp; The $Phishing keyword can be u=
sed by a delivery agent to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mark a message as highly lik=
ely to be a phishing email.&nbsp; An email<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that's determined to be a ph=
ishing email by the delivery agent<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should also be considered a =
junk email and have the appropriate<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; junk filtering applied, incl=
uding setting the $Junk flag and<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; placing in the \Junk special=
-use mailbox (see Section 7.2.3) if<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If both the $Phishing flag a=
nd the $Junk flag are set, the user<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agent should display an addi=
tional warning message to the user.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User agents should not use t=
he term &quot;phishing&quot; in their warning<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message as most users do not=
 understand this term.&nbsp; Phrasing of<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the form &quot;this message =
may be trying to steal your personal<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information&quot; is recomme=
nded.&nbsp; Additionally the user agent may<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; display a warning when click=
ing on any hyperlinks within the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; I tend to believe that phishing is now<br>
&gt; (unfortunately) known by most users.<br>
&gt; I have the impression that UI is always a<br>
&gt; difficult problem, and I am wondering if such<br>
&gt; recommendations are still valid or if that is<br>
&gt; a legacy statement. I do not have strong<br>
&gt; feeling about what to do, so I leave it to<br>
&gt; you, but is interested in your opinion.<br>
This text matches the original registration of the $Phishing keyword. I <br=
>
have seen some modern email clients still following this advice, so I <br>
think it is useful. Which part of it do you find outdated?</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&lt;mglt&gt;</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText"><span style=3D"color: rgb(0, 0, 0);">Just to be cl=
ear that was just a comment. In the following sentence,&nbsp;&nbsp;</span><=
br>
</div>
<div class=3D"PlainText"><span style=3D"color:rgb(0, 0, 0);background-color=
:rgb(255, 255, 255);display:inline !important">&quot;&quot;&quot;</span></d=
iv>
<div class=3D"PlainText"><span style=3D"color:rgb(0, 0, 0);background-color=
:rgb(255, 255, 255);display:inline !important">User agents should not use t=
he term &quot;phishing&quot; in their warning</span><br>
<span style=3D"color:rgb(0, 0, 0);background-color:rgb(255, 255, 255);displ=
ay:inline !important">message as most users do not understand this term.&nb=
sp;<span>&nbsp;</span></span><br>
</div>
<div class=3D"PlainText"><span style=3D"color:rgb(0, 0, 0);background-color=
:rgb(255, 255, 255);display:inline !important"><span>&quot;&quot;&quot;</sp=
an></span></div>
<div class=3D"PlainText"><span style=3D"color:rgb(0, 0, 0);background-color=
:rgb(255, 255, 255);display:inline !important"><span>I was questioning&nbsp=
; &quot;<span style=3D"background-color:rgb(255, 255, 255);display:inline !=
important">as most users do not understand this
 term&quot; and tend to believe that most users have heard what phishing me=
ans. So I am wondering if the user the message is being shown does not tran=
slate to itself: &quot;Oh yeah they mean phishing&quot;.&nbsp; Again just s=
ome random thoughts from my part.</span></span></span></div>
<div class=3D"PlainText"><span style=3D"color:rgb(0, 0, 0);background-color=
:rgb(255, 255, 255);display:inline !important"><span><span style=3D"backgro=
und-color:rgb(255, 255, 255);display:inline !important"><br>
</span></span></span></div>
<div class=3D"PlainText">&lt;/mglt&gt;<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt; [ ... ]<br>
&gt;<br>
&gt; 6.2.3.&nbsp; LOGIN Command<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Arguments:&nbsp; user name<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; password<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Responses:&nbsp; no specific responses for thi=
s command<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Result:&nbsp;&nbsp;&nbsp;&nbsp; OK - login com=
pleted, now in authenticated state<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; NO - login failure: user name or password rejecte=
d<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; BAD - command unknown or arguments invalid<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; The LOGIN command identifies the client to the=
 server and carries the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; plaintext password authenticating this user.<b=
r>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; A server MAY include a CAPABILITY response cod=
e in the tagged OK<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; response to a successful LOGIN command in orde=
r to send capabilities<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; automatically.&nbsp; It is unnecessary for a c=
lient to send a separate<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; CAPABILITY command if it recognizes these auto=
matic capabilities.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Melnikov &amp; Leiba&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Expires July 9, 2021&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 32]<br>
&gt;&nbsp; <br>
&gt; Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IMAP4rev2&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; January 2021<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Example:&nbsp;&nbsp;&nbsp; C=
: a001 LOGIN SMITH SESAME<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: a001 OK LOGIN completed<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Note: Use of the LOGIN command over an insecur=
e network (such as the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Internet) is a security risk, because anyone m=
onitoring network<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; traffic can obtain plaintext passwords.&nbsp; =
The LOGIN command SHOULD NOT<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; be used except as a last resort, and it is rec=
ommended that client<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; implementations have a means to disable any au=
tomatic use of the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; LOGIN command.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; For my personal information.&nbsp; It is unclear<br>
&gt; to me why the LOGIN command is SHOULD NOT and<br>
&gt; not MUST NOT. I am mostly likely missing<br>
&gt; something, but my impression was so far that<br>
&gt; STARTTLS was mandatory. I suppose that &quot;a<br>
&gt; configuration&quot; means that it is not always<br>
&gt; the case, but then it becomes unclear to me<br>
&gt; why we would have STARTTLS in one<br>
&gt; configuration but not the other. This sounds<br>
&gt; to me that we are sort of allowing a<br>
&gt; vulnerable configuration as long the server<br>
&gt; may be accessed with a secure configuration.<br>
&gt; I think I am missing some dots.<br>
<br>
Thank you for drawing my attention to this. I agree that the text is <br>
wrong. I think the intent was to allow LOGIN on &quot;secure networks&quot;=
 and <br>
disallow it otherwise. After rereading this the quoted paragraph is not <br=
>
saying that. I will fix.<br>
<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Unless either the client is accessing IMAP ser=
vice on IMAPS port<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; [RFC8314], the STARTTLS command has been negot=
iated or some other<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; mechanism that protects the session from passw=
ord snooping has been<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; provided, a server implementation MUST impleme=
nt a configuration in<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; which it advertises the LOGINDISABLED capabili=
ty and does NOT permit<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; the LOGIN command.&nbsp; Server sites SHOULD N=
OT use any configuration<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; which permits the LOGIN command without such a=
 protection mechanism<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; against password snooping.&nbsp; A client impl=
ementation MUST NOT send a<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; LOGIN command if the LOGINDISABLED capability =
is advertised.<br>
&gt;<br>
&gt; [... ]<br>
&gt;<br>
&gt; 11.&nbsp; Security Considerations<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; IMAP4rev2 protocol transactions, including ele=
ctronic mail data, are<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; sent in the clear over the network unless prot=
ection from snooping is<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; negotiated.&nbsp; This can be accomplished eit=
her by the use of IMAPS<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; service, STARTTLS command, negotiated privacy =
protection in the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; AUTHENTICATE command, or some other protection=
 mechanism.<br>
&gt;<br>
&gt; 11.1.&nbsp; STARTTLS Security Considerations<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; IMAP client and server implementations MUST co=
mply with relevant TLS<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; recommendations from [RFC8314].<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Melnikov &amp; Leiba&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Expires July 9, 2021&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 143]<br>
&gt;&nbsp; <br>
&gt; Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IMAP4rev2&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; January 2021<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Clients and servers MUST implement TLS 1.2 [TL=
S-1.2] or newer.&nbsp; Use<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; of TLS 1.3 [TLS-1.3] is RECOMMENDED.&nbsp; TLS=
 1.2 may be used only in<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; cases where the other party has not yet implem=
ented TLS 1.3.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Additionally, when using TLS 1.2, IMAP impleme=
ntations MUST implement<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher s=
uite, and SHOULD<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; implement the TLS_RSA_WITH_AES_128_CBC_SHA [TL=
S-1.2] cipher suite.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; I suspect there is an issue and that<br>
&gt; TLS_RSA_WITH_AES_128_CBC_SHA&nbsp; is instead<br>
&gt; TLS_RSA_WITH_AES_128_CBC_SHA256.<br>
&gt;<br>
&gt; However, these suites are not set as<br>
&gt; &quot;recommended&quot; on the IANA registry.&nbsp; Note<br>
&gt; that the term recommended may be misleading<br>
&gt; as it does not necessarily means the cipher<br>
&gt; is weak. It means instead that the cipher<br>
&gt; suite has not been through a standard<br>
&gt; process.&nbsp; This could mean, for example, the<br>
&gt; cipher suite may correspond to a specific use<br>
&gt; case. If that is the case, I believe that<br>
&gt; should be mentioned.&nbsp; However, I believe that<br>
&gt; in this case, the motivation for the<br>
&gt; community is that RSA authentication suffers<br>
&gt; from a significant number of attacks - [1],<br>
&gt; no forward secrecy - and I tend to believe<br>
&gt; its support may not be recommended. RFC7525<br>
&gt; for example mentions it as SHOULD NOT.<br>
Good point. I will remove TLS_RSA_WITH_AES_128_CBC_SHA from the document.<b=
r>
&gt; [1]https://www.usenix.org/conference/usenixsecurity18/presentation/boc=
k<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; In order to defer the cryptographic<br>
&gt; recommendations to RFC8447, and ensure these<br>
&gt; recommendations to be update to date, I would<br>
&gt; reference that the TLS client and server are<br>
&gt; expected to follow RFC8447 for their<br>
&gt; cryptographic recommendations. Currently<br>
&gt; RFC8847 sets a cipher suite as recommended<br>
&gt; when it has received a wide support from the<br>
&gt; community and it intend is as far as I think<br>
&gt; to remove ciphers that will become weak.<br>
&gt;<br>
&gt; RFC8447 works for TLS 1.2 and 1.3&nbsp; keeps the<br>
&gt; number of cipher suites relatively low, so if<br>
&gt; the motivation to mandate<br>
&gt; TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and<br>
&gt; LS_RSA_WITH_AES_128_CBC_SHA256 was to keep<br>
&gt; the number of cipher suites low. If that is<br>
&gt; the case,<br>
&gt; TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 may<br>
&gt; be a better fit at least in my opinion.<br>
Ok.<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; This is important as it assures that any two c=
ompliant<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; implementations can be configured to interoper=
ate.&nbsp; Other TLS cipher<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; suites recommended in RFC 7525 are RECOMMENDED=
:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.&nbsp; A=
ll other cipher suites are<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; OPTIONAL.&nbsp; Note that this is a change fro=
m section 2.1 of [IMAP-TLS].<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; I believe this is good to mention RFC7525 for<br>
&gt; TLS 1.2. There might small overlap concerning<br>
&gt; cipher recommendations with RFC8447, but<br>
&gt; RFC7525 recommendations go beyond and is not<br>
&gt; limited to cipher suites recommendations.<br>
&gt;<br>
&gt; Regarding the RSA versus ECDSA it seems to me<br>
&gt; that RSA is a bit behind. [1] mentions ECDSA<br>
&gt; and RSA in their intermediate profile with<br>
&gt; ECDSA recommended. I would maybe avoid<br>
&gt; explicitly recommend these cipher suites, and<br>
&gt; if that is needed, I would explain why these<br>
&gt; are recommended.<br>
&gt;<br>
&gt; [1]https://wiki.mozilla.org/Security/Server_Side_TLS<br>
Thank you for the link, I will review.<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; The list of mandatory-to-implement TLS 1.3 cip=
her suites is described<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; in Section 9.1 of [TLS-1.3].<br>
&gt;<br>
&nbsp;&nbsp;[snip]<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Both the client and server MUST check the resu=
lt of the STARTTLS<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; command and subsequent TLS ([TLS-1.3][TLS-1.2]=
) negotiation to see<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; whether acceptable authentication and/or priva=
cy was achieved.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; This is a bit unclear to me as I do not<br>
&gt; expect to have a server / client accepting<br>
&gt; cipher_suites, or being configured to<br>
&gt; establish a TLS session that does not achieve<br>
&gt; what we expect. In other word, I understand<br>
&gt; the paragraph as saying after the<br>
&gt; session establishment, we recheck that<br>
&gt; parameters chosen are appropriated. I suppose<br>
&gt; I am missing something, but if not I would<br>
&gt; have expected it to be the other way around.<br>
<br>
I don't think all implementations control cipher suites to be used <br>
before negotiation starts (this might be API and/or implementation <br>
limitation), so this is encouraging to check whether negotiated <br>
ciphersuite matches policy after negotiation completes.</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&lt;mglt&gt;</div>
<div class=3D"PlainText">ok, I agree this maybe the case for the client, bu=
t I expect the server to have its library being &quot;specifically&quot; co=
nfigured.&nbsp;</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&lt;/mglt&gt;<br>
<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&nbsp;&nbsp;[snip]<br>
&gt; 11.4.&nbsp; Other Security Considerations<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; A server error message for an AUTHENTICATE com=
mand which fails due to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; invalid credentials SHOULD NOT detail why the =
credentials are<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; invalid.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Use of the LOGIN command sends passwords in th=
e clear.&nbsp; This can be<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; avoided by using the AUTHENTICATE command with=
 a [SASL] mechanism<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; that does not use plaintext passwords, by firs=
t negotiating<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; encryption via STARTTLS or some other protecti=
on mechanism.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; A server implementation MUST implement a confi=
guration that, at the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; time of authentication, requires:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (1) The STARTTLS command has been negotiated.<=
br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; OR<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (2) Some other mechanism that protects the ses=
sion from password<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; snooping has been provided.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; OR<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (3) The following measures are in place:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (a) The LOGINDISABLED capability is advertised=
, and [SASL] mechanisms<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (such as PLAIN) using plaintext passwords are =
NOT advertised in the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; CAPABILITY list.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; AND<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (b) The LOGIN command returns an error even if=
 the password is<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; correct.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; AND<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; (c) The AUTHENTICATE command returns an error =
with all [SASL]<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; mechanisms that use plaintext passwords, even =
if the password is<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; correct.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; A server error message for a failing LOGIN com=
mand SHOULD NOT specify<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; that the user name, as opposed to the password=
, is invalid.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; A server SHOULD have mechanisms in place to li=
mit or delay failed<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; AUTHENTICATE/LOGIN attempts.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Additional security considerations are discuss=
ed in the section<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; discussing the AUTHENTICATE (see Section 6.2.2=
) and LOGIN (see<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Section 6.2.3) commands.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; Another concern regarding<br>
&gt; authentication with IMAP is user have usually<br>
&gt; one account and one login/password for a<br>
&gt; cloud account as well as an IMAP account. In<br>
&gt; many cases, the cloud account provides 2FA<br>
&gt; which makes possession of the login password<br>
&gt; not sufficient to gain access. However, IMAP<br>
&gt; authentication hardly provide 2FA, and mail<br>
&gt; may not benefit from the same protection and<br>
&gt; could be used to escape 2FA. I believe this<br>
&gt; could be mentioned as well as known<br>
&gt; mechanisms to provide 2FA with IMAP - if<br>
&gt; there are some.<br>
There are some drafts adding 2FA to SASL authentication that are likely <br=
>
to be discussed in the KITTEN WG. But at this point there is nothing <br>
that can be referenced normatively. I will think what can be said about <br=
>
that.<br>
&gt; Note that 2FA may not necessarily prevent to<br>
&gt; guess the correspondence between login and<br>
&gt; password.<br>
&gt;<br>
&gt; The section mentions that repeated attempts<br>
&gt; for a password associated is detected,<br>
&gt; somehow prevented. It may also worth<br>
&gt; mentioning that with a large number of login<br>
&gt; (known or guessed),<br>
&gt; an attacker may try to guess a login<br>
&gt; associated to a small number of commonly<br>
&gt; known weak passwords ( password<br>
&gt; spraying). I believe it might worth being<br>
&gt; mentioned, that correlating failed attempts<br>
&gt; worth also being mentioned.<br>
Fair enough. Can you suggest some text?<br>
<br>
</div>
<div class=3D"PlainText">&lt;mglt&gt;</div>
<div class=3D"PlainText">Maybe something around these lines:</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">An IMAP server SHOULD report any authentication fa=
ilure and analyze the attempt with regard to a password brute force attack =
as well as a password spraying attack. Accounts that matching password spra=
ying attacks MUST be blocked and request
 to change their passwords and only password with significant strength SHOU=
LD be accepted.&nbsp;</div>
<div class=3D"PlainText">&lt;/mglt&gt;&nbsp;</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&gt; Maybe that goes a bit too far in the purpose<=
br>
&gt; of recommendations, but it might may sense to<br>
&gt; recommend strong random passwords used in<br>
&gt; conjunction of passwords wallets or the use<br>
&gt; of mutually authenticate TLS.<br>
&gt;<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; One question I would have - and with very<br>
&gt; little opinion on it - is how vulnerable IMAP<br>
&gt; parsing is to injection. I usually see the<br>
&gt; use of JSON as a big advantage toward<br>
&gt; this, but I would be happy to known<br>
&gt; your opinion on it.<br>
Can you give me an example, as I am not sure what do you mean by <br>
injection in this case?</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&lt;mglt&gt;</div>
<div class=3D"PlainText">I do not have specific example in mind. My questio=
n was if there are known ways to inject some commands in a specific field o=
r if some parsers checks have been relaxed to enable interoperability.&nbsp=
;</div>
<div class=3D"PlainText"><br>
</div>
<div class=3D"PlainText">&lt;/mglt&gt;</div>
<div class=3D"PlainText"><br>
&gt; I also have the impression that injections<br>
&gt; can be performed via the web interface, so a<br>
&gt; web front end should be carefully considered<br>
&gt; and IMAP server may not believe they are<br>
&gt; always immune behind a web front end and<br>
&gt; still require to follow the best practises.<br>
&gt;<br>
&gt; &lt;/mglt&gt;<br>
<br>
Best Regards,<br>
<br>
Alexey<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_DM6PR15MB2379AD34B141FD5015D25E86E3A30DM6PR15MB2379namp_--


From nobody Wed Jan 20 09:31:26 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 BFB313A1028; Wed, 20 Jan 2021 09:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 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.262, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, 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 6HFP6p3DBRt1; Wed, 20 Jan 2021 09:31:19 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id AB0D73A0AE8; Wed, 20 Jan 2021 09:31:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611163877; d=isode.com; s=june2016; i=@isode.com; bh=M8tMXbRgBudrl2UlcRB0PCcw71rntN+ExU926NUd1yw=; 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=KuVoDbuCQAC7t0YzRBnpv40snSqvoyKdEGgdGhBlmI4TaRveHE4VjsNRmbCJikhVL6nnDl F6CUoOEQQ8Shx0I9zLak+yfIJaW4bPpl4RX4tPXxQjnIX3s/obS9v4phjQXF/Ed6OWCZln dZ9u6heY+05x+XEGu3ZdFO6MkdlJMWw=;
Received: from [172.27.250.196] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YAho5ABqmkwt@statler.isode.com>; Wed, 20 Jan 2021 17:31:16 +0000
To: Daniel Migault <daniel.migault@ericsson.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>
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com> <99082ebc-318b-5c4d-a9e6-b3893ab99c0d@isode.com> <DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.prod.outlook.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <ecbc01e4-4a84-4a5b-e7be-e87c7897a01c@isode.com>
Date: Wed, 20 Jan 2021 17:31:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------13083B1379C3450CCE4C04B9"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/MGqlflUY1m7VCfEHzyA5_m3Yy2o>
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: Wed, 20 Jan 2021 17:31:25 -0000

--------------13083B1379C3450CCE4C04B9
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: quoted-printable

Hi Daniel,


On 19/01/2021 20:46, Daniel Migault wrote:
> Hi Alexey,
>
> Thanks for your response. Please find some clarifications/responses.
Thank you for the followup. My responses below.
>
> Yours,
> Daniel
>
> ------------------------------------------------------------------------
> *From:* Alexey Melnikov <alexey.melnikov@isode.com>
> *Sent:* Tuesday, January 19, 2021 12:46 PM
> *To:* Daniel Migault <daniel.migault@ericsson.com>; secdir@ietf.org=20
> <secdir@ietf.org>
> *Cc:* draft-ietf-extra-imap4rev2.all@ietf.org=20
> <draft-ietf-extra-imap4rev2.all@ietf.org>; extra@ietf.org=20
> <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,
>
> Thank you for your review. My replies below. I removed some of your
> comments that I need to think a bit more and will reply to them=20
> separately.
>
> On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:
> > Reviewer: Daniel Migault
> > Review result: Has Nits
> >
 =A0[snip]
> >
> > [ ... ]
> >
> >=A0=A0=A0=A0 $Phishing=A0 The $Phishing keyword can be used by a delivery=
 agent to
> >=A0=A0=A0=A0=A0=A0=A0 mark a message as highly likely to be a phishing em=
ail.=A0 An email
> >=A0=A0=A0=A0=A0=A0=A0 that's determined to be a phishing email by the del=
ivery agent
> >=A0=A0=A0=A0=A0=A0=A0 should also be considered a junk email and have the=
 appropriate
> >=A0=A0=A0=A0=A0=A0=A0 junk filtering applied, including setting the $Junk=
 flag and
> >=A0=A0=A0=A0=A0=A0=A0 placing in the \Junk special-use mailbox (see Secti=
on 7.2.3) if
> >=A0=A0=A0=A0=A0=A0=A0 available.
> >=A0=A0=A0=A0=A0=A0=A0 If both the $Phishing flag and the $Junk flag are s=
et, the user
> >=A0=A0=A0=A0=A0=A0=A0 agent should display an additional warning message =
to the user.
> >=A0=A0=A0=A0=A0=A0=A0 User agents should not use the term "phishing" in t=
heir warning
> >=A0=A0=A0=A0=A0=A0=A0 message as most users do not understand this term.=
=A0 Phrasing of
> >=A0=A0=A0=A0=A0=A0=A0 the form "this message may be trying to steal your =
personal
> >=A0=A0=A0=A0=A0=A0=A0 information" is recommended.=A0 Additionally the us=
er agent may
> >=A0=A0=A0=A0=A0=A0=A0 display a warning when clicking on any hyperlinks w=
ithin the
> >=A0=A0=A0=A0=A0=A0=A0 message.
> >
> > <mglt>
> > I tend to believe that phishing is now
> > (unfortunately) known by most users.
> > I have the impression that UI is always a
> > difficult problem, and I am wondering if such
> > recommendations are still valid or if that is
> > a legacy statement. I do not have strong
> > feeling about what to do, so I leave it to
> > you, but is interested in your opinion.
> This text matches the original registration of the $Phishing keyword. I
> have seen some modern email clients still following this advice, so I
> think it is useful. Which part of it do you find outdated?
>
> <mglt>
>
> Just to be clear that was just a comment. In the following sentence,
> """
> User agents should not use the term "phishing" in their warning
> message as most users do not understand this term.
> """
> I was questioning=A0 "as most users do not understand this term" and=20
> tend to believe that most users have heard what phishing means. So I=20
> am wondering if the user the message is being shown does not translate=20
> to itself: "Oh yeah they mean phishing".=A0 Again just some random=20
> thoughts from my part.
Sorry, I was staring at this text so much that I stopped noticing it.=20
Now that you pointed this out I think removing this sentence makes sense.
>
> </mglt>
 =A0[snip]
> >
> > The section mentions that repeated attempts
> > for a password associated is detected,
> > somehow prevented. It may also worth
> > mentioning that with a large number of login
> > (known or guessed),
> > an attacker may try to guess a login
> > associated to a small number of commonly
> > known weak passwords ( password
> > spraying). I believe it might worth being
> > mentioned, that correlating failed attempts
> > worth also being mentioned.
> Fair enough. Can you suggest some text?
>
> <mglt>
> Maybe something around these lines:
>
> An IMAP server SHOULD report any authentication failure and analyze=20
> the attempt with regard to a password brute force attack as well as a=20
> password spraying attack. Accounts that matching password spraying=20
> attacks MUST be blocked and request to change their passwords and only=20
> password with significant strength SHOULD be accepted.
I edited this slightly. Thank you for the suggestion.
> /**/
> </mglt>
>
> > Maybe that goes a bit too far in the purpose
> > of recommendations, but it might may sense to
> > recommend strong random passwords used in
> > conjunction of passwords wallets or the use
> > of mutually authenticate TLS.
> >
> > </mglt>
> >
> >
> > <mglt>
> > One question I would have - and with very
> > little opinion on it - is how vulnerable IMAP
> > parsing is to injection. I usually see the
> > use of JSON as a big advantage toward
> > this, but I would be happy to known
> > your opinion on it.
> Can you give me an example, as I am not sure what do you mean by
> injection in this case?
>
> <mglt>
> I do not have specific example in mind. My question was if there are=20
> known ways to inject some commands in a specific field or if some=20
> parsers checks have been relaxed to enable interoperability.
I can't think of any. IMAP is either using octet-counted literals or=20
strict syntax (LIST-like). Syntax is quite regular and easier than XML=20
(IMHO).
>
> </mglt>
>
> > I also have the impression that injections
> > can be performed via the web interface, so a
> > web front end should be carefully considered
> > and IMAP server may not believe they are
> > always immune behind a web front end and
> > still require to follow the best practises.
> >
> > </mglt>
>
> Best Regards,
>
> Alexey
>

--------------13083B1379C3450CCE4C04B9
Content-Type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html;
      charset=3Dwindows-1252">
  </head>
  <body>
    <p>Hi Daniel,</p>
    <p><br>
    </p>
    <div class=3D"moz-cite-prefix">On 19/01/2021 20:46, Daniel Migault
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3Dwindows-1252">
      <style type=3D"text/css" style=3D"display:none;">P {margin-top:0;margi=
n-bottom:0;}</style>
      <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
        Hi Alexey,=A0</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);">
        Thanks for your response. Please find some
        clarifications/responses. <br>
      </div>
    </blockquote>
    Thank you for the followup. My responses below.<br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <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,=A0<br>
        Daniel</div>
      <div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; 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 style=3D"font-size:11pt"
          face=3D"Calibri, sans-serif" color=3D"#000000"><b>From:</b> Alexey
          Melnikov <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:alexey.=
melnikov@isode.com">&lt;alexey.melnikov@isode.com&gt;</a><br>
          <b>Sent:</b> Tuesday, January 19, 2021 12:46 PM<br>
          <b>To:</b> Daniel Migault <a class=3D"moz-txt-link-rfc2396E" href=
=3D"mailto:daniel.migault@ericsson.com">&lt;daniel.migault@ericsson.com&gt;<=
/a>;
          <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:secdir@ietf.o=
rg">secdir@ietf.org</a> <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:se=
cdir@ietf.org">&lt;secdir@ietf.org&gt;</a><br>
          <b>Cc:</b> <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:dr=
aft-ietf-extra-imap4rev2.all@ietf.org">draft-ietf-extra-imap4rev2.all@ietf.o=
rg</a>
          <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:draft-ietf-extra=
-imap4rev2.all@ietf.org">&lt;draft-ietf-extra-imap4rev2.all@ietf.org&gt;</a>=
;
          <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:extra@ietf.or=
g">extra@ietf.org</a> <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:extr=
a@ietf.org">&lt;extra@ietf.org&gt;</a>; <a class=3D"moz-txt-link-abbreviated=
" href=3D"mailto:last-call@ietf.org">last-call@ietf.org</a>
          <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:last-call@ietf.o=
rg">&lt;last-call@ietf.org&gt;</a><br>
          <b>Subject:</b> Re: Secdir last call review of
          draft-ietf-extra-imap4rev2-24</font>
        <div>=A0</div>
      </div>
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt">
            <div class=3D"PlainText">Hi Daniel,<br>
              <br>
              Thank you for your review. My replies below. I removed
              some of your <br>
              comments that I need to think a bit more and will reply to
              them separately.<br>
              <br>
              On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:<br>
              &gt; Reviewer: Daniel Migault<br>
              &gt; Review result: Has Nits<br>
              &gt;<br>
            </div>
          </span></font></div>
    </blockquote>
    <font size=3D"2">=A0[snip]</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt">
            <div class=3D"PlainText">&gt;<br>
              &gt; [ ... ]<br>
              &gt;<br>
              &gt;=A0=A0=A0=A0 $Phishing=A0 The $Phishing keyword can be use=
d by a
              delivery agent to<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 mark a message as highly likely to b=
e a
              phishing email.=A0 An email<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 that's determined to be a phishing e=
mail by
              the delivery agent<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 should also be considered a junk ema=
il and
              have the appropriate<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 junk filtering applied, including se=
tting the
              $Junk flag and<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 placing in the \Junk special-use mai=
lbox (see
              Section 7.2.3) if<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 available.<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 If both the $Phishing flag and the $=
Junk flag
              are set, the user<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 agent should display an additional w=
arning
              message to the user.<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 User agents should not use the term =
"phishing"
              in their warning<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 message as most users do not underst=
and this
              term.=A0 Phrasing of<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 the form "this message may be trying=
 to steal
              your personal<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 information" is recommended.=A0 Addi=
tionally the
              user agent may<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 display a warning when clicking on a=
ny
              hyperlinks within the<br>
              &gt;=A0=A0=A0=A0=A0=A0=A0 message.<br>
              &gt;<br>
              &gt; &lt;mglt&gt;<br>
              &gt; I tend to believe that phishing is now<br>
              &gt; (unfortunately) known by most users.<br>
              &gt; I have the impression that UI is always a<br>
              &gt; difficult problem, and I am wondering if such<br>
              &gt; recommendations are still valid or if that is<br>
              &gt; a legacy statement. I do not have strong<br>
              &gt; feeling about what to do, so I leave it to<br>
              &gt; you, but is interested in your opinion.<br>
              This text matches the original registration of the
              $Phishing keyword. I <br>
              have seen some modern email clients still following this
              advice, so I <br>
              think it is useful. Which part of it do you find outdated?</di=
v>
            <div class=3D"PlainText"><br>
            </div>
            <div class=3D"PlainText">&lt;mglt&gt;</div>
            <div class=3D"PlainText"><br>
            </div>
            <div class=3D"PlainText"><span style=3D"color: rgb(0, 0, 0);">Ju=
st
                to be clear that was just a comment. In the following
                sentence,=A0=A0</span><br>
            </div>
            <div class=3D"PlainText"><span style=3D"color:rgb(0, 0,
                0);background-color:rgb(255, 255, 255);display:inline
                !important">"""</span></div>
            <div class=3D"PlainText"><span style=3D"color:rgb(0, 0,
                0);background-color:rgb(255, 255, 255);display:inline
                !important">User agents should not use the term
                "phishing" in their warning</span><br>
              <span style=3D"color:rgb(0, 0, 0);background-color:rgb(255,
                255, 255);display:inline !important">message as most
                users do not understand this term.=A0<span>=A0</span></span>=
<br>
            </div>
            <div class=3D"PlainText"><span style=3D"color:rgb(0, 0,
                0);background-color:rgb(255, 255, 255);display:inline
                !important"><span>"""</span></span></div>
            <div class=3D"PlainText"><span style=3D"color:rgb(0, 0,
                0);background-color:rgb(255, 255, 255);display:inline
                !important"><span>I was questioning=A0 "<span
=20                   style=3D"background-color:rgb(255, 255,
                    255);display:inline !important">as most users do not
                    understand this term" and tend to believe that most
                    users have heard what phishing means. So I am
                    wondering if the user the message is being shown
                    does not translate to itself: "Oh yeah they mean
                    phishing".=A0 Again just some random thoughts from my
                    part.</span></span></span></div>
          </span></font></div>
    </blockquote>
    <font size=3D"2">Sorry, I was staring at this text so much that I
      stopped noticing it. Now that you pointed this out I think
      removing this sentence makes sense.</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt">
            <div class=3D"PlainText"><span style=3D"color:rgb(0, 0,
                0);background-color:rgb(255, 255, 255);display:inline
                !important"><span><span style=3D"background-color:rgb(255,
                    255, 255);display:inline !important"><br>
                  </span></span></span></div>
            <div class=3D"PlainText">&lt;/mglt&gt;</div>
          </span></font></div>
    </blockquote>
    =A0[snip]<br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt">
            <div class=3D"PlainText">&gt;<br>
              &gt; The section mentions that repeated attempts<br>
              &gt; for a password associated is detected,<br>
              &gt; somehow prevented. It may also worth<br>
              &gt; mentioning that with a large number of login<br>
              &gt; (known or guessed),<br>
              &gt; an attacker may try to guess a login<br>
              &gt; associated to a small number of commonly<br>
              &gt; known weak passwords ( password<br>
              &gt; spraying). I believe it might worth being<br>
              &gt; mentioned, that correlating failed attempts<br>
              &gt; worth also being mentioned.<br>
              Fair enough. Can you suggest some text?<br>
              <br>
            </div>
            <div class=3D"PlainText">&lt;mglt&gt;</div>
            <div class=3D"PlainText">Maybe something around these lines:</di=
v>
            <div class=3D"PlainText"><br>
            </div>
          </span></font>
        <div class=3D"PlainText">An IMAP server SHOULD report any
          authentication failure and analyze the attempt with regard to
          a password brute force attack as well as a password spraying
          attack. Accounts that matching password spraying attacks MUST
          be blocked and request to change their passwords and only
          password with significant strength SHOULD be accepted. <br>
        </div>
      </div>
    </blockquote>
    I edited this slightly. Thank you for the suggestion.<br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt"><i><b>
              </b></i>
            <div class=3D"PlainText">&lt;/mglt&gt;=A0</div>
            <div class=3D"PlainText"><br>
            </div>
            <div class=3D"PlainText">&gt; Maybe that goes a bit too far in
              the purpose<br>
              &gt; of recommendations, but it might may sense to<br>
              &gt; recommend strong random passwords used in<br>
              &gt; conjunction of passwords wallets or the use<br>
              &gt; of mutually authenticate TLS.<br>
              &gt;<br>
              &gt; &lt;/mglt&gt;<br>
              &gt;<br>
              &gt;<br>
              &gt; &lt;mglt&gt;<br>
              &gt; One question I would have - and with very<br>
              &gt; little opinion on it - is how vulnerable IMAP<br>
              &gt; parsing is to injection. I usually see the<br>
              &gt; use of JSON as a big advantage toward<br>
              &gt; this, but I would be happy to known<br>
              &gt; your opinion on it.<br>
              Can you give me an example, as I am not sure what do you
              mean by <br>
              injection in this case?</div>
            <div class=3D"PlainText"><br>
            </div>
            <div class=3D"PlainText">&lt;mglt&gt;</div>
            <div class=3D"PlainText">I do not have specific example in
              mind. My question was if there are known ways to inject
              some commands in a specific field or if some parsers
              checks have been relaxed to enable interoperability. <br>
            </div>
          </span></font></div>
    </blockquote>
    <font size=3D"2">I can't think of any. IMAP is either using
      octet-counted literals or strict syntax (LIST-like). Syntax is
      quite regular and easier than XML (IMHO).</font><br>
    <blockquote type=3D"cite"
cite=3D"mid:DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.pr=
od.outlook.com">
      <div class=3D"BodyFragment"><font size=3D"2"><span
            style=3D"font-size:11pt">
            <div class=3D"PlainText"><br>
            </div>
            <div class=3D"PlainText">&lt;/mglt&gt;</div>
            <div class=3D"PlainText"><br>
              &gt; I also have the impression that injections<br>
              &gt; can be performed via the web interface, so a<br>
              &gt; web front end should be carefully considered<br>
              &gt; and IMAP server may not believe they are<br>
              &gt; always immune behind a web front end and<br>
              &gt; still require to follow the best practises.<br>
              &gt;<br>
              &gt; &lt;/mglt&gt;<br>
              <br>
              Best Regards,<br>
              <br>
              Alexey<br>
              <br>
            </div>
          </span></font></div>
    </blockquote>
  </body>
</html>

--------------13083B1379C3450CCE4C04B9--


From nobody Wed Jan 20 10:22:24 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 8B0613A11B5; Wed, 20 Jan 2021 10:22:20 -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 WPrcfCDz8Vlh; Wed, 20 Jan 2021 10:22:18 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2049.outbound.protection.outlook.com [40.107.220.49]) (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 9B8893A11B6; Wed, 20 Jan 2021 10:22:17 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S0+igAr8foh6zqlVJV0oaLufXVBGCg4+Ud1Qc7umCL1644wyvWKyxBQwb38paQDbFBMqYVBNKapOAEmm0Ak17P6lFS72cXfAXM8iOK4+T7XFp0D2rjWNCO8OOSISKEeroKoGKtRUAqV2ahNj4BletJLLm7vI55uiKVHEnomWgb5a7FKNTo8O08Rl1LDuWxLC2FNHhKR9vu1iA8GDtpFQ79JiQu17KhFl7J7d0I/DvOoqGwUJiGYTuLqq9y0SNrk5tGtVEoN+qjCTHNbAIvJ67RV5u4kJz3qoMHV14i6IqcO6S+srmVIgSqPcewxUpt9ofvZQ+eNKMKLn7YaHLZePRQ==
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=MEO3CUHPFCpmt0LfX2T5d+4QiR0GEqXudOrTiEzGMD8=; b=eNqiI+TUjhE4kubK0UaYiD3BmR9I53oRZ7AndMNVzDhTaI98FvY/s/jC5W9Uf8Klk3SKh8rkrTrfTf/UPB6HLMG0AmHO07/qOnH5OaWtgouE7+sjEnIPnDyaZDS5NMvdNXrOs8TlP5PR+rrV3UYhclCtz3peGKQDnduYehPCT05fOtY9sBezOPpWmoI9CBx1Mys1VGO5Vk1pc6Eb0VpT4sVgc/E0AowfAmBstNL6c3QoJIJCpMyKCwSQw/5b3rplNmz2TWL7YcX3ON2H2YVMRnPARrEyg2FW/bZX5UJvudJH6o5QV7mG/2J1rsJ5oFBe7YwU/990LjV51tYYIxK+HA==
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=MEO3CUHPFCpmt0LfX2T5d+4QiR0GEqXudOrTiEzGMD8=; b=X0OphG7tLHyTeor0x7WG/8OYN2cVKcnTz9Cy5YU0dItaV79OcwyFk3G8qVK1DR5CmRtlsYfQao62WvoWhWaEmGfyAhtMlZan9UyjYIJDSaR+cu0yOmjxhmqlv4kheTDRqnINeV2qMQRfMpFUUwpE25ZcVoX8mioNEnLgtRxeUQQ=
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.3784.11; Wed, 20 Jan 2021 18:22:16 +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.3763.014; Wed, 20 Jan 2021 18:22:16 +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: AQHW7osBCZRYcejh/kaFOg7r/oDlOqovTFtxgAF6oICAAA4TNQ==
Date: Wed, 20 Jan 2021 18:22:16 +0000
Message-ID: <DM6PR15MB2379B58281E066E4523B1404E3A20@DM6PR15MB2379.namprd15.prod.outlook.com>
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com> <99082ebc-318b-5c4d-a9e6-b3893ab99c0d@isode.com> <DM6PR15MB2379AD34B141FD5015D25E86E3A30@DM6PR15MB2379.namprd15.prod.outlook.com>, <ecbc01e4-4a84-4a5b-e7be-e87c7897a01c@isode.com>
In-Reply-To: <ecbc01e4-4a84-4a5b-e7be-e87c7897a01c@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: fe2391ab-e7bb-4b04-7630-08d8bd7050cb
x-ms-traffictypediagnostic: DM6PR15MB4005:
x-microsoft-antispam-prvs: <DM6PR15MB400557148B4DB8F10FCED2FDE3A29@DM6PR15MB4005.namprd15.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: PFKxMv8WyveqjET9E0t0xwIqV287zDkocc/gX6CI9C/LBIz9JMlmRFy+PWGZR+nhamBqIo1Tos0flXFlA8qHJB6BRv9R78vERbwZERQmzuGMmdDQGAfvSXONXcN7Xg1AcwAEdRs0BKvmESgdH0ht/OzdJY6rrBmddwVC7SOVVjgkFxOVS5Z7CGbZ0cvVLeg7ul+L3PvV6cPFo+ql8iTKNLlspkvzeVSlHzt6qDRx9gwCKbf64G6E9Yibn+NgbgZtsLlj4IBKTz18nuVRoeEftqrICxIkcFSvK4aIdgyBR+QB7FtDIjXbmAe0G/b8TlLnr7yKD8oSpesLgQXEnry2bMrIpxTdrmEJ7HG+OqPvZnlxVB1p6RHQuSfErEdGFjG/vG3jnz02KpaPkLg/6qKUHA==
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)(136003)(376002)(346002)(366004)(396003)(39860400002)(54906003)(64756008)(19627405001)(52536014)(66476007)(66446008)(5660300002)(2906002)(7696005)(316002)(91956017)(26005)(33656002)(76116006)(44832011)(186003)(66946007)(8936002)(71200400001)(66556008)(83380400001)(9686003)(86362001)(55016002)(110136005)(8676002)(478600001)(53546011)(6506007)(4326008); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?Y3ndetPOyLqhXL0b+dGtwiXWJXyEVs52cJ1YLf5JedOBiXwluDcSCUpz/GUP?= =?us-ascii?Q?sIXuUlJiTl1N2RJN46G0uwJ7ZigT7MkHvuYDMjbfBLbFrda6sa0LEm1Ct4K2?= =?us-ascii?Q?Dg7seXFjMwnxW19+GRoamQTH0j0gDx/x95ZbZ6cQkyohFqaixT2NRZLUxHra?= =?us-ascii?Q?0HtfgxbDLnfURIt2tV0gpXPSez6TIuVM9c+PpFSvoDqvZRfqS8tv0TNaZt/0?= =?us-ascii?Q?qFlJFF34AJ24doTnegQhgZEewfkPSs491v4WpVaFMvUzQ5fhKZj9vR+Qn9OF?= =?us-ascii?Q?P5E+la12tv9oOszEJiRca35Qw634L15iQFtA0k0p3lqWYFl2morEWUy74ehr?= =?us-ascii?Q?wfnqHXRUudne8wsdhA1Duf0m79JXZ07JSJWGhERYvA54u9Qfwg+Px3MpemC/?= =?us-ascii?Q?OIcnpUAQI7/bH/dATFrLEoeixBrrKfKyTIp8kD1AnXQ6X4NWO+Q6oGnq5ztG?= =?us-ascii?Q?7+aopdhSvGAkJxvjI38NbzYm1NASbtKjpVUOkTkpdv6Bf45uMECrgOruclcg?= =?us-ascii?Q?D/Itjz1LaDeXUqAaMR7MqLbCYkAtbHxPyiiGhEkOvy3n/moD7Q0KHtEW1RAu?= =?us-ascii?Q?4XhnHRFHZaTJr/4aKrJ4Oe0lUrEy3OqWhfxK5I5uxY/iWNtyexnXvVlg2klE?= =?us-ascii?Q?5PZhpSpZFnM3fNZhMAuuSPcQwFHVvM07vDkI+E2WfQdUoT0FpaYmN8kQxkCr?= =?us-ascii?Q?LeRLBld2enDGZ2DCI1++gL9LTDnVpUlTWSjAVQ/0+kEzNrm0BwTzqD2tmdDn?= =?us-ascii?Q?LPHfiLYbelVKZ5Js8GW21jIPO+/N8RDqu4ZCRLKwVSTR79A7Sm2Ja43NuY1z?= =?us-ascii?Q?Nl0RA+W50JVN8X57MTQRb5hkOO37Bqp6Skgkj0WcdfizNxQ9RWNP9vnNpVVm?= =?us-ascii?Q?Pw3G7mnheITt6mvG+hQlRFtOpk6GtIY+eG0+1LCiw3mJgZ/8upPMg05CLMYa?= =?us-ascii?Q?H9JjUO6C0PX7nVNenJfby6QuOcxCHiygeKOa5tlJJBk=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR15MB2379B58281E066E4523B1404E3A20DM6PR15MB2379namp_"
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: fe2391ab-e7bb-4b04-7630-08d8bd7050cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jan 2021 18:22:16.1913 (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: qvc0XjKhL4fPpueZwekY7JnI1x+8qc8Bo0Dz9kCudO2nCRIsTuLDTo9j+moHaPNOWhy/BxJU3h60QOaxn6oOpEvU1+phxnV561eKBJ6ZAac=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB4005
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/9iIJuvztG97_6k-wH8mg18AScAY>
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: Wed, 20 Jan 2021 18:22:20 -0000

--_000_DM6PR15MB2379B58281E066E4523B1404E3A20DM6PR15MB2379namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the response!
Yours,
Daniel
________________________________
From: Alexey Melnikov <alexey.melnikov@isode.com>
Sent: Wednesday, January 20, 2021 12:31 PM
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 20:46, Daniel Migault wrote:
Hi Alexey,

Thanks for your response. Please find some clarifications/responses.
Thank you for the followup. My responses below.

Yours,
Daniel

________________________________
From: Alexey Melnikov <alexey.melnikov@isode.com><mailto:alexey.melnikov@is=
ode.com>
Sent: Tuesday, January 19, 2021 12:46 PM
To: Daniel Migault <daniel.migault@ericsson.com><mailto:daniel.migault@eric=
sson.com>; secdir@ietf.org<mailto:secdir@ietf.org> <secdir@ietf.org><mailto=
:secdir@ietf.org>
Cc: draft-ietf-extra-imap4rev2.all@ietf.org<mailto:draft-ietf-extra-imap4re=
v2.all@ietf.org> <draft-ietf-extra-imap4rev2.all@ietf.org><mailto:draft-iet=
f-extra-imap4rev2.all@ietf.org>; extra@ietf.org<mailto:extra@ietf.org> <ext=
ra@ietf.org><mailto:extra@ietf.org>; last-call@ietf.org<mailto:last-call@ie=
tf.org> <last-call@ietf.org><mailto:last-call@ietf.org>
Subject: Re: Secdir last call review of draft-ietf-extra-imap4rev2-24

Hi Daniel,

Thank you for your review. My replies below. I removed some of your
comments that I need to think a bit more and will reply to them separately.

On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:
> Reviewer: Daniel Migault
> Review result: Has Nits
>
 [snip]
>
> [ ... ]
>
>     $Phishing  The $Phishing keyword can be used by a delivery agent to
>        mark a message as highly likely to be a phishing email.  An email
>        that's determined to be a phishing email by the delivery agent
>        should also be considered a junk email and have the appropriate
>        junk filtering applied, including setting the $Junk flag and
>        placing in the \Junk special-use mailbox (see Section 7.2.3) if
>        available.
>        If both the $Phishing flag and the $Junk flag are set, the user
>        agent should display an additional warning message to the user.
>        User agents should not use the term "phishing" in their warning
>        message as most users do not understand this term.  Phrasing of
>        the form "this message may be trying to steal your personal
>        information" is recommended.  Additionally the user agent may
>        display a warning when clicking on any hyperlinks within the
>        message.
>
> <mglt>
> I tend to believe that phishing is now
> (unfortunately) known by most users.
> I have the impression that UI is always a
> difficult problem, and I am wondering if such
> recommendations are still valid or if that is
> a legacy statement. I do not have strong
> feeling about what to do, so I leave it to
> you, but is interested in your opinion.
This text matches the original registration of the $Phishing keyword. I
have seen some modern email clients still following this advice, so I
think it is useful. Which part of it do you find outdated?

<mglt>

Just to be clear that was just a comment. In the following sentence,
"""
User agents should not use the term "phishing" in their warning
message as most users do not understand this term.
"""
I was questioning  "as most users do not understand this term" and tend to =
believe that most users have heard what phishing means. So I am wondering i=
f the user the message is being shown does not translate to itself: "Oh yea=
h they mean phishing".  Again just some random thoughts from my part.
Sorry, I was staring at this text so much that I stopped noticing it. Now t=
hat you pointed this out I think removing this sentence makes sense.

</mglt>
 [snip]
>
> The section mentions that repeated attempts
> for a password associated is detected,
> somehow prevented. It may also worth
> mentioning that with a large number of login
> (known or guessed),
> an attacker may try to guess a login
> associated to a small number of commonly
> known weak passwords ( password
> spraying). I believe it might worth being
> mentioned, that correlating failed attempts
> worth also being mentioned.
Fair enough. Can you suggest some text?

<mglt>
Maybe something around these lines:

An IMAP server SHOULD report any authentication failure and analyze the att=
empt with regard to a password brute force attack as well as a password spr=
aying attack. Accounts that matching password spraying attacks MUST be bloc=
ked and request to change their passwords and only password with significan=
t strength SHOULD be accepted.
I edited this slightly. Thank you for the suggestion.
</mglt>

> Maybe that goes a bit too far in the purpose
> of recommendations, but it might may sense to
> recommend strong random passwords used in
> conjunction of passwords wallets or the use
> of mutually authenticate TLS.
>
> </mglt>
>
>
> <mglt>
> One question I would have - and with very
> little opinion on it - is how vulnerable IMAP
> parsing is to injection. I usually see the
> use of JSON as a big advantage toward
> this, but I would be happy to known
> your opinion on it.
Can you give me an example, as I am not sure what do you mean by
injection in this case?

<mglt>
I do not have specific example in mind. My question was if there are known =
ways to inject some commands in a specific field or if some parsers checks =
have been relaxed to enable interoperability.
I can't think of any. IMAP is either using octet-counted literals or strict=
 syntax (LIST-like). Syntax is quite regular and easier than XML (IMHO).

</mglt>

> I also have the impression that injections
> can be performed via the web interface, so a
> web front end should be carefully considered
> and IMAP server may not believe they are
> always immune behind a web front end and
> still require to follow the best practises.
>
> </mglt>

Best Regards,

Alexey


--_000_DM6PR15MB2379B58281E066E4523B1404E3A20DM6PR15MB2379namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<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);">
Thanks for the response!</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 id=3D"appendonsend"></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Alexey Melnikov &lt;a=
lexey.melnikov@isode.com&gt;<br>
<b>Sent:</b> Wednesday, January 20, 2021 12:31 PM<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>
<p>Hi Daniel,</p>
<p><br>
</p>
<div class=3D"x_moz-cite-prefix">On 19/01/2021 20:46, Daniel Migault wrote:=
<br>
</div>
<blockquote type=3D"cite"><style type=3D"text/css" style=3D"display:none">
<!--
p
	{margin-top:0;
	margin-bottom:0}
-->
</style>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
Hi Alexey,&nbsp;</div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
Thanks for your response. Please find some clarifications/responses. <br>
</div>
</blockquote>
Thank you for the followup. My responses below.<br>
<blockquote type=3D"cite">
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
Yours,&nbsp;<br>
Daniel</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"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Alexey Melnikov
<a class=3D"x_moz-txt-link-rfc2396E" href=3D"mailto:alexey.melnikov@isode.c=
om">&lt;alexey.melnikov@isode.com&gt;</a><br>
<b>Sent:</b> Tuesday, January 19, 2021 12:46 PM<br>
<b>To:</b> Daniel Migault <a class=3D"x_moz-txt-link-rfc2396E" href=3D"mail=
to:daniel.migault@ericsson.com">
&lt;daniel.migault@ericsson.com&gt;</a>; <a class=3D"x_moz-txt-link-abbrevi=
ated" href=3D"mailto:secdir@ietf.org">
secdir@ietf.org</a> <a class=3D"x_moz-txt-link-rfc2396E" href=3D"mailto:sec=
dir@ietf.org">
&lt;secdir@ietf.org&gt;</a><br>
<b>Cc:</b> <a class=3D"x_moz-txt-link-abbreviated" href=3D"mailto:draft-iet=
f-extra-imap4rev2.all@ietf.org">
draft-ietf-extra-imap4rev2.all@ietf.org</a> <a class=3D"x_moz-txt-link-rfc2=
396E" href=3D"mailto:draft-ietf-extra-imap4rev2.all@ietf.org">
&lt;draft-ietf-extra-imap4rev2.all@ietf.org&gt;</a>; <a class=3D"x_moz-txt-=
link-abbreviated" href=3D"mailto:extra@ietf.org">
extra@ietf.org</a> <a class=3D"x_moz-txt-link-rfc2396E" href=3D"mailto:extr=
a@ietf.org">
&lt;extra@ietf.org&gt;</a>; <a class=3D"x_moz-txt-link-abbreviated" href=3D=
"mailto:last-call@ietf.org">
last-call@ietf.org</a> <a class=3D"x_moz-txt-link-rfc2396E" href=3D"mailto:=
last-call@ietf.org">
&lt;last-call@ietf.org&gt;</a><br>
<b>Subject:</b> Re: Secdir last call review of draft-ietf-extra-imap4rev2-2=
4</font>
<div>&nbsp;</div>
</div>
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText">Hi Daniel,<br>
<br>
Thank you for your review. My replies below. I removed some of your <br>
comments that I need to think a bit more and will reply to them separately.=
<br>
<br>
On 19/01/2021 14:52, Daniel Migault via Datatracker wrote:<br>
&gt; Reviewer: Daniel Migault<br>
&gt; Review result: Has Nits<br>
&gt;<br>
</div>
</span></font></div>
</blockquote>
<font size=3D"2">&nbsp;[snip]</font><br>
<blockquote type=3D"cite">
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText">&gt;<br>
&gt; [ ... ]<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; $Phishing&nbsp; The $Phishing keyword can be u=
sed by a delivery agent to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mark a message as highly lik=
ely to be a phishing email.&nbsp; An email<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that's determined to be a ph=
ishing email by the delivery agent<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should also be considered a =
junk email and have the appropriate<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; junk filtering applied, incl=
uding setting the $Junk flag and<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; placing in the \Junk special=
-use mailbox (see Section 7.2.3) if<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If both the $Phishing flag a=
nd the $Junk flag are set, the user<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agent should display an addi=
tional warning message to the user.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User agents should not use t=
he term &quot;phishing&quot; in their warning<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message as most users do not=
 understand this term.&nbsp; Phrasing of<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the form &quot;this message =
may be trying to steal your personal<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information&quot; is recomme=
nded.&nbsp; Additionally the user agent may<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; display a warning when click=
ing on any hyperlinks within the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message.<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; I tend to believe that phishing is now<br>
&gt; (unfortunately) known by most users.<br>
&gt; I have the impression that UI is always a<br>
&gt; difficult problem, and I am wondering if such<br>
&gt; recommendations are still valid or if that is<br>
&gt; a legacy statement. I do not have strong<br>
&gt; feeling about what to do, so I leave it to<br>
&gt; you, but is interested in your opinion.<br>
This text matches the original registration of the $Phishing keyword. I <br=
>
have seen some modern email clients still following this advice, so I <br>
think it is useful. Which part of it do you find outdated?</div>
<div class=3D"x_PlainText"><br>
</div>
<div class=3D"x_PlainText">&lt;mglt&gt;</div>
<div class=3D"x_PlainText"><br>
</div>
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0)">Just to be clea=
r that was just a comment. In the following sentence,&nbsp;&nbsp;</span><br=
>
</div>
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0); background-colo=
r:rgb(255,255,255); display:inline!important">&quot;&quot;&quot;</span></di=
v>
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0); background-colo=
r:rgb(255,255,255); display:inline!important">User agents should not use th=
e term &quot;phishing&quot; in their warning</span><br>
<span style=3D"color:rgb(0,0,0); background-color:rgb(255,255,255); display=
:inline!important">message as most users do not understand this term.&nbsp;=
<span>&nbsp;</span></span><br>
</div>
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0); background-colo=
r:rgb(255,255,255); display:inline!important"><span>&quot;&quot;&quot;</spa=
n></span></div>
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0); background-colo=
r:rgb(255,255,255); display:inline!important"><span>I was questioning&nbsp;=
 &quot;<span style=3D"background-color:rgb(255,255,255); display:inline!imp=
ortant">as most users do not understand this term&quot;
 and tend to believe that most users have heard what phishing means. So I a=
m wondering if the user the message is being shown does not translate to it=
self: &quot;Oh yeah they mean phishing&quot;.&nbsp; Again just some random =
thoughts from my part.</span></span></span></div>
</span></font></div>
</blockquote>
<font size=3D"2">Sorry, I was staring at this text so much that I stopped n=
oticing it. Now that you pointed this out I think removing this sentence ma=
kes sense.</font><br>
<blockquote type=3D"cite">
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText"><span style=3D"color:rgb(0,0,0); background-colo=
r:rgb(255,255,255); display:inline!important"><span><span style=3D"backgrou=
nd-color:rgb(255,255,255); display:inline!important"><br>
</span></span></span></div>
<div class=3D"x_PlainText">&lt;/mglt&gt;</div>
</span></font></div>
</blockquote>
&nbsp;[snip]<br>
<blockquote type=3D"cite">
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText">&gt;<br>
&gt; The section mentions that repeated attempts<br>
&gt; for a password associated is detected,<br>
&gt; somehow prevented. It may also worth<br>
&gt; mentioning that with a large number of login<br>
&gt; (known or guessed),<br>
&gt; an attacker may try to guess a login<br>
&gt; associated to a small number of commonly<br>
&gt; known weak passwords ( password<br>
&gt; spraying). I believe it might worth being<br>
&gt; mentioned, that correlating failed attempts<br>
&gt; worth also being mentioned.<br>
Fair enough. Can you suggest some text?<br>
<br>
</div>
<div class=3D"x_PlainText">&lt;mglt&gt;</div>
<div class=3D"x_PlainText">Maybe something around these lines:</div>
<div class=3D"x_PlainText"><br>
</div>
</span></font>
<div class=3D"x_PlainText">An IMAP server SHOULD report any authentication =
failure and analyze the attempt with regard to a password brute force attac=
k as well as a password spraying attack. Accounts that matching password sp=
raying attacks MUST be blocked and
 request to change their passwords and only password with significant stren=
gth SHOULD be accepted.
<br>
</div>
</div>
</blockquote>
I edited this slightly. Thank you for the suggestion.<br>
<blockquote type=3D"cite">
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t"><i><b></b></i>
<div class=3D"x_PlainText">&lt;/mglt&gt;&nbsp;</div>
<div class=3D"x_PlainText"><br>
</div>
<div class=3D"x_PlainText">&gt; Maybe that goes a bit too far in the purpos=
e<br>
&gt; of recommendations, but it might may sense to<br>
&gt; recommend strong random passwords used in<br>
&gt; conjunction of passwords wallets or the use<br>
&gt; of mutually authenticate TLS.<br>
&gt;<br>
&gt; &lt;/mglt&gt;<br>
&gt;<br>
&gt;<br>
&gt; &lt;mglt&gt;<br>
&gt; One question I would have - and with very<br>
&gt; little opinion on it - is how vulnerable IMAP<br>
&gt; parsing is to injection. I usually see the<br>
&gt; use of JSON as a big advantage toward<br>
&gt; this, but I would be happy to known<br>
&gt; your opinion on it.<br>
Can you give me an example, as I am not sure what do you mean by <br>
injection in this case?</div>
<div class=3D"x_PlainText"><br>
</div>
<div class=3D"x_PlainText">&lt;mglt&gt;</div>
<div class=3D"x_PlainText">I do not have specific example in mind. My quest=
ion was if there are known ways to inject some commands in a specific field=
 or if some parsers checks have been relaxed to enable interoperability.
<br>
</div>
</span></font></div>
</blockquote>
<font size=3D"2">I can't think of any. IMAP is either using octet-counted l=
iterals or strict syntax (LIST-like). Syntax is quite regular and easier th=
an XML (IMHO).</font><br>
<blockquote type=3D"cite">
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText"><br>
</div>
<div class=3D"x_PlainText">&lt;/mglt&gt;</div>
<div class=3D"x_PlainText"><br>
&gt; I also have the impression that injections<br>
&gt; can be performed via the web interface, so a<br>
&gt; web front end should be carefully considered<br>
&gt; and IMAP server may not believe they are<br>
&gt; always immune behind a web front end and<br>
&gt; still require to follow the best practises.<br>
&gt;<br>
&gt; &lt;/mglt&gt;<br>
<br>
Best Regards,<br>
<br>
Alexey<br>
<br>
</div>
</span></font></div>
</blockquote>
</div>
</body>
</html>

--_000_DM6PR15MB2379B58281E066E4523B1404E3A20DM6PR15MB2379namp_--


From nobody Wed Jan 20 10:44:12 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 850D13A11E8; Wed, 20 Jan 2021 10:44:10 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161116825043.14636.11363330782678240238@ietfa.amsl.com>
Date: Wed, 20 Jan 2021 10:44:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/pbdVyGXYHFYb1nzMkmFH1vLJl-8>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-25.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, 20 Jan 2021 18:44:11 -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-25.txt
	Pages           : 167
	Date            : 2021-01-20

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-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


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 Fri Jan 22 20:57:25 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 E02E53A0C53; Fri, 22 Jan 2021 20:57:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Martin Duke 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: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
Date: Fri, 22 Jan 2021 20:57:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/DgfyWjscZragheI2AEWEFiajXls>
Subject: [Extra] Martin Duke's No Objection on draft-ietf-extra-imap4rev2-25: (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: Sat, 23 Jan 2021 04:57:24 -0000

Martin Duke has entered the following ballot position for
draft-ietf-extra-imap4rev2-25: 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:
----------------------------------------------------------------------

Various non-blocking questions/comments:

2.3.1.1 what would happen if the UID approached 2^32 due to a lifetime of spam
or something? The server can increment the validity value, but doesn’t that
make earlier email unreferenceable except via sequence number?

2.3.2 In the $Phishing definition, do you mean the user agent SHOULD (in caps)
display an additional warning message?

4.1.1 the last statement, “ the "*" value for a sequence number is not
permitted.”, is oddly placed, enough that it almost reads like a typo where you
meant UID. A clearer statement might be “The ‘*’ value is permitted for UIDs
but not sequence numbers.”




From nobody Sat Jan 23 19:14: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 57BA73A1114; Sat, 23 Jan 2021 19:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 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_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=fastmailteam.com header.b=EP068hNR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ES0jPjad
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 J7Nah2qDnkQP; Sat, 23 Jan 2021 19:14:52 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253953A1113; Sat, 23 Jan 2021 19:14:51 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 6A6F25C0120; Sat, 23 Jan 2021 22:14:50 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sat, 23 Jan 2021 22:14: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:cc:subject:content-type; s=fm1; bh=PhxZ orp8z7eneNic4cWTgFKFg4lsEdDTyeFfGqq1oNI=; b=EP068hNR8r4A1vFKKAxZ Vo4TLZG6ZVgLG8iIf1ULU4uX20FTD6jwYD0MZuaqhNR7x52eE58jajdcmYvlfP3j nnWgDipGCwEUH4dd9vYz31/ScWokTEYMQe/qcNIJ/wO9sIRd4ZLGBTfpkfFTMii7 s5TScNWfN9mYRPWY0w+1NmZSvSJRXUrZG2+1xY89I4+kN9sj/SptwrtF+Y7BdvgZ 463Je4Tudhfz7xVOhSkMlWfPcD5A1vwL6Su55pvIi7+IkPe+2MPitoMbB89g371O TSR52ti5DfepE/YVU6OubFbmzYMF5tAyRbf6brxBlX29mAPF60j84X+jJ6Ct6nhA Gw==
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=PhxZor p8z7eneNic4cWTgFKFg4lsEdDTyeFfGqq1oNI=; b=ES0jPjaduLJR1reIiiCPOV W3TkXDQsi+CUfaZ30WEsHZ2Ynb+1DiK/nZUvN94W5+GqF8m94naVdqSWt1PaxUsx TEYXD+odd70uInj5F8te8Yqg/POsaw9CT8CVxMOfFA4GPkqweY9hlOJQw7MGf195 hSDvdVcJmLObql6qVMa1at6r0KD3BrjFD3cDwEq/V5kqnPBejTOspjNSBYUrAinn aj0u6nBy02mCAJ39GXYmwDhYJAqzcueKyo+OT4hfFAE2bUVV5OrOWIhi+MP/okFc eQHSchq1w2leW5o4nfHE3ZZTMopNkrl8tHJIEKcZz54VS/AIr96OxmnW1g4v5iJw ==
X-ME-Sender: <xms:KuYMYL3_SPEMp49384EihyEvUsp0HA1viwnmKmmQ4rF2q-k1t8pkRA> <xme:KuYMYKHNCkKbLlnIj8G5pHQ_lSrWLy70ueTs-oPcER3wFyi-G40OwJqa3cTRxzDit ubBvLM75_U>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelgdehiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeetvdejvdffudetleefteetgfegkefffffgkeeugfeijeei hfejteffvedtvddttdenucffohhmrghinhepihgrnhgrrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:KuYMYL6LJPkaJ3Aq4PPMbM3lFnBpNOSP5Da0JGH3Vw3-Cir5fJZmdw> <xmx:KuYMYA2gJ8b7R49yf6LpHg9fReXUMWeRLrWbnRGvJp1qzoesoMqikQ> <xmx:KuYMYOGX6gZj1P3-R_nFvdOXvmJEAv1qQO9Gegi07y71DK2AmTDkYg> <xmx:KuYMYDRg4gdi4qbPFloVC987YhO-ZeaGeg2PNiXGkdVqHSXopP4wYQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F0D9B36005C; Sat, 23 Jan 2021 22:14:49 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com>
In-Reply-To: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
References: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
Date: Sun, 24 Jan 2021 14:14:28 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Martin Duke" <martin.h.duke@gmail.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=2a23ac5a6cb74bbc91c6078df482e500
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/awjar_gNmWp9N8JTY3BwgCQ4HW0>
Subject: Re: [Extra]  =?utf-8?q?Martin_Duke=27s_No_Objection_on_draft-ietf-ext?= =?utf-8?q?ra-imap4rev2-25=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: Sun, 24 Jan 2021 03:14:54 -0000

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

On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:

(I know the answers to these!)

> 2.3.1.1 what would happen if the UID approached 2^32 due to a lifetime=
 of spam
> or something? The server can increment the validity value, but doesn=E2=
=80=99t that
> make earlier email unreferenceable except via sequence number?

Sequence number is even less persistent - but when you increment the UID=
VALIDITY you can renumber the UIDs for everything, so you'd just start a=
t 1 and reid all the existing records.  So they'll be referenceable by t=
heir new UIDs next time the mailbox is selected.

And (plug) if the server implements RFC8474 (object ids) then a client c=
an even tell that it's the same email and not need to fetch the content =
again, even after a UIDVALIDITY change.

> 2.3.2 In the $Phishing definition, do you mean the user agent SHOULD (=
in caps)
> display an additional warning message?

This definition is copied from the IANA registry for keywords:

https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishing-te=
mplate

I'm not sure there's any point in changing the text to be different from=
 the IANA registration just to make it capital SHOULD.  It's unlikely to=
 change anybody's behaviour on reading this document.

> 4.1.1 the last statement, =E2=80=9C the "*" value for a sequence numbe=
r is not
> permitted.=E2=80=9D, is oddly placed, enough that it almost reads like=
 a typo where you
> meant UID. A clearer statement might be =E2=80=9CThe =E2=80=98*=E2=80=99=
 value is permitted for UIDs
> but not sequence numbers.=E2=80=9D

No, that would be an incorrect statement.  The phrase "UID set" is a def=
initional term which means:

* a sequence set;
* that references UIDs, not message numbers; and
* that consists only of numbers, not the magic '*' character (which can =
change value as new messages arrive)

You can have a "sequence set" which references UIDs and does contain '*'=
, but then it's not a "UID set" any more by definition.

Cheers,

Bron.

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


--2a23ac5a6cb74bbc91c6078df482e500
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;">On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracke=
r wrote:<br></div><div style=3D"font-family:Arial;"><br></div><div style=
=3D"font-family:Arial;">(I know the answers to these!)<br></div><div sty=
le=3D"font-family:Arial;"><br></div><blockquote type=3D"cite" id=3D"qt" =
style=3D""><div style=3D"font-family:Arial;">2.3.1.1 what would happen i=
f the UID approached 2^32 due to a lifetime of spam<br></div><div style=3D=
"font-family:Arial;">or something? The server can increment the validity=
 value, but doesn=E2=80=99t that<br></div><div style=3D"font-family:Aria=
l;">make earlier email unreferenceable except via sequence number?<br></=
div></blockquote><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">Sequence number is even less persistent - but when =
you increment the UIDVALIDITY you can renumber the UIDs for everything, =
so you'd just start at 1 and reid all the existing records.&nbsp; So the=
y'll be referenceable by their new UIDs next time the mailbox is selecte=
d.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fo=
nt-family:Arial;">And (plug) if the server implements RFC8474 (object id=
s) then a client can even tell that it's the same email and not need to =
fetch the content again, even after a UIDVALIDITY change.<br></div><div =
style=3D"font-family:Arial;"><br></div><blockquote type=3D"cite" id=3D"q=
t" style=3D""><div style=3D"font-family:Arial;">2.3.2 In the $Phishing d=
efinition, do you mean the user agent SHOULD (in caps)<br></div><div sty=
le=3D"font-family:Arial;">display an additional warning message?<br></di=
v></blockquote><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">This definition is copied from the IANA registry fo=
r keywords:<br></div><div style=3D"font-family:Arial;"><br></div><div st=
yle=3D"font-family:Arial;"><a href=3D"https://www.iana.org/assignments/i=
map-jmap-keywords/phishing/phishing-template">https://www.iana.org/assig=
nments/imap-jmap-keywords/phishing/phishing-template</a><br></div><div s=
tyle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">=
I'm not sure there's any point in changing the text to be different from=
 the IANA registration just to make it capital SHOULD.&nbsp; It's unlike=
ly to change anybody's behaviour on reading this document.<br></div><div=
 style=3D"font-family:Arial;"><br></div><blockquote type=3D"cite" id=3D"=
qt" style=3D""><div style=3D"font-family:Arial;">4.1.1 the last statemen=
t, =E2=80=9C the "*" value for a sequence number is not<br></div><div st=
yle=3D"font-family:Arial;">permitted.=E2=80=9D, is oddly placed, enough =
that it almost reads like a typo where you<br></div><div style=3D"font-f=
amily:Arial;">meant UID. A clearer statement might be =E2=80=9CThe =E2=80=
=98*=E2=80=99 value is permitted for UIDs<br></div><div style=3D"font-fa=
mily:Arial;">but not sequence numbers.=E2=80=9D<br></div></blockquote><d=
iv id=3D"sig56629417"><div class=3D"signature"><br></div><div style=3D"f=
ont-family:Arial;">No, that would be an incorrect statement.&nbsp; The p=
hrase "UID set" is a definitional term which means:<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">* a seq=
uence set;<br></div><div style=3D"font-family:Arial;">* that references =
UIDs, not message numbers; and<br></div><div style=3D"font-family:Arial;=
">* that consists only of numbers, not the magic '*' character (which ca=
n change value as new messages arrive)<br></div><div style=3D"font-famil=
y:Arial;"><br></div><div style=3D"font-family:Arial;">You can have a "se=
quence set" which references UIDs and does contain '*', but then it's no=
t a "UID set" any more by definition.<br></div><div style=3D"font-family=
:Arial;"><br></div><div style=3D"font-family:Arial;">Cheers,<br></div><d=
iv style=3D"font-family:Arial;"><br>Bron.<br></div><div style=3D"font-fa=
mily:Arial;"><br></div><div style=3D"font-family:Arial;">--<br></div><di=
v class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></d=
iv><div class=3D"signature">&nbsp; brong@fastmailteam.com<br></div><div =
class=3D"signature"><br></div></div><div style=3D"font-family:Arial;"><b=
r></div></body></html>
--2a23ac5a6cb74bbc91c6078df482e500--


From nobody Sun Jan 24 04:27:08 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 5062F3A0BC7 for <extra@ietfa.amsl.com>; Sun, 24 Jan 2021 04:27:06 -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, 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.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 5RuCKQ7ICDWc for <extra@ietfa.amsl.com>; Sun, 24 Jan 2021 04:27:04 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id B7EB73A0BC2 for <extra@ietf.org>; Sun, 24 Jan 2021 04:27:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611491223; d=isode.com; s=june2016; i=@isode.com; bh=fV31kqYFjlcQcJ1nm5RbVMDhEjgM/+UpLMY+/sMpv2I=; 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=uOb17WvbZ3YTvv1NQg7UQLT1jGbFl8ERDIqLNy5YqA9uPc2YwWWq4011gt+6ylWaV+tdYM rQJYyri2gabVJng2qaMmebxeVq3XURHiMJpu6aeWuPgHURUlUJRorQiC0ZVrC34niFZf1C XaP5bCm9fm9Yjl6p8R2PI/IV7QEzQ7k=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YA1nlgAuQVKo@waldorf.isode.com>; Sun, 24 Jan 2021 12:27:03 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: extra@ietf.org
References: <CAL0qLwaLa+PuGWRrKTbpmDa_SWKT9ZQUEQ9dsPgXfUmTzcYAYw@mail.gmail.com> <bb662e64-626c-914b-de59-f85ef18ee5e3@isode.com> <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
Message-ID: <5f5be9be-347b-52c3-399d-37c731f0be59@isode.com>
Date: Sun, 24 Jan 2021 12:27:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
In-Reply-To: <CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=YhWT-A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------54EFE22022E4341279B906E7"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/FrbOLZNnNIqGKpE7ezOFAYSYi3U>
Subject: Re: [Extra] AD Review of draft-ietf-extra-imap4rev2
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: Sun, 24 Jan 2021 12:27:06 -0000

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

Hi Murray,

Following up on a few little things:

On 04/01/2021 17:21, Murray S. Kucherawy wrote:

> On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov=20
> <alexey.melnikov@isode.com <mailto:alexey.melnikov@isode.com>> wrote:
>
 =C2=A0[snip]

>
>>
>>     Section 6.3.9.2
>>
>>
>>     This section (and the previous) require that \Subscribed be
>>     computed accurately before the response is generated.=C2=A0 How does
>>     this square with the text in Section 6.3.9 that insists replies
>>     come quickly?
>>
>     You have to comply with both :-). It is quite important for
>     \Subscribed to be accurate, so implementations need to do that
>     while maintaining reasonable performance.
>
>
> OK.=C2=A0 I just wanted to make sure the reader isn't getting "You MUST be=
=20
> fast!" from one direction while also doing "You MUST do all this=20
> expensive stuff!" from the other with no guidance about how to resolve=20
> this.
I will clarify this in the next version.
>
>     [snip]
>>
>>     The second paragraph also gets into the presentation of the
>>     reply.=C2=A0 This is human factors stuff the IETF tends to avoid.=C2=
=A0 Are
>>     we sure it belongs here?
>>
>     This is copy of the text from another RFC and I personally found
>     this text to be useful when implementing.
>
>
> You might consider putting these presentation advice paragraphs into=20
> an appendix too.

Due to a similar comment in SecDir review, I now removed the offending=20
text. I think this should address your comment.

Best Regards,

Alexey


--------------54EFE22022E4341279B906E7
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 Murray,</p>
    <p>Following up on a few little things:<br>
    </p>
    <p>On 04/01/2021 17:21, Murray S. Kucherawy wrote:<br>
    </p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div>
        <div dir=3D"ltr">On Mon, Jan 4, 2021 at 6:05 AM Alexey Melnikov
          &lt;<a href=3D"mailto:alexey.melnikov@isode.com"
            moz-do-not-send=3D"true">alexey.melnikov@isode.com</a>&gt;
          wrote:</div>
        <br>
      </div>
    </blockquote>
    <p><font size=3D"2">=C2=A0[snip]</font></p>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div><br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">Section 6.3.9.2</span></font></p>
                    <font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">This section (and the previous) require that \Subscribed be computed =
accurately before the response is generated.=C2=A0 How does this square with=
 the text in Section 6.3.9 that insists replies come quickly?</span></font><=
/p>
                  </div>
                </div>
              </blockquote>
              <font size=3D"2">You</font> have to comply with both :-). It
              is quite important for \Subscribed to be accurate, so
              implementations need to do that while maintaining
              reasonable performance.</div>
          </blockquote>
          <div><br>
          </div>
          <div>OK.=C2=A0 I just wanted to make sure the reader isn't getting
            "You MUST be fast!" from one direction while also doing "You
            MUST do all this expensive stuff!" from the other with no
            guidance about how to resolve this. <br>
          </div>
        </div>
      </div>
    </blockquote>
    I will clarify this in the next version.<br>
    <blockquote type=3D"cite"
cite=3D"mid:CAL0qLwYXht2r_83PCZo6+tJUJAoYCd0EoGyCHm6BQEQ=3DYhWT-A@mail.gmail=
.com">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div> </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"> [snip]<br>
            <div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><font size=3D"2"><br>
                    </font>
                    <p dir=3D"ltr"
                      style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><font
                        size=3D"2"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font=
-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">The second paragraph also gets into the presentation of the reply.=C2=
=A0 This is human factors stuff the IETF tends to avoid.=C2=A0 Are we sure i=
t belongs here?</span></font></p>
                  </div>
                </div>
              </blockquote>
              <font size=3D"2">This is copy of the text from another RFC
                and I personally found this text to be useful when
                implementing.</font></div>
          </blockquote>
          <div><br>
          </div>
          <div>You might consider putting these presentation advice
            paragraphs into an appendix too.</div>
        </div>
      </div>
    </blockquote>
    <p>Due to a similar comment in SecDir review, I now removed the
      offending text. I think this should address your comment.<br>
    </p>
    <p>Best Regards,</p>
    <p>Alexey<br>
    </p>
  </body>
</html>

--------------54EFE22022E4341279B906E7--


From nobody Sun Jan 24 04:51: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 492AD3A089C; Sun, 24 Jan 2021 04:50:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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.262, 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 YfPsowWVfAMZ; Sun, 24 Jan 2021 04:50:57 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id D60403A0888; Sun, 24 Jan 2021 04:50:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611492655; d=isode.com; s=june2016; i=@isode.com; bh=ienI35VtEv8fFBs7TNGn3YZFAHRFCz3wcCRGaGJMmHY=; 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=fKy1vyUNOFSE9ZliMps4hkpaf4BdaU0Et90l2WXhRsvi5cd3bf2Bm7UAwwI813K7TmMru8 Qp1/Tfvo7JBd7sxPCmdnQjD9jXbLvplwUFenTbX6Co396ws8y04Y73vlEQKfHZsSeWXHTW LW0EhLMsvZjg4wZRTBFmXIeElaM9N+Y=;
Received: from [192.168.0.5] (4e697ac1.skybroadband.com [78.105.122.193])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YA1tLwAuQVe4@waldorf.isode.com>; Sun, 24 Jan 2021 12:50:55 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Daniel Migault <daniel.migault@ericsson.com>, secdir@ietf.org
Cc: draft-ietf-extra-imap4rev2.all@ietf.org, extra@ietf.org, last-call@ietf.org
References: <161106792581.26552.4563982290675643872@ietfa.amsl.com>
Message-ID: <180cc9c6-f438-f05d-741c-f250024738db@isode.com>
Date: Sun, 24 Jan 2021 12:50:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
In-Reply-To: <161106792581.26552.4563982290675643872@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/E5eQWyTIHIwpKiElBe9Y4HQ6wEo>
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: Sun, 24 Jan 2021 12:50:58 -0000

Hi Daniel,

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

 =C2=A0[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=20
how to use DANE with email clients (an alternative/update to RFC 7817)=20
and I am not aware of any client implementations that use DANE=20
experimentally for this.

Best Regards,

Alexey


From nobody Sun Jan 24 04:59:24 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 AFB363A094E; Sun, 24 Jan 2021 04:59:21 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: extra@ietf.org
Message-ID: <161149316157.25371.18168652114347139515@ietfa.amsl.com>
Date: Sun, 24 Jan 2021 04:59:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/zA-vDwuk-jdO8K8nMD8jvmnXJzY>
Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-26.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: Sun, 24 Jan 2021 12:59:22 -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-26.txt
	Pages           : 168
	Date            : 2021-01-24

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-26
https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26

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


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 Jan 24 13:14:33 2021
Return-Path: <martin.h.duke@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 85B933A0B16; Sun, 24 Jan 2021 13:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 WM370OsuCiM8; Sun, 24 Jan 2021 13:14:29 -0800 (PST)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 6DFF93A0B12; Sun, 24 Jan 2021 13:14:29 -0800 (PST)
Received: by mail-io1-xd2a.google.com with SMTP id u8so9531635ior.13; Sun, 24 Jan 2021 13:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qwy8DunQMS5hD6SKr3NyecHbqKcQeSeL0tJfNyoDkVo=; b=t7UW6P1VzMLpv9hDWeIoD1IzD4PQBVWgaOlotv8+XYUFGAyyAMk6Yv9NT7IBKhKsVs PdhHpz1UtZw1T0GQjZp7cLqj4mKb51dqWbNTojHxc+mygTLhNLNnksaXRNenDuiYwXms +vIYx3ueaT18kULW7WYlJhC6SHpRQM5q3FSORK2mLZ5UI9fNWO6IXs2vaPNWSI//fRpJ LszE9+V3frwup0nZSWBXOP9LN1P9bCixSYo9CpH0uUrhlm/siS9OKngV4Wn9F4fy7WPr sib7EfoiWBWjB/vHLVWvSwkmU8eykQ/G3bERRdx+ddoWh1B6/SbZ9DtlY179AcW8OqE4 NcMQ==
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=Qwy8DunQMS5hD6SKr3NyecHbqKcQeSeL0tJfNyoDkVo=; b=HgLZtInuPUmiESWMFcEHXL8FvNwTBQ1OG6TK4w00eI6V2ykxiBj36SGK1e6ubxTTia 06KGuC5ZTaxeXiguGd8QEfJ9pOYT3P+7+2CmVcLO6MQhXXCeN9jf7nzOCLuMiHverKLW eiNJHRGjru44MMZurhxBd/NabvM5TX51JxfF2GBRjrAS/+9hP7xma9hUdPw4UjgTwVEw IkxUjAGR7LFGInL9DijFnrGVRoiNYV3GbmqOmUPuOKm/WMdEJhnS7Ve9gbLbcnU8PDJk ximz2Zs3hlvtR0In0zS1DK5lvQLitD01YJrFcZR2F14f4Ke4XT1QU1HlWHSJy+G3sKyM wtsA==
X-Gm-Message-State: AOAM530+IIHIkXtlhkqiPj7AA42hmLZ7GqGSrSva96g8MI/jle1m1PW0 ZQG0U7EEjwZzGx98dDYK2BNhlSjSOayjAV4ca5Kb4yMgddMVzQ==
X-Google-Smtp-Source: ABdhPJzjJJxY+ASi24METnySvvPtkpiea2mZCXm2ag+PAnU1Yeg/vH2kEojIJrsIFP8OVM5wAxjizEXF/c985g4zRbk=
X-Received: by 2002:a02:5889:: with SMTP id f131mr156386jab.121.1611522868491;  Sun, 24 Jan 2021 13:14:28 -0800 (PST)
MIME-Version: 1.0
References: <161137784334.20615.12096399788075509949@ietfa.amsl.com> <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com>
In-Reply-To: <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Sun, 24 Jan 2021 13:14:18 -0800
Message-ID: <CAM4esxS07JxMAQnfOOASxAZd3PvT=_GZpYE=P9i8d9nzpwmN=w@mail.gmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-extra-imap4rev2@ietf.org,  extra-chairs@ietf.org, extra@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001fbdcb05b9abe86b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/z8K9KRKbrvu5eCg7qxcL6v1Q8Ec>
Subject: Re: [Extra] Martin Duke's No Objection on draft-ietf-extra-imap4rev2-25: (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: Sun, 24 Jan 2021 21:14:32 -0000

--0000000000001fbdcb05b9abe86b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Bron,

Your replies make sense, but one:

Regarding 4.1.1, I find this terminology confusing, overloading the word
"sequence", although at this stage maybe it can't be helped. Still, this
section still seems very unclear to me.

4.1.1 <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#=
section-4.1.1>.
Sequence set and UID set

   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See Section
9 <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#sect=
ion-9>
   for details.  Sequence sets can contain ranges (e.g. "5:50"), an
   enumeration of specific message/UID numbers, a special symbol "*", or
   a combination of the above.

   A "UID set" is similar to the sequence set of unique identifiers;
   however, the "*" value for a sequence number is not permitted.

So if I got this right, there's a "sequence set" that contains either
sequence numbers or UIDs and can contain "*".
then there is also a "UID Set" which is UID only, and cannot contain "*".
But then I have two questions:
(1) Can a sequence set have a combination of sequence numbers and UIDs (" a
combination of the above")?
(2) If a UID set can't have sequence numbers, then why is it explaining the
lack of "*" in the context of UID sets with sequence numbers?

On Sat, Jan 23, 2021 at 7:14 PM Bron Gondwana <brong@fastmailteam.com>
wrote:

> On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:
>
> (I know the answers to these!)
>
> 2.3.1.1 what would happen if the UID approached 2^32 due to a lifetime of
> spam
> or something? The server can increment the validity value, but doesn=E2=
=80=99t that
> make earlier email unreferenceable except via sequence number?
>
>
> Sequence number is even less persistent - but when you increment the
> UIDVALIDITY you can renumber the UIDs for everything, so you'd just start
> at 1 and reid all the existing records.  So they'll be referenceable by
> their new UIDs next time the mailbox is selected.
>
> And (plug) if the server implements RFC8474 (object ids) then a client ca=
n
> even tell that it's the same email and not need to fetch the content agai=
n,
> even after a UIDVALIDITY change.
>
> 2.3.2 In the $Phishing definition, do you mean the user agent SHOULD (in
> caps)
> display an additional warning message?
>
>
> This definition is copied from the IANA registry for keywords:
>
>
> https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishing-tem=
plate
>
> I'm not sure there's any point in changing the text to be different from
> the IANA registration just to make it capital SHOULD.  It's unlikely to
> change anybody's behaviour on reading this document.
>
> 4.1.1 the last statement, =E2=80=9C the "*" value for a sequence number i=
s not
> permitted.=E2=80=9D, is oddly placed, enough that it almost reads like a =
typo
> where you
> meant UID. A clearer statement might be =E2=80=9CThe =E2=80=98*=E2=80=99 =
value is permitted for
> UIDs
> but not sequence numbers.=E2=80=9D
>
>
> No, that would be an incorrect statement.  The phrase "UID set" is a
> definitional term which means:
>
> * a sequence set;
> * that references UIDs, not message numbers; and
> * that consists only of numbers, not the magic '*' character (which can
> change value as new messages arrive)
>
> You can have a "sequence set" which references UIDs and does contain '*',
> but then it's not a "UID set" any more by definition.
>
> Cheers,
>
> Bron.
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
>
>
>

--0000000000001fbdcb05b9abe86b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Thanks Bron,</div><div><br></div><di=
v>Your replies make sense, but one:<br></div><div><br></div><div>Regarding =
4.1.1, I find this terminology confusing, overloading the word &quot;sequen=
ce&quot;, although at this stage maybe it can&#39;t be helped. Still, this =
section still seems very unclear to me.<br></div><div><br></div><div>
<pre class=3D"gmail-newpage"><span class=3D"gmail-h4"><a class=3D"gmail-sel=
flink" id=3D"gmail-section-4.1.1" href=3D"https://datatracker.ietf.org/doc/=
html/draft-ietf-extra-imap4rev2-26#section-4.1.1">4.1.1</a>.  Sequence set =
and UID set</span>

   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See <a href=3D"h=
ttps://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#section-=
9">Section 9</a>
   for details.  Sequence sets can contain ranges (e.g. &quot;5:50&quot;), =
an
   enumeration of specific message/UID numbers, a special symbol &quot;*&qu=
ot;, or
   a combination of the above.

   A &quot;UID set&quot; is similar to the sequence set of unique identifie=
rs;
   however, the &quot;*&quot; value for a sequence number is not permitted.=
</pre>

</div></div><div>So if I got this right, there&#39;s a &quot;sequence set&q=
uot; that contains either sequence numbers or UIDs and can contain &quot;*&=
quot;. <br></div><div>then there is also a &quot;UID Set&quot; which is UID=
 only, and cannot contain &quot;*&quot;. But then I have two questions:</di=
v><div>(1) Can a sequence set have a combination of sequence numbers and UI=
Ds (&quot; a combination of the above&quot;)?</div><div>(2) If a UID set ca=
n&#39;t have sequence numbers, then why is it explaining the lack of &quot;=
*&quot; in the context of UID sets with sequence numbers?<br></div><div><br=
></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Sat, Jan 23, 2021 at 7:14 PM Bron Gondwana &lt;<a href=3D"mailto:brong@fast=
mailteam.com">brong@fastmailteam.com</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><u></u><div><div style=3D"font-family:A=
rial">On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:<br=
></div><div style=3D"font-family:Arial"><br></div><div style=3D"font-family=
:Arial">(I know the answers to these!)<br></div><div style=3D"font-family:A=
rial"><br></div><blockquote type=3D"cite" id=3D"gmail-m_6628427668922159651=
qt"><div style=3D"font-family:Arial">2.3.1.1 what would happen if the UID a=
pproached 2^32 due to a lifetime of spam<br></div><div style=3D"font-family=
:Arial">or something? The server can increment the validity value, but does=
n=E2=80=99t that<br></div><div style=3D"font-family:Arial">make earlier ema=
il unreferenceable except via sequence number?<br></div></blockquote><div s=
tyle=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">Seque=
nce number is even less persistent - but when you increment the UIDVALIDITY=
 you can renumber the UIDs for everything, so you&#39;d just start at 1 and=
 reid all the existing records.=C2=A0 So they&#39;ll be referenceable by th=
eir new UIDs next time the mailbox is selected.<br></div><div style=3D"font=
-family:Arial"><br></div><div style=3D"font-family:Arial">And (plug) if the=
 server implements RFC8474 (object ids) then a client can even tell that it=
&#39;s the same email and not need to fetch the content again, even after a=
 UIDVALIDITY change.<br></div><div style=3D"font-family:Arial"><br></div><b=
lockquote type=3D"cite" id=3D"gmail-m_6628427668922159651qt"><div style=3D"=
font-family:Arial">2.3.2 In the $Phishing definition, do you mean the user =
agent SHOULD (in caps)<br></div><div style=3D"font-family:Arial">display an=
 additional warning message?<br></div></blockquote><div style=3D"font-famil=
y:Arial"><br></div><div style=3D"font-family:Arial">This definition is copi=
ed from the IANA registry for keywords:<br></div><div style=3D"font-family:=
Arial"><br></div><div style=3D"font-family:Arial"><a href=3D"https://www.ia=
na.org/assignments/imap-jmap-keywords/phishing/phishing-template" target=3D=
"_blank">https://www.iana.org/assignments/imap-jmap-keywords/phishing/phish=
ing-template</a><br></div><div style=3D"font-family:Arial"><br></div><div s=
tyle=3D"font-family:Arial">I&#39;m not sure there&#39;s any point in changi=
ng the text to be different from the IANA registration just to make it capi=
tal SHOULD.=C2=A0 It&#39;s unlikely to change anybody&#39;s behaviour on re=
ading this document.<br></div><div style=3D"font-family:Arial"><br></div><b=
lockquote type=3D"cite" id=3D"gmail-m_6628427668922159651qt"><div style=3D"=
font-family:Arial">4.1.1 the last statement, =E2=80=9C the &quot;*&quot; va=
lue for a sequence number is not<br></div><div style=3D"font-family:Arial">=
permitted.=E2=80=9D, is oddly placed, enough that it almost reads like a ty=
po where you<br></div><div style=3D"font-family:Arial">meant UID. A clearer=
 statement might be =E2=80=9CThe =E2=80=98*=E2=80=99 value is permitted for=
 UIDs<br></div><div style=3D"font-family:Arial">but not sequence numbers.=
=E2=80=9D<br></div></blockquote><div id=3D"gmail-m_6628427668922159651sig56=
629417"><div><br></div><div style=3D"font-family:Arial">No, that would be a=
n incorrect statement.=C2=A0 The phrase &quot;UID set&quot; is a definition=
al term which means:<br></div><div style=3D"font-family:Arial"><br></div><d=
iv style=3D"font-family:Arial">* a sequence set;<br></div><div style=3D"fon=
t-family:Arial">* that references UIDs, not message numbers; and<br></div><=
div style=3D"font-family:Arial">* that consists only of numbers, not the ma=
gic &#39;*&#39; character (which can change value as new messages arrive)<b=
r></div><div style=3D"font-family:Arial"><br></div><div style=3D"font-famil=
y:Arial">You can have a &quot;sequence set&quot; which references UIDs and =
does contain &#39;*&#39;, but then it&#39;s not a &quot;UID set&quot; any m=
ore by definition.<br></div><div style=3D"font-family:Arial"><br></div><div=
 style=3D"font-family:Arial">Cheers,<br></div><div style=3D"font-family:Ari=
al"><br>Bron.<br></div><div style=3D"font-family:Arial"><br></div><div styl=
e=3D"font-family:Arial">--<br></div><div>=C2=A0 Bron Gondwana, CEO, Fastmai=
l Pty Ltd<br></div><div>=C2=A0 <a href=3D"mailto:brong@fastmailteam.com" ta=
rget=3D"_blank">brong@fastmailteam.com</a><br></div><div><br></div></div><d=
iv style=3D"font-family:Arial"><br></div></div></blockquote></div></div>

--0000000000001fbdcb05b9abe86b--


From nobody Sun Jan 24 15:01:27 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 1885A3A0CC1 for <extra@ietfa.amsl.com>; Sun, 24 Jan 2021 15:01:26 -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, 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=htf5JCOo; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IgnIAnqa
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 N2kdXUcaBHF7 for <extra@ietfa.amsl.com>; Sun, 24 Jan 2021 15:01:24 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBE1F3A0CBE for <extra@ietf.org>; Sun, 24 Jan 2021 15:01:23 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 00FD92B8; Sun, 24 Jan 2021 18:01:22 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 24 Jan 2021 18:01:23 -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=i/tt On0IGPR4xQmXxQw0xpIScN30jhyBYUNGONHg4Ic=; b=htf5JCOo3RB4RV1yRmdF RG1J/myzd/SmJQCgf1Pw6ZqskoMz4WaKifhS6JW/1umlYAbbYXtHi61ycdE0TeRZ CsYcRn2m/5kdQvzPpvnAFim9MWaALpsAMTYBXuYRZ96DKavCANsxyljGcDuL/zTh HGuDh5i/cCYQYpLHAJcAZ9+awNz02BLAAOHrkEzxIUaOjFrUMEQ63wei79DqkoTq 6MtCQWnT+BXufpNQVw7P/bwIx9D7kLy1kG6RvgJmSyxGzDL7AIAzVQ702qGGag3R eXUPuq1nWiEtPo4RwnQnmei/e2QjvwRXoUy+NtMilGM/Ag2ba1HS4MjSgNUwd+at pw==
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=i/ttOn 0IGPR4xQmXxQw0xpIScN30jhyBYUNGONHg4Ic=; b=IgnIAnqadx8/UuyAP+iyQj HvYCr+Ac+WacnJSmh2J+7o+JqrfFaRpwYTlh2vix47bGr8DIuaV08tMJDuI/M7VJ aTFAbf+bsm7QhEreET4/eEL+ydNtJ2ZoXpMI0W/AA1FIHcLXMFV6qkX+HZ0nUnYY Xn7QwrPk/emZgHow8+ck9KwBveEVgW1WgTcpkrGOJaQ5a1xJ5eQbEknIU9aU48JE 1+ovIFTgZVC/FbbyIsv7B6T81VoNdueAVebaGv8MoDTPkAKqLDBogevFHPW7bxNy mYogRlpTI/4Io8q//01Gubjax9nyifLKw370fAI6aXmfiPQ3XTak6vH9fcudVUXg ==
X-ME-Sender: <xms:QfwNYK0eRq9X9E1Lbm4S6TZMzJD17pB6dz47yP2mzumxJ_SF2g2NHQ> <xme:QfwNYNGZ3DWEL_3xtfB73-O9a3GfT98aJyLy9d7Sq5mR6Nd-1TfGDBJNI5G6unShK uiyZWjM0G8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeehffduieffuefffeeuuedtiefhleeuvdeihfefuedvgfeu hffgffdthfefjedvieenucffohhmrghinhepihgvthhfrdhorhhgpdhirghnrgdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhho nhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:QfwNYC6cKyNnnFCUoUn5OTGJKalKomUQGvil6z4crt4Gi5xCJzUhMg> <xmx:QfwNYL0_Lkuugd7E0bnVueto1TPapIt-K0pdOQsustHdJJ9hyL99LQ> <xmx:QfwNYNG1dHReABJh1l_-E2o_E2kYtepO0N_3o3KFFWpa4eisTBcz8Q> <xmx:QvwNYAPRkuttn8lp9Z4eKP1kQPqE_8Ye18o19M0UnakQm3bB53YUwQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id BD72C360068; Sun, 24 Jan 2021 18:01:21 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com>
In-Reply-To: <CAM4esxS07JxMAQnfOOASxAZd3PvT=_GZpYE=P9i8d9nzpwmN=w@mail.gmail.com>
References: <161137784334.20615.12096399788075509949@ietfa.amsl.com> <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com> <CAM4esxS07JxMAQnfOOASxAZd3PvT=_GZpYE=P9i8d9nzpwmN=w@mail.gmail.com>
Date: Mon, 25 Jan 2021 10:01:01 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Cc: "Alexey Melnikov" <alexey.melnikov@isode.com>, "Barry Leiba" <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=f069f4f0ed79464fa55612e15a0c52a1
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/FNQZ99xubwciXy7JRUJUPfXoPIk>
Subject: Re: [Extra]  =?utf-8?q?Martin_Duke=27s_No_Objection_on_draft-ietf-ext?= =?utf-8?q?ra-imap4rev2-25=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: Sun, 24 Jan 2021 23:01:26 -0000

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

Oh hey - I'll defer to Alexey / Barry on this one.  It looks like "UID S=
et" is fresh terminology in imap4rev2 - I can't see it in RFC3501 - so t=
hey can explain why it's needed.

Cheers,

Bron.

On Mon, Jan 25, 2021, at 08:14, Martin Duke wrote:
> Thanks Bron,
>=20
> Your replies make sense, but one:
>=20
> Regarding 4.1.1, I find this terminology confusing, overloading the wo=
rd "sequence", although at this stage maybe it can't be helped. Still, t=
his section still seems very unclear to me.
>=20
> 4.1.1 <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev=
2-26#section-4.1.1>.  Sequence set and UID set

   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See Section 9=
 <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#se=
ction-9>
   for details.  Sequence sets can contain ranges (e.g. "5:50"), an
   enumeration of specific message/UID numbers, a special symbol "*", or=

   a combination of the above.

   A "UID set" is similar to the sequence set of unique identifiers;
   however, the "*" value for a sequence number is not permitted.
> So if I got this right, there's a "sequence set" that contains either =
sequence numbers or UIDs and can contain "*".=20
> then there is also a "UID Set" which is UID only, and cannot contain "=
*". But then I have two questions:
> (1) Can a sequence set have a combination of sequence numbers and UIDs=
 (" a combination of the above")?
> (2) If a UID set can't have sequence numbers, then why is it explainin=
g the lack of "*" in the context of UID sets with sequence numbers?
>=20
> On Sat, Jan 23, 2021 at 7:14 PM Bron Gondwana <brong@fastmailteam.com>=
 wrote:
>> __
>> On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:
>>=20
>> (I know the answers to these!)
>>=20
>>> 2.3.1.1 what would happen if the UID approached 2^32 due to a lifeti=
me of spam
>>> or something? The server can increment the validity value, but doesn=
=E2=80=99t that
>>> make earlier email unreferenceable except via sequence number?
>>=20
>> Sequence number is even less persistent - but when you increment the =
UIDVALIDITY you can renumber the UIDs for everything, so you'd just star=
t at 1 and reid all the existing records.  So they'll be referenceable b=
y their new UIDs next time the mailbox is selected.
>>=20
>> And (plug) if the server implements RFC8474 (object ids) then a clien=
t can even tell that it's the same email and not need to fetch the conte=
nt again, even after a UIDVALIDITY change.
>>=20
>>> 2.3.2 In the $Phishing definition, do you mean the user agent SHOULD=
 (in caps)
>>> display an additional warning message?
>>=20
>> This definition is copied from the IANA registry for keywords:
>>=20
>> https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishing=
-template
>>=20
>> I'm not sure there's any point in changing the text to be different f=
rom the IANA registration just to make it capital SHOULD.  It's unlikely=
 to change anybody's behaviour on reading this document.
>>=20
>>> 4.1.1 the last statement, =E2=80=9C the "*" value for a sequence num=
ber is not
>>> permitted.=E2=80=9D, is oddly placed, enough that it almost reads li=
ke a typo where you
>>> meant UID. A clearer statement might be =E2=80=9CThe =E2=80=98*=E2=80=
=99 value is permitted for UIDs
>>> but not sequence numbers.=E2=80=9D
>>=20
>> No, that would be an incorrect statement.  The phrase "UID set" is a =
definitional term which means:
>>=20
>> * a sequence set;
>> * that references UIDs, not message numbers; and
>> * that consists only of numbers, not the magic '*' character (which c=
an change value as new messages arrive)
>>=20
>> You can have a "sequence set" which references UIDs and does contain =
'*', but then it's not a "UID set" any more by definition.
>>=20
>> Cheers,
>>=20
>> Bron.
>>=20
>> --
>>   Bron Gondwana, CEO, Fastmail Pty Ltd
>>   brong@fastmailteam.com
>>=20
>>=20
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
>=20

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


--f069f4f0ed79464fa55612e15a0c52a1
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}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"f=
ont-family:Arial;">Oh hey - I'll defer to Alexey / Barry on this one.&nb=
sp; It looks like "UID Set" is fresh terminology in imap4rev2 - I can't =
see it in RFC3501 - so they can explain why it's needed.<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 Mon, Jan 25, 2021, at =
08:14, Martin Duke wrote:<br></div><blockquote type=3D"cite" id=3D"qt" s=
tyle=3D""><div dir=3D"ltr"><div dir=3D"ltr"><div>Thanks Bron,<br></div><=
div><br></div><div>Your replies make sense, but one:<br></div><div><br><=
/div><div>Regarding 4.1.1, I find this terminology confusing, overloadin=
g the word "sequence", although at this stage maybe it can't be helped. =
Still, this section still seems very unclear to me.<br></div><div><br></=
div><div><pre class=3D"qt-gmail-newpage"><span class=3D"qt-gmail-h4"><a =
class=3D"qt-gmail-selflink" id=3D"qt-gmail-section-4.1.1" href=3D"https:=
//datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#section-4.=
1.1">4.1.1</a>.  Sequence set and UID set</span>

   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See <a href=3D=
"https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#sec=
tion-9">Section 9</a>
   for details.  Sequence sets can contain ranges (e.g. "5:50"), an
   enumeration of specific message/UID numbers, a special symbol "*", or=

   a combination of the above.

   A "UID set" is similar to the sequence set of unique identifiers;
   however, the "*" value for a sequence number is not permitted.<br></p=
re></div></div><div>So if I got this right, there's a "sequence set" tha=
t contains either sequence numbers or UIDs and can contain "*". <br></di=
v><div>then there is also a "UID Set" which is UID only, and cannot cont=
ain "*". But then I have two questions:<br></div><div>(1) Can a sequence=
 set have a combination of sequence numbers and UIDs (" a combination of=
 the above")?<br></div><div>(2) If a UID set can't have sequence numbers=
, then why is it explaining the lack of "*" in the context of UID sets w=
ith sequence numbers?<br></div><div><br></div><div class=3D"qt-gmail_quo=
te"><div dir=3D"ltr" class=3D"qt-gmail_attr">On Sat, Jan 23, 2021 at 7:1=
4 PM Bron Gondwana &lt;<a href=3D"mailto:brong@fastmailteam.com">brong@f=
astmailteam.com</a>&gt; wrote:<br></div><blockquote class=3D"qt-gmail_qu=
ote" style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margin-l=
eft:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;b=
order-left-width:1px;padding-left:1ex;"><div><u></u><br></div><div><div =
style=3D"font-family:Arial;">On Sat, Jan 23, 2021, at 15:57, Martin Duke=
 via Datatracker wrote:<br></div><div style=3D"font-family:Arial;"><br><=
/div><div style=3D"font-family:Arial;">(I know the answers to these!)<br=
></div><div style=3D"font-family:Arial;"><br></div><blockquote type=3D"c=
ite" id=3D"qt-gmail-m_6628427668922159651qt"><div style=3D"font-family:A=
rial;">2.3.1.1 what would happen if the UID approached 2^32 due to a lif=
etime of spam<br></div><div style=3D"font-family:Arial;">or something? T=
he server can increment the validity value, but doesn=E2=80=99t that<br>=
</div><div style=3D"font-family:Arial;">make earlier email unreferenceab=
le except via sequence number?<br></div></blockquote><div style=3D"font-=
family:Arial;"><br></div><div style=3D"font-family:Arial;">Sequence numb=
er is even less persistent - but when you increment the UIDVALIDITY you =
can renumber the UIDs for everything, so you'd just start at 1 and reid =
all the existing records.&nbsp; So they'll be referenceable by their new=
 UIDs next time the mailbox is selected.<br></div><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;">And (plug) if th=
e server implements RFC8474 (object ids) then a client can even tell tha=
t it's the same email and not need to fetch the content again, even afte=
r a UIDVALIDITY change.<br></div><div style=3D"font-family:Arial;"><br><=
/div><blockquote type=3D"cite" id=3D"qt-gmail-m_6628427668922159651qt"><=
div style=3D"font-family:Arial;">2.3.2 In the $Phishing definition, do y=
ou mean the user agent SHOULD (in caps)<br></div><div style=3D"font-fami=
ly:Arial;">display an additional warning message?<br></div></blockquote>=
<div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Ar=
ial;">This definition is copied from the IANA registry for keywords:<br>=
</div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fam=
ily:Arial;"><a href=3D"https://www.iana.org/assignments/imap-jmap-keywor=
ds/phishing/phishing-template" target=3D"_blank">https://www.iana.org/as=
signments/imap-jmap-keywords/phishing/phishing-template</a><br></div><di=
v style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial=
;">I'm not sure there's any point in changing the text to be different f=
rom the IANA registration just to make it capital SHOULD.&nbsp; It's unl=
ikely to change anybody's behaviour on reading this document.<br></div><=
div style=3D"font-family:Arial;"><br></div><blockquote type=3D"cite" id=3D=
"qt-gmail-m_6628427668922159651qt"><div style=3D"font-family:Arial;">4.1=
.1 the last statement, =E2=80=9C the "*" value for a sequence number is =
not<br></div><div style=3D"font-family:Arial;">permitted.=E2=80=9D, is o=
ddly placed, enough that it almost reads like a typo where you<br></div>=
<div style=3D"font-family:Arial;">meant UID. A clearer statement might b=
e =E2=80=9CThe =E2=80=98*=E2=80=99 value is permitted for UIDs<br></div>=
<div style=3D"font-family:Arial;">but not sequence numbers.=E2=80=9D<br>=
</div></blockquote><div id=3D"qt-gmail-m_6628427668922159651sig56629417"=
><div><br></div><div style=3D"font-family:Arial;">No, that would be an i=
ncorrect statement.&nbsp; The phrase "UID set" is a definitional term wh=
ich means:<br></div><div style=3D"font-family:Arial;"><br></div><div sty=
le=3D"font-family:Arial;">* a sequence set;<br></div><div style=3D"font-=
family:Arial;">* that references UIDs, not message numbers; and<br></div=
><div style=3D"font-family:Arial;">* that consists only of numbers, not =
the magic '*' character (which can change value as new messages arrive)<=
br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-=
family:Arial;">You can have a "sequence set" which references UIDs and d=
oes contain '*', but then it's not a "UID set" any more by definition.<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;">Cheers,<br></div><div style=3D"font-family:Arial;"><div><b=
r></div><div>Bron.<br></div></div><div style=3D"font-family:Arial;"><br>=
</div><div style=3D"font-family:Arial;">--<br></div><div>&nbsp; Bron Gon=
dwana, CEO, Fastmail Pty Ltd<br></div><div>&nbsp; <a href=3D"mailto:bron=
g@fastmailteam.com" target=3D"_blank">brong@fastmailteam.com</a><br></di=
v><div><br></div></div><div style=3D"font-family:Arial;"><br></div></div=
></blockquote></div></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/e=
xtra</a><br></div><div><br></div></blockquote><div style=3D"font-family:=
Arial;"><br></div><div id=3D"sig56629417"><div class=3D"signature">--<br=
></div><div 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>
--f069f4f0ed79464fa55612e15a0c52a1--


From nobody Mon Jan 25 03:12:26 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 540FA3A0EED; Mon, 25 Jan 2021 03:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 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, 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 TGadfE63scde; Mon, 25 Jan 2021 03:12:18 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id F1A913A0F00; Mon, 25 Jan 2021 03:12:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611573136; d=isode.com; s=june2016; i=@isode.com; bh=/wc/ANeYB0c0wh5v5AG1IgN6ZlJGmT21EMgjbD92LMg=; 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=T1g0WTg3ncFLbPbwo9ZMUeVIbvSP45scjANZLTdVarp7B0AIXvZMm1CA9jwB3zOKgTYOWx I96aDEI5S8z2Tyfxdn1CUst3CzAcWDbj8g4oXlcjbqPFW1+ALlvplQRRPVSZE6IIAtOyrG rpDmibSXvsr/8dyetrd3X3rdM5xGIoc=;
Received: from [172.27.251.194] (connect.isode.net [172.20.0.72])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YA6nkAAuQQjZ@waldorf.isode.com>; Mon, 25 Jan 2021 11:12:16 +0000
To: Bron Gondwana <brong@fastmailteam.com>, Martin Duke <martin.h.duke@gmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, extra@ietf.org, The IESG <iesg@ietf.org>
References: <161137784334.20615.12096399788075509949@ietfa.amsl.com> <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com> <CAM4esxS07JxMAQnfOOASxAZd3PvT=_GZpYE=P9i8d9nzpwmN=w@mail.gmail.com> <e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <7b366fe2-9bfe-dc5c-d510-29a256e43b01@isode.com>
Date: Mon, 25 Jan 2021 11:12:15 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------ECD533FDA9757F8833541938"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/gHuBx9G9byNMOK-iXiYkHLX9nVc>
Subject: Re: [Extra] Martin Duke's No Objection on draft-ietf-extra-imap4rev2-25: (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, 25 Jan 2021 11:12:20 -0000

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

On 24/01/2021 23:01, Bron Gondwana wrote:

> Oh hey - I'll defer to Alexey / Barry on this one.=C2=A0 It looks like "UI=
D=20
> Set" is fresh terminology in imap4rev2 - I can't see it in RFC3501 -=20
> so they can explain why it's needed.

"UID Set" came from RFC 4315 (UIDPLUS), which was folded into this=20
document. It is needed to describe COPYUID/APPENDUID response codes,=20
which always contain definite set of UIDs, i.e. no special "*".

Replying to Martin's comments below:

> Cheers,
>
> Bron.
>
> On Mon, Jan 25, 2021, at 08:14, Martin Duke wrote:
>> Thanks Bron,
>>
>> Your replies make sense, but one:
>>
>> Regarding 4.1.1, I find this terminology confusing, overloading the=20
>> word "sequence", although at this stage maybe it can't be helped.=20
>> Still, this section still seems very unclear to me.
>>
>> 4.1.1=20
>> <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#sect=
ion-4.1.1>.=20
>> Sequence set and UID set
>>
>>     A set of messages can be referenced by a sequence set containing
>>     either message sequence numbers or unique identifiers.  SeeSection 9 =
 <https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#sectio=
n-9>
>>     for details.  Sequence sets can contain ranges (e.g. "5:50"), an
>>     enumeration of specific message/UID numbers, a special symbol "*", or
>>     a combination of the above.
>>
>>     A "UID set" is similar to the sequence set of unique identifiers;
>>     however, the "*" value for a sequence number is not permitted.
>> So if I got this right, there's a "sequence set" that contains either=20
>> sequence numbers or UIDs and can contain "*".
>> then there is also a "UID Set" which is UID only, and cannot contain=20
>> "*". But then I have two questions:
>> (1) Can a sequence set have a combination of sequence numbers and=20
>> UIDs (" a combination of the above")?
No it is not possible to combine them. And it is always clear from=20
context (syntax) whether it is a sequence set of message numbers or a=20
sequence set of UIDs. For example, FETCH command always takes a sequence=20
set of message numbersas a parameter, while UID FETCH a always takes a=20
sequence set of UIDs as a parameter.
>> (2) If a UID set can't have sequence numbers, then why is it=20
>> explaining the lack of "*" in the context of UID sets with sequence=20
>> numbers?

Hopefully my explanation below anwered that. Also, sequence set is the=20
original concept from IMAP4, so explaining how UID set differs from it=20
seem to make sense.

Basically "*" is suitable as input to a command, when its value can be=20
evaluated by the server, while the client might not even know its exact=20
value at the time the command is executed.

When the server is returning a UID set (which is typically a part of a=20
map from old UID set to a new UID set), the client has to know all=20
values. So "*" is not suitable for this case.

Best Regards,

Alexey

>>
>> On Sat, Jan 23, 2021 at 7:14 PM Bron Gondwana <brong@fastmailteam.com=20
>> <mailto:brong@fastmailteam.com>> wrote:
>>
>>
>>     On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:
>>
>>     (I know the answers to these!)
>>
>>>     2.3.1.1 what would happen if the UID approached 2^32 due to a
>>>     lifetime of spam
>>>     or something? The server can increment the validity value, but
>>>     doesn=E2=80=99t that
>>>     make earlier email unreferenceable except via sequence number?
>>
>>     Sequence number is even less persistent - but when you increment
>>     the UIDVALIDITY you can renumber the UIDs for everything, so
>>     you'd just start at 1 and reid all the existing records.=C2=A0 So
>>     they'll be referenceable by their new UIDs next time the mailbox
>>     is selected.
>>
>>     And (plug) if the server implements RFC8474 (object ids) then a
>>     client can even tell that it's the same email and not need to
>>     fetch the content again, even after a UIDVALIDITY change.
>>
>>>     2.3.2 In the $Phishing definition, do you mean the user agent
>>>     SHOULD (in caps)
>>>     display an additional warning message?
>>
>>     This definition is copied from the IANA registry for keywords:
>>
>>     https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishing=
-template
>>     <https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishin=
g-template>
>>
>>     I'm not sure there's any point in changing the text to be
>>     different from the IANA registration just to make it capital
>>     SHOULD. It's unlikely to change anybody's behaviour on reading
>>     this document.
>>
>>>     4.1.1 the last statement, =E2=80=9C the "*" value for a sequence num=
ber
>>>     is not
>>>     permitted.=E2=80=9D, is oddly placed, enough that it almost reads li=
ke a
>>>     typo where you
>>>     meant UID. A clearer statement might be =E2=80=9CThe =E2=80=98*=E2=
=80=99 value is
>>>     permitted for UIDs
>>>     but not sequence numbers.=E2=80=9D
>>
>>     No, that would be an incorrect statement.=C2=A0 The phrase "UID set"
>>     is a definitional term which means:
>>
>>     * a sequence set;
>>     * that references UIDs, not message numbers; and
>>     * that consists only of numbers, not the magic '*' character
>>     (which can change value as new messages arrive)
>>
>>     You can have a "sequence set" which references UIDs and does
>>     contain '*', but then it's not a "UID set" any more by definition.
>>
>>     Cheers,
>>
>>     Bron.
>>
>>     --
>>     =C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd
>>     brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>>
>>
>> _______________________________________________
>> Extra mailing list
>> Extra@ietf.org <mailto:Extra@ietf.org>
>> https://www.ietf.org/mailman/listinfo/extra=20
>> <https://www.ietf.org/mailman/listinfo/extra>
>>
>
> --
> =C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd
> =C2=A0 brong@fastmailteam.com
>
>
>
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra

--------------ECD533FDA9757F8833541938
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>On 24/01/2021 23:01, Bron Gondwana wrote:<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com"=
>
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <title></title>
      <style type=3D"text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}p.MsoNorm=
al,p.MsoNoSpacing{margin:0}</style>
      <div style=3D"font-family:Arial;">Oh hey - I'll defer to Alexey /
        Barry on this one.=C2=A0 It looks like "UID Set" is fresh terminolog=
y
        in imap4rev2 - I can't see it in RFC3501 - so they can explain
        why it's needed.<br>
      </div>
    </blockquote>
    <p>"UID Set" came from RFC 4315 (UIDPLUS), which was folded into
      this document. It is needed to describe COPYUID/APPENDUID response
      codes, which always contain definite set of UIDs, i.e. no special
      "*".</p>
    <p>Replying to Martin's comments below:<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com"=
>
      <div style=3D"font-family:Arial;">Cheers,<br>
      </div>
      <div style=3D"font-family:Arial;"><br>
        Bron.<br>
      </div>
      <div style=3D"font-family:Arial;"><br>
      </div>
      <div>On Mon, Jan 25, 2021, at 08:14, Martin Duke wrote:<br>
      </div>
      <blockquote type=3D"cite" id=3D"qt" style=3D"">
        <div dir=3D"ltr">
          <div dir=3D"ltr">
            <div>Thanks Bron,<br>
            </div>
            <div><br>
            </div>
            <div>Your replies make sense, but one:<br>
            </div>
            <div><br>
            </div>
            <div>Regarding 4.1.1, I find this terminology confusing,
              overloading the word "sequence", although at this stage
              maybe it can't be helped. Still, this section still seems
              very unclear to me.<br>
            </div>
            <div><br>
            </div>
            <div>
              <pre class=3D"qt-gmail-newpage"><span class=3D"qt-gmail-h4"><a=
 class=3D"qt-gmail-selflink" id=3D"qt-gmail-section-4.1.1" href=3D"https://d=
atatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#section-4.1.1" mo=
z-do-not-send=3D"true">4.1.1</a>.  Sequence set and UID set</span>

   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See <a href=3D"ht=
tps://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-26#section-9"=
 moz-do-not-send=3D"true">Section 9</a>
   for details.  Sequence sets can contain ranges (e.g. "5:50"), an
   enumeration of specific message/UID numbers, a special symbol "*", or
   a combination of the above.

   A "UID set" is similar to the sequence set of unique identifiers;
   however, the "*" value for a sequence number is not permitted.
</pre>
            </div>
          </div>
          <div>So if I got this right, there's a "sequence set" that
            contains either sequence numbers or UIDs and can contain
            "*". <br>
          </div>
          <div>then there is also a "UID Set" which is UID only, and
            cannot contain "*". But then I have two questions:<br>
          </div>
          <div>(1) Can a sequence set have a combination of sequence
            numbers and UIDs (" a combination of the above")?<br>
          </div>
        </div>
      </blockquote>
    </blockquote>
    No it is not possible to combine them. And it is always clear from
    context (syntax) whether it is a sequence set of message numbers or
    a sequence set of UIDs. For example, FETCH command always takes a
    sequence set of message numbersas a parameter, while UID FETCH a
    always takes a sequence set of UIDs as a parameter.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com"=
>
      <blockquote type=3D"cite" id=3D"qt" style=3D"">
        <div dir=3D"ltr">
          <div>(2) If a UID set can't have sequence numbers, then why is
            it explaining the lack of "*" in the context of UID sets
            with sequence numbers?<br>
          </div>
        </div>
      </blockquote>
    </blockquote>
    <p>Hopefully my explanation below anwered that. Also, sequence set
      is the original concept from IMAP4, so explaining how UID set
      differs from it seem to make sense.<br>
    </p>
    <p>Basically "*" is suitable as input to a command, when its value
      can be evaluated by the server, while the client might not even
      know its exact value at the time the command is executed.</p>
    <p>When the server is returning a UID set (which is typically a part
      of a map from old UID set to a new UID set), the client has to
      know all values. So "*" is not suitable for this case.</p>
    <p>Best Regards,</p>
    <p>Alexey<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:e132060b-1f15-4f36-982b-6aba2d1f8171@dogfood.fastmail.com"=
>
      <blockquote type=3D"cite" id=3D"qt" style=3D"">
        <div dir=3D"ltr">
          <div><br>
          </div>
          <div class=3D"qt-gmail_quote">
            <div dir=3D"ltr" class=3D"qt-gmail_attr">On Sat, Jan 23, 2021 at
              7:14 PM Bron Gondwana &lt;<a
                href=3D"mailto:brong@fastmailteam.com"
                moz-do-not-send=3D"true">brong@fastmailteam.com</a>&gt;
              wrote:<br>
            </div>
            <blockquote class=3D"qt-gmail_quote"
style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex=
;border-left-color:rgb(204,
              204,
              204);border-left-style:solid;border-left-width:1px;padding-lef=
t:1ex;">
              <div><br>
              </div>
              <div>
                <div style=3D"font-family:Arial;">On Sat, Jan 23, 2021, at
                  15:57, Martin Duke via Datatracker wrote:<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;">(I know the answers to
                  these!)<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <blockquote type=3D"cite"
                  id=3D"qt-gmail-m_6628427668922159651qt">
                  <div style=3D"font-family:Arial;">2.3.1.1 what would
                    happen if the UID approached 2^32 due to a lifetime
                    of spam<br>
                  </div>
                  <div style=3D"font-family:Arial;">or something? The
                    server can increment the validity value, but doesn=E2=80=
=99t
                    that<br>
                  </div>
                  <div style=3D"font-family:Arial;">make earlier email
                    unreferenceable except via sequence number?<br>
                  </div>
                </blockquote>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;">Sequence number is even
                  less persistent - but when you increment the
                  UIDVALIDITY you can renumber the UIDs for everything,
                  so you'd just start at 1 and reid all the existing
                  records.=C2=A0 So they'll be referenceable by their new
                  UIDs next time the mailbox is selected.<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;">And (plug) if the server
                  implements RFC8474 (object ids) then a client can even
                  tell that it's the same email and not need to fetch
                  the content again, even after a UIDVALIDITY change.<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <blockquote type=3D"cite"
                  id=3D"qt-gmail-m_6628427668922159651qt">
                  <div style=3D"font-family:Arial;">2.3.2 In the $Phishing
                    definition, do you mean the user agent SHOULD (in
                    caps)<br>
                  </div>
                  <div style=3D"font-family:Arial;">display an additional
                    warning message?<br>
                  </div>
                </blockquote>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;">This definition is
                  copied from the IANA registry for keywords:<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;"><a
href=3D"https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishin=
g-template"
                    target=3D"_blank" moz-do-not-send=3D"true">https://www.i=
ana.org/assignments/imap-jmap-keywords/phishing/phishing-template</a><br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <div style=3D"font-family:Arial;">I'm not sure there's any
                  point in changing the text to be different from the
                  IANA registration just to make it capital SHOULD.=C2=A0
                  It's unlikely to change anybody's behaviour on reading
                  this document.<br>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
                <blockquote type=3D"cite"
                  id=3D"qt-gmail-m_6628427668922159651qt">
                  <div style=3D"font-family:Arial;">4.1.1 the last
                    statement, =E2=80=9C the "*" value for a sequence number=
 is
                    not<br>
                  </div>
                  <div style=3D"font-family:Arial;">permitted.=E2=80=9D, is =
oddly
                    placed, enough that it almost reads like a typo
                    where you<br>
                  </div>
                  <div style=3D"font-family:Arial;">meant UID. A clearer
                    statement might be =E2=80=9CThe =E2=80=98*=E2=80=99 valu=
e is permitted for
                    UIDs<br>
                  </div>
                  <div style=3D"font-family:Arial;">but not sequence
                    numbers.=E2=80=9D<br>
                  </div>
                </blockquote>
                <div id=3D"qt-gmail-m_6628427668922159651sig56629417">
                  <div><br>
                  </div>
                  <div style=3D"font-family:Arial;">No, that would be an
                    incorrect statement.=C2=A0 The phrase "UID set" is a
                    definitional term which means:<br>
                  </div>
                  <div style=3D"font-family:Arial;"><br>
                  </div>
                  <div style=3D"font-family:Arial;">* a sequence set;<br>
                  </div>
                  <div style=3D"font-family:Arial;">* that references
                    UIDs, not message numbers; and<br>
                  </div>
                  <div style=3D"font-family:Arial;">* that consists only
                    of numbers, not the magic '*' character (which can
                    change value as new messages arrive)<br>
                  </div>
                  <div style=3D"font-family:Arial;"><br>
                  </div>
                  <div style=3D"font-family:Arial;">You can have a
                    "sequence set" which references UIDs and does
                    contain '*', but then it's not a "UID set" any more
                    by definition.<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;">
                    <div><br>
                    </div>
                    <div>Bron.<br>
                    </div>
                  </div>
                  <div style=3D"font-family:Arial;"><br>
                  </div>
                  <div style=3D"font-family:Arial;">--<br>
                  </div>
                  <div>=C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd<br>
                  </div>
                  <div>=C2=A0 <a href=3D"mailto:brong@fastmailteam.com"
                      target=3D"_blank" moz-do-not-send=3D"true">brong@fastm=
ailteam.com</a><br>
                  </div>
                  <div><br>
                  </div>
                </div>
                <div style=3D"font-family:Arial;"><br>
                </div>
              </div>
            </blockquote>
          </div>
        </div>
        <div>_______________________________________________<br>
        </div>
        <div>Extra mailing list<br>
        </div>
        <div><a href=3D"mailto:Extra@ietf.org" moz-do-not-send=3D"true">Extr=
a@ietf.org</a><br>
        </div>
        <div><a href=3D"https://www.ietf.org/mailman/listinfo/extra"
            moz-do-not-send=3D"true">https://www.ietf.org/mailman/listinfo/e=
xtra</a><br>
        </div>
        <div><br>
        </div>
      </blockquote>
      <div style=3D"font-family:Arial;"><br>
      </div>
      <div id=3D"sig56629417">
        <div class=3D"signature">--<br>
        </div>
        <div class=3D"signature">=C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd=
<br>
        </div>
        <div class=3D"signature">=C2=A0 <a class=3D"moz-txt-link-abbreviated=
" href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a><br>
        </div>
        <div class=3D"signature"><br>
        </div>
      </div>
      <div style=3D"font-family:Arial;"><br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <pre class=3D"moz-quote-pre" wrap=3D"">_______________________________=
________________
Extra mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Extra@ietf.org">Extra@i=
etf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/list=
info/extra">https://www.ietf.org/mailman/listinfo/extra</a>
</pre>
    </blockquote>
  </body>
</html>

--------------ECD533FDA9757F8833541938--


From nobody Fri Jan 29 07:00:55 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 405CD3A1049; Fri, 29 Jan 2021 07:00:53 -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_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 1PC5TBWauOr5; Fri, 29 Jan 2021 07:00:51 -0800 (PST)
Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) (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 DA3403A1042; Fri, 29 Jan 2021 07:00:47 -0800 (PST)
Received: by mail-lf1-f44.google.com with SMTP id h7so12904375lfc.6; Fri, 29 Jan 2021 07:00:47 -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=NRDPD0wvhvX+4S2YOnyHS0K7crmDWbUailyhesDs7NA=; b=d+tRryreTBxzl7uanPd0nUqPwEIar4sI8jqUdt4FwogdIBtjCLHtMQSjCc58cTJHLn QCmwGxPBpDGkNTjlGE+a+fqTQujKVvMgwF8PWvIzBDYrChGoIfmaKnkQuW80b02gBiQ3 C5dRBYf18oa1S1m7+CWCpMmZyHR1or86IHMoi1fIrBEM8Pgcy7wp6rixyADHrdjkYiR9 X7S09KBeLPsTj+iOoV5uguXwfnopGkpkXoZZEszj3u4ODTPPtIe3A0Zfn3+R5/h4oc1w 6o32sNVUeiaeafw+zHfbIE+4EfHPAYwakkzTycj5GtNdClMrb3SksQqeZAuvnsgCJDdu 7Vlw==
X-Gm-Message-State: AOAM5317T3/iGWb7x1M6mdWRFtSnzEXTdWx/ZINgW4Bj9fpKy5MV0O+J EFDpmZ/zSAjGEjCJ73s8u5qv4xZR/cNJVaUVd/SONCX6
X-Google-Smtp-Source: ABdhPJxiI0uAXT6ODPuY+UFrkNfski0+3hzyej2bmxQ8oLebYBlxLYNoq1ALeYNXBYOrJ1acVp3HMQRIz5wosNbq99w=
X-Received: by 2002:ac2:420a:: with SMTP id y10mr2269708lfh.377.1611932444395;  Fri, 29 Jan 2021 07:00:44 -0800 (PST)
MIME-Version: 1.0
References: <160804212198.17646.8123862646316973469@ietfa.amsl.com>
In-Reply-To: <160804212198.17646.8123862646316973469@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 29 Jan 2021 10:00:33 -0500
Message-ID: <CALaySJ++V+zPThbv0Fb2zCV4c=xwLPLSCpRFs6gC_fj8N-AtLg@mail.gmail.com>
To: draft-ietf-extra-sieve-mailboxid@ietf.org
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, The IESG <iesg@ietf.org>, extra@ietf.org,  YAO Jiankang <yaojk@cnnic.cn>, extra-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/muEXo1dqJhN4Yiay6-Qr5DULxt8>
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: Fri, 29 Jan 2021 15:00:53 -0000

Bron,

I haven't seen a response to this DISCUSS from Magnus, nor to some of
the non-blocking comments (from Ben, for example).

Barry

On Tue, Dec 15, 2020 at 9:22 AM Magnus Westerlund via Datatracker
<noreply@ietf.org> 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/
>
>
>
> ----------------------------------------------------------------------
> 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.
>
> 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.
>
>
>
>
>

