IETF Logo Mail Archive

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

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 21 October 2011 18:05 UTC

Return-Path: <HKaplan@acmepacket.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 10F4721F8783 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.127
X-Spam-Level:
X-Spam-Status: No, score=-2.127 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, J_CHICKENPOX_27=0.6]
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 xO+3DQMei8j0 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:05:52 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 79DBA21F85C7 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 11:05:52 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 21 Oct 2011 14:05:50 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Fri, 21 Oct 2011 14:05:51 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Thread-Topic: [rtcweb] Does ROAP mandate the on-the-wire format?
Thread-Index: AQHMkBwQmEXXTEsSfEaLWlSDmayJ4w==
Date: Fri, 21 Oct 2011 18:05:49 +0000
Message-ID: <CA84D0C6-8BBA-4471-B77D-0C39210959B7@acmepacket.com>
References: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com> <F6C22392-95FE-4CB2-836A-5DF1B5143F8B@acmepacket.com> <CALiegfnTJVJTnNy-V_UrQtzAptQ1LUhCyaZFvsAr-L39ePBFGw@mail.gmail.com> <5E920713-0B41-493D-9457-7FE48DB6A98D@skype.net>
In-Reply-To: <5E920713-0B41-493D-9457-7FE48DB6A98D@skype.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2674A7316C3DD24C82EC774542A8D204@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
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 18:05:53 -0000

On Oct 21, 2011, at 1:47 PM, Matthew Kaufman wrote:

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

Not disagreeing with your high-level point... but I don't think early media is possible in RTCweb no matter how we dice it, if by "early media" you mean your JS+browser being able to render media before getting some high-path info back from the Server.  Because you can't do ICE until you know the other side's ICE user/pass, so media won't flow till then.  Right?

-hadriel

v2.23.0 | Report a Bug | By Email