Re: [nfsv4] New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt

> On Feb 19, 2023, at 3:53 PM, tigran.mkrtchyan@desy.de wrote:
> 
> Hi Tom, 
> I like the idea. It looks like that the draft is limited only to NFSv3 based flexfiles layouts.

Yes, despite Dave earlier bringing this up, I have clung to the notation that it was generic.

> Neither nfsv41_files nor flexfiles layouts allow GETATTR requests to be sent to data servers.
> Thus only in responses to READ or WRITE over v3 clients will get the wcc informationHowever the draft position itself to be more generic. 

I will fix this.

> Do I miss something? 
> Best regards, 
> - Tigran
> -------- Original message --------
> From: Thomas Haynes
> Date: Thu, Feb 16, 2023, 00:02
> To: NFSv4
> Subject: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt
> 
> 
> Hi,
> 
> As part of the review of delstid, it was suggested that I pull this part out of that document and create a new draft.
> 
> This then is that result.
> 
> I ask the working group to adopt this draft was a WG one. This is work that had previously been accepted as part of the delstid one.
> 
> Thanks,
> Tom
> 
> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt
> Date: February 15, 2023 at 2:58:00 PM PST
> To: "Thomas Haynes" <loghyr@hammerspace.com>, "Trond Myklebust" <trondmy@hammerspace.com>
> 
> 
> A new version of I-D, draft-haynes-nfsv4-layoutwcc-00.txt
> has been successfully submitted by Thomas Haynes and posted to the
> IETF repository.
> 
> Name: draft-haynes-nfsv4-layoutwcc
> Revision: 00
> Title: Add LAYOUT_WCC to NFSv4.2
> Document date: 2023-02-15
> Group: Individual Submission
> Pages: 9
> URL:            https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-haynes-nfsv4-layoutwcc/
> Html:           https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-00.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-haynes-nfsv4-layoutwcc
> 
> 
> Abstract:
>  The Parallel Network File System (pNFS) allows for a file's metadata
>  (MDS) and data (DS) to be on different servers.  It does not provide
>  a mechanism for the data server to update the metadata server of
>  changes to the data part of the file.  The client has knowledge of
>  such updates, but lacks the ability to update the metadata server.
>  This document presents several refinements to both RFC8881 and
>  RFC8434 to allow the client to update the metadata server to changes
>  on the data server.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> 
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4