diff --git a/xep-0247.xml b/xep-0247.xml index c9c7598d..77cd0b5e 100644 --- a/xep-0247.xml +++ b/xep-0247.xml @@ -60,7 +60,7 @@

First, the party that wishes to initiate the stream determines the responder's capabilities (via &xep0030; or &xep0115;). Here we assume that the responder supports a service discovery feature of 'urn:xmpp:tmp:jingle:apps:xmlstream' &NSNOTE; corresponding to the Jingle XML stream functionalited defined herein, as well as the 'urn:xmpp:tmp:jingle:transports:bytestreams' and 'urn:xmpp:tmp:jingle:transports:ibb' features currently defined in &xep0234;.

The initiator then sends a Jingle session-initiation request to the responder. The content-type of the request specifies two things:

    -
  1. An application type of "urn:xmpp:tmp:jingle:apps:xmlstream" &NSNOTE;, where the <description/> element specifies parameters for the XML stream, where the parameters map to those provided in &xep0155; in a way that is consistent with &xep0116;.

  2. +
  3. An application type of "urn:xmpp:tmp:jingle:apps:xmlstream" &NSNOTE;, where the <description/> element specifies parameters for the XML stream and the parameters map to those provided in &xep0155; in a way that is consistent with &xep0116;.

  4. Options for the reliable transport method, such as In-Band Bytestreams ("IBB") as defined in XEP-0047 or SOCKS5 Bytestreams ("S5B") as defined in XEP-0065.

In this example, the initiator is <alice@example.org>, the responder is <bob@example.com>, and the initiation request specifies Alice's desired stream parameters along with a transport method of "bytestreams" (i.e., XEP-0065).