[nfsv4] Fwd: Post-IETF-107 Recommended Virtual Interim Schedule

David Noveck <davenoveck@gmail.com> Fri, 13 March 2020 21:33 UTC

Return-Path: <davenoveck@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72CF13A1066 for <nfsv4@ietfa.amsl.com>; Fri, 13 Mar 2020 14:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 Mc0QwJeFRwa1 for <nfsv4@ietfa.amsl.com>; Fri, 13 Mar 2020 14:33:31 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 ED5083A1065 for <nfsv4@ietf.org>; Fri, 13 Mar 2020 14:33:28 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id i24so9850462eds.1 for <nfsv4@ietf.org>; Fri, 13 Mar 2020 14:33:28 -0700 (PDT)
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=qFtApvYLLrh/h/swdmxI9vZRNVBtJE5JhpQSoE7kYJI=; b=bPxhVd6oE/TlP27n5v8+MiCWhg77BnHo3P2YhCRnGF0DrRdRh7M+AjqeurthE0FHwz xaQZzBPyJK+3j8q09h7/Vamwvl5StkwDkGwoXh0JewarWwufwtv7lALW3mFduJBsNB05 6Ww41ExkHoYBx5T9iqxCl3BGTvOWWTMlh5fixscrqhDe0CEMxRnV6ObbRldlE2VnJ++U HGlq2WArcPnQ5eoxu90qSih1DAvUCLJhY0IkW4BNluX9SvHqAWQ3kdvD0VboAnWB0aM2 PCNhNtpu2h6RLKI0dzj5Pd1XLX8y2YoiAlQcnEcn88ztN5lHtFSGPygWPa+rGa35UXA9 IUNw==
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=qFtApvYLLrh/h/swdmxI9vZRNVBtJE5JhpQSoE7kYJI=; b=U2mpMEnIMz64yZgTWcLnda3uIFnqrapf1ZSbV1P3t4T/hTwVpWyfgAoXSiuXESZANQ 24LnIykAYaH5NwarpQHCYx/Bx/vTElKwIP7W+hmb5Zds45hXwO7LdakenB4xN7Zns/Hy bSXKq8qqYTLd8XyxxQZy8V/dHI2ZP6Flry/9+zQXJh8o/9FJcgrAqUia1EQwfURhttKz F0GN5NsXy1yh4jq5uyTZEQgDDKJFW24mAfEF4nGpeIbK1W3Lw5dstkI/nJDEyoLhDbgT 5BZeqUpKEJ6BQ6P2toGfR2IcSpC53jTQOeghK7hGlnzF0Wi/+BBdFaP67thcZ0dxN2Vd 071w==
X-Gm-Message-State: ANhLgQ27Id3FawLKw5tGT4lK2GNdVrSb2srxvcfnuFfv93p4nPepueSu TIaTh9QLTdgNfHoLG3QP09mz3oQaUkjPHgNH09jgMw==
X-Google-Smtp-Source: =?utf-8?q?ADFU+vvJr09v4+TPHsG4Kc8OlU/e3svW2xobsWuW3X23?= =?utf-8?q?qLGCLdGV7mTK4vgpBCPnTz+6OzVlW8QOUlIsOCjrnlV28Bw=3D?=
X-Received: by 2002:aa7:d793:: with SMTP id s19mr15538550edq.306.1584135206697; Fri, 13 Mar 2020 14:33:26 -0700 (PDT)
MIME-Version: 1.0
References: <EE84F8E3-3EF5-430E-B780-3AC2C148927D@cooperw.in>
In-Reply-To: <EE84F8E3-3EF5-430E-B780-3AC2C148927D@cooperw.in>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 13 Mar 2020 17:33:15 -0400
Message-ID: <CADaq8jf1rw8B6a6YT-4DA2TreS6NuEsVAq1EugHVgJE0c44dAA@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="000000000000457df205a0c33842"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/fsGZA5EVwQAVPTsSpqZbPGZopeQ>
Subject: [nfsv4] Fwd: Post-IETF-107 Recommended Virtual Interim Schedule
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 21:33:34 -0000

It seems that we now have an IETF recommendation as to interim meeting
dates which Magnus tells us we are free to ignore (within limits).   I thnk
we have settled on 10AM-noon Pacific  as the meeting time.   The simplest
way to have  two meetings one week apart, as previously suggested, without
having to worry about potential conflicts is to have them 4/22 and 4/29.
If people are OK with that, I'll make the official request.

---------- Forwarded message ---------
From: Alissa Cooper <alissa@cooperw.in>
Date: Fri, Mar 13, 2020 at 12:52 PM
Subject: Post-IETF-107 Recommended Virtual Interim Schedule
To: IETF WG Chairs <wgchairs@ietf.org>


Dear chairs,

The IESG has put together a recommended virtual interim schedule in the
absence of an in-person IETF 107: <
https://trac.ietf.org/trac/wgchairs/raw-attachment/wiki/WikiStart/April2020-RecommendedSchedule.pdf>gt;.
We are recommending this schedule as a starting point. Each time slot in
the original in-person meeting schedule corresponds to one day in this
schedule (in UTC). As the original schedule avoided WG and RG conflicts to
the maximum extent possible, working groups and research groups can be
reasonably sure that most participants will not have a conflict with
another IETF interim meeting on the same day. We have avoided Fridays,
Saturdays, Sundays, and some common bank holidays.

Groups are free to choose a time within their recommended day that works
for most participants in the group, with the knowledge that in some time
zones it may be the day before or the day after. We realize that the day
recommended for your group may not work for your group. Working groups are
free to request a session on a different day than their recommended day or
to request additional ones.

You may request a virtual interim meeting using the form at <
https://datatracker.ietf.org/meeting/interim/request>gt;.

Because we are anticipating an increased volume of virtual interims, AD (or
IRTF chair) approval will be required to schedule a virtual interim meeting
through the beginning of IETF 108 -- even if requested for the day
recommended below. We will be assessing conflicts as well as the overall
spread of interim meetings and how that spread may affect participants in
different time zones. We may ask you to select a different time based on
these factors.

If you do not choose to use your recommended day, we recommend polling your
group to determine suitable times for a meeting. If your group holds
interims regularly, please be cognizant of which time zones are
disadvantaged by your scheduling choices and try to avoid consistently
scheduling virtual interims that disadvantage the same set of participants.
The meeting planner located at <
https://www.timeanddate.com/worldclock/meeting.html> may be a useful tool.

If you are going to poll your group to find a suitable virtual interim
slot, please review the existing schedule of upcoming virtual interim
meetings <https://datatracker.ietf.org/meeting/upcoming>. Review your
group's most recent list of conflicts <
https://datatracker.ietf.org/meeting/requests>gt;. Please do not request a
virtual interim slot that conflicts with an already-scheduled interim for a
different group that is either (a) within the same IETF area as your group,
or (b) on your conflicts list.

Finally, we recommend reviewing the IESG guidance on interim meetings which
provides further details: <
https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/
>

When working group chairs schedule a date and time for the meeting, it will
automatically update the calendar in datatracker: <
https://datatracker.ietf.org/meeting/upcoming>gt;.

Thanks,
Alissa Cooper on behalf of the IESG