Re: [rtcweb] Silvia Pfeifer's choices

Maik Merten <maikmerten@googlemail.com> Sat, 28 December 2013 16:47 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 528621AFD60 for <rtcweb@ietfa.amsl.com>; Sat, 28 Dec 2013 08:47:00 -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 XLUJFXPJVFXi for <rtcweb@ietfa.amsl.com>; Sat, 28 Dec 2013 08:46:58 -0800 (PST)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9306F1AFD5E for <rtcweb@ietf.org>; Sat, 28 Dec 2013 08:46:58 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id h10so4493167eak.30 for <rtcweb@ietf.org>; Sat, 28 Dec 2013 08:46:53 -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=7JcDb79z/WsF8PB2msZCks3Rz/msjP5IJzoQLaLrMRU=; b=n1Sh6NtGAsR1xgVgSJdARn8sBIkUWpdZUfoXRkqrt4se1hojK/k09jsWvp5UbaXBEK AxghBfvtaCEQZKp3qq4qi90HFa+3CDsHhVrkef8edR+T6dRphE319HMq6rqhdcwrf4DG Rqxibak1bkPzi0RbnJz7XD9OfeSeAcuauOQdr2Acz51Qtgbq1ccpuMo1Ou6G+OX8nWIS 0IqlWJ2LQvfWU8mzpEZFog5u7TBKdTKmwLAnyLDF/kpWy5Fy77dhOAB5HpBQsBF4A+9b 8PTbx+apP0mjwZjfgfF3XrMOI4qT2MwBLtYCna2PRz0RpAs75Ytyvss5gD9gzyBB4q0f 8cZA==
X-Received: by 10.15.82.136 with SMTP id a8mr3079902eez.81.1388249212851; Sat, 28 Dec 2013 08:46:52 -0800 (PST)
Received: from [192.168.2.109] (port-92-201-32-146.dynamic.qsc.de. [92.201.32.146]) by mx.google.com with ESMTPSA id o1sm92033770eea.10.2013.12.28.08.46.51 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 28 Dec 2013 08:46:51 -0800 (PST)
Message-ID: <52BF0079.5080609@googlemail.com>
Date: Sat, 28 Dec 2013 17:46:49 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <CAHp8n2mSQQ1s8GD4s0LR3HM27Hs6HmiL62sB+mzTaWCw06zxYA@mail.gmail.com>
In-Reply-To: <CAHp8n2mSQQ1s8GD4s0LR3HM27Hs6HmiL62sB+mzTaWCw06zxYA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Silvia Pfeifer's choices
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: Sat, 28 Dec 2013 16:47:00 -0000

Am 27.12.2013 03:45, schrieb Silvia Pfeiffer:
> 8. All entities MUST support H.261 and all entities MUST support at
> least one of H.264 and VP8
>    .a Acceptable (0.40)
>    .b I think we can achieve the same effect with 6. but 6. is a bit
> more future-proof
> Also, requiring the support of several codecs certainly increases
> maintenance requirements, but a compromise is certainly required.
> Maybe H.261 as the MTI and a recommendation on H.264 or VP8 as the
> newer codecs to implement right now with a need to revisit every 2
> years or so.

<snip>


> 10. All entities MUST implement at least two of {VP8, H.264, H.261}
>     .a Acceptable (0.35)
>     .b It's effectively the same as 8 and thus 8.b applies.
>

Actually, IMO option 10 is quite different from option 8. Note that with 
option 10 anyone who implements VP8 and H.264 (e.g., Mozilla) will not 
have to implement H.261, while still guaranteeing a non-empty 
intersection of codecs (i.e., no negotiation failure).

Option 10 encourages parties to implement two high-performance codecs to 
avoid old codec baggage, which overall will increase real-life 
performance. Option 8 does not have the "baggage drop" option and 
encourages choosing between the two high-performance codecs if one does 
not want to implement three codecs.


Maik