From 5a603999e059109b5792460c6e58d07c09897c93 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 16 May 2007 22:35:41 +0000 Subject: [PATCH] Proposed git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@842 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0156.xml | 2 +- xep-0199.xml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xep-0156.xml b/xep-0156.xml index 96e1be00..acab0677 100644 --- a/xep-0156.xml +++ b/xep-0156.xml @@ -10,7 +10,7 @@ This document defines a DNS TXT Resource Record format for use in discovering alternative methods of connecting to an XMPP server. &LEGALNOTICE; 0156 - Experimental + Proposed Standards Track Standards Council diff --git a/xep-0199.xml b/xep-0199.xml index 96cb1c88..3bd38ac2 100644 --- a/xep-0199.xml +++ b/xep-0199.xml @@ -10,7 +10,7 @@ This document defines an XMPP protocol extension for sending pings over XML streams. &LEGALNOTICE; 0199 - Experimental + Proposed Standards Track Standards Council @@ -55,7 +55,7 @@

The XMPP ping protocol is extremely simple:

  1. The pinging entity sends an IQ-get containing a <ping/> element qualified by the 'http://www.xmpp.org/extensions/xep-0199.html#ns' namespace &NSNOTE;.
  2. -
  3. The pinged entity returns either an IQ-result (if it supports the namespace) or an IQ-error (if it does not). The pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence information to an entity that is not authorized to view that information; this mainly applies to client-to-client pings.
  4. +
  5. The pinged entity returns either an IQ-result (if it supports the namespace) or an IQ-error (if it does not). (See the Security Considerations regarding leaks of presence information in the context of pings sent to clients.)
@@ -214,7 +214,7 @@ ]]> -

A pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence information to an entity that is not authorized to view that information; this mainly applies to client-to-client pings.

+

A pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence (network availability) information to an entity that is not authorized to view that information; this mainly applies to pings sent to clients (where the response would reveal client availability) but may apply to other entities as well.