[nfsv4] Potential session at ietf113

David Noveck <davenoveck@gmail.com> Sun, 30 January 2022 14:32 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 416273A0C55; Sun, 30 Jan 2022 06:32:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 gMCBe-Apv-NL; Sun, 30 Jan 2022 06:32:23 -0800 (PST)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 B2E903A0C51; Sun, 30 Jan 2022 06:32:22 -0800 (PST)
Received: by mail-ej1-x633.google.com with SMTP id a8so34679290ejc.8; Sun, 30 Jan 2022 06:32:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=/26CEx6K1toR0wdyxPZiTIC8Aah14Zq89sR5fMi7u3Y=; b=oPkgBTCJdBnn4l5nKcxU52Ek67Fua2qmH9/BRyxU5Efxhvvy/bfSi+BOtlIsJhftbC dbUh4BYxWEkGWe31flIVTnmuLcrSOjKAmXbgUHbUKedXVtMveJmV+YA0lBWOxzBhywpX uixrAdo0mxjvQii6F3hipV3oIllqZ6czDrhUPJ/kUwsv5+oOssB3O/R7Nh+eUiCW3bPs aC630k5R1J6EEoRJLBKtYf4CuLBRluvP6iosNXZdPdycmLl3LpFaWm9AvWbVhiv7UshQ z3v+Q4HjgivWcLLULGuZ0wvTxrIZ7m20cYsDFbD/pyfjcqBBlI4C3Om+SuknN9ak275l 9jwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/26CEx6K1toR0wdyxPZiTIC8Aah14Zq89sR5fMi7u3Y=; b=frkZh431Qwku2+R9ANhErlIzMwHNH8cjLRRZ/eJid41D7/JW42i9zUAUa4jO0MEGHl sWb5T+Kk7wF93KGW+KWy1SEzs9iZOTp0U3ImBKR4LSXJ//n8coAoz3V9Tol6RJku7x9h 5g2rdpye+m0uOC4cu0jw69Oq2Fcx3lZOt6oXG0sKMS+tzuxTVnvIfIcLXiG8K3HKuQvz beV2S/Yq6oOs8tSGE6+4ntqxhlh/DFWq5hp+a2dMZPPBHohcJ2eKv/cNUIYIX44WQdhc AILQ8c+kAyTMlTrvjU95JYrymQFXyWzYk38frwN3UgU8t3Zqj9e55D7a+9dWVpb74YRK 1k1A==
X-Gm-Message-State: AOAM530UBi4oaac5H7hMPxGzFtLSHIMYvN6VM+qsjQ7k19+clzArrhej RC32NS6Zxk75AAS99vzTVBl6GbEAZgfBf3LMC5l4PpCx
X-Google-Smtp-Source: ABdhPJzm0fKV7qMV9cMMZce23dVkT9IiKsa8IgSs0aHPlmnccGWtWigz6Wz1yzmxlLB+jUICHmztlTl2uDC77fmkIn8=
X-Received: by 2002:a17:907:1c9f:: with SMTP id nb31mr14191938ejc.24.1643553139728; Sun, 30 Jan 2022 06:32:19 -0800 (PST)
MIME-Version: 1.0
From: David Noveck <davenoveck@gmail.com>
Date: Sun, 30 Jan 2022 09:32:08 -0500
Message-ID: <CADaq8jekTNYQC=y_avtUaDOXpYwYhi25P1N+aa_wVP3=JuwOzQ@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>, nfsv4-chairs <nfsv4-chairs@ietf.org>, nfsv4-ads@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001023b205d6cd89ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ie5iZOeKjD2mT2MlM4hYqvQx2oA>
Subject: [nfsv4] Potential session at ietf113
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: Sun, 30 Jan 2022 14:32:26 -0000

IETF113 is scheduled for 3/19-3/25 with an onsite component in Vienna,
although it seems likely that remote participation will be heavily used.
 My inclination is not to request a session (deadline is 2/4) as I expect
people are unlikely to want to travel to Vienna for this (Vienna caseloads
don't look bad but air travel is a crapshoot) or have a remote meeting in
Vienna working hours 9GMT+1).   I intend not to request a session.   Please
let me know soon if you think this is the wrong decision.

I don't think we want to go too long  without a working group meeting so we
need to look at our options for interim meeting.
My understanding, based on Zahed's comment that scheduling an
interim meeting within a month of the official meeting is frowned upon.
This leaves us a choice between trying to schedule something before 2/19 or
after 4/25.   So, I'm assuming the latter choice and will send email
about scheduling/contents within the next few weeks.  Again, if  you
have issues with this choice,  please let me and the working group know, as
soon as you can.