draft-ietf-jmap-websocket-06.txt   draft-ietf-jmap-websocket-07.txt 
JMAP K. Murchison JMAP K. Murchison
Internet-Draft Fastmail Internet-Draft Fastmail
Intended status: Standards Track March 9, 2020 Intended status: Standards Track March 19, 2020
Expires: September 10, 2020 Expires: September 20, 2020
A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
draft-ietf-jmap-websocket-06 draft-ietf-jmap-websocket-07
Abstract Abstract
This document defines a binding for the JSON Meta Application This document defines a binding for the JSON Meta Application
Protocol (JMAP) over a WebSocket transport layer. The WebSocket Protocol (JMAP) over a WebSocket transport layer. The WebSocket
binding for JMAP provides higher performance than the current HTTP binding for JMAP provides higher performance than the current HTTP
binding for JMAP. binding for JMAP.
Open Issues
o Still need to craft some text to discuss/address potential
security risks of using WebSocket compression.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 10, 2020. This Internet-Draft will expire on September 20, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Discovering Support for JMAP over WebSocket . . . . . . . . . 3 3. Discovering Support for JMAP over WebSocket . . . . . . . . . 3
4. JMAP Subprotocol . . . . . . . . . . . . . . . . . . . . . . 4 4. JMAP Subprotocol . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Authentication . . . . . . . . . . . . . . . . . . . . . 4 4.1. Authentication . . . . . . . . . . . . . . . . . . . . . 4
4.2. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 4
4.3. WebSocket Messages . . . . . . . . . . . . . . . . . . . 5 4.3. WebSocket Messages . . . . . . . . . . . . . . . . . . . 5
4.3.1. Handling Invalid Data . . . . . . . . . . . . . . . . 5 4.3.1. Handling Invalid Data . . . . . . . . . . . . . . . . 5
4.3.2. JMAP Requests . . . . . . . . . . . . . . . . . . . . 5 4.3.2. JMAP Requests . . . . . . . . . . . . . . . . . . . . 5
4.3.3. JMAP Responses . . . . . . . . . . . . . . . . . . . 6 4.3.3. JMAP Responses . . . . . . . . . . . . . . . . . . . 6
4.3.4. JMAP Request-Level Errors . . . . . . . . . . . . . . 6 4.3.4. JMAP Request-Level Errors . . . . . . . . . . . . . . 6
4.3.5. JMAP Push Notifications . . . . . . . . . . . . . . . 7 4.3.5. JMAP Push Notifications . . . . . . . . . . . . . . . 6
4.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 8 4.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5.1. Connection Confidentiality and Integrity . . . . . . . . 12 5.1. Connection Confidentiality and Integrity . . . . . . . . 12
5.2. Non-Browser Clients . . . . . . . . . . . . . . . . . . . 12 5.2. Non-Browser Clients . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.1. Registration of the WebSocket JMAP Subprotocol . . . . . 12 6.1. Registration of the WebSocket JMAP Subprotocol . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 14
skipping to change at page 14, line 22 skipping to change at page 14, line 22
8.2. Informative References 8.2. Informative References
[RFC8621] Jenkins, N. and C. Newman, "The JSON Meta Application [RFC8621] Jenkins, N. and C. Newman, "The JSON Meta Application
Protocol (JMAP) for Mail", RFC 8621, DOI 10.17487/RFC8621, Protocol (JMAP) for Mail", RFC 8621, DOI 10.17487/RFC8621,
August 2019, <https://www.rfc-editor.org/info/rfc8621>. August 2019, <https://www.rfc-editor.org/info/rfc8621>.
Appendix A. Change History (To be removed by RFC Editor before Appendix A. Change History (To be removed by RFC Editor before
publication) publication)
Changes since ietf-06:
o Removed open issue on security of WebSocket compression, per
Alexey Melnikov.
Changes since ietf-05: Changes since ietf-05:
o Renamed "webSocketUrl" to "url" and "supportsWebSocketPush" to o Renamed "webSocketUrl" to "url" and "supportsWebSocketPush" to
"supportsPush", per Benjamin Schwartz. "supportsPush", per Benjamin Schwartz.
o Added a security subsection with a nod to Sections 10.1 and 10.2 o Added a security subsection with a nod to Sections 10.1 and 10.2
of RFC6455, per Leif Johansson. of RFC6455, per Leif Johansson.
o Clarified "unsupported JMAP" vs "unsupported JSON", per Benjamin o Clarified "unsupported JMAP" vs "unsupported JSON", per Benjamin
Kaduk. Kaduk.
 End of changes. 7 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/