[nfsv4] [Technical Errata Reported] RFC5661 (5982)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 13 February 2020 15:58 UTC

To: shepler@storspeed.com, mike@eisler.com, dnoveck@netapp.com, ietf@kuehlewind.net, magnus.westerlund@ericsson.com, beepee@gmail.com, davenoveck@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: davenoveck@gmail.com, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200213155737.DAC4FF406F2@rfc-editor.org>
Date: Thu, 13 Feb 2020 07:57:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/-031YRU4PJOeSVn2WHHzm-z20Y0>
Subject: [nfsv4] [Technical Errata Reported] RFC5661 (5982)
Precedence: list

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:
https://www.rfc-editor.org/errata/eid5982

--------------------------------------
Type: Technical
Reported by: David Noveck <davenoveck@gmail.com>

Section: 2.10.6.1.3.1

Original Text
-------------
   If a requester sent a Sequence operation with a slot ID and sequence
   ID that are in the reply cache but the replier detected that the
   retried request is not the same as the original request, including a
   retry that has different operations or different arguments in the
   operations from the original and a retry that uses a different
   principal in the RPC request's credential field that translates to a
   different user, then this is a false retry.  When the replier detects
   a false retry, it is permitted (but not always obligated) to return
   NFS4ERR_FALSE_RETRY in response to the Sequence operation when it
   detects a false retry.

Corrected Text
--------------
   If a requester sent a Sequence operation with a slot ID and sequence
   ID that are in the reply cache but the replier detected that the
   retried request is not the same as the original request, including a
   retry that was issued with a different XID or has different operations 
   or different arguments in the operations from the original and a retry 
   that uses a different principal in the RPC request's credential field 
   that translates to a different user, then this is a false retry.  When 
   the replier detects a false retry, it is permitted (but not always 
   obligated) to return NFS4ERR_FALSE_RETRY in response to the Sequence 
   operation when it detects a false retry

Notes
-----
The existing text can be read as requiring checksumming of all requests to foreclose the possibility of not noticing a false retry, which can result in data corruption.  This can be a
significant performance consideraation in the processing of WRITE requests and could undercut the benefits of directly placing data to be written which is one of the impotant goals of RPC-over-RDMA.

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 (5982) RFC Errata System
Re: [nfsv4] [Technical Errata Reported] RFC5661 (… Trond Myklebust
Re: [nfsv4] [Technical Errata Reported] RFC5661 (… David Noveck