Re: [rtcweb] Straw Poll on Video Codec Alternatives

[Stephan Wenger <[e-mail]>]

I’m in the camp that questions the value of this straw poll, but it doesn’t take much time for me, and I’m a good little nerd, so I comply with the esteemed chairs’ request.
Please find below my input.
Stephan





  1.  All entities MUST support H.264

     *   Are you in favor of this option [Yes/No/Acceptable]: Acceptable

     *   Do you have any objections to this option, if so please summarize them: Preference for SVC, H.265, modern codecs with scalability in general

  2.  All entities MUST support VP8

     *   Are you in favor of this option [Yes/No/Acceptable]: Acceptable

     *   Do you have any objections to this option, if so please summarize them: Preference for SVC, H.265, modern codecs with scalability in general

  3.  All entities MUST support both H.264 and VP8

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: High cost (licensing, risk allowance) for no gain

  4.  Browsers MUST support both H.264 and VP8, other entities MUST support at least one of H.264 and VP8

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: PC software centric view (Browser!=other entities) is not future proof—doesn’t hold up well even today.

  5.  All entities MUST support at least one of H.264 and VP8

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: No interop point

  6.  All entities MUST support H.261

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: misapplying yesterdays’ technology just for compliance with “requirements” of a business model that is not mine does not make sense to me.

  7.  There is no MTI video codec

     *   Are you in favor of this option [Yes/No/Acceptable]: Yes.

     *   Do you have any objections to this option, if so please summarize them: Running code (W3C/WhatWG no MTI decision worked out well enough for the web).  There is at least a chance that the world decides on a modern codec, against ideologists and niche folk noisy demands.

  8.  All entities MUST support H.261 and all entities MUST support at least one of H.264 and VP8

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: misapplying yesterdays’ technology just for compliance with “requirements” of a business model that is not mine does not make sense to me.  In addition: High cost (licensing, risk allowance) for no gain

  9.  All entities MUST support Theora

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: Hi risk for no gain.  W3C/WhatWG looked into this, carefully, and decided against it.

  10. All entities MUST implement at least two of {VP8, H.264, H.261}

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: misapplying yesterdays’ technology just for compliance with “requirements” of a business model that is not mine does not make sense to me. In addition: High cost (licensing, risk allowance) for no gain

  11. All entities MUST implement at least two of {VP8, H.264, H.263}

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: misapplying yesterdays’ technology just for compliance with “requirements” of a business model that is not mine does not make sense to me. In addition: High cost (licensing, risk allowance) for no gain

  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

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: High cost (licensing, risk allowance) for almost no gain.  Does not mitigate encoder patent risk in any meaningful way.

  13. All entities MUST support H.263

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: misapplying yesterdays’ technology just for compliance with “requirements” of a business model that is not mine does not make sense to me—especially when many the folks subscribing to the business model don’t want this alternative themselves.

  14. All entities MUST implement at least two of {VP8, H.264, Theora}

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: Potentially very high cost (licensing, risk allowance) for no gain

  15. All entities MUST support decoding using Theora.

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: Hi risk for no gain.  W3C/WhatWG looked into this, carefully, and decided against it.

  16. All entities MUST support Motion JPEG

     *   Are you in favor of this option [Yes/No/Acceptable]: No

     *   Do you have any objections to this option, if so please summarize them: technically inferior beyond reason.



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]<mailto:[e-mail]> https://www.ietf.org/mailman/listinfo/rtcweb