Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
Peter Thatcher <pthatcher@google.com> Wed, 30 October 2013 15:15 UTC
Return-Path: <pthatcher@google.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 3904921E80FC for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 08:15:57 -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_57=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 kUUNp6wGznSk for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 08:15:56 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id CD90411E8296 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 08:14:39 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ld10so1078082pab.38 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 08:14:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LPq9eJXjMAN/7MR4lmp9lY/jKxSTA4iBYEC6VlUbE3A=; b=cGS4+ok2L+CfTi++rA798QrR1/5sAaMxm9lOJHc8ypsGapp9TPGitxjmOOA2yw/Zk7 oW8XczdUc/gFhd4JI0EMd+fjMm5/8qso/FQz9bIFanQPuE35K2qqtLF5vvJy8ji7Qptk 1gVRDcrE5K/nC3PhNL9YECrbiZZREeS1J+yt0cgjm+ZxeFxLaXULyBA67YreQyQ6AbBN iULRLeR9CdIESHsnqOvfbrIXN1sTePUq/sCOD21BWCnkffQ9pPmu9OOIi5aaU2A5hLBX 59/pqHTbGiskfoxCerXAg97PXz6NInI8XlcxkClgzt8UJVQhDqtRnUgw1vcvZnb8Irvs vEMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LPq9eJXjMAN/7MR4lmp9lY/jKxSTA4iBYEC6VlUbE3A=; b=W1I8S/BRwESt/cT56dKNQQmb5BqQjHNc/okXm5tjkPm8b9K8G3hxzY8f6KXILcOBHS ex6fa+d2ce/qetZsq6E1nsXTFyCTYthVX1iF9nOnLRFuG6nXNwSA8/iq7iDKD9iSv941 fH5MiRJiqqHqd+QRAEpANwu5pes6aH/8iSUxBx4Co0AApQ+OMhcHx5gtvnhqpGWQSIP+ 6NT7H0eCHdWjPOsMxcsrp56KCNZ96H4fL+SWsbwfeVf7IsfbpSEmAlu1rNwRmfcXestN A8Jiavg2AOPIhkUTbprAGC5xYUgbXmsIpagXOlCcVmWUhsnF/qsj0QHblR079cNiq54h TlHQ==
X-Gm-Message-State: ALoCoQmcsCy1POTpCb+4pANjw2Dg9KQEEImLvk+Lfxwzg2gg5FWkXVEGQ8538MlqvsPATgUSgWn3sKijAnJceeqKGfOrlBOgHVDKyQTvfuSwEEpk4M0O7/oOM683p3ZfHk63RAt4pRexVUErzJGqK9J4MeBEPXX4eekahClj/TMql87zBspG8ogOcfMPLHeM4CGc1rkPg5R8
X-Received: by 10.68.101.225 with SMTP id fj1mr5817365pbb.8.1383146078537; Wed, 30 Oct 2013 08:14:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.163.234 with HTTP; Wed, 30 Oct 2013 08:13:56 -0700 (PDT)
In-Reply-To: <CA+23+fHdKBwezhtsES1w_qDJgvVC=ChaBcaF1x0_N65aKv-9yQ@mail.gmail.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>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 30 Oct 2013 08:13:56 -0700
Message-ID: <CAJrXDUF78kg++03jduVxvFVG2wz35_sNPkRjzGTaJCYv3o+UMQ@mail.gmail.com>
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
Content-Type: multipart/alternative; boundary="047d7b673288af40c904e9f6ca97"
Cc: "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 15:15:57 -0000
On Wed, Oct 30, 2013 at 7:08 AM, Jonathan Rosenberg <jdrosen@jdrosen.net>wrote: > One of the reasons we're open sourcing it is so that interested parties > could build the module for other platforms. So, yes. If the platform allows > for fetch+install the community can build for that and Cisco will not pass > on any MPEG-LA licensing costs for applications on that platform. > You keep using the phrase "Cisco will not pass on any MPEG-LA licensing costs for applications" in a careful way, which I'm sure you have to for legal reasons, but it does leave some of us wondering what it really means. As a specific example, what about a Linux distribution? I think it's clear that Debian, for example, cannot make this source code part of their distribution because of the patent implications. Are you suggesting that a linux distribution could take the Cisco source code, compile their own binary module, and host it on Cisco servers as a way to distribute h264 functionality that avoids the need to pay the MPEG-LA? You seem to be implying that, but not outright saying it. I believe neither WinRT nor Winphone 7/8 allow for apps to fetch/install so > that the fetch+install model won't work there. > > > On Wed, Oct 30, 2013 at 9:43 AM, Leon Geyser <lgeyser@gmail.com> wrote: > >> Great news. >> >> I see this in the Q/A: >> *Q. iOS is noticeably absent from the list of platforms. Why is that?* >> A: Unfortunately, iOS does not allow for applications to fetch and >> install modules from the Internet once that application has been installed >> on the device. Consequently, it is simply not feasible for us to provide a >> distribution at this time. >> -- >> Does the same apply to other platforms like Windows Phone 7/8, Windows RT? >> Also if we want to use the module on a different platform not listed by >> you and that allow fetch+install can we ask for the module to be compiled? >> >> >> On 30 October 2013 15:20, Karl Stahl <karl.stahl@intertex.se> wrote: >> >>> Thanks for this surprise! **** >>> >>> ** ** >>> >>> Hope that it will result in that we can keep codecs in the endpoints and >>> can avoid video transcoding in gateways.**** >>> >>> ** ** >>> >>> /Karl**** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> *Från:* rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] *För *Jonathan >>> Rosenberg (jdrosen) >>> >>> *Skickat:* den 30 oktober 2013 13:29 >>> *Till:* rtcweb@ietf.org >>> *Ämne:* [rtcweb] Cisco to open source its H.264 implementation and >>> absorb MPEG-LA licensing fees**** >>> >>> ** ** >>> >>> I’d like to make an announcement material to the conversations around >>> MTI video codecs in rtcweb.**** >>> >>> ** ** >>> >>> Cisco is announcing today that we will take our H.264 implementation, >>> and open source it under BSD license terms. Development and maintenance >>> will be overseen by a board from industry and the open source community. >>> Furthermore, we will provide a binary form suitable for inclusion in >>> applications across a number of different operating systems (Windows, >>> MacOS, Linux x86, Linux ARM and Android ARM), and make this binary module >>> available for download from the Internet. We will not pass on our MPEG-LA >>> licensing costs for this module, and based on the current licensing >>> environment, this will effectively make H.264 free for use on supported >>> platforms. **** >>> >>> ** ** >>> >>> We believe that this contribution to the community can help address the >>> concerns many have raised around selection of H.264 as MTI. I firmly >>> believe that with H.264 we can achieve maximal interoperability and now, do >>> it with open source and for free (well, at least for others – its not free >>> for Cisco J)**** >>> >>> More information on the open source project can be found at >>> http://www.openh264.org, which is sparse now but more coming soon.**** >>> >>> ** ** >>> >>> ** ** >>> >>> Thx,**** >>> >>> Jonathan R.**** >>> >>> ** ** >>> >>> --**** >>> >>> Jonathan Rosenberg, PhD**** >>> >>> VP, CTO Collaboration**** >>> >>> Cisco Systems**** >>> >>> jdrosen@cisco.com**** >>> >>> ** ** >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Jonathan Rosenberg, Ph.D. > jdrosen@jdrosen.net > http://www.jdrosen.net > > _______________________________________________ > 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