RFC 8620 on The JSON Meta Application Protocol (JMAP)

rfc-editor@rfc-editor.org Thu, 18 July 2019 16:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@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
Subject: RFC 8620 on The JSON Meta Application Protocol (JMAP)
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qD2sj2lm3fLNeqhOwRbhZesos-s>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=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