Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Wed, 30 October 2013 18:46 UTC
Return-Path: <jlaurens@cisco.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 9952621E8165 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 11:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.315
X-Spam-Level:
X-Spam-Status: No, score=-10.315 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 hM8r13DifvON for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 11:46:11 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id B10D211E8160 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 11:44:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18028; q=dns/txt; s=iport; t=1383158658; x=1384368258; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=FZwCDKLEahnLT4ifoJsaTUnLSi80mKoIJ+kYZO006f4=; b=Vqhw7oQTP6Cj566pf0omxZkDXJDJQUZO9fX2B+SjCRzvIxkyDhQxvrKB YwvDd6VBGenroZUIKBaFvbXoBOxEHG8FEbz/ouv74VTxhioKymVES3yEi aF3Rass70EPoBuOxq/SP470GcT3nPju/Fj3ohawWA00uZyvYOlseVwffO E=;
X-Files: smime.p7s : 4459
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFANpScVKtJV2a/2dsb2JhbABZgkNEOFS/CUuBJxZ0giUBAQEDAQEBAWsLBQsCAQgOCgokAh8GCyUCBA4FCAaHZwMJBg2wdA2JZwSMX4I/FhcEB4MfgQ0DkC2BMIRCjj2FN4FogT6BaAc7
X-IronPort-AV: E=Sophos; i="4.93,603,1378857600"; d="p7s'?scan'208,217"; a="278638905"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 30 Oct 2013 18:44:09 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9UIi9Cc022694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 30 Oct 2013 18:44:09 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.247]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Wed, 30 Oct 2013 13:44:08 -0500
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: Steve Sokol <ssokol@digium.com>
Thread-Topic: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
Thread-Index: AQHO1XYAmf9gXRoQT1qWOAYOe51tPQ==
Date: Wed, 30 Oct 2013 18:44:08 +0000
Message-ID: <FCBEDCB500188C488DA30C874B94F80E1C018EF5@xmb-rcd-x03.cisco.com>
References: <186CE8D65BA3A741A81A543F936DD0D10A5803D8@xmb-rcd-x07.cisco.com> <527107e5.0201430a.0aa1.ffff9b09SMTPIN_ADDED_BROKEN@mx.google.com> <CAGgHUiSOFGxuNmqoa9BS2+_yjT2hb20KDut5WL264x5tdpTU-g@mail.gmail.com> <CA+23+fHdKBwezhtsES1w_qDJgvVC=ChaBcaF1x0_N65aKv-9yQ@mail.gmail.com> <CAHZ_z=wsQFB=SoH5zq-p-J7KkqrAx4gWJFkPLyAoFtZ8b2zP+w@mail.gmail.com> <527128A7.3050101@nostrum.com> <20131030164716.3d3be136@lminiero> <CALQ_quj6LyjhV1JocAH-aY7o4ppLNZFmYfe9kLVsddzTZA2U6g@mail.gmail.com> <CAHZ_z=xAviWcmpEhp-JHgzzCG-zMF5itqtvs8tyuK0YPTq8GoQ@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123CF835F@xmb-aln-x02.cisco.com> <CAFg4Z=wnoGD=vuhFD2MWQXeO5u3q9BObhCiHxO+Aah0afCNBaw@mail.gmail.com>
In-Reply-To: <CAFg4Z=wnoGD=vuhFD2MWQXeO5u3q9BObhCiHxO+Aah0afCNBaw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.254.104]
Content-Type: multipart/signed; boundary="Apple-Mail=_88E10742-EE33-4E6C-B5B0-7F8F2B1ED8AF"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "Jonathan Rosenberg (jdrosen)" <jdrosen@cisco.com>
Subject: Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
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, 30 Oct 2013 18:46:18 -0000
+1 I suppose from a WebRTC platform support perspective, the gods at Apple could easily adopt WebRTC in Safari and deliver their own hardware-accelerated .264 implementation. Developers could surface that in a UIWebView, although I have not noodled what types of additional hooks may be needed. Ultimately this falls into the Apple bucket. On Oct 30, 2013, at 12:42 PM, Steve Sokol <ssokol@digium.com> wrote: > Jonathan and Fluffy, > > In regards to Apple's restriction on the installation of binary modules the prevents iOS from being included in the list of supported platforms: what precludes Cisco from offering a binary static library built for iOS? If it's because the licensing terms you've struck with MPEG LA require you count downloads, could you offer an iOS version that simply does a one-time "phone-home" to cover the count requirement? The phone-home call could be anonymous and unique (hash of MAC or similar). Not necessarily ideal from a privacy perspective, but better than leaving a large, affluent and vocal part of the digital ecosystem out. > > > > On Wed, Oct 30, 2013 at 11:17 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: > > On Oct 30, 2013, at 9:55 AM, Matt Fredrickson <creslin@digium.com> wrote: > > > That is only as long as the binary versions don't have any additions or changes for such things. Nothing says that the binary modules cannot be built in this way. > > The binary module will be build that way. > > All the build scripts etc that Cisco uses will be part of the open source project so that anyone can build it them selves and check that their build matches the Cisco binary and check the code does not have backdoors to send all your video to the NSA. > > > > > > Matthew Fredrickson > > > > > > On Wed, Oct 30, 2013 at 10:52 AM, Ethan Hugg <ethanhugg@gmail.com> wrote: > > > > Lorenzo, > > > > You will be able to inspect the source yourself for nefarious things like tracking as the code will be freely available. > > > > -EH > > > > > > > > On Wed, Oct 30, 2013 at 8:47 AM, Lorenzo Miniero <lorenzo@meetecho.com> wrote: > > Il giorno Wed, 30 Oct 2013 10:41:27 -0500 > > Adam Roach <adam@nostrum.com> ha scritto: > > > > > On 10/30/13 10:20, Matt Fredrickson wrote: > > > > Does this mean that system information (for systems that this is > > > > installed on) may be tracked and sent back to the Cisco servers for > > > > accurate license usage count? (ethernet MAC address, or some other > > > > system specific info) so that redownloads of modules on the same > > > > system are not counted towards your license usage accounting? > > > > > > My understanding is that MPEG-LA has a per-organization royalty cap > > > for H.264 (13 MUSD, if my memory serves), and that Cisco reaches that > > > cap quite easily with their own products. > > > > > > /a > > > > > > Which doesn't preclude the fact the module may do tracking anyway. > > > > Lorenzo > > > > > > > _______________________________________________ > > > 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 > > > > > > _______________________________________________ > > 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 > > > > -- > <digium_RGB_signature.gif> > Steven Sokol > Digium, Inc. · Director of Strategic Programs > 445 Jan Davis Drive NW · Huntsville, AL 35806 · US > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Cisco to open source its H.264 implement… Jonathan Rosenberg (jdrosen)
- Re: [rtcweb] Cisco to open source its H.264 imple… Karl Stahl
- Re: [rtcweb] Cisco to open source its H.264 imple… Leon Geyser
- Re: [rtcweb] Cisco to open source its H.264 imple… Matt Fredrickson
- Re: [rtcweb] Cisco to open source its H.264 imple… Jonathan Rosenberg
- Re: [rtcweb] Cisco to open source its H.264 imple… Peter Thatcher
- Re: [rtcweb] Cisco to open source its H.264 imple… Matt Fredrickson
- Re: [rtcweb] Cisco to open source its H.264 imple… Adam Roach
- Re: [rtcweb] Cisco to open source its H.264 imple… Adam Roach
- Re: [rtcweb] Cisco to open source its H.264 imple… Ted Hardie
- Re: [rtcweb] Cisco to open source its H.264 imple… Lorenzo Miniero
- Re: [rtcweb] Cisco to open source its H.264 imple… Adam Roach
- Re: [rtcweb] Cisco to open source its H.264 imple… Ethan Hugg
- Re: [rtcweb] Cisco to open source its H.264 imple… Monty Montgomery
- Re: [rtcweb] Cisco to open source its H.264 imple… Monty Montgomery
- Re: [rtcweb] Cisco to open source its H.264 imple… Lorenzo Miniero
- Re: [rtcweb] Cisco to open source its H.264 imple… Max Jonas Werner
- Re: [rtcweb] Cisco to open source its H.264 imple… Matt Fredrickson
- Re: [rtcweb] Cisco to open source its H.264 imple… Ted Hardie
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… Jonathan Rosenberg
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… Matt Fredrickson
- Re: [rtcweb] Cisco to open source its H.264 imple… Steve Sokol
- Re: [rtcweb] Cisco to open source its H.264 imple… Leon Geyser
- Re: [rtcweb] Cisco to open source its H.264 imple… Matt Fredrickson
- Re: [rtcweb] Cisco to open source its H.264 imple… Jonathan Rosenberg
- Re: [rtcweb] Cisco to open source its H.264 imple… Adam Roach
- Re: [rtcweb] Cisco to open source its H.264 imple… Jeremy Laurenson (jlaurens)
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… Göran Eriksson AP
- Re: [rtcweb] Cisco to open source its H.264 imple… Jeremy Laurenson (jlaurens)
- Re: [rtcweb] Cisco to open source its H.264 imple… Lorenzo Miniero
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… DRAGE, Keith (Keith)
- Re: [rtcweb] Cisco to open source its H.264 imple… cowwoc
- Re: [rtcweb] Cisco to open source its H.264 imple… Lorenzo Miniero
- Re: [rtcweb] Cisco to open source its H.264 imple… David Singer
- Re: [rtcweb] Cisco to open source its H.264 imple… cowwoc
- Re: [rtcweb] Cisco to open source its H.264 imple… Paul Giralt
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Paul Giralt
- Re: [rtcweb] Cisco to open source its H.264 imple… Leon Geyser
- Re: [rtcweb] Cisco to open source its H.264 imple… Kaiduan Xie
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- Re: [rtcweb] Cisco to open source its H.264 imple… cowwoc
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Roman Shpount
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings (fluffy)
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- [rtcweb] VP8 binary module (Was: Cisco to open so… cowwoc
- Re: [rtcweb] Cisco to open source its H.264 imple… Roman Shpount
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] VP8 binary module (Was: Cisco to ope… Kaiduan Xie
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Roman Shpount
- Re: [rtcweb] Cisco to open source its H.264 imple… Engel Nyst
- Re: [rtcweb] Cisco to open source its H.264 imple… Daniel-Constantin Mierla
- Re: [rtcweb] Cisco to open source its H.264 imple… cowwoc
- Re: [rtcweb] Cisco to open source its H.264 imple… Stephan Wenger
- Re: [rtcweb] VP8 binary module (Was: Cisco to ope… Bjoern Hoehrmann
- Re: [rtcweb] Cisco to open source its H.264 imple… Adam Roach
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] VP8 binary module (Was: Cisco to ope… Justin Uberti
- Re: [rtcweb] Cisco to open source its H.264 imple… Daniel-Constantin Mierla
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… DRAGE, Keith (Keith)
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- Re: [rtcweb] Cisco to open source its H.264 imple… Cullen Jennings
- Re: [rtcweb] Cisco to open source its H.264 imple… Jack Moffitt
- Re: [rtcweb] Cisco to open source its H.264 imple… Engel Nyst
- Re: [rtcweb] Cisco to open source its H.264 imple… Mo Zanaty (mzanaty)
- [rtcweb] H.264 IPR disclosures (or persistent lac… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Basil Mohamed Gohar
- Re: [rtcweb] H.264 IPR disclosures (or persistent… DRAGE, Keith (Keith)
- Re: [rtcweb] Cisco to open source its H.264 imple… Engel Nyst
- Re: [rtcweb] Cisco to open source its H.264 imple… Mo Zanaty (mzanaty)
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Ron
- Re: [rtcweb] Cisco to open source its H.264 imple… Gili
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Mo Zanaty (mzanaty)
- Re: [rtcweb] H.264 IPR disclosures (or persistent… SM
- Re: [rtcweb] Cisco to open source its H.264 imple… Mo Zanaty (mzanaty)
- [rtcweb] H.264's high-low play (Was: H.264 IPR di… cowwoc
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Mo Zanaty (mzanaty)
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Markus.Isomaki
- Re: [rtcweb] H.264 IPR disclosures (or persistent… DRAGE, Keith (Keith)
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Ron
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Lorenzo Miniero
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Ron
- Re: [rtcweb] H.264 IPR disclosures (or persistent… SM
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… bryandonnovan
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… bryandonnovan
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Silvia Pfeiffer
- [rtcweb] Hermetic builds (Re: Cisco to open sourc… Harald Alvestrand
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… cowwoc
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Jeremy Laurenson (jlaurens)
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Basil Mohamed Gohar
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Dave Crocker
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… DRAGE, Keith (Keith)
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Ron
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Basil Mohamed Gohar
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Roman Shpount
- Re: [rtcweb] H.264 IPR disclosures (or persistent… DRAGE, Keith (Keith)
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… cowwoc
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Adam Roach
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… cowwoc
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… cowwoc
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Eric Rescorla
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… cowwoc
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Harald Alvestrand
- Re: [rtcweb] H.264's high-low play (Was: H.264 IP… Harald Alvestrand
- Re: [rtcweb] VP8 binary module (Was: Cisco to ope… Harald Alvestrand
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Bjoern Hoehrmann
- Re: [rtcweb] H.264 IPR disclosures (or persistent… Harald Alvestrand
- Re: [rtcweb] Hermetic builds (Re: Cisco to open s… Bjoern Hoehrmann
- [rtcweb] Is there room for a compromise? John Leslie
- Re: [rtcweb] Hermetic builds (Re: Cisco to open s… Ron
- Re: [rtcweb] Is there room for a compromise? cowwoc
- Re: [rtcweb] Hermetic builds (Re: Cisco to open s… Randell Jesup
- Re: [rtcweb] Is there room for a compromise? John Leslie
- Re: [rtcweb] Is there room for a compromise? cowwoc
- Re: [rtcweb] Is there room for a compromise? what… David Singer
- Re: [rtcweb] Is there room for a compromise? what… cowwoc
- Re: [rtcweb] Is there room for a compromise? Ron
- Re: [rtcweb] Is there room for a compromise? what… Justin Uberti
- Re: [rtcweb] Is there room for a compromise? what… Dave Crocker
- Re: [rtcweb] Is there room for a compromise? Matthew Kaufman (SKYPE)
- Re: [rtcweb] Is there room for a compromise? Ron
- Re: [rtcweb] Is there room for a compromise? cowwoc
- Re: [rtcweb] Is there room for a compromise? Matthew Kaufman (SKYPE)
- Re: [rtcweb] Is there room for a compromise? Jack Moffitt
- Re: [rtcweb] Is there room for a compromise? John Leslie
- Re: [rtcweb] Is there room for a compromise? what… Bernard Aboba
- Re: [rtcweb] Is there room for a compromise? what… Ron
- Re: [rtcweb] Interoperability - what have we lear… Bernard Aboba
- Re: [rtcweb] Interoperability - what have we lear… Ron
- Re: [rtcweb] Is there room for a compromise? what… Martin Thomson
- Re: [rtcweb] Is there room for a compromise? what… Justin Uberti
- Re: [rtcweb] Is there room for a compromise? what… Eric Rescorla
- Re: [rtcweb] Interoperability - what have we lear… Bernard Aboba
- Re: [rtcweb] Interoperability - what have we lear… Colin Perkins
- Re: [rtcweb] Is there room for a compromise? what… Dave Crocker
- Re: [rtcweb] Is there room for a compromise? what… Eric Rescorla
- Re: [rtcweb] Is there room for a compromise? what… Dave Crocker
- Re: [rtcweb] Is there room for a compromise? what… Bjoern Hoehrmann
- Re: [rtcweb] Is there room for a compromise? what… Eric Rescorla
- Re: [rtcweb] Is there room for a compromise? what… Ron
- Re: [rtcweb] Is there room for a compromise? what… Bjoern Hoehrmann
- Re: [rtcweb] Is there room for a compromise? what… Eric Rescorla
- Re: [rtcweb] Is there room for a compromise? what… Dave Crocker
- Re: [rtcweb] Is there room for a compromise? what… Ron
- Re: [rtcweb] Is there room for a compromise? what… Richard Shockey
- Re: [rtcweb] Interoperability - what have we lear… Bernard Aboba
- Re: [rtcweb] Is there room for a compromise? what… tim panton
- Re: [rtcweb] Is there room for a compromise? what… Martin Thomson