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

Alissa Cooper <alissa@cooperw.in> Mon, 25 February 2019 06:34 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91D40130DE4; Sun, 24 Feb 2019 22:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=FCpIaXkt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ylkKrfBN
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 CnhfnNNg2hfD; Sun, 24 Feb 2019 22:34:30 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24638130E0A; Sun, 24 Feb 2019 22:34:30 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E597021FBF; Mon, 25 Feb 2019 01:34:28 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 25 Feb 2019 01:34:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=1 q0jDaamVHp9bkLhnqwke9wOZdc6GywRSPvusK8xD+U=; b=FCpIaXktUB4mfKqIY hToKLuZEGInImk4ogHBQJZjdknxyqELxunbznwsPMDPIaQ/q2aah/XveK/49gbKD 3MW0eeHR/s2ybnbU9sYpsJm0QPglZnoRbuv8ItiO9cnmMJ8XsDVreJsTej7iJffi ZPU0pPFGpn/YQzru1a9uszhx2VTrf4h8PVsQlSvfxXvG6EnrmAOu4dJEpCAntRal 4umIh2/eg3ZXeeXtBMM8CMruqn/GN42XqgBEowMK9FQldFpRV9DVNrKW7DdWu3qi FuntM9ShhfhnrGMysG8o19siPdzrxLJluwTWhcjhEMn1dAutpmemlh87sHzQNYEE wgbKQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=1q0jDaamVHp9bkLhnqwke9wOZdc6GywRSPvusK8xD +U=; b=ylkKrfBNfpYREk1v0iykGwGkMFM0bE07YRS/VNGUI4AUP8M77zCojun+6 tdsWH03UR5YWgnESc7/zni6DwNzYmWstddg5aUMgl2NPeTISK7AmzeyvLGIHC6F5 Vmakwvhz4IaE76bKr3CCol8tugtpxgQcIILVwWsD2xnnw2CCBPwxD49uwAkOQWRM mltlW/OInOzg3XdkO/9oR8KTzdmopNEqGu70hrDEbOdVZRO8p+ErssPwuys7Ca8E kWQKsPAae48sXtLavWwLAyfMTQvoIWQT/WSKvzaG3xZEJIAm5xfsuUvBUi8hp2hA loX3CYmM7mlK+NUQRocgmUTDy0v+A==
X-ME-Sender: <xms:dIxzXNGebChgx4PVJM6S28wbNrSyA8P7SIQbq0pJTNToDc35KS2_0w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrudehgdelgeculddtuddrgedtledrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesrgejmherhhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepshhurhhvvgihmhhonhhkvgihrdgtohhmpdhivghtfhdrohhrghenucfkphepudei iedrudefjedrudejledrvdehnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrg estghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:dIxzXHlumoKh6Y4sfC1WWt3MqQYWJTgA34iqjHFP7ORXbnbkhZfb5w> <xmx:dIxzXA1fIflsau-W5Gti-1QpkG01Aodn-X5BoG7cJLRZm-jR-pNwiA> <xmx:dIxzXLQc4Cg5Lev_zTokqhAE86XoRiy6N-Vmbdjlot-AEufnsApyXw> <xmx:dIxzXBowqdnTYW2wMPKFyLutQjAj0rMTtzIUbsiVuxKzBq5ZraJBmw>
Received: from [10.221.157.109] (mobile-166-137-179-025.mycingular.net [166.137.179.25]) by mail.messagingengine.com (Postfix) with ESMTPA id E6538E40C2; Mon, 25 Feb 2019 01:34:26 -0500 (EST)
Content-Type: multipart/alternative; boundary=Apple-Mail-9AC991C2-6766-4AA3-B59B-060780F134F1
Mime-Version: 1.0 (1.0)
Subject: Re: [104all] Further Clarification Re: IETF 104 Preliminary Agenda
From: Alissa Cooper <alissa@cooperw.in>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <ea13d9b6-78bb-8067-d8f2-a7b98c5de307@pi.nu>
Date: Mon, 25 Feb 2019 07:34:23 +0100
Cc: Lou Berger <lberger@labn.net>, Stewart Bryant <stewart.bryant@gmail.com>, wgchairs@ietf.org, recentattendees@ietf.org, ietf@ietf.org, ietf-announce@ietf.org, 104all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <EE41BDFB-ED4E-4944-9E87-5E56766FAE37@cooperw.in>
References: <155089851917.5347.209761560453230605.idtracker@ietfa.amsl.com> <23D062E4-4464-48C2-9464-61697C2351D6@cooperw.in> <A7B3EF23-DE19-4330-A660-D27744B95A34@gmail.com> <3a201a22-6ed2-ab83-5205-a28af7ba49d7@labn.net> <ea13d9b6-78bb-8067-d8f2-a7b98c5de307@pi.nu>
To: Loa Andersson <loa@pi.nu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/c2T2D-hUNEvEHtGxHLPw0NSGWgg>
X-Mailman-Approved-At: Mon, 25 Feb 2019 07:49:45 -0800
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2019 06:34:34 -0000

Hi Loa,

We have multiple sources of feedback. Individual complaints are one and the meeting survey is another. See Q11-13 at 
https://www.surveymonkey.com/results/SM-KDSV3LH9V/ 

Of course, the point of publishing the preliminary agenda (what we did last week) is to solicit even further feedback before the agenda is finalized. 

Alissa

> On Feb 25, 2019, at 3:34 AM, Loa Andersson <loa@pi.nu> wrote:
> 
> Folks,
> 
> I strongly agree with Stewart Lou, I think that we sent a strong message
> to the IESG that any experiment that decreases the the number of
> available slots is causing problem and should be avoided. Instead we
> have another such experiment :(.
> 
> Stewart, you are not alone, but I think what you see is that more and
> more people feel that they are not listen too, because the opinions we
> have is not what the people that should list don't want to hear them.
> 
> /Loa
> 
> 
> 
>> On 2019-02-24 19:48, Lou Berger wrote:
>> nope.  Couldn't agree me more.  These experiments seem to me to be reducing the value of the meetings.
>> Yes, people meet on their own during the meeting, but this has always worked pretty well in self organizing ways - and having rooms formally available for this *is* helpful in this regard.
>> Lou
>>> On 2/24/2019 3:24 AM, Stewart Bryant wrote:
>>> Am I alone I wishing that the IESG had used this time to address the unacceptable number of scheduling conflicts that exist in the meeting agenda?
>>> 
>>> Stewart
>>> 
>>> Sent from my iPad
>>> 
>>>> On 23 Feb 2019, at 11:13, Alissa Cooper <alissa@cooperw.in> wrote:
>>>> 
>>>> Thank you, Secretariat.
>>>> 
>>>> We got a bunch of feedback after the last meeting (and previously) that people want to experiment with open time in the schedule. We’re trying it on Wednesday this time. Depending on how people like it we can try something different or not at future meetings.
>>>> 
>>>> Alissa
>>>> 
>>>>> On Feb 23, 2019, at 12:08 AM, IETF Agenda <agenda@ietf.org> wrote:
>>>>> 
>>>>> Hi everyone,
>>>>> 
>>>>> Our message earlier today announcing the preliminary agenda [1] was missing some further context. As previously mentioned by Alissa after IETF 103 [2], the IESG wanted to continue the unstructured time experiment at IETF 104.
>>>>> 
>>>>> Wednesday's schedule has regular sessions until 13:20, unstructured time in the afternoon, and the plenary in the evening at 17:10. This leaves almost four hours of unstructured time for attendees to reserve for side meetings. During this period, there will also be one unique Technology Deep Dive session with the acronym WGTLGO [3].
>>>>> 
>>>>> Monday through Friday, we will have two rooms available for attendees to reserve for side meetings as usual. On Wednesday afternoon, we will have five rooms available for side meetings. Further details about how to sign up for these rooms will be announced shortly.
>>>>> 
>>>>> Thanks,
>>>>> IETF Secretariat
>>>>> 
>>>>> 
>>>>> [1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/_JeP2fQ7rHPosZWpNtpl8I_uL5U 
>>>>> [2]  https://mailarchive.ietf.org/arch/msg/ietf-announce/H64AuTYhxsGqM1a8BfTkszCZyso 
>>>>> [3]  https://www.ietf.org/blog/ietf104-bofs/
>>>>> 
>>>>> -- 
>>>>> 104all mailing list
>>>>> 104all@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/104all
>>> 
> 
> -- 
> 
> 
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert
> Bronze Dragon Consulting             phone: +46 739 81 21 64