Adding an Uncacheable Attribute to NFSv4.2
draft-ietf-nfsv4-uncacheable-00
| Document | Type | Replaced Internet-Draft (nfsv4 WG) Expired & archived | |
|---|---|---|---|
| Author | Thomas Haynes | ||
| Last updated | 2025-11-07 | ||
| Replaces | draft-haynes-nfsv4-uncacheable | ||
| Replaced by | draft-ietf-nfsv4-uncacheable-files, draft-ietf-nfsv4-uncacheable-directories | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-nfsv4-uncacheable-files, draft-ietf-nfsv4-uncacheable-directories | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Network File System version 4.2 (NFSv4.2) allows a client to cache both metadata and data for file objects, as well as metadata for directory objects. While caching directory entries (dirents) can improve performance, it can also prevent the server from enforcing access control on individual dirents. Similarly, caching file data can lead to performance issues if the cache hit rate is low. This document introduces a new uncacheable attribute for NFSv4. Files and dirents marked as uncacheable MUST NOT be stored in client-side caches. This ensures data consistency and integrity by requiring clients to always retrieve the most recent data directly from the server. This document extends NFSv4.2 (see RFC7862).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)