Last Call: <draft-ietf-nfsv4-layrec-01.txt> (Reporting of Errors via LAYOUTRETURN in NFSv4.2) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 13 August 2024 14:39 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from [10.244.2.52] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id B9732C14F71B; Tue, 13 Aug 2024 07:39:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-nfsv4-layrec-01.txt> (Reporting of Errors via LAYOUTRETURN in NFSv4.2) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <172355999939.854616.8932766804072740757@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Tue, 13 Aug 2024 07:39:59 -0700
Message-ID-Hash: VVKAS7HFI62M5Z4LLA6H6R5LXEUKSM4N
X-Message-ID-Hash: VVKAS7HFI62M5Z4LLA6H6R5LXEUKSM4N
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-nfsv4-layrec@ietf.org, inacio@cert.org, nfsv4-chairs@ietf.org, nfsv4@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ZUjad1aexsHpHtsKonDkPk2Lw10>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

The IESG has received a request from the Network File System Version 4 WG
(nfsv4) to consider the following document: - 'Reporting of Errors via
LAYOUTRETURN in NFSv4.2'
  <draft-ietf-nfsv4-layrec-01.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-08-27. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   The Parallel Network File System (pNFS) allows for a file's metadata
   (MDS) and data (DS) to be on different servers.  When the metadata
   server is restarted, the client can still modify the data file
   component.  During the recovery phase of startup, the metadata server
   and the data servers work together to recover state (which files are
   open, last modification time, size, etc).  If the client has not
   encountered errors with the data files, then the state can be
   recovered, avoiding resilvering of the data files.  With any errors,
   there is no means by which the client can report errors to the
   metadata server.  As such, the metadata server has to assume that
   file needs resilvering.  This document presents an extension to
   RFC8435 to allow the client to update the metadata and avoid the
   resilvering.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layrec/



No IPR declarations have been submitted directly on this I-D.