From ecd0e29c4fd676a204ab5aac66d725d9084c7c36 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 8 Feb 2007 22:09:04 +0000 Subject: [PATCH] 1.1pre1 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@504 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0092.xml | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/xep-0092.xml b/xep-0092.xml index e0148686..aa422644 100644 --- a/xep-0092.xml +++ b/xep-0092.xml @@ -7,11 +7,10 @@
Software Version - This specification provides canonical documentation of the existing 'jabber:iq:version' namespace currently used within the Jabber community. - &LEGALNOTICE; + This specification provides canonical documentation of an XMPP protocol extension for retrieving information about the software version associated with another XMPP entity. &LEGALNOTICE; 0092 - Active - Historical + Draft + Standards Track Standards XMPP Core @@ -23,6 +22,12 @@ http://www.xmpp.org/schemas/iq-version.xsd &stpeter; + + 1.1pre1 + in progress, last updated 2007-02-08 + psa + Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information. + 1.0 2003-10-08 @@ -36,18 +41,19 @@ Initial version.
- +

The Jabber protocols have long included a method for discovering version information about the software running at another entity's JID. This method makes use of the 'jabber:iq:version' namespace and has been documented variously in Internet-Drafts and elsewhere. Because this protocol is not required by &rfc2779;, the 'jabber:iq:version' namespace was removed from &xmppim;. This specification fills the void for canonical documentation.

+

Note Well: The jabber:iq:version protocol SHOULD NOT be used to determine the identity of entities from which an application receives presence (e.g., contacts in a user's roster and certain kinds of gateways); &xep0115; SHOULD be used instead. However, the jabber:iq:version protocol MAY be used to determine the identity of entities from which an application does not receive presence (e.g., servers and many kinds of components).

 - +

The 'jabber:iq:version' namespace provides a standard way for Jabber entities to exchange information about the software version used by the entities. The information is communicated in a request/response pair using an <iq/> element that contains a <query/> scoped by the 'jabber:iq:version' namespace. The following children of the <query/> are allowed in an IQ result:

  • <name/> -- The natural-language name of the software. This element is REQUIRED in a result.
  • <version/> -- The specific version of the software. This element is REQUIRED in a result.
    • -
  • <os/> -- The operating system of the queried entity. This element is OPTIONAL in a result.
    • +
  • <os/> -- The operating system of the queried entity. This element is OPTIONAL in a result (see also the Security Considerations).
 - +

The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).

 - -

There are no security features or concerns related to this proposal.

+ +

Revealing the application's underlying operating system may open the user or system to attacks directed against that operating system; therefore, an application MUST provide a way for a human user or administrator to disable sharing of information about the operating system.

 - +

This document requires no interaction with &IANA;.

 - +

The 'jabber:iq:version' namespace is registered in the protocol namespaces registry maintained by the ®ISTRAR;.

 - +