From 3dd1e4b590ecd2353ebb64b66c19412e39370010 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Tue, 24 May 2016 13:22:53 +0200 Subject: [PATCH 1/5] Add 'jingle' XMPP URI querytype to XEP-0358 --- xep-0358.xml | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/xep-0358.xml b/xep-0358.xml index 1c222ee4..2011084c 100644 --- a/xep-0358.xml +++ b/xep-0358.xml @@ -25,6 +25,12 @@ &fippo; &lance; &stpeter; + + 0.3 + 2016-05-24 + fs +

Add Jingle query type and XMPP registrar submission.

 + 0.2 2015-08-11 @@ -234,6 +240,25 @@ ]]> + + +

This document defines the 'jingle' XMPP URI/IRI querytype, + which MUST posses an 'id' key/value pair, whose value is the + 'jinglepub' identifier (the <jinglepub/> 'id' + attribute).

+ + + +

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 +270,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 + + +]]> + + Date: Tue, 24 May 2016 16:38:05 +0200 Subject: [PATCH 2/5] XEP-0358: Use &xep0166; at least once --- xep-0358.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0358.xml b/xep-0358.xml index 2011084c..2c520e18 100644 --- a/xep-0358.xml +++ b/xep-0358.xml @@ -65,7 +65,7 @@ -

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;).

 From 8dc8708acb46dd29cd040f41a62e7c0ed915bc31 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Tue, 24 May 2016 16:45:02 +0200 Subject: [PATCH 3/5] Add ASCII art for XEP-0358 initiation process --- xep-0358.xml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/xep-0358.xml b/xep-0358.xml index 2c520e18..333a43f3 100644 --- a/xep-0358.xml +++ b/xep-0358.xml @@ -144,6 +144,20 @@ ]]> +

In general, the process to trigger a stream initiation request is as follows:

+ | + |---------------------------->| + | | + |<----------------------------| + | session-initiate | + |<----------------------------| + | [further jingle | + | negotiation] | + |<--------------------------->| + | |]]>

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:

Date: Wed, 25 May 2016 08:17:23 +0200 Subject: [PATCH 4/5] Introduce "jinglepub identifier" in XEP-0358 --- xep-0358.xml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/xep-0358.xml b/xep-0358.xml index 333a43f3..ad684434 100644 --- a/xep-0358.xml +++ b/xep-0358.xml @@ -81,7 +81,7 @@ ]]>

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.

@@ -258,14 +258,13 @@ Initiator Responder

This document defines the 'jingle' XMPP URI/IRI querytype, which MUST posses an 'id' key/value pair, whose value is the - 'jinglepub' identifier (the <jinglepub/> 'id' - attribute).

+ "jinglepub identifier".

The information found in such an URI, an XMPP address and a - 'jinglepub' identifier, can be used to trigger an an Jingle + "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 From 3a62faf4eb6ab3f51441112aa78625198f0a9589 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Wed, 25 May 2016 08:19:26 +0200 Subject: [PATCH 5/5] =?UTF-8?q?XEP-0358:=20Initator/Response=20=E2=86=92?= =?UTF-8?q?=20Requester/Publisher?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- xep-0358.xml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/xep-0358.xml b/xep-0358.xml index ad684434..a387f05b 100644 --- a/xep-0358.xml +++ b/xep-0358.xml @@ -146,18 +146,18 @@

In general, the process to trigger a stream initiation request is as follows:

| - |---------------------------->| - | | - |<----------------------------| - | session-initiate | - |<----------------------------| - | [further jingle | - | negotiation] | - |<--------------------------->| - | |]]> +Requester Publisher + | | + | | + |-------------------------->| + | | + |<--------------------------| + | session-initiate | + |<--------------------------| + | [further jingle | + | negotiation] | + |<------------------------->| + | |]]>

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: