Skip to main content

Add LAYOUT_WCC to NFSv4.2's Flex File Layout Type
draft-ietf-nfsv4-layoutwcc-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-nfsv4-layoutwcc@ietf.org, inacio@cert.org, nfsv4-chairs@ietf.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org, zahed.sarker.ietf@gmail.com
Subject: Protocol Action: 'Add LAYOUT_WCC to NFSv4.2's Flex File Layout Type' to Proposed Standard (draft-ietf-nfsv4-layoutwcc-07.txt)

The IESG has approved the following document:
- 'Add LAYOUT_WCC to NFSv4.2's Flex File Layout Type'
  (draft-ietf-nfsv4-layoutwcc-07.txt) as Proposed Standard

This document is the product of the Network File System Version 4 Working
Group.

The IESG contact persons are Zaheduzzaman Sarker and Francesca Palombini.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layoutwcc/


Ballot Text

Technical Summary

   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.

Working Group Summary

   Agreement was reached across the WG for this draft. This draft was relatively uncontroversial. Nothing has been threatened or no particular conflict present. 

Document Quality

   There are some significant implementations (in Linux) but not broadly yet
beyond Linux.  There is at least one server implementation.  The Linux
implementation is part of the kernel mainline, and so included in all
distributions. This is, however, an optional feature.

Personnel

   The Document Shepherd for this document is Christopher Inacio. The
   Responsible Area Director is Zaheduzzaman Sarker.


RFC Editor Note