[Jmap] RFC 8887 on A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket

rfc-editor@rfc-editor.org Fri, 28 August 2020 00:02 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 AAAA63A145C; Thu, 27 Aug 2020 17:02:31 -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 U4-n0y6Hayvd; Thu, 27 Aug 2020 17:02:29 -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 2F02F3A1459; Thu, 27 Aug 2020 17:02:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 37C30F40788; Thu, 27 Aug 2020 17:02:23 -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: <20200828000223.37C30F40788@rfc-editor.org>
Date: Thu, 27 Aug 2020 17:02:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Wzk7Zaydx3gZN1pI9A6VeN9w4mA>
Subject: [Jmap] RFC 8887 on A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
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: Fri, 28 Aug 2020 00:02:32 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8887

        Title:      A JSON Meta Application Protocol 
                    (JMAP) Subprotocol for WebSocket 
        Author:     K. Murchison
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2020
        Mailbox:    murch@fastmailteam.com
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-jmap-websocket-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8887

        DOI:        10.17487/RFC8887

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.

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