Re: [rtcweb] Video Codec Selection Alternatives - Timing

"Mishra, Sanjay" <sanjay.mishra@verizon.com> Wed, 27 November 2013 20:57 UTC

Return-Path: <sanjay.mishra@verizon.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 06D5E1ADFFD for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 12:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 1RUEx5_cC9u4 for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 12:57:51 -0800 (PST)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) by ietfa.amsl.com (Postfix) with ESMTP id A06381ADEBA for <rtcweb@ietf.org>; Wed, 27 Nov 2013 12:57:51 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by omzsmtpe02.verizonbusiness.com with ESMTP; 27 Nov 2013 20:57:50 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="4.93,784,1378857600"; d="scan'208";a="601579434"
Received: from fhdp1lumxc7hb03.verizon.com (HELO FHDP1LUMXC7HB03.us.one.verizon.com) ([166.68.59.190]) by fldsmtpi03.verizon.com with ESMTP; 27 Nov 2013 20:57:45 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB03.us.one.verizon.com ([166.68.59.190]) with mapi; Wed, 27 Nov 2013 15:57:43 -0500
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, =?utf-8?B?SGVydsOp?= <h_o_w_@hotmail.com>
Date: Wed, 27 Nov 2013 15:57:42 -0500
Thread-Topic: [rtcweb] Video Codec Selection Alternatives - Timing
Thread-Index: AQHO65/RWnplPSF720KudunmUkqDapo5jPZg
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62C80C15604@FHDP1LUMXC7V23.us.one.verizon.com>
References: <52935C89.5040408@ericsson.com> <CAGgHUiQnkQKkc-ptMu6DtfUYJY6N9i7PUaeAqKxp96nB2MQBGA@mail.gmail.com> <52936207.5040704@ericsson.com> <E44893DD4E290745BB608EB23FDDB7620A13302B@008-AM1MPN1-041.mgdnok.nokia.com> <5295B273.1060305@ericsson.com> <C5B67CF6-44C2-44ED-A087-67D9737870AD@gmail.com> <5295F718.9010603@ericsson.com> <900A1E2059ADB149B905E3C8FA0046A62C80B27806@FHDP1LUMXC7V23.us.one.verizon.com> <FEF4EFFB-0027-486B-BF99-8C3EA1514CFF@cisco.com>
In-Reply-To: <FEF4EFFB-0027-486B-BF99-8C3EA1514CFF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Video Codec Selection Alternatives - Timing
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, 27 Nov 2013 20:57:54 -0000

Cullen -- Got it. Thanks for clarifying.

Herve -- Thank you for your e-mail on the same as well.

Thank you
Sanjay
-----Original Message-----
From: Cullen Jennings (fluffy) [mailto:fluffy@cisco.com] 
Sent: Wednesday, November 27, 2013 1:38 PM
To: Mishra, Sanjay
Cc: Magnus Westerlund; rtcweb@ietf.org
Subject: Re: [rtcweb] Video Codec Selection Alternatives - Timing


Sanjay, the first step will be to ask if there is consensus to use the process. Right now we have been collecting comments on the process then Magnus will send out a revised process and a consensus call to use that process. I'd expect that consensus call to and revised process to go out tomorrow at the earliest and possibly a bit later. That consensus call would last roughly 2 weeks. If there is consensus to use that process then the voting period would start and be at least a few weeks long but adjusted to be longer if it ran over a significant holiday. 


On Nov 27, 2013, at 9:33 AM, "Mishra, Sanjay" <sanjay.mishra@verizon.com>; wrote:

> Magnus -- To confirm, the voting period is be two weeks, so I am assuming starting tomorrow (Nov 28) and lasting for two weeks (Dec 12?).
> 
> Thanks
> Sanjay
> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus 
> Westerlund
> Sent: Wednesday, November 27, 2013 8:44 AM
> To: Thomas Reisinger
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Video Codec Selection Alternatives 10 and 11: Merge?
> 
> On 2013-11-27 14:16, Thomas Reisinger wrote:
>> Magnus,
>> 
>> Could you please share the latest list and how the voting will be conducted/what's required to vote.
> 
> For the proposed voting process see our previous message 
> http://www.ietf.org/mail-archive/web/rtcweb/current/msg09909.html
> 
> As I stated, we chairs will need to update this based on the discussion.
> 
> For the current list of alternatives is on the WG's wiki:
> http://trac.tools.ietf.org/wg/rtcweb/trac/wiki/WikiStart
> 
> 
> Reproduced here:
> The following alternatives has been proposed:
> 
> 1. All entities MUST support H.264
> 2. All entities MUST support VP8
> 3. All entities MUST support both H.264 and VP8  4. Browsers MUST support both H.264 and VP8, other entities MUST
>    support at least one of H.264 and VP8  5. All entities MUST support at least one of H.264 and VP8  6. All entities MUST support H.261  7. There is no MTI video codec  8. 5+6, i.e. All entities MUST support H.261 and all entities MUST
>    support at least one of H.264 and VP8  9. All entities MUST support Theora 10. All entities MUST implement at least two of {VP8, H.264, H.261} 11. All entities MUST implement at least two of {VP8, H.264, H.263} 12. All entities MUST support decoding using both H.264 and VP8, and
>    MUST support encoding using at least one of H.264 or VP8
> 
> H.264 is a reference to the proposal in ​ 
> https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/
> 
> VP8 is a reference to the proposal in ​ 
> https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/
> 
> 
> 
>> 
>> Cheers,
>> 
>> Thomas Reisinger
>> 
>>> On 27.11.2013, at 09:50, Magnus Westerlund <magnus.westerlund@ericsson.com>; wrote:
>>> 
>>>> On 2013-11-25 20:51, Markus.Isomaki@nokia.com wrote:
>>>> MUST implement at least two of {VP8, H.264 CBP, H.261}
>>> 
>>> I have now updated the list to read:
>>> 
>>> 10. All entities MUST implement at least two of {VP8, H.264 CBP, 
>>> H.261} 11. All entities MUST implement at least two of {VP8, H.264 
>>> CBP, H.263}
>>> 
>>> Cheers
>>> 
>>> Magnus Westerlund
>>> 
>>> --------------------------------------------------------------------
>>> -
>>> - Multimedia Technologies, Ericsson Research EAB/TVM
>>> ----------------------------------------------------------------------
>>> Ericsson AB                | Phone  +46 10 7148287
>>> Färögatan 6                | Mobile +46 73 0949079
>>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> 
>>> 
>> 
>> 
> 
> 
> --
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb