IETF Logo Mail Archive

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

Benoit Tellier <btellier@linagora.com> Fri, 27 November 2020 12:03 UTC

Return-Path: <btellier@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 AE9013A0A0B for <jmap@ietfa.amsl.com>; Fri, 27 Nov 2020 04:03:46 -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, 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 pFAhoPuTN-Ou for <jmap@ietfa.amsl.com>; Fri, 27 Nov 2020 04:03:45 -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 037623A09F9 for <jmap@ietf.org>; Fri, 27 Nov 2020 04:03:44 -0800 (PST)
Received: from [10.75.246.15] (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 0F7C03F0A6 for <jmap@ietf.org>; Fri, 27 Nov 2020 13:03:39 +0100 (CET)
To: jmap@ietf.org
X-LINAGORA-Copy-Delivery-Done: 1
From: Benoit Tellier <btellier@linagora.com>
Message-ID: <a769713e-62ef-0eef-b61d-7fa64a8371ce@linagora.com>
Date: Fri, 27 Nov 2020 13:03:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/dhqZpMAhgYxG_BZXx9FVyt5vXSI>
Subject: [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, 27 Nov 2020 12:03:47 -0000

Hello!

First I'm very happy to report I have been successfully using
https://github.com/iNPUTmice/lttrs-android on top to (a slightly
modified james server). This leads to the following code changes:
https://github.com/linagora/james-project/pull/4089

An incompatibility was found: In James we so far mandate the core
capability on every API calls, in addition to extra capabilities (mail,
submission for instance). For my experiments, I relaxed this
requirements. I also think that in doubt clients can always position
this capability to avoid issues.

However my question is: as a server, should I reject api requests not
using `urn:ietf:params:jmap:core` in the using field?

Thanks for answer ;-)

v2.23.0 | Report a Bug | By Email