IETF Logo Mail Archive

Re: [rtcweb] Video Codec MTI & User Experience == 1

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 14 March 2013 19:23 UTC

Return-Path: <btv1==7857ef4b335==HKaplan@acmepacket.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 91BE711E812A for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level:
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599]
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 yDt7n2upYKfK for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:23:42 -0700 (PDT)
Received: from mx1.acmepacket.com (mx1.acmepacket.com [216.41.24.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFA811E80F2 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 12:23:42 -0700 (PDT)
X-ASG-Debug-ID: 1363289013-03fc200f265c39d0001-4f8tJD
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx1.acmepacket.com with ESMTP id 081VGN0AqxJEdvPP (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Mar 2013 15:23:33 -0400 (EDT)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.222]) by Mail1.acmepacket.com ([169.254.1.130]) with mapi id 14.02.0283.003; Thu, 14 Mar 2013 15:23:33 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [rtcweb] Video Codec MTI & User Experience == 1
X-ASG-Orig-Subj: Re: [rtcweb] Video Codec MTI & User Experience == 1
Thread-Index: AQHOIOlqOBwpPfyVPU2s5T4qQkHCPA==
Date: Thu, 14 Mar 2013 19:23:33 +0000
Message-ID: <7EE4B84B-FEDE-4878-A21A-9CB8968E62D5@acmepacket.com>
References: <CAMRcRGS6_UZzhdGQEByxR1tBXudjpcNBO9Jx3euZLjkaaQZ15g@mail.gmail.com>
In-Reply-To: <CAMRcRGS6_UZzhdGQEByxR1tBXudjpcNBO9Jx3euZLjkaaQZ15g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9A282570229FF145875A36C437227328@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1363289013
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://spam.acmepacket.com:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.125204 Rule breakdown below pts rule name description ---- ---------------------- --------------------------------------------------
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Video Codec MTI & User Experience == 1
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: Thu, 14 Mar 2013 19:23:44 -0000

On Mar 14, 2013, at 1:59 PM, Suhas Nandakumar <suhasietf@gmail.com> wrote:

>  I feel a good user experience is as important as MTI being successfully negotiated. Users will turn off their video and de-escalate to audio only interaction if they look terribly bad in any kind of use-cases dealt within RTCWeb. 

Yes, but that's the point - a *user* can choose to do it.  And a user can choose to instead live with whatever crappy video they can get.  The great thing is it would be the user's choice.  But if we don't pick at least one MTI, no matter how good or bad it is, then the user won't have that choice... because there will be no video if the two ends don't happen to implement the same one.

And I'm not saying that with respect to either VP8 or H.264 - as far as I can tell neither of them can be an MTI codec right now, since we've been told each group of vendors can't live with the other's codec.


> We should be avoiding this at any cause since it defeats the purpose of RTCWeb to enable rich interactions via audio, video.

Define "rich interactions".  Obviously choosing an MTI codec that provides 4-pixel video would be a waste of our time.  But is H.261 sufficient to 'richly' communicate?  If I communicate with my wife/kids/siblings while I'm traveling, of course I'd prefer it be great quality video, but I can live with H.261.  What I won't put up with is having my browser decide the video's "not good enough for me", or having to make us all use the same browser vendor. (we don't)

Just my 2 cents.

-hadriel

v2.23.0 | Report a Bug | By Email