Return-Path: <marka@isc.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 687DD1C900AD
	for <ietf@mail2.ietf.org>; Tue, 15 Apr 2025 14:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 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, HTML_MESSAGE=0.001,
	MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001,
	MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_MED=-2.3,
	RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001,
	RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001]
	autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key)
	header.d=isc.org header.b="dci41zUz"; dkim=pass (1024-bit key)
	header.d=isc.org header.b="TP+jaN0K"
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 1kVsNoltaMGm for <ietf@mail2.ietf.org>;
	Tue, 15 Apr 2025 14:17:40 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.2.50])
	(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 7E58F1C900A8
	for <ietf@ietf.org>; Tue, 15 Apr 2025 14:17:40 -0700 (PDT)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.2.31])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest
 SHA256)
	(Client did not present a certificate)
	by mx.pao1.isc.org (Postfix) with ESMTPS id C33F63AB327;
	Tue, 15 Apr 2025 21:17:39 +0000 (UTC)
ARC-Filter: OpenARC Filter v1.0.0 mx.pao1.isc.org C33F63AB327
Authentication-Results: mx.pao1.isc.org; arc=none smtp.remote-ip=149.20.2.31
ARC-Seal: i=1; a=rsa-sha256; d=isc.org; s=ostpay; t=1744751859; cv=none;
 b=oZ8jSyiFFdjwJ1o6EfQ54HPZbHqpZd5CHZLR09KC6wgnVt0+tdGRiz58Vd6I9R2z8//Kt/cZxDMpE0+p/HBgw3j/0mHJqHa1uRftRNXb2KmSjpuNx+iRCu6GgRbKyrMZmWnG0crCLvnCnBbeKauN4XY+c66Ad8CYa9vdKhl5ois=
ARC-Message-Signature: i=1; a=rsa-sha256; d=isc.org; s=ostpay; t=1744751859;
	c=relaxed/relaxed; bh=18ChF87MPRp5QLKanpdEP3Hsbj+GRI/HMJytSi9eUJg=;
	h=DKIM-Signature:DKIM-Signature:From:Mime-Version:Subject:Date:
	 Message-Id:To;
 b=nfyU42qik4aqLH7dETca1puS5WInzGLEfn5yCK3GrN4W3Z45HoZG2oLZxgzV0RwGx/yOsUXOp84qD6EmuyYInxqe973qFIrhaNFeK7qdkBu/xnsR9lLolCCJUNa+BAbT0u4G5I7/PyS9jzcqnqKWG6JjAou/R/3A8rBVpDHndHw=
ARC-Authentication-Results: i=1; mx.pao1.isc.org
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org C33F63AB327
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay;
	t=1744751859; bh=jfUqfJTJzLUUCHE4WCC4upRiCI+5T3rWbpZBlPIyW2g=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To;
	b=dci41zUz1yUlkoISfXNh67fx/Q9LVB/ckjeo5F1gTdGNTENEPuD7JCSKJH8G09uXp
	 qQWYmtiblCLUQ1hV64tpoPQyZLc42oiBBG3gAfr235Yriw6kNG60IEATltZjdXQ/hM
	 ek/V0lv4oapGA/lXXKdhWyIFjR3jyIAS4SPrzRcw=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1])
	by zimbrang.isc.org (Postfix) with ESMTPS id C0824136C288;
	Tue, 15 Apr 2025 21:17:39 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by zimbrang.isc.org (Postfix) with ESMTP id 9E9E9136C295;
	Tue, 15 Apr 2025 21:17:39 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 9E9E9136C295
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org;
	s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1744751859;
	bh=18ChF87MPRp5QLKanpdEP3Hsbj+GRI/HMJytSi9eUJg=;
	h=From:Mime-Version:Date:Message-Id:To;
	b=TP+jaN0Kjdva2twsW5PPuL6XhDCUXPkjE195L4A2mQOkD9yq1IiL67mhSWBALvSBq
	 70l+IsriSqUW9PaZGW7ej8OgvbOEOHxBhVD/oKCR9qznyhlnyqtD2dtrXA9KLRh+P1
	 2TesAcpmKp/K1UidDkBfV6qBeiXys1MbWTqoVU+g=
Received: from zimbrang.isc.org ([127.0.0.1])
 by localhost (zimbrang.isc.org [127.0.0.1]) (amavis, port 10026) with ESMTP
 id zzAkiDTULafS; Tue, 15 Apr 2025 21:17:39 +0000 (UTC)
Received: from smtpclient.apple (n49-187-18-238.bla1.nsw.optusnet.com.au
 [49.187.18.238])
	by zimbrang.isc.org (Postfix) with ESMTPSA id 30449136C288;
	Tue, 15 Apr 2025 21:17:39 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-D312CF00-870B-46E8-A46F-25B8BAE795AD
Content-Transfer-Encoding: 7bit
From: Mark Andrews <marka@isc.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Names on blue sheets
Date: Wed, 16 Apr 2025 07:17:26 +1000
Message-Id: <8B69ABF5-F1A6-4688-A31D-55AE17FCBF9E@isc.org>
References: 
 <CAKr6gn3NJwgMx3DJ8RxuOM3qQiYMu0JZMQMPkFaVwZiCJdWgTA@mail.gmail.com>
In-Reply-To: 
 <CAKr6gn3NJwgMx3DJ8RxuOM3qQiYMu0JZMQMPkFaVwZiCJdWgTA@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: iPhone Mail (22E240)
Message-ID-Hash: H7GUI52KJEG55S4GNHTDNOIRZTAWLRJZ
X-Message-ID-Hash: H7GUI52KJEG55S4GNHTDNOIRZTAWLRJZ
X-MailFrom: marka@isc.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@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/_Lb3SdqmEtiBtJyq72dLMNg98mE>
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>


--Apple-Mail-D312CF00-870B-46E8-A46F-25B8BAE795AD
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Blue sheets serve multiple purposes. &nbsp;=
Room sizing is just one of them. &nbsp;Intellectual property issues is anoth=
er part of their use.<div><br></div><div>It is my understanding that the blu=
e sheets have been subpoenaed in the past to determine who was present in th=
e room.</div><div><div><div dir=3D"ltr">--&nbsp;<div>Mark Andrews</div></div=
><div dir=3D"ltr"><br><blockquote type=3D"cite">On 16 Apr 2025, at 07:06, Ge=
orge Michaelson &lt;ggm@algebras.org&gt; wrote:<br><br></blockquote></div><b=
lockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"auto">Purely a=
s a point of information for a very long time we were told blue sheets were f=
or room sizing and no one cared about the name.<div dir=3D"auto"><br></div><=
div dir=3D"auto">Meetecho logins manage queues and would provide a record of=
 participation as a similar quality in my personal opinion.</div><div dir=3D=
"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">We also historically ha=
d complaints with people taking photos of blue sheets.</div><div dir=3D"auto=
"><br></div><div dir=3D"auto">I can't speak to current motivations or practi=
ce.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">George (in a personal capacity)</div></di=
v></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr=
" class=3D"gmail_attr">On Wed, 16 Apr 2025, 6:38=E2=80=AFam S Moonesamy, &lt=
;<a href=3D"mailto:sm%2Bietf@elandsys.com">sm+ietf@elandsys.com</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">Hi Rob,<br>
At 11:40 AM 15-04-2025, Rob Sayre wrote:<br>
&gt;I noticed some extremely brief names on the blue sheets from IETF <br>
&gt;122. That led me to question what purpose these forms serve. I asked <br=
>
&gt;a bit, and was told it was a matter for the LLC. I don't know where <br>=

&gt;to ask, so it's here.<br>
&gt;<br>
&gt;I'll use my own name as an example. What is OK on a blue sheet?<br>
&gt;<br>
&gt;Robert F. Sayre<br>
&gt;Robert Sayre<br>
&gt;Rob Sayre<br>
&gt;Rob S &lt;--- I saw these<br>
&gt;RS<br>
&gt;R<br>
&gt;Rob da MC<br>
&gt;...<br>
&gt;<br>
&gt;If we allow all of these, what is the point?<br>
<br>
The rule is that the Chair and/or Secretary must ensure that minutes <br>
of a session are taken and that an attendance list is <br>
circulated.&nbsp; The attendance list used to be referred to as "blue <br>
sheets" because of the color of the sheets of paper.&nbsp; It is viewed as <=
br>
good practice in other venues to have a list of persons who attended <br>
a meeting.&nbsp; It may be the same for meetings held within the context <br=
>
of the "standards process".<br>
<br>
The practice at IETF meetings was to disclose name and <br>
affiliation.&nbsp; I assume that it was about openness (BCP 9).&nbsp; The <b=
r>
affiliation part could be about not having to formalize "balance".<br>
<br>
I noticed that some attendees did not disclose name or <br>
affiliation.&nbsp; A meeting would not look like a serious activity if the <=
br>
information in attendance list is opaque.&nbsp; There may have been some <br=
>
assumption which led to the practice of disclosing name and <br>
affiliation, i.e. there was no need to write a "best current <br>
practice" to explain to an attendee how to write his/her name.<br>
<br>
Regards,<br>
S. Moonesamy&nbsp; &nbsp; <br>
<br>
</blockquote></div>
</div></blockquote></div></div></body></html>=

--Apple-Mail-D312CF00-870B-46E8-A46F-25B8BAE795AD--

