[Unwanted-trackers] IAB Review of dult charter

Mirja Kuehlewind <ietf@kuehlewind.net> Wed, 07 February 2024 15:17 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: unwanted-trackers@ietfa.amsl.com
Delivered-To: unwanted-trackers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A9C8C151717; Wed, 7 Feb 2024 07:17:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level:
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYAYKdEliA9Z; Wed, 7 Feb 2024 07:17:29 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7DEFC14F708; Wed, 7 Feb 2024 07:17:29 -0800 (PST)
Received: from dslb-002-207-003-157.002.207.pools.vodafone-ip.de ([2.207.3.157] helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rXjg0-0004cp-4p; Wed, 07 Feb 2024 16:17:28 +0100
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5882657B-EED7-47FD-B651-A2B6E7449038"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <69466858-C759-4805-8051-8EFE0C04533F@kuehlewind.net>
Date: Wed, 07 Feb 2024 16:17:17 +0100
Cc: IAB <iab@ietf.org>
To: The IESG <iesg@ietf.org>, unwanted-trackers@ietf.org
X-Mailer: Apple Mail (2.3731.700.6)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1707319049;60e8736e;
X-HE-SMSGID: 1rXjg0-0004cp-4p
Archived-At: <https://mailarchive.ietf.org/arch/msg/unwanted-trackers/8alpwWykKlWK03fBLmXlOiZSdYw>
Subject: [Unwanted-trackers] IAB Review of dult charter
X-BeenThere: unwanted-trackers@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on detecting unwanted location trackers <unwanted-trackers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unwanted-trackers>, <mailto:unwanted-trackers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unwanted-trackers/>
List-Post: <mailto:unwanted-trackers@ietf.org>
List-Help: <mailto:unwanted-trackers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unwanted-trackers>, <mailto:unwanted-trackers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Feb 2024 15:17:34 -0000

Hi all,

as part of the IAB’s role in reviewing new WG charters, I reviewed the dult charter. The IAB maintains a list of high level topics to consider for review (https://wiki.ietf.org/en/group/iab/IAB_Review_of_Proposed_WG_Charters) covering Internet health, deployment incentives, security & privacy, protocol evolution, and the broader ecosystem. This review reflects my own assessment of these topics and not a consensus view of the IAB.

The dult work aims to increase privacy for user (or non-users) of already deployed tacking devices. The charter covers security and privacy aspects appropriately. Given the group is addressing an existing and important problem, this is is also important for the Internet health. The proposed solution is enabling an open ecosystem and provides guidance and incentive to act responsibly. The proposed work does not fully address deployment incentives, however, it does include guidance that aims to deter malicious use.

The charter does not discuss protocol extensibility or use of existing protocols or protocol mechanism. While this is not discussed explicitly, there is noting in the charter that would lead to the conclusion that this would not be considered appropriately in the working group process.

The scope of work is slightly boarder than other groups in the IETF, however, this topic is important and there is already a large community with interest and the right expertise in the IETF (incl. input from a boarder community during the BoFs and the charter discussion, which is curial for this work and great to see that the IETF can provide such a fora).

Thanks everybody for working on the charter! Based on my review I don’t see any concern to move forward with this work.

Mirja