[nfsv4] [Technical Errata Reported] RFC5661 (5040)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 12 June 2017 17:29 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 22247129469 for <nfsv4@ietfa.amsl.com>; Mon, 12 Jun 2017 10:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 fYtiV4Uco4TF for <nfsv4@ietfa.amsl.com>; Mon, 12 Jun 2017 10:29:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FFC712945E for <nfsv4@ietf.org>; Mon, 12 Jun 2017 10:29:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 82507B8122A; Mon, 12 Jun 2017 10:29:17 -0700 (PDT)
To: shepler@storspeed.com, mike@eisler.com, dnoveck@netapp.com, spencerdawkins.ietf@gmail.com, ietf@kuehlewind.net, beepee@gmail.com, spencer.shepler@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jonathan.price@dell.com, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170612172917.82507B8122A@rfc-editor.org>
Date: Mon, 12 Jun 2017 10:29:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/K9Nd6AafU7xxCBf77Sl3niyQQCI>
X-Mailman-Approved-At: Mon, 12 Jun 2017 10:37:56 -0700
Subject: [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: Mon, 12 Jun 2017 17:29:29 -0000
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