[Jmap] [Technical Errata Reported] RFC8620 (6607)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 09 June 2021 04:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 <jmap@ietfa.amsl.com>; 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 <jmap@ietfa.amsl.com>; 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 <jmap@ietf.org>; 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 <rfc-editor@rfc-editor.org>
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: <https://mailarchive.ietf.org/arch/msg/jmap/twiqdZyF7TUEGGy72XweX2tQ2hg>
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 <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: 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 <neilj@fastmailteam.com>

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