Re: [rtcweb] Offer & Answer interworking between JSEP & SIP draft for review
Roman Shpount <roman@telurix.com> Wed, 12 June 2013 23:27 UTC
Return-Path: <roman@telurix.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 C130721E80BE for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 16:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, NO_RELAYS=-0.001]
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 QfgybrkHbr7T for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 16:27:16 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id C81F921E80BA for <rtcweb@ietf.org>; Wed, 12 Jun 2013 16:27:15 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a12so5758359wgh.16 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 16:27:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8dSDQaOG2YtXVlwocxePKjjatilKzDEN41I3mp+n3AM=; b=oL9w5up/vnRqokKuBDaPFkyOom2nF7VWloK9G3B2SWIZV8rQGM5PIB1ELWWxREOWu7 I/7Bl21/WlzRBrHNNhxuu6a0RoIg7EoJ1YTJZFZlIbli01ZRC7wPHbbqSkt9qja/pxlT ePLErtVxi5VZvchlpgzPID7BQqI+hoELpSsriqbz5A77mKHr6eF93u9OMWJDO6dOHBxW ZhmMJZNhUN4posMcI6u5XPIWNrJQT5EYDdS71XwZgymFy0aZyVrU7qNTUjg3YNQBxgqk IVid0r4Z0n1axuRdo5p4dl2pHK0QmkOMG1xo6uLLmDNEWjspcWGonNhMzrUfiEQmVoN+ ddSw==
X-Received: by 10.194.238.199 with SMTP id vm7mr3262354wjc.37.1371079634912; Wed, 12 Jun 2013 16:27:14 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [2a00:1450:400c:c00::22d]) by mx.google.com with ESMTPSA id b19sm27921702wik.10.2013.06.12.16.27.13 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Jun 2013 16:27:14 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id j13so2088177wgh.0 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 16:27:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.87.71 with SMTP id v7mr13238315wjz.33.1371079633322; Wed, 12 Jun 2013 16:27:13 -0700 (PDT)
Received: by 10.216.52.134 with HTTP; Wed, 12 Jun 2013 16:27:13 -0700 (PDT)
In-Reply-To: <9515CA24-1B11-4D40-AC5F-0E54D977C470@skype.net>
References: <20130612173723.20266.87116.idtracker@ietfa.amsl.com> <004601ce6795$ee3546a0$ca9fd3e0$@co.in> <9515CA24-1B11-4D40-AC5F-0E54D977C470@skype.net>
Date: Wed, 12 Jun 2013 19:27:13 -0400
Message-ID: <CAD5OKxupjaX5Jby+4sDeFQDPr8sKRLcL+aE7SGLxe_GR26Cx4g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary="047d7bf10ab080cd5404defd5adf"
X-Gm-Message-State: ALoCoQnUBd5oXWIJDycK2M92jHNAEG7StJZKQhkHJNDpzFXGEqxL7Es8yClKPOAIcIUVynJ/HCnl
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:27:17 -0000
To be honest, the whole SDP O/A affair reminds me the verse from Haddock's Eyes song by Lewis Carroll: But I was thinking of a plan To dye one's whiskers green,And always use so large a fan That they could not be seen. The whole thing would be easier to use, simpler to standardize, and much simpler to interop with SIP if instead of O/A underlying C++ API's from Voice and Video engines were mapped to JavaScript. _____________ Roman Shpount On Wed, Jun 12, 2013 at 7:11 PM, Matthew Kaufman (SKYPE) < matthew.kaufman@skype.net> wrote: > 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 > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
- [rtcweb] Offer & Answer interworking between JSEP… Parthasarathi R
- Re: [rtcweb] Offer & Answer interworking between … Christer Holmberg
- Re: [rtcweb] Offer & Answer interworking between … Matthew Kaufman (SKYPE)
- Re: [rtcweb] Offer & Answer interworking between … Roman Shpount
- Re: [rtcweb] Offer & Answer interworking between … Erik Lagerway
- Re: [rtcweb] Offer & Answer interworking between … Parthasarathi R
- Re: [rtcweb] Offer & Answer interworking between … Parthasarathi R