From nobody Mon Jul 1 19:49:53 2019 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 CF2831200D7 for ; Mon, 1 Jul 2019 19:49:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=eSWdPfCB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hXr+k8k9 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 GEaNwu_2hfmr for ; Mon, 1 Jul 2019 19:49:49 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80111201BC for ; Mon, 1 Jul 2019 19:49:48 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E308D21E44 for ; Mon, 1 Jul 2019 22:49:47 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Mon, 01 Jul 2019 22:49:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:subject :content-type; s=fm3; bh=63pYLJoq3pzGRLsrgPKsgqFINQu+Fa66J9Lm0L6 6Xfg=; b=eSWdPfCBbD25kUZ5/XN0jJXvWreWGXIFtCxb64AdXLH7ns5Dk9VLwQF +lDWqha8HGCC0MSK6af5NxAaIQT3/Jo9axtkDCdTPLTtbhfuQisJ1kroCyKLggPT Foi2z2MjkJHCRyie0zj2h35hACVjKf23ACcW+yPjNodrHngOLe2LX8qZ8M2jh9Mm eHWqwbTNnSru+Z3YghKMJoYOkgqZRG7/8WPDCJF/tFDJsc/eL94aR4JhDTEETeEt HhKGDAt4LzSICemknBMlFLPtTH9iTvQpwLdSTty3Bc/HEHPCAE76uW/7WHkKWROJ Hr+PDvFkyJQzPfKfBRKzFIdJvyLc8+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=63pYLJoq3pzGRLsrgPKsgqFINQu+F a66J9Lm0L66Xfg=; b=hXr+k8k9MGq48naOTQl4rcJD62chBZGO5gWldvPFwX98r SWDgKzrm63G+JgD9nVrC0qcedTgOyt+hz3exqPCsO33gFMYxHrnoEMt3VTPeUSG0 gYVBWP1np97YHML9j0tLTziWCODVxto9e8Teez3tDt7Gl93QgY+iwy7jTqiiLf+E 5c+uhrVxTtAf+Ce7/fEMJczRAYWjDytoZospkwpd+YhSA/d5vXWOzWgs4ya/LI0m hLEW4cla4Q1yib/K39MOAlCxt4A5EnZkm6Ft9XXPLsaljsbH01VCySKirEIYbY3H dABFalo3f+Si+5batzhyGP2SSq0U2T1s9hE8sYekg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrvdejgdeiudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhlucfl vghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqnecurf grrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtgho mhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9615A180091; Mon, 1 Jul 2019 22:49:47 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-731-g19d3b16-fmstable-20190627v1 Mime-Version: 1.0 Message-Id: Date: Tue, 02 Jul 2019 12:49:47 +1000 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=3ea2d782c0d7426bbc4ca409ac6c64fc Archived-At: Subject: [Jmap] Mailbox/set onDestroyRemoveMessages argument 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: Tue, 02 Jul 2019 02:49:51 -0000 --3ea2d782c0d7426bbc4ca409ac6c64fc Content-Type: text/plain Hi all, In reviewing the final edits for the JMAP Mail document, I realised the extra argument to Mailbox/set should have been renamed from `onDestroyRemoveMessages` to `onDestroyRemoveEmails` for consistency with the terminology used everywhere else. I have done this, but as it is a semantic change I am notifying the list in case anyone has any objection. Cheers, Neil. --3ea2d782c0d7426bbc4ca409ac6c64fc Content-Type: text/html
Hi all,

In reviewing the final edits for the JMAP Mail document, I realised the extra argument to Mailbox/set should have been renamed from onDestroyRemoveMessages to onDestroyRemoveEmails for consistency with the terminology used everywhere else. I have done this, but as it is a semantic change I am notifying the list in case anyone has any objection.

Cheers,
Neil.
--3ea2d782c0d7426bbc4ca409ac6c64fc-- From nobody Fri Jul 5 18:59:19 2019 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 EC85F120145; Fri, 5 Jul 2019 18:59:09 -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: 6.98.2 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <156237834989.21757.11466738476771239567@ietfa.amsl.com> Date: Fri, 05 Jul 2019 18:59:09 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-websocket-02.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: Sat, 06 Jul 2019 01:59:10 -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 : A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket Author : Kenneth Murchison Filename : draft-ietf-jmap-websocket-02.txt Pages : 12 Date : 2019-07-05 Abstract: This document defines a binding for the JSON Meta Application Protocol (JMAP) over a WebSocket transport layer. The WebSocket binding for JMAP provides higher performance than the current HTTP binding for JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-websocket/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-websocket-02 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-websocket-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-websocket-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jul 8 08:57:37 2019 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 AC6431200A4; Mon, 8 Jul 2019 08:57:35 -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: 6.98.3 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <156260145563.826.4810817574787450987@ietfa.amsl.com> Date: Mon, 08 Jul 2019 08:57:35 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-smime-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, 08 Jul 2019 15:57:36 -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 : Extensions to JMAP for S/MIME signature verification Author : Alexey Melnikov Filename : draft-ietf-jmap-smime-00.txt Pages : 5 Date : 2019-07-08 Abstract: This document specifies extension to JMAP for returning S/MIME signature verification status. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-smime/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-smime-00 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-smime-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jul 14 18:53:40 2019 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 C3543120163 for ; Sun, 14 Jul 2019 18:53:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=d3LQiNS3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=esPjHkgp 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 jZjgVfRF7aO3 for ; Sun, 14 Jul 2019 18:53:36 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EB0212014E for ; Sun, 14 Jul 2019 18:53:36 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 96C0922131; Sun, 14 Jul 2019 21:53:35 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Sun, 14 Jul 2019 21:53:35 -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:cc:subject:content-type; s=fm3; bh=3BdX G/iJ2q/yhZiO5xxlddmauGiPjb5lpcIPUqlH9zk=; b=d3LQiNS3i7QmQV0NPWcZ TKMcXWbxW2orNa/lWTq3J8qcBOLVE+stEx+n+Ty9GTZ/B680s57Dytdmfvhfoy7P Fv4JKYS0csWK2QBxkjfRFPRqiqolKvN0eJoTq7H5FLm4526G52bpOB81oFw7sfKz Gc5JdDSCbQjjXXvcHcDKSWsPJipfkAXrYWa2sQuVZqAe7j6o9RNf5gAUszdlxH6P oTPUL6YkeHY7B9J0EhF9t+/zmB7dceHwv1mufMG+MkUrVwTZI3pcd9PalGx6J74N v3M1TO8cQMTg3sR/I2/kY0O4DvBTLdIfFPygUp7kBdvBuVxSqhlF7/W6BXDYAznI Ng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=3BdXG/ iJ2q/yhZiO5xxlddmauGiPjb5lpcIPUqlH9zk=; b=esPjHkgp7JA3sNLDS89M5J 84oUlrrIqkAhZvK0vwMCV++kca0wjD4xpUARHfKl0yIgBrJL04e+iMfZ2V35Bjxs adm/apZaPgoWCIiBjeFDuO6MOSMhSLObl19/iNea0FThpi90LPjQXvrD0fEjPzfe ORiCCSZcPSBv5m55UBnuA+wIQGWKoAH13TUX0mkl3P8UddV4K5Re3fYNyD0y8lxf 6Oc3HPc+lVh5yiyIRVagcQyE+2qBelsVVJQcqKwlRsyiJBq6NL8fkllRbkp1gCcv KXBtVcSwOeLYgjvK3pSAftkvDw8Gs3UoGwUXDSahNWSwnesARmUyFgZttd1lW9rw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrheejgddvgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhl ucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqne curfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmhdr tghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id DEFDB18A053; Sun, 14 Jul 2019 21:53:34 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-731-g19d3b16-fmstable-20190627v1 Mime-Version: 1.0 Message-Id: <13dfd724-1bd2-40cb-b9ed-171189876c3f@beta.fastmail.com> In-Reply-To: <1ddd3a8f0763f028bae89ace0e33081e@linagora.com> References: <155197652116.24727.17736633253141543762@ietfa.amsl.com> <879444dd-28a7-4661-a057-e2f4d142eda3@beta.fastmail.com> <1ddd3a8f0763f028bae89ace0e33081e@linagora.com> Date: Mon, 15 Jul 2019 11:53:34 +1000 From: "Neil Jenkins" To: "Raphael OUAZANA" Cc: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=fd4c94aafca54d23b0b621afcd420135 Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-mdn-01.txt 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: Mon, 15 Jul 2019 01:53:39 -0000 --fd4c94aafca54d23b0b621afcd420135 Content-Type: text/plain Hi Raphael, Sorry I missed replying to this before. In answer to your questions: > >> The client SHOULD NOT issue a sendMDN request if the message has > >> the > >> "$MDNSent" keyword set. In this case, the server MUST reject the > >> submission with a standard "forbiddenToSend" SetError. > > > > I don't think this should be a forbiddenToSend error; that implies the > > user does not have permission to send. An alreadyExists error might be > > appropriate, or some kind of new "precondition-failed" type error. > > I wrote it in the sense of forbidden by the RFC: > [...]In any case, in the presence of the $MDNSent keyword, > the client MUST ignore all other flags or keywords for the > purpose of generating an MDN and MUST NOT send the MDN. > > AlreadyExists seems misleading as the user could just not want to send > the MDN, and in this case it will never exist. You mean the user set an `$MDNSent` flag but didn't send the MDN before? > Maybe AlreadyProcessed or something like that then? That would be OK, although I still think `alreadyExists` is a reasonable mapping. > >> o *created*: "String[EmailSubmission]" A map of creation id > >> (client- > >> specified) to an email sent from the referenced properties. > > > > The type says this is a map to EmailSubmission objects, but the > > description says it is a map to an Email. Which is it? > > I wrote a map to "an email sent [...]". Maybe my English is not good > enough, but for me an email sent means an EmailSubmission. How could I > clarify? I would write "an EmailSubmission object" instead of "an email sent". It's unclear to me exactly which properties you expect to be returned for the EmailSubmission object in this case. Is it creating a whole EmailSubmission record? This seems overkill and also a poor match: almost none of the properties are relevant or useful, and indeed would be confusing if you got this back with other EmailSubmission objects representing user email submission. I think it would be better if it just returned a success/failure response, without creating an EmailSubmission object. The other, probably better and more JMAP-y way of modelling this would be to just use a standard "MDN/set" to create an MDN object, separate from the EmailSubmission data type entirely. There does not have to be /get, /query etc. methods. > >> EMAILSUBMISSION/PARSEMDN > > > > This method is nothing to do with EmailSubmission really. Probably > > should be called MDN/PARSE. > > Probably, I hesitated because like this all the MDN stuff is related to > EmailSubmission, but I can write a MDN/parse if you think it's better. Yes, I think this would definitely be better. So this spec then defines the MDN data type, plus MDN/set and MDN/parse methods. Cheers, Neil. --fd4c94aafca54d23b0b621afcd420135 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi Raphael,
=

Sorry I missed replying to this before. In ans= wer to your questions:

>> The client SHOULD NOT issue a sendMDN request i= f the message has
>> the
>> "$MD= NSent" keyword set.  In this case, the server MUST reject the
>> submission with a standard "forbiddenToSend" SetError.=

> I don't think this should b= e a forbiddenToSend error; that implies the
> user does= not have permission to send. An alreadyExists error might be
<= div>> appropriate, or some kind of new "precondition-failed" type err= or.

I wrote it in the sense of forbidden by= the RFC:
        [...]= In any case, in the presence of the $MDNSent keyword,
&nbs= p;       the client MUST ignore all other = flags or keywords for the
     &n= bsp;  purpose of generating an MDN and MUST NOT send the MDN.

AlreadyExists seems misleading as the user could= just not want to send 
the MDN, and in this case it = will never exist.

You mean th= e user set an $MDNSent flag but didn't send the MDN before?

Maybe Already= Processed or something like that then?
<= br>
That would be OK, although I still think alreadyExists is a reasonable mapping.

>> o  *created*: "String[EmailSubmission= ]" A map of creation id
>> (client-
&g= t;> specified) to an email sent from the referenced properties.

> The type says this is a map to Em= ailSubmission objects, but the
> description says it is= a map to an Email. Which is it?

I wrote a = map to "an email sent [...]". Maybe my English is not good 
enough, but for me an email sent means an EmailSubmission. How co= uld I 
clarify?

=
I would write "an EmailSubmission object" instead of "an email sent= ".

It's unclear to me exactly which propert= ies you expect to be returned for the EmailSubmission object in this cas= e. Is it creating a whole EmailSubmission record? This seems overkill an= d also a poor match: almost none of the properties are relevant or usefu= l, and indeed would be confusing if you got this back with other EmailSu= bmission objects representing user email submission.

<= /div>
I think it would be better if it just returned a success/failu= re response, without creating an EmailSubmission object. The other, prob= ably better and more JMAP-y way of modelling this would be to just use a= standard "MDN/set" to create an MDN object, separate from the EmailSubm= ission data type entirely. There does not have to be /get, /query etc. m= ethods.

>> EMAILSUBMISSION/PARSEMDN

> This method is nothing to do with EmailSubmission really. Probabl= y
> should be called MDN/PARSE.

Probably, I hesitated because like this all the MDN stuff is relat= ed to 
EmailSubmission, but I can write a MDN/parse i= f you think it's better.

Yes, = I think this would definitely be better. So this spec then defines the M= DN data type, plus MDN/set and MDN/parse methods.

Cheers,
Neil.
--fd4c94aafca54d23b0b621afcd420135-- From nobody Thu Jul 18 09:16:02 2019 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 96EC0120835; Thu, 18 Jul 2019 09:15:59 -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 zxmBs4hYPTHw; Thu, 18 Jul 2019 09:15:57 -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 C68EC120830; Thu, 18 Jul 2019 09:15:57 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 801F1B80C83; Thu, 18 Jul 2019 09:15:52 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, jmap@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20190718161552.801F1B80C83@rfc-editor.org> Date: Thu, 18 Jul 2019 09:15:52 -0700 (PDT) Archived-At: Subject: [Jmap] =?utf-8?q?RFC_8620_on_The_JSON_Meta_Application_Protocol_?= =?utf-8?b?KEpNQVAp?= 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, 18 Jul 2019 16:16:00 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8620 Title: The JSON Meta Application Protocol (JMAP) Author: N. Jenkins, C. Newman Status: Standards Track Stream: IETF Date: July 2019 Mailbox: neilj@fastmailteam.com, chris.newman@oracle.com Pages: 90 Characters: 180653 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-jmap-core-17.txt URL: https://www.rfc-editor.org/info/rfc8620 DOI: 10.17487/RFC8620 This document specifies a protocol for clients to efficiently query, fetch, and modify JSON-based data objects, with support for push notification of changes and fast resynchronisation and for out-of- band binary data upload/download. This document is a product of the JSON Mail Access Protocol Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Fri Jul 19 14:24:12 2019 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 1D0F612086D for ; Fri, 19 Jul 2019 14:24:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.998 X-Spam-Level: X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 AHX154r0vUlb for ; Fri, 19 Jul 2019 14:24:08 -0700 (PDT) Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 E645012018A for ; Fri, 19 Jul 2019 14:24:07 -0700 (PDT) Received: by mail-pf1-x42f.google.com with SMTP id r7so14700467pfl.3 for ; Fri, 19 Jul 2019 14:24:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:message-id:date:to:mime-version; bh=HflNmaCN3QQ0Ib0VxUA+XAzkSgztwNbrhWIClJ+S+aw=; b=RHVX4xDRhvMRggKCzsgrdoUbaeuWaQIB+CemBVzwT6+V5BjIlW4THOWGEDo8+zQem8 HaoMWtHuFW3bUpLl3LyFD96JGtERaZNILyL4lc01xyw65fUDmk43D7gVVGGnj/+zF5vN B44JideFch5kYqe483XgZkdfil1ZoNLo6tSw2TKPqsVMLQonbejfJ0BRPTOUT4ZONO1l wmUcWe2rXxuqiMO7V73nIUymhUWX8Y/yn/gcjmp+GSBYCIg5Y7u7fn7hW6OK8eo9RlOq C99XVKc/1Bce2Db08U+b7z2OjSfNgAytdbQtRsIBgC9Xb7upi68uov/bAkIHVbWzM5T9 7PGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:message-id:date:to:mime-version; bh=HflNmaCN3QQ0Ib0VxUA+XAzkSgztwNbrhWIClJ+S+aw=; b=OndDDkI5i/46q32ZjLD/PnHdChUki1ZicxqeegSLz4pP0amfcBLwwYiyjvlsHN3Wwo iCjVGRuXYhiujhcd64sd1IzbFDz375vyklvDus7Kx5t63TVSNF0JKTJXY9iO8wl9pLca 8Pktvbh3jpMmkCQa8bQpLOjGZL0gA2q2qYYgghFGx7wzqnwARJMKeIlC4XLsr60wB59J 2aF7SYGgB+X6gWyn74BIgnupg0JOUMQYGz6xwyvccfi1KLKbOV003X7Y2yFqmfiyY2aZ GTuvD36F1jLrYvEpdnWIyHzAvkLyPfO3/mkjQW1l0cOvRW4XvoKQsPvbUsUXwZm7YSYz CWyg== X-Gm-Message-State: APjAAAVkdvGBn/TxCyw+KU+hr6XR2ELEHTlUT6l1rUfRNLq81tTkHL9P 9tEX1QwD7BT36ynt4AXiHMCEh2VmPg0= X-Google-Smtp-Source: APXvYqxJoJoSb2Gr2RJYMk8lEPJ9FDxS349mOJ1mSlAZXLGhYvq0G+HzyLuvB67AMSvZFoKZhQV7kQ== X-Received: by 2002:a17:90a:26ea:: with SMTP id m97mr60229566pje.59.1563571447181; Fri, 19 Jul 2019 14:24:07 -0700 (PDT) Received: from [10.8.44.98] ([199.73.114.148]) by smtp.gmail.com with ESMTPSA id l31sm56859341pgm.63.2019.07.19.14.24.06 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 19 Jul 2019 14:24:06 -0700 (PDT) From: Michael Toomim Content-Type: multipart/alternative; boundary="Apple-Mail=_46A2AA98-FE65-4CE1-A266-4AA906FE3A99" Message-Id: <9D024982-AC44-45D7-ABCF-0A8936B06E30@gmail.com> Date: Fri, 19 Jul 2019 14:23:59 -0700 To: jmap@ietf.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Archived-At: Subject: [Jmap] Braid: Synchronization for HTTP 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: Fri, 19 Jul 2019 21:24:10 -0000 --Apple-Mail=_46A2AA98-FE65-4CE1-A266-4AA906FE3A99 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, I am involved with Braid=E2=80=94an extension to HTTP that adds state = synchronization=E2=80=94which I believe addresses much of JMAP's = synchronization problem, but at a lower level of the protocol stack. Braid's development could certainly benefit from the experience and = expertise of the JMAP working group. Could someone from JMAP review it? = In a future world, I could imagine JMAP using Braid. The first draft of the Braid spec was just published here: https://tools.ietf.org/html/draft-toomim-braid-00 = Abstract: Braid is an extension to HTTP, which gives it the ability to synchronize = changing state, rather than just transfer it. Braid integrates the power = of Operational Transform and CRDTs with the web, improving network = performance and robustness, and enabling peer-to-peer web applications. At the same time, Braid creates an open standard for the dynamic = internal state of websites. Programmers can access state uniformly, = whether local or on another website. This creates a separation of UI = from State, and allows any user to edit or choose their own UI for any = website's state. Additional resources are at https://braid.news . Thank you! I will also be in Montreal and would be very happy to discuss = this in person. Michael > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: New Version Notification for draft-toomim-braid-00.txt > Date: July 8, 2019 at 4:55:28 PM PDT > To: "Michael Toomim" >, = "Rafie Walker" > >=20 >=20 > A new version of I-D, draft-toomim-braid-00.txt > has been successfully submitted by Michael Toomim and posted to the > IETF repository. >=20 > Name: draft-toomim-braid > Revision: 00 > Title: The Braid Protocol: Synchronization for HTTP > Document date: 2019-07-08 > Group: Individual Submission > Pages: 15 > URL: = https://www.ietf.org/internet-drafts/draft-toomim-braid-00.txt = > Status: https://datatracker.ietf.org/doc/draft-toomim-braid/ = > Htmlized: https://tools.ietf.org/html/draft-toomim-braid-00 = > Htmlized: = https://datatracker.ietf.org/doc/html/draft-toomim-braid = >=20 >=20 > Abstract: > Braid is a proposal for an extension to HTTP that transforms it from > a state *transfer* protocol into a state *synchronization* protocol. > Braid puts the power of Operational Transform and CRDTs onto the web, > improving network performance and robustness, and enabling > peer-to-peer web applications. >=20 > At the same time, Braid creates an open standard for the dynamic > internal state of websites. Programmers can access state uniformly, > whether local or on another website. This creates a separation of UI > from State, and allows any user to edit or choose their own UI for = any > website's state. >=20 > We have a working prototype of the Braid, and have deployed it with > production websites. This memo describes the protocol, how it > differs from prior versions of HTTP, and a plan to deploy it in a > backwards-compatible way, where web developers can opt into the new > synchronization features without breaking the rest of the web. >=20 >=20 >=20 >=20 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org = . >=20 > The IETF Secretariat --Apple-Mail=_46A2AA98-FE65-4CE1-A266-4AA906FE3A99 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi all,

I am involved with Braid=E2=80=94an extension to HTTP that = adds state synchronization=E2=80=94which I = believe addresses much of JMAP's synchronization problem, but at a = lower level of the protocol stack.

Braid's development could certainly = benefit from the experience and expertise of the JMAP working group. = Could someone from JMAP review it? In a future world, I could imagine = JMAP using Braid.

The first draft of the Braid spec was just published = here:


Abstract:
Braid is an extension to HTTP, = which gives it the ability to synchronize changing state, rather than just transfer it. Braid integrates the power of = Operational Transform and CRDTs with the web, improving network = performance and robustness, and enabling peer-to-peer web = applications.

At the same time, Braid creates an open = standard for the dynamic internal state of websites. =  Programmers can access state uniformly,  whether local = or on another website.  This creates a separation of UI from = State, and allows any user to edit or choose their own UI for = any website's state.

Additional = resources are at https://braid.news.

Thank you! I will also be in Montreal = and would be very happy to discuss this in person.

Michael

Begin forwarded message:

Subject: New Version Notification for draft-toomim-braid-00.txt
Date: July 8, 2019 at 4:55:28 PM PDT
To: "Michael Toomim" <toomim@gmail.com>, "Rafie Walker" <slickytail.mc@gmail.com>


A new version = of I-D, draft-toomim-braid-00.txt
has been successfully = submitted by Michael Toomim and posted to the
IETF = repository.

Name: = draft-toomim-braid
Revision: 00
Title: The Braid Protocol: Synchronization for HTTP
Document date: 2019-07-08
Group: Individual Submission
Pages: 15
URL: =            https://www.ietf.org/internet-drafts/draft-toomim-braid-00.txt<= /a>
Status: =         
https://datatracker.ietf.org/doc/draft-toomim-braid/
Htmlized:       https://tools.ietf.org/html/draft-toomim-braid-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-toomim-braid

Abstract:
 Braid is a proposal for an extension to HTTP that = transforms it from
 a state *transfer* protocol into = a state *synchronization* protocol.
 Braid puts the = power of Operational Transform and CRDTs onto the web,
 improving network performance and robustness, and = enabling
 peer-to-peer web applications.

 At the same time, Braid creates an open = standard for the dynamic
 internal state of websites. =  Programmers can access state uniformly,
 whether = local or on another website.  This creates a separation of UI
 from State, and allows any user to edit or choose their = own UI for any
 website's state.

 We have a working prototype of the Braid, and have = deployed it with
 production websites.  This = memo describes the protocol, how it
 differs from = prior versions of HTTP, and a plan to deploy it in a
 backwards-compatible way, where web developers can opt = into the new
 synchronization features without = breaking the rest of the web.






Please note that it may take a couple of minutes from the = time of submission
until the htmlized version and diff are = available at tools.ietf.org.

The IETF = Secretariat
= --Apple-Mail=_46A2AA98-FE65-4CE1-A266-4AA906FE3A99-- From nobody Sat Jul 20 14:03:27 2019 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 56479120256 for ; Sat, 20 Jul 2019 14:03:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=fNWEJthK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=UtL1skIZ 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 1xdX2n5OUrJT for ; Sat, 20 Jul 2019 14:03:17 -0700 (PDT) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE5B6120236 for ; Sat, 20 Jul 2019 14:03:17 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id DEABF3E7 for ; Sat, 20 Jul 2019 17:03:16 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Sat, 20 Jul 2019 17:03:17 -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=fm3; bh=aIUwKnB QDH8r8W+ZMrYEoumLqYFXXK2qD6WXq3SgP6Y=; b=fNWEJthK9Tl606yTwiLHoun uQ/j5vCXeIkXcvFJ/NPBwwn/cwBqqFFIBLMJuCbOq73vXsZEbdSszaNZBlJ9CfWx nptSYqKIGHGJKrPtYFBF979rqshhQjt8iIPlc8iNY4yYM76ne8ahZo2Wt3KLlcyq hYeWOg1LXtVknmSTh1i37TjVekswmYNlYQuz13M5dYzeEzm3ujEX/1kP8M94Xh8l /hE7vjGkTswKlOIHogI3kgI1kTU8jIEIZFwtM7wBF/dXmHKKjKX+aF1G/XbxJ2Lp Xu/AaQ7JIqcUnuTFn4HeROXlsy5d3H0k8KE1sxNEqwHoqxjapvp1D3IPC35eoEw= = 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=aIUwKn BQDH8r8W+ZMrYEoumLqYFXXK2qD6WXq3SgP6Y=; b=UtL1skIZOAg2ugpWslyzjf S+9suaLkJvSClsQUv18hnYP4+uJcU9nB9y9lmR9ip606QzuS3nUZLOM9Mx2XSG44 8xEz47sovwG4qN+VYeGm7DFCd1dkzwCJFgSeDr7jztu0iOc3OTy3Mym9oNMM0BrW bjpQKkN1YHNQNYOD07XrL5NRFIbHhgscWHbO8Q0oUYTgmtm3EaP2PC6YJ87ze7Fy 9iktPyQNHsNdcLVc0hSJQosonrS64y7cdIchK4AuweT7AdvlY9mLv73kVYD9Dczk dZ1rvQlSCjgVaiG84ToB/nvQxENQpMAHmFD2YOWYZnxAalBCbITciRmVRTXpy5FA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrieelgdduieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucfrrghrrghmpehmrghilhhfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghm rdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 064B3185115; Sat, 20 Jul 2019 17:03:16 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-736-gdfb8e44-fmstable-20190718v2 Mime-Version: 1.0 Message-Id: <0404e38e-a183-424a-ae5a-5390ce6d0acf@beta.fastmail.com> In-Reply-To: <9D024982-AC44-45D7-ABCF-0A8936B06E30@gmail.com> References: <9D024982-AC44-45D7-ABCF-0A8936B06E30@gmail.com> Date: Sat, 20 Jul 2019 17:03:15 -0400 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=3d99f92aec1640a0abd86268759dec3a Archived-At: Subject: Re: [Jmap] Braid: Synchronization for HTTP 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: Sat, 20 Jul 2019 21:03:27 -0000 --3d99f92aec1640a0abd86268759dec3a Content-Type: text/plain Hi Michael, I've read through the RFC and this seems from my initial reading to be a bit more of a framework than specific model, but happy to talk about it if you want to come find me in the hackathon this weekend. I'm on the "Email" table. Cheers, Neil. --3d99f92aec1640a0abd86268759dec3a Content-Type: text/html
Hi Michael,

I've read through the RFC and this seems from my initial reading to be a bit more of a framework than specific model, but happy to talk about it if you want to come find me in the hackathon this weekend. I'm on the "Email" table.

Cheers,
Neil.
--3d99f92aec1640a0abd86268759dec3a-- From nobody Mon Jul 22 01:31:45 2019 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 757B1120191; Mon, 22 Jul 2019 01:31:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <156378430323.27951.4849868258181534215@ietfa.amsl.com> Date: Mon, 22 Jul 2019 01:31:43 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-mdn-02.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, 22 Jul 2019 08:31:44 -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 : Handling Message Disposition Notification with JMAP Author : Raphaƫl Ouazana Filename : draft-ietf-jmap-mdn-02.txt Pages : 9 Date : 2019-07-22 Abstract: This document specifies a data model for handling [RFC8098] MDN messages with a server using JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-mdn/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-mdn-02 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-mdn-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-mdn-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jul 23 09:34:04 2019 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 15425120387 for ; Tue, 23 Jul 2019 09:33:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=r+G1PP8z; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=YbS68uUx 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 YB5uI7NiQ2Bo for ; Tue, 23 Jul 2019 09:33:51 -0700 (PDT) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1E361203A0 for ; Tue, 23 Jul 2019 09:33:51 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 98379663; Tue, 23 Jul 2019 12:33:50 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Tue, 23 Jul 2019 12:33:51 -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:cc:subject:content-type; s=fm3; bh=5bvN foA+xSwMFk7fPrIY++T4QVkEFzTezrPZMNX7if4=; b=r+G1PP8zxoKOVDcs36Yf f6oLbmY/x7O/cFco8o57KjKQ/MUOshxQMs3AbsCBScsHkTMabfPTkm0iPd8EjMkM dAJNFguYjDdFnhxvj204oYaHPhVHjAHdaf3twmX0Z18FDcV0VNwbagBkYxLPxObs 9+0hanMgDbHbFxx3317Qd9HqGwSyD9OKJOGM1dh11/wGswFBQJGoFs9StUD/CDJY swvA0xZ4k/tU+M4Pm4Aiin8d0U8aWmGOKBdfd8elEx+0M0JlORjq1RrxL4wZT2XI Sn7qvkomqS9eRxGZ2ACWAwBsMFkDNUVA0FzrrXhReGQc7MWPvm73+cIYVoZUY1O5 AA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=5bvNfo A+xSwMFk7fPrIY++T4QVkEFzTezrPZMNX7if4=; b=YbS68uUx+hg1mGmf2b6jRo zBDuvMlLr+6qDDJKJwhn3qBzP7a4OE3foAbZRhnGm4eTY+3BUAS2i1AISKePlX6p cTi03EHptwAEZ23a1YiBYByTPaAJCJmbkZ5tbPVjTFzgNi5XL2Q/Lnzwce+nDSLC YG45XyNmw2x+FXD7eUfca/hBp0wWU3D0qDgsBlMG6yynr77vaPdgVzjTf3I7n1TK PuIQJoRS1X5F495UmKPGU36XojQJZrf6Xbexr3XRdIQ38RbX1C1DoCq5oykwLaVD vNuOi72yP5fxLTAbMFEuOLfdk4seFYFExFCeyBrvtwknoUu3gflr6JK6Zh14rFZw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrjeekgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucffohhmrghinheprhhftgdqvgguihhtohhrrdhorhhgpdgvgigrmhhplhgvrdgtohhm necurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmh drtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1D612186527; Tue, 23 Jul 2019 12:33:49 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-736-gdfb8e44-fmstable-20190718v2 Mime-Version: 1.0 Message-Id: <5f4c9627-7fb5-454b-99df-3e42fd18e270@beta.fastmail.com> In-Reply-To: <20190723155616.CE844B80D4D@rfc-editor.org> References: <20190723155616.CE844B80D4D@rfc-editor.org> Date: Tue, 23 Jul 2019 12:33:43 -0400 From: "Neil Jenkins" To: rfc-editor , "Chris Newman" , "Barry Leiba" , "Alexey Melnikov" , "Adam Roach" , "Bron Gondwana" , "Jim Fenton" Cc: "Neil Jhaveri" , "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=2da00270ace846c38d168869bb373e5a Archived-At: Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2019 16:34:03 -0000 --2da00270ace846c38d168869bb373e5a Content-Type: text/plain I can verify this errata report is correct. What is the process to 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 > > 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": {} --2da00270ace846c38d168869bb373e5a Content-Type: text/html Content-Transfer-Encoding: quoted-printable
I can verify th= is errata report is correct. What is the process to 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)".
<= br>
--------------------------------------
You m= ay review the report below and at:
https://www.rfc-editor.= org/errata/eid5791

------------------------= --------------
Type: Technical
Reported by: = Neil Jhaveri <neil@neiljhaveri.com>

S= ection: 2.1

Original Text
---= ----------
"capabilities": {
  "urn:iet= f:params:jmap:core": {
    "maxSizeUpload":= 50000000,
    "maxConcurrentUpload": 8,
    "maxSizeRequest": 10000000,
    "maxConcurrentRequest": 8,
  = ;  "maxCallsInRequest": 32,
    "maxOb= jectsInGet": 256,
    "maxObjectsInSet": 12= 8,
    "collationAlgorithms": [
      "i;ascii-numeric",
 = ;     "i;ascii-casemap",
  &= nbsp;   "i;unicode-casemap"
    ]=
  },
  "urn:ietf:params:jmap:mail= ": {}
  "urn:ietf:params:jmap:contacts": {},
  "https://example.com/apis/foobar": {
 &n= bsp;  "maxFoosFinangled": 42
  }
}=

Corrected Text
-------------= -
"capabilities": {
  "urn:ietf:params:= jmap:core": {
    "maxSizeUpload": 50000000= ,
    "maxConcurrentUpload": 8,
    "maxSizeRequest": 10000000,
 &n= bsp;  "maxConcurrentRequests": 8,
    = "maxCallsInRequest": 32,
    "maxObjectsInG= et": 256,
    "maxObjectsInSet": 128,
    "collationAlgorithms": [
 = ;     "i;ascii-numeric",
  &= nbsp;   "i;ascii-casemap",
   &nb= sp;  "i;unicode-casemap"
    ]
  },
  "urn:ietf:params:jmap:mail": {},
  "urn:ietf:params:jmap:contacts": {},
&= nbsp; "https://example.com/apis/foobar": {
  &nb= sp; "maxFoosFinangled": 42
  }
}

Notes
-----
In the ca= pabilities section of the example Session Resource response, "maxConcurr= entRequest" should be "maxConcurrentRequests". 

<= /div>
In addition, the following line is missing a trailing comma:
  "urn:ietf:params:jmap:mail": {}

--2da00270ace846c38d168869bb373e5a-- From nobody Tue Jul 23 09:35:47 2019 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 DBE37120351 for ; Tue, 23 Jul 2019 09:35:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=fastmail.fm header.b=EPPixuyn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TtYFLfxN 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 O7437d6siQbZ for ; Tue, 23 Jul 2019 09:35:44 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66DE4120356 for ; Tue, 23 Jul 2019 09:35:39 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6C7CB22053; Tue, 23 Jul 2019 12:35:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 23 Jul 2019 12:35:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=e rZUXAip8q3+vXozwUvw3xLNVX21yerB7PSc2OLOi88=; b=EPPixuynHsghkaHBY IioKF7ah9q7NpTeps6Q1TgvL33UD4m3n3hTb6kMGo+JAsECTZp6ihMbJYLvC51+O yMYzU9+pCl7RAWw+H7YZxkiZCTL3jNDrsXFrfdrLMDK4hVk9i2++UazC4A031kpw TmYSnxGnfVB6KU4zqsauz/w86ecDfAykf/5S0NhZ2FM3QJ6nokABeVlC8CuUcJVg mV4HGp8JfQKTv3zhJCrQLU22hDABaRqun71DOu6JbXHk+kDiVJdUwXFIumM+i60v 0YggPRsyQ2/wQYAjbaI1bugYIbXte4IdrTL2nh7BYFH3effkJBImYoD5SDEvChJv WUy2w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=erZUXAip8q3+vXozwUvw3xLNVX21yerB7PSc2OLOi 88=; b=TtYFLfxNEubbkM7oGsvoKuvmgIhZsVQ9TrrUVQ0hiL23/aIdNbs0P7NQN LDXFiO9IzIR587oQYz4ONSP30YC7zouAhr8jwdNW9Fmt6CWYPhUWsC1SjClplh9x l2WplH+vzcZ9xGvMKatoYoEXQLjJ9/SENj7AbRqP652S+fJ5LpBSqvlY8/a4Kkpd vP7fmkxU/FzEcGD5HsyHUbLmqvVMyup+rgEJYvSnyw3ERoPv9uefCM3haPXQRFGX s6ifR++jwvtkHoseHwQyHiiR+Mm5t19NXa82hkwqTSC1CfHEATI5uZMgr0fMQi1P s14luBvHPguRu+lQElf7puqoDZ72g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrjeekgddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesthhqmhdthhdtvdenucfhrhhomheptehlvgig vgihucfovghlnhhikhhovhcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh eqnecuffhomhgrihhnpehrfhgtqdgvughithhorhdrohhrghdpvgigrghmphhlvgdrtgho mhenucfkphepfedurddufeefrdduhedtrddukeegnecurfgrrhgrmhepmhgrihhlfhhroh hmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenucevlhhushhtvghrufhi iigvpedt X-ME-Proxy: Received: from [31.133.150.184] (dhcp-96b8.meeting.ietf.org [31.133.150.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4D2D480066; Tue, 23 Jul 2019 12:35:37 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Alexey Melnikov X-Mailer: iPad Mail (16D57) In-Reply-To: <5f4c9627-7fb5-454b-99df-3e42fd18e270@beta.fastmail.com> Date: Tue, 23 Jul 2019 12:35:36 -0400 Cc: rfc-editor , Chris Newman , Barry Leiba , Adam Roach , Bron Gondwana , Jim Fenton , Neil Jhaveri , IETF JMAP Mailing List 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 Archived-At: Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2019 16:35:46 -0000 > On 23 Jul 2019, at 12:33, Neil Jenkins wrote: >=20 > I can verify this errata report is correct. What is the process to approve= ? I need to login and approve. >=20 > Neil. >=20 >> 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)". >>=20 >> -------------------------------------- >> You may review the report below and at: >> https://www.rfc-editor.org/errata/eid5791 >>=20 >> -------------------------------------- >> Type: Technical >> Reported by: Neil Jhaveri >>=20 >> Section: 2.1 >>=20 >> 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 >> } >> } >>=20 >> 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 >> } >> } >>=20 >> Notes >> ----- >> In the capabilities section of the example Session Resource response, "ma= xConcurrentRequest" should be "maxConcurrentRequests".=20 >>=20 >> In addition, the following line is missing a trailing comma: >> "urn:ietf:params:jmap:mail": {} >=20 From nobody Tue Jul 23 10:04:13 2019 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 270D8120121 for ; 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 ; 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 ; 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 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 (PDT) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 From nobody Tue Jul 23 10:32:33 2019 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 D2A5212067A; Tue, 23 Jul 2019 10:32:24 -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: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <156390314478.27838.14290900641688451899@ietfa.amsl.com> Date: Tue, 23 Jul 2019 10:32:24 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-websocket-03.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: Tue, 23 Jul 2019 17:32:25 -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 : A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket Author : Kenneth Murchison Filename : draft-ietf-jmap-websocket-03.txt Pages : 14 Date : 2019-07-23 Abstract: This document defines a binding for the JSON Meta Application Protocol (JMAP) over a WebSocket transport layer. The WebSocket binding for JMAP provides higher performance than the current HTTP binding for JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-websocket/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-websocket-03 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-websocket-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-websocket-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sat Jul 27 22:17:40 2019 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 6EF37120096 for ; Sat, 27 Jul 2019 22:17:39 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <156429105944.27920.2764055733349410029.idtracker@ietfa.amsl.com> Date: Sat, 27 Jul 2019 22:17:39 -0700 From: IETF Secretariat Archived-At: Subject: [Jmap] Milestones changed for jmap WG 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: Sun, 28 Jul 2019 05:17:40 -0000 Changed milestone "Update charter to reflect current and planned work", resolved as "Done". Changed milestone "Adopt a document for calendar access via JMAP", resolved as "Done", added draft-ietf-jmap-calendars to milestone. Changed milestone "Adopt a document for S/MIME interaction via JMAP", resolved as "Done", added draft-ietf-jmap-smime to milestone. URL: https://datatracker.ietf.org/wg/jmap/about/