Re: [Extra] Éric Vyncke's No Objection on draft-ietf-extra-imap4rev2-26: (with COMMENT)

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 01 February 2021 18:18 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E69A93A1386; Mon, 1 Feb 2021 10:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puOU6m11q05P; Mon, 1 Feb 2021 10:18:56 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0856A3A1384; Mon, 1 Feb 2021 10:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1612203535; d=isode.com; s=june2016; i=@isode.com; bh=LvG9rcXTSakVnBxVv5XJuWbARBdulIhLhSY0EWfVOCw=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=sbMZEtWWepYz5ASW4eai1R8QXHqBuK0wpRseAJQ/G4F8RT3NXVjq78RQO2dAom/iGXu2+T 0gCukmEHRp4MhyWAZ3XnWiJavPrmVJKTrNEpnxVg5Q3DE9BMLEmYm9+UbjQxy9eJZ9nyGv gQ7AZo3Uf4ZjDzcjrGypBnKV4lzetuY=;
Received: from [192.168.1.222] (host5-81-100-50.range5-81.btcentralplus.com [5.81.100.50]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <YBhGDgAqZlSH@statler.isode.com>; Mon, 1 Feb 2021 18:18:54 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: =?UTF-8?Q?=c3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: extra@ietf.org, brong@fastmailteam.com, draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org
References: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
Message-ID: <d30bbdde-a98f-9b10-8293-86a37cd477a4@isode.com>
Date: Mon, 1 Feb 2021 18:18:54 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <161219302403.27128.9041237679555543330@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/toFxEXtJ5_pF4ecKmaIo0OkS6aE>
Subject: Re: [Extra] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-extra-imap4rev2-26=3A_=28with_COMMENT=29?=
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2021 18:18:59 -0000

Hi Éric,

Thank you for your review. Comments below.

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

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

So no, this has nothing to do with IMAP.

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

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

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

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

Best Regards,

Alexey