Re: [nfsv4] Possible need for wg meeting in or after IETF 114

Christoph Hellwig <hch@lst.de> Thu, 02 June 2022 16:54 UTC

Return-Path: <hch@lst.de>
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 67DF9C14CF01; Thu, 2 Jun 2022 09:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
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 TBjHtmgOnEiN; Thu, 2 Jun 2022 09:54:25 -0700 (PDT)
Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F040C14CF14; Thu, 2 Jun 2022 09:54:24 -0700 (PDT)
Received: by verein.lst.de (Postfix, from userid 2407) id 9C0F768AFE; Thu, 2 Jun 2022 18:54:20 +0200 (CEST)
Date: Thu, 02 Jun 2022 18:54:20 +0200
From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "Noveck, David" <David.Noveck=40netapp.com@dmarc.ietf.org>, "nfsv4-chairs@ietf.org" <nfsv4-chairs@ietf.org>, "nfsv4-ads@ietf.org" <nfsv4-ads@ietf.org>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Message-ID: <20220602165420.GA14677@lst.de>
References: <MN2PR06MB5597860F139142B4E5601803E1DC9@MN2PR06MB5597.namprd06.prod.outlook.com> <38D9A018-27A3-4597-9784-F63F1F756664@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <38D9A018-27A3-4597-9784-F63F1F756664@oracle.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/iwCa7F5gya1PuFbChRhfV5MFF0o>
Subject: Re: [nfsv4] Possible need for wg meeting in or after IETF 114
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: Thu, 02 Jun 2022 16:54:26 -0000

On Thu, Jun 02, 2022 at 01:56:03PM +0000, Chuck Lever III wrote:
> > I'd like to get working group input regarding:
> > - what you would be be willing and able to lead a discussion of
> > - what you want to hear discussed and possibly contribute to
> > - whether there are scheduling or other considerations that argue for an IETF meeting (7/23-7/29) or a post-IETF114 interim several weeks later.
> 
> One more item I'd like to discuss: Is there /any/ way to get the
> pNFS with NVMe layout draft unstuck?

We just need someone with enough interest to replace the reference
to the NVMe to SCSI translation spec/whitepaper with proper normative
text.  In them meantime the biggest part of the Linux implementation of
this draft did land upstream already :)