Re: [rtcweb] Proposed Video Selection Process

Maik Merten <maikmerten@googlemail.com> Thu, 21 November 2013 21:07 UTC

Return-Path: <maikmerten@googlemail.com>
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 BDB251AE27F for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 13:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Gm-Zf_2HUh5u for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 13:07:16 -0800 (PST)
Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7780F1AE092 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 13:07:16 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id q10so126459ead.17 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 13:07:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=125aR1hkRucme0YGA+WOCtC4VBapPBFBDx58iHUL/qs=; b=LaPUZvuMNXTzcNNrvf5H4lYQZdSfgZb4W2BNZP2V8d2aKhVTD94jrCRM4uJF3leaCb LDvTO1gA+aQABDp3RIKOQJbBJaONx11WJNvBYgySRWp26n4ZHLy/q5QIWfDX0P2bM/ME fZSTCFCEZ0PMWwzE7y2M/Qd0DRn1m8Gq43EGn+zDs8y6R6eD0MvcvFKqKMIY+jyY5OK2 cTKDkIy3HJkqTpQcN+Ou0J4AMwBDetBXjeaH+vMQuu6U4gdJX6aC7Baw43qqsRcytLcB ea1zNw88hDoAfjRv8hSa63YxrCvvTFCVG/jW+LYZ0kyvlwbimw4q2UGm90+Nmm9VE/o2 8RMA==
X-Received: by 10.14.0.72 with SMTP id 48mr33830eea.50.1385068029235; Thu, 21 Nov 2013 13:07:09 -0800 (PST)
Received: from [192.168.2.101] (dslb-188-101-189-061.pools.arcor-ip.net. [188.101.189.61]) by mx.google.com with ESMTPSA id x4sm73712389eef.1.2013.11.21.13.07.07 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Nov 2013 13:07:08 -0800 (PST)
Message-ID: <528E75FA.4000101@googlemail.com>
Date: Thu, 21 Nov 2013 22:07:06 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <528E39F4.4010706@ericsson.com> <CAEqTk6RrHSzgJ9QA_spJQWN+6SaRWwwq6H4cwBxNbTHXnHmhYA@mail.gmail.com> <8647A71C-CDCF-4897-96D6-4CD1C6566BE6@cisco.com> <CAOJ7v-1kdXreZbF0Q7=DinObV5=eWcdfFuwrJ13BQ0Hk=Fec-Q@mail.gmail.com> <528E5B47.70702@nostrum.com> <20131121204147.GV3245@audi.shelbyville.oz> <528E71AC.4040202@librevideo.org> <CABkgnnUKPMTpMqX6G5=kDQomG9wgqZeTomOnjGecTFZ7T3GjfQ@mail.gmail.com>
In-Reply-To: <CABkgnnUKPMTpMqX6G5=kDQomG9wgqZeTomOnjGecTFZ7T3GjfQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposed Video Selection Process
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: Thu, 21 Nov 2013 21:07:17 -0000

Am 21.11.2013 21:52, schrieb Martin Thomson:
> And I find the argument raised quite compelling.  It's hard to justify
> spending valuable time and resources on implementing something that
> crappy.

The justification would be "to enable P2P video interoperability, at 
least on a basic level". Interoperability apparently sometimes (often? 
always?) comes at a price.

However, I'm completely with you: It *is* (very!) unfortunate that IPR 
concerns seem to block anything but technologically vastly outdated formats.


Maik