IETF Logo Mail Archive

Re: Next W3C/IETF call scheduling

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 18 February 2013 00:38 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECD921F8B48 for <w3c-policy@ietfa.amsl.com>; Sun, 17 Feb 2013 16:38:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kmdxaaH9rGpn for <w3c-policy@ietfa.amsl.com>; Sun, 17 Feb 2013 16:38:37 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D6B9821F8B46 for <w3c-policy@ietf.org>; Sun, 17 Feb 2013 16:38:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 39323BE47; Mon, 18 Feb 2013 00:38:15 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Kihrn3LOH+O; Mon, 18 Feb 2013 00:38:14 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.44.73.97]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 48C3FBE38; Mon, 18 Feb 2013 00:38:14 +0000 (GMT)
Message-ID: <512177F4.2060804@cs.tcd.ie>
Date: Mon, 18 Feb 2013 00:38:12 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Philippe Le Hegaret <plh@w3.org>
Subject: Re: Next W3C/IETF call scheduling
References: <1360966338.1769.94.camel@chacal>
In-Reply-To: <1360966338.1769.94.camel@chacal>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 00:38:37 -0000

Hiya,

On 02/15/2013 10:12 PM, Philippe Le Hegaret wrote:
> IETF 86 is approaching and Thomas and I have a list of items (json bof,
> ipr, http auth, video codec, media types).

On agenda - could we add drm or whatever is the term-de-jour? I'm
wondering what's up in w3c there given recent reports related I
guess to [1].

I'm not so much interested in commenting on developments, more
in understanding what and perhaps why. If its possible and makes
sense I'd also be interested in any views as to how that might
be similar to or different from DNT.

But if folks think that inappropriate or impractical for a call,
I'm fine with constraining the topic or trying to chat about
it in Orlando if the right people will be there, or whatever
else makes sense.

Ta,
S.

[1]
https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html

v2.23.0 | Report a Bug | By Email