IETF Logo Mail Archive

Re: [rtcweb] Mapping between SIP and ROAP/JSEP

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Wed, 09 May 2012 06:52 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 7DCCC21F84E4 for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 23:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.223
X-Spam-Level:
X-Spam-Status: No, score=-6.223 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_MED=-4]
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 Z3ZBFWh1Dfxz for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 23:52:46 -0700 (PDT)
Received: from na3sys010aog101.obsmtp.com (na3sys010aog101.obsmtp.com [74.125.245.70]) by ietfa.amsl.com (Postfix) with ESMTP id 209F121F8505 for <rtcweb@ietf.org>; Tue, 8 May 2012 23:52:46 -0700 (PDT)
Received: from USMA-EX-HUB2.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob101.postini.com ([74.125.244.12]) with SMTP ID DSNKT6oUPUnrWMlb5xZk+pP8WAwRzeCsKDMM@postini.com; Tue, 08 May 2012 23:52:46 PDT
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by USMA-EX-HUB2.sonusnet.com (66.203.90.17) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 9 May 2012 02:52:56 -0400
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0355.002; Wed, 9 May 2012 12:22:41 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Avasarala, Ranjit" <Ranjit.Avasarala@Polycom.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Mapping between SIP and ROAP/JSEP
Thread-Index: Ac0tr4YLviHfLY88RY29wN4t47YFowAAJYtA
Date: Wed, 09 May 2012 06:52:40 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C16033818@inba-mail01.sonusnet.com>
References: <1F2A2C70609D9E41844A2126145FC09804BCD25222@HKGMBOXPRD22.polycom.com>
In-Reply-To: <1F2A2C70609D9E41844A2126145FC09804BCD25222@HKGMBOXPRD22.polycom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.54.99]
Content-Type: multipart/alternative; boundary="_000_387F9047F55E8C42850AD6B3A7A03C6C16033818inbamail01sonus_"
MIME-Version: 1.0
Subject: Re: [rtcweb] Mapping between SIP and ROAP/JSEP
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: Wed, 09 May 2012 06:52:47 -0000

Ranjit,

I agree with you that Interworking document for JSEP to SIP is important for developing the interworking solution. I'll interested in contributing one such draft. Such a draft will help in identify the gap in JSEP to support SIP interworking like UPDATE during early dialog.

Thanks
Partha

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Avasarala, Ranjit
Sent: Wednesday, May 09, 2012 12:19 PM
To: rtcweb@ietf.org
Subject: [rtcweb] Mapping between SIP and ROAP/JSEP

Hi

Is there any interest in the coming up with a mapping between SIP and ROAP/JSEP protocols?  Though JSEP is a set of APIs as of now which map closely with ROAP APIs, ROAP has messages like OFFER,ANSWER and OK which can be mapped to SIP.

Comment?

Thanks

Regards
Ranjit

v2.23.0 | Report a Bug | By Email