IETF Logo Mail Archive

Re: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 12 June 2013 18:11 UTC

Return-Path: <prvs=18750f8074=christer.holmberg@ericsson.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 1485721E8084 for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 11:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.695
X-Spam-Level:
X-Spam-Status: No, score=-5.695 tagged_above=-999 required=5 tests=[AWL=0.554, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 9X8xjlC9UGN3 for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 11:11:32 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 15B4521E8056 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 11:11:31 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-a4-51b8b9d27844
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id E6.2A.15700.2D9B8B15; Wed, 12 Jun 2013 20:11:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.02.0328.009; Wed, 12 Jun 2013 20:11:30 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review
Thread-Index: Ac5nmEmmXFOwKCwpR1e2EqmBZUP0kQ==
Date: Wed, 12 Jun 2013 18:11:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3893F6@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvre7lnTsCDab8ZLWYP/Mou8XkT32s Fmv/tbM7MHssWfKTyePn+qvsHh/mf2EPYI7itklKLCkLzkzP07dL4M64vm8WY8Ea8Yp3+++z NDC2CHcxcnJICJhI3L32gxHCFpO4cG89WxcjF4eQwGFGiRU3r0M5Sxgl3rbNAnI4ONgELCS6 /2mDNIgIhEu8eX6ZGcRmFjCVmPjwIDtIiTBQ/N7yKoiSCIn/658wgoRFBPQkVrRpgZgsAqoS 1/qyQCp4BXwlFnVOARvCCHTB91NrmCAGikt8OHidGeIyAYkle85D2aISLx//Y4WwlSR+bLjE AlGvJ3Fj6hQ2CFtbYtnC18wQ8wUlTs58wjKBUWQWkrGzkLTMQtIyC0nLAkaWVYzsuYmZOenl hpsYgTFwcMtv3R2Mp86JHGKU5mBREueNV90RKCSQnliSmp2aWpBaFF9UmpNafIiRiYMTRHBJ NTAm/mRdzytVFar2SfxFgJgkT8zE0AVzmbmOL/gQYlxbX8zq8r2juV+3RW/V3H//+Pg3SGSf C43lPrAi+X38fu7ve9Qs/zEekbXrCfhz65zNpaD3ClliF/S2Gd452Rj8xmuGoE+79fypf9hn 7Fz0VaEwzeIt65QP36I8FsU2rvvle+50R2Np6m8lluKMREMt5qLiRAAAgrfnVAIAAA==
Cc: 'Elangovan Manickam' <elangovan.manickam@nsn.com>
Subject: Re: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review
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, 12 Jun 2013 18:11:38 -0000

Hi,

I have some issues with your way of solving forking.

In sections 5.5 and 5.6, you are mapping SIP Answers to JSEP Offer. I think that is a very bad thing to do, because what happens if something has changed in the associated JSEP Answer? Then you'll have to map that into a SIP Offer, and then again map the associated SIP Answer into a JSEP Offer. Etc etc etc. 

I do like that fact that you are not using PRANSWER, but unfortunately I don't think the suggested way will work :)

My suggestion is still that we should support some kind of "cloning" (I use that as a generic term), in order to support forking.

Regards,

Christer


-----Alkuperäinen viesti-----
Lähettäjä: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] Puolesta Parthasarathi R
Lähetetty: 12. kesäkuuta 2013 20:55
Vastaanottaja: rtcweb@ietf.org
Kopio: 'Elangovan Manickam'
Aihe: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review

Hi all,

Offer/answer Interworking between JSEP & SIP IETF draft is written as JSEP (O/A) model is different from SIP O/A and there is a need of mapping document. This draft will act  as a building block for developing the O/A interwork between SIP & JSEP. The draft is available at http://www.ietf.org/internet-drafts/draft-partha-rtcweb-jsep-sip-00.txt. Could you please provide your valuable review comments.

Thanks
Partha

> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Wednesday, June 12, 2013 11:07 PM
> To: Uwe Rauschenbach; Elangovan Manickam; Parthasarathi Ravindran
> Subject: New Version Notification for draft-partha-rtcweb-jsep-sip- 
> 00.txt
> 
> 
> A new version of I-D, draft-partha-rtcweb-jsep-sip-00.txt
> has been successfully submitted by Parthasarathi Ravindran and posted 
> to the IETF repository.
> 
> Filename:	 draft-partha-rtcweb-jsep-sip
> Revision:	 00
> Title:		 Offer & Answer interworking between JSEP & SIP
> Creation date:	 2013-06-12
> Group:		 Individual Submission
> Number of pages: 13
> URL:             http://www.ietf.org/internet-drafts/draft-partha-
> rtcweb-jsep-sip-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-partha-rtcweb-
> jsep-sip
> Htmlized:        http://tools.ietf.org/html/draft-partha-rtcweb-jsep-
> sip-00
> 
> 
> Abstract:
>    Real time communcation Web (RTCWeb) workgroup defines the real time
>    commmunication using JavaScript Session establishment protocol
> (JSEP)
>    as an offer/answer mechanism.  Session Initiation protocol (SIP) is
>    IETF defined and well deployed protocol for real time communication.
>    This document provides offer & answer interworking between JSEP and
>    SIP.
> 
> 
> 
> 
> The IETF Secretariat

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email