Re: [rtcweb] Plan for MTI video codec?

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 20 October 2014 10:05 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414FB1A7033 for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 03:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUgMskmDHBPR for <rtcweb@ietfa.amsl.com>; Mon, 20 Oct 2014 03:05:54 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF69F1A7028 for <rtcweb@ietf.org>; Mon, 20 Oct 2014 03:05:53 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 4519FF4BCD7EE; Mon, 20 Oct 2014 10:05:49 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9KA5Zg6008913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Oct 2014 12:05:51 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.25]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 12:05:49 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Victor Pascual <victor.pascual.avila@gmail.com>, Ca By <cb.list6@gmail.com>
Thread-Topic: [rtcweb] Plan for MTI video codec?
Thread-Index: AQHP669ol2Qsv7sEAECBFDAOBE1Cspw3bfYAgABSSQCAAA5FgIAAQIoAgAAzigCAABrFgIAAWhNA
Date: Mon, 20 Oct 2014 10:05:48 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B262458@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CAGTXFp-HVJDwd86207PNM2QVYO4Z_K4WF-KarnRs1fb7nvy4zA@mail.gmail.com> <CA+9kkMDfES8gpi0-PTXpCnQHjFYUSF2r44TNzH5B4UfDGo8PtA@mail.gmail.com> <CAGTXFp8O-7ACksk3v3f=KjCkcDb4e8G=t-e=EJ1503vt7TkpCQ@mail.gmail.com> <CAGTXFp867AMUZ_fEKxG9uAoR1H1AirVHi3-ayJ=KTQk9L+C7+g@mail.gmail.com> <CA+9kkMAZufR7gUrwkS7Tf5GOfg+ZtsZWGcn-8YLCvnmYnTgfFw@mail.gmail.com> <544035DE.8000606@matthew.at> <CABkgnnUNgWaauS6-nZ5fcExjsMPy4ZGPXaahduzA39=iqh9+fQ@mail.gmail.com> <D5D11F2B-9E32-4932-A601-F1D7FD50C706@gmail.com> <544117FB.6050706@alvestrand.no> <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com> <CA+23+fGWnWd0QEeCmZ=6BmJkPrUVW6cZ0jwmXA+fM88=_+_NWw@mail.gmail.com> <CAOW+2dugTtfLhk0VuJOk7OPEonGBApMjY93EZocH90RbX6X22w@mail.gmail.com> <54442128.6070009@alvestrand.no> <CAOW+2dt8j2VwmpeQ3qaCNOKNgrGz95Sp_ROq=FO9sNm7M2EX2w@mail.gmail.com> <E36D1A4AE0B6AA4091F1728D584A6AD2400622F1@ORSMSX158.amr.corp.intel.com> <CAD6AjGQVyxJrkbcB=vVaMbphckTwWT2k-U8evc2JAsPr6=6KaQ@mail.gmail.com> <09B5A70C-2537-412E-9898-E60E72008CBA@gmail.com>
In-Reply-To: <09B5A70C-2537-412E-9898-E60E72008CBA@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/qXJyILQ4CDaHg6ekt54rCDd_IXg
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Plan for MTI video codec?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 20 Oct 2014 10:06:00 -0000

Given that codecs appear in the end device and the 3GPP activity is to provide a gateway, either the gateway provides transcoding or the two end devices use SDP to agree on a mutually acceptable codec. 

Our view is that in many of these cases, it is perfectly possible for a webRTC device and the 3GPP device to decide to use H.264 as the codec and will do so, in order to avoid transcoding. 

That will occur whatever is specified as an MTI video codec.

Keith

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of 
> Victor Pascual
> Sent: 20 October 2014 07:00
> To: Ca By
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Plan for MTI video codec?
> 
> And that's what the 3GPP is doing for release 12: 
> http://webrtchacks.com/ims-approach-webrtc/
> 
> > On Oct 20, 2014, at 6:24 AM, Ca By <cb.list6@gmail.com> wrote:
> > 
> > My guess is the IMS will change to interop with webrtc in 
> an effort to stay relevant.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>