[saag] W3C Update for IETF112

Samuel Weiler <weiler@w3.org> Thu, 11 November 2021 16:07 UTC

Return-Path: <weiler@w3.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3441B3A0AD1 for <saag@ietfa.amsl.com>; Thu, 11 Nov 2021 08:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tB9GIkp2fut5 for <saag@ietfa.amsl.com>; Thu, 11 Nov 2021 08:07:37 -0800 (PST)
Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by ietfa.amsl.com (Postfix) with ESMTP id BAD133A0AB5 for <saag@ietf.org>; Thu, 11 Nov 2021 08:07:37 -0800 (PST)
Received: from sams-2020-air (unknown [73.238.229.70]) by cyrus.watson.org (Postfix) with ESMTPSA id 78A629139B for <saag@ietf.org>; Thu, 11 Nov 2021 16:07:36 +0000 (UTC)
Date: Thu, 11 Nov 2021 11:07:36 -0500 (EST)
From: Samuel Weiler <weiler@w3.org>
To: Security Area Advisory Group <saag@ietf.org>
Message-ID: <2361e57b-59b6-56a6-3e1-d9c03a222fc@watson.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/_20PU80TuBD4pg6kIuNrcHlM46A>
Subject: [saag] W3C Update for IETF112
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2021 16:07:40 -0000

W3C has several new Community Groups (CGs) which are open to all - no 
W3C membership needed.

Two are focused on problems that are made more challenging by the 
demise of 3rd party cookies:

Federated Identity Community Group
https://www.w3.org/community/fed-id/

Anti Fraud Community Group
https://www.w3.org/community/antifraud/
Minutes of breakout meeting (think "BOF"): 
https://github.com/WICG/trust-token-api/blob/main/meetings/tpac2021-antifraud-breakout.md

We also have a new Private Advertising Technology Community Group 
looking at technologies that support advertising while acting in the 
interests of users, using technical - not legal or policy - 
mechanisms to provide strong privacy assurances.
https://www.w3.org/community/patcg/
Minutes of first meeting:
https://www.w3.org/2021/10/29-patcg-minutes.html

And we have a Privacy Community Group working on storage partitioning 
and similar broader privacy measures:
https://www.w3.org/community/privacycg/
(n.b. some work is migrating from this group to the new Private 
Advertising Technology CG)

As above, all of these are open to the entire community, with no W3C 
membership needed.

The Web Applications Security WG (WebAppSec) continues to make 
progress on site isolation primitives such as COEP and COOP.
https://www.w3.org/2011/webappsec/

I am also looking for additional security reviewers for W3C specs, 
similar to the work done by the IETF's SecDir.  If you would like to 
occasionally review a spec, please send me a note.

-- Sam