Re: [rtcweb] Video codec selection - way forward

[Gonzalo Camarillo <[e-mail]>]

Hi,

with respect to what types of alternatives will be considered, at this
point I would prefer to focus on agreeing on a MUST-level statement.
Once we do that, we can consider SHOULD-level statements if the group
considers them important.

Additionally, there have been a few suggestions related to combining
several options. For example, 4+5 or 5+6. I would suggest to keep these
combinations separate and not to treat them as completely new options
for clarity. Such separation would help us decide among atomic options
(which is already difficult enough) as opposed to deciding among
more-complex combinations.

In any case, these are just my preferences. As usual, I will let the
chairs manage this process with the inputs of the WG.

Cheers

Gonzalo

On 13/11/2013 10:23 PM, Gonzalo Camarillo wrote:
> Folks,
> 
> I hope everybody had a safe trip back home after Vancouver.
> 
> As you all know, we need to make progress regarding the selection of the
> MTI video codec. The following are some of the alternatives we have on
> the table:
> 
>  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
>  5. All entities MUST support either H.264 or VP8
>  6. All entities MUST support H.261
>  7. There is no MTI video codec
> 
> If you want the group to consider additional alternatives to the ones
> above, please let the group know within the following *two weeks*. At
> that point, the chairs will be listing all the received alternatives and
> proposing a process to select one among them.
> 
> Please, send your proposals in an email to the list. You do not need to
> write a draft; just send the text you would like to see in the final
> document regarding video codecs.
> 
> Thanks,
> 
> Gonzalo
> Responsible AD for this WG
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>