Re: [rtcweb] Straw Poll on Video Codec Alternatives

["Roni Even" <[e-mail]>]

Hi,

Here is my view

Roni

1.  All entities MUST support H.264

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

b.    Do you have any objections to this option, if so please summarize
them:

2.    All entities MUST support VP8

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

a.    Do you have any objections to this option, if so please summarize
them:  Inteop issues with video conferencing

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

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

a.    Do you have any objections to this option, if so please summarize
them: Complicate the implementation but provide interoperability

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]: Acceptable

a.    Do you have any objections to this option, if so please summarize
them: Complicate the implementation but provide interoperability

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

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

a.    Do you have any objections to this option, if so please summarize
them:  Does not provide interoperability

6.  All entities MUST support H.261

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

a.    Do you have any objections to this option, if so please summarize
them: low quality

7.  There is no MTI video codec

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

a.    Do you have any objections to this option, if so please summarize
them:  There are better options like having more than one MTI codec

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

a.    Do you have any objections to this option, if so please summarize
them: H.261 does not provide the quality

9.  All entities MUST support Theora

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

a.    Do you have any objections to this option, if so please summarize
them: Not widespread enough for interoperability

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

a.    Do you have any objections to this option, if so please summarize
them: H.261 is not the right codec

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

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

a.    Do you have any objections to this option, if so please summarize
them: A better solution if cannot agree on one MTI codec

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]: Acceptable

a.    Do you have any objections to this option, if so please summarize
them: will have interoperability issues with video conferencing systems

13.  All entities MUST support H.263

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

a.    Do you have any objections to this option, if so please summarize
them:  better have newer codecs

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

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

a.    Do you have any objections to this option, if so please summarize
them:  will not address interoperability

15.  All entities MUST support decoding using Theora.

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

a.    Do you have any objections to this option, if so please summarize
them: No MTI codec and no interoperability

16.  All entities MUST support Motion JPEG

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

a.    Do you have any objections to this option, if so please summarize
them: bandwidth and interoperability issues

 

H.264 is a reference to the pro
<https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/> posal
in https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/

 

VP8 is a reference to the pro
<https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/> posal in
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>
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>
http://tools.ietf.org/html/rfc4587 

 

Motion JPEG is a reference to  <http://tools.ietf.org/html/rfc2435>
http://tools.ietf.org/html/rfc2435 

 

Thanks,

 

The Chairs