Re: [nfsv4] [Technical Errata Reported] RFC5661 (5040)
Megan Ferguson <mferguson@amsl.com> Tue, 13 June 2017 05:18 UTC
Return-Path: <mferguson@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 23A7F1294C4 for <nfsv4@ietfa.amsl.com>; Mon, 12 Jun 2017 22:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 ROaO793ierBN for <nfsv4@ietfa.amsl.com>; Mon, 12 Jun 2017 22:18:57 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F43C126CD6 for <nfsv4@ietf.org>; Mon, 12 Jun 2017 22:18:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1181D1CA41D; Mon, 12 Jun 2017 22:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flL6n-buFifz; Mon, 12 Jun 2017 22:18:47 -0700 (PDT)
Received: from [10.0.1.11] (cpe-76-168-191-223.socal.res.rr.com [76.168.191.223]) by c8a.amsl.com (Postfix) with ESMTPA id 97E6E1CA41C; Mon, 12 Jun 2017 22:18:47 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <AACEBEA74B2A864AB3A420F5818E9EA4C58B6940@MX307CL03.corp.emc.com>
Date: Mon, 12 Jun 2017 22:18:55 -0700
Cc: "Noveck, David" <David.Noveck@netapp.com>, RFC System <rfc-editor@rfc-editor.org>, "shepler@storspeed.com" <shepler@storspeed.com>, "mike@eisler.com" <mike@eisler.com>, "spencerdawkins.ietf@gmail.com" <spencerdawkins.ietf@gmail.com>, "ietf@kuehlewind.net" <ietf@kuehlewind.net>, "beepee@gmail.com" <beepee@gmail.com>, "spencer.shepler@gmail.com" <spencer.shepler@gmail.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A56480-0EFA-4716-8736-0F2802A01F41@amsl.com>
References: <20170612172917.82507B8122A@rfc-editor.org> <MWHPR06MB3021EC2041CE2652161BFBEDE1CD0@MWHPR06MB3021.namprd06.prod.outlook.com> <AACEBEA74B2A864AB3A420F5818E9EA4C58B6940@MX307CL03.corp.emc.com>
To: "Price, Jonathan" <Jonathan.Price@dell.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/vfHdr1HkFGVvCxE--aMIOQjL33Y>
X-Mailman-Approved-At: Tue, 13 Jun 2017 09:41:48 -0700
Subject: Re: [nfsv4] [Technical Errata Reported] RFC5661 (5040)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 13 Jun 2017 05:18:59 -0000
Hi Jonathan, We have updated the corrected text to use DESTROY_CLIENTID. Thank you. RFC Editor/mf On Jun 12, 2017, at 10:56 AM, Price, Jonathan <Jonathan.Price@dell.com> wrote: > Errata to my errata - mea culpa: > > It should be "DESTROY_CLIENTID", not "DESTROY_CLIENT_ID" as I have in my errata submission. > > -----Original Message----- > From: Noveck, David [mailto:David.Noveck@netapp.com] > Sent: Monday, June 12, 2017 1:49 PM > To: RFC Errata System; shepler@storspeed.com; mike@eisler.com; spencerdawkins.ietf@gmail.com; ietf@kuehlewind.net; beepee@gmail.com; spencer.shepler@gmail.com > Cc: Price, Jonathan; nfsv4@ietf.org > Subject: RE: [Technical Errata Reported] RFC5661 (5040) > > Should be verified. Leaving out DESTROY_CLIENT_ID in 18.46.13 was an oversight. > > -----Original Message----- > From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] > Sent: Monday, June 12, 2017 1:29 PM > To: shepler@storspeed.com; mike@eisler.com; Noveck, David <David.Noveck@netapp.com>; spencerdawkins.ietf@gmail.com; ietf@kuehlewind.net; beepee@gmail.com; spencer.shepler@gmail.com > Cc: jonathan.price@dell.com; nfsv4@ietf.org; rfc-editor@rfc-editor.org > Subject: [Technical Errata Reported] RFC5661 (5040) > > The following errata report has been submitted for RFC5661, "Network File System (NFS) Version 4 Minor Version 1 Protocol". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata/eid5040 > > -------------------------------------- > Type: Technical > Reported by: Jonathan Price <jonathan.price@dell.com> > > 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, DESTROY_CLIENT_ID, CREATE_SESSION, and DESTROY_SESSION, MUST NOT appear as the first operation in a COMPOUND. > > Notes > ----- > In the section for DESTROY_CLIENTID (18.50.3), the following text exists (see snipped section below). > This means that DESTROY_CLIENTID must also be in the list for operations that are allowed in the first operation of a compound. > > <...snip...> > If DESTROY_CLIENTID is not prefixed by SEQUENCE, it MUST be the only > operation in the COMPOUND request (otherwise, the server MUST return > NFS4ERR_NOT_ONLY_OP). If the operation is sent without a SEQUENCE > preceding it, a client that retransmits the request may receive an > error in response, because the original request might have been > successfully executed. > <...snip...> > > 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. > > -------------------------------------- > 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
- [nfsv4] [Technical Errata Reported] RFC5661 (5040) RFC Errata System
- Re: [nfsv4] [Technical Errata Reported] RFC5661 (… Noveck, David
- Re: [nfsv4] [Technical Errata Reported] RFC5661 (… Price, Jonathan
- Re: [nfsv4] [Technical Errata Reported] RFC5661 (… Megan Ferguson