…. ¶ The next step is to generate session-level lip sync groups, as defined in [ RFC5888 ], Section 7 . For each group of type "LS" present in the offer, select the local RtpTransceivers that are referenced by the MID values in the specified group, and determine which of them eith…

…--------------+ 1. In can be appropriate to map to the a=mid value defined in [ RFC5888 ]. The 'senders' attribute is optional in Jingle, with a default value of "both"; thus in case the attribute is absent the SDP direction value MUST be considered as 'sendrecv'. The 'action' at…

…how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5888 . Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisio…

…xer with the different incoming RTP sessions, which is the correct behavior." [ RFC5888 10 . Security Considerations Traditionally, security requirements in IETF documents have been expressed with a mixture of requirements words from RFC 2119 RFC2119 ] and the phrases used above.…

…e Session Description Protocol (SDP) 2002-12 Proposed Standard RFC Obsoleted by rfc5888 Allison J. Mankin 6 pages RFC 3524 Mapping of Media Streams to Resource Reservation Flows 2003-04 Proposed Standard RFC Allison J. Mankin 8 pages RFC 3605 Real Time Control Protocol (RTCP) att…

…ation- tag associated with an "m=" section through the use of a 'id' attribute [RFC5888]. It should say: A media recipient informs the media sender about the identification- tag associated with an "m=" section through the use of a 'mid' attribute [RFC5888]. Notes: As you can see …

…ation- tag associated with an "m=" section through the use of a 'id' attribute [RFC5888]. It should say: A media recipient informs the media sender about the identification- tag associated with an "m=" section through the use of a 'mid' attribute [RFC5888]. Notes: As you can see …