Re: Names on blue sheets
S Moonesamy <sm+ietf@elandsys.com> Thu, 17 April 2025 09:34 UTC
Return-Path: <sm@elandsys.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 B83041D8A3C8 for <ietf@mail2.ietf.org>; Thu, 17 Apr 2025 02:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FUZZY_CPILL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 LZq7Y28QJZtI for <ietf@mail2.ietf.org>; Thu, 17 Apr 2025 02:34:39 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 5E6971D8A3AD for <ietf@ietf.org>; Thu, 17 Apr 2025 02:34:38 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.155.132]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 53H9XqdY007336 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2025 02:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1744882464; x=1744968864; i=@elandsys.com; bh=PBbgLMAXQ/ot0Cfp0JksBnAPN5CJqT0UaSCV+3rvaw8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=45rwFZr5iMz+ZU3/D0VLWT8LGWRIG7QLPdrx2lvgexNBuorXd7ODOd+Z1VmSiqQXi khBjbNjYmwDNtTxsljopeagrNH9X8+8vOooOYK8km+MiX30CACI8yS/c2wrkbbv6zC Xs44XIgeNuPMd6bTfyNuztGBvyMIWTl4RpBWJ4FA=
Message-Id: <6.2.5.6.2.20250416224634.0ad35e48@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Apr 2025 02:32:42 -0700
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Names on blue sheets
In-Reply-To: <1787102263.36701.1744804996864@appsuite.open-xchange.com>
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> <1787102263.36701.1744804996864@appsuite.open-xchange.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: HQKDNPTPZEZ2EC37N7ZBKEDD3QTD6IDA
X-Message-ID-Hash: HQKDNPTPZEZ2EC37N7ZBKEDD3QTD6IDA
X-MailFrom: sm@elandsys.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
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/d4iduJuQzwOGB_YZbOoZjrhUCzg>
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>
Hi Vittorio, At 05:03 AM 16-04-2025, Vittorio Bertola wrote: > > 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. There are a few persons on this mailing list who noticed that attendees affiliated with the National Cyber Security Centre, United Kingdom, hide their last name. Eric Vyncke posted a message at https://mailarchive.ietf.org/arch/msg/ietf/ZXK1aL1zOJaYh8OkxDTxqS8O4Lg It showed that the last name was visible. The "hide my name" approach does not seem very effective if the attendee doing that authors an Internet-Draft. I took a quick look into the "hide my name". It seems like it was a trend over the past five years to maintain some level of anonymity. Some people may have valid reasons to do that. A few IETF participants may be wary to see that happening within the standards process due to some past revelations pertaining to cryptography. The meetings are generally described as public meetings. The records of public meetings are generally published. It would be inconsistent for the community to claim that it is transparent if it does not make those records accessible to the general public. Regards, S. Moonesamy
- 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