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

Likepeng <likepeng@huawei.com> Wed, 09 May 2012 08:21 UTC

Return-Path: <likepeng@huawei.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 B156721F85B1 for <rtcweb@ietfa.amsl.com>; Wed, 9 May 2012 01:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.446
X-Spam-Level: **
X-Spam-Status: No, score=2.446 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
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 HOJfgJZCS2Bd for <rtcweb@ietfa.amsl.com>; Wed, 9 May 2012 01:21:53 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7C35821F85AF for <rtcweb@ietf.org>; Wed, 9 May 2012 01:21:52 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFZ03100; Wed, 09 May 2012 04:21:48 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 9 May 2012 01:18:33 -0700
Received: from SZXEML423-HUB.china.huawei.com (10.82.67.162) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 9 May 2012 01:18:36 -0700
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.182]) by szxeml423-hub.china.huawei.com ([10.82.67.162]) with mapi id 14.01.0323.003; Wed, 9 May 2012 16:18:31 +0800
From: Likepeng <likepeng@huawei.com>
To: "Avasarala, Ranjit" <Ranjit.Avasarala@Polycom.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Mapping between SIP and ROAP/JSEP
Thread-Index: Ac0tr4YLviHfLY88RY29wN4t47YFowAC8oJA
Date: Wed, 09 May 2012 08:18:31 +0000
Message-ID: <34966E97BE8AD64EAE9D3D6E4DEE36F2035816DE@szxeml525-mbs.china.huawei.com>
References: <1F2A2C70609D9E41844A2126145FC09804BCD25222@HKGMBOXPRD22.polycom.com>
In-Reply-To: <1F2A2C70609D9E41844A2126145FC09804BCD25222@HKGMBOXPRD22.polycom.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.109.51]
Content-Type: multipart/alternative; boundary="_000_34966E97BE8AD64EAE9D3D6E4DEE36F2035816DEszxeml525mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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 08:21:54 -0000

I think it is useful to have such a draft which provides a mapping between SIP and ROAP/JSEP protocols.

Previously Cullen has an expired draft related to this:
http://tools.ietf.org/html/draft-jennings-rtcweb-signaling-gateway-00

Some time ago, I submitted a draft to map ROAP with XMPP/Jingle.
http://datatracker.ietf.org/doc/draft-li-rtcweb-roap-jingle-interworking/

I need to update it to reflect the JSEP concept.

I would appreciate if anybody has interest to work with me about this.

Thanks,
Kind Regards
Kepeng
发件人: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] 代表 Avasarala, Ranjit
发送时间: 2012年5月9日 14:49
收件人: rtcweb@ietf.org
主题: [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