Re: [rtcweb] Agenda for the upcoming meeting

Peter Saint-Andre - &yet <peter@andyet.net> Mon, 20 October 2014 19:28 UTC

Return-Path: <peter@andyet.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 4DCD01AC406 for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 12:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 S-Qr0rHKJtqq for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 12:28:25 -0700 (PDT)
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C753D1AC3FF for <rtcweb@ietf.org>; Mon, 20 Oct 2014 12:28:23 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id at20so63258iec.39 for <rtcweb@ietf.org>; Mon, 20 Oct 2014 12:28:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MF0KmWG8N2i581mjvUR+Fkx/LqzamGMYFPR+CP4TCzY=; b=cug0w5wbZrPOFpFkuL160/eIkuPYdSTgNNzZQh5a3Ti0l5jmU5vBuvdk8iIkqsFK1Z sN4zypuBR+5IX3O0ZZM5pdvGDnzXQvASWUzxle5xosxiujL8//xtuB1756gW0dNCGxmQ a5zzOfU8QhbeTDdpxkQFBug4LPZNb3R1UPXWp0If5EfqBVLCRGvRkYDqC8wc6VVoTrdh mR56tpvPYu+d085vFum01urFcnRcJocP5d6lx1K7sXWFIKek8vh2WC7UfNbzywJ8MHld HLIEH/n9xjfrBdRYSgojdo6VaidSgWe1ZtoiciyJq+tWn7caBgVtx41qqVT3jtPoCS6L vaiQ==
X-Gm-Message-State: ALoCoQkQWIGZiLOlZGWfeaTNgJzJew1JCxucWg+MJ+phs9H2emzguZMO6eK3g2+8/IozAb3hAetV
X-Received: by 10.50.171.138 with SMTP id au10mr21103349igc.4.1413833303047; Mon, 20 Oct 2014 12:28:23 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id v8sm4950294ioe.16.2014.10.20.12.28.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Oct 2014 12:28:22 -0700 (PDT)
Message-ID: <54456254.50201@andyet.net>
Date: Mon, 20 Oct 2014 13:28:20 -0600
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <CA+9kkMBQobeA_6aiMZffA6hHNkySK+CZptJU0XYzDyxGF4xE2A@mail.gmail.com> <54442F52.3090608@andyet.net> <3A26E75E-BEF0-4D71-9372-01CE9D199E3D@cisco.com>
In-Reply-To: <3A26E75E-BEF0-4D71-9372-01CE9D199E3D@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/fhTRDJRi6i-rIAT6rITMMS5JM8Y
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda for the upcoming meeting
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: Mon, 20 Oct 2014 19:28:27 -0000

On 10/20/14, 12:55 PM, Cullen Jennings (fluffy) wrote:
>
> So lets be clear here. Every time we checked, there has been
> consensus that we need an MTI codec. So right now this work is sort
> of blocked on that and we would like to get what people are calling
> webrtc 1.0 out before the end of 2015.  I think that a pragmatic look
> at this would result there is at least some reasonable odds it might
> take more than one or two meetings to resolve this if we end up in an
> alternative consensus process.

Given the parameters being assumed, you're probably right that several 
IETF meeting cycles will likely be needed.

> You said on the list you felt "the state of video codec development
> needs to evolve" before this discussions. I did not know what you
> what you see needs to happen in this evolution and how long should we
> wait before on this. I was wondering if you meant we should wait for
> the IETF to standardize a video codec (like the netvc BOF is
> proposing) but I really had no idea what you meant

IMHO, if that working group had been formed after the video codec BoF 
two years ago, we might be further along toward a real solution.

> Do you think there would be a better time to discuss this?

When we can make a decision on a technical basis, not a political basis. 
The current situation involves "camps", as you say, and I just don't 
think that's a good foundation from which to make decisions.

As things stand today, the most likely outcome appears to be "two MTIs" 
(which we've done in draft-ietf-rtcweb-audio so I suppose it's not the 
end of the world).

Peter

-- 
Peter Saint-Andre
https://andyet.com/