draft-ietf-xmpp-websocket-00.txt   draft-ietf-xmpp-websocket-01.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: March 09, 2014 Mozilla Expires: August 18, 2014 Mozilla
E. Cestari E. Cestari
cstar industries cstar industries
September 05, 2013 February 14, 2014
An XMPP Sub-protocol for WebSocket An XMPP Sub-protocol for WebSocket
draft-ietf-xmpp-websocket-00 draft-ietf-xmpp-websocket-01
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 March 09, 2014. This Internet-Draft will expire on August 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
skipping to change at page 2, line 25 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. XMPP Sub-Protocol . . . . . . . . . . . . . . . . . . . . . . 3 3. XMPP Sub-Protocol . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. XMPP Stream Setup . . . . . . . . . . . . . . . . . . . . 4 3.3. XMPP Stream Setup . . . . . . . . . . . . . . . . . . . . 4
3.4. Stream Errors . . . . . . . . . . . . . . . . . . . . . . 5 3.4. Stream Errors . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Closing the Connection . . . . . . . . . . . . . . . . . 5 3.5. Closing the Connection . . . . . . . . . . . . . . . . . 5
3.5.1. see-other-uri . . . . . . . . . . . . . . . . . . . . 6
3.6. Stanzas . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.6. Stanzas . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.7. Stream Restarts . . . . . . . . . . . . . . . . . . . . . 6 3.7. Stream Restarts . . . . . . . . . . . . . . . . . . . . . 7
3.8. Pings and Keepalives . . . . . . . . . . . . . . . . . . 6 3.8. Pings and Keepalives . . . . . . . . . . . . . . . . . . 7
3.9. Use of TLS . . . . . . . . . . . . . . . . . . . . . . . 7 3.9. Use of TLS . . . . . . . . . . . . . . . . . . . . . . . 8
3.10. Stream Management . . . . . . . . . . . . . . . . . . . . 7 3.10. Stream Management . . . . . . . . . . . . . . . . . . . . 8
4. Discovering Connection Method . . . . . . . . . . . . . . . . 7 4. Discovering Connection Method . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5.1. WebSocket Subprotocol Name . . . . . . . . . . . . . . . 9
7. Informative References . . . . . . . . . . . . . . . . . . . 8 5.2. URN Sub-Namespace . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
Applications using XMPP (see [RFC6120] and [RFC6121]) on the Web Applications using XMPP (see [RFC6120] and [RFC6121]) on the Web
currently make use of BOSH (see [XEP-0124] and [XEP-0206]), an XMPP 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, binding to HTTP. BOSH is based on the HTTP long polling technique,
and it suffers from high transport overhead compared to XMPP's native and it suffers from high transport overhead compared to XMPP's native
binding to TCP. In addition, there are a number of other known binding to TCP. In addition, there are a number of other known
issues with long polling [RFC6202], which have an impact on BOSH- issues with long polling [RFC6202], which have an impact on BOSH-
based systems. based systems.
skipping to change at page 4, line 24 skipping to change at page 4, line 24
S: HTTP/1.1 101 Switching Protocols S: HTTP/1.1 101 Switching Protocols
Upgrade: websocket Upgrade: websocket
Connection: Upgrade Connection: Upgrade
... ...
Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo= Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
Sec-WebSocket-Protocol: xmpp Sec-WebSocket-Protocol: xmpp
[WebSocket connection established] [WebSocket connection established]
C: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" C: <open xmlns="urn:ietf:params:xml:ns:xmpp-framing"
xmlns="jabber:client" to="example.com"
to="example.com" version="1.0" />
version="1.0">
3.2. Messages 3.2. Messages
Data frame messages in the XMPP sub-protocol MUST be of the text type Data frame messages in the XMPP sub-protocol MUST be of the text type
and contain UTF-8 encoded data. The close control frame's contents and contain UTF-8 encoded data. The close control frame's contents
are specified in Section 3.5. Control frames other than close are are specified in Section 3.5. Control frames other than close are
not restricted. not restricted.
Unless noted in text, the word "message" will mean a WebSocket Unless noted in text, the word "message" will mean a WebSocket
message composed of text data frames. message composed of text data frames.
3.3. XMPP Stream Setup 3.3. XMPP Stream Setup
The first message sent after the handshake is complete MUST be an The first message sent after the handshake is complete MUST be an
XMPP opening stream tag as defined in XMPP [RFC6120] or an XML text <open /> element using the "urn:ietf:params:xml:ns:xmpp-framing"
declaration (see Section 4.3.1 of [W3C.REC-xml-20081126]) followed by namespace, whose 'from', 'id', 'to' and 'version' attributes
an XMPP opening stream tag. The stream tag MUST NOT be closed (i.e. mirror those in the XMPP opening stream tag as defined for the
the closing </stream:stream> tag should not appear in the message) as 'http://etherx.jabber.org/streams' namespace in XMPP [RFC6120]. The
it is the start of the client's outgoing XML. The '<' character of '<' character of the open tag MUST be the first character of the text
the tag or text declaration MUST be the first character of the text
payload. payload.
The server MUST respond with a message containing an error (see The server MUST respond with an <open /> element, or a <close />
Section 3.4), its own opening stream tag, or an XML text declaration element (see Section 3.5.1).
followed by an opening stream tag.
Except in the case of certain stream errors (see Section 3.4), the Clients MUST NOT attempt to multiplex XMPP streams for multiple JIDs
opening stream tag, <stream:stream>, MUST appear in a message by over the same WebSocket.
itself.
3.4. Stream Errors 3.4. Stream Errors
Stream level errors in XMPP are terminal. Should such an error Stream level errors in XMPP are terminal. Should such an error
occur, the server MUST send the stream error as a complete element in occur, the server MUST send the stream error as a complete element in
a message to the client. a message to the client.
If the error occurs during the opening of a stream, the stream error If the error occurs during the opening of a stream, the server MUST
message MUST start with an opening stream tag (see Section 4.7.1 of send the initial open element response, followed by the stream level
[RFC6120]) and end with a closing stream tag. error in a second WebSocket message frame. The server MUST then
close the connection as specified in Section 3.5.
After the stream error and closing stream tag have been sent, the
server MUST close the connection as in Section 3.5.
3.5. Closing the Connection 3.5. Closing the Connection
Either the server or the client may close the connection at any time. Either the server or the client may close the connection at any time.
Before closing the connection, the closing party SHOULD close the Before closing the connection, the closing party SHOULD close the
XMPP stream, if it has been established, by sending a message with XMPP stream, if it has been established, by sending a message with
the closing </stream:stream> tag. The XMPP stream is considered the <close /> element, qualified by the "urn:ietf:params:xml:ns:xmpp-
closed when a corresponding </stream:stream> tag is received from the framing" namespace. The stream is considered closed when a
other party. corresponding <close/> element is received from the other party.
If a client closes the WebSocket connection without closing the XMPP
stream after having enabled stream management (see Section 3.10), the
server SHOULD keep the XMPP session alive for a period of time based
on server policy, as specified in [XEP-0198].
To initiate closing the WebSocket connection, the closing party MUST To initiate closing the WebSocket connection, the closing party MUST
send a normal WebSocket close message with an empty body. The send a normal WebSocket close message with an empty body. The
connection is considered closed when a matching close message is connection is considered closed when a matching close message is
received (see Section 1.4 of [RFC6455]). received (see Section 1.4 of [RFC6455]).
Except in the case of certain stream errors (see Section 3.4), the
closing stream tag, </stream:stream>, MUST appear in a message by
itself.
An example of ending an XMPP over WebSocket session by first closing An example of ending an XMPP over WebSocket session by first closing
the XMPP stream layer and then the WebSocket connection layer: the XMPP stream layer and then the WebSocket connection layer:
Client (XMPP WSS) Server Client (XMPP WSS) Server
| | | | | | | |
| | </stream:stream> | | | | <close xmlns="urn:ietf:params:xml:ns:xmpp-framing /> | |
| |------------------------------------>| | | |------------------------------------------------------------>| |
| | </stream:stream> | | | | <close xmlns="urn:ietf:params:xml:ns:xmpp-framing" /> | |
| |<------------------------------------| | | |<------------------------------------------------------------| |
| | | | | | | |
| | (XMPP Stream Closed) | | | | (XMPP Stream Closed) | |
| +-------------------------------------+ | | +-------------------------------------------------------------+ |
| | | |
| WS CLOSE FRAME | | WS CLOSE FRAME |
|------------------------------------------>| |------------------------------------------------------------------>|
| WS CLOSE FRAME | | WS CLOSE FRAME |
|<------------------------------------------| |<------------------------------------------------------------------|
| | | |
| (Connection Closed) | | (Connection Closed) |
+-------------------------------------------+ +-------------------------------------------------------------------+
If a client closes the WebSocket connection without closing the XMPP
stream after having enabled stream management (see Section 3.10), the
server SHOULD keep the XMPP session alive for a period of time based
on server policy, as specified in [XEP-0198]. If the client has not
negotiated the use of [XEP-0198], there is no distinction between a
stream that was closed as described above and a simple disconnection;
the stream is then considered implicitly closed and the XMPP session
ended.
3.5.1. see-other-uri
If the server (or a connection mananger intermediary) wishes to
instruct the client to move to a different WebSocket endpoint (e.g.
for load balancing purposes), the server MAY send a <close /> element
and set the "see-other-uri" attribute to the URI of the new WebSocket
endpoint.
Clients MUST NOT accept suggested endpoints with a lower security
context (e.g. moving from a "wss://" endpoint to a "ws://" endpoint).
An example of the server closing a stream and instructing the client
to connect at a different WebSocket endpoint:
S: <close xmlns="urn:ietf:params:xml:ns:xmpp-framing"
see-other-uri="wss://otherendpoint.example/xmpp-bind" />
3.6. Stanzas 3.6. Stanzas
Each XMPP stanza MUST be sent in its own message. A stanza MUST NOT Every XMPP stanza or other XML element sent directly over the XMPP
be split over multiple messages. All first level children of the stream (e.g. <features xmlns="http://etherx.jabber.org/streams" />)
<stream:stream> element MUST be treated the same as stanzas (e.g. MUST be sent in its own message. As such, every WebSocket text
<stream:features> and <stream:error>). message that is received MUST be a complete and parsable XML
fragment, with all relevant xmlns and xml:lang declarations
specified.
As it is already mandated that the content of each message is UTF-8
encoded, XML text declarations SHOULD NOT be included in messsages.
Examples of WebSocket messages that contain independently parsable
XML fragments (note that for stream features and errors, there is no
parent context element providing the "stream" namespace prefix as in
[RFC6120], and thus the stream namespace MUST be declared):
<features xmlns="http://etherx.jabber.org/streams">
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind" />
</features>
<error xmlns="http://etherx.jabber.org/streams">
<host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
</error>
<message xmlns="jabber:client" xml:lang="en">
<body>Every WebSocket message is parsable by itself.</body>
</message>
3.7. Stream Restarts 3.7. Stream Restarts
After successful SASL authentication, an XMPP stream needs to be After successful SASL authentication, an XMPP stream needs to be
restarted. In these cases, as soon as the message is sent (or restarted. In these cases, as soon as the message is sent (or
received) containing the success indication, both the server and received) containing the success indication, both the server and
client streams are implicitly closed, and new streams need to be client streams are implicitly closed, and new streams need to be
opened. The client MUST open a new stream as in Section 3.3 and MUST opened. The client MUST open a new stream as in Section 3.3 and MUST
NOT send a closing stream tag. NOT send a closing <close /> element.
S: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl" /> S: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl" />
[Streams implicitly closed] [Streams implicitly closed]
C: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" C: <open xmlns="urn:ietf:params:xml:ns:xmpp-framing"
xmlns="jabber:client" to="example.com"
to="example.com" version="1.0" />
version="1.0">
3.8. Pings and Keepalives 3.8. Pings and Keepalives
XMPP servers send whitespace pings as keepalives between stanzas, and XMPP servers send whitespace pings as keepalives between stanzas, and
XMPP clients can do the same as these extra whitespace characters are XMPP clients can do the same as these extra whitespace characters are
not significant in the protocol. Servers and clients SHOULD use not significant in the protocol. Servers and clients SHOULD use
WebSocket ping control frames instead for this purpose. WebSocket ping control frames instead for this purpose.
In some cases, the WebSocket connection might be served by an In some cases, the WebSocket connection might be served by an
intermediary connection manager and not the XMPP server. In these intermediary connection manager and not the XMPP server. In these
situations, the use of WebSocket ping messages are insufficient to situations, the use of WebSocket ping messages are insufficient to
test that the XMPP stream is still alive. Both the XMPP Ping test that the XMPP stream is still alive. Both the XMPP Ping
extension [XEP-0199] and the XMPP Stream Management extension extension [XEP-0199] and the XMPP Stream Management extension
skipping to change at page 7, line 45 skipping to change at page 8, line 34
when stanzas have been received by the server. when stanzas have been received by the server.
In particular, the use of session resumption in [XEP-0198] MAY be In particular, the use of session resumption in [XEP-0198] MAY be
used to allow for recreating the same stream session state after a used to allow for recreating the same stream session state after a
temporary network unavailability or after navigating to a new URL in temporary network unavailability or after navigating to a new URL in
a browser. a browser.
4. Discovering Connection Method 4. Discovering Connection Method
The XMPP extension Discovering Alternate XMPP Connection Methods The XMPP extension Discovering Alternate XMPP Connection Methods
[XEP-0156] provides a mechanism to discover the additional [XEP-0156] provides mechanisms to discover the additional information
information needed to connect to an XMPP server outside of the needed to connect to an XMPP server outside of the procedure defined
procedure defined in in Section 3 of [RFC6120]. in in Section 3 of [RFC6120].
For the XMPP over Websocket connection type, the connection method
name "_xmpp-client-websocket" is used to specify a URI for the
server's WebSocket connection endpoint.
An example entry advertising that the URI "wss://example.com/xmpp" is
an XMPP over WebSocket endpoint, using a DNS TXT record as specified
in [XEP-0156]:
_xmppconnect IN TXT "_xmpp-client-websocket=wss://example.com/xmpp"
Implementation Note: A server is able to expose both BOSH [XEP-0206]
and WebSocket endpoints over the registered port 5280, using the URI
path and connection upgrade headers to determine which transport to
serve.
5. Security Considerations
Since application level TLS cannot be used (see Section 3.9), Servers MAY expose such discovery information, and clients MAY use
applications which need to protect the privacy of the XMPP traffic such information to determine the WebSocket endpoint for a server.
need to do so at the WebSocket or other appropriate layer.
The Security Considerations for both WebSocket (See Section 10 of Use of the HTTP lookup method in [XEP-0156] MAY be used to establish
[RFC6455] and XMPP (See Section 13 of [RFC6120]) apply to the trust between the XMPP server domain and the WebSocket endpoint,
WebSocket XMPP sub-protocol. particularly in multi-tenant situations where the same WebSocket
endpoint is serving multiple XMPP domains.
6. IANA Considerations 5. IANA Considerations
5.1. WebSocket Subprotocol Name
This specification requests IANA to register the WebSocket XMPP sub- This specification requests IANA to register the WebSocket XMPP sub-
protocol under the "WebSocket Subprotocol Name" Registry with the protocol under the "WebSocket Subprotocol Name" Registry with the
following data: following data:
Subprotocol Identifier: xmpp Subprotocol Identifier: xmpp
Subprotocol Common Name: WebSocket Transport for the Extensible Subprotocol Common Name: WebSocket Transport for the Extensible
Messaging and Presence Protocol (XMPP) Messaging and Presence Protocol (XMPP)
Subprotocol Definition: RFC XXXX Subprotocol Definition: RFC XXXX
[[NOTE TO RFC EDITOR: Please change XXXX to the number assigned to [[ NOTE TO RFC EDITOR: Please replace "XXXX" with the number assigned
this document upon publication.]] to this document upon publication as an RFC. ]]
7. Informative References 5.2. URN Sub-Namespace
A URN sub-namespace for framing of Extensible Messaging and Presence
Protocol (XMPP) streams is defined as follows.
URI: urn:ietf:params:xml:ns:xmpp-framing
Specification: RFC XXXX
Description: This is the XML namespace name for framing of
Extensible Messaging and Presence Protocol (XMPP) streams as
defined by RFC XXXX.
Registrant Contact: IESG <iesg@ietf.org>
[[ NOTE TO RFC EDITOR: Please replace "XXXX" with the number assigned
to this document upon publication as an RFC. ]]
6. Security Considerations
Since application level TLS cannot be used (see Section 3.9),
applications which need to protect the privacy of the XMPP traffic
need to do so at the WebSocket or other appropriate layer.
Browser based applications are not able to inspect and verify at the
application layer the certificate used for the WebSocket connection
to ensure that it corresponds to the domain specified as the "to"
address of the XMPP stream. For hosts whose domain matches the
origin for the WebSocket connection, that check is already performed
by the browser. However, in situations where the domain of the XMPP
server might not match the origin for the WebSocket endpoint
(especially multi-tenant hosting situations), the HTTP discovery
method in [XEP-0156] MAY be used to delegate trust from the XMPP
server domain to the WebSocket origin.
When presented with a new WebSocket endpoint via the "see-other-uri"
attribute of a <close/> element, clients MUST NOT accept the
suggestion if the security context of the new endpoint is lower than
the current one in order to prevent downgrade attacks from a "wss://"
endpoint to "ws://".
The Security Considerations for both WebSocket (see Section 10 of
[RFC6455] and XMPP (see Section 13 of [RFC6120]) apply to the
WebSocket XMPP sub-protocol.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6120] Saint-Andre, P., "Extensible Messaging and Presence [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Core", RFC 6120, March 2011. Protocol (XMPP): Core", RFC 6120, March 2011.
[XEP-0156]
Hildebrand, J., Saint-Andre, P., and L. Stout,
"Discovering Alternative XMPP Connection Methods", XSF XEP
0156, January 2014.
7.2. Informative References
[RFC6121] Saint-Andre, P., "Extensible Messaging and Presence [RFC6121] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Instant Messaging and Presence", RFC Protocol (XMPP): Instant Messaging and Presence", RFC
6121, March 2011. 6121, March 2011.
[RFC6202] Loreto, S., Saint-Andre, P., Salsano, S., and G. Wilkins, [RFC6202] Loreto, S., Saint-Andre, P., Salsano, S., and G. Wilkins,
"Known Issues and Best Practices for the Use of Long "Known Issues and Best Practices for the Use of Long
Polling and Streaming in Bidirectional HTTP", RFC 6202, Polling and Streaming in Bidirectional HTTP", RFC 6202,
April 2011. April 2011.
[RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", RFC [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", RFC
6455, December 2011. 6455, December 2011.
[W3C.REC-xml-20081126]
Sperberg-McQueen, C., Yergeau, F., Paoli, J., Bray, T.,
and E. Maler, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>.
[XEP-0124] [XEP-0124]
Paterson, I., Smith, D., Saint-Andre, P., and J. Moffitt, Paterson, I., Smith, D., Saint-Andre, P., Moffitt, J., and
"Bidirectional-streams Over Synchronous HTTP (BOSH)", XSF L. Stout, "Bidirectional-streams Over Synchronous HTTP
XEP 0124, July 2010. (BOSH)", XSF XEP 0124, November 2013.
[XEP-0156]
Hildebrand, J. and P. Saint-Andre, "Discovering
Alternative XMPP Connection Methods", XSF XEP 0156, June
2007.
[XEP-0198] [XEP-0198]
Karneges, J., Saint-Andre, P., Hildebrand, J., Forno, F., Karneges, J., Saint-Andre, P., Hildebrand, J., Forno, F.,
Cridland, D., and M. Wild, "Stream Management", XSF XEP Cridland, D., and M. Wild, "Stream Management", XSF XEP
0198, June 2011. 0198, June 2011.
[XEP-0199] [XEP-0199]
Saint-Andre, P., "XMPP Ping", XSF XEP 0199, June 2009. Saint-Andre, P., "XMPP Ping", XSF XEP 0199, June 2009.
[XEP-0206] [XEP-0206]
Paterson, I. and P. Saint-Andre, "XMPP Over BOSH", XSF XEP Paterson, I., Saint-Andre, P., and L. Stout, "XMPP Over
0206, July 2010. BOSH", XSF XEP 0206, November 2013.
[XML-SCHEMA]
Thompson, H., Maloney, M., Mendelsohn, N., and D. Beech,
"XML Schema Part 1: Structures Second Edition", World Wide
Web Consortium Recommendation REC-xmlschema-1-20041028,
October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
Appendix A. XML Schema
The following schema formally defines the 'urn:ietf:params:xml:ns
:xmpp-framing' namespace used in this document, in conformance with
W3C XML Schema [XML-SCHEMA]. Because validation of XML streams and
stanzas is optional, this schema is not normative and is provided for
descriptive purposes only.
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:ietf:params:xml:ns:xmpp-framing'
xmlns='urn:ietf:params:xml:ns:xmpp-framing'
elementFormDefault='unqualified'>
<xs:element name='open'>
<xs:complexType>
<xs:simpleContent>
<xs:extension base='empty'>
<xs:attribute name='from' type='xs:string'
use='optional'/>
<xs:attribute name='id' type='xs:string'
use='optional'/>
<xs:attribute name='see-other-uri' type='xs:anyURI'
use='optional'/>
<xs:attribute name='to' type='xs:string'
use='optional'/>
<xs:attribute name='version' type='xs:decimal'
use='optional'/>
<xs:attribute ref='xml:lang'
use='optional'/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name='close'>
<xs:complexType>
<xs:simpleContent>
<xs:extension base='empty'>
<xs:attribute name='from' type='xs:string'
use='optional'/>
<xs:attribute name='id' type='xs:string'
use='optional'/>
<xs:attribute name='see-other-uri' type='xs:anyURI'
use='optional'/>
<xs:attribute name='to' type='xs:string'
use='optional'/>
<xs:attribute name='version' type='xs:decimal'
use='optional'/>
<xs:attribute ref='xml:lang'
use='optional'/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:simpleType name='empty'>
<xs:restriction base='xs:string'>
<xs:enumeration value=''/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
Authors' Addresses Authors' Addresses
Lance Stout (editor) Lance Stout (editor)
&yet &yet
Email: lance@andyet.net Email: lance@andyet.net
Jack Moffitt Jack Moffitt
Mozilla Mozilla
 End of changes. 30 change blocks. 
122 lines changed or deleted 259 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/