Re: [rtcweb] Alternative decision process in RTCWeb
Maik Merten <maikmerten@googlemail.com> Wed, 04 December 2013 09:21 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 75F3C1ADFD0 for <rtcweb@ietfa.amsl.com>; Wed, 4 Dec 2013 01:21:18 -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 EcP9Q-ij1u1b for <rtcweb@ietfa.amsl.com>; Wed, 4 Dec 2013 01:21:17 -0800 (PST)
Received: from mail-bk0-x22e.google.com (mail-bk0-x22e.google.com [IPv6:2a00:1450:4008:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 170E91AE218 for <rtcweb@ietf.org>; Wed, 4 Dec 2013 01:21:06 -0800 (PST)
Received: by mail-bk0-f46.google.com with SMTP id u15so6380657bkz.5 for <rtcweb@ietf.org>; Wed, 04 Dec 2013 01:21:03 -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=3/voxlAyBZmd8L13XP9mghKciQ0g9nYWJTG/WwFyx60=; b=jfM+KjkVn4SruSde/9b+NPr1nJ5Udhx/RSpk7Y3NCPyk6e0kgXWhysOtzifiTFTiTd OarC+nlEgk4f9bEBW7IlJ380yxVogdK3B4xM0sVLilTnhjV/qFWwcLiZ3ihhH+37Zoct u+kGxG+YOCUL9VaXRmIrU83vcxdVVvSzcr3ng6Xz1cEJtqAdjFgs1TI9Mpz1zm4POsiV wBe6SnizLZ+tDasjLW0jp2q0+ledEZG20bDhYqbZfMqey5Bk9wGb9qfzrgy2wlXJ1HIw QGRigEFoX033yjRKvidTCfxeDLR1FGqJjdrMPxEq1GfFYpJJo40NcSSHxxhgXHqGgswN aX5Q==
X-Received: by 10.204.107.8 with SMTP id z8mr79653bko.126.1386148863297; Wed, 04 Dec 2013 01:21:03 -0800 (PST)
Received: from [0.0.0.0] (v2201202116457532.yourvserver.net. [46.38.243.75]) by mx.google.com with ESMTPSA id tb8sm549441bkb.10.2013.12.04.01.21.01 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Dec 2013 01:21:01 -0800 (PST)
Message-ID: <529EF456.3040706@googlemail.com>
Date: Wed, 04 Dec 2013 10:22:30 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <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> <CAMm+LwhUB+Ppj8QXNA+=2thi0ZTgymc1G7=XH9jd+agEEAvwHA@mail.gmail.com> <242q99176qj0e4t7as5lu3e7rosd8grn1v@hive.bjoern.hoehrmann.de> <CEC277EC.AB897%stewe@stewe.org> <65ECB9F5-49F1-492A-A5DC-A4EE02C37092@apple.com>
In-Reply-To: <65ECB9F5-49F1-492A-A5DC-A4EE02C37092@apple.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
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: Wed, 04 Dec 2013 09:21:18 -0000
Am 04.12.2013 02:25, schrieb David Singer: > Nonetheless, I still think H.263 deserves a more careful look. I know Stephan is negative, but so far, he’s the only one. For those who DON’T currently implement H.263, could/would you? Quite clearly H.263 is not yet in the "so old it's as safe as it can get" realm, and the MPEG-4 visual patent pool lists numerous patents tagged as "H.263". Of course, this does not necessarily mean that these patents read on the proposed H.263 baseline, but this is certainly difficult to assess without legal consultation. An interesting, if not conclusive, data point would be if those who deploy H.263 have a licensing agreement of any sorts in place. Then again I wonder if the IPR-situation of H.263 (or MPEG-1 Part 2, or Theora, ...) can be simplified by mandating support only for Intra-frames (a decoder would be allowed, but not required, to skip decoding other frame types). This would mostly boil down to "mimick MJPEG", but with a clear upgrade path to "real video codec" for those who feel that the IPR situation for additional bitstream features is under control (by age of the codec, by IPR research, by licensing, ...). Best regards, Maik
- 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