IETF Logo Mail Archive

Re: [Jmap] Question: Mandate core capability on each API call?

Neil Jenkins <neilj@fastmailteam.com> Tue, 08 December 2020 00:54 UTC

Return-Path: <neilj@fastmailteam.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6AEA3A0D35 for <jmap@ietfa.amsl.com>; Mon, 7 Dec 2020 16:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=nIoSVvtx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hI47mchU
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 mpVIg2Pov3XJ for <jmap@ietfa.amsl.com>; Mon, 7 Dec 2020 16:54:26 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FA023A0D32 for <jmap@ietf.org>; Mon, 7 Dec 2020 16:54:26 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 5CF867BE for <jmap@ietf.org>; Mon, 7 Dec 2020 19:54:24 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Mon, 07 Dec 2020 19:54:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=Nj98qgr IChBASx5vBWHEYl/1lT7V6WlRXSx0qvhbAy0=; b=nIoSVvtxDVwJB2yK9qWR1OP erpYVCca61P3Cdju/PCmlYB3Agvx5qpJs2Y2fFP/J0zx7ha0d5vRrTSXI7iFWNVQ 9nLbC0lKlX3A4UDIEoHm6YERjIec03rruH9A1DfxgO0B2P5wFy5akWHMipWbrwHP VKscLvs/w9Avpdwm5uAw1TCGeNIscFpzInEKqDcmnQ4Y+rXka9SSmh1vY1ZgKl9M 3lyZOURPnAaxDbjE99dBRvfQjOJikF7YDuo3msiDirvDvnNRVy5hLuvu3rzP4jHH 1TJINsoFoyni4tK4M05Ak6zkv9GCEM82Di1cHRLaa5oVppIPMTBuiXH5MP7z4MA= =
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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Nj98qg rIChBASx5vBWHEYl/1lT7V6WlRXSx0qvhbAy0=; b=hI47mchUU9ef0GlXkeHWYJ xlG40D0M3RfgdR0ccu9DoHNj73w0wWksp0jrb1CDjCOei7xyBKNcwDx8qc+mi+Lz y3AFhLkFQ8dNw51/DQ6YGZtqscsiojXND0NapTDp/Llq9ksWBQsxK0XiQXudx4Z9 lZx7i068XqoRw1geZGeRv1ysLK4UtfZlNDB20dGzbOFrdi2e844si8SwbyY0eYtY 1t2xx4MwQAWOwyB1GKpWvG1D774suWbw/nPNH29HM0whAQtYrC6+z82TVWkq/myE ivpkEg0LFPXSjU2zXBmD4U++PvdFXptFXAT8+Hx4wXc/QhP0ijdT0mdH8LMeORUg ==
X-ME-Sender: <xms:v87OX6xMxGVO3wMzKHxvBJ6VVdGqAJw1NvpIQWpaUa1O-HxFBAYdXA> <xme:v87OX2RJ_c_9V2PJd1MGt_mk4u8n08DSsvc37un6dVvssRgsB67-IayQzs-qih0B2 rMcW0RzdYMfCQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudejhedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeejuddttdeuieffuefgjeeuuefhhfeiteehheefjeefteev ffduieeiudehgfdtteenucffohhmrghinhepihgvthhfrdhorhhgpdhgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehn vghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:v87OX8VvWHZRZwWUV6MYF9RKLt98urp5GjDPAROWicWf61G_0j1dnQ> <xmx:v87OXwgBkvwdRRxTdnihy1pSqa_kLZDNig-XFt_Z0wn3fSFR6A7DFg> <xmx:v87OX8Bku9bkLAzslzMNeSnFenZvbK7OfJ9hNSZOmk9UZkBmE7fCpA> <xmx:v87OX_MgGX8mR3Y7Ruh_xzir_RLczQYzsF-2hJ-GLzzigtRGuAv1hA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 74EA3180093; Mon, 7 Dec 2020 19:54:23 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-622-g4a97c0b-fm-20201115.001-g4a97c0b3
Mime-Version: 1.0
Message-Id: <82ad0634-847c-4cd3-be8c-e1a6dbba9da5@beta.fastmail.com>
In-Reply-To: <6252ac04-caf9-6c32-eb29-8f075851dffc@linagora.com>
References: <a769713e-62ef-0eef-b61d-7fa64a8371ce@linagora.com> <8df9abc8-4c5d-47da-9966-b9646561e286@dogfood.fastmail.com> <17a0c929-66bc-71f8-54bd-cbf4faa8181e@linagora.com> <722e4258-1b8a-4b43-9a1a-2b8b910484b9@beta.fastmail.com> <6252ac04-caf9-6c32-eb29-8f075851dffc@linagora.com>
Date: Tue, 08 Dec 2020 11:54:13 +1100
From: Neil Jenkins <neilj@fastmailteam.com>
To: IETF JMAP Mailing List <jmap@ietf.org>
Content-Type: multipart/alternative; boundary="b6b17bcaa09d472db8877e5abd31490f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/wQaw_ivbvFtOrEPbkkOkDp3OGrU>
Subject: Re: [Jmap] Question: Mandate core capability on each API call?
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2020 00:54:28 -0000

OK, I've found our previous discussion of this <https://mailarchive.ietf.org/arch/msg/jmap/a37hu-PbJwsV0I0lygcg8nUcuTk/> and it looks like the conclusion then was to require it to be explicit, because it's cleaner if we need to replace it with core2 in the future, rather than have it be "implicit core unless coreX is specified".

So probably we should do an errata just to clarify that it's mandatory to include `"urn:ietf:params:jmap:core"` in the `using` param, and Raphaël you might want to file a bug with lttrs <https://github.com/iNPUTmice/lttrs-android>?

Cheers,
Neil.

v2.23.0 | Report a Bug | By Email