IETF Logo Mail Archive

Re: [rtcweb] Does ROAP mandate the on-the-wire format?

Matthew Kaufman <matthew.kaufman@skype.net> Fri, 21 October 2011 17:47 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 0CBAA1F0C91 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 10:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level:
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 0AowdWBSMU2Q for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 10:47:15 -0700 (PDT)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id 7B8BC1F0C8C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 10:47:15 -0700 (PDT)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id CC1DE1707; Fri, 21 Oct 2011 19:47:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=subject :references:content-transfer-encoding:from:content-type :in-reply-to:message-id:date:to:cc:mime-version; s=mx; bh=dCTkk2 odWSA5Ph6Ro7fa0+BmUT8=; b=iXqOuY1poClG10VdwRPTGU7tG9MYx8hhKGFcnJ czcs2n1Clu/beaRbhezdNNOSwPnSurg3r3V2AUu/Ru4sApJ5/+OxJeD5G8BTc2kP yejcohTsP14T4l3RCznky3S627Cjy65Mbp5pRxlMNaS1KWUobFfjCHrlEueQSTnC wxhKg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=subject:references :content-transfer-encoding:from:content-type:in-reply-to :message-id:date:to:cc:mime-version; q=dns; s=mx; b=vBbF6pTbyIwa ZHHsog9R3JMma7WQiyc4eceRjVPvwtv0kajBCTjop+Bvf8jY1iD1QmehuTAgovbo qGga3ye75ueQQqquIRfoY0fibyhBUixK8Nt1nAxud0gnP3bYl1gX/cWzzTR2USq/ cQAlgkcQBQYBFVW8EbjOMlqwcwpiCLw=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id C973E7F8; Fri, 21 Oct 2011 19:47:14 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id A35A31672682; Fri, 21 Oct 2011 19:47:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TnPEB85v2WJs; Fri, 21 Oct 2011 19:47:13 +0200 (CEST)
Received: from zimbra.skype.net (lu2-zimbra.skype.net [78.141.177.82]) by zimbra.skype.net (Postfix) with ESMTP id C810C1672681; Fri, 21 Oct 2011 19:47:13 +0200 (CEST)
References: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com> <F6C22392-95FE-4CB2-836A-5DF1B5143F8B@acmepacket.com> <CALiegfnTJVJTnNy-V_UrQtzAptQ1LUhCyaZFvsAr-L39ePBFGw@mail.gmail.com>
Content-Transfer-Encoding: base64
From: Matthew Kaufman <matthew.kaufman@skype.net>
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <CALiegfnTJVJTnNy-V_UrQtzAptQ1LUhCyaZFvsAr-L39ePBFGw@mail.gmail.com>
Message-Id: <5E920713-0B41-493D-9457-7FE48DB6A98D@skype.net>
Date: Fri, 21 Oct 2011 19:47:13 +0200
To: Iñaki Baz Castillo <ibc@aliax.net>
Mime-Version: 1.0
X-Mailer: Zimbra 6.0.9_GA_2686 (MobileSync - Apple-iPad2C2/812.1)
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Does ROAP mandate the on-the-wire format?
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: Fri, 21 Oct 2011 17:47:16 -0000


On Oct 21, 2011, at 9:43 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> 
> 
> If ROAP includes a real SDP (as the draft currently states) then I'm
> done as I just need to create a ROAP object (in JavaScript) and pass
> it the received SDP string (and also set some session status
> variables, which can be easily mapped from the received SIP
> request/response).
> 
> 

If you can do this as easily as it sounds above, and it supports both early media and forking, then I think we've put far too much into the browser logic. So this is actually a good test of the design.

For a browser, there should be no such thing as early media... Just media.

And for a browser, there should be no such thing as forking, just two (or more) connection objects that represent the two (or more) possible call legs.

And it should be possible, with the right JavaScript and the right APIs to achieve exactly what you describe above. But perhaps not as easily as you describe.

Matthew Kaufman

Sent from my iPad, on a plane

v2.23.0 | Report a Bug | By Email