Re: [Extra] Protocol Action: 'The JMAPACCESS Extension for IMAP' to Proposed Standard (draft-ietf-extra-jmapaccess-08.txt)

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 07 March 2024 15:54 UTC

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 9E48CC151986 for <extra@ietfa.amsl.com>; Thu, 7 Mar 2024 07:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 buaj3WaIr2Dt for <extra@ietfa.amsl.com>; Thu, 7 Mar 2024 07:54:28 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE13CC151532 for <extra@ietf.org>; Thu, 7 Mar 2024 07:54:26 -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 55D41C017C; Thu, 7 Mar 2024 15:54:23 +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=pass smtp.mailfrom=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1709826863; bh=YWnk7yavKCVyOyI4RZu5md6xMT8eTb98d8mjMkR/6m8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=svH74c4Pt7gPsmL2MTRzRDxAerBELmx6IN7xyDPs2Pn0iTBSxSXbju5dH3qp8Pgg3 UyKdWsENVniVnJqSNF/I4KOTGwGgG01yZNxeubFWVuwEg3mhdYnz6ynkxPY/XCCV2d aTkFiP7xk0CL9TCh+pAcEpkuRM+DAi8m67XL8wVk=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1709826862-27907-27898/9/3028; Thu, 7 Mar 2024 15:54:22 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Ken Murchison <murch@fastmail.com>
Cc: extra@ietf.org
Date: Thu, 07 Mar 2024 16:54:22 +0100
Mime-Version: 1.0
Message-Id: <370ab6b6-c9b8-4d1f-be4f-8f2abb5d9957@gulbrandsen.priv.no>
In-Reply-To: <5e429fb1-13e3-b169-9c2e-c0b6f4c6ea10@fastmail.com>
References: <170933386873.22107.4252444886939473126@ietfa.amsl.com> <5e429fb1-13e3-b169-9c2e-c0b6f4c6ea10@fastmail.com>
User-Agent: Trojita/v0.7-599-g1d6a1f7d; Qt/5.15.10; xcb; Linux; Devuan GNU/Linux 6 (excalibur/ceres)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/Abd69r0GKFDE4fPOPifHiukgpYE>
Subject: Re: [Extra] Protocol Action: 'The JMAPACCESS Extension for IMAP' to Proposed Standard (draft-ietf-extra-jmapaccess-08.txt)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.39
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, 07 Mar 2024 15:54:32 -0000

Ken Murchison writes:
> I gave this another read as I get ready to add support to 
> Cyrus.  Two comments:
>
> The DEBUGGING response code was removed from this spec, so I 
> think the second paragraph of the introduction should also be 
> removed.

Good point, noted. Sorry about the lateness.

> The ABNF for the JMAPACCESS response code simply uses  the 
> 'quoted' token where the JMAP Session URL is located.

I changed to quoted due to implementer feedback. There are several 
constraints:

1. It needs to be within the syntax for unknown response code.
2. It needs to NOT include literal, because literal can be multiline.
3. It needs to not permit an "]", I think.
4. It should be a single production, because two implementers suggested 
that having yet another string quasiproduction was annoying and I see their 
point.

Using jmap-session-uri might work, if that does not permit either CRLF or 
]. Uncertain, and I need to stop working and do household chores now.

Arnt