Return-Path: 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 1069930F429A for ; Wed, 4 Jun 2025 12:05:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.893 X-Spam-Level: X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, 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 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 vVRJ5ZwLXPNl for ; Wed, 4 Jun 2025 12:05:04 -0700 (PDT) Received: from mail-qv1-f41.google.com (mail-qv1-f41.google.com [209.85.219.41]) (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 627D330F4292 for ; Wed, 4 Jun 2025 12:05:04 -0700 (PDT) Received: by mail-qv1-f41.google.com with SMTP id 6a1803df08f44-6faf6e1378dso3096756d6.1 for ; Wed, 04 Jun 2025 12:05:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749063904; x=1749668704; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Oyu1qIUlpgWacySzNGOJiG/nHV6qtI6fRqeX9QBsIks=; b=VTnqYW1nDUo7GRqbqVlMRayq4FhYFqqlYYB1z6i/oirX/JcN6yLKL8HoGLNwJ1H9lP s5iJKTIKLaFsOnmzCOzdAzwxssq0154TM+EeAImTFW1dysT8qAyUMg2yiFDkiTZyWdAt OWu60HjOglWuX3iPo0obTsowt2315oVW16v8kBN+g44KC56hIrXg18TxWx9gojV2o284 MErJ+Y3PiMmAboHQUECYQFvm36fkoZLT7vORHu2ObrPYj9H4VbKKmtHYRkCYB55RIoVk Xq9QUENRjF3X8pO2JX00zn2FXwL64juF2xERDLkaUQDYlbD5O8iXjHJ3oNpLPxg+QI8r G0CQ== X-Gm-Message-State: AOJu0Yx067EeNQ7vxWqIhUZQaZX3+CQNHvy0Ba92DbHklwfWe+Bmw0Tu CGXAZt/b/KXuqOXW5cFLlvsp2L4pxWKoGG3xBdzLxhv5Snmx5YeRmdO2O3u362z4zO4lVI3i+Rr isOoViiXNsu9K29AkBGut3a8ULcQtZuagFx4J X-Gm-Gg: ASbGnctgEng51wAUBrK8FXFqoSH9i76B2by6K1Sl5Sw2DD4ttRTmo5WTAgVRWnZe6zl Z8QZWRzfWTAN3lEJXpDS/ZP/bvZnVKGKghvVlXyvfZedDQA44oSEaiPnz3htV2gjU9jVNy/LaPw cK/lndfGbXWco7YOQkMxxS5QMTumXrcpBM6g== X-Google-Smtp-Source: AGHT+IFA3bUZkYHm/BeFlKKqgKb4k3+eLEgrUm/vCjhi+ya7bkCuJyGDjTRlcwlreS8OYq9Qt+L+i+C7CAR9lirRK/M= X-Received: by 2002:a05:6214:e87:b0:6f5:3ffc:5ae7 with SMTP id 6a1803df08f44-6faf745e456mr63970516d6.19.1749063903731; Wed, 04 Jun 2025 12:05:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Phillip Hallam-Baker Date: Wed, 4 Jun 2025 15:04:52 -0400 X-Gm-Features: AX0GCFvez6dwHLxmBbI6hv6ym5Qgx16pi8QwVT79KjSK-lohCF5gm2MLshIJVsA Message-ID: Subject: Re: Names on blue sheets To: Rob Sayre Content-Type: multipart/alternative; boundary="000000000000abe7c80636c3ac02" Message-ID-Hash: IZTIA3B5Y3H37KZQETNLMWIW5NP654QZ X-Message-ID-Hash: IZTIA3B5Y3H37KZQETNLMWIW5NP654QZ X-MailFrom: hallam@gmail.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 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." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000abe7c80636c3ac02 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hmm... Started reading this thread, looked at the entry in the Data Tracker for the draft and though 'Bet Flo D. is Flo Driscoll and Michael P. Is Michael Parsons'. Then went to the draft and found I was right because they have both given their full names there. Yes, there are some folk who participate in IETF under an alias and some folk who have interesting personal security concerns. But this isn't one of them. On Tue, Apr 15, 2025 at 8:01=E2=80=AFPM Rob Sayre wrote: > Hi, > > Jennifer Richards 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 the= y > write their full name? > > thanks, > Rob > > > --000000000000abe7c80636c3ac02 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hmm= ... Started reading this thread, looked at the entry in the Data Tracker fo= r the draft and though 'Bet Flo D. is Flo Driscoll and Michael P. Is Mi= chael Parsons'.

Then = went to the draft and found I was right because they have both given their = full=C2=A0names there.

Ye= s, there are some folk who participate in IETF under an alias and some folk= who have interesting personal security concerns. But this isn't one of= them.


On Tue, Apr 15, 2025 at 8:01=E2=80=AFPM Rob Sayre <sayrer@gmail.com> wrote:
Hi,
Jennifer Richards <jennifer@staff.ietf.org> wrote:
> B= ecause that is the name of the Person record in the Datatracker:
><= br>> https://datatracker.ietf.org/person/Michael%20P

Is there a special policy for British=C2=A0government employees? Wh= y can't they write their full name?

thanks,
Rob


--000000000000abe7c80636c3ac02--