Re: [rtcweb] Straw Poll on Video Codec Alternatives

[Jan-Ivar Bruaroey <[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:
        - Does not achieve interoperability, because it is not FOSS.
        - Still license encumbered. Even with decoder binary gift, this
        is still the blue pill.
        - Encoding is key to interoperability.

 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:
        - Risk. It might be prudent to wait a bit for Nokia claim to
        unfold (or fold).
        - Still best option until Daala.

 3.

    All entities MUST support both 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:
        - A compromise that marginalizes FOSS (license-free gets
        noncomply-labeled).

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

     2.

        Do you have any objections to this option, if so please
        summarize them:
        - What's a non-browser? Weakness of tying limits to names.
        - Not interoperable.

 5.

    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:
        - Not interoperable.

 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:
        - I'm unfamiliar with H.261, but claims of low quality makes me
        uninterested.

 7.

    There is no MTI video codec

     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:
        - Not interoperable.

 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:
        - Interoperably indistinguishable from #6 to me.

 9.

    All entities MUST support Theora

     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:
        - Seems like a less famous yet-to-be-sued VP8.

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:
        - I'm unfamiliar with H.261, but claims of low quality make me
        uninterested.

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:
        - I'm unfamiliar with H.263, but claims of IPR make me
        uninterested + seems old.

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:
        - Trojan!
        - At first seems like pragmatic result of #3 (why encode both
        when unnecessary)
        - But if few devices encode VP8 then even non-compliers cannot
        ignore licensing.
        - Hence not interoperable by my definition.

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:
        - I'm unfamiliar with H.263, but claims of IPR make me
        uninterested + seems old.

14.

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

     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:
        - Theora seems like a less famous yet-to-be-sued VP8.

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:
        - Trojan! Incoming call, hello?
        - If few devices encode Theora then even non-compliers cannot
        ignore licensing.
        - Theora seems like a less famous yet-to-be-sued VP8.

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:
        - Too bandwidth demanding.


Clarification: Why I call out "Trojan" in two answers above: Consistent 
with my other answers, a key to interoperability in my view is accepting 
(even non-compliant) license-unencumbered nodes in a network. I.e. Both 
sides of a call negotiation must agree to either of multiple formats, or 
"both" isn't truly both. - Thus, any question that separates encoding 
from decoding I call a Trojan, because incoming calls rule. I.e. If the 
other side requires a license, I need a license. True, I avoid an 
encoding license, so the distinction has merit, but beware of the 
licensing consequence when answering.

.: Jan-Ivar :.