Add LAYOUT_WCC to NFSv4.2's Flex File Layout Type
draft-ietf-nfsv4-layoutwcc-01
| Document | Type |
Expired Internet-Draft
(nfsv4 WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas Haynes , Trond Myklebust | ||
| Last updated | 2023-10-01 (Latest revision 2023-03-30) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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 Parallel Network File System (pNFS) Flexible File Layout 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 a refinement to RFC8435 to allow the client to update the metadata server to changes on the data server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)