Re: [Jmap] [Technical Errata Reported] RFC8620 (5791)

Alexey Melnikov <aamelnikov@fastmail.fm> Tue, 23 July 2019 16:35 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <5f4c9627-7fb5-454b-99df-3e42fd18e270@beta.fastmail.com>
Date: Tue, 23 Jul 2019 12:35:36 -0400
Cc: rfc-editor <rfc-editor@rfc-editor.org>, Chris Newman <chris.newman@oracle.com>, Barry Leiba <barryleiba@computer.org>, Adam Roach <adam@nostrum.com>, Bron Gondwana <brong@fastmailteam.com>, Jim Fenton <fenton@bluepopcorn.net>, Neil Jhaveri <neil@neiljhaveri.com>, IETF JMAP Mailing List <jmap@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <17DFDFD2-C54B-4887-87F6-FD72F7B7470C@fastmail.fm>
References: <20190723155616.CE844B80D4D@rfc-editor.org> <5f4c9627-7fb5-454b-99df-3e42fd18e270@beta.fastmail.com>
To: Neil Jenkins <neilj@fastmailteam.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Tyr0S2UCKUGEvrxw2y28jk809hI>
Subject: Re: [Jmap] [Technical Errata Reported] RFC8620 (5791)
Precedence: list

> On 23 Jul 2019, at 12:33, Neil Jenkins <neilj@fastmailteam.com> wrote:
> 
> I can verify this errata report is correct. What is the process to approve?

I need to login and approve.
> 
> Neil.
> 
>> On Tue, 23 Jul 2019, at 11:56, RFC Errata System wrote:
>> 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": {}
>

Re: [Jmap] [Technical Errata Reported] RFC8620 (5… Neil Jenkins
Re: [Jmap] [Technical Errata Reported] RFC8620 (5… Alexey Melnikov