[Jmap] [Technical Errata Reported] RFC8620 (5791)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 July 2019 15:56 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 270D8120121 for <jmap@ietfa.amsl.com>; Tue, 23 Jul 2019 08:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 34WNWYaiBDVn for <jmap@ietfa.amsl.com>; Tue, 23 Jul 2019 08:56:27 -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 0AEB9120059 for <jmap@ietf.org>; Tue, 23 Jul 2019 08:56:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CE844B80D4D; Tue, 23 Jul 2019 08:56:16 -0700 (PDT)
To: neilj@fastmailteam.com, chris.newman@oracle.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, brong@fastmailteam.com, fenton@bluepopcorn.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: neil@neiljhaveri.com, jmap@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190723155616.CE844B80D4D@rfc-editor.org>
Date: Tue, 23 Jul 2019 08:56:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/V0U3_wt8uwlHHa1gmr9O6MlPLtU>
X-Mailman-Approved-At: Tue, 23 Jul 2019 10:04:13 -0700
Subject: [Jmap] [Technical Errata Reported] RFC8620 (5791)
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, 23 Jul 2019 15:56:29 -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/eid5791 -------------------------------------- Type: Technical Reported by: Neil Jhaveri <neil@neiljhaveri.com> Section: 2.1 Original Text ------------- "capabilities": { "urn:ietf:params:jmap:core": { "maxSizeUpload": 50000000, "maxConcurrentUpload": 8, "maxSizeRequest": 10000000, "maxConcurrentRequest": 8, "maxCallsInRequest": 32, "maxObjectsInGet": 256, "maxObjectsInSet": 128, "collationAlgorithms": [ "i;ascii-numeric", "i;ascii-casemap", "i;unicode-casemap" ] }, "urn:ietf:params:jmap:mail": {} "urn:ietf:params:jmap:contacts": {}, "https://example.com/apis/foobar": { "maxFoosFinangled": 42 } } Corrected Text -------------- "capabilities": { "urn:ietf:params:jmap:core": { "maxSizeUpload": 50000000, "maxConcurrentUpload": 8, "maxSizeRequest": 10000000, "maxConcurrentRequests": 8, "maxCallsInRequest": 32, "maxObjectsInGet": 256, "maxObjectsInSet": 128, "collationAlgorithms": [ "i;ascii-numeric", "i;ascii-casemap", "i;unicode-casemap" ] }, "urn:ietf:params:jmap:mail": {}, "urn:ietf:params:jmap:contacts": {}, "https://example.com/apis/foobar": { "maxFoosFinangled": 42 } } Notes ----- In the capabilities section of the example Session Resource response, "maxConcurrentRequest" should be "maxConcurrentRequests". In addition, the following line is missing a trailing comma: "urn:ietf:params:jmap:mail": {} 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
- [Jmap] [Technical Errata Reported] RFC8620 (5791) RFC Errata System