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

Erik Lagerway <erik@hookflash.com> Thu, 13 June 2013 00:17 UTC

Return-Path: <elagerway@gmail.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 BDFAA21F99B6 for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 17:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 ib9Pl2mruxPL for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 17:17:36 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 8C80121F99B2 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 17:17:35 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id p58so7541577wes.12 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 17:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=l45H5DwRwQn1snim20AelPLcfVvtoqPEZMA5sgoWIQo=; b=nr4uKduxSG97FiDwX81IUvpI3j4XZfuNS4CiTTNHk4/u910KV7sQArz9C7EFMryiGr c1FIxboE3wlmfT/WcG9FtBQl6/ejJcnjRVztMEsoMrnE/zvzsIerUxYw/0IW+6XNxk1s rlSFUvD0MfaUycxVy4qJUAAV2ZgCgAHtVnknOcJwfQ1ok9kunIJRwEgVRj6dBJEAOKY+ NXUr+4uq5Omm+nlS77kYm1LgJ/ZeP658O4K2ZvhOuFIKmd0MYU5VlicE2FOCQweJM3tw +XBOT74AF8o1RdPA8dB8kAwkJsvzkOEO2LHwuvUmSaYDppVTacS1OQsdn4nQsJMHf1+C +1OA==
MIME-Version: 1.0
X-Received: by 10.180.99.232 with SMTP id et8mr6013524wib.17.1371082649893; Wed, 12 Jun 2013 17:17:29 -0700 (PDT)
Sender: elagerway@gmail.com
Received: by 10.216.22.132 with HTTP; Wed, 12 Jun 2013 17:17:29 -0700 (PDT)
In-Reply-To: <CAD5OKxupjaX5Jby+4sDeFQDPr8sKRLcL+aE7SGLxe_GR26Cx4g@mail.gmail.com>
References: <20130612173723.20266.87116.idtracker@ietfa.amsl.com> <004601ce6795$ee3546a0$ca9fd3e0$@co.in> <9515CA24-1B11-4D40-AC5F-0E54D977C470@skype.net> <CAD5OKxupjaX5Jby+4sDeFQDPr8sKRLcL+aE7SGLxe_GR26Cx4g@mail.gmail.com>
Date: Wed, 12 Jun 2013 17:17:29 -0700
X-Google-Sender-Auth: AzcqtVlC3cUYZRyK8rFDn6wv60o
Message-ID: <CAPF_GTYO8x_gCM3m8mfhmDcj1Ht2DNzDb_vcVsHoxH84kXqY3A@mail.gmail.com>
From: Erik Lagerway <erik@hookflash.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary=f46d041825ac4e023f04defe0e64
Cc: "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: Thu, 13 Jun 2013 00:17:37 -0000

+1 Roman


*Erik Lagerway <http://ca.linkedin.com/in/lagerway> |
*Hookflash<http://hookflash.com>
* *
****


On Wed, Jun 12, 2013 at 4:27 PM, Roman Shpount <roman@telurix.com>; wrote:

> 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 mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>