IETF Logo Mail Archive

Re: [rtcweb] Agenda for the upcoming meeting

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Mon, 20 October 2014 18:55 UTC

Return-Path: <fluffy@cisco.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 479D71A90D5 for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 11:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 GSgNNshcMn1p for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 11:55:37 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2D9C1A90D7 for <rtcweb@ietf.org>; Mon, 20 Oct 2014 11:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1906; q=dns/txt; s=iport; t=1413831338; x=1415040938; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=J3A9/6wTrESAn/X9Py/swD3/mHU/rfe9ziLhpRtZtqo=; b=guTMLtM70aea9allQbhRUx7F16gkcBFtBt+pasWRLUyApFpm9tTh3s6B 070od5TDt8b8ag/N7S8jNBofZrKL6KNqYDtoiwOjpDaDL4slbsgKDgNgH XcEClZicW7F2zx7M+HIQGyPZluGn5h4uXV6DeVu6iLYF9iff6ucK+/8hC o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAG1ZRVStJA2F/2dsb2JhbABcgmsjU1gEzCMKhnlUAoETFgF9hAIBAQEDAQEBATc0CwULAgEIGB4QJwslAgQOBYg3BwEBDMU1AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSQHjMHgy2BHgWFFYxshEaHE5Yig3dsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,757,1406592000"; d="scan'208";a="364645935"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-1.cisco.com with ESMTP; 20 Oct 2014 18:55:37 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9KItaGu029522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Oct 2014 18:55:36 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 13:55:36 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>
Thread-Topic: [rtcweb] Agenda for the upcoming meeting
Thread-Index: AQHP6WQkELuqOHwpNkKkJQp4VRk4Xpw4SxAAgAFk34A=
Date: Mon, 20 Oct 2014 18:55:36 +0000
Message-ID: <3A26E75E-BEF0-4D71-9372-01CE9D199E3D@cisco.com>
References: <CA+9kkMBQobeA_6aiMZffA6hHNkySK+CZptJU0XYzDyxGF4xE2A@mail.gmail.com> <54442F52.3090608@andyet.net>
In-Reply-To: <54442F52.3090608@andyet.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.20.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0F4DE9B87218E248994EB145EC6ABAB3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/CzUKRYluMupvrU0EhEl9xoM86Xo
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 18:55:39 -0000

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. 

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 

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

Cullen

So far much of conversation has been folks in the Microsoft camp - keep in mind some of that group has said in the past they would be 

On Oct 19, 2014, at 3:38 PM, Peter Saint-Andre - &yet <peter@andyet.net> wrote:

> On 10/16/14, 11:10 AM, Ted Hardie wrote:
>> During this morning chairs call, we discussed the agenda for the
>> upcoming meeting.  The two big items are JSEP and the video codec
>> discussion, and our current thought is to have the JSEP discussion on
>> Monday and the video codec discussion on Thursday.
> 
> As far as I can see, the temper of the list has been that it would be premature and a waste of energy to discuss the video codec topic at IETF 91. Do the chairs see things differently?
> 
> Peter
> 
> -- 
> Peter Saint-Andre
> https://andyet.com/
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email