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

Re: SDP is not suitable for WebRTC

From: <piranna@gmail.com>
Date: Mon, 29 Jul 2013 19:42:59 +0200
Message-ID: <CAKfGGh1_1FPz4JSaUXTiwgUm5KV6VUDt_dCHnNhDRAkZM__xuQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: public-webrtc <public-webrtc@w3.org>, rtcweb@ietf.org
No, this scenario seems more of a beta or maybe an alpha than a polished
1.0 version.
El 29/07/2013 19:34, "Iñaki Baz Castillo" <ibc@aliax.net> escribió:

> Hi, I initiated a thread [*] about Plan-Unified and multiple m lines,
> but it was moved to MMUSIC maillist (don't know why since it is about
> WebRTC applications design):
>
> http://www.ietf.org/mail-archive/web/mmusic/current/msg11966.html
>
> Sorry for the cross-posting but at this point I'm a bit lost and do
> not know which is the appropriate group for my concern.
>
>
>
> So my concern is:
>
>
> - Web application with a SIP over WebSocket client running in the web.
>
> - The web user is provided with a conference SIP URI in which there
> are *already* 8 participants (5 of them emitting audio and video and 3
> just emitting audio).
>
> - The user calls, from his webphone, to the given URI to join the
> conference.
>
>
>
> Let's imagine that the JS app knows the number of participant in the
> conference.
> Let's imagine my browser have mic and webcam.
>
>
>
> QUESTION:
>
> How can my browser join the conference without requiring SDP
> renegotiation from the server and, at the same time, being able to
> send audio/video and receive audio/video from others (different tracks
> / m=lines)?
>
>
>
>
> "SOLUTIONS":
>
>
>
> 1)
>
> I tell my browser to generate a SDP offer with:
>
>   - 1 send/receive m=audio line.
>   - 7 recvonly m=audio line.
>   - 1 send/only m=video line.
>   - 4 recvonly m=video line.
>
> (Obviously this is a joke)
>
>
>
> 2)
>
> SDP seems to allow that the offer and the answer have different number
> of m lines (I'm not aware of that but I believe that SDP can do
> "everything"). So my browser generates a SDP offer with 1 m=audio line
> and 1 m=video line, and the server replies with 8 m=audio lines and 4
> m=video lines.
>
> Will my browser understand such a SDP answer with more m lines than
> its generated offer? I assume NOT.
>
>
>
> 3)
>
> My browser generates a SDP offer with 1 m=audio line and 1 m=video
> line and the server too. And later the server sends re-INVITE with all
> the m lines.
>
> Oppss, SDP renegotiation...
>
>
>
>
> SDP is bad for WebRTC. SDP is good for legacy symmetric communications
> in which there is a single-track audio communication and, of course,
> both endpoints emit audio. But SDP is bad for modern RTC protocols in
> which an endpoint can emit tons of tracks to a single endpoint.
>
>
> Do we really want this for WebRTC 1.0 ?
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
>
>
Received on Monday, 29 July 2013 17:43:28 UTC

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