From 1597835c28351a8a799747b98bd25eca571a8b91 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 21 Nov 2006 23:21:12 +0000 Subject: [PATCH] initial version git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@202 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0199.xml | 129 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 xep-0199.xml diff --git a/xep-0199.xml b/xep-0199.xml new file mode 100644 index 00000000..dcea764f --- /dev/null +++ b/xep-0199.xml @@ -0,0 +1,129 @@ + + +%ents; +]> + + +
+ XMPP Ping + This document defines an XMPP protocol extension for sending pings over an XML stream. + &LEGALNOTICE; + 0199 + Experimental + Standards Track + Standards JIG + Council + + XMPP Core + + + + ping + &stpeter; + + 0.1 + 2006-11-21 + psa +

Initial version.

 + +
+ +

As specified in &rfc3920;, the XML streams used in XMPP are bound to TCP. Unfortunately, TCP connections can go down without the application (XMPP) layer knowing about it. The traditional approach to solving this issue has been to periodically send so-called "whitespace pings" over the XML stream. This document recommends a more XML-friendly and XMPP-friendly approach, which can also be used with other bindings such as &xep0124;.

+ + +

This document addresses the following requirements:

+
    +
  1. Determining the per-hop viability of an XML stream (i.e., its underlying binding) between a client and a server, or between two servers.
    2. +
  2. Determining end-to-end connectivity between any two XMPP entities.
    3. +
+ + + +

The typical usage for stream-level pings is for a server to test the viability of the underlying stream connection by pinging a connected client or server (however, a client may send pings as well). This is done by sending an &IQ; set over the stream, which SHOULD NOT include 'to' and 'from' addresses.

+ + + + ]]> +

If the other party to the stream supports the ping namespace, it MUST return an IQ result:

+ + ]]> +

If the other party to the stream does not support the ping namespace, it MUST return an IQ error, which SHOULD be &unavailable;:

+ + + + + + + ]]> + + +

For end-to-end pings, the 'from' and 'to' addresses are necessary.

+ + + + + ]]> +

If the receiving entity supports the ping namespace, it SHOULD return an IQ result:

+ + ]]> +

If the receiving entity does not support the ping namespace, it SHOULD return an IQ error, which SHOULD be &unavailable;:

+ + + + + + + ]]> +

However, the receiving entity MAY ignore the IQ (e.g., if doing so would reveal presence information to an entity that is not authorized to view that information).

+ + + + +

This specification introduces no known security concerns above and beyond those specified in RFC 3920.

+ + + +

No interaction with &IANA; is necessary as a result of this document.

+ + + + +

The ®ISTRAR; shall include 'urn:xmpp:ping' in its registry of protocol namespaces (see &NAMESPACES;).

+ + + + + + + + + + + + + + + + + + ]]> + +