W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2011

Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling

From: Cullen Jennings <fluffy@cisco.com>
Date: Tue, 18 Oct 2011 11:41:52 -0700
Cc: <rtcweb@ietf.org>, <public-webrtc@w3.org>, "Jonathan Rosenberg" <jonathan.rosenberg@skype.net>
Message-Id: <01441535-7FF6-4C88-AA28-53B5CB68374F@cisco.com>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>

So I might have messed up the draft a bit. I'm fine with things can be implemented as dialog statefull, what I want is that it is possible to make a signaling gateway that is only transaction statefull. I'm fine if some signaling gateways are built as dialog statefull.

 (As a side note, some B2BUA are effectively transaction statefull but that is pretty rare )

On Oct 17, 2011, at 15:28 , Ravindran Parthasarathi wrote:

> Cullen/Joanthan,
> I like your proposed idea as it is going in the direction of having
> "standard" signaling protocol for RTCWeb. I'm seeing your proposal as
> SDP offer/answer over websocket and the proposal helps to easy gateway
> development between RTCWeb server and legacy signaling protocols.
> I have fundamental question in the proposal as it proposes RTCWeb server
> as SIP proxy equivalent and in reality, unfortunately most of the SIP
> deployment work is based on B2BUA. The question is whether RTCWeb server
> shall be dialog-state or MUST be transaction-stateful only. 
> Also, session-id in the draft is used to uniquely understand the offerer
> and answerer in the transaction or session. In case it is session, how
> to indicate the termination of the session.

My personal opinion is that to be able to clean up all the state in a clean an easy way, we should add some message to indicate the SDP offer / answer state and related media streams can be discarded.  I'd like to add that to the next version. 

> Thanks
> Partha
>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf
>> Of Cullen Jennings
>> Sent: Saturday, October 15, 2011 8:39 AM
>> To: rtcweb@ietf.org; public-webrtc@w3.org
>> Cc: Jonathan Rosenberg
>> Subject: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling
>> Jonathan and I submitted a new draft on setting up media based on the
>> SDP Offer/Answer model. The ASCII flows are a bit hard to read so until
>> I update them, I recommend reading the PDF version at
>> http://tools.ietf.org/pdf/draft-jennings-rtcweb-signaling-00.pdf
>> Clearly the draft is an early stage but we plan to revise it before the
>> deadline for the IETF 82. Love to get input - particularly on if this
>> looks like generally the right direction to go.
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
Received on Tuesday, 18 October 2011 18:42:32 UTC

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