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

Василий Долматов <vdolmatov@gmail.com> Wed, 27 February 2019 07:35 UTC

Return-Path: <vdolmatov@gmail.com>
X-Original-To: 104all@ietfa.amsl.com
Delivered-To: 104all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECE3130E76; Tue, 26 Feb 2019 23:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.019
X-Spam-Level:
X-Spam-Status: No, score=-1.019 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, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 MfIVHwa1boag; Tue, 26 Feb 2019 23:35:26 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 8FF90130E6E; Tue, 26 Feb 2019 23:35:25 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id 131so2513430lfa.5; Tue, 26 Feb 2019 23:35:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JhGPjyjOEVitZSY07HOHlbivgjsve07imBep7EK6xzE=; b=kqM8S+x+0QtLocNMHJ1jmM5j6wjrpFIYJmUA33XHIkJ7Hq3iU8q75TVTRP2PknTe2+ BIH8o6+C2GEu6eOSM9r2l+qykGXWGXrkYHRG91uIvFKG428NVIgXvPy5qhZh+c4a+kMQ hHsfjslQAlchK7NBdrR3RoBliRQ+U4pY7EOkAXCDId2h+KdfvoisC+i1+N90XkmtVmx5 T1QgcZYblUa6KKKUaxYHfibYG/53M0eoGBfyLhxO3VpshoI3PTrKXazhbqlM+M4EAEzE pb3hbgnhF43i7AdxQmzk/jIok3Q7ZDQKhyS75S5WyGDXiHrBusJiW/GZ/8kEH8265Q+G +oYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JhGPjyjOEVitZSY07HOHlbivgjsve07imBep7EK6xzE=; b=K8oOOBTNCPpF0WEMJXG3WdJbkU1gEpcCgNjd9AzGj23LeXXG1hXxbulwfsPnkLmLRw i8MESjLK88rCslIG7SfpaFKz9Mr9Xf142a7pHHqi+wfbEt+xTd2ogGQFuxRmBypmIqFG 1fj+3icgeDhQyW6Rik+359G29Qy/XBnIge4aGwDJANdd1aqDG0IWK+ziOk50w4wv3pAx 1dhfdgbvLxhnmR6imXxDhAZaOs6C+/uPv9KD2cYw01uUXAYKHLOj43bNvQ39MHje9fwg iRyTxaRpERpyN2gqX0BOLXm8GfKG0a+h7ZC2jYHNcIG3rFBaWmHx31+i03Kz5KA5CQaV 3MzA==
X-Gm-Message-State: AHQUAuZ55PxaNAu8wP+usGVGPMcj0pd1zmzghJqYlowcgB/6g3PLZgQ3 H5di7rFWg0XvvYGPzsUwQ8Y=
X-Google-Smtp-Source: AHgI3IYBHLpVl/0e5dxLBWj3eka+d1mu3Cg0fwZv6GIoTYFsTG6kbqtmMaMbeEsMsySgcnZrelrR2Q==
X-Received: by 2002:ac2:424e:: with SMTP id m14mr15953846lfl.4.1551252923681; Tue, 26 Feb 2019 23:35:23 -0800 (PST)
Received: from [192.168.191.94] ([89.175.23.171]) by smtp.gmail.com with ESMTPSA id m5sm3699599lfb.78.2019.02.26.23.35.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 23:35:22 -0800 (PST)
From: =?utf-8?B?0JLQsNGB0LjQu9C40Lkg0JTQvtC70LzQsNGC0L7Qsg==?= <vdolmatov@gmail.com>
Message-Id: <5968C3DA-3D6F-494A-83BE-06C43676E882@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4AAA50AA-09F7-4398-9481-66BC212A2371"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 27 Feb 2019 10:35:20 +0300
In-Reply-To: <CA+RyBmWkPWVHhRu52xfL7retKQzifXQmfyMfKQycaF8XtJSWtw@mail.gmail.com>
Cc: agenda@ietf.org, wgchairs@ietf.org, recentattendees@ietf.org, IETF list <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, 104all@ietf.org
To: Greg Mirsky <gregimirsky@gmail.com>
References: <155089851917.5347.209761560453230605.idtracker@ietfa.amsl.com> <CA+RyBmWkPWVHhRu52xfL7retKQzifXQmfyMfKQycaF8XtJSWtw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/104all/V5jzhb8u1TSkxppN1biva8tIDa0>
X-Mailman-Approved-At: Wed, 27 Feb 2019 08:10:48 -0800
Subject: Re: [104all] Further Clarification Re: IETF 104 Preliminary Agenda
X-BeenThere: 104all@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Official Communication about IETF 104 <104all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/104all>, <mailto:104all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/104all/>
List-Post: <mailto:104all@ietf.org>
List-Help: <mailto:104all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/104all>, <mailto:104all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2019 07:35:30 -0000

Agreed…

There are number of options for side meetings which can be used and IETF could assist in organizing it.

For instance - to reserve rooms on Saturday-Sunday-Friday_afternoon_ for possible use for side meetings.

I agree that IETF time should be used for IETF mostly and any modifications in the schedule should lower number of conflicts between IETF WG meetings.

dol@

> 25 февр. 2019 г., в 18:29, Greg Mirsky <gregimirsky@gmail.com>; написал(а):
> 
> Dear All,
> I'm disappointed to find that the number of conflicts for me at IETF-104 is as high as in Bangkok which was two times higher than at any meeting before. I'm stressed that I'll have to run from DetNet to BFD to deliver presentations on work being done, forget being able to follow the discussion adequately. If that's the new normal, then why to come to the meeting at all. 
> I strongly encourage IESG to let us use all available time for WG sessions and let attendees use their time for "corridor talks".
> 
> Regards,
> Greg
> 
> 
> 
> 
> On Fri, Feb 22, 2019 at 9:08 PM IETF Agenda <agenda@ietf.org <mailto: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 <https://mailarchive.ietf.org/arch/msg/ietf-announce/_JeP2fQ7rHPosZWpNtpl8I_uL5U>
> [2]  https://mailarchive.ietf.org/arch/msg/ietf-announce/H64AuTYhxsGqM1a8BfTkszCZyso <https://mailarchive.ietf.org/arch/msg/ietf-announce/H64AuTYhxsGqM1a8BfTkszCZyso>
> [3]  https://www.ietf.org/blog/ietf104-bofs/ <https://www.ietf.org/blog/ietf104-bofs/>
> 
> -- 
> 104all mailing list
> 104all@ietf.org <mailto:104all@ietf.org>
> https://www.ietf.org/mailman/listinfo/104all <https://www.ietf.org/mailman/listinfo/104all>