Re: [rtcweb] Proposal for H.263 baseline codec
Lorenzo Miniero <lorenzo@meetecho.com> Thu, 29 March 2012 12:29 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 EE07821F8A62 for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 05:29:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id weN29LeRh2ok for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 05:29:36 -0700 (PDT)
Received: from smtplq04.aruba.it (smtplqs-out26.aruba.it [62.149.158.66]) by ietfa.amsl.com (Postfix) with SMTP id B5FAF21F89F4 for <rtcweb@ietf.org>; Thu, 29 Mar 2012 05:29:35 -0700 (PDT)
Received: (qmail 31025 invoked by uid 89); 29 Mar 2012 12:29:32 -0000
Received: from unknown (HELO smtp4.aruba.it) (62.149.158.224) by smtplq04.aruba.it with SMTP; 29 Mar 2012 12:29:32 -0000
Received: (qmail 32265 invoked by uid 89); 29 Mar 2012 12:29:32 -0000
Received: from unknown (HELO lminiero-acer) (lorenzo@meetecho.com@130.129.23.208) by smtp4.ad.aruba.it with SMTP; 29 Mar 2012 12:29:32 -0000
Date: Thu, 29 Mar 2012 14:29:28 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Dean Willis <dean.willis@softarmor.com>
Message-ID: <20120329142928.4c21fee2@lminiero-acer>
In-Reply-To: <CAOHm=4snSTbVKpGvuktC+wMYKBu1hvBkwippAQKbA9H1KdFo6w@mail.gmail.com>
References: <CAOHm=4snSTbVKpGvuktC+wMYKBu1hvBkwippAQKbA9H1KdFo6w@mail.gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp4.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Proposal for H.263 baseline codec
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: Thu, 29 Mar 2012 12:29:37 -0000
+1 Lorenzo Il giorno Thu, 29 Mar 2012 14:15:35 +0200 Dean Willis <dean.willis@softarmor.com> ha scritto: > In today's meeting I made a plea for a mandatory baseline codec that > is approachable to the small developer without the cost and IPR risks > of either H.264 or VP8. > > I believe that some sort of baseline codec is required to jump start > the protocol. It's OK if this isn't the best possible codec. Market > forces will assure that commercial implementations converge on a > higher quality when the market requires it. > > While I proposed today that H.261 could serve as a baseline, we know > this would be "extremely basic". In other words, it might not pass > the "good enough to use" test required for a successful launch. > > Stephane and several others suggested H.263 as an alternative during > the after-meeting chat. While it is not as IPR-safe a choice as > H.261, it is relatively mature and the known challenges have > generally failed. Implementations are reasonably available and should > make it possible for smaller implementers, students, and hobbyists to > play ball. It's not all that network efficient and is outright piggy > at higher resolutions, but it probably works "well enough to use." > > So I propose we set H.263 as the baseline ( I expect a bit of > profiling may be necessary to further qualify the baseline) and run > with that for now. If the situation changes, we can always replace it > before final publication. -- > Dean -- Lorenzo Miniero, COB Meetecho s.r.l. Web Conferencing and Collaboration Tools http://www.meetecho.com
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- [rtcweb] Proposal for H.263 baseline codec Dean Willis
- Re: [rtcweb] Proposal for H.263 baseline codec Lorenzo Miniero
- Re: [rtcweb] Proposal for H.263 baseline codec Markus.Isomaki
- Re: [rtcweb] Proposal for H.263 baseline codec Bernard Aboba
- Re: [rtcweb] Proposal for H.263 baseline codec Piers O'Hanlon
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Silvia Pfeiffer
- Re: [rtcweb] Proposal for H.263 baseline codec Paul E. Jones
- Re: [rtcweb] Proposal for H.263 baseline codec Silvia Pfeiffer
- Re: [rtcweb] Proposal for H.263 baseline codec Paul E. Jones
- Re: [rtcweb] Proposal for H.263 baseline codec Marshall Eubanks
- Re: [rtcweb] Proposal for H.263 baseline codec Randell Jesup
- Re: [rtcweb] Proposal for H.263 baseline codec Gregory Maxwell
- Re: [rtcweb] Proposal for H.263 baseline codec Marshall Eubanks
- Re: [rtcweb] Proposal for H.263 baseline codec Randell Jesup
- Re: [rtcweb] Proposal for H.263 baseline codec Dean Willis
- Re: [rtcweb] Proposal for H.263 baseline codec Kevin P. Fleming
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Harald Alvestrand
- Re: [rtcweb] Proposal for H.263 baseline codec Kevin P. Fleming
- Re: [rtcweb] Proposal for H.263 baseline codec David Benham (dbenham)