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

Greg Mirsky <gregimirsky@gmail.com> Mon, 25 February 2019 15:29 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: recentattendees@ietfa.amsl.com
Delivered-To: recentattendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089C6130EE3; Mon, 25 Feb 2019 07:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 8TfV__D3ULsA; Mon, 25 Feb 2019 07:29:43 -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 517A312D4F2; Mon, 25 Feb 2019 07:29:43 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id q12so7220921lfm.0; Mon, 25 Feb 2019 07:29:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+a7xbNFk49SXUJBccELRhXc4xlnI3O0pQF4iVOrABec=; b=gPhOrxKMSTkCpCjGSB/K9NIIYo7Yo/Ss+Iv8pJnmQvgz6zvSU1A+V6keg1KyNbZoyK KdmiOtar/h+JHggx6/8qWsnfRhTE8UfqZsTZb+rJfwt8xRa8tIxiEueTn3LJUhha0NCU NqI91ZuOkLt1HxzQgbfOhDNj/+xj1rdIxitjYLHBpmvXxlP3ANMatP8LyNLtVYvyU7xB iVcs1pauOnd53B23SCiKw1BPqMdK7cjNhOoOz/PGswJWS2sHK0jV6UEJnfd7h+g4n2gR IPB21XS+NmN2kUslx02SLgu9aGit04fPscSYCHVJHcavJU4MFAFMMAmlVZuhbVtw4RXu J1iA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+a7xbNFk49SXUJBccELRhXc4xlnI3O0pQF4iVOrABec=; b=gBnvqsBNwHaMJcrLV0UgyHPxc4rM6NBLni479qVkIJRsHz4UoacfNn5nHbl9DBcrX5 uFWv6hREzbOfxTDv9xGcFcLAU/6SXsUOkRVsml/17DqKP8qGyLCvklRFtNgbeiw4oHXG zDc+t49iPpw6s4nF4wFLvmkBbv8M4t82nQezoeGKcUwP4zABdlaV6226pqWWjHu17EfZ NpYgNLpxT1mjAAAeAKoyhr65eStade63Sn3Oi4tUkRqEi68j8o9Bvkwr+3qR13njrRs2 YRhmmcN1JjFf/STdPpRxN57lfp4L1jJrgZje79MiJQ1EK2kSPfs+Fb+lwuVRkRpjVQPS WjNQ==
X-Gm-Message-State: AHQUAuZZdeUymLhZti8Hn5qolCPlrhE3rogGV0CZG2Ztmf0Kmmgjyqui XWCdATA+Hi3pLnwC7wnNa9aXUKFlG8q2r/rhePKA+yxt
X-Google-Smtp-Source: AHgI3IYlJP79yAVqkFAcsbUiMRJIMN5LE70eKHVPuODjkzfOTqVl33GtlAHMV1ph0qaxzFvXUFRShGo9t8M9C4a99sY=
X-Received: by 2002:a19:4948:: with SMTP id l8mr11443375lfj.156.1551108580824; Mon, 25 Feb 2019 07:29:40 -0800 (PST)
MIME-Version: 1.0
References: <155089851917.5347.209761560453230605.idtracker@ietfa.amsl.com>
In-Reply-To: <155089851917.5347.209761560453230605.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 25 Feb 2019 07:29:29 -0800
Message-ID: <CA+RyBmWkPWVHhRu52xfL7retKQzifXQmfyMfKQycaF8XtJSWtw@mail.gmail.com>
To: agenda@ietf.org
Cc: IETF Announcement List <ietf-announce@ietf.org>, wgchairs@ietf.org, recentattendees@ietf.org, IETF list <ietf@ietf.org>, 104all@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f7dcb40582b99b85"
Archived-At: <https://mailarchive.ietf.org/arch/msg/recentattendees/EHEI7Bk67TppAd0VWnbXzhu8TsM>
Subject: Re: [Recentattendees] [104all] Further Clarification Re: IETF 104 Preliminary Agenda
X-BeenThere: recentattendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Recent IETF Attendees <recentattendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recentattendees>, <mailto:recentattendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recentattendees/>
List-Post: <mailto:recentattendees@ietf.org>
List-Help: <mailto:recentattendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recentattendees>, <mailto:recentattendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2019 15:29:47 -0000

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>; 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
>