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

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Wed, 12 June 2013 23:12 UTC

Return-Path: <matthew.kaufman@skype.net>
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 2990611E80FD for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 16:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 i73p7Rfer+md for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 16:12:52 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFB311E80F8 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 16:12:51 -0700 (PDT)
Received: from BN1AFFO11FD010.protection.gbl (10.58.52.203) by BN1BFFO11HUB024.protection.gbl (10.58.53.134) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 12 Jun 2013 23:11:37 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD010.mail.protection.outlook.com (10.58.52.70) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 12 Jun 2013 23:11:36 +0000
Received: from TK5EX14MBXC274.redmond.corp.microsoft.com ([169.254.3.236]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Wed, 12 Jun 2013 23:11:34 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Parthasarathi R <partha@parthasarathi.co.in>
Thread-Topic: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review
Thread-Index: Ac5nk3+ps46dBqooTTyECIsVCFaIQwAAUnbQAAo/lwA=
Date: Wed, 12 Jun 2013 23:11:34 +0000
Message-ID: <9515CA24-1B11-4D40-AC5F-0E54D977C470@skype.net>
References: <20130612173723.20266.87116.idtracker@ietfa.amsl.com> <004601ce6795$ee3546a0$ca9fd3e0$@co.in>
In-Reply-To: <004601ce6795$ee3546a0$ca9fd3e0$@co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-ID: <79B80949A2B99D43800DB23B9B405F50@microsoft.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(377454002)(199002)(24454002)(377424003)(51704005)(13464003)(53754005)(56816003)(6806003)(54316002)(36756003)(23726002)(81542001)(77096001)(74502001)(79102001)(74662001)(33656001)(56776001)(74366001)(47976001)(47446002)(50986001)(46102001)(76786001)(31966008)(51856001)(76482001)(49866001)(77982001)(54356001)(76796001)(47736001)(53806001)(50466002)(59766001)(4396001)(80022001)(74706001)(65816001)(69226001)(47776003)(20776003)(46406003)(63696002)(81342001)(15202345002)(16406001)(74876001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB024; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08756AC3C8
Cc: Elangovan Manickam <elangovan.manickam@nsn.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
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 23:12:57 -0000

I have a meta review comment: does the fact that the content of this document is not null mean that the reasoning for choosing SDP O/A as the API surface was faulty?

Matthew Kaufman

(Sent from my iPhone)

On Jun 12, 2013, at 10:55 AM, "Parthasarathi R" <partha@parthasarathi.co.in> wrote:

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