Re: [Gen-art] Genart last call review of draft-ietf-extra-jmapaccess-04

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 23 August 2023 08:41 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E933C14CE47; Wed, 23 Aug 2023 01:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.084
X-Spam-Level:
X-Spam-Status: No, score=-6.084 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmI-y2KQUYnm; Wed, 23 Aug 2023 01:41:39 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5928DC14CE2F; Wed, 23 Aug 2023 01:41:36 -0700 (PDT)
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 591D1C0026; Wed, 23 Aug 2023 09:41:35 +0100 (IST)
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=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1692780095; bh=FGMVd9HS02EV8LaELAFDCLhbiZ47paNyRzZWvguh9nc=; h=From:Cc:Subject:Date:In-Reply-To:References:From; b=C7caCuq4ZzQVGkIsWt1c8dUso8SF4AqKD+5/bcEHJKjDL7ezVbmfLb1J//uBa+iVR SsU82nm8ZFc0bAv6gMREfaHNFRmU277OZhlpHEHGN6xP7ryIW9fhAWiUycXOx3hgjq VRU9Ssd6+HFPz/buWJcLMZCTIdJ7gdJKidgjPdzw=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1692780094-16509-16496/9/13; Wed, 23 Aug 2023 08:41:34 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Cc: gen-art@ietf.org, draft-ietf-extra-jmapaccess.all@ietf.org, extra@ietf.org, last-call@ietf.org, Robert Sparks <rjsparks@nostrum.com>
Date: Wed, 23 Aug 2023 10:41:33 +0200
Mime-Version: 1.0
Message-Id: <37de52dd-dc63-4425-9ea6-2918c9fa4db7@gulbrandsen.priv.no>
In-Reply-To: <169273084467.16878.11065354795302493891@ietfa.amsl.com>
References: <169273084467.16878.11065354795302493891@ietfa.amsl.com>
User-Agent: Trojita/v0.7-599-g1d6a1f7d; Qt/5.15.8; xcb; Linux; Devuan GNU/Linux 5 (daedalus/ceres)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Ut1G5mqUZTqGjszBOz2wIPD3uMA>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-extra-jmapaccess-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Aug 2023 08:41:43 -0000

Thanks.

Robert Sparks via Datatracker writes:
> Nits/editorial comments:
>
> At:
>    A few IMAP client maintainers have asked for ways to use features
>    that are available in JMAP without having to drop their expensively
>    tested IMAP code.
>
> Why does this need to be in the document at all?

It answers the first question people ask — "why would a client want to use 
both?"

> It will not 
> age well. Consider just removing it.

I did, and added "or …" to the the abstract instead, which now ends 
"intended for clients that want to migrate gradually to JMAP or use JMAP 
extensions within an IMAP client."

Arnt