IETF Logo Mail Archive

[nfsv4] [Technical Errata Reported] RFC8881 (7386)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 13 March 2023 14:51 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 DAF3EC13739B for <nfsv4@ietfa.amsl.com>; Mon, 13 Mar 2023 07:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.108
X-Spam-Level:
X-Spam-Status: No, score=-3.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.84, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 4U1hJDQ_cG7i for <nfsv4@ietfa.amsl.com>; Mon, 13 Mar 2023 07:51:50 -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 37C65C16B5BF for <nfsv4@ietf.org>; Mon, 13 Mar 2023 07:51:50 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 17E364C922; Mon, 13 Mar 2023 07:51:50 -0700 (PDT)
To: dnoveck@netapp.com, chuck.lever@oracle.com, martin.h.duke@gmail.com, Zaheduzzaman.Sarker@ericsson.com, davenoveck@gmail.com, beepee@gmail.com, inacio@cert.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc@pali.im, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230313145150.17E364C922@rfcpa.amsl.com>
Date: Mon, 13 Mar 2023 07:51:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Y-ZQZObzyy81X8V8IeAGyUxVBIs>
X-Mailman-Approved-At: Tue, 21 Mar 2023 16:33:50 -0700
Subject: [nfsv4] [Technical Errata Reported] RFC8881 (7386)
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: Mon, 13 Mar 2023 14:51:50 -0000

The following errata report has been submitted for RFC8881,
"Network File System (NFS) Version 4 Minor Version 1 Protocol".

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

--------------------------------------
Type: Technical
Reported by: Pali Rohár <rfc@pali.im>

Section: 18.46.3.

Original Text
-------------
                                                             Operations
   other than SEQUENCE, BIND_CONN_TO_SESSION, EXCHANGE_ID,
   CREATE_SESSION, and DESTROY_SESSION, MUST NOT appear as the first
   operation in a COMPOUND.

Corrected Text
--------------
                                                             Operations
   other than SEQUENCE, BIND_CONN_TO_SESSION, EXCHANGE_ID,
   CREATE_SESSION, DESTROY_SESSION, and DESTROY_CLIENTID, MUST NOT
   appear as the first operation in a COMPOUND.

Notes
-----
Section 18.50.3. DESCRIPTION of DESTROY_CLIENTID says

"DESTROY_CLIENTID MAY be preceded with a SEQUENCE"

and also says

"If DESTROY_CLIENTID is not prefixed by SEQUENCE, it MUST be the only operation in the COMPOUND request"

which implies that DESTROY_CLIENTID can appear as the first (and the only) operation in a COMPOUND.

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. 

--------------------------------------
RFC8881 (draft-ietf-nfsv4-rfc5661sesqui-msns-04)
--------------------------------------
Title               : Network File System (NFS) Version 4 Minor Version 1 Protocol
Publication Date    : August 2020
Author(s)           : D. Noveck, Ed., C. Lever
Category            : PROPOSED STANDARD
Source              : Network File System Version 4
Area                : Transport
Stream              : IETF
Verifying Party     : IESG

v2.30.2 | Report a Bug | By Email | System Status