Minor changes to track modifications to XEP-0166; updated security considerations for consistency with other transport methods; added section on service discovery.
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;.
+