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

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Mon, 17 October 2011 22:28 UTC

Return-Path: <pravindran@sonusnet.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF121F0C4C for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 15:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.908
X-Spam-Level:
X-Spam-Status: No, score=-2.908 tagged_above=-999 required=5 tests=[AWL=-0.309, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Al+8JskyIn8 for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 15:28:23 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5B40F1F0C43 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 15:28:23 -0700 (PDT)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p9HMStnd030335; Mon, 17 Oct 2011 18:28:55 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail06.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Oct 2011 18:28:21 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Oct 2011 03:58:03 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF51159957@sonusinmail02.sonusnet.com>
In-Reply-To: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling
Thread-Index: AcyK59gjnHrw6AUkQx6KmrMgad4vKACMb4Ng
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com>
From: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
To: "Cullen Jennings" <fluffy@cisco.com>, <rtcweb@ietf.org>, <public-webrtc@w3.org>
X-OriginalArrivalTime: 17 Oct 2011 22:28:21.0388 (UTC) FILETIME=[1392A4C0:01CC8D1C]
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>
Subject: Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2011 22:28:24 -0000

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

>-----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