Re: [rtcweb] Input to Video Codec Selection

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Sun, 03 March 2013 08:44 UTC

Return-Path: <stefan.lk.hakansson@ericsson.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 B9BBD21F862E for <rtcweb@ietfa.amsl.com>; Sun, 3 Mar 2013 00:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.907
X-Spam-Level:
X-Spam-Status: No, score=-5.907 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60MTF2lj7aTb for <rtcweb@ietfa.amsl.com>; Sun, 3 Mar 2013 00:44:58 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1D36921F8626 for <rtcweb@ietf.org>; Sun, 3 Mar 2013 00:44:50 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-ea-51330d815d55
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id E1.0B.32353.18D03315; Sun, 3 Mar 2013 09:44:50 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0318.004; Sun, 3 Mar 2013 09:44:49 +0100
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [rtcweb] Input to Video Codec Selection
Thread-Index: AQHOFohSX+FIz7sRDUakjRmzQELT9piTpd7w
Date: Sun, 03 Mar 2013 08:44:48 +0000
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B0BA4DF@ESESSMB209.ericsson.se>
References: <5130B9C3.3010404@ericsson.com>
In-Reply-To: <5130B9C3.3010404@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+JvjW4Tr3GgwcyfzBZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY9oO3oK7/BX//y9kbWB8z9PFyMkhIWAiceLDM2YIW0ziwr31 bF2MXBxCAocYJb582MgK4SxilFh46RATSBWbQKDE1n0L2EBsEQEziYcT9oPZzALqEncWn2MH sYWBpk7oPMcEUWMqcfbUI6h6I4m3l9YCDeXgYBFQkTiyNxskzCvgLfHy0CJGEFtIQFvi+M92 sDGcAjoSxyYdZQGxGYGO+35qDRPEKnGJW0/mM0EcLSCxZM95qAdEJV4+/scKYStK7DzbzgxR rydxY+oUqDO1JZYtfM0MsVdQ4uTMJywTGMVmIRk7C0nLLCQts5C0LGBkWcXInpuYmZNebr6J ERgNB7f8NtjBuOm+2CFGaQ4WJXHecNcLAUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYW4y2 C+mJn3vrOJX9m+tHJYOtctkMUy8vjeUqj98g1np7vX70ucXymxtXbTmhkO/eIuq1msmeXfL2 /79XD06cs6FQ80eZ2n22lYfs2W3f9BnfCjlkKpxwsc262uWhbmz13+ypJU8bXjJce75sM5NX Xbnra/mz+hPm8lxVlmG/3XH1rO7Bzi1FSizFGYmGWsxFxYkAWcORA1QCAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Input to Video Codec Selection
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: Sun, 03 Mar 2013 08:44:59 -0000

I can understand the logic behind not wanting any new input before the meeting, but at the same time we did postpone this discussion one meeting cycle on request by Serge [1]. In his request Serge stated that "Google understands that concerns have been raised within the IETF RTCWEB WG in regards to VP8 IPR." and "We hereby commit to addressing this by the next IETF meeting in Orlando. Our  proposal will address prevalent IPR issues."

I have seen no such input yet, and if no new input is allowed, it seems like we will have the same discussion we postponed last time (all inputs look more or less unchanged to me). Is this the plan? Have the chairs reached out to Google to check the status (perhaps the IPR related things did encounter some delay, but will be ready shortly after the meeting)?

Stefan

[1] http://www.ietf.org/mail-archive/web/rtcweb/current/msg05698.html

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
Sent: den 1 mars 2013 15:23
Cc: rtcweb@ietf.org
Subject: [rtcweb] Input to Video Codec Selection

WG,

I hope everyone, especially Google, now have provided whatever input they have into the Video Codec discussion and selection. It is important that everyone has the possibility to evaluate the input in good time prior to the meeting. It is especially important if one might require legal or other support when evaluating the proposals or additional information, which might apply for IPR, as an example.

To be extremely blunt, we don't want anyone revealing new input material during the presentations in Orlando. These presentations is only intended to provide a summary of the most important aspects from the proponents side.


The RTCWEB WG chairs

Magnus Westerlund
Ted Hardie
Cullen Jennings

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