Re: [rtcweb] Alternative decision process in RTCWeb
cowwoc <cowwoc@bbs.darktech.org> Tue, 03 December 2013 02:46 UTC
Return-Path: <cowwoc@bbs.darktech.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721F61AE027 for <rtcweb@ietfa.amsl.com>; Mon, 2 Dec 2013 18:46:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RV8htp8Ni2xo for <rtcweb@ietfa.amsl.com>; Mon, 2 Dec 2013 18:46:53 -0800 (PST)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by ietfa.amsl.com (Postfix) with ESMTP id 431C91AE026 for <rtcweb@ietf.org>; Mon, 2 Dec 2013 18:46:53 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id lx4so22234668iec.23 for <rtcweb@ietf.org>; Mon, 02 Dec 2013 18:46:50 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=cGApMNI5BNjl7rpv9IsK/lAvRktBq1HGN9byHIIS/eM=; b=HnYrlpNaWEkQfj7cNAHR0sxaomInhwcT7P1U2iemiSUmS2eL0Ypdgxe4gOZGXouPnj 7pJxJFSKcgBawfdgNoPQx93nglWKYKxnjlz7Jeu6NO9fkMKOp0LmtXX8ZGaT1pJYbxdg IJ6cykfxUNSIfMSPWafaCHrVlTxuDKyVAM3kl+sb8Ktn21Jn8zBNAQ2nKftqLpwfNHBu t1Id7aBYBxQEO88vjnLJPYkdIdt5Zby4WYbUgINK/LWQ0JjirwxskSiosiynItyuVzZY 75J3Jrodm8CKrNi/5+qkz8FX3ud3FrYUimgdmVjPbeeorK6OGf1AemAM5GHivZWvuiip yLCw==
X-Gm-Message-State: ALoCoQkhAHHq7W6NSA3qFIzZ3VeyFzK4RMKVUIyr5jaisp4NCkUhZ2w4pUOQzQsaDyoTGhrI0/WS
X-Received: by 10.42.224.10 with SMTP id im10mr4509217icb.46.1386038810595; Mon, 02 Dec 2013 18:46:50 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id i11sm797829igh.0.2013.12.02.18.46.48 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 18:46:49 -0800 (PST)
Message-ID: <529D4617.6060909@bbs.darktech.org>
Date: Mon, 02 Dec 2013 21:46:47 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <DUB127-W23531D0E8B15570331DB51E0EE0@phx.gbl> <52974AA8.6080702@cisco.com> <1F79045E-8CD0-4C5D-9090-3E82853E62E9@nominum.com> <52976F56.4020706@dcrocker.net> <3CD78695-47AD-4CDF-B486-3949FFDC107B@nominum.com> <5006.1385666853@sandelman.ca> <D4D5920A-E041-42E8-BB1C-1CB24FBEE3F4@nominum.com> <BLU169-W1176AB7AECF0757C380A70E93EE0@phx.gbl> <20131129060936.GV3245@audi.shelbyville.oz> <6mkp9912042i9gkg87fc3ji8g9tkv6uqrh@hive.bjoern.hoehrmann.de> <529CEAA6.9000501@librevideo.org> <e5bq99dg3h6e82mnsn6k21aunc9eqlvc7q@hive.bjoern.hoehrmann.de>
In-Reply-To: <e5bq99dg3h6e82mnsn6k21aunc9eqlvc7q@hive.bjoern.hoehrmann.de>
Content-Type: multipart/alternative; boundary="------------030306040008090406060407"
Subject: Re: [rtcweb] Alternative decision process in RTCWeb
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 03 Dec 2013 02:46:55 -0000
On 02/12/2013 9:00 PM, Bjoern Hoehrmann wrote: > I think it is highly relevant whether the mandatory-to-implement codec > supports two people in typical German households communicate via video > in sign language, and how it does so relative to non-mandatory > options, as a simple example. If H.264 supports the scenario and H.261 > does not, then selecting H.261 does not in fact prevent the absolute > worst case and does not ensure that communication via video can always > happen. Bjoern, I'd like to point you to http://www.netindex.com/upload/allcountries/ for two reasons: 1. It states that Germany has an average upload rate of 3.13Mbps. 2. It shows that upload speeds are increasing over time. >> The fight against H.261 as MTI is really not about quality or >> efficiency, but rather, about forcing a royalty-bearing format on what >> should be an open standard and to save a few big players some >> implementation dollars because they might want to reuse some existing >> hardware, all of which are secondary points in this charter compared to >> a universally applicable MTI video codec. > Like I said, I have not seen a convincing argument that H.261 performs > well enough, and the implementation techniques that can reasonably be > assumed to be unencumbered are old enough that I think it is fair to > assume without investigating myself that selecting H.261 as only manda- > tory-to-implement video codec could work on paper, but not in practise. > > I read the "irrelevant" responses as essentially advocating that we may > just as well make sending raw and unencoded RGB data the MTI codec. I'm > more than willing to hear better arguments. The same goes for the H.263 > option that has been suggested. H.261 is meant as a fallback only in the case that the market cannot agree to upgrade to VP8 or H.264 at runtime. If a sizable portion of the market cannot agree at runtime, what makes you believe that that same sizable portion can agree on a MTI codec? And a final question, in case you disagree with everything I've written so far: How do you advocate we proceed in light of the fact that we already tried to (and failed) to reach consensus around VP8 and H.264? Gili
- Re: [rtcweb] Alternative decision process in RTCW… Ted Lemon
- Re: [rtcweb] Alternative decision process in RTCW… Ted Lemon
- Re: [rtcweb] Alternative decision process in RTCW… cowwoc
- Re: [rtcweb] Alternative decision process in RTCW… Dave Crocker
- Re: [rtcweb] Alternative decision process in RTCW… Eliot Lear
- Re: [rtcweb] Alternative decision process in RTCW… Ted Lemon
- Re: [rtcweb] Alternative decision process in RTCW… Bernard Aboba
- Re: [rtcweb] Alternative decision process in RTCW… DRAGE, Keith (Keith)
- Re: [rtcweb] Alternative decision process in RTCW… Ted Lemon
- Re: [rtcweb] Alternative decision process in RTCW… Ron
- Re: [rtcweb] Alternative decision process in RTCW… Michael Richardson
- Re: [rtcweb] Alternative decision process in RTCW… Maik Merten
- Re: [rtcweb] Alternative decision process in RTCW… Roger Jørgensen
- Re: [rtcweb] Alternative decision process in RTCW… Roberto Peon
- Re: [rtcweb] Alternative decision process in RTCW… cowwoc
- Re: [rtcweb] Alternative decision process in RTCW… Leon Geyser
- Re: [rtcweb] Alternative decision process in RTCW… Basil Mohamed Gohar
- Re: [rtcweb] Alternative decision process in RTCW… Mary Barnes
- Re: [rtcweb] Alternative decision process in RTCW… Bjoern Hoehrmann
- Re: [rtcweb] Alternative decision process in RTCW… Basil Mohamed Gohar
- Re: [rtcweb] Alternative decision process in RTCW… Bjoern Hoehrmann
- Re: [rtcweb] Alternative decision process in RTCW… Martin Thomson
- Re: [rtcweb] Alternative decision process in RTCW… Silvia Pfeiffer
- Re: [rtcweb] Alternative decision process in RTCW… Bjoern Hoehrmann
- Re: [rtcweb] Alternative decision process in RTCW… Stephan Wenger
- Re: [rtcweb] Alternative decision process in RTCW… Bernard Aboba
- Re: [rtcweb] Alternative decision process in RTCW… cowwoc
- Re: [rtcweb] Alternative decision process in RTCW… Basil Mohamed Gohar
- Re: [rtcweb] Alternative decision process in RTCW… Bjoern Hoehrmann
- Re: [rtcweb] Alternative decision process in RTCW… Max Jonas Werner
- Re: [rtcweb] Alternative decision process in RTCW… John Leslie
- Re: [rtcweb] Alternative decision process in RTCW… cowwoc
- Re: [rtcweb] Alternative decision process in RTCW… cowwoc
- Re: [rtcweb] Alternative decision process in RTCW… Dave Crocker
- Re: [rtcweb] Alternative decision process in RTCW… Phillip Hallam-Baker
- Re: [rtcweb] Alternative decision process in RTCW… Sam Hartman
- Re: [rtcweb] Alternative decision process in RTCW… Richard Shockey
- Re: [rtcweb] Alternative decision process in RTCW… David Singer
- Re: [rtcweb] Alternative decision process in RTCW… Maik Merten
- Re: [rtcweb] Alternative decision process in RTCW… Harald Alvestrand
- Re: [rtcweb] Alternative decision process in RTCW… Silvia Pfeiffer
- Re: [rtcweb] Alternative decision process in RTCW… Randell Jesup