Re: [rtcweb] A different perspective on the video codec MTI discussion

The operative word being "IF" - and always read the fine print first!

From: Cameron Byrne [mailto:cb.list6@gmail.com]
Sent: Wednesday, March 13, 2013 09:26 PM Central Standard Time
To: Andrew Allen
Cc: lorenzo@meetecho.com <lorenzo@meetecho.com>; rtcweb@ietf.org <rtcweb@ietf.org>; jdrosen@jdrosen.net <jdrosen@jdrosen.net>
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion

On Mar 13, 2013 7:11 PM, "Andrew Allen" <aallen@blackberry.com<mailto:aallen@blackberry.com>> wrote:
>
>
>
> Lorenzo
>
> A good piece of advice when shopping is to always beware of the places where the price is not well advertised - the fact that the price is not known in advance does not mean its free - and often quite the opposite!
>
> Andrew
>
Since we are handing out advice.

Here is another piece if advice.

If it's free, take 2.

CB
> ----- Original Message -----
> From: Lorenzo Miniero [mailto:lorenzo@meetecho.com<mailto:lorenzo@meetecho.com>]
> Sent: Wednesday, March 13, 2013 06:55 PM Central Standard Time
> To: Jonathan Rosenberg <jdrosen@jdrosen.net<mailto:jdrosen@jdrosen.net>>
> Cc: rtcweb@ietf.org<mailto:rtcweb@ietf.org> <rtcweb@ietf.org<mailto:rtcweb@ietf.org>>
> Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion
>
> Il giorno Wed, 13 Mar 2013 18:06:47 -0400
> Jonathan Rosenberg <jdrosen@jdrosen.net<mailto:jdrosen@jdrosen.net>> ha scritto:
>
> > I have one more thing to say - speaking now as a developer.
> >
> > As some of you may know, I recently returned to Cisco as CTO of the
> > cloud collaboration group, which is responsible for Webex. Webex was
> > one of the first services to do voice and video on the web, using
> > plugins of course. For our business, a key requirement is
> > interoperability with other video systems in the Cisco portfolio,
> > including our video clients and telepresence units. Those are all
> > based on H.264. Consequently, much as I would like to avoid the need
> > for a plugin, the benefits of eliminating the plugin do not outweigh
> > the drawbacks of having to transcode from VP8 to H.264. If IETF
> > selects VP8 as the MTI codec, this will make it dramatically more
> > difficult and expensive for us to use webRTC. If H.264 is the MIT
> > codec, it will make it much easier for us to use webRTC.
> >
>
> Speaking as a developer working for a company with much less money than
> yours, if the IETF selects H.264 as the MTI codec, this will make it
> even more dramatically difficult and expensive (if not impossible) for
> pretty much everybody else to use webRTC, or at least to develop
> services based on it.
>
> Lorenzo
>
> --
> Lorenzo Miniero, COB
>
> Meetecho s.r.l.
> Web Conferencing and Collaboration Tools
> http://www.meetecho.com
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.