W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: Moving forward with SDP control

From: Roman Shpount <roman@telurix.com>
Date: Tue, 16 Jul 2013 14:00:27 -0400
Message-ID: <CAD5OKxvDvQj4__rJrbUfAg8hviFTA1Ereys_0VTYPQwX6qxAVg@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>

We can definitely start in this direction, but would not you think that we
need to define what is available SDP before figuring out all the use cases
that require SDP mangling? Otherwise, the only answer that I can think of
is that we need to be able to modify pretty much everything available in
SDP as long as it controls something (no one should care about the "t="
line). I can come up with use cases that require modification of almost all
the SDP components, such as codecs, codec parameters, codec order, ptime,
bandwidth, and ice candidates, may be with a few exceptions of things like
DTLS fingerprints. Even for the non-modifiable parameters I can come up
with use cases when the application will need to read them. Bottom line,
everything defined in SDP will need to be exposed in API. The only reason
not to expose something in the API is that this SDP portion can be ignored.
We can rate the importance of different SDP components in this group and
only expose "the most important" ones, but I would think this would be
driven by personal preference of group members as much as anything else.
Roman Shpount
Received on Tuesday, 16 July 2013 18:01:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:49 UTC