From nobody Sun Jun 6 23:30:00 2021 Return-Path: X-Original-To: jmap@ietf.org Delivered-To: jmap@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3083A38E5; Sun, 6 Jun 2021 23:29:59 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.30.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <162304739912.25981.11078740944084834646@ietfa.amsl.com> Date: Sun, 06 Jun 2021 23:29:59 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-sharing-00.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2021 06:29:59 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Mail Access Protocol WG of the IETF. Title : JMAP Sharing Author : Neil Jenkins Filename : draft-ietf-jmap-sharing-00.txt Pages : 11 Date : 2021-06-06 Abstract: This document specifies a data model for sharing data between users using JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-sharing/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-jmap-sharing-00.html Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jun 8 20:42:16 2021 Return-Path: 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 E9C153A10E3 for ; Tue, 8 Jun 2021 20:42:04 -0700 (PDT) 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_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 8TcI7-P-m70N for ; Tue, 8 Jun 2021 20:42:00 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC6803A10BA for ; Tue, 8 Jun 2021 20:41:59 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id CF4E9F4073B; Tue, 8 Jun 2021 20:41:28 -0700 (PDT) To: neilj@fastmailteam.com, chris.newman@oracle.com, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, fenton@bluepopcorn.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Cc: neilj@fastmailteam.com, jmap@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20210609034128.CF4E9F4073B@rfc-editor.org> Date: Tue, 8 Jun 2021 20:41:28 -0700 (PDT) Archived-At: Subject: [Jmap] [Technical Errata Reported] RFC8620 (6603) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 03:42:14 -0000 The following errata report has been submitted for RFC8620, "The JSON Meta Application Protocol (JMAP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6603 -------------------------------------- Type: Technical Reported by: Neil Jenkins Section: 5.6 Original Text ------------- In the "upToId" request argument definition: If the sort and filter are both only on immutable properties, this allows the server to omit changes after this point in the results, which can significantly increase efficiency. If they are not immutable, this argument is ignored. In the "removed" response argument definition: If the sort and filter are both only on immutable properties and an "upToId" is supplied and exists in the results, any ids that were removed but have a higher index than "upToId" SHOULD be omitted. In the "added" response argument definition: If the sort and filter are both only on immutable properties and an "upToId" is supplied and exists in the results, any ids that were added but have a higher index than "upToId" SHOULD be omitted. Corrected Text -------------- In the upToId argument definition: The server may be able to omit added or removed items that are after the client's last cached id, making the update more efficient. In the "removed" response argument definition: If an "upToId" is supplied and existed in the old results, any ids that were removed but had a higher index than "upToId" in those results SHOULD be omitted. If the server cannot calculate this, the "upToId" MUST be ignored. In the "added" response argument definition: If an "upToId" is supplied and exists in the new results, any ids that were added but have a higher index than "upToId" SHOULD be omitted. Notes ----- This errata fixes two issues with the upToId definition: 1. Using upToId doesn't require immutable properties in some server implementations; this is an implementation detail. The important thing is it's an optional optimisation that the server can ignore if it does not have the data to calculate it. The text has been updated to reflect this. 2. Clarify that for the "removed" argument, the indexes we are comparing for the upToId optimisation are of the ids in the *old* results. The original text is unclear and seems to imply you might compare with the index of the id in the new results, which will give an incorrect result. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8620 (draft-ietf-jmap-core-17) -------------------------------------- Title : The JSON Meta Application Protocol (JMAP) Publication Date : July 2019 Author(s) : N. Jenkins, C. Newman Category : PROPOSED STANDARD Source : JSON Mail Access Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Tue Jun 8 20:46:28 2021 Return-Path: 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 88A8A3A10BE for ; Tue, 8 Jun 2021 20:46:27 -0700 (PDT) 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_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 ZC3P8y3u5tKC for ; Tue, 8 Jun 2021 20:46:22 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE20E3A10AD for ; Tue, 8 Jun 2021 20:46:22 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 051F8F4073B; Tue, 8 Jun 2021 20:45:52 -0700 (PDT) To: neilj@fastmailteam.com, chris.newman@oracle.com, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, fenton@bluepopcorn.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Cc: neilj@fastmailteam.com, jmap@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20210609034552.051F8F4073B@rfc-editor.org> Date: Tue, 8 Jun 2021 20:45:52 -0700 (PDT) Archived-At: Subject: [Jmap] [Technical Errata Reported] RFC8620 (6604) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 03:46:28 -0000 The following errata report has been submitted for RFC8620, "The JSON Meta Application Protocol (JMAP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6604 -------------------------------------- Type: Technical Reported by: Neil Jenkins Section: 5.6 Original Text ------------- If it *splices out* all ids in the removed array that it has in its cached results, then: removed = [ "id2", "id31", ... ]; fooIds => [ "id1", null, null, "id3", "id4", null, null, null ] and *splices in* (one by one in order, starting with the lowest index) all of the ids in the added array: added = [{ id: "id5", index: 0, ... }]; fooIds => [ "id5", "id1", null, null, "id3", "id4", null, null, null ] Corrected Text -------------- If it *splices out* all ids in the removed array that it has in its cached results, then: removed = [ "id2", "id31", ... ]; fooIds => [ "id1", null, null, "id3", "id4", null, null, null ] and if any of the "removed" ids were not found, invalidates all cached ids after the first gap in the sparse array: fooIds => [ "id1", null, null, null, null, null, null, null ] and *splices in* (one by one in order, starting with the lowest index) all of the ids in the added array: added = [{ id: "id5", index: 0, ... }]; fooIds => [ "id5", "id1", null, null, null, null, null, null, null ] Notes ----- Adds a critical step that was omitted from the description for how a client should process a "/queryUpdates" response. Without this step, the client could end up with ids in incorrect positions in its cached query results. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8620 (draft-ietf-jmap-core-17) -------------------------------------- Title : The JSON Meta Application Protocol (JMAP) Publication Date : July 2019 Author(s) : N. Jenkins, C. Newman Category : PROPOSED STANDARD Source : JSON Mail Access Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Tue Jun 8 20:51:21 2021 Return-Path: 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 B13333A10F6 for ; Tue, 8 Jun 2021 20:51:20 -0700 (PDT) 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_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 E0bSNpRADtR6 for ; Tue, 8 Jun 2021 20:51:16 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 261E23A10F5 for ; Tue, 8 Jun 2021 20:51:12 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 4E8D5F4073B; Tue, 8 Jun 2021 20:50:41 -0700 (PDT) To: neilj@fastmailteam.com, chris.newman@oracle.com, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, fenton@bluepopcorn.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Cc: neilj@fastmailteam.com, jmap@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20210609035041.4E8D5F4073B@rfc-editor.org> Date: Tue, 8 Jun 2021 20:50:41 -0700 (PDT) Archived-At: Subject: [Jmap] [Technical Errata Reported] RFC8620 (6605) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 03:51:21 -0000 The following errata report has been submitted for RFC8620, "The JSON Meta Application Protocol (JMAP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6605 -------------------------------------- Type: Technical Reported by: Neil Jenkins Section: 5.5 Original Text ------------- o position: "UnsignedInt" The zero-based index of the first result in the "ids" array within the complete list of query results. Corrected Text -------------- o position: "UnsignedInt" The zero-based index of the first result in the "ids" array within the complete list of query results. If the "ids" array is empty, the value is undefined and MUST NOT be used by the client. Notes ----- The position response argument in "/query" is only defined when there is at least one id returned in the response. Make it clearer that when there are no ids returned, the client cannot rely on it being any particular value. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8620 (draft-ietf-jmap-core-17) -------------------------------------- Title : The JSON Meta Application Protocol (JMAP) Publication Date : July 2019 Author(s) : N. Jenkins, C. Newman Category : PROPOSED STANDARD Source : JSON Mail Access Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Tue Jun 8 20:55:32 2021 Return-Path: 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 9285A3A1125 for ; Tue, 8 Jun 2021 20:55:30 -0700 (PDT) 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_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 Th2FVxX0G8eN for ; Tue, 8 Jun 2021 20:55:26 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 671BB3A1121 for ; Tue, 8 Jun 2021 20:55:26 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 6E25DF4073A; Tue, 8 Jun 2021 20:54:55 -0700 (PDT) To: neilj@fastmailteam.com, chris.newman@oracle.com, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, fenton@bluepopcorn.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Cc: neilj@fastmailteam.com, jmap@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20210609035455.6E25DF4073A@rfc-editor.org> Date: Tue, 8 Jun 2021 20:54:55 -0700 (PDT) Archived-At: Subject: [Jmap] [Technical Errata Reported] RFC8620 (6606) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 03:55:31 -0000 The following errata report has been submitted for RFC8620, "The JSON Meta Application Protocol (JMAP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6606 -------------------------------------- Type: Technical Reported by: Neil Jenkins Section: 3.3 Original Text ------------- o using: "String[]" The set of capabilities the client wishes to use. The client MAY include capability identifiers even if the method calls it makes do not utilise those capabilities. The server advertises the set of specifications it supports in the Session object (see Section 2), as keys on the "capabilities" property. Corrected Text -------------- o using: "String[]" The set of capabilities the client wishes to use. The client MAY include capability identifiers even if the method calls it makes do not utilise those capabilities. The server advertises the set of specifications it supports in the Session object (see Section 2), as keys on the "capabilities" property. The "urn:ietf:params:jmap:core" capability represents this document and MUST be included in the "using" list. This is to allow a smooth upgrade path for future revisions to the core JMAP specification with different capability identifiers. Notes ----- The original text was unclear on whether the capability for this document (JMAP core) had to be included in the "using" list, or just those of extensions to JMAP core. Clarify that the "core" capability must also be included, and give the rationale. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8620 (draft-ietf-jmap-core-17) -------------------------------------- Title : The JSON Meta Application Protocol (JMAP) Publication Date : July 2019 Author(s) : N. Jenkins, C. Newman Category : PROPOSED STANDARD Source : JSON Mail Access Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Tue Jun 8 21:00:32 2021 Return-Path: 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 7DC533A1149 for ; Tue, 8 Jun 2021 21:00:30 -0700 (PDT) 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_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 7r6B2WJIEEFU for ; Tue, 8 Jun 2021 21:00:25 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1D0B3A1147 for ; Tue, 8 Jun 2021 21:00:25 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id ECAABF4073B; Tue, 8 Jun 2021 20:59:54 -0700 (PDT) To: neilj@fastmailteam.com, chris.newman@oracle.com, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, fenton@bluepopcorn.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Cc: neilj@fastmailteam.com, jmap@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20210609035954.ECAABF4073B@rfc-editor.org> Date: Tue, 8 Jun 2021 20:59:54 -0700 (PDT) Archived-At: Subject: [Jmap] [Technical Errata Reported] RFC8620 (6607) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 04:00:31 -0000 The following errata report has been submitted for RFC8620, "The JSON Meta Application Protocol (JMAP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6607 -------------------------------------- Type: Technical Reported by: Neil Jenkins Section: 5.3 Original Text ------------- [...] In the case of records with references to the same type, the server MUST order the creates and updates within a single method call so that creates happen before their creation ids are referenced by another create/update/destroy in the same call. Corrected Text -------------- [...] In the case of records with references to the same type, the server MUST order the creates and updates within a single method call so that creates happen before their creation ids are referenced by another create/update/destroy in the same call. A record may be updated/destroyed in the same request as it is created. The update/destroy arguments may use creation ids as keys by prefixing the creation id with a "#". Notes ----- Clarify that it's explicitly permitted to update/destroy records created in the same request using the same mechanism as setting foreign keys in records. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8620 (draft-ietf-jmap-core-17) -------------------------------------- Title : The JSON Meta Application Protocol (JMAP) Publication Date : July 2019 Author(s) : N. Jenkins, C. Newman Category : PROPOSED STANDARD Source : JSON Mail Access Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Tue Jun 8 21:02:56 2021 Return-Path: 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 B45753A115F for ; Tue, 8 Jun 2021 21:02:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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.001, RCVD_IN_MSPIKE_WL=0.001, 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=gKkmLcln; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Kgl3CbYY 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 J3cER9mjCTqP for ; Tue, 8 Jun 2021 21:02:49 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AEC43A115C for ; Tue, 8 Jun 2021 21:02:49 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 71D785C0107 for ; Wed, 9 Jun 2021 00:02:43 -0400 (EDT) Received: from imap42 ([10.202.2.92]) by compute5.internal (MEProxy); Wed, 09 Jun 2021 00:02:43 -0400 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=fm2; bh=lHgStii tPnmTudPckdrfeqk7xvm4qo0MuhFzD/+sFng=; b=gKkmLcln6eWDXHRd6szyt0y EtPhl1w9IbxtDE3xh80hjynp8FuGmADJh1gKf0r3P5I128iYwfD9dIvVnuUG6obm VzhFiA50IElNJaGM/v9uZZZdeRD5ETn2NOkH0bgfR1LIIo/jg9NUL82vifxUyZZg NwKq6JEbNYO/TS9HSVfZHNzNeQ01BdFvBwX6T4hXjDmjWM+GeizB/JY3UB1l2Ybi cEbj27eTXbiWtQkDScRcaavj1EAoJ+bwkFLJxv194W3fZUoexXyzVrCs2nh9jZ33 pBhoDE5KMJNrmyAhsJz/r5b+76AkryayOQlsuEYV1PH8Os0NcX3uVkSWpkZZzOQ= = 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=fm3; bh=lHgSti itPnmTudPckdrfeqk7xvm4qo0MuhFzD/+sFng=; b=Kgl3CbYYW3WoXY5UbeY/ki i5zhpksfIvff3/7ZZ4KiJhe6W/fuKvj1La6l2TXYlzEZRUw4TqTCqeOPLLoHZuvu Czo/aVwN4lRgTkYBdMHIj5lP4Z3J5RqzEYmwPTj/Alw8X/rZam1uI3nm4fSKGRRp qirFvBrsiySsDxzue3yS7cVy7Nx7PaUD24xNNUQTAwYcqfnTM3KzORdqx5G2ZiJW le0HZHanptkPJ78txBrOT7tlvgSlfj1UuB1ng8RmlxWMfQYd3Htp8oZofizl340T rV/fWwX97PYyYWJUPBqwjOP7YN612GLxPjb0N+fpo7GBi2vzdr/YEdqP2wZDq79g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedutddgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeevvdetvdduleekhfeghfetfeettdelhfehfeevffevleek uddtudffieevjeevhfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 97275310005F; Wed, 9 Jun 2021 00:02:42 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-800-ga300ffa46a-fm-ubox-20210608.003-ga300ffa4 Mime-Version: 1.0 Message-Id: <3eab9f42-8657-4380-a181-934c1a396acd@dogfood.fastmail.com> In-Reply-To: <82ad0634-847c-4cd3-be8c-e1a6dbba9da5@beta.fastmail.com> References: <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> <82ad0634-847c-4cd3-be8c-e1a6dbba9da5@beta.fastmail.com> Date: Wed, 09 Jun 2021 14:02:41 +1000 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=5273d983e86b408499e2ef72a1fea539 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 04:02:55 -0000 --5273d983e86b408499e2ef72a1fea539 Content-Type: text/plain I have now (finally!) submitted an erratum to clarify this. Please reply to the email thread for the erratum if you have any comments or suggestions for to clarify the text further. Cheers, Neil. --5273d983e86b408499e2ef72a1fea539 Content-Type: text/html
I have now (finally!) submitted an erratum to clarify this. Please reply to the email thread for the erratum if you have any comments or suggestions for to clarify the text further.

Cheers,
Neil.
--5273d983e86b408499e2ef72a1fea539-- From nobody Tue Jun 8 21:04:21 2021 Return-Path: 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 D6ADC3A1168 for ; Tue, 8 Jun 2021 21:04:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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.001, RCVD_IN_MSPIKE_WL=0.001, 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=k/9erIJH; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QsEX8OlJ 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 omRzYD9g3CIZ for ; Tue, 8 Jun 2021 21:04:13 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9C823A1161 for ; Tue, 8 Jun 2021 21:04:13 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1180D5C00E2 for ; Wed, 9 Jun 2021 00:04:11 -0400 (EDT) Received: from imap42 ([10.202.2.92]) by compute5.internal (MEProxy); Wed, 09 Jun 2021 00:04:11 -0400 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=fm2; bh=JJfTmG1 7CgPttG80bcrmpvXpbmlxbcq+1m6rHUcSuGc=; b=k/9erIJHdq86ePpc2eYYcGV mj6huJClN+WmVuCW2G2NFnbNLUqRj+nF1iqHEbQCfqbkhvuw8gezioRD/e/u6GEC WeR4ZDOXPzHv0V82oSkqBmXAPaYuCAM6AAigrvhQFaoWMfpDtXcTOpI7lsmtzBUD aeBW2X6WqQG0ObJ7YOyCIQtp7WMMkpRHBe76a6+8fqIXkvgdUoxNbGd+XmGUy9bt HIKjXIlNWtRZ3lTQgSufCRuzlQw5QINpFyhPJ6xt2H7AG10c9Cz2EknzW6xGvaPs nkg8j6/9RezEwUbw9TXOD0ud7rrF9W1bJzFNIpb292zhB9NQmDBF3OB4TQ811eA= = 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=fm3; bh=JJfTmG 17CgPttG80bcrmpvXpbmlxbcq+1m6rHUcSuGc=; b=QsEX8OlJ+2sy5/4G7bVgVQ jfi0nmG8mOF+nHQEkAXv+p0o+OdwwrUDr605dzBM/cY7cfztc6HK577T6A4fJdd9 xZ4oRMpZiLE3TCFlSDMM4GuQAiqI1x1mpDfIO7qKB02zZUlgh+azBEA7ywKlD1Z8 sJmKTf5hE+EATV1ioOMa3pp4nKSHrDi5TdAfozpJgxMevkFhPqACbkOwPE07PSk+ 3k1q6Zc5JkHoOMtOYeayFFNUZa+WEXD/uPgonbp4DFuHCZvzad+r/UDFbBFSbczz TdZSGyOwY6ledr/rht91w78mQWJMMd8LEJ/dJcx8SCZNxQaVwEBJ9x7X6vW+Ixpg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedutddgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeevvdetvdduleekhfeghfetfeettdelhfehfeevffevleek uddtudffieevjeevhfenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrih hlfhhrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id E2C51310005F; Wed, 9 Jun 2021 00:04:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-800-ga300ffa46a-fm-ubox-20210608.003-ga300ffa4 Mime-Version: 1.0 Message-Id: <799293e3-0a0c-4425-a35e-4de0242b0246@dogfood.fastmail.com> In-Reply-To: <590c785d-7e1a-420e-9f2a-5989e6a76c04@dogfood.fastmail.com> References: <20210526222836.GA1792@eh> <590c785d-7e1a-420e-9f2a-5989e6a76c04@dogfood.fastmail.com> Date: Wed, 09 Jun 2021 14:04:10 +1000 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=628a1decff0f4f9e97f7c8a7fa7c3319 Archived-At: Subject: Re: [Jmap] new JMAP server for prototyping X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 04:04:19 -0000 --628a1decff0f4f9e97f7c8a7fa7c3319 Content-Type: text/plain I have submitted erratas for the issues raised in this thread. There's an email for each one gone on out on this list. Please reply to the email thread for a specific erratum if you have any comments or suggestions to clarify the text further. Cheers, Neil. --628a1decff0f4f9e97f7c8a7fa7c3319 Content-Type: text/html
I have submitted erratas for the issues raised in this thread. There's an email for each one gone on out on this list. Please reply to the email thread for a specific erratum if you have any comments or suggestions to clarify the text further.

Cheers,
Neil.
--628a1decff0f4f9e97f7c8a7fa7c3319-- From nobody Wed Jun 9 15:34:15 2021 Return-Path: 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 848EE3A28DE for ; Wed, 9 Jun 2021 15:34:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=minilop.net 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 JU7TapAsiA4S for ; Wed, 9 Jun 2021 15:34:08 -0700 (PDT) Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 127503A28E2 for ; Wed, 9 Jun 2021 15:34:06 -0700 (PDT) Received: by mail-pl1-x635.google.com with SMTP id h1so5852558plt.1 for ; Wed, 09 Jun 2021 15:34:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=minilop.net; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=nqB0NtdkMvB6uNXEyuQ2ar5GQtIi+0JLzUyg8jQukjY=; b=INTeAe0wphQnDnI+XkLqyMvII86m+TbRbsnSmmxZHVkr/Jj7FRhIV4AKUVdDHG+HxW gmfo0XHCMuGV1yH0LGO4LmMUAyHb52GvIkP+2Mgj5z2LYNmIIp1cYq+vM+azumXJ4nsR xJVEmps0qxS0mUu+GpGZxPeQxwRrD+0X3mluY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=nqB0NtdkMvB6uNXEyuQ2ar5GQtIi+0JLzUyg8jQukjY=; b=N8l9aiNm4dDY6cu8cRl0JiueUIer0YT8YNtKryR1LzHhfDMqlI6l0Ymcw8N0YHv4nq /wPt1ES8lG4b9OWjV4tfA8OxiHQcRc0f9L4E1pzVeHOEOMgLUL+Ii6JUBQc9F757CGDf t6DnpAF9ZFEFn/5t6UAAZp219fTfa7f0I7BcdbYi+OsvNFJP2Lgs0MUjJ1TGHvnEDjgL HqwcZm0dFNOS0sVcAW9d4yKYUvd/FXde9P7zmo/kgWpzLRpMXrB2Un6cnT7I3soLWDkF boxRiaSyGr8phKdiOZ1fgmJ0zIQWW5MxRFWpAOU6Usk7WfOp3eYBleTapQPqrs3rzC8l ygHA== X-Gm-Message-State: AOAM5313BnMSpKuhvZlGonDtyTKeMIUChY1ZF6zNP4Ft55ETOPU/XMhK rj1B1lRKKtNGxkmiiWtyKjKCYa+cq4BSsw== X-Google-Smtp-Source: ABdhPJxYMm+fGJANK7+puXvRk0TVZSsXrMbMzy3dcgsEx8KkNwxYhqvy4ATTq2oGv8fNJ9h2JQQwVg== X-Received: by 2002:a17:90a:ce02:: with SMTP id f2mr12758542pju.45.1623278045391; Wed, 09 Jun 2021 15:34:05 -0700 (PDT) Received: from eh (63-230-166-62.ptld.qwest.net. [63.230.166.62]) by smtp.gmail.com with ESMTPSA id o5sm684171pgn.44.2021.06.09.15.34.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Jun 2021 15:34:04 -0700 (PDT) Received: by eh (sSMTP sendmail emulation); Wed, 09 Jun 2021 15:34:03 -0700 Date: Wed, 9 Jun 2021 15:34:03 -0700 From: Jamey Sharp To: IETF JMAP Mailing List Message-ID: <20210609223403.GE1792@eh> References: <20210526222836.GA1792@eh> <590c785d-7e1a-420e-9f2a-5989e6a76c04@dogfood.fastmail.com> <799293e3-0a0c-4425-a35e-4de0242b0246@dogfood.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <799293e3-0a0c-4425-a35e-4de0242b0246@dogfood.fastmail.com> Archived-At: Subject: Re: [Jmap] new JMAP server for prototyping X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 22:34:13 -0000 On Wed, Jun 09, 2021 at 02:04:10PM +1000, Neil Jenkins wrote: >I have submitted erratas for the issues raised in this thread. There's >an email for each one gone on out on this list. Please reply to the >email thread for a specific erratum if you have any comments or >suggestions to clarify the text further. They all look great to me. Thanks so much! Jamey From nobody Thu Jun 10 07:32:29 2021 Return-Path: X-Original-To: jmap@ietf.org Delivered-To: jmap@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BA9513A4271; Thu, 10 Jun 2021 07:32:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.31.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <162333554369.30322.11332619906198657642@ietfa.amsl.com> Date: Thu, 10 Jun 2021 07:32:23 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-jscontact-vcard-05.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2021 14:32:24 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Mail Access Protocol WG of the IETF. Title : JSContact: Converting from and to vCard Authors : Mario Loffredo Robert Stepanek Filename : draft-ietf-jmap-jscontact-vcard-05.txt Pages : 41 Date : 2021-06-10 Abstract: This document defines how to convert contact information as defined in the JSContact [draft-ietf-jmap-jscontact] specification from and to vCard. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-jscontact-vcard/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-jmap-jscontact-vcard-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-jscontact-vcard-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jun 10 07:55:57 2021 Return-Path: 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 C61173A4333 for ; Thu, 10 Jun 2021 07:55:55 -0700 (PDT) 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, 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 fl6Vb5yVjut7 for ; Thu, 10 Jun 2021 07:55:51 -0700 (PDT) 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 873C63A432F for ; Thu, 10 Jun 2021 07:55:50 -0700 (PDT) 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 47EAD41780 for ; Thu, 10 Jun 2021 16:55:48 +0200 (CEST) To: jmap@ietf.org References: <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> <82ad0634-847c-4cd3-be8c-e1a6dbba9da5@beta.fastmail.com> <3eab9f42-8657-4380-a181-934c1a396acd@dogfood.fastmail.com> X-LINAGORA-Copy-Delivery-Done: 1 From: =?UTF-8?Q?Rapha=c3=abl_Ouazana?= Message-ID: Date: Thu, 10 Jun 2021 16:55:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <3eab9f42-8657-4380-a181-934c1a396acd@dogfood.fastmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2021 14:55:56 -0000 That's fine to me, thanks! Raphaël. Le 09/06/2021 à 06:02, Neil Jenkins a écrit : > I have now (finally!) submitted an erratum to clarify this. Please reply > to the email thread for the erratum if you have any comments or > suggestions for to clarify the text further. > > Cheers, > Neil. > > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap >