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

Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com> Fri, 06 September 2024 09:18 UTC

MIME-Version: 1.0
References: <20230313145150.17E364C922@rfcpa.amsl.com> <CADaq8jcGiuAEu65X6=y85ss2tT=hPe_F5d+=cLT4RGUxPjbWJQ@mail.gmail.com>
In-Reply-To: <CADaq8jcGiuAEu65X6=y85ss2tT=hPe_F5d+=cLT4RGUxPjbWJQ@mail.gmail.com>
From: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Date: Fri, 06 Sep 2024 11:17:56 +0200
Message-ID: <CAEh=tccR49cvFSnZ_Orw65s-tm+zEfavAaWFP-JpSPU+d0q1pA@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000a4da9206216fe27d"
Message-ID-Hash: PDL6JIKKCA52FO7R2VP5CRMFBHPZWJCL
CC: Dave Noveck <dnoveck@netapp.com>, Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, rfc@pali.im, NFSv4 <nfsv4@ietf.org>
Precedence: list
Subject: [nfsv4] Re: [Technical Errata Reported] RFC8881 (7386)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/GOgUL7e_nLmAcApFJMpdDS8CAsE>

Hi NFSv4,

If there is not objection to what David proposed ( verfiy the errata) by
end of next week, I will verity this technical errata.

//Zahed

On Fri, Sep 6, 2024 at 10:08 AM David Noveck <davenoveck@gmail.com> wrote:

> Should be verified.  Will address in next draft of
> draft-ietf-nfsv4-rfc5661bis.
>
> On Mon, Mar 13, 2023, 10:51 AM RFC Errata System <
> rfc-editor@rfc-editor.org> wrote:
>
>> 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
>>
> _______________________________________________
> nfsv4 mailing list -- nfsv4@ietf.org
> To unsubscribe send an email to nfsv4-leave@ietf.org
>

[nfsv4] [Technical Errata Reported] RFC8881 (7386) RFC Errata System
[nfsv4] Re: [Technical Errata Reported] RFC8881 (… David Noveck
[nfsv4] Re: [Technical Errata Reported] RFC8881 (… Zaheduzzaman Sarker