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

I believe it may be B2BUA along with proxy-capability that a Web server might have. However, Cullen and Jonathan might clearify this.

BR/Radhika

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ravindran Parthasarathi
Sent: Monday, October 17, 2011 6:28 PM
To: Cullen Jennings; rtcweb@ietf.org; public-webrtc@w3.org
Cc: Jonathan Rosenberg
Subject: Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling

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.

Thanks
Partha