Re: [rtcweb] Proposed Video Selection Process

"Ashish V. Thapliyal" <quavtum@gmail.com> Fri, 22 November 2013 21:54 UTC

Return-Path: <quavtum@gmail.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 206EE1AE241 for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 13:54:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 nRXQPl0XWmQX for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 13:54:08 -0800 (PST)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9521AE1BA for <rtcweb@ietf.org>; Fri, 22 Nov 2013 13:54:08 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id x12so1695488wgg.4 for <rtcweb@ietf.org>; Fri, 22 Nov 2013 13:54:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/hSkL6t6Dl8BfbfFP2F7GPBDNZqvLsIVqNq33vuO00A=; b=tQZIacjIP+1WpuRsGyOrL8+Kb990nnQ8utm/H7hu+dS96VaLY7wtv2EyINbXiD+p7x gaB6e93Jbct+bqb0e3L2Qx2VBFH0TdT7ZDSNwguPf3kzqPeIItOGfr6TWkeKEcEzVjJu sXdQVDLZ5wZ8gT6QIDBZtrqmz3FOh9M7skwWZWqCxGigLAZ4RVxLosQCRIreJGlih7Nc AqexqCO2b0dx7uTbChLx2xhGVASs7RG3B/747DjOKdigTN5uOiPp7mOoM4n9W6fF/+QR OF+B7K3O/zMWyGTanudR1zsvx8dH45pBD3cgSx5Dndos4qnds8CeoVPIpn40QwuYmcM6 mW2Q==
MIME-Version: 1.0
X-Received: by 10.180.206.18 with SMTP id lk18mr4413306wic.64.1385157240496; Fri, 22 Nov 2013 13:54:00 -0800 (PST)
Received: by 10.194.151.6 with HTTP; Fri, 22 Nov 2013 13:54:00 -0800 (PST)
In-Reply-To: <528E39F4.4010706@ericsson.com>
References: <528E39F4.4010706@ericsson.com>
Date: Fri, 22 Nov 2013 13:54:00 -0800
Message-ID: <CAJ8sk_54ky7n=FUmLRKuyyF-sucPNvz0tEO94JL4ZYVuEsmjnQ@mail.gmail.com>
From: "Ashish V. Thapliyal" <quavtum@gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11c3876a47290004ebcb0d68
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Fri, 22 Nov 2013 21:54:10 -0000

Dear Chairs,
         I have participated in a face-to-face interim meeting in 2012 and
have been closely following the discussions on this list.

         I appreciate your heroic efforts to get to consensus on a
mandatory-to-implement video codec.  I am against the proposal to put this
issue to vote.  It will be hard to get it right and it will generate a lot
of complaints about who gets to vote and who does not.  In my opinion, a
fair coin toss, or allowing "either H.264 or VP8" would be preferable.
         Another interesting proposal, mentioned later in this email
thread, is the decoupling of encoder and decoder requirements.  In
particular, the idea of making both VP8 and H.264 decoders mandatory to
implement, while allowing a choice of either VP8 or H.264 encoders, is very
interesting.  It may provide a good avenue for compromise while giving us
most of the benefits of choosing one of the codecs.  It may also discourage
patent trolling because if one of the encoders gets hit by an unforeseen
intellectual property issue,  vendors could switch to the other, without
waiting for a change in the standards.


Thanks,
Ashish.