Re: [nfsv4] Draft agenda

David Noveck <davenoveck@gmail.com> Sun, 26 March 2023 11:49 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 EC531C14CE40 for <nfsv4@ietfa.amsl.com>; Sun, 26 Mar 2023 04:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fAwzsfpC2SjN for <nfsv4@ietfa.amsl.com>; Sun, 26 Mar 2023 04:49:29 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399A2C14CE36 for <nfsv4@ietf.org>; Sun, 26 Mar 2023 04:49:29 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id o82so1631465qka.11 for <nfsv4@ietf.org>; Sun, 26 Mar 2023 04:49:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679831368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rANNMsCmHDX1BaprmGpJDUT9VaP9vo3+YkQA2/5H3TE=; b=DBAhu2dEIVGm4kahqAXokX9AxjZC+2BGPq7c3zcR2QesHrUkuZqOODCjdXMbzHccpu HwLXlN6zWUVG+7GNek1udwMI/ZAA95uk1p8yLATrh+BXXwu/1TVSs+Rg74z9ouT5PxPQ zvaXYHc29Z249wtZztHo5zXWLi9+T8iAMWplygny0IfKDHHbhPzMO1iWgRpDCHOA0wL6 U2GR9JYPzT5Zv6Zdls3bmeDS3J0lYvVJtkAiPEYuCE4tTyvK6ZWnM7R8I9v7ExiAEgun J2zCLSWFBQe4kFZrZfAJXrA20WyrqKH1sB+ULY8APgAsjZKcKZWA/gli7aYN4d7rrN1b LBPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679831368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rANNMsCmHDX1BaprmGpJDUT9VaP9vo3+YkQA2/5H3TE=; b=k8SFwTYpZKMmMRMk/bkrwfQoBlcYUo2jJhBIfyYsURjpAPJNNvpI/p97eGaUA4jcMo E/EE7w6DdkZUrVzpXKn7UCacrCz2UKFF1Fc4wvi4I13rFgJ5HlT0huu96hhaEMp1K7WO AQE/lrGOb06wqzFIobk2TdEzUUqV6KBMii9D76hVbAlnz+OVTi7UEp6YvE/Omm8+Sr4h WBGQ83Mo0/q5tqM4PXDX2J4/D9nuodjJjuF28EjJCPx5T4VfCaJ9aLUZw4hKyQN8VBE0 jJtLAFnjmHDx/XbuWz8X+EMhQqPekbZejoktpQi54wCWG6hh1Jja7WcIhdBkVo6rXQjS lijw==
X-Gm-Message-State: AAQBX9dDJY7hprPcgeKjh70kWUapobO+r1Q7P1sihxJWW4Re/VjYHhcs F3JAGzf5LgHxgTmIVlAr32EunSJSOzkQ+2ujMJo=
X-Google-Smtp-Source: AKy350aPn7rm9W81lI+Iff/RAl/sZqEtkV6hnlNrM7DmqT/CxAxHUJIN4au5rluJAQiv/SCrY6QTh6GNhtrlTQifE2I=
X-Received: by 2002:a05:620a:678:b0:748:49ac:1e0f with SMTP id a24-20020a05620a067800b0074849ac1e0fmr1561701qkh.7.1679831367882; Sun, 26 Mar 2023 04:49:27 -0700 (PDT)
MIME-Version: 1.0
References: <0B984CCD-5D9A-4033-A144-EB63E07B47E1@cert.org> <CADaq8jeQ0saw0gCoqumyFjO5juctBe3-17qehn0Bexp1kZPyAA@mail.gmail.com> <F09E3D73-497C-48C9-A18D-7AE47EE03C63@cert.org> <MN2PR19MB40457F8E1F6B453FD0F5F47283BA9@MN2PR19MB4045.namprd19.prod.outlook.com> <EC55BCD1-C5C3-4FFF-8ABF-DEAA1081A68F@cert.org> <80FAFC2E-4FE1-4012-B434-95D9064258CB@cert.org>
In-Reply-To: <80FAFC2E-4FE1-4012-B434-95D9064258CB@cert.org>
From: David Noveck <davenoveck@gmail.com>
Date: Sun, 26 Mar 2023 07:49:16 -0400
Message-ID: <CADaq8jc15xvYzb+0SSPd5FRahm370HZqNCfNBVbofFZQbf+AMQ@mail.gmail.com>
To: Chris Inacio <inacio@cert.org>
Cc: "Black, David" <David.Black@dell.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f71c7705f7cc37fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/yq2nSz2WLE5BOMqjC_rZAzfaRnQ>
Subject: Re: [nfsv4] Draft agenda
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
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, 26 Mar 2023 11:49:33 -0000

You need to post the date and time of the meeting for non-JST participants
(UTC is ok) and provide links for participation.


On Sat, Mar 25, 2023, 11:28 PM Chris Inacio <inacio@cert.org> wrote:

> All,
>
> IETF week has started - so here is the final agenda (until people bash
> it.). This is mostly just taking David Black’s asks into account.
>
> Also looking for slides from speakers if you haven’t sent them in, please
> send them to nfsv4-chairs@ietf.org as soon as reasonable.  Ideally, all
> slides are in by Thursday midday Japan time.  If you have already sent your
> slides in - thank you.  I definitely want to acknowledge that we already
> have some slides.  If you don’t intend to have slides, please let the
> chairs know that as well.
>
>
> ====
>
> IETF-116 NFSv4 WG Agenda
> Welcome (back) to Yokohama
>
> * Chairs Welcome / Agenda Bash (chairs)
> * WG status and interim meetings (5 min - chairs/all)
>         - interim meetings and draft progress
> * pNFS layout using NVMe (15 min - Hellwig)
> * RDMA Commit (10 min - Tom Talpey)
> * 5661-bis (20 min - Noveck/Chairs)
> * Delstid - Extending opening of files / Reporting of Errors via
> LAYOUTRETURN in NFSv4.2 (15 min - Haynes)
> * Implementation Status (10 min - Lever)
> * Sequence ID Calibration (10 min - Yang Jing)
>
> * end of IETF-116, safe travels
>
>
> Thank you,
> Nfsv4 chairs
>
> ----
> Chris Inacio
> inacio@cert.org
>
>
>
> On Mar 11, 2023, at 2:01 AM, Chris Inacio <inacio@cert.org> wrote:
>
> Hi Dave,
>
>
> Thanks for the feedback.
>
> As to those within the meeting changes, I think that’s all doable.  BUT,
> before I do those changes, Christoph is on site but leaving before the
> Friday meeting time.  We would like to change the actual WG time to
> accommodate that if possible.  Stay tuned - and then keep me honest!  You
> might need another round of suggestions IF we can get the meeting time
> changed; so I would look to hold off till then.
>
>
> Regards,
> ----
> Chris Inacio
> inacio@cert.org
>
>
>
> On Mar 10, 2023, at 11:56 AM, Black, David <David.Black@dell.com> wrote:
>
> Chris and Dave,
>
> > The timing of this meeting really sucks for those in EDT.   This was not
> supposed to happen.
>
> timeanddate.com says that Friday, March 31 12:00pm (noon) in Yokohama
> (JST) is 11:00pm on Thursday, March 30 in Boston (EDT).
>
> I believe that I can make that time work.  It would help if the agenda
> were bashed so that Christoph’s pNFS layout using NVMe draft comes earlier
> with the aim of covering it (and Tom’s RDMA commit draft) before midnight
> EDT.  I’d suggest moving the pNFS layout using NVMe draft to follow the
> RDMA commit draft, if that doesn’t cause problems for other presenters.  Is
> that possible?
>
> Thanks, --David
>
> *From:* nfsv4 <nfsv4-bounces@ietf.org> *On Behalf Of *Chris Inacio
> *Sent:* Friday, March 10, 2023 9:31 AM
> *To:* David Noveck
> *Cc:* NFSv4
> *Subject:* Re: [nfsv4] Draft agenda
>
>
> [EXTERNAL EMAIL]
>
>
>
>
> Also, I would like to hear about any issues with the time slot as
> scheduled.
>
>
> You say you would like to hear about these issues but I don't believe you.
> But at least, you are willing to hear about these issues.
>
> The timing of this meeting really sucks for those in EDT.   This was not
> supposed to happen.
>
>
>
> Dave - as you know, I put comments in the schedule request asking for a
> time slot that was first thing in the morning to be as accommodative as
> possible to the participants I was aware of.  We didn’t get that slot.  I
> can have empathy without power to change the circumstances.  They powers
> that be, trying to solve their impossible scheduling problems, don’t give
> me preference (or you, or any of the other participants or chairs.) I would
> like this to be the best possible time slot for the working group.  I will
> ask again when I understand what people would like - but it doesn’t mean I
> can get it.
>
> With all that said - everyone, I’m still open to hearing feedback.
>
> Thanks
> Chris (as a chair)
>
>
>
>