IETF Logo Mail Archive

Re: Names on blue sheets

Jay Daley <exec-director@ietf.org> Wed, 16 April 2025 00:10 UTC

Return-Path: <jay@staff.ietf.org>
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 5A72B1CA3C77 for <ietf@mail2.ietf.org>; Tue, 15 Apr 2025 17:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=staff-ietf-org.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 uk0lMXDsG9Zw for <ietf@mail2.ietf.org>; Tue, 15 Apr 2025 17:10:10 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 1C0BB1CA3C72 for <ietf@ietf.org>; Tue, 15 Apr 2025 17:10:10 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-879d2e419b9so5210360a12.2 for <ietf@ietf.org>; Tue, 15 Apr 2025 17:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1744762209; x=1745367009; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=HwqwrL2SfMDWGO8AuUCwNJfw4+njfdVlnCpnjVfzErE=; b=Bj+mIn+tnIG/1yZf1m0CBAgmGrIMpaztK8PevObwrgtDZXGi+QUocIat/dFpRX+++N p1z2VSct2wBf721D5g5mYVergynpbiBJkwdFY9+gWUmYs7H8BOsv+6YoRjghmbPr+qYi lurhepSztRcTuOOVbnGh2v80lPrYvTC+Q8nVYgBYR03NVSxOJZ5fmNimTxg3roSi5Ad9 mj2iRnLTJajsFp0cGRy3mTAyhef/mL5/hUdzBHNMLyIMifzXGnwx9J5Tjdkp0pzxXJOe Z7oKj4FyAiMtIdSQFhDrHOZuPAFGXe7FIvpNngsfdWH+13S6PscoIjRJGK5bKUPCURd0 6ecg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744762209; x=1745367009; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HwqwrL2SfMDWGO8AuUCwNJfw4+njfdVlnCpnjVfzErE=; b=TmUKM+aBo3MD1WO17VyEPZiwAc3vhm/fYwFPvFkKv9KUrl+F5YLaD80zwRcAwE0jIm 9/vwK1uil/eMMXoFAqGValHAB+eFqjMaf6g2ZNwW70m+m283rY0CUHc/QP8hd0wajA2r Cl5igWXkHRvPyYDzdmRyVL0MA2qwN74v0x3DsWeT27xA+rH/QQdq5gvQvSHz4aPKbf/a 8aByw+Q/rePG4A3gxiUEDfrz+pSJlZk3zIjPSrG6twuvwimt6xqWuIOYKAwW7CFciwcG IrAvdm9ZSaaJfkpBTtKL9HAhLp0ZJWQensp7QzYZIcUTrNVg8Db2oTFcVri3e4pk5V1P UK2w==
X-Gm-Message-State: AOJu0YwlLINSSXaYbiGumHFnK2QhdZyEXG9/HxUSj0mTNCN/fmeXxuW0 kkCAX8IIl1ChuFPF+u94H0nE1wNu5GNmubTrRj4xKk2tsAgOgo3bvDNAMd5Jqgs7PA==
X-Gm-Gg: ASbGnctlqTfA5fQrV+6KIir2NsGpLdMnneFANSm+/mE2chMCePFJihgQtJRin4L+eJC S2NvB1dTuc5XPwPZJPRk/XlzDw/IIndG6WxZ0WkMXxtDQxKAk82BTwTgqflRPZ0bT4cwEsjRw6o 1ZBk/m0YqnC5NXyzkdsW4jLjAlt3hCVxJ5bwanzsecpHWvBP3VeHxM18GU2AeY5vpewGWloHsxY 4C3CZgbEHtA1U9o5c4Fk2KYd5sxzyX1HFIqmug6/aPZxDFgbQz2ooSpyEBlE/8M/ft4DR0K/mYp vT9Qhx+wxy/yzhJyww3cgDrOFKYkPz/OdICMQI7jbykJdbDPmu6vBeN64RFonomirPamVZUdlIK BHAr3+N6j7CQg/oalRr/enHBBljnDHcp744M=
X-Google-Smtp-Source: AGHT+IFuze/wGA1xvjK4vbFrTKWUEFrRCvHynb58QfOiJHaa833NwZF9kRPvcoKs/Ir1/HNQo1iFvQ==
X-Received: by 2002:a17:90b:3cc6:b0:2ff:4e90:3c55 with SMTP id 98e67ed59e1d1-3085efc54abmr1458719a91.27.1744762209075; Tue, 15 Apr 2025 17:10:09 -0700 (PDT)
Received: from smtpclient.apple (203-96-136-53.dsl-dynamic.connections.net.nz. [203.96.136.53]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-30861212fa6sm213078a91.27.2025.04.15.17.10.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Apr 2025 17:10:08 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Subject: Re: Names on blue sheets
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <CAChr6Sz4ntZpQqLqAzw4+_9zp_EfkGuBKZYLHbgvmukXAGuEcg@mail.gmail.com>
Date: Wed, 16 Apr 2025 12:09:54 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FE6E707-5F01-42B9-9D83-CB60402C8B32@ietf.org>
References: <CAChr6Sz4ntZpQqLqAzw4+_9zp_EfkGuBKZYLHbgvmukXAGuEcg@mail.gmail.com>
To: Rob Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: 2SLVXCTQNGVYHZJAKC46WGWNMO3DU62V
X-Message-ID-Hash: 2SLVXCTQNGVYHZJAKC46WGWNMO3DU62V
X-MailFrom: jay@staff.ietf.org
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/kXOsbn60PkET9C2CvnvB9IVGPtE>
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>

> On 16 Apr 2025, at 11:59, Rob Sayre <sayrer@gmail.com> wrote:
> 
> Hi,
> 
> Jennifer Richards <jennifer@staff.ietf.org> wrote:
> > Because that is the name of the Person record in the Datatracker:
> >
> > https://datatracker.ietf.org/person/Michael%20P
> 
> Is there a special policy for British government employees? Why can't they write their full name?

I don’t know how long this has been going on, but in the context of meetings it has only recently been something that we have acted on.  The revised IETF meeting terms and conditions [1] now require people to give us their real name and separately provide a badge name if they wish to be known as something different.  We use the phrase 'real name' as it conveys what we mean without getting into the complexities of legal names.  As noted on that page, the reason for this is legal compliance with US sanctions laws.

I would need to speak with others (at least lawyers, possibly IESG, possibly the IETF Trust) to see if this same rule is necessary for Datatracker accounts if that account is linked to a contribution.

Jay

[1]  https://www.ietf.org/meeting/terms-and-conditions/

> 
> thanks,
> Rob
> 
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org

v2.39.1 | Report a Bug | By Email | System Status