An XMPP Sub-protocol for WebSocket
draft-ietf-xmpp-websocket-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (xmpp WG)
|
|
Last updated |
|
2014-03-14
|
|
Replaces |
|
draft-moffitt-xmpp-over-websocket
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
XMPP Working Group L. Stout, Ed.
Internet-Draft &yet
Intended status: Standards Track J. Moffitt
Expires: September 15, 2014 Mozilla
E. Cestari
cstar industries
March 14, 2014
An XMPP Sub-protocol for WebSocket
draft-ietf-xmpp-websocket-02
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 September 15, 2014.
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 September 15, 2014 [Page 1]
Internet-Draft XMPP over WebSocket March 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. Messages . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. XMPP Stream Setup . . . . . . . . . . . . . . . . . . . . 4
3.4. Stream Errors . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Closing the Connection . . . . . . . . . . . . . . . . . 5
3.5.1. see-other-uri . . . . . . . . . . . . . . . . . . . . 6
3.6. Stanzas . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.7. Stream Restarts . . . . . . . . . . . . . . . . . . . . . 7
3.8. Pings and Keepalives . . . . . . . . . . . . . . . . . . 7
3.9. Use of TLS . . . . . . . . . . . . . . . . . . . . . . . 8
3.10. Stream Management . . . . . . . . . . . . . . . . . . . . 8
4. Discovering the WebSocket Connection Method . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. WebSocket Subprotocol Name . . . . . . . . . . . . . . . 9
5.2. URN Sub-Namespace . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . 10
7.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. XML Schema . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
Applications using the Extensible Messaging and Presence Protocol
(XMPP) (see [RFC6120] and [RFC6121]) on the Web currently make 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 XMPP
over HTTP long polled connections and instead use the XMPP protocol
directly. However, the APIs and sandbox that browsers have provided
do not allow this. The WebSocket protocol [RFC6455] exists to solve
these kinds of problems. The WebSocket protocol is a bidirectional
Show full document text