W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2015

Re: Javascript based browser API to send/receive the RTCP APP messages

From: Justin Uberti <juberti@google.com>
Date: Wed, 18 Feb 2015 11:18:37 -0800
Message-ID: <CAOJ7v-3miT12hwDROVEr0up4TLjx5W2o_+PQiSzSSvk2M329aA@mail.gmail.com>
To: Bibhudatta Biswal <bbibhu@kodiaknetworks.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
If you use BUNDLE, these disadvantages go away entirely.

Right now there are no plans to support RTCP APP messaging in the 1.0
timeframe.

On Mon, Feb 16, 2015 at 8:12 PM, Bibhudatta Biswal <
bbibhu@kodiaknetworks.com> wrote:

> Thanks Randell for the support.
>
>
>
> Implementing DataChannels to support the RTCP APP message has the
> following disadvantages.
>
> ·         Consumes the additional resource on the operator’s NAT/Firewal
> to create the separate port/connection mapping.
>
> ·         In the RTCP-MUX scenarios, we need to have the separate DTLS
> session for the data channel just to send/receive the RTCP APP message
> which could have been done as SRTCP message on the same RTP port.
>
>
>
> In Push To Talk Over Cellular applications, the Media Burst Control
> Protocol (MBCP) is used to exchange the floor/volley information which is
> based on the RTCP Application Packets (RTCP: APP). The MBCP protocol is
> defined by the Open Mobile Alliance(OMA) group is widely used for Push To
> Talk over cellular applications.
>
>
>
> Please find the link to the specification below.
>
>
>
>
> http://technical.openmobilealliance.org/Technical/release_program/docs/PoC/V2_0-20071002-C/OMA-TS-PoC_UserPlane-V2_0-20071002-C.pdf
>
>
>
>
>
Received on Wednesday, 18 February 2015 19:19:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:43 UTC