Re: Session attendance reconciliation (was "Management team")

Fred Baker <fredbaker.ietf@gmail.com> Thu, 23 April 2020 01:31 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE9C43A1054 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 18:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UTPYMMo0YbE for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 18:31:28 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90D6F3A104C for <ietf@ietf.org>; Wed, 22 Apr 2020 18:31:28 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id j7so2035245pgj.13 for <ietf@ietf.org>; Wed, 22 Apr 2020 18:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=DOYdUqOEVbm96az0iBfutXrDBD1Qcao3x/z3m1AX7d8=; b=nlcHz4PfP/dZNUrn6Irz/OdC1lXVUJ2lbfUqFyPUI6uBT5th6iFq2AAmS/8Mj58phk +9CQtUbo9LVC/TVBDDZ9WyGzs5hUe9ODK/7YwLJPe5ibxKBC1z5Nkp93fKVXEIRfcH/V S+fuXo2VUecQj1HZFJb1Fz03dYZS9Uyb1mzmVbweW9bfikBhZlPLU9hG2lEx84qIMnZO iPIRdlxhkvl3FgAfAvXG3gK3j8L7LPHTlzfJSl+NrPTA0XF8UpJKaoZsej43XIvpEoOk WOIX0dlNg6+/eKLzqFJSg9dHyQSIh95k6RKpRpXX3AsE5mS8uANpAQdA5OfpCNj+hU2Q A2PA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=DOYdUqOEVbm96az0iBfutXrDBD1Qcao3x/z3m1AX7d8=; b=NGK3+KEO97Y+D6DwZl/GGQFzLzPAcofqXMfU6Z+PuphHm24pwvbunTfj0ulhLC4Nkd ymZRAn7OiRjcXVUMIXiv7WD7177+6bDKUv1+oDcCrLMkGafDshs0qrY/aK3WwTIEUAE0 hyqiAXh0Kf68JmiZGvbzixUxTeF6N92DQg7zcm9BBuaFn62y41esWawfSp7h4cLRmbcr R7K/rMLJwB5m/QuVr02dGeUgSPs2jACAuFvYUvG3nlt4nn3s5zneJBqoZqpOOZvcQzZX RJbpDC/UbJae9GwVGYrpRZuJ7YbRrPvzjvE0qHw+ifeLllrETx+6pnA64aHHR8fz32Wm hgSw==
X-Gm-Message-State: AGi0PuYks+vBdhrSfmsxwlyjIGALwD/jBdOmPvaoNTtdUxGnv+UoPqgb qUXy7RPMxo9wOsrkmbZa5mAia1LE
X-Google-Smtp-Source: APiQypJqMLITGvzVcnp2CfnIUYXn8VUmTwJk/AYmTJUQqBc/1Myk+7Amt4ep6VJwcNpZ+BE9Te0CcQ==
X-Received: by 2002:a63:2b52:: with SMTP id r79mr1684858pgr.261.1587605487942; Wed, 22 Apr 2020 18:31:27 -0700 (PDT)
Received: from ?IPv6:2600:8802:5900:13c4::100a? ([2600:8802:5900:13c4::100a]) by smtp.gmail.com with ESMTPSA id s12sm475093pgi.38.2020.04.22.18.31.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Apr 2020 18:31:27 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Fred Baker <fredbaker.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Session attendance reconciliation (was "Management team")
Date: Wed, 22 Apr 2020 18:31:26 -0700
Message-Id: <9AAB2DB5-065C-40D4-83AA-2ADD352D7C7A@gmail.com>
References: <CAKr6gn3dqEXZtiyNNDgGCMV2obqU3EEwN8wOVC-FD39DUzy5sg@mail.gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>
In-Reply-To: <CAKr6gn3dqEXZtiyNNDgGCMV2obqU3EEwN8wOVC-FD39DUzy5sg@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: iPad Mail (17E262)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z3EgAhGmNlzkHErilCworrRjRz0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 01:31:39 -0000

I might be mistaken, but I bel8eve that blue sheets have been subpoenaed for IPR discussions (kind of like -00 drafts), and have therefore not been discarded for some time.

Sent from my iPad

> On Apr 22, 2020, at 6:07 PM, George Michaelson <ggm@algebras.org> wrote:
> 
> There you go. My memory is completely the reverse. Blue sheets were
> for counts for room sizing only, and had no requirement for a real
> identity and were (for privacy reasons) not retained about individuals
> or used to do things which related to them as individuals.
> 
> And no.. I haven't gone into the mail stacks to prove that: I'm saying
> what I thought had been said. Not unusual that its the inverse of what
> was actually said.
> 
> _G
> 
>> On Thu, Apr 23, 2020 at 9:12 AM Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>> 
>>> On 23-Apr-20 10:35, George Michaelson wrote:
>>> I thought some things were said about blue sheets which went to "we
>>> will never do that, its only for volume and not PII"
>>> 
>>> but memory may be wrong, and .. we're not about "obeying the laws of
>>> physics" here. But.. if we did say that, don't we need to "un-say" it?
>> 
>> I hope we never said it. The blue sheets are proof of presence for
>> the purposes of our IPR disclosure rules. A list of attendees
>> is required by BCP25.
>> 
>> As the Note Well says,
>> 
>> * As a participant in or attendee to any IETF activity you acknowledge that written, audio, video, and photographic records of meetings may be made public.
>> * Personal information that you provide to IETF will be handled in accordance with the IETF Privacy Statement.
>> 
>>   Brian
>> 
>>> 
>>> Blue Sheets are not purely informational by count now: You may be
>>> identified by adding your data to a blue sheet and it may be
>>> reconciled against other records in ways which are PII, and hence
>>> invoke GDPR and CCPA
>>> 
>>> -G
>>> 
>>> On Thu, Apr 23, 2020 at 8:30 AM Jay Daley <jay@ietf.org> wrote:
>>>> 
>>>> On 23/04/2020, at 9:09 AM, John C Klensin <john-ietf@jck.com> wrote:
>>>> 
>>>> This suggests something else that may be relevant.  If there is
>>>> _any_ chance that we might want to use session attendance
>>>> information for IETF 107 for anything at all, including but
>>>> definitely not limited to Nomcom eligibility in the future (not
>>>> this year's NomCom), it would probably be wise to either merge
>>>> to information from the Etherpad with Jabber logins and/or to
>>>> explicit ask people who were unable (or sufficiently
>>>> inconvenienced by technology) to record their presence on the
>>>> Etherpad to identify themselves to the Secretariat in some
>>>> appropriate way (I hope not on this mailing list).
>>>> 
>>>> Jay, is that feasible?
>>>> 
>>>> 
>>>> For IETF 107 the secretariat reconciled the list of Webex participants with the bluesheets to create a single list on a per session basis.  Inferring a participant’s name from a jabber ID is too hard.
>>>> 
>>>> Jay
>>>> 
>>>> 
>>>>   thanks,
>>>>  john
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Jay Daley
>>>> IETF Executive Director
>>>> jay@ietf.org
>>>> 
>>> 
>>> 
>> 
>