[nfsv4] [Errata Held for Document Update] RFC5661 (4492)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 25 October 2019 08:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 03FAA12001E; Fri, 25 Oct 2019 01:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPSrCk1RUhOL; Fri, 25 Oct 2019 01:36:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82F8512026E; Fri, 25 Oct 2019 01:36:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 446C4F4071F; Fri, 25 Oct 2019 01:36:06 -0700 (PDT)
To: davenoveck@gmail.com, shepler@storspeed.com, mike@eisler.com, dnoveck@netapp.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: magnus.westerlund@ericsson.com, iesg@ietf.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20191025083606.446C4F4071F@rfc-editor.org>
Date: Fri, 25 Oct 2019 01:36:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/uNA7TUskREV5v2_f0KHztfDQmC0>
Subject: [nfsv4] [Errata Held for Document Update] RFC5661 (4492)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 25 Oct 2019 08:36:08 -0000

The following errata report has been held for document update 
for RFC5661, "Network File System (NFS) Version 4 Minor Version 1 Protocol". 

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

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: David Noveck <davenoveck@gmail.com>
Date Reported: 2015-10-05
Held by: Magnus Westerlund (IESG)

Section: 18.17.4

Original Text
-------------
If the server does not support named attributes for the current 
filehandle, an error of NFS4ERR_NOTSUPP will be returned to the 
client.

Corrected Text
--------------
If the server does not support named attributes for file system 
objects on the file system associated with the current filehandle, 
an error of NFS4ERR_NOTSUPP will be returned to the client.

Notes
-----
There are a number of situations in which, a server might not support named attributes on particular file system objects.   A number of cases concern doing an OPENATTR on a named attribute directory or named attribute and are mentioned in the immediately preceeding section.
Aside from that contradiction, many implementations might allow named attributes on 
symbolic likes or special files.  The existing text would require NFS4ERR_NOTSUPP rather 
than NFS4ERR_WRONG_TYPE to be returned in such cases, causing the client to conclude 
incorrectly that named attribute support is not present for the file system in question, or at 
least be uncertain about the presence/absence of such support.

--------------------------------------
RFC5661 (draft-ietf-nfsv4-minorversion1-29)
--------------------------------------
Title               : Network File System (NFS) Version 4 Minor Version 1 Protocol
Publication Date    : January 2010
Author(s)           : S. Shepler, Ed., M. Eisler, Ed., D. Noveck, Ed.
Category            : PROPOSED STANDARD
Source              : Network File System Version 4
Area                : Transport
Stream              : IETF
Verifying Party     : IESG