Re: [rtcweb] Straw Poll on Video Codec Alternatives

["Karl Stahl" <[e-mail]>]

Karl Stahl's response (for Ingate and Intertex):

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:

- Only if a downloadable codec (like Cisco's offering, for IPR concern) slot
and multiple codec slots are recommended: "SHOULD" - we must not get locked
into another 50 years of "Video G.711" base level now - and also other
services (IPR or not) should be able to use browsers if providing their own
downloadable codec - will also drive improvement and innovation (VP9,
H.26x.).

- Transcoding (which we got as priority request from day one of the "VP8
only days", from both SP and PBX/UC side, must be avoided [1] as being
against the core idea of WebRTC  

 

2.    All entities MUST support VP8

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

Yes

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

- Only if a downloadable codec (like Cisco's offering, for compatibility and
for VP8 itself for those that e.g. believes that Nokia IPR objections are
more than political) slot and multiple codec slots are mandated: "MUST" - we
must not get locked into another 50 years of "Video G.711" base level now -
and also other services (IPR or not) should be able to use browsers if
providing their own downloadable codec - will also drive improvement and
innovation (VP9, H.26x.).

- Transcoding (which we got as priority request from day one of the "VP8
only days", from both SP and PBX/UC side, must be avoided [1] as being
against the core idea of WebRTC  

 

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:

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:

5.    All 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:

Only if codec slots also are mandated: "MUST"

6.    All entities MUST support H.261

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

No, simply too old/bad

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

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:

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:

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:

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

No

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

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

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

No

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

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

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:

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:

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:

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:

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:

 

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