Re: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02

Ken Murchison <murch@fastmail.com> Mon, 26 March 2018 12:38 UTC

Return-Path: <murch@fastmail.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 543AD127201 for <extra@ietfa.amsl.com>; Mon, 26 Mar 2018 05:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=ClZn0aoh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Cb5zeOhF
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 7qDDneCxKm6j for <extra@ietfa.amsl.com>; Mon, 26 Mar 2018 05:38:17 -0700 (PDT)
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 A5AFD124205 for <extra@ietf.org>; Mon, 26 Mar 2018 05:38:17 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E217420C2A for <extra@ietf.org>; Mon, 26 Mar 2018 08:38:16 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 26 Mar 2018 08:38:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=xwzzPBtUnH5dVUURMr3nfXJzJZirmY603NhQ45WtCe4=; b=ClZn0aoh LFGGLrfH5A7WvwyO17QcWqHq7g7isQHbVmN6a5CEFEVLeQQp75HBKQqN/2/+WGtq 014l2GaU3NajEJbKotZC2L0JWfmAwVwsk4Jzjdm2GUBgJGIgvtnBkSRq4AS9+Y60 Cvd4p+7KquOLutZe29W5HWpzQz8OdiqB1hBJZUjyC4RZSEpbjOUWs4U1a4bHBojZ 80C1LHCWQBAP10WbhTUtvS5LaaIPuVob9Qx1L7Gro9rGuarCQ85T/y3wmUOal8ju cv7h8ooL3ondNyrQOTUl1ctY8ZkIPeaTkTGhV3T8b3pQLhlzgzs8E39a00A9EW3z sJTTcAEGo86/eg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=xwzzPBtUnH5dVUURMr3nfXJzJZirm Y603NhQ45WtCe4=; b=Cb5zeOhF0YaQIJeZhW0uMkje0FIi7rI+lWOAbHML/RF4S 3aIH2lD+3JOSGgfEPLcg5V1xDP2b473cUCklGorx8e2CZxTMYpduJumr2C9nBJrO 1nOXsuj6UB3IDqD9uRq9P9g1ZqcC55vSmqb9bMl+EdczaLqbg4IkFZe86p3GO7/J ribRIv4PZAPNvjSM1SlqtrGRsoh/fMLx9mF+WPD1gzpbJxm0/IEUpXj644NQ/98p IHERagi6PywJTVq9vb8wHWjKOKYMcv6fFgBVKdi8w/klmwVm+QQtFylBGRhERd01 4Wq065xpNn+E8x9HMs91sSdN8gY0dCPHsYjHqHxxg==
X-ME-Sender: <xms:uOm4WgbY9cif7obPkd-Gu5sawV-ktLmgnVbxHrs_Z8Ju0qWLakHENA>
Received: from localhost.localdomain (248.sub-70-195-140.myvzw.com [70.195.140.248]) by mail.messagingengine.com (Postfix) with ESMTPA id 8227BE4488 for <extra@ietf.org>; Mon, 26 Mar 2018 08:38:16 -0400 (EDT)
To: extra@ietf.org
References: <CALaySJ+qk9rYkdiDU+gtvznGvCM-UEtGm=W0F7Crg4zu8gpWhQ@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Organization: FastMail US LLC
Message-ID: <5419ed87-0778-25d3-e6b3-7e3919a2c6e2@fastmail.com>
Date: Mon, 26 Mar 2018 08:38:13 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+qk9rYkdiDU+gtvznGvCM-UEtGm=W0F7Crg4zu8gpWhQ@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------B33E0574DA6704E400A08990"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/_lBYPIYf3mIaqInIe1m05_5jepU>
Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 12:38:21 -0000

Hi Barry,

Thanks for the review.  Changes have been made in the working copy:
<https://github.com/ietfextra/tracking/commit/436c8e56970cdf4bef73cbd887c1ee4eaf55b85d>

https://github.com/ietfextra/tracking/commit/436c8e56970cdf4bef73cbd887c1ee4eaf55b85d



On 03/26/2018 05:42 AM, Barry Leiba wrote:
> The document's in very good shape and is almost ready.  I have a
> couple of minor points below.
>
> — Section 3 —
>
>     For each listable mailbox matching
>     the list pattern and selection options, the server MUST return an
>     untagged LIST response followed by an untagged MYRIGHTS response
>     containing the set of rights granted to the logged-in user.
>
> We don’t usually specify any particular ordering for untagged
> responses, and for the most part, ordering is not significant.  I
> presume it’s not significant here, and that both of the following
> would be equally acceptable to a client:
>
>     C: A01 LIST "" % RETURN (MYRIGHTS)
>     S: * LIST () "." "INBOX"
>     S: * MYRIGHTS "INBOX" lrswipkxtecda
>     S: * LIST () "." "foo"
>     S: * MYRIGHTS "foo" lrs
>     S: A01 OK List completed.
>
>     C: A01 LIST "" % RETURN (MYRIGHTS)
>     S: * LIST () "." "INBOX"
>     S: * LIST () "." "foo"
>     S: * MYRIGHTS "foo" lrs
>     S: * MYRIGHTS "INBOX" lrswipkxtecda
>     S: A01 OK List completed.
>
> Now, one wonders whether this would also be acceptable:
>
>     C: A01 LIST "" % RETURN (MYRIGHTS)
>     S: * MYRIGHTS "foo" lrs
>     S: * MYRIGHTS "INBOX" lrswipkxtecda
>     S: * LIST () "." "INBOX"
>     S: * LIST () "." "foo"
>     S: A01 OK List completed.
>
> …as a client might not be happy seeing MYRIGHTS responses for
> mailboxes for which it has not yet seen a LIST response.
>
> Also, the MUST attached to the production of the MYRIGHTS response is
> contradicted by the MAY in the next paragraph.
>
> I think we shouldn’t imply that the responses have to be interleaved,
> and we should point out that the MYRIGHTS response for a given mailbox
> can’t precede the LIST response for that mailbox.  Maybe this?:
>
> NEW
>     For each listable mailbox matching
>     the list pattern and selection options, the server MUST return an
>     untagged LIST response and SHOULD also return an untagged MYRIGHTS
>     response containing the set of rights granted to the logged-in user.
>     The ordering of the responses is significant only in that the server
>     MUST NOT send a MYRIGHTS for a given mailbox before it sends that
>     mailbox’s LIST response.
> END
>
> Now, as to the following paragraph that explains the SHOULD:
>
>     If the server is unable to look up the set of rights for a given
>     mailbox, it MAY drop the corresponding MYRIGHTS reply.
>
> What else could it do?  If there are other reasonable choices, we
> should say what they are.  If not, we shouldn’t imply that there are.
> And it’s not really a MAY; the server has to do something reasonable,
> so I suggest one of the following:
>
> NEW-1
>     If the server is unable to look up the set of rights for a given
>     mailbox, it does not send the MYRIGHTS reply for that mailbox.
> END
>
> NEW-2
>     If the server is unable to look up the set of rights for a given
>     mailbox, it either does not send the MYRIGHTS reply for that
>     mailbox or <—fill in other possible actions here—>.
> END
>
> — Section 8 —
> It’s always a good idea to give IANA the full name of the registry,
> rather than citing where the registry is defined (this is highlighted
> by the fact that there are two registries “defined in Section 9 of
> [RFC5258]”):
>
> OLD
>     This document defines the "LIST-MYRIGHTS" IMAP capability to be added
>     to the registry defined in Section 12 of [RFC3501].
> NEW
>     This document defines the "LIST-MYRIGHTS" IMAP capability to be added
>     to the “IMAP Capabilities” registry:
>     <https://www.iana.org/assignments/imap-capabilities#imap-capabilities-1>
> END
>
> OLD
>     This section registers the "MYRIGHTS" option to be added to the
>     registry defined in Section 9 of [RFC5258].
> NEW
>     This section registers the "MYRIGHTS" option to be added to the
>     “LIST-EXTENDED options” registry:
>     <https://www.iana.org/assignments/imap-list-extended#imap-list-extended-1>
> END
>
> — Section 10.2 —
> I find it somewhat odd to have a formal reference to 5819 (implying
> that there’s something in there that the reader might find useful in
> reading this one), when it’s only used in the Acknowledgments.  I
> suggest changing the Acks to just say “RFC 5819” (plain text, not as a
> citation), and removing the informative reference.
>

-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC