Subject: Re: [rtcweb] Does ROAP mandate the on-the-wire format?
From: Iñaki Baz Castillo <[email-masked]>
To: Matthew Kaufman <[email-masked]>
Cc: "<[email-masked]>" <[email-masked]>
Date: Fri, 21 Oct 2011 20:12:09 +0200
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>

2011/10/21 Matthew Kaufman <[email-masked]>:
> If you can do this as easily as it sounds above, and it supports both early media and forking, then I think we've put far too much into the browser logic. So this is actually a good test of the design.
>
> For a browser, there should be no such thing as early media... Just media.

As Hadriel has pointed out, in SIP early media is just a *normal*
media session but without a confirmed INVITE transaction (not a final
response yet, but just 180/183 with SDP). So there is no problem in
implementing early media in the browser.

> And for a browser, there should be no such thing as forking,

Why not? my current implementation can receive different SIP 180/183
with different To-tags, which means "forking".

Regards.

-- 
Iñaki Baz Castillo
<[email-masked]>