Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)

Iñaki Baz Castillo <ibc@aliax.net> Wed, 05 November 2014 15:47 UTC

Return-Path: <ibc@aliax.net>
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 A45221ACE86 for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 07:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 xrYYWdTU3zuf for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 07:47:44 -0800 (PST)
Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CB301A8888 for <rtcweb@ietf.org>; Wed, 5 Nov 2014 07:47:44 -0800 (PST)
Received: by mail-qa0-f41.google.com with SMTP id s7so675222qap.0 for <rtcweb@ietf.org>; Wed, 05 Nov 2014 07:47:43 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=TQRINA6hllD3JUJzdQ8L7N3W8qt0/e0bg4EsnMG5gZA=; b=Q5gvRynNrEbPfNDl1zyb2Mlt/H0NbLjAC0nDZzClNQjv45baWGTi6YxnV2LIba4W5u I/WYXrazf55WL9fgny8xK4f/BxNTJZNqozwbI9wznVW+PmcJAdzyNao0aXL9gaSoIST2 LVwZnMunpT1txbXY1kkQSZYQp4D8DltPtKLLxIMMRET0DNGWoQUAFvi/pMFFyBCH1k6T u6fEF7tJOTo/f4rC0Bdz5fdhHpShGnC2FjLVn6FO1zHlR7NMtpMmfpZq22KEr0VJdlBp 4ljwYuIvPkvTo8YRxeIADQWDY0UYoVRQKm7/BYW+oXSrXzKXozOrDcXgcKCJ3er+F1zz nM+Q==
X-Gm-Message-State: ALoCoQnL7IwZeIWKvuxtn6eGxCrwL6xddUJssLKkB838FjHVGNSdGm8ZYca1e+Cd6OLHQZKr2faR
X-Received: by 10.140.19.9 with SMTP id 9mr33802339qgg.98.1415202463328; Wed, 05 Nov 2014 07:47:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.69.200 with HTTP; Wed, 5 Nov 2014 07:47:23 -0800 (PST)
In-Reply-To: <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com>
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se> <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 05 Nov 2014 16:47:23 +0100
Message-ID: <CALiegf=c=APH4adLXGeRKAf8rf68yCPL8Sp8mDfAzm18_oSxHg@mail.gmail.com>
To: tim panton <tim@phonefromhere.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/y2a5pZRZzCQtPSD6uhWt1eYNZ7A
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)
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, 05 Nov 2014 15:47:45 -0000

2014-11-04 18:01 GMT+01:00 tim panton <tim@phonefromhere.com>:
> All implementations of the rtcweb specification must implement at least one of  VP8 or H.264,
> implementations that also implement the w3c’s webRTC javascript  API must implement  both VP8 and H264

+1

This is obviously the only way-to-go and the only reasonable and
feasible decision.

BTW and given that this is a W3C business, I would replace:
  "implementations that also implement the w3c’s webRTC javascript  API"
with:
  "browsers"

-- 
Iñaki Baz Castillo
<ibc@aliax.net>