Re: [rtcweb] On the topic of MTI video codecs
Simon Perreault <simon.perreault@viagenie.ca> Fri, 01 November 2013 13:10 UTC
Return-Path: <simon.perreault@viagenie.ca>
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 C38AD21E84EF for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 06:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 7BCr4huImegL for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 06:10:53 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D2FE821E8450 for <rtcweb@ietf.org>; Fri, 1 Nov 2013 06:06:16 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:2001::1000]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2BBDC403AB for <rtcweb@ietf.org>; Fri, 1 Nov 2013 09:06:15 -0400 (EDT)
Message-ID: <5273A746.4060504@viagenie.ca>
Date: Fri, 01 Nov 2013 09:06:14 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <527147FF.5010506@nostrum.com> <C72DB04F-F363-45A9-A51F-31900037C239@vipadia.com> <C81F0BD3-F5E6-4E1A-955D-16D55E698BD1@edvina.net> <5272C6C8.3070006@gmail.com> <CABcZeBM6T0a9iLHVujzAiwFi5X5=S0oNK=xR3=FkHM2wi5bngQ@mail.gmail.com> <CAL02cgTwJwf27PuxGhhZAZgDN2jguxhNFBNPeJC4W1dwd5jzYA@mail.gmail.com>
In-Reply-To: <CAL02cgTwJwf27PuxGhhZAZgDN2jguxhNFBNPeJC4W1dwd5jzYA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] On the topic of MTI video codecs
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, 01 Nov 2013 13:10:53 -0000
Le 2013-10-31 18:36, Richard Barnes a écrit : > You would need something more than that if you don't trust Cisco not to > tinker with the binaries (no offense). But even that doesn't have to be > complicated. You could just do something like have the software call > back to the vendor whenever it gets a new binary from Cisco to check > that the binary it just got is good (say, by comparing hashes). Is it even necessary that Cisco do the actual compiling of source code? As far as I understand, Cisco only needs to be distributing the binaries. So here's a crazy idea... how about a self-serve binary hosting service? You compile your code, upload it to Cisco, Cisco does the download tracking and accounting, and you and your users just need to download and verify the checksum. Heck, Cisco could even host binaries of x264! That would be much simpler on Cisco's part: much less investment in manpower, much fewer things to maintain and care for. It would just be a glorified FTP server. Unlicensed binary comes in, licensed binary comes out. Platforms could multiply without any effort from Cisco. Win win. Simon -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca
- Re: [rtcweb] On the topic of MTI video codecs Daniel-Constantin Mierla
- Re: [rtcweb] On the topic of MTI video codecs Leon Geyser
- [rtcweb] On the topic of MTI video codecs Adam Roach
- Re: [rtcweb] On the topic of MTI video codecs Leon Geyser
- Re: [rtcweb] On the topic of MTI video codecs Jeremy Laurenson (jlaurens)
- Re: [rtcweb] On the topic of MTI video codecs Adam Roach
- Re: [rtcweb] On the topic of MTI video codecs Jeremy Laurenson (jlaurens)
- Re: [rtcweb] On the topic of MTI video codecs Jeremy Laurenson (jlaurens)
- Re: [rtcweb] On the topic of MTI video codecs Adam Roach
- Re: [rtcweb] On the topic of MTI video codecs Peter Saint-Andre
- Re: [rtcweb] On the topic of MTI video codecs Cullen Jennings (fluffy)
- Re: [rtcweb] On the topic of MTI video codecs Jean-Marc Valin
- Re: [rtcweb] On the topic of MTI video codecs Daniel-Constantin Mierla
- Re: [rtcweb] On the topic of MTI video codecs Olle E. Johansson
- Re: [rtcweb] On the topic of MTI video codecs Silvia Pfeiffer
- Re: [rtcweb] On the topic of MTI video codecs Cullen Jennings (fluffy)
- Re: [rtcweb] On the topic of MTI video codecs Lorenzo Miniero
- Re: [rtcweb] On the topic of MTI video codecs Neil Stratford
- Re: [rtcweb] On the topic of MTI video codecs Olle E. Johansson
- Re: [rtcweb] On the topic of MTI video codecs Eric Rescorla
- Re: [rtcweb] On the topic of MTI video codecs Daniel-Constantin Mierla
- Re: [rtcweb] On the topic of MTI video codecs Eric Rescorla
- Re: [rtcweb] On the topic of MTI video codecs Richard Barnes
- Re: [rtcweb] On the topic of MTI video codecs Eric Rescorla
- Re: [rtcweb] On the topic of MTI video codecs cowwoc
- Re: [rtcweb] On the topic of MTI video codecs Olle E. Johansson
- Re: [rtcweb] On the topic of MTI video codecs Daniel-Constantin Mierla
- Re: [rtcweb] On the topic of MTI video codecs Olle E. Johansson
- Re: [rtcweb] On the topic of MTI video codecs Simon Perreault
- Re: [rtcweb] On the topic of MTI video codecs DRAGE, Keith (Keith)
- Re: [rtcweb] On the topic of MTI video codecs Emil Ivov
- Re: [rtcweb] On the topic of MTI video codecs Chris Wendt
- Re: [rtcweb] On the topic of MTI video codecs Emil Ivov
- Re: [rtcweb] On the topic of MTI video codecs Cullen Jennings