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

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 09 June 2021 03:55 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 9285A3A1125 for <jmap@ietfa.amsl.com>; 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 <jmap@ietfa.amsl.com>; 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 <jmap@ietf.org>; 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 <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: <20210609035455.6E25DF4073A@rfc-editor.org>
Date: Tue, 8 Jun 2021 20:54:55 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Wlh1oofk4uhPvwmaujrh18zjOog>
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 <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 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 <neilj@fastmailteam.com>

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