draft-ietf-xmpp-websocket-08.txt   draft-ietf-xmpp-websocket-09.txt 
XMPP Working Group L. Stout, Ed. XMPP Working Group L. Stout, Ed.
Internet-Draft &yet Internet-Draft &yet
Intended status: Standards Track J. Moffitt Intended status: Standards Track J. Moffitt
Expires: January 23, 2015 Mozilla Expires: February 12, 2015 Mozilla
E. Cestari E. Cestari
cstar industries cstar industries
July 22, 2014 August 11, 2014
An XMPP Sub-protocol for WebSocket An XMPP Sub-protocol for WebSocket
draft-ietf-xmpp-websocket-08 draft-ietf-xmpp-websocket-09
Abstract Abstract
This document defines a binding for the XMPP protocol over a This document defines a binding for the XMPP protocol over a
WebSocket transport layer. A WebSocket binding for XMPP provides WebSocket transport layer. A WebSocket binding for XMPP provides
higher performance than the current HTTP binding for XMPP. higher performance than the current HTTP binding for XMPP.
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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 January 23, 2015. This Internet-Draft will expire on February 12, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 8, line 35 skipping to change at page 8, line 35
If the WebSocket connection is closed or broken without the XMPP If the WebSocket connection is closed or broken without the XMPP
stream having been closed first, then the XMPP stream is considered stream having been closed first, then the XMPP stream is considered
implicitly closed and the XMPP session ended; however, if the use of implicitly closed and the XMPP session ended; however, if the use of
stream management resumption was negotiated (see [XEP-0198]), the stream management resumption was negotiated (see [XEP-0198]), the
server SHOULD consider the XMPP session still alive for a period of server SHOULD consider the XMPP session still alive for a period of
time based on server policy as specified in [XEP-0198]. time based on server policy as specified in [XEP-0198].
3.6.1. see-other-uri 3.6.1. see-other-uri
If the server (or a connection manager intermediary) wishes at any If the server wishes at any point to instruct the client to move to a
point to instruct the client to move to a different WebSocket different WebSocket endpoint (e.g., for load balancing purposes),
endpoint (e.g., for load balancing purposes), then a <close/> element then a <close/> element is sent with the 'see-other-uri' attribute
is sent with the 'see-other-uri' attribute set to the URI of the new set to the URI of the new connection endpoint (which MAY be for a
connection endpoint (which MAY be for a different transport method, different transport method, such as BOSH (see [XEP-0124] and
such as BOSH (see [XEP-0124] and [XEP-0206])). [XEP-0206])).
Clients MUST NOT accept suggested endpoints with a lower security Clients MUST NOT accept suggested endpoints with a lower security
context (e.g., moving from a 'wss://' endpoint to a 'ws://' or 'http: context (e.g., moving from a 'wss://' endpoint to a 'ws://' or 'http:
//' endpoint). //' endpoint).
An example of the server closing a stream and instructing the client An example of the server closing a stream and instructing the client
to connect at a different WebSocket endpoint: to connect at a different WebSocket endpoint:
S: <close xmlns="urn:ietf:params:xml:ns:xmpp-framing" S: <close xmlns="urn:ietf:params:xml:ns:xmpp-framing"
see-other-uri="wss://otherendpoint.example/xmpp-bind" /> see-other-uri="wss://otherendpoint.example/xmpp-bind" />
 End of changes. 5 change blocks. 
10 lines changed or deleted 10 lines changed or added

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