[Atp] Re: Temperature Check on Charter Scoping

Willem Dantuma <willem.dantuma@dobs.nl> Wed, 26 November 2025 14:05 UTC

Return-Path: <willem@dobs.nl>
X-Original-To: atp@mail2.ietf.org
Delivered-To: atp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 854AB9113CBC for <atp@mail2.ietf.org>; Wed, 26 Nov 2025 06:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=dobs-nl.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71n9OSEpqSBD for <atp@mail2.ietf.org>; Wed, 26 Nov 2025 06:05:05 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5A8E49113913 for <atp@ietf.org>; Wed, 26 Nov 2025 06:02:58 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-640b0639dabso11699116a12.3 for <atp@ietf.org>; Wed, 26 Nov 2025 06:02:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dobs-nl.20230601.gappssmtp.com; s=20230601; t=1764165777; x=1764770577; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3jNpKe2EpzE91vWPhwU2dBv+CaUDnjw88ifa4axbwM4=; b=ezXHs06KQchiId6eUtwsXEZCBKSOKoWE9YiPoPfV+LMLU3wFjLT/cOfaNcAe7hmgOD 8W1cH/lhlgX2QRARzmxDyHx4XonrHPIgbfR3nsqKTAJlXgRa+59ee1QK/n8w6BKREkl0 WnPlxS4l2lsRlF+1NqKuVXbUM0h9aTmllz1I6A1Bxqe1/aMM0eYs/QftwNJneZ0E4g8u ZxZRKRXK4WC/3y70RVvr26dRaPVPnkr5AgclUkUE9JqDXo4n1wfpQA/YmlwpM/59ZXFR LfG9T0+VhPsoLKmInzci95KD70waC23E172Vc8X73BpJDhRX2JOT0Obce6/IkRDy6xc/ ywkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764165777; x=1764770577; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3jNpKe2EpzE91vWPhwU2dBv+CaUDnjw88ifa4axbwM4=; b=supKKNx4iykX8ump5KQ9UqVN3Pnbt71jwcOup4JSrOESVYfce9sgLnA8C5Y4X0cTl8 YRffS+OotOZ+h3gMLJNinyC+eYhQwXthyzZ0sqQCY8uApJNMqXyv5F145si9NxeWXBVM QMT69tZbA59mxDxrtyhcEqfV3JbknCHzq7bnEHk9gFysMMUlC8ob6cI4Lt4ajiMQty5S H0Xhp0MzO43hHhj0jouXiEdJ2ptntpAs1Q/OfcAruBMuuoIxPuziJvHnjRXVRoKxpqgV 1K47om65xkZoOhUgE9PHHW9FPyUSAKd9HCZwwgDpuYcDzH1oJi/gSsmA/ow2a5xUQCZC KCzQ==
X-Gm-Message-State: AOJu0YwzkeyJoDzpivR73pHC3L6rYzse9deeck+yu8qs8qBNVzBmDHSb LAbDpY6rBoxYv9nMvYp17umu2xzxeAjBX6dKSK/JD5riNpqk63UOPxeQb28IgZN68RtKnqhJGui 1WMknpo5efnSJYFQf9dY8fUvnNzSkC4+JpdD+bFSBFw==
X-Gm-Gg: ASbGncsQoJegE/atT1pAt246mcFAQfbQrvhygJ0kpLw10d7n9eU6EOzwypiixut5IfM lNaiaS9I2R9k+P6trP3zBQsLzmMsMfnJn2dimDVvDlN9QaX8+kPCshfM9jGa+h/oedKB70PDrjV S1bmXe8+VXro1X+Io+7eG9lQzfsDFh9PY++xpiLLAW9lEWO6ux/NNM+w9MdgBi+i7+0f5TKE4Hx PkDa+sF37GVEmoKPAiBh1zFU/qPljsvH2aqdV01H+sb+TVlX9QN2aDWW32RuO+3w2bm4vXpgxfx 9W4RlbVImhZH5+LGZ81a6FRl44qpZe1zZW3n
X-Google-Smtp-Source: AGHT+IFPz2YA8XZXwSbPzajgk/L4qepsFKysHrIyTnmk/UuW2kaRyigMpJcSo+7OttT1mJYnyn7x3A6H/05LrnhSmiI=
X-Received: by 2002:a05:6402:518a:b0:643:d1b:41d9 with SMTP id 4fb4d7f45d1cf-64554674b58mr18791531a12.17.1764165777332; Wed, 26 Nov 2025 06:02:57 -0800 (PST)
MIME-Version: 1.0
References: <CABFYohjpJqRooHQf0VEUmWq5RTFwO8JOtmgf2UT02Q1ED2UprQ@mail.gmail.com>
In-Reply-To: <CABFYohjpJqRooHQf0VEUmWq5RTFwO8JOtmgf2UT02Q1ED2UprQ@mail.gmail.com>
From: Willem Dantuma <willem.dantuma@dobs.nl>
Date: Wed, 26 Nov 2025 15:02:46 +0100
X-Gm-Features: AWmQ_bmpAdkJgH1gFFWTSYjH549x_YgUV22mNUQAfmLh0EDPdke3DKAiJLYNu2U
Message-ID: <CACOhus5R+YENOF5bP0XMX73rpVcbfxLZhgHEdyjYzriP516=tw@mail.gmail.com>
To: Bryan Newbold <bryan=40blueskyweb.xyz@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007bab9406447fda5b"
Message-ID-Hash: CG2XOMVCQZGKRV2RBMIYC7J3WE2UUJC2
X-Message-ID-Hash: CG2XOMVCQZGKRV2RBMIYC7J3WE2UUJC2
X-MailFrom: willem@dobs.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: atp@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Atp] Re: Temperature Check on Charter Scoping
List-Id: Authenticated Transfer <atp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/atp/5kLTkbmAZGenEIEbGA3-nSYNhus>
List-Archive: <https://mailarchive.ietf.org/arch/browse/atp>
List-Help: <mailto:atp-request@ietf.org?subject=help>
List-Owner: <mailto:atp-owner@ietf.org>
List-Post: <mailto:atp@ietf.org>
List-Subscribe: <mailto:atp-join@ietf.org>
List-Unsubscribe: <mailto:atp-leave@ietf.org>

I think the second strongest driver for the use of ATproto next to the
protocol itself is the use of did:plc. So standardizing the protocol
without defining a small! set of blessed did's would give us a false start.

In the draft charter text the URI scheme is already put in scope  ( so we
probably already conforming to did as the identifier scheme ?),  From an
implementer viewpoint I prefer the set of (did) methods I need to implement
should be as limited as possible.

If the blessed methods should be covered by a separate charter/WG is open
for discussion.


Willem

Op wo 26 nov 2025 om 02:19 schreef Bryan Newbold <bryan=
40blueskyweb.xyz@dmarc.ietf.org>:

> Hi folks,
>
> Right around the BoF there were a few discussions around charter scope,
> and since then there has been a detailed thread about the interface to
> identity systems. Beyond that there has not been as much debate about scope.
>
> I want to try and get a temperature check as to whether this means folks
> are broadly satisfied with the proposed scope and draft charter, or if the
> identity question is singular enough that we need to hash that out before
> considering other dimensions.
>
> If you have other thoughts please chime in! In particular these can be at
> an abstract level ("what should folks be able to accomplish with the output
> of the WG"), or a bit lower level ("really seems like part A can't be
> specified without piece B").
>
> We are hoping to starting converging on a more firm charter proposal in
> the next couple weeks. Some folks may be traveling this week (smooth
> travels if that is you), so I may poke again next week.
>
> --bryan
> _______________________________________________
> Atp mailing list -- atp@ietf.org
> To unsubscribe send an email to atp-leave@ietf.org
>