Re: [rtcweb] Uploaded unified minutes for both days of IETF 86 meetings

Gaelle Martin-Cocher <gmartincocher@blackberry.com> Mon, 08 April 2013 16:10 UTC

Return-Path: <prvs=08103f7bc8=gmartincocher@blackberry.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 3D3F421F9374 for <rtcweb@ietfa.amsl.com>; Mon, 8 Apr 2013 09:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level:
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_BACKHAIR_21=1, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 Mlrx27cOxyhm for <rtcweb@ietfa.amsl.com>; Mon, 8 Apr 2013 09:10:33 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 9C54621F938A for <rtcweb@ietf.org>; Mon, 8 Apr 2013 09:10:32 -0700 (PDT)
X-AuditID: 0a41282f-b7f1a6d0000054a3-55-5162e84ba7bf
Received: from XCT103CNC.rim.net (smtp-pop.rim.net [10.65.161.203]) by mhs060cnc.rim.net (SBG) with SMTP id F2.6C.21667.B48E2615; Mon, 8 Apr 2013 10:54:51 -0500 (CDT)
Received: from XMB106BCNC.rim.net ([fe80::99b8:8d0e:cdcd:c00d]) by XCT103CNC.rim.net ([fe80::b8:d5e:26a5:f4d6%17]) with mapi id 14.02.0328.009; Mon, 8 Apr 2013 11:54:51 -0400
From: Gaelle Martin-Cocher <gmartincocher@blackberry.com>
To: Ted Hardie <ted.ietf@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Uploaded unified minutes for both days of IETF 86 meetings
Thread-Index: AQHOMjwy+L3NVZ7OuEeDDzWE1rlyipjMd+mw
Date: Mon, 08 Apr 2013 15:54:50 +0000
Message-ID: <92D0D52F3A63344CA478CF12DB0648AA2655AD06@XMB106BCNC.rim.net>
References: <CA+9kkMA4JGWULm37tfLfDLN1y47wx7bYC4ciqdkLrtAnVW1d5Q@mail.gmail.com>
In-Reply-To: <CA+9kkMA4JGWULm37tfLfDLN1y47wx7bYC4ciqdkLrtAnVW1d5Q@mail.gmail.com>
Accept-Language: fr-FR, en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.160.249]
Content-Type: multipart/alternative; boundary="_000_92D0D52F3A63344CA478CF12DB0648AA2655AD06XMB106BCNCrimne_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFKsWRmVeSWpSXmKPExsXC5bjwtK73i6RAg4dnNC3W/mtnt2ica+fA 5LFz1l12jyVLfjIFMEU1MNokJZaUBWem5+nb2STm5eWXJJakKqSkFifbKvmkpifmKAQUZZYl JlcquGQWJ+ckZuamFikpZKbYKpkoKRTkJCan5qbmldgqJRYUpOalKNlxKWAAG6CyzDyF1Lzk /JTMvHRbJc9gf10LC1NLXUMlO92ETp6MHe+fMRe8XcJY0XfmAnsD48HpjF2MnBwSAiYSC1+8 Z4OwxSQu3FsPZHNxCAmsZJRoeNAO5WxilJh58Dc7SBWbgKXE/1d7WEBsEQEPiU1/f7OC2MIC QRJPDt9lhIgHS/x92glVYySx8fIZZhCbRUBFYvWzO0A2BwevgKfE/LVqIGEhgQCJ97vuMYHY nAKBEq9272EHKWEEKj/5NBwkzCwgLnHryXwmiDsFJJbsOc8MYYtKvHz8jxXCVpTY++woE0R9 vsSOP3PBLuAVEJQ4OfMJywRGkVlIRs1CUjYLSRlEXE/ixtQpbBC2tsSyha+ZIWxdiRn/DrEg iy9gZF/FKJibUWxgZpCcl6xXlJmrl5dasokRnD409Hcwvn1vcYhRgINRiYdX53JSoBBrYllx Ze4hRgkOZiUR3tazQCHelMTKqtSi/Pii0pzU4kOMQcCwmsgsxZ2cD0xteSXxxgYGRHKUxHl/ C0cHCgmkAxNZdmpqQWoRzFAmDk6QpVxSIsXAdJRalFhakhEPSprxxcC0KdXAeNhNZPes8zGb ft2/aHP67KZFs7atnaL38qbEwTMb5ibJtFvYXhAxXXb8eMDE8oMO/Quf6FxL28lUeXxas3rx 6+/a+Z8s75dq350btJ6zcMbR29sLG7+tntXq69fLcGB+oWBC8xKF82nbZiVtKXvINUf0lNCH Rl/p6Qo7NJ5mfqjfxdv+Oyfwba4SS3FGoqEWc1FxIgAi82g1bQMAAA==
Subject: Re: [rtcweb] Uploaded unified minutes for both days of IETF 86 meetings
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: Mon, 08 Apr 2013 16:10:36 -0000

Dear all,

Some corrections made by Magnus and sent to the list on April 2nd were lost; page 3 the first changes under the VP8 IPR presentation should read:
VP8 IPR: http<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>://<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>www<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>ietf<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>org<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>proceedings<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>/86/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>-86-<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>rtcweb<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>-10.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>pdf<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-10.pdf>
Serge Lachapelle presenting

Gaelle reiterated that more details are needed on the recent announcement and noted that there are more patent holders for H.264 in the ITU-T database that are not part of MPEG-LA.  She asked if the IETF could send letters to solicit information from these IPR-holders.


Also, please see below some corrections/clarifications:
In the same section:
The MPEG-LA pool is a subset.  She re-iterated her view that in light of the answers provided by the area directors, the IETF is not the place for clarifying this.

In the section:
Mandatory to Implement Video Codec discussion
VP8 Technical: http<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>://<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>www<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>ietf<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>org<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>proceedings<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>/86/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>-86-<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>rtcweb<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>-9.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>pdf<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-9.pdf>
Harald Alvestrand presenting
....
Gaelle then spoke, saying that in light of the inaccuracy of the tests and related data the venue is wrong, that  MPEG is the right place to perform those tests and IETF should rely on MPEG results before making a decision.  She wants to be sure that the tests are accurate, and that the test set and methodology used in IETF are problematic.

In the last section:
It was clearly indicated that additional questions should not be the one that were already asked during the meeting or sent on the reflector. (Some of these are still pending answers).

Sense of the room query: http<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>://<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>www<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>ietf<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>org<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>proceedings<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>/86/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>/<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>slides<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>-86-<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>rtcweb<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>-14.<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>pd<http://www.ietf.org/proceedings/86/slides/slides-86-rtcweb-14.pd>f
Robert Sparks (as a favor to the chairs)

The questions to be asked were put on the slides.  If you can't answer these question, think about what you really need.  Come articulate at the mic after the questions, issues or questions that have not already being posted on the reflector or that have not been raised during the meeting.

Thank you
Sincerely,
Gaëlle


From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ted Hardie
Sent: Friday, April 05, 2013 4:29 PM
To: rtcweb@ietf.org
Subject: [rtcweb] Uploaded unified minutes for both days of IETF 86 meetings

Howdy,

We have now uploaded unified minutes with the corrections we received on the list; thanks to all who reviewed.  If you have not yet done so, there is still time to update, so please take a look.

thanks,

Ted Hardie, for the chairs.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.