Re: [rtcweb] On video codec for rtcweb

Cameron Byrne <cb.list6@gmail.com> Sat, 24 March 2012 01:10 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A852721E8011 for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 18:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.462
X-Spam-Level:
X-Spam-Status: No, score=-3.462 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MakK8v+P8npp for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B379F21E800F for <rtcweb@ietf.org>; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so3233271pbb.31 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nslgQF86YX2q4TALRtp9liBPhyY8u2f3PJwmh6myNeo=; b=sDhR9DByV/PNwqKxOMZufZvQnQi0dyLKm/lempdyLGvmQDR8SeoAFQKcTv3QPndYHe EVJwfZsUnDGhA8o3QCsHe9f3Bhr9acTQoWCXWoRo7yBsBsrqoIkH7rCoeJgpcKlN9y4l KvE05gu5xIMGBpmS3i8Ql5vWpFFYP/AgWhJFwtEYCpd/Fm8dJga3vSzbClfgEfPtrFhi xAkLebqxY2uPMpMkXRJb0asJgQCTAEmSelq5LK2EDTl6pvmyizohCHHV1yiI/KjQW+39 ZU3m+eavMruZh+NXfCdpzvYYZdp+yECJarqa1JK9zuvffqRatsjeR86qe/DYJa6sqcMB tnQQ==
MIME-Version: 1.0
Received: by 10.68.219.131 with SMTP id po3mr33466827pbc.70.1332551424454; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
Received: by 10.143.160.13 with HTTP; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
Received: by 10.143.160.13 with HTTP; Fri, 23 Mar 2012 18:10:24 -0700 (PDT)
In-Reply-To: <BCB3F026FAC4C145A4A3330806FEFDA94086731AF2@EMBX01-HQ.jnpr.net>
References: <4F6C5A5E.6050100@ericsson.com> <4F6C6138.6010908@mozilla.com> <E44893DD4E290745BB608EB23FDDB76219E813@008-AM1MPN1-041.mgdnok.nokia.com> <4F6C6DC1.7020606@mozilla.com> <CAD5OKxu3Q45wASxLUhOR5kyPUZZb=81ybvZrpkbFuyqomsRH9Q@mail.gmail.com> <4F6CC86A.3090107@hidayahonline.org> <CAD5OKxu_668CbS1sPYzfK-Je9XGvDstsGMCmK_6-UbOMFZ2DUQ@mail.gmail.com> <BCB3F026FAC4C145A4A3330806FEFDA94086731AF2@EMBX01-HQ.jnpr.net>
Date: Fri, 23 Mar 2012 18:10:24 -0700
Message-ID: <CAD6AjGSn+qqc=w5uZ+D1svLth4Xx3z7PV19LWRBaBN0BzDLFDg@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Gregory Maxwell <gmaxwell@juniper.net>
Content-Type: multipart/alternative; boundary="e89a8ff249794caf5c04bbf2ce74"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] On video codec for rtcweb
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2012 01:10:25 -0000

On Mar 23, 2012 5:49 PM, "Gregory Maxwell" <gmaxwell@juniper.net> wrote:
>
> Roman Shpount wrote:
> > I am not arguing for making H.264 a base codec. I would actually prefer
> > VP8. All I was saying that despite lack of interoperability on
> > encryption, ICE, and identity, there are still significant benefits of
> > supporting the same codecs when communicating with legacy equipment,
>
> This is all true, but there won't always be a gateway or SBC in the media
> path and users may not want one even if all it did was transcode. The case
> with no media gateway can _only_ work reliably by virtue of compatibility
> being baked into the specification— in the other cases interoperability
> is 'simply' a matter of different tradeoffs.
>
> An interesting observation on the cost of transcoding: a number of
> mobile providers are now transparently transcoding their users' http
> video downloads on the fly, not for the purposes of changing the codec,
> but solely to make them smaller. This can do terrible things to the video
> quality (beyond just the reduction in bitrate: MP4 wasn't designed to
> stream from a live source). Perhaps this is an argument for more pervasive
> end-to-end encryption— but the point remains that CPU power, especially

Excellent points both about encryption and codec. This carrier transcoding
mess is a real challenge and should be architecturally thwarted.

Cb

> CPU power in high density data-centers, is still relatively cheap.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb