Re: [Recentattendees] [104all] Further Clarification Re: IETF 104 Preliminary Agenda

Fred Baker <> Tue, 26 February 2019 01:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5235F128B14; Mon, 25 Feb 2019 17:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kWXBR1QVQ4Bt; Mon, 25 Feb 2019 17:03:10 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A487012867A; Mon, 25 Feb 2019 17:03:10 -0800 (PST)
Received: by with SMTP id m1so9687771otf.5; Mon, 25 Feb 2019 17:03:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=iHB09VpCKaf66pfX2nPOZhwkvyDCLOz6ralDgL2F+2M=; b=rmIHz1cZMoeGSqLX9mw/s0xF5GgRNLPn2d3gTZovcifS1VGhAFFFtYm3WUIAGAKjRz pFr9C5mTA0WH1SNURiSpElvyCD/0X8z3fH0RC4z9uCyhPxwt4hdHYbKFmHOM2UG9D8X8 m3ETM+u2X9kpnM+wzKC2tTRX+Fwnal+zYeQUMt6LW963N8gl7Utn5eB+eihkeQb44vEt pAaT62BnjzNLd3EzbLz2l+lLlyLJ9qTSiens8OpE1XrYhPlImZ0j6C/ez8EMwiqsgF1v hpYZNZHB7d9Sr9TR0Bhx7duP7/XItnTrSALB/EwFttXXswK0Ig6GRrzb1ZmU3WPNv61o LheQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=iHB09VpCKaf66pfX2nPOZhwkvyDCLOz6ralDgL2F+2M=; b=LEY/WsF3Zs9DU8FsLTUPIVzFkMHOkEdPK+sOAcYw4UDC3YYLU9IU/p3fAMx4JmUQE3 T2s6HiQnYKGcqRFYib8It/jrC7HWCjj044VCpJahaQVlogtRT9h1Xb2xPUR5v0+b0hz6 lEtNbNvGBWwtQXW6nk1H24nvsJJu+mkhEESzS764EyxtLg9MzKs6ED6NumGfa/7gFsdz 3K3qO/qIEAOyw6roittuBegbvPA8Y+M5RBkblTTVkyRcJr+k4p6O/s2jweeG5R1mWD8I a7PA8KeRuC1ElxBdXpm60GRceQlHBmgZMk01kGo6N9Mlv2NfJRo+IeeRzS25L4Y2xAZ3 7U2w==
X-Gm-Message-State: AHQUAubgge/NfnhvJuKspvlxlTxgtG3NvvVUuLdEhzDwwOz05tU02MTs JET4z96ykqjk+4OSquLoC7w=
X-Google-Smtp-Source: AHgI3IYIZKVq4j80Hw90dMGszvBX1SAv1K+cCbW4ocncMVIpAsSO9KKCMGRn5V2r/loRsq4tGyDfZA==
X-Received: by 2002:a9d:7554:: with SMTP id b20mr12770770otl.32.1551142989762; Mon, 25 Feb 2019 17:03:09 -0800 (PST)
Received: from ?IPv6:2600:8802:5600:164::100b? ([2600:8802:5600:164::100b]) by with ESMTPSA id c26sm4460765otm.10.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Feb 2019 17:03:08 -0800 (PST)
From: Fred Baker <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_9212F539-E2C5-4CF3-821A-654E74A8BDE9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Date: Mon, 25 Feb 2019 17:03:06 -0800
In-Reply-To: <>
Cc: Working Group Chairs <>,, IETF <>,
To: Tom Pusateri <>
References: <> <> <> <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.104.2)
Archived-At: <>
Subject: Re: [Recentattendees] [104all] Further Clarification Re: IETF 104 Preliminary Agenda
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Recent IETF Attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 26 Feb 2019 01:03:13 -0000

Puzzling about the CC line, and have reduced it somewhat. I am a paid attendee at IETF 104, and got a bounce from saying that mere mortals can't post to it.

> On Feb 25, 2019, at 1:36 PM, Tom Pusateri <> wrote:
>> On Feb 25, 2019, at 10:33 AM, Fred Baker <> wrote:
>>> On Feb 24, 2019, at 11:34 PM, Stewart Bryant <> wrote:
>>> A better approach might be to ask people at registration what sessions they needed to attend.
>> An even better approach, although it delays feedback by one meeting, would be to look into the IETFers Application data. People list what they want to attend for the purpose of calendar maintenance. That would inform the next meeting's agenda development.
> While a neat idea, it’s not currently possible because I don’t save any private data. And while no user is associated with that data, (I don’t even create users), it is something that could be collected anonymously in the future. There’s a lot that could be done with anonymous statistics or even creating actual users (like automatic blue sheet sign in using Bluetooth LE Proximity sensors or locating colleagues or subscribing to notifications), but I haven’t had time to think through the GDPR implications.
> Tom

OK, I'm confused. There is this app, which runs on IOS or Android. I don't know where the data is stored, but I know I can tell it what WGs I care about and it will be displayed both on my phone, and on my laptop in a calendar called "IETFers". If it can get from my phone to my calendar on my laptop, it can get to somewhere else. I'm suggesting that the "somewhere else" might anonymize the data and summarize it in some useful way.

Is that "every IETFer?" No. But I'll bet it's a large sample...