diff --git a/xep-0261.xml b/xep-0261.xml index eb20bd6b..f77246e7 100644 --- a/xep-0261.xml +++ b/xep-0261.xml @@ -22,6 +22,12 @@ jingle-ibb jingle &stpeter; + + 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 @@ -76,7 +82,7 @@ Initiator Responder id='xn28s7gk' to='juliet@capulet.lit/balcony' type='set'> - + action='session-initiate' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -103,7 +109,7 @@ Initiator Responder id='bsa91h5' to='romeo@montague.lit/orchard' type='set'> - - @@ -174,7 +180,7 @@ Initiator Responder id='znb376s4' to='juliet@capulet.lit/balcony' type='set'> - + action='transport-info' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> @@ -193,8 +199,34 @@ Initiator Responder

The same processing rules and usage guidelines defined in XEP-0047 apply to the Jingle IBB Transport Method.

+ +

To advertise its support for the Jingle In-Band 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:ibb: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-0047 apply to the Jingle IBB Transport Method.

+ +

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

+