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

Barry Leiba <barryleiba@computer.org> Tue, 02 February 2021 18:13 UTC

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

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

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

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

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

I agree with you.

That said, there are two things:

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

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

Alexey, thoughts?

Barry