From ddcb924cef293e8dba8786b4ec3e6eb985eadcb6 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 18 Feb 2009 02:40:56 +0000 Subject: [PATCH] tracking other XEPs git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2751 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index 2caa30ff..ea09e0b4 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -152,7 +152,7 @@

  • The transport negotiation process is defined in the Protocol Description section of this document.

  • The semantics of the &TRANSPORT; element are defined in the Transport Initiation section of this document.

  • Successful negotiation of the Raw UDP method results in use of a datagram transport that is suitable for applications where some packet loss is tolerable, such as audio and video.

    • -

  • If multiple components are to be communicated over the transport in the context of the Real-time Transport Protocol (RTP; see &rfc3550;), the component numbered "1" shall be associated with RTP and the component numbered "2" shall be associated with the Real Time Control Protocol (RTCP).

    • +

  • If multiple components are to be communicated by the application type that uses the transport, the transport shall support those components and assign identifiers for them as described in the specification that defines the application type.

    • @@ -232,7 +232,7 @@ INITIATOR RESPONDER to='romeo@montague.lit/orchard' type='result'/> ]]> -

    As soon as the responding user agrees to proceed with the session, the responding client MUST send a Jingle session-accept to the initiator. This session-accept message MAY include a candidate that is generated by the responder.

    +

    As soon as the responding user agrees to proceed with the session, the responding client MUST send a Jingle session-accept to the initiator. This session-accept message MAY include one or more candidates generated by the responder.