From a1133defad647b64ac378d02ca9b5a1796c2fadc Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 9 Mar 2009 18:04:00 +0000 Subject: [PATCH] 0.2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2859 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0260.xml | 60 +++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 50 insertions(+), 10 deletions(-) diff --git a/xep-0260.xml b/xep-0260.xml index cf488ee4..0723d46f 100644 --- a/xep-0260.xml +++ b/xep-0260.xml @@ -24,6 +24,12 @@ jingle &stpeter; &dmeyer; + + 0.2 + 2009-03-09 + psa +

Minor changes to track modifications to XEP-0166; updated security considerations for consistency with other transport methods; added section on service discovery.

+
0.1 2009-02-19 @@ -93,7 +99,7 @@ Romeo Juliet id='xn28s7gk' to='juliet@capulet.lit/balcony' type='set'> - + action='session-initiate' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -130,7 +136,7 @@ Romeo Juliet id='hwd987h' to='romeo@montague.lit/orchard' type='set'> - + action='session-accept' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -169,7 +175,7 @@ Romeo Juliet id='hjdi8' to='juliet@capulet.lit/balcony' type='set'> - + action='transport-info' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -200,7 +206,7 @@ Romeo Juliet id='hz81vf48' to='juliet@capulet.lit/balcony' type='set'> - @@ -251,7 +257,7 @@ Romeo Juliet id='jingle1' to='juliet@capulet.lit/balcony' type='set'> - @@ -285,7 +291,7 @@ Romeo Juliet id='hwd987h' to='romeo@montague.lit/orchard' type='set'> - + action='session-accept' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -324,7 +330,7 @@ Romeo Juliet id='jfd75jk' to='romeo@montague.lit/orchard' type='set'> - - @@ -377,7 +383,7 @@ Romeo Juliet id='is71ns63' to='romeo@montague.lit/orchard' type='set'> - @@ -409,8 +415,42 @@ Romeo Juliet + +

To advertise its support for the Jingle SOCKS5 Bytestreams Transport Method, when replying to &xep0030; information requests an entity MUST return URNs for any version of this protocol that the entity supports -- e.g., "urn:xmpp:jingle:transports:s5b:0" for this version &VNOTE;.

+ + + + ]]> + + + + + + + ]]> +

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

+
+ -

The same security considerations defined in XEP-0065 apply to the Jingle S5B Transport Method.

+ +

The exchange of StreamHosts might result in exposure of the sender's IP addresses, which comprise a form of personally identifying information. A Jingle client MUST enable a user to control which entities will be allowed to receive such information. If a human user explicitly accepts a session request, then the client SHOULD consider that action to imply approval of IP address sharing. However, waiting for a human user to explicitly accept the session request can result in delays during session setup, since it is more efficient to immediately begin sharing transport candidates. Therefore, it is RECOMMENDED for the client to immediately send transport candidates to a contact (without waiting for explicit user approval of the session request) in the following cases:

+
    +
  1. The user has permanently and formally authorized the contact to view the user's presence information via a presence subscription as reflected in an XMPP roster item (see &xmppim;).
  2. +
  3. The user has temporarily and dynamically shared presence with the contact via "directed presence" as described in RFC 3921.
  4. +
  5. The user has explicitly added the contact to a "whitelist" of entities who are allowed to access the user's personally-identifying information.
  6. +
+
+ +

A Jingle implementation SHOULD support security preconditions that are enforced before application media is allowed to flow over the bytestream, such as those described in &xtls;.

+