Re: Issue 154: RTCP Port Control from Peter Thatcher on 2014-10-14 (public-ortc@w3.org from October 2014)

From: Peter Thatcher <pthatcher@google.com>
Date: Tue, 14 Oct 2014 14:29:39 -0700
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <CAJrXDUGs4HXTeA-n+JAK4bGpVMoZki4FcbxuZ4vEL-b9qbf3dw@mail.gmail.com>

Here's an idea:

When the app needs the browser to know the gatherer is RTCP before
gathering (presumably so that the browser can do some kind of
not-specified-by-the-standard "+1 port" behavior), couldn't it just
not call IceGatherer.gather() and instead wait and call
IceTransport.start?  It would delay gathering RTCP candidates 0.5RTT,
but RTCP isn't as time-sensitive as RTP.  Would it be that big of a
deal?

On Wed, Oct 8, 2014 at 12:02 PM, Bernard Aboba
<Bernard.Aboba@microsoft.com> wrote:
> While RFC 3605 defines the "a=rtcp:" SDP attribute which allows for control of the RTCP port, there are legacy RTP implementations that assume that RTCP uses a port of RTP + 1.
>
> Currently there is no way to indicate a relationship between RTP and RTCP RTCIceGatherer objects, or to request that an RTCIceGatherer object created for TCP use the port + 1 of the object created for RTP.
>

Received on Tuesday, 14 October 2014 21:30:50 UTC