IETF Logo Mail Archive

Re: [nfsv4] Draft agenda

David Noveck <davenoveck@gmail.com> Fri, 10 March 2023 18:46 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 80410C14CEF9 for <nfsv4@ietfa.amsl.com>; Fri, 10 Mar 2023 10:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_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 RoMKQyRRJ-bS for <nfsv4@ietfa.amsl.com>; Fri, 10 Mar 2023 10:46:55 -0800 (PST)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 D57C6C153CBB for <nfsv4@ietf.org>; Fri, 10 Mar 2023 10:46:55 -0800 (PST)
Received: by mail-qk1-x731.google.com with SMTP id p12so2340297qki.1 for <nfsv4@ietf.org>; Fri, 10 Mar 2023 10:46:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678474015; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iRZ8F/CZPuIRa/4wxrhyEg7sq1LRFJs+1nsviIk/o1k=; b=RP1xnTHUXNpoT2wUBS9QbdSbFjKFLzvx4snBjUmRKVY6kFb4FZAySIsCNcXs+Gia8C KDXSzrHOG6yGz6PzglFZXdOsexwJdu3d9WYDiQdRmoEK5PFXqlOt81jky/KfyWOkkJUa ggcEFELVsj4YA1m6dAJ45e9nAphyXpOKcmoKmSthKGiWh6Wn4h+z45wr84eoC0OB3HqS Siy91K8PjKw/M+TeLIVFcAye53ourp55vRGxdw4uisabBHhyt64sf4FLMQGosQL1aNJP QgDbRTCB56vcOOCNFDXZfWTK6yUBf4hJyGItvrW25GNVDWXf2C3LAefbSpbIHS5WXTuk qs4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678474015; 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=iRZ8F/CZPuIRa/4wxrhyEg7sq1LRFJs+1nsviIk/o1k=; b=rXXP+AUYkU2Imz9qNZRcwdIZz+/EFQbEC9/weUg856vkKFlUmtTe30nNT3rpB7gqZT s237l9QIkJkHH9LvIHko375A8bz3nseH5J393KAvjb3YC/r9tnd6YIEumJFw+j54dIDn RNKkcPSVtgabrdt4pLTpgBia1YZFLLooopZpE+5mAAzJu6w4kJ/3tA4pERZdFNKKffii Y+PUms6SSbjFbtyc4fOaSXMTcXj4U7iS3JbhuvQRzv/GzvxLrDvxvsrgDjYDJH+zhSv6 pb750UmuYGROPSzAm7DxXymBgUICmAh4s9VywvGGfwAzuJeFFB1LGZ3MoQwL4FLyp8Eg retQ==
X-Gm-Message-State: AO0yUKXc0/9UGJy/1xPbk8XWQbf73Zo4mATAk1wk3bkqE8gHNNTQHp8w 0t5p9b7dfVaRzqlgr0dvXAsmpmlUX8Sx5zdy8sI=
X-Google-Smtp-Source: AK7set/G0kvwMRZHUbpCbc3LPxZ2Or38V4fD5QkqCfsRuesrTRej/pBw2vaUzcJ7+zmIY2BLXkIA5+8FM7Tyg3g588U=
X-Received: by 2002:a05:620a:3c3:b0:743:5877:8aae with SMTP id r3-20020a05620a03c300b0074358778aaemr1065419qkm.4.1678474014763; Fri, 10 Mar 2023 10:46:54 -0800 (PST)
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>
In-Reply-To: <MN2PR19MB40457F8E1F6B453FD0F5F47283BA9@MN2PR19MB4045.namprd19.prod.outlook.com>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 10 Mar 2023 13:46:44 -0500
Message-ID: <CADaq8jdt1S99=Yq++pyAJdZLQyJ6feU=79gbDmAxOm3ZUUWRVg@mail.gmail.com>
To: "Black, David" <David.Black@dell.com>
Cc: Chris Inacio <inacio@cert.org>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a30a705f6902f00"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/PI0f48c6AsA6YjR77qg27KW2CyQ>
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: Fri, 10 Mar 2023 18:46:59 -0000

It makes problems for me.  Please drop it.

On Fri, Mar 10, 2023, 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)
>
>
>
>
>
>
>
>
>

v2.23.0 | Report a Bug | By Email