Re: [rtcweb] Checkpointing decisions in RTCWEB

[Robin Raymond <[e-mail]>]

On Fri, Mar 8, 2013 at 9:57 AM, Jim Barnett <[e-mail]>wrote:

> Mary,
>   How can there be interoperability issues if no one is required to use
> SDP over the wire?  Are you saying that there are things that we need that
> SDP cannot express (or cannot be extended to express)?
>
> - Jim
>
>
I just want to clarify something. Is the expectation that an application
developer can (if they so choose) take the SDP, parse it, extract the data,
send in an alternative format and then reassemble the SDP at the remote
side an accepted practice and an expected use case?

Regardless if it is or not, I'm positive that this extraction/assembly
process will be done but I want to make sure the expectation/use case is
absolutely clear. From what I've been reading, the expectation is the
browser generates "blob" and "blob" gets given to other party 'as is' but
perhaps I'm mistaken.

Further, the issue with SDP is also offer/answer. SDP isn't just a
arcane/obtuse format. It's a state machine and a media signalling protocol.
That causes a great deal of pain (breaks or messy hybrids) for other models
even if we can "disassemble and reassemble" SDP.