Re: Remote participants, registration, and mailing lists -- unintended consequences

Ray Pelletier <rpelletier@isoc.org> Sun, 03 April 2016 15:53 UTC

Return-Path: <rpelletier@isoc.org>
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 4BB8112D0E2; Sun, 3 Apr 2016 08:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 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_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 CO-r8oKLMgti; Sun, 3 Apr 2016 08:53:30 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0656.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::656]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD4C212D0A0; Sun, 3 Apr 2016 08:53:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com; s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RbbkCRBiC073zPCJ03V6JTwdPdon3OJctLfD6cVsuY4=; b=ulcFb0Ya5p604Iq5IbStLQBO8iR9SrfUdmfUmBxuL2Cl6O+HUThYB7R3t/ChaSHgP6OvGRSMLVp1FugJ+bDa0mk0nFdSRRoXJKKwOAvt+SVbBaI9cgLJgSsqdQC3IJWS46D3q537fzTQoxPjbcBB3W19tj583+eFXKyGiuMNQ8I=
Authentication-Results: jck.com; dkim=none (message not signed) header.d=none;jck.com; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:67c:370:176:b8e6:cbb6:d842:643e] (2001:67c:370:176:b8e6:cbb6:d842:643e) by BY2PR0601MB1558.namprd06.prod.outlook.com (10.163.107.140) with Microsoft SMTP Server (TLS) id 15.1.447.15; Sun, 3 Apr 2016 15:53:06 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Remote participants, registration, and mailing lists -- unintended consequences
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
Date: Sun, 3 Apr 2016 12:54:43 -0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <297ADFD7-8581-42EE-8C5C-358EE8DC322F@isoc.org>
References: <57012A74.1060400@alvestrand.no> <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3112)
X-Originating-IP: [2001:67c:370:176:b8e6:cbb6:d842:643e]
X-ClientProxiedBy: SN1PR15CA0016.namprd15.prod.outlook.com (10.163.200.26) To BY2PR0601MB1558.namprd06.prod.outlook.com (10.163.107.140)
X-MS-Office365-Filtering-Correlation-Id: 9231c75b-3b00-4af6-0a41-08d35bd80cde
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 2:41PmaEtQhChfs6t14xyc0iPR48HJyi/CrLVNym/WwbRTv9Gg+Vl6AWrdi3g7EJ9WC58rq3n6jN5yB8mZ3bkXwKXw5DM45HZ14mcMdh/GuaKUYKm/g02/LxbliNWa5GzIvfWfnm9Rc6rtjdyA/MX396pccqpsa5Qfc4klTERBZmk0t7WgWCUj7lzIoZbjfIWA; 3:PZ+tGEk2orEbgCuekQB/BVD89T5+1moygStOgmwuuq/u+p1UIRHwN+Aw7lIol/EG2hS+dSeQfXwKwZehif2A0CG68GNeGqiNGq3plt66MBdniivdfOa2qh1amyoKEyhM; 25:BNhnE6sWwUqQeowkVIHntvfoQZUpbaMUngll8ztMHEqPcTc+AtunIJuqK7LPXpH1u5qJwGGICqRQfW7NxaMXMfFwnRJ/pxRPj9benYMWmz8BmMqyq1m5uwI279jIu9fSfI1H4t02faJ4/29mgdWDnrQS7Fw2Lv3vafVmaNMbe174lZkhfkfS0qq4veQlJHw5zA1P3hw3mUQfYNKnA+vnaM3Cj2Urns9wqPN6ocxqw2jHtB4/gdk5sQyg/0P+djkk0ybn1eG4nk0y1HGHYqNlp3rvhrgAdYyDWbieqeKTePvIZwMuvXflXhH2/d76411xOWJ8MsvNK7cJJ9DWlPDOS1y6BQDx5M5SRSWJnEjCXo8=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0601MB1558;
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 20:eHnvas/vxfFw8jb6ntA0oyfY5X8TBX5szmyU2FZfreMqr0CMxSX1PZjussG849UIlt6abmJYN1mPZbJ2Ox/yQB/kEL7iIoOeNC++I9lEnwpC6xwqOMt15tKj064iWcWjclXctNY1INA+xVPbySflzcSLYNvx4LYdKp4hcP8yTsAUiCkKKHBZtsROe7onUQX2UcWOBflsNqGML+pCcPms/T2BHMssxhdZWRiOFrBmKL4I6OZcinnh3t8e2TTz6+SlccdUscvB3OxNnhOVMT5ZwZK1IId7ghmjBxFfLeq+MbzJfJxL+S7KC8M30gKTPSM1S12z3CaEPIH/WWHQxNIUk1Ly1eAzDj6HmqKcWp38cmhucNNx3Ygx1Mj9Zfcc+vLwImK2KvWMuLx2SjmwsE8VS+x1MJ/xxsEMdjrs47AWFgN+7KKyOYCgPwlz8sIsvNuFWqsNfwCsVFsOTMufOE/aDMChDLam+XBnpCYEolwG1QXf4MAYXLgrleKOkb/k/ht1; 4:Ia2XzMH3Lo6vCf317MS2JfUcOCYxxOeIaT92DxOY2ret1aQ3QqSDIeMjKtj9v/TmIzjE2GfH0AgdasVBbBYjsBkoUpvR4AXu3aEYoeLfAv7RWconUPKKKcpuLBxAujAGhX5YfzD8Elk7Q70a+8fa5IkpRSj4JLV1ksGDo8SZfHyEWHFNF9T9atUAHi8pwpw5pyqcpMNFIfkBVQ8dopI+q1qlFJvQo2U5KShnv1svulb0u1JAlyYjyeXs8nzjbraQDnIWavY9au4QBr1lB/UDX9OqZ445Sn7AgJ5bdGs34pIR7RrE69CE+360syajZOLxbmkgNKzadHdtQ5HRKZE4QRx/IHiw4712qZ44YNNSk8xzx++Fwb1karuOd5GOFXKb
X-Microsoft-Antispam-PRVS: <BY2PR0601MB1558CF17FDC5D6301FBC3A5AB09C0@BY2PR0601MB1558.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:BY2PR0601MB1558; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0601MB1558;
X-Forefront-PRVS: 09011458FC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(24454002)(377454003)(23676002)(57306001)(189998001)(82746002)(4326007)(47776003)(36756003)(110136002)(2950100001)(1096002)(6116002)(2906002)(15975445007)(81166005)(77096005)(19580405001)(19580395003)(92566002)(86362001)(586003)(50986999)(83716003)(76176999)(5004730100002)(5008740100001)(33656002)(50466002)(42186005)(50226001)(3826002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR0601MB1558; H:[IPv6:2001:67c:370:176:b8e6:cbb6:d842:643e]; FPR:; SPF:None; MLV:sfv; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 23:9KPBubFFWxhIcFfOsMrW+MS9CTqobts9oLkJg+VYCdG4IagxFtS9CaDsIoqcuTEGMr9uGdCcU4OV/bQHj3IOVimVJIiv4lELR282c7MH1v4elOTFJjO9ivvLczx7KZs6md9d6iTQbQVzX6iHB4xPi3rmFrYBckjonOQd0Xkoc0ndPPwh9+xsDB79h52iUFIkUx566KXWLwq7gdMh8kWqmLJqzn2J7Osw7VKXWx9BgdG0AC19RWVZzbsc++cEt3Ud8gF8oKqcW+YD7eXzNVXdBhgoSP9++Ytc+pI9S7zM+BGahVADMQtgNXoEMkFSd0/muyMxJCTYOrIrN8XtaaLj4y9IMeJgCQIFUHQjRVp38c8OsXOjbhET00JUf1BzYLMPvqXhCqw7cZGGgD+Js7tImhOL+S+BGPAjcFoEClC7+r2UUmbfpQNNxl6f+tg2oLRX8xXT6e8sgvaKhaYIubN6YlmwiEwAAXTlDLY0kY1DrR6eiNKzX7Q9qu1ZKk3wyvSY/nqIrADo8CDoTNf6wcVj6pk57v67HFy+jGXOqL2mFHUh05G6vKx8GkggjaRvuxhr1jEZBDMiYoy3+ix3JqBgSYIcwxN3ztF9GPC4s3YkgNoBb/EJ2b8kp9v8MgpwhwpdPD/UR56uQiPYBpbeKgF+DqTGJuf0cJ2OtsBHW2z+EeTe+VA13amN8/KkGHMKvbMetVCwvwwO5IYCqJ0cYOMX8OzemZb+ATO+4xE3IjsUtuflRF+yY4F8EOmd79iFxHOcFE5AVxbVPvxTq5U4RmQuXIIqmPsMCn9GYqhD3G8QILYJp4JRh5QVICXfwIeXu01v19xbSFh2fDiGGkAtl6cjVniHy0175fvX/3pXY6sgS8fDlCAJdQ9ciVotkPqQ4tDjL3I5QsDXrbAy4yAmH8MGcUOcHRQtSXN99p/yPn33/Wk=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 5:oL2RNljBtKyF6hYE2viU+BBCGQJaxafDPeMd1tXBsuwJBbKtG5JYN3S0MEdcBzkQBrsvA92x4EwD27TXC171GoGy+JEJyr8KWquVjuCYsBVdT438DaDF7wo4OcOK74+cykHLhbEmSi1LZwkFJtsPpg==; 24:+GFAh9+oTg7KXuEvab7Av9uWGAQ2pV3ItDNuKZzypVjbBuNgz9PaSGcn0sIGG2iFKhpBt1p1I1JesJ2aaLU3/qDQ21mC4ks+Jm3ifZ32dP4=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Apr 2016 15:53:06.3032 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0601MB1558
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C2kG9M0vY4QiHPpiKhKTGwFYLOA>
Cc: 95attendees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 03 Apr 2016 15:53:32 -0000

John,

> On Apr 3, 2016, at 12:29 PM, John C Klensin <john-ietf@jck.com>; wrote:
> 
> Hi.
> 
> Not to complain but to add to whatever consideration occurs this
> week about getting remote participants, more evidence that these
> things need to be thought through carefully has turned up in the
> last 24 hours.
> 
> * Apparently, remote participants who have registered are listed
> on the "registered attendees" list without any differentiation
> from face to face attendees.

Thanks.  It has been noticed and will be changed.

>  That has resulted in my getting
> several "when can we meet up" messages and some confused people.
> Not a big deal, but an unnecessary waste of people's time.

This is not clear to me.  This traffic wouldn’t be passed on the 
95All list.  It could be on the 95Attendees list.

>  More
> important, if questions arose in the future about who was, or
> was not, at a particular meeting, it could lead to even more
> confusion and inconvenience (e.g., IIR, registration records
> have sometimes been the subject of subpoenas).

When asked it’s usually the Blue Sheet, which now includes 
remote attendance "eBlue Sheets” at WG sessions.

> 
> * When we register, we apparently automatically signed up for
> the [95all]

Yes, administrative matters related to the meeting, e.g. schedule
changes.

> and allowed to check the box that gets us on the
> [95attendees] mailing lists.

Correct, that is optional.  

>  That is fine -- I used to have to
> try to monitor the archives of [NNall] to be sure I didn't miss,
> e.g., important schedule changes (although most of those are
> copied to IETF-announce and/or the IETF discussion list).
> Announcements of specially-formatted agendas, workshop and lunch
> seminar announcements, and the like are as useful to those of us
> who are remote as those who are present (even if relevant
> sessions are not supported remotely, we know what we are
> missing).  But the N/S ratio is incredible -- I really don't
> need the regular extended  discussions of plug converters,
> nearby restaurants, SIM cards, laundry, nearby ATMs, and so on.

We’ve tried to decrease this by having a wiki for each meeting so that
these matters can be addressed there, some by staff, but much of it
by locals and experienced travelers.  So far, the use of the wiki
has been disappointing.  

https://www.ietf.org/registration/MeetingWiki/wiki/ietf95

> 
> So, for the future, if we are really going to do this remote
> participant registration thing, it would be nice if someone
> would really take responsibility for thinking through all of the
> implications and take action on them.

We are going to do this remote participation thing  and 
welcome all suggestions to making it a better experience for 
all - remotees,local attendees, WG Chairs, etc.

> 
> To all who are in Buenos Aires, best wishes for a successful
> meeting.  And to all who are participating remotely, let's hope
> that these difficulties with registration are the last problems
> of the week and that everything else --the actual feeds and
> connections-- will go really smoothly.

Amen.

Best
Ray
> 
>    john
>