Re: [rtcweb] Form of the video codec question

Lorenzo Miniero <lorenzo@meetecho.com> Wed, 31 October 2012 06:56 UTC

Return-Path: <lorenzo@meetecho.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 D9C5621F8654 for <rtcweb@ietfa.amsl.com>; Tue, 30 Oct 2012 23:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VWEwLz9lwdf for <rtcweb@ietfa.amsl.com>; Tue, 30 Oct 2012 23:56:32 -0700 (PDT)
Received: from smtpdg3.aruba.it (smtpdg3.aruba.it [62.149.158.233]) by ietfa.amsl.com (Postfix) with ESMTP id BB0BF21F8540 for <rtcweb@ietf.org>; Tue, 30 Oct 2012 23:56:31 -0700 (PDT)
Received: from rainpc ([79.49.159.202]) by smtpcmd01.ad.aruba.it with bizsmtp id HiwT1k00A4NJ6Ef01iwTtB; Wed, 31 Oct 2012 07:56:29 +0100
Date: Wed, 31 Oct 2012 07:56:26 +0100
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Roni Even <ron.even.tlv@gmail.com>
Message-ID: <20121031075626.6fbf6ea4@rainpc>
In-Reply-To: <01c301cdb732$0fac72a0$2f0557e0$@gmail.com>
References: <CA+9kkMCQBw27XwvZ=hARs1DyyQufY2H7R4FwYq-3P-Tp7T7W+w@mail.gmail.com> <20121029210443.GB68232@verdi> <509055C4.6060500@nostrum.com> <01c301cdb732$0fac72a0$2f0557e0$@gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Form of the video codec question
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, 31 Oct 2012 06:56:33 -0000

On Wed, 31 Oct 2012 08:36:26 +0200
"Roni Even" <ron.even.tlv@gmail.com> wrote:

> Hi,
> Just to be precise, if we do not chose a common video codec the
> interoperability point will be an audio call
> Roni
> 


Not if we pick an "older" video codec as a MTI one as we did for G.711 (well maybe not *that* old).

L.


> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of
> Adam Roach
> Sent: 31 October, 2012 12:34 AM
> To: John Leslie
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Form of the video codec question
> 
> On 10/29/12 16:04, Oct 29, John Leslie wrote:
> >     I view both being MTI as somewhat reasonable, and neither being 
> > MTI as a likely best-choice
> 
> That's an interesting set of assertions. I, for one, cannot see how you
> reached either conclusion.
> 
> Selecting "both" solves none of the problems that have been raised to date.
> It takes on the entire union of disadvantages that have been raised about
> the candidate codecs, while providing the benefits of neither.
> 
> Selecting "neither" is intentionally aiming the ship for the rocks: we
> guarantee failure. If we publish a specification to which two
> implementations can comply but cannot subsequently inter-operate, then the
> entire point of standardization is defeated.
> 
> /a
> _______________________________________________
> 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


-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com