Re: [rtcweb] Video Codec Selection Alternatives 10 and 11: Merge?

[Leon Geyser <[e-mail]>]

Why don't we keep CBP on each H.264 entry? It will be more clear for the
voter for what they are actually voting for,

My opinions on some of the options:
Personally I feel there are too many options :)
1 and 2: Was already debated so I don't know why we should list them again.
3: Might be too difficult to follow resulting in people breaking the spec
anyway.
5: Actually implies 7.
7: Fail
8: I know I suggested this one, but 10 is actually nearly the same and is a
better option. Votes might get split between the two resulting in another
option taking lead. Is my thinking wrong?
11: Is H.263 really safe?
12: Do we know if you only implement a decoder that royalties won't apply?



On 27 November 2013 15:43, Magnus Westerlund <[e-mail]
> wrote:

> 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 <
> [e-mail]> wrote:
> >>
> >>> On 2013-11-25 20:51, [e-mail] 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  [phone]
> >> Färögatan 6                | Mobile [phone]
> >> SE-164 80 Stockholm, Sweden| mailto: [e-mail]
> >> ----------------------------------------------------------------------
> >>
> >>
> >
> >
>
>
> --
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  [phone]
> Färögatan 6                | Mobile [phone]
> SE-164 80 Stockholm, Sweden| mailto: [e-mail]
> ----------------------------------------------------------------------
>
>