From c397fef7afb3b3a5955bfe3b8953710745ad75bf Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 7 Aug 2007 19:10:25 +0000 Subject: [PATCH] added service discovery use case git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1110 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0066.xml | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/xep-0066.xml b/xep-0066.xml index fc5cb323..01a47c0f 100644 --- a/xep-0066.xml +++ b/xep-0066.xml @@ -150,6 +150,30 @@ ]]> + +

If an entity supports the out of band data protocol, it MUST report that by including a service discovery feature of "jabber:iq:oob" and/or "jabber:x:oob" in response to a &xep0030; information request:

+ + + + ]]> + + + ... + + + ... + + + ]]> +

The value of the <url/> element is not limited to URIs that conform to the http: URI scheme (as specified by &rfc2616;). For example, file transfers could also be effected using ftp: URIs as (specified by &rfc0959;). Going further afield, several existing Jabber clients use the callto: URI scheme to initiate voice conferencing via NetMeeting or GnomeMeeting. Other out-of-band communications could be initiated in a similar way via URI schemes such as sip: (as specified by &rfc3261;). All of these usages are allowed by the existing OOB namespaces, as long as the value of the <url/> element is a valid URI (as specified by &rfc3986;).