IETF Logo Mail Archive

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

Ted Hardie <ted.ietf@gmail.com> Mon, 08 April 2013 17:24 UTC

Return-Path: <ted.ietf@gmail.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 52FC421F8678 for <rtcweb@ietfa.amsl.com>; Mon, 8 Apr 2013 10:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 fErpf5brc7up for <rtcweb@ietfa.amsl.com>; Mon, 8 Apr 2013 10:24:14 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id C68EA21F861B for <rtcweb@ietf.org>; Mon, 8 Apr 2013 10:24:11 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id qd14so7402851ieb.28 for <rtcweb@ietf.org>; Mon, 08 Apr 2013 10:24:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Bk3oxiXg+2esjNFqOifNl5J4/we4jOApQa7V2NcL1ng=; b=QVIA/ZyV2l1qZ4tqOltv+iv79UpWDmm9LQAG64rm/qhLdva3HNlWclqYzqo0FQcLkA 0nJj9nuZWOSCaGjJhc7zsTcG5os7kgI4gJbRRZFIEQ9UyZg4JTrPC21WYMbbzcbX+QX8 Ey9a0oemXSnNaktt4Y0Hu3S1zhd1tjZQqzMDXMvAIre5jViEZ7atymGRUbmf7k6RPp06 TRU2nIBMu+arspP802haroQWkMkUOgGUJmu21jSOYEMQGKF+8rPbjsuC6A/WdZVKXq6x 7DjILYikYqTiGcOSpgyrtY89Q8t37rmlqVyAD+E0LFlCl+/DRmT7LVPXGoHoeYXDIGbi 1Bow==
MIME-Version: 1.0
X-Received: by 10.50.36.169 with SMTP id r9mr7595562igj.96.1365441845158; Mon, 08 Apr 2013 10:24:05 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Mon, 8 Apr 2013 10:24:05 -0700 (PDT)
In-Reply-To: <92D0D52F3A63344CA478CF12DB0648AA2655AD06@XMB106BCNC.rim.net>
References: <CA+9kkMA4JGWULm37tfLfDLN1y47wx7bYC4ciqdkLrtAnVW1d5Q@mail.gmail.com> <92D0D52F3A63344CA478CF12DB0648AA2655AD06@XMB106BCNC.rim.net>
Date: Mon, 08 Apr 2013 10:24:05 -0700
Message-ID: <CA+9kkMDp+P7ts8zgdLPaFw5LbL+uUxKWieS-4ZwNKrGmMBm5LQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Gaelle Martin-Cocher <gmartincocher@blackberry.com>
Content-Type: multipart/alternative; boundary="14dae934032b247afa04d9dcb488"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 17:24:16 -0000

Thanks for pointing these out; they'll get fixed in the next update.

Ted

On Mon, Apr 8, 2013 at 8:54 AM, Gaelle Martin-Cocher <
gmartincocher@blackberry.com> wrote:

>  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.
>

v2.23.0 | Report a Bug | By Email