IETF Logo Mail Archive

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

Raphaël Ouazana <rouazana@linagora.com> Fri, 04 December 2020 13:08 UTC

Return-Path: <rouazana@linagora.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 258423A0C8E for <jmap@ietfa.amsl.com>; Fri, 4 Dec 2020 05:08:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Ix5cqSvOXrMf for <jmap@ietfa.amsl.com>; Fri, 4 Dec 2020 05:08:18 -0800 (PST)
Received: from smtp.linagora.com (smtp.linagora.com [54.36.8.78]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D6313A0C88 for <jmap@ietf.org>; Fri, 4 Dec 2020 05:08:17 -0800 (PST)
Received: from [192.168.0.37] (91-168-246-100.subs.proxad.net [91.168.246.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id 3712D3FE64 for <jmap@ietf.org>; Fri, 4 Dec 2020 14:08:14 +0100 (CET)
To: jmap@ietf.org
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>
X-LINAGORA-Copy-Delivery-Done: 1
From: Raphaël Ouazana <rouazana@linagora.com>
Message-ID: <6252ac04-caf9-6c32-eb29-8f075851dffc@linagora.com>
Date: Fri, 04 Dec 2020 14:08:09 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <722e4258-1b8a-4b43-9a1a-2b8b910484b9@beta.fastmail.com>
Content-Type: multipart/alternative; boundary="------------31BC74F98D78A5C9421E5772"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/G05dux-UB2zJhPyVIVERwXT34MU>
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: Fri, 04 Dec 2020 13:08:20 -0000

Le 04/12/2020 à 06:19, Neil Jenkins a écrit :
> On Tue, 1 Dec 2020, at 21:37, Raphaël Ouazana wrote:
>>
>> What about:
>>
>> The server MUST only follow the specifications that are opted into 
>> and behave as though it does not implement anything else when 
>> processing a request.
>>
>
> Sure, this applies to anything other than the core spec. But if you 
> are obeying this text, you are already implementing RFC8620 so it 
> would be a bit of a circular argument to imply that this means you 
> must include the core capability in the using array in order to 
> support 8620!


For now yes but this is also "for compatibility with future versions of 
JMAP". If a future client wants to communicate with a future server, it 
would have to use "urn:ietf:params:jmapv2:core" and would be fine to not 
have "urn:ietf:params:jmap:core" taken by default, no?

Raphaël.

v2.23.0 | Report a Bug | By Email