Re: [rtcweb] Straw Poll on Video Codec Alternatives

[Erik Lagerway <[e-mail]>]

>
>
>
>    1.
>
>    All entities MUST support H.264
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *Insisting on royalty bearing codec will have an adverse
>       effect on software development, specifically with indie development in
>       mind. I would take the IPR issues over royalties.*
>       2.
>
>    All entities MUST support VP8
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *YES*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *It seems this codec is getting closer to MPEG-LA thumbs up
>       so I don't see why we should not all use this codec as a minimum. It's also
>       the current codec in the majority of WebRTC implementations today.*
>       3.
>
>    All entities MUST support both H.264 and VP8
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 1.*
>       4.
>
>    Browsers MUST support both H.264 and VP8, other entities MUST support
>    at least one of H.264 and VP8
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *YES*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *This is likely the best scenario after VP8*
>       5.
>
>    All entities MUST support at least one of H.264 and VP8
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]:  *Acceptable*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them:
>       6.
>
>    All entities MUST support H.261
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *Feels like we are going backwards here.*
>       7.
>
>    There is no MTI video codec
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *Acceptable*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *If we can't agree on a specific codec this could be a way
>       forward and put the MTI issue to rest.*
>       8.
>
>    All entities MUST support H.261 and all entities MUST support at least
>    one of H.264 and VP8
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 6*
>       9.
>
>    All entities MUST support Theora
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *Too obscure.*
>       10.
>
>    All entities MUST implement at least two of {VP8, H.264, H.261}
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *Mandating one codec is hard enough.*
>       11.
>
>    All entities MUST implement at least two of {VP8, H.264, H.263}
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 10*
>       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
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 10*
>       13.
>
>    All entities MUST support H.263
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 6*
>       14.
>
>    All entities MUST implement at least two of {VP8, H.264, Theora}
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 10*
>       15.
>
>    All entities MUST support decoding using Theora.
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 9*
>       16.
>
>    All entities MUST support Motion JPEG
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]: *NO*
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them: *See 9*
>
>
>
>  H.264 is a reference to the proposal in
> https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/<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/<https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/>
>
> Theora is a reference to Xiph.org Theora Specification from March 16, 2011
> (http://www.xiph.org/theora/doc/Theora_I_spec.pdf)
>
> H.263 is a reference to profile 0 level 70 defined in annex X of ITU-T rec
> H.263 (http://www.itu.int/rec/T-REC-H.263/)
>
> H.261 is a reference to http://tools.ietf.org/html/rfc4587
>
> Motion JPEG is a reference to http://tools.ietf.org/html/rfc2435
>
>
> Thanks,
>
> The Chairs
>
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>