Re: Names on blue sheets
Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 16 April 2025 12:03 UTC
Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 41AC41CED10C for <ietf@mail2.ietf.org>; Wed, 16 Apr 2025 05:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 BxZvvdXyvEvs for <ietf@mail2.ietf.org>; Wed, 16 Apr 2025 05:03:18 -0700 (PDT)
Received: from mx1.open-xchange.com (alcatraz-dus.open-xchange.com [89.163.165.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B65951CED0F9 for <ietf@ietf.org>; Wed, 16 Apr 2025 05:03:18 -0700 (PDT)
Received: from mx1.open-xchange.com (localhost.localdomain [127.0.0.1]) by mx1.open-xchange.com (Proxmox) with ESMTP id 5ED5EE1464; Wed, 16 Apr 2025 14:03:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= open-xchange.com; h=cc:cc:content-transfer-encoding:content-type :content-type:date:from:from:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=s1dus; bh=ipRYfIFb L772yhaaqLd7lkUWAiQI6Q2+9Lbn3GU136Q=; b=Nz3vdlpy/KHkgVEgxNRDoLOY PEdsmU71edAyAeyytO38cXo+fHv6qO5mpqxpJhKL73I28xCDDxEHlwby1utKJMxh noeXpWUnb4ZDBGBaJpEF3f7olvidKRn8R+GSXxocj3qSm4BLfK9Mg0MkVl9VUNkl nMhPdx4j9hjE2U2iF5at470xqliKFHcHe1++p/bFwBbdZgLV4GVudUpe+6Vnm+BH RLOFmMskewFVEIzOOrSUZCu1Ft5Z2m/bH/ycsf/rEl7d6qA4OhxMRO3UhUt2HF/1 BhvAhyUneJAQygykQ349gVPe8Z8Bdg45dcjzNIR/Eu30oJEzh3uQzOfOHMOKqQ==
Received: from imap.open-xchange.com (unknown [10.120.0.15]) by mx1.open-xchange.com (Proxmox) with ESMTPS id 0E3DAE12CF; Wed, 16 Apr 2025 14:03:16 +0200 (CEST)
Received: from gw1.appsuite.int.oxdus.io ([10.110.1.1]) by imap.open-xchange.com with ESMTPSA id WzKfNoSc/2f50REA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Wed, 16 Apr 2025 14:03:16 +0200
Date: Wed, 16 Apr 2025 14:03:16 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <1787102263.36701.1744804996864@appsuite.open-xchange.com>
In-Reply-To: <9ce72630-4875-4771-803a-5d2472c767ce@cs.tcd.ie>
References: <CAChr6Sz4ntZpQqLqAzw4+_9zp_EfkGuBKZYLHbgvmukXAGuEcg@mail.gmail.com> <9FE6E707-5F01-42B9-9D83-CB60402C8B32@ietf.org> <CAChr6SwgcD+=KZV+DJAvqGNC4yHwo5FhTud7ukZ0DEWFGE4d7w@mail.gmail.com> <9ce72630-4875-4771-803a-5d2472c767ce@cs.tcd.ie>
Subject: Re: Names on blue sheets
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev75
X-Originating-Client: open-xchange-appsuite
Message-ID-Hash: E56RLCY55NOZYLZTVGIHJIX57RLWFFZA
X-Message-ID-Hash: E56RLCY55NOZYLZTVGIHJIX57RLWFFZA
X-MailFrom: vittorio.bertola@open-xchange.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IETF discussion list <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hUz49GcEWm_c6AppSH2Ld2soBG8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
> Il 16/04/2025 09:43 JST Stephen Farrell <stephen.farrell@cs.tcd.ie> ha scritto: > > ISTM it's generally fine to use "Rob S" so long as there's a > way to track back to find a more real-world identity, which > could be via the LLC and payments or whatever, whenever that > is something necessary, e.g. in the case of some IPR dispute. > I don't think the real-world identity needs to be trivially > apparent to readers of the blue-sheets. I agree, and actually, I am not sure that the IETF's policy of forcing people to disclose online in public that they were in a specific meeting is GDPR-compliant. It's fine to record who was in the room and even to require disclosure of full and true identity for that, but IMHO (and IANAL) it is hard to argue that publishing the resulting lists to the general public is strictly necessary to the functioning of the meeting, up to the point that no specific, separate, optional consent is necessary. It would be sufficient to disclose the list to the appropriate parties if problems arise. In any case, the only case I have seen of people not signing with their full name is the UK NCSC employees one, and I have seen them do the same at every conference. I do not know if this is an agency policy and what are the reasons, but perhaps, if lists weren't made public on the web, they would have less need to do so. At the same time, should we introduce a policy that people cannot choose how to name themselves in Datatracker but must use their "true identity" (i.e. the one on their documents), please understand that there are people whose ID card name is not the one they chose to bear in public and this could be a serious problem for them. -- vb.
- Names on blue sheets Rob Sayre
- Re: Names on blue sheets Salz, Rich
- Re: Names on blue sheets Rob Sayre
- Re: Names on blue sheets Ross Finlayson
- Re: Names on blue sheets Salz, Rich
- Re: Names on blue sheets Mark Andrews
- Re: Names on blue sheets S Moonesamy
- Re: Names on blue sheets George Michaelson
- Re: Names on blue sheets Rob Sayre
- Re: Names on blue sheets Rob Sayre
- Re: Names on blue sheets Stephen Farrell
- Re: Names on blue sheets Salz, Rich
- Re: Names on blue sheets Watson Ladd
- Re: Names on blue sheets Michael Richardson
- Re: Names on blue sheets Robert Sparks
- Re: Names on blue sheets Jennifer Richards
- Re: Names on blue sheets Jay Daley
- Re: Names on blue sheets Rob Sayre
- Re: Names on blue sheets Rob Sayre
- Re: Names on blue sheets Eric Vyncke (evyncke)
- Re: Names on blue sheets Vittorio Bertola
- RE: Names on blue sheets Andrew Campling
- Re: Names on blue sheets John Scudder
- Re: Names on blue sheets Jay Daley
- Re: Names on blue sheets S Moonesamy
- Re: Names on blue sheets Phillip Hallam-Baker