The IESG has approved the following document: - 'Adding an Uncacheable File Data Attribute to NFSv4.2' (draft-ietf-nfsv4-uncacheable-files-15.txt) as Proposed Standard
This document is the product of the Network File System Version 4 Working Group. The IESG contact persons are Gorry Fairhurst and Mike Bishop. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-nfsv4-uncacheable-files/ Technical Summary This document introduces the fattr4_uncacheable_file_data attribute (FATTR4_UNCACHEABLE_FILE_DATA, attribute number 87) for NFSv4.2. The attribute is a per-file boolean that lets a server or administrator indicate that client-side caching of file data is unsuitable for a particular file. When it is set, clients suppress write-behind caching, transmitting WRITE data promptly rather than combining multiple writes, and suppress read caching, revalidating the change attribute and file size before serving cached data to applications. The attribute is advisory and is not a security boundary. It is motivated by High-Performance Computing workloads in which multiple clients write disjoint byte ranges of a shared file and require predictable data visibility. The extension follows the NFSv4 minor version extension mechanism of RFC 8178 and does not formally update RFC 7862. Working Group Summary Was there anything in the WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Document Quality Two prototypes are reported in Section 6: a Hammerspace server and a Linux NFS client. The Linux prototype applies O_DIRECT-like behavior and revalidates file-associated metadata before serving cached state to applications. Experience with it indicates the attribute delivers much of the practical benefit of O_DIRECT without requiring application modification. The normative XDR is two declarations, and the extraction script in Section 8 produces output that appends cleanly to the NFSv4.2 XDR base from RFC 7863. Personnel Document Shepherd: Chuck Lever <[email protected]> Responsible Area Director: Gorry Fairhurst (Web and Internet Transport) IANA Note The document claims attribute number 87. Numbered FATTR4 attributes are allocated by IETF publication of Standards Track RFCs rather than through an IANA registry. RFC Editor Note Please remove "Note to Readers" after the abstract when published. _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
