An XMPP Sub-protocol for WebSocket
draft-ietf-xmpp-websocket-09
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (xmpp WG) | |
Authors | Lance Stout , Jack Moffitt , Eric Cestari | ||
Last updated | 2014-08-11 | ||
Replaces | draft-moffitt-xmpp-over-websocket | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Peter Saint-Andre | ||
Shepherd write-up | Show (last changed 2014-06-16) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Unknown | ||
Telechat date |
Needs 8 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Richard Barnes | ||
Send notices to | xmpp-chairs@tools.ietf.org, draft-ietf-xmpp-websocket@tools.ietf.org, stpeter@jabber.org | ||
IANA | IANA review state | Version Changed - Review Needed |
XMPP Working Group L. Stout, Ed. Internet-Draft &yet Intended status: Standards Track J. Moffitt Expires: February 12, 2015 Mozilla E. Cestari cstar industries August 11, 2014 An XMPP Sub-protocol for WebSocket draft-ietf-xmpp-websocket-09 Abstract This document defines a binding for the XMPP protocol over a WebSocket transport layer. A WebSocket binding for XMPP provides higher performance than the current HTTP binding for XMPP. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on February 12, 2015. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Stout, et al. Expires February 12, 2015 [Page 1] Internet-Draft XMPP over WebSocket August 2014 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. XMPP Sub-Protocol . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. WebSocket Messages . . . . . . . . . . . . . . . . . . . 4 3.3. XMPP Framing . . . . . . . . . . . . . . . . . . . . . . 5 3.3.1. Framed XML Stream . . . . . . . . . . . . . . . . . . 5 3.3.2. Framed Stream Namespace . . . . . . . . . . . . . . . 5 3.3.3. Stream Frames . . . . . . . . . . . . . . . . . . . . 5 3.4. Stream Initiation . . . . . . . . . . . . . . . . . . . . 6 3.5. Stream Errors . . . . . . . . . . . . . . . . . . . . . . 7 3.6. Closing the Connection . . . . . . . . . . . . . . . . . 7 3.6.1. see-other-uri . . . . . . . . . . . . . . . . . . . . 8 3.7. Stream Restarts . . . . . . . . . . . . . . . . . . . . . 9 3.8. Pings and Keepalives . . . . . . . . . . . . . . . . . . 9 3.9. Use of TLS . . . . . . . . . . . . . . . . . . . . . . . 9 3.10. Stream Management . . . . . . . . . . . . . . . . . . . . 10 4. Discovering the WebSocket Connection Method . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5.1. WebSocket Subprotocol Name . . . . . . . . . . . . . . . 11 5.2. URN Sub-Namespace . . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . 13 7.2. Informative References . . . . . . . . . . . . . . . . . 13 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 14 Appendix B. XML Schema . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 1. Introduction To date, applications using the Extensible Messaging and Presence Protocol (XMPP) (see [RFC6120] and [RFC6121]) on the Web have made use of BOSH (see [XEP-0124] and [XEP-0206]), an XMPP binding to HTTP. BOSH is based on the HTTP long polling technique, and it suffers from high transport overhead compared to XMPP's native binding to TCP. In addition, there are a number of other known issues with long polling [RFC6202], which have an impact on BOSH-based systems. It would be much better in most circumstances to avoid tunneling XMPPShow full document text