[nfsv4] [Editorial Errata Reported] RFC8276 (7004)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 23 June 2022 12:18 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 C9726C184E70 for <nfsv4@ietfa.amsl.com>; Thu, 23 Jun 2022 05:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 nxmNyaIlGyDT for <nfsv4@ietfa.amsl.com>; Thu, 23 Jun 2022 05:18:19 -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 0BEC6C131813 for <nfsv4@ietf.org>; Thu, 23 Jun 2022 05:18:18 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id AAE5EAEA1; Thu, 23 Jun 2022 05:18:18 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: radchenkoy@gmail.com, manoj.naik@nutanix.com, eshel@us.ibm.com, nfsv4@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220623121818.AAE5EAEA1@rfcpa.amsl.com>
Date: Thu, 23 Jun 2022 05:18:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/i0l8oFcyVyMo7_Icd55daW-GRRw>
Subject: [nfsv4] [Editorial Errata Reported] RFC8276 (7004)
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: Thu, 23 Jun 2022 12:18:22 -0000
The following errata report has been submitted for RFC8276, "File System Extended Attributes in NFSv4". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7004 -------------------------------------- Type: Editorial Reported by: Yuri Radchenko <radchenkoy@gmail.com> Section: 8.4.5 Original Text ------------- | LISTXATTRS | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, | | | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED, | | | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE, | | | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR, | | | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM, | | | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE, | | | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP, | | | NFS4ERR_SERVERFAULT, NFS4ERR_STALE, Corrected Text -------------- | LISTXATTRS | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, | | | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED, | | | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE, | | | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR, | | | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM, | | | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE, | | | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP, | | | NFS4ERR_SERVERFAULT, NFS4ERR_STALE, NFS4ERR_TOOSMALL Notes ----- Section 8.4.3.3. DESCRIPTION says about NFS4ERR_TOOSMALL status code: "If the server is unable to return a single xattr name within the maxcount limit, the error NFS4ERR_TOOSMALL will be returned to the client." But this status code not specified in section 8.4.5. Valid Errors for LISTXATTRS operation. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- 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 Verifying Party : IESG
- [nfsv4] [Editorial Errata Reported] RFC8276 (7004) RFC Errata System
- Re: [nfsv4] [Editorial Errata Reported] RFC8276 (… David Noveck