Add Jingle query type and XMPP registrar submission.
This document defines a way for an entity that can initiate a Jingle session (often for the purpose of file transfer as specified in &xep0234;) to advertise that session, thus enabling a receiver to then request initiation of the session by the sender. In essence, this document defines the Jingle equivalent of &xep0137; (previously defined for &xep0095;).
+This document defines a way for an entity that can initiate a &xep0166; session (often for the purpose of file transfer as specified in &xep0234;) to advertise that session, thus enabling a receiver to then request initiation of the session by the sender. In essence, this document defines the Jingle equivalent of &xep0137; (previously defined for &xep0095;).
The 'from' attribute MUST be present and MUST be the valid JID for the session owner.
-The 'id' attribute is an opaque identifier. This attribute MUST be present, and MUST be a valid non-empty string. It uniquely identifies the published request at the session owner's JID.
+The 'id' attribute is an opaque identifier, called the "jinglepub identifier". This attribute MUST be present, and MUST be a valid non-empty string. It uniquely identifies the published request at the session owner's JID.
The <jinglepub/> element MUST contain a <description/> element qualified by the namespace of the relevant Jingle application format (e.g., <description xmlns='urn:xmpp:jingle:apps:file-transfer:4'/> for file transfer).
The <jinglepub/> element MAY contain one or more <meta/> elements qualified by the jingle-pub namespace; if more than one element is included, each element MUST have a different value for the 'xml:lang' attribute.
The <jinglepub/> element MAY contain a <uri/> element which contains a URI for an alternative way to access the content, or other information about the content. The resource provided by the URI SHOULD be meaningful for clients that do not directly support the included Jingle content definitions, and accessing the URI MAY result in a different experience than initiating the published Jingle session. For example, the URI could be to a content landing page of an image hosting service from which an image could be viewed instead of directly downloading the image file.
@@ -138,6 +144,20 @@ ]]>In general, the process to trigger a stream initiation request is as follows:
+ |
+ |-------------------------->|
+ |
A potential receiver requests initiation of the session by sending an IQ-get to the sender, using the <start xmlns='urn:xmpp:jinglepub:1'/> element. This element contains the 'id' attribute to specify which published stream to retrieve:
This document defines the 'jingle' XMPP URI/IRI querytype, + which MUST posses an 'id' key/value pair, whose value is the + "jinglepub identifier".
+ +The information found in such an URI, an XMPP address and a + "jinglepub identifier", can be used to trigger an an Jingle + session initation request as specified in ยง 2.2. This + Jingle session can be used to transfer files (&xep0234;), audio + and video streams (&xep0167;) and other Jingle application + formats.
+ +This document introduces no security concerns beyond those specified in XEP-0060 and the relevant Jingle application format in use.
@@ -245,6 +283,27 @@The ®ISTRAR; will be requested to include 'urn:xmpp:jinglepub:1' in its registry of protocol namespaces.
As authorized by &xep0147;, the XMPP Registrar maintains a + registry of queries and key-value pairs for use in XMPP URIs (see + &QUERYTYPES;).The following submission registers the 'jingle' + querytype.
+ +
+ jingle
+ urn:xmpp:jinglepub:1
+ enables retrieving Jingle sessions (file transfer, etc.)
+ XEP-0358
+
+ id
+ The 'jinglepub' identifier
+
+
+
+