[nfsv4] [Errata Verified] RFC8881 (7386)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 30 October 2024 10:09 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: nfsv4@ietf.org
Delivered-To: nfsv4@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EABB6C1516EB; Wed, 30 Oct 2024 03:09:27 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 52AB97F9E1; Wed, 30 Oct 2024 03:09:27 -0700 (PDT)
To: rfc@pali.im, dnoveck@netapp.com, chuck.lever@oracle.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20241030100927.52AB97F9E1@rfcpa.rfc-editor.org>
Date: Wed, 30 Oct 2024 03:09:27 -0700
Message-ID-Hash: F22YGGBKXI4EALFBQ3DMTL5JYOPQPDPZ
X-Message-ID-Hash: F22YGGBKXI4EALFBQ3DMTL5JYOPQPDPZ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: zaheduzzaman.sarker@nokia.com, iesg@ietf.org, nfsv4@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [nfsv4] [Errata Verified] RFC8881 (7386)
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/w3OHnusn7L386_veMbRIyyX34dU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>

The following errata report has been verified 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

--------------------------------------
Status: Verified
Type: Technical

Reported by: Pali Rohár <rfc@pali.im>
Date Reported: 2023-03-13
Verified by: Zaheduzzaman Sarker (IESG)

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.

--------------------------------------
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
Stream              : IETF
Verifying Party     : IESG