Re: [rtcweb] Sanjay Mishra's choices

"Mishra, Sanjay" <sanjay.mishra@verizon.com> Sat, 28 December 2013 03:37 UTC

Return-Path: <sanjay.mishra@verizon.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 157561AEEAF for <rtcweb@ietfa.amsl.com>; Fri, 27 Dec 2013 19:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.139
X-Spam-Level:
X-Spam-Status: No, score=-3.139 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 XMyoAWIaE9CA for <rtcweb@ietfa.amsl.com>; Fri, 27 Dec 2013 19:37:07 -0800 (PST)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id 414181AE867 for <rtcweb@ietf.org>; Fri, 27 Dec 2013 19:37:06 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe01.verizon.com with ESMTP; 28 Dec 2013 03:36:58 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="4.95,564,1384300800"; d="scan'208";a="619837798"
Received: from fhdp1lumxc7hb05.verizon.com (HELO FHDP1LUMXC7HB05.us.one.verizon.com) ([166.68.59.192]) by fldsmtpi02.verizon.com with ESMTP; 28 Dec 2013 03:36:58 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB05.us.one.verizon.com ([166.68.59.192]) with mapi; Fri, 27 Dec 2013 22:36:58 -0500
To: cowwoc <cowwoc@bbs.darktech.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Fri, 27 Dec 2013 22:36:57 -0500
Thread-Topic: [rtcweb] Sanjay Mishra's choices
Thread-Index: Ac8DPzp+anyakcElTHqCzYqym8EXHwAN/2pA
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62C82365481@FHDP1LUMXC7V23.us.one.verizon.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <900A1E2059ADB149B905E3C8FA0046A62C82365151@FHDP1LUMXC7V23.us.one.verizon.com> <52BA718E.1030105@it.aoyama.ac.jp> <900A1E2059ADB149B905E3C8FA0046A62C823653F7@FHDP1LUMXC7V23.us.one.verizon.com> <52BDDDBB.60703@bbs.darktech.org>
In-Reply-To: <52BDDDBB.60703@bbs.darktech.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [rtcweb] Sanjay Mishra's choices
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: Sat, 28 Dec 2013 03:37:09 -0000

Gili -- There are and can be many possibilities based on the specific use cases that a service provider like my employer may need to support that may not exclude transcoding or possibly dropping to audio only. 

It is a bit early for me to conjecture on choices the working group may end up with to then take the consensus call on but I for one hope the group & chairs pay more credence to a decision that is forward looking and not one where an MTI codec is selected but at the cost of needing plug-ins.

Thanks
Sanjay

-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of cowwoc
Sent: Friday, December 27, 2013 3:06 PM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] Sanjay Mishra's choices

So you are saying that if H.264 is not selected as MTI you would rather drop down to audio-only (or do transcoding) than support any other codec?

I know H.264 is your ideal choice, but what option do you favor if that falls through?

Gili

On 27/12/2013 1:20 PM, Mishra, Sanjay wrote:
> Martin -- We are ok to have VP8 in addition to H.264 which is what option 3 is, but are not supportive of eliminating H.264 as a MTI which is a possible outcome of choices under option 10. H.261 is not a reasonable alternative to H.264; it is an inherently low resolution (CIF) and used for video conferencing over the ISDN lines and is a big step backwards.
>
>
> Thanks
> Sanjay
>
>
> -----Original Message-----
> From: "Martin J. Dürst" [mailto:duerst@it.aoyama.ac.jp]
> Sent: Wednesday, December 25, 2013 12:48 AM
> To: Mishra, Sanjay
> Cc: rtcweb@ietf.org
> Subject: Sanjay Mishra's choices (was: Re: [rtcweb] Straw Poll on 
> Video Codec Alternatives)
>
> Hello Sanjay, others,
>
> I have a clarifying question below.
>
> On 2013/12/24 23:44, Mishra, Sanjay wrote:
>> Please see responses for video codec alternatives below.
>>
>> Thanks
>> Sanjay
> [snip]
>
>> 3.    All entities MUST support both H.264 and VP8
>>
>> a.    Are you in favor of this option [Yes/No/Acceptable]: YES
> [snip]
>
>> 10.  All entities MUST implement at least two of {VP8, H.264, H.261}
>>
>> a.    Are you in favor of this option [Yes/No/Acceptable]: NO
>>
>> b.    Do you have any objections to this option, if so please summarize them:
>>
>> o   Do not support possible outcome of VP8 and H.261 as MTI
> Given that you are in favor of 3, and surprised at the NO here, and even more surprised at your justification. What's the problem if, under this option, some entities (not you) decide to implement VP8 and H.261, and communicate among themselves using either of these two?
>
> It looks to me like there's either a fundamental issue for you that nobody else has mentioned yet, or there is a misunderstanding, and it would be great if you could clarify.
>
> Regards,   Martin.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb