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

Raphaël Ouazana <rouazana@linagora.com> Tue, 01 December 2020 10:37 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 55E653A10CC for <jmap@ietfa.amsl.com>; Tue, 1 Dec 2020 02:37:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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, URIBL_BLOCKED=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 wmVUo5uFc5Hg for <jmap@ietfa.amsl.com>; Tue, 1 Dec 2020 02:37:13 -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 639783A03EC for <jmap@ietf.org>; Tue, 1 Dec 2020 02:37:12 -0800 (PST)
Received: from [10.75.246.26] (reverse.completel.net [92.103.166.6]) (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 458B03F3C2 for <jmap@ietf.org>; Tue, 1 Dec 2020 11:37:08 +0100 (CET)
To: jmap@ietf.org
References: <a769713e-62ef-0eef-b61d-7fa64a8371ce@linagora.com> <8df9abc8-4c5d-47da-9966-b9646561e286@dogfood.fastmail.com>
X-LINAGORA-Copy-Delivery-Done: 1
From: =?UTF-8?Q?Rapha=c3=abl_Ouazana?= <rouazana@linagora.com>
Message-ID: <17a0c929-66bc-71f8-54bd-cbf4faa8181e@linagora.com>
Date: Tue, 1 Dec 2020 11:37:07 +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: <8df9abc8-4c5d-47da-9966-b9646561e286@dogfood.fastmail.com>
Content-Type: multipart/alternative; boundary="------------1F5C16088F4952037120AB85"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/D_MBfAvAhAGX0ed8wFlgALzBk2o>
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, 01 Dec 2020 10:37:15 -0000

Hello,

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.

Raphaël.

Le 01/12/2020 à 05:18, Neil Jenkins a écrit :
> Hi Benoit,
>
> Good question! I thought we had specified this, but I can't see it in 
> the final draft. I don't see any particular downside to making it 
> optional, but perhaps someone else has an argument as to why it should 
> be mandatory? Whatever we decide, it is probably worth an erratum for 
> the benefit of future implementors.
>
> Neil.
>
> _______________________________________________
> Jmap mailing list
> Jmap@ietf.org
> https://www.ietf.org/mailman/listinfo/jmap