[nfsv4] [Errata Verified] RFC8276 (7050)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 26 July 2022 20:27 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F14BFC13C21D; Tue, 26 Jul 2022 13:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6P1_tdbCTa7e; Tue, 26 Jul 2022 13:27:34 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F238C131949; Tue, 26 Jul 2022 13:27:34 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DF3BA4C29F; Tue, 26 Jul 2022 13:27:33 -0700 (PDT)
To: anton.rang@dell.com, manoj.naik@nutanix.com, eshel@us.ibm.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, nfsv4@ietf.org, iana@iana.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220726202733.DF3BA4C29F@rfcpa.amsl.com>
Date: Tue, 26 Jul 2022 13:27:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ZDTvha8xe8cab_fcCtPtCc-8zFU>
Subject: [nfsv4] [Errata Verified] RFC8276 (7050)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2022 20:27:38 -0000

The following errata report has been verified for RFC8276,
"File System Extended Attributes in NFSv4". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7050

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Anton Rang <anton.rang@dell.com>
Date Reported: 2022-07-26
Verified by: RFC Editor  

Section: 1

Original Text
-------------
   This document discusses (in Section 5) the reasons that NFSv4-named
   attributes, as currently standardized in [RFC5661], are unsuitable
   for representing xattrs.  Instead, it describes a separate protocol


Corrected Text
--------------
   This document discusses (in Section 6) the reasons that NFSv4-named
   attributes, as currently standardized in [RFC5661], are unsuitable
   for representing xattrs.  Instead, it describes a separate protocol


Notes
-----
The reference to the discussion of named attributes has the wrong section number.

--------------------------------------
RFC8276 (draft-ietf-nfsv4-xattrs-06)
--------------------------------------
Title               : File System Extended Attributes in NFSv4
Publication Date    : December 2017
Author(s)           : M. Naik, M. Eshel
Category            : PROPOSED STANDARD
Source              : Network File System Version 4
Area                : Transport
Stream              : IETF