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

["Noveck, David" <[e-mail]>]

It is addressed in rfc56661bis-09, although the errata report is not mentioned.  Could do that it -10.

From: Zaheduzzaman Sarker <[e-mail]>
Sent: Wednesday, October 30, 2024 6:10 AM
To: Pali Rohár <[e-mail]>
Cc: David Noveck <[e-mail]>; Noveck, David <[e-mail]>; Zaheduzzaman Sarker <[e-mail]>; NFSv4 <[e-mail]>
Subject: Re: [nfsv4] Re: [Technical Errata Reported] RFC8881 (7386)

You don't often get email from [e-mail]<mailto:[e-mail]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

EXTERNAL EMAIL - USE CAUTION when clicking links or attachments


Verified!!

//Zahed

On Fri, Oct 25, 2024 at 12:58 PM Pali Rohár <[e-mail]<mailto:[e-mail]>> wrote:
Hello Zahed,

Were there some objections about this errata report?

Pali

On Friday 06 September 2024 11:17:56 Zaheduzzaman Sarker wrote:
> 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 <[e-mail]<mailto:[e-mail]>> 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 <
> > [e-mail]<mailto:[e-mail]>> 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 <[e-mail]<mailto:[e-mail]>>
> >>
> >> 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 -- [e-mail]<mailto:[e-mail]>
> > To unsubscribe send an email to [e-mail]<mailto:[e-mail]>
> >