Re: [secdir] [new-work] Proposed W3C Charters: Web Application Security Working Group, and XML Security Working Group (until 2013-10-21)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 23 September 2013 13:26 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB25421F9FB6 for <secdir@ietfa.amsl.com>; Mon, 23 Sep 2013 06:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.876
X-Spam-Level:
X-Spam-Status: No, score=-102.876 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LBgmhuUr83Pt for <secdir@ietfa.amsl.com>; Mon, 23 Sep 2013 06:26:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id BC08221F9E9F for <secdir@ietf.org>; Mon, 23 Sep 2013 06:26:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7DD7CBE20; Mon, 23 Sep 2013 14:26:22 +0100 (IST)
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 uq-fKPD7z5tU; Mon, 23 Sep 2013 14:26:22 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5DF3EBDCA; Mon, 23 Sep 2013 14:26:22 +0100 (IST)
Message-ID: <5240417E.4040508@cs.tcd.ie>
Date: Mon, 23 Sep 2013 14:26:22 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: "secdir@ietf.org" <secdir@ietf.org>
References: <op.w3u2nbycsvvqwp@sith.local>
In-Reply-To: <op.w3u2nbycsvvqwp@sith.local>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Coralie Mercier <coralie@w3.org>
Subject: Re: [secdir] [new-work] Proposed W3C Charters: Web Application Security Working Group, and XML Security Working Group (until 2013-10-21)
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 13:26:29 -0000

I wasn't sure what was changing here so I asked, and Coralie
helpfully answered:

"The XML Security group has completed its Recommendations and
is re-chartered for maintenance only.

WebAppSec adds deliverables: an extended version of the Content
Security Policy specification, already in progress, and new
Recommendations on Secure Mixed Content and Lighweight
Isolated / Safe Content."

Cheers,
S.

On 09/23/2013 12:10 PM, Coralie Mercier wrote:
> 
> Hello,
> 
> Today W3C Advisory Committee Representatives received a Proposal to
> revise the Security Activity [0] (see the W3C Process
> Document description of Activity Proposals [1]). This proposal includes
> a draft charter for the  Web Application Security Working Group and the
> XML Security Working Group:
>   http://www.w3.org/2013/07/webappsec-charter.html
>   http://www.w3.org/2013/02/xmlsec-charter.html
> 
> As part of ensuring that the community is aware of proposed work at W3C,
> this draft charter is public during the Advisory
> Committee review period.
> 
> W3C invites public comments through 2013-10-21 on the proposed charter.
> Please send comments to public-new-work@w3.org, which has a public archive:
>   http://lists.w3.org/Archives/Public/public-new-work/
> 
> Other than comments sent in formal responses by W3C Advisory Committee
> Representatives, W3C cannot guarantee a response to comments. If you
> work for a W3C Member [2], please coordinate your comments with your
> Advisory Committee Representative. For example, you may wish to make
> public comments via this list and have your Advisory Committee
> Representative refer to it from his or her formal review comments.
> 
> If you should have any questions or need further information, please
> contact Wendy Seltzer, Team contact <wseltzer@w3.org>.
> 
> Thank you,
> 
> Coralie Mercier, W3C Communications
> 
> [0] https://www.w3.org/Security/
> [1] http://www.w3.org/2005/10/Process-20051014/activities#ActivityCreation
> [2] http://www.w3.org/Consortium/Member/List
>