< draft-ietf-nfsv4-rfc5667bis-11.txt   draft-ietf-nfsv4-rfc5667bis-12.txt >
Network File System Version 4 C. Lever, Ed. Network File System Version 4 C. Lever
Internet-Draft Oracle Internet-Draft Oracle
Obsoletes: 5667 (if approved) May 8, 2017 Obsoletes: 5667 (if approved) August 7, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: November 9, 2017 Expires: February 8, 2018
Network File System (NFS) Upper Layer Binding To RPC-Over-RDMA Version Network File System (NFS) Upper Layer Binding To RPC-Over-RDMA Version 1
One draft-ietf-nfsv4-rfc5667bis-12
draft-ietf-nfsv4-rfc5667bis-11
Abstract Abstract
This document specifies Upper Layer Bindings of Network File System This document specifies Upper Layer Bindings of Network File System
(NFS) protocol versions to RPC-over-RDMA Version One, enabling the (NFS) protocol versions to RPC-over-RDMA version 1, enabling the use
use of Direct Data Placement. This document obsoletes RFC 5667. of Direct Data Placement. This document obsoletes RFC 5667.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 9, 2017. This Internet-Draft will expire on February 8, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 19
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Reply Size Estimation . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
2.1. Short Reply Chunk Retry . . . . . . . . . . . . . . . . . 4 3. Reply Size Estimation . . . . . . . . . . . . . . . . . . . . 3
3. Upper Layer Binding for NFS Versions 2 and 3 . . . . . . . . 5 3.1. Short Reply Chunk Retry . . . . . . . . . . . . . . . . . 4
3.1. Reply Size Estimation . . . . . . . . . . . . . . . . . . 5 4. Upper Layer Binding for NFS Versions 2 and 3 . . . . . . . . 5
3.2. RPC Binding Considerations . . . . . . . . . . . . . . . 5 4.1. Reply Size Estimation . . . . . . . . . . . . . . . . . . 5
4. Upper Layer Bindings for NFS Version 2 and 3 Auxiliary 4.2. RPC Binding Considerations . . . . . . . . . . . . . . . 5
5. Upper Layer Bindings for NFS Version 2 and 3 Auxiliary
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. MOUNT, NLM, and NSM Protocols . . . . . . . . . . . . . . 6 5.1. MOUNT, NLM, and NSM Protocols . . . . . . . . . . . . . . 6
4.2. NFSACL Protocol . . . . . . . . . . . . . . . . . . . . . 6 5.2. NFSACL Protocol . . . . . . . . . . . . . . . . . . . . . 6
5. Upper Layer Binding For NFS Version 4 . . . . . . . . . . . . 7 6. Upper Layer Binding For NFS Version 4 . . . . . . . . . . . . 7
5.1. DDP-Eligibility . . . . . . . . . . . . . . . . . . . . . 7 6.1. DDP-Eligibility . . . . . . . . . . . . . . . . . . . . . 7
5.2. Reply Size Estimation . . . . . . . . . . . . . . . . . . 7 6.2. Reply Size Estimation . . . . . . . . . . . . . . . . . . 7
5.3. RPC Binding Considerations . . . . . . . . . . . . . . . 8 6.3. RPC Binding Considerations . . . . . . . . . . . . . . . 8
5.4. NFS COMPOUND Requests . . . . . . . . . . . . . . . . . . 8 6.4. NFS COMPOUND Requests . . . . . . . . . . . . . . . . . . 9
5.5. NFS Callback Requests . . . . . . . . . . . . . . . . . . 11 6.5. NFS Callback Requests . . . . . . . . . . . . . . . . . . 11
5.6. Session-Related Considerations . . . . . . . . . . . . . 12 6.6. Session-Related Considerations . . . . . . . . . . . . . 12
5.7. Transport Considerations . . . . . . . . . . . . . . . . 13 6.7. Transport Considerations . . . . . . . . . . . . . . . . 13
6. Extending NFS Upper Layer Bindings . . . . . . . . . . . . . 14 7. Extending NFS Upper Layer Bindings . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15 10.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16 10.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Changes Since RFC 5667 . . . . . . . . . . . . . . . 17 Appendix A. Changes Since RFC 5667 . . . . . . . . . . . . . . . 17
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 18 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
The RPC-over-RDMA Version One transport may employ direct data The RPC-over-RDMA version 1 transport may employ direct data
placement to convey data payloads associated with RPC transactions placement to convey data payloads associated with RPC transactions
[I-D.ietf-nfsv4-rfc5666bis]. To enable successful interoperation, [RFC8166]. To enable successful interoperation, RPC client and
RPC client and server implementations using RPC-over-RDMA Version One server implementations using RPC-over-RDMA version 1 must agree which
must agree which XDR data items and RPC procedures are eligible to XDR data items and RPC procedures are eligible to use direct data
use direct data placement (DDP). placement (DDP).
An Upper Layer Binding specifies this agreement for one RPC Program. An Upper Layer Binding specifies this agreement for one RPC Program.
Other operational details, such as RPC binding assignments, pairing Other operational details, such as RPC binding assignments, pairing
Write chunks with result data items, and reply size estimation, are Write chunks with result data items, and reply size estimation, are
also specified by this Binding. also specified by this Binding.
This document contains material required of Upper Layer Bindings, as This document contains material required of Upper Layer Bindings, as
specified in [I-D.ietf-nfsv4-rfc5666bis], for the following NFS specified in [RFC8166]. for the following NFS protocol versions:
protocol versions:
o NFS Version 2 [RFC1094] o NFS version 2 [RFC1094]
o NFS Version 3 [RFC1813] o NFS version 3 [RFC1813]
o NFS Version 4.0 [RFC7530] o NFS version 4.0 [RFC7530]
o NFS Version 4.1 [RFC5661] o NFS version 4.1 [RFC5661]
o NFS Version 4.2 [RFC7862] o NFS version 4.2 [RFC7862]
Upper Layer Bindings are also provided for auxiliary protocols used Upper Layer Bindings are also provided for auxiliary protocols used
with NFS versions 2 and 3. with NFS versions 2 and 3 (see Section 5).
This document assumes the reader is already familiar with concepts This document assumes the reader is already familiar with concepts
and terminology defined in [I-D.ietf-nfsv4-rfc5666bis] and the and terminology defined in [RFC8166] and the documents it references.
documents it references.
2. Reply Size Estimation 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all capitals, as shown
here.
3. Reply Size Estimation
During the construction of each RPC Call message, a requester is During the construction of each RPC Call message, a requester is
responsible for allocating appropriate resources for receiving the responsible for allocating appropriate resources for receiving the
corresponding Reply message. If the requester expects the RPC Reply corresponding Reply message. If the requester expects the RPC Reply
message will be larger than its inline threshold, it provides Write message will be larger than its inline threshold, it provides Write
and/or Reply chunks wherein the responder can place results and the and/or Reply chunks wherein the responder can place results and the
reply's Payload stream. reply's Payload stream.
A reply resource overrun occurs if the RPC Reply Payload stream does A reply resource overrun occurs if the RPC Reply Payload stream does
not fit into the provided Reply chunk, or no Reply chunk was provided not fit into the provided Reply chunk, or no Reply chunk was provided
skipping to change at page 4, line 26 skipping to change at page 4, line 26
o The client limits the number of results (e.g. using the "count" o The client limits the number of results (e.g. using the "count"
field of an NFS READDIR request). field of an NFS READDIR request).
o The client has already cached the size of the whole object it is o The client has already cached the size of the whole object it is
about to request (say, via a previous NFS GETATTR request). about to request (say, via a previous NFS GETATTR request).
o The client and server have negotiated a maximum size for all calls o The client and server have negotiated a maximum size for all calls
and responses (using a CREATE_SESSION operation, for instance). and responses (using a CREATE_SESSION operation, for instance).
2.1. Short Reply Chunk Retry 3.1. Short Reply Chunk Retry
In a few cases, either the size of one or more returned data items or In a few cases, either the size of one or more returned data items or
the number of returned data items cannot be known in advance of the number of returned data items cannot be known in advance of
forming an RPC Call. forming an RPC Call.
If an NFS server finds that the NFS client provided inadequate If an NFS server finds that the NFS client provided inadequate
receive resources to return the whole reply, it returns an RPC level receive resources to return the whole reply, it returns an RPC level
error or a transport error, such as ERR_CHUNK. error or a transport error, such as ERR_CHUNK.
In response to these errors, an NFS client can choose to: In response to these errors, an NFS client can choose to:
o Terminate the RPC transaction immediately with an error, or o Terminate the RPC transaction immediately with an error, or
o Allocate a larger Reply chunk and send the same request as a new o Allocate a larger Reply chunk and send the same request as a new
RPC transaction (to avoid hitting in a Duplicate Reply Cache). RPC transaction (a new XID should be assigned to the retransmitted
The NFS client should avoid retrying the request indefinitely request to avoid matching a cached RPC Reply that caches the
because a responder may return ERR_CHUNK for a variety of reasons. original error). The NFS client should avoid retrying the request
indefinitely because a responder may return ERR_CHUNK for a
variety of reasons.
Subsequent sections of this document discuss exactly which operations Subsequent sections of this document discuss exactly which operations
might have ultimate difficulty with Reply size estimation. These might have ultimate difficulty with Reply size estimation. These
operations are eligible for "short Reply chunk retry." Unless operations are eligible for "short Reply chunk retry." Unless
explicitly mentioned as applicable, short Reply chunk retry should explicitly mentioned as applicable, short Reply chunk retry should
not be used. not be used since accurate reply size estimation is problematic in
only a few cases. In all other cases reply size underestimation is
considered a correctable implementation bug.
NFS server implementations can avoid connection loss by first NFS server implementations can avoid connection loss by first
confirming that target RDMA segments are large enough to receive confirming that target RDMA segments are large enough to receive
results before initiating explicit RDMA operations. results before initiating explicit RDMA operations.
3. Upper Layer Binding for NFS Versions 2 and 3 4. Upper Layer Binding for NFS Versions 2 and 3
The Upper Layer Binding specification in this section applies to NFS The Upper Layer Binding specification in this section applies to NFS
Version 2 [RFC1094] and NFS Version 3 [RFC1813]. For brevity, in version 2 [RFC1094] and NFS version 3 [RFC1813]. For brevity, in
this document a "Legacy NFS client" refers to an NFS client using the this document a "Legacy NFS client" refers to an NFS client using the
NFS version 2 or NFS version 3 RPC Programs (100003) to communicate NFS version 2 or NFS version 3 RPC Programs (100003) to communicate
with an NFS server. Likewise, a "Legacy NFS server" is an NFS server with an NFS server. Likewise, a "Legacy NFS server" is an NFS server
communicating with clients using NFS version 2 or NFS version 3. communicating with clients using NFS version 2 or NFS version 3.
The following XDR data items in NFS versions 2 and 3 are DDP- The following XDR data items in NFS versions 2 and 3 are DDP-
eligible: eligible:
o The opaque file data argument in the NFS WRITE procedure o The opaque file data argument in the NFS WRITE procedure
skipping to change at page 5, line 36 skipping to change at page 5, line 38
o The pathname result in the NFS READLINK procedure o The pathname result in the NFS READLINK procedure
All other argument or result data items in NFS versions 2 and 3 are All other argument or result data items in NFS versions 2 and 3 are
not DDP-eligible. not DDP-eligible.
A transport error does not give an indication of whether the server A transport error does not give an indication of whether the server
has processed the arguments of the RPC Call, or whether the server has processed the arguments of the RPC Call, or whether the server
has accessed or modified client memory associated with that RPC. has accessed or modified client memory associated with that RPC.
3.1. Reply Size Estimation 4.1. Reply Size Estimation
A Legacy NFS client determines the maximum reply size for each A Legacy NFS client determines the maximum reply size for each
operation using the criteria outlined in Section 2. There are no operation using the criteria outlined in Section 3. There are no
operations in NFS version 2 or 3 that benefit from short Reply chunk operations in NFS version 2 or 3 that benefit from short Reply chunk
retry. retry.
3.2. RPC Binding Considerations 4.2. RPC Binding Considerations
Legacy NFS servers traditionally listen for clients on UDP and TCP Legacy NFS servers traditionally listen for clients on UDP and TCP
port 2049. Additionally, they register these ports with a local port 2049. Additionally, they register these ports with a local
portmapper [RFC1833] service. portmapper [RFC1833] service.
A Legacy NFS server supporting RPC-over-RDMA Version One on such a A Legacy NFS server supporting RPC-over-RDMA version 1 on such a
network and registering itself with the RPC portmapper MAY choose an network and registering itself with the RPC portmapper MAY choose an
arbitrary port, or MAY use the alternative well-known port number for arbitrary port, or MAY use the alternative well-known port number for
its RPC-over-RDMA service (see Section 8). The chosen port MAY be its RPC-over-RDMA service (see Section 9). The chosen port MAY be
registered with the RPC portmapper under the netids assigned in registered with the RPC portmapper under the netids assigned in
[I-D.ietf-nfsv4-rfc5666bis]. [RFC8166].
4. Upper Layer Bindings for NFS Version 2 and 3 Auxiliary Protocols 5. Upper Layer Bindings for NFS Version 2 and 3 Auxiliary Protocols
NFS versions 2 and 3 are typically deployed with several other NFS versions 2 and 3 are typically deployed with several other
protocols, sometimes referred to as "NFS auxiliary protocols." These protocols, sometimes referred to as "NFS auxiliary protocols." These
are distinct RPC Programs that define procedures which are not part are distinct RPC Programs that define procedures which are not part
of the NFS version 2 or version 3 RPC Programs. The Upper Layer of the NFS version 2 or version 3 RPC Programs. The Upper Layer
Bindings in this section apply to: Bindings in this section apply to:
o Versions 2 and 3 of the MOUNT protocol [RFC1813] o Versions 2 and 3 of the MOUNT protocol [RFC1813]
o Versions 1, 3, and 4 of the NLM protocol [RFC1813] o Versions 1, 3, and 4 of the NLM protocol [RFC1813]
o Version 1 of the NSM protocol, described in Chapter 11 of [XNFS] o Version 1 of the NSM protocol, described in Chapter 11 of [XNFS]
o Version 1 of the NFSACL protocol, which does not have a public o Version 1 of the NFSACL protocol, which does not have a public
definition. NFSACL is treated in this document as a de facto definition. NFSACL is treated in this document as a de facto
standard, as there are several interoperating implementations. standard, as there are several interoperating implementations.
4.1. MOUNT, NLM, and NSM Protocols 5.1. MOUNT, NLM, and NSM Protocols
Historically, NFS/RDMA implementations have chosen to convey the Historically, NFS/RDMA implementations have chosen to convey the
MOUNT, NLM, and NSM protocols via TCP. To enable interoperation of MOUNT, NLM, and NSM protocols via TCP. To enable interoperation of
these protocols when NFS/RDMA is in use, a legacy NFS server MUST these protocols when NFS/RDMA is in use, a legacy NFS server MUST
provide TCP-based MOUNT, NLM, and NSM services. provide support for these protocols via TCP.
4.2. NFSACL Protocol 5.2. NFSACL Protocol
Legacy clients and servers that support the NFSACL RPC Program Legacy clients and servers that support the NFSACL RPC Program
typically convey NFSACL procedures on the same connection as NFS RPC typically convey NFSACL procedures on the same connection as the NFS
Programs. This obviates the need for separate rpcbind queries to RPC program (100003). This obviates the need for separate rpcbind
discover server support for this RPC Program. queries to discover server support for this RPC Program.
ACLs are typically small, but even large ACLs must be encoded and ACLs are typically small, but even large ACLs must be encoded and
decoded to some degree. Thus no data item in this Upper Layer decoded to some degree. Thus no data item in this Upper Layer
Protocol is DDP-eligible. Protocol is DDP-eligible.
For procedures whose replies do not include an ACL object, the size For procedures whose replies do not include an ACL object, the size
of a reply is determined directly from the NFSACL RPC Program's XDR of a reply is determined directly from the NFSACL RPC Program's XDR
definition. definition.
There is no protocol-specified size limit for NFS version 3 ACLs, and There is no protocol-specified size limit for NFS version 3 ACLs, and
there is no mechanism in either the NFSACL or NFS RPC Programs for a there is no mechanism in either the NFSACL or NFS RPC Programs for a
Legacy client to ascertain the largest ACL a Legacy server can Legacy client to ascertain the largest ACL a Legacy server can
return. Legacy client implementations should choose a maximum size return. Legacy client implementations should choose a maximum size
for ACLs based on their own internal limits. for ACLs based on their own internal limits.
Because an NFSACL client cannot know in advance how large a returned Because an NFSACL client cannot know in advance how large a returned
ACL will be, it can use short Reply chunk retry when an NFSACL GETACL ACL will be, it can use short Reply chunk retry when an NFSACL GETACL
operation encounters a transport error. operation encounters a transport error.
5. Upper Layer Binding For NFS Version 4 6. Upper Layer Binding For NFS Version 4
The Upper Layer Binding specification in this section applies to RPC The Upper Layer Binding specification in this section applies to RPC
Programs defined in NFS Version 4.0 [RFC7530], NFS Version 4.1 Programs defined in NFS version 4.0 [RFC7530], NFS version 4.1
[RFC5661], and NFS Version 4.2 [RFC7862]. [RFC5661], and NFS version 4.2 [RFC7862].
5.1. DDP-Eligibility 6.1. DDP-Eligibility
Only the following XDR data items in the COMPOUND procedure of all Only the following XDR data items in the COMPOUND procedure of all
NFS version 4 minor versions are DDP-eligible: NFS version 4 minor versions are DDP-eligible:
o The opaque data field in the WRITE4args structure o The opaque data field in the WRITE4args structure
o The linkdata field of the NF4LNK arm in the createtype4 union o The linkdata field of the NF4LNK arm in the createtype4 union
o The opaque data field in the READ4resok structure o The opaque data field in the READ4resok structure
o The linkdata field in the READLINK4resok structure o The linkdata field in the READLINK4resok structure
5.2. Reply Size Estimation 6.2. Reply Size Estimation
Within NFS version 4, there are certain variable-length result data Within NFS version 4, there are certain variable-length result data
items whose maximum size cannot be estimated by clients reliably items whose maximum size cannot be estimated by clients reliably
because there is no protocol-specified size limit on these arrays. because there is no protocol-specified size limit on these arrays.
These include: These include:
o The attrlist4 field o The attrlist4 field
o Fields containing ACLs such as fattr4_acl, fattr4_dacl, o Fields containing ACLs such as fattr4_acl, fattr4_dacl,
fattr4_sacl fattr4_sacl
o Fields in the fs_locations4 and fs_locations_info4 data structures o Fields in the fs_locations4 and fs_locations_info4 data structures
o Fields opaque to the NFS version 4 protocol which pertain to pNFS o Fields opaque to the NFS version 4 protocol which pertain to pNFS
layout metadata, such as loc_body, loh_body, da_addr_body, layout metadata, such as loc_body, loh_body, da_addr_body,
lou_body, lrf_body, fattr_layout_types and fs_layout_types, lou_body, lrf_body, fattr_layout_types and fs_layout_types,
5.2.1. Reply Size Estimation for Minor Version 0 6.2.1. Reply Size Estimation for Minor Version 0
The NFS version 4.0 protocol itself does not impose any bound on the The NFS version 4.0 protocol itself does not impose any bound on the
size of NFS calls or responses. size of NFS calls or responses.
Some of the data items enumerated in Section 5.2 (in particular, the Some of the data items enumerated in Section 6.2 (in particular, the
items related to ACLs and fs_locations) make it difficult to predict items related to ACLs and fs_locations) make it difficult to predict
the maximum size of NFS version 4.0 replies that interrogate the maximum size of NFS version 4.0 replies that interrogate
variable-length fattr4 attributes. Client implementations might rely variable-length fattr4 attributes. Client implementations might rely
on their own internal architectural limits to constrain the reply on their own internal architectural limits to constrain the reply
size, but such limits are not always guaranteed to be reliable. size, but such limits are not always guaranteed to be reliable.
When an especially large fattr4 result is expected, a Reply chunk When an especially large fattr4 result is expected, a Reply chunk
might be required. An NFS version 4.0 client can use short Reply might be required. An NFS version 4.0 client can use short Reply
chunk retry when an NFS COMPOUND containing a GETATTR operation chunk retry when an NFS COMPOUND containing a GETATTR operation
encounters a transport error. encounters a transport error.
The use of NFS COMPOUND operations raises the possibility of requests The use of NFS COMPOUND operations raises the possibility of requests
that combine a non-idempotent operation (e.g. RENAME) with a GETATTR that combine a non-idempotent operation (e.g. RENAME) with a GETATTR
operation that requests one or more variable-length results. This operation that requests one or more variable-length results. This
combination should be avoided by ensuring that any GETATTR operation combination should be avoided by ensuring that any GETATTR operation
that requests a result of unpredictable length is sent in an NFS that requests a result of unpredictable length is sent in an NFS
COMPOUND by itself. COMPOUND by itself.
5.2.2. Reply Size Estimation for Minor Version 1 and Newer 6.2.2. Reply Size Estimation for Minor Version 1 and Newer
In NFS version 4.1 and newer minor versions, the csa_fore_chan_attrs In NFS version 4.1 and newer minor versions, the csa_fore_chan_attrs
argument of the CREATE_SESSION operation contains a argument of the CREATE_SESSION operation contains a
ca_maxresponsesize field. The value in this field can be taken as ca_maxresponsesize field. The value in this field can be taken as
the absolute maximum size of replies generated by an NFS version 4.1 the absolute maximum size of replies generated by an NFS version 4.1
server. server.
This value can be used in cases where it is not possible to estimate This value can be used in cases where it is not possible to estimate
a reply size upper bound precisely. In practice, objects such as a reply size upper bound precisely. In practice, objects such as
ACLs, named attributes, layout bodies, and security labels are much ACLs, named attributes, layout bodies, and security labels are much
smaller than this maximum. smaller than this maximum.
5.3. RPC Binding Considerations 6.3. RPC Binding Considerations
NFS version 4 servers are required to listen on TCP port 2049, and NFS version 4 servers are required to listen on TCP port 2049, and
they are not required to register with an rpcbind service [RFC7530]. they are not required to register with an rpcbind service [RFC7530].
Therefore, an NFS version 4 server supporting RPC-over-RDMA Version Therefore, an NFS version 4 server supporting RPC-over-RDMA version 1
One MUST use the alternative well-known port number for its RPC-over- MUST use the alternative well-known port number for its RPC-over-RDMA
RDMA service (see Section 8). Clients SHOULD connect to this well- service (see Section 9). Clients SHOULD connect to this well-known
known port without consulting the RPC portmapper (as for NFS version port without consulting the RPC portmapper (as for NFS version 4 on
4 on TCP transports). TCP transports).
5.4. NFS COMPOUND Requests 6.4. NFS COMPOUND Requests
5.4.1. Multiple DDP-eligible Data Items 6.4.1. Multiple DDP-eligible Data Items
An NFS version 4 COMPOUND procedure can contain more than one An NFS version 4 COMPOUND procedure can contain more than one
operation that carries a DDP-eligible data item. An NFS version 4 operation that carries a DDP-eligible data item. An NFS version 4
client provides XDR Position values in each Read chunk to client provides XDR Position values in each Read chunk to
disambiguate which chunk is associated with which argument data item. disambiguate which chunk is associated with which argument data item.
However NFS version 4 server and client implementations must agree in However NFS version 4 server and client implementations must agree in
advance on how to pair Write chunks with returned result data items. advance on how to pair Write chunks with returned result data items.
In the following list, a "READ operation" refers to any NFS Version 4 In the following list, a "READ operation" refers to any NFS version 4
operation which has a DDP-eligible result data item. The mechanism operation which has a DDP-eligible result data item. The mechanism
specified in Section 4.3.2 of [I-D.ietf-nfsv4-rfc5666bis]) is applied specified in Section 4.3.2 of [RFC8166] is applied to this class of
to this class of operations: operations:
o If an NFS version 4 client wishes all DDP-eligible items in an NFS o If an NFS version 4 client wishes all DDP-eligible items in an NFS
reply to be conveyed inline, it leaves the Write list empty. reply to be conveyed inline, it leaves the Write list empty.
o The first chunk in the Write list MUST be used by the first READ o The first chunk in the Write list MUST be used by the first READ
operation in an NFS version 4 COMPOUND procedure. The next Write operation in an NFS version 4 COMPOUND procedure. The next Write
chunk is used by the next READ operation, and so on. chunk is used by the next READ operation, and so on.
o If an NFS version 4 client has provided a matching non-empty Write o If an NFS version 4 client has provided a matching non-empty Write
chunk, then the corresponding READ operation MUST return its DDP- chunk, then the corresponding READ operation MUST return its DDP-
skipping to change at page 9, line 37 skipping to change at page 9, line 45
o If a READ operation returns a union arm which does not contain a o If a READ operation returns a union arm which does not contain a
DDP-eligible result, and the NFS version 4 client has provided a DDP-eligible result, and the NFS version 4 client has provided a
matching non-empty Write chunk, an NFS version 4 server MUST matching non-empty Write chunk, an NFS version 4 server MUST
return an empty Write chunk in that Write list position. return an empty Write chunk in that Write list position.
o If there are more READ operations than Write chunks, then o If there are more READ operations than Write chunks, then
remaining NFS Read operations in an NFS version 4 COMPOUND that remaining NFS Read operations in an NFS version 4 COMPOUND that
have no matching Write chunk MUST return their results inline. have no matching Write chunk MUST return their results inline.
5.4.2. Chunk List Complexity 6.4.2. Chunk List Complexity
The RPC-over-RDMA Version One protocol does not place any limit on The RPC-over-RDMA version 1 protocol does not place any limit on the
the number of chunks or segments that may appear in Read or Write number of chunks or segments that may appear in Read or Write lists.
lists. However, for various reasons NFS version 4 server However, for various reasons NFS version 4 server implementations
implementations often have practical limits on the number of chunks often have practical limits on the number of chunks or segments they
or segments they are prepared to process in a single RPC transaction are prepared to process in a single RPC transaction conveyed via RPC-
conveyed via RPC-over-RDMA Version One. over-RDMA version 1.
These implementation limits are especially important when Kerberos These implementation limits are especially important when Kerberos
integrity or privacy is in use [RFC7861]. GSS services increase the integrity or privacy is in use [RFC7861]. GSS services increase the
size of credential material in RPC headers, potentially requiring size of credential material in RPC headers, potentially requiring
more frequent use of Long messages. This can increase the complexity more frequent use of Long messages. This can increase the complexity
of chunk lists independent of the NFS version 4 COMPOUND being of chunk lists independent of the NFS version 4 COMPOUND being
conveyed. conveyed.
In the absence of explicit knowledge of the server's limits, NFS In the absence of explicit knowledge of the server's limits, NFS
Version 4 clients SHOULD follow the prescriptions listed below when version 4 clients SHOULD follow the prescriptions listed below when
constructing RPC-over-RDMA Version One messages. NFS Version 4 constructing RPC-over-RDMA version 1 messages. NFS version 4 servers
servers MUST accept and process such requests. MUST accept and process such requests.
o The Read list can contain either a Position-Zero Read chunk, one o The Read list can contain either a Position-Zero Read chunk, one
Read chunk with a non-zero Position, or both. Read chunk with a non-zero Position, or both.
o The Write list can contain no more than one Write chunk. o The Write list can contain no more than one Write chunk.
o Any chunk can contain up to sixteen RDMA segments. o Any chunk can contain up to sixteen RDMA segments.
NFS version 4 clients wishing to send more complex chunk lists can NFS version 4 clients wishing to send more complex chunk lists can
provide configuration interfaces to bound the complexity of NFS provide configuration interfaces to bound the complexity of NFS
version 4 COMPOUNDs, limit the number of elements in scatter-gather version 4 COMPOUNDs, limit the number of elements in scatter-gather
operations, and avoid other sources of chunk overruns at the operations, and avoid other sources of chunk overruns at the
receiving peer. receiving peer.
An NFS Version 4 server SHOULD return one of the following responses An NFS version 4 server SHOULD return one of the following responses
to a client that has sent an RPC transaction via RPC-over-RDMA to a client that has sent an RPC transaction via RPC-over-RDMA
Version One which cannot be processed due to chunk list complexity version 1 which cannot be processed due to chunk list complexity
limits on the server: limits on the server:
o A problem is detected by the transport layer while parsing the o A problem is detected by the transport layer while parsing the
transport header in an RPC Call message. The server responds with transport header in an RPC Call message. The server responds with
an RDMA_ERROR message with the err field set to ERR_CHUNK. an RDMA_ERROR message with the err field set to ERR_CHUNK.
o A problem is detected during XDR decoding of the RPC Call message o A problem is detected during XDR decoding of the RPC Call message
while the RPC layer reassembles the call's XDR stream. The server while the RPC layer reassembles the call's XDR stream. The server
responds with an RPC reply with its "reply_stat" field set to responds with an RPC reply with its "reply_stat" field set to
MSG_ACCEPTED and its "accept_stat" field set to GARBAGE_ARGS. MSG_ACCEPTED and its "accept_stat" field set to GARBAGE_ARGS.
After receiving one of these errors, an NFS version 4 client SHOULD After receiving one of these errors, an NFS version 4 client SHOULD
NOT retransmit the failing request, as the result would be the same NOT retransmit the failing request, as the result would be the same
error. It SHOULD immediately terminate the RPC transaction error. It SHOULD immediately terminate the RPC transaction
associated with the XID in the reply. associated with the XID in the reply.
5.4.3. NFS Version 4 COMPOUND Example 6.4.3. NFS Version 4 COMPOUND Example
The following example shows a Write list with three Write chunks, A, The following example shows a Write list with three Write chunks, A,
B, and C. The NFS version 4 server consumes the provided Write B, and C. The NFS version 4 server consumes the provided Write
chunks by writing the results of the designated operations in the chunks by writing the results of the designated operations in the
compound request (READ and READLINK) back to each chunk. compound request (READ and READLINK) back to each chunk.
Write list: Write list:
A --> B --> C A --> B --> C
skipping to change at page 11, line 20 skipping to change at page 11, line 27
PUTFH LOOKUP READ PUTFH LOOKUP READLINK PUTFH LOOKUP READ PUTFH LOOKUP READ PUTFH LOOKUP READLINK PUTFH LOOKUP READ
| | | | | |
v v v v v v
A B C A B C
If the NFS version 4 client does not want to have the READLINK result If the NFS version 4 client does not want to have the READLINK result
returned via RDMA, it provides an empty Write chunk for buffer B to returned via RDMA, it provides an empty Write chunk for buffer B to
indicate that the READLINK result must be returned inline. indicate that the READLINK result must be returned inline.
5.5. NFS Callback Requests 6.5. NFS Callback Requests
The NFS version 4 family of protocols support server-initiated The NFS version 4 family of protocols support server-initiated
callbacks to notify NFS version 4 clients of events such as recalled callbacks to notify NFS version 4 clients of events such as recalled
delegations. delegations.
5.5.1. NFS Version 4.0 Callback 6.5.1. NFS Version 4.0 Callback
NFS version 4.0 implementations typically employ a separate TCP NFS version 4.0 implementations typically employ a separate TCP
connection to handle callback operations, even when the forward connection to handle callback operations, even when the forward
channel uses an RPC-over-RDMA Version One transport. channel uses an RPC-over-RDMA version 1 transport.
No operation in the NFS version 4.0 callback RPC Program conveys a No operation in the NFS version 4.0 callback RPC Program conveys a
significant data payload. Therefore, no XDR data items in this RPC significant data payload. Therefore, no XDR data items in this RPC
Program is DDP-eligible. Program is DDP-eligible.
A CB_RECALL reply is small and fixed in size. The CB_GETATTR reply A CB_RECALL reply is small and fixed in size. The CB_GETATTR reply
contains a variable-length fattr4 data item. See Section 5.2.1 for a contains a variable-length fattr4 data item. See Section 6.2.1 for a
discussion of reply size prediction for this data item. discussion of reply size prediction for this data item.
An NFS version 4.0 client advertises netids and ad hoc port addresses An NFS version 4.0 client advertises netids and ad hoc port addresses
for contacting its NFS version 4.0 callback service using the for contacting its NFS version 4.0 callback service using the
SETCLIENTID operation. SETCLIENTID operation.
5.5.2. NFS Version 4.1 Callback 6.5.2. NFS Version 4.1 Callback
In NFS version 4.1 and newer minor versions, callback operations may In NFS version 4.1 and newer minor versions, callback operations may
appear on the same connection as is used for NFS version 4 forward appear on the same connection as is used for NFS version 4 forward
channel client requests. NFS version 4 clients and servers MUST use channel client requests. NFS version 4 clients and servers MUST use
the approach described in [I-D.ietf-nfsv4-rpcrdma-bidirection] when the approach described in [RFC8167] when backchannel operations are
backchannel operations are conveyed on RPC-over-RDMA Version One conveyed on RPC-over-RDMA version 1 transports.
transports.
The csa_back_chan_attrs argument of the CREATE_SESSION operation The csa_back_chan_attrs argument of the CREATE_SESSION operation
contains a ca_maxresponsesize field. The value in this field can be contains a ca_maxresponsesize field. The value in this field can be
taken as the absolute maximum size of backchannel replies generated taken as the absolute maximum size of backchannel replies generated
by a replying NFS version 4 client. by a replying NFS version 4 client.
There are no DDP-eligible data items in callback procedures defined There are no DDP-eligible data items in callback procedures defined
in NFS version 4.1 or NFS version 4.2. However, some callback in NFS version 4.1 or NFS version 4.2. However, some callback
operations, such as messages that convey device ID information, can operations, such as messages that convey device ID information, can
be large, in which case a Long Call or Reply might be required. be large, in which case a Long Call or Reply might be required.
When an NFS version 4.1 client can support Long Calls in its When an NFS version 4.1 client can support Long Calls in its
backchannel, it reports a backchannel ca_maxrequestsize that is backchannel, it reports a backchannel ca_maxrequestsize that is
larger than the connection's inline thresholds. Otherwise an NFS larger than the connection's inline thresholds. Otherwise an NFS
version 4 server MUST use only Short messages to convey backchannel version 4 server MUST use only Short messages to convey backchannel
operations. operations.
5.6. Session-Related Considerations 6.6. Session-Related Considerations
The presence of an NFS session (defined in [RFC5661]) has no effect The presence of an NFS session (defined in [RFC5661]) has no effect
on the operation of RPC-over-RDMA Version One. None of the on the operation of RPC-over-RDMA version 1. None of the operations
operations introduced to support NFS sessions (e.g. the SEQUENCE introduced to support NFS sessions (e.g. the SEQUENCE operation)
operation) contain DDP-eligible data items. There is no need to contain DDP-eligible data items. There is no need to match the
match the number of session slots with the number of available RPC- number of session slots with the number of available RPC-over-RDMA
over-RDMA credits. credits.
However, there are a few new cases where an RPC transaction can fail. However, there are a few new cases where an RPC transaction can fail.
For example, a requester might receive, in response to an RPC For example, a requester might receive, in response to an RPC
request, an RDMA_ERROR message with an rdma_err value of ERR_CHUNK. request, an RDMA_ERROR message with an rdma_err value of ERR_CHUNK.
These situations are not different from existing RPC errors which an These situations are not different from existing RPC errors which an
NFS session implementation is already prepared to handle for other NFS session implementation is already prepared to handle for other
transports. And as with other transports during such a failure, transports. And as with other transports during such a failure,
there might be no SEQUENCE result available to the requester to there might be no SEQUENCE result available to the requester to
distinguish whether failure occurred before or after the requested distinguish whether failure occurred before or after the requested
operations were executed on the responder. operations were executed on the responder.
When a transport error occurs (e.g. RDMA_ERROR), the requester When a transport error occurs (e.g. RDMA_ERROR), the requester
proceeds as usual to match the incoming XID value to a waiting RPC proceeds as usual to match the incoming XID value to a waiting RPC
Call. The RPC transaction is terminated, and the result status is Call. The RPC transaction is terminated, and the result status is
reported to the Upper Layer Protocol. The requester's session reported to the Upper Layer Protocol. The requester's session
implementation then determines the session ID and slot for the failed implementation then determines the session ID and slot for the failed
request, and performs slot recovery to make that slot usable again. request, and performs slot recovery to make that slot usable again.
If this were not done, that slot could be rendered permanently If this were not done, that slot could be rendered permanently
unavailable. unavailable.
5.7. Transport Considerations When an NFS session is not present (for example, when NFS version 4.0
is in use), a transport error does not provide an indication of
whether the server has processed the arguments of the RPC Call, or
whether the server has accessed or modified client memory associated
with that RPC.
5.7.1. Congestion Avoidance 6.7. Transport Considerations
6.7.1. Congestion Avoidance
Section 3.1 of [RFC7530] states: Section 3.1 of [RFC7530] states:
Where an NFS version 4 implementation supports operation over the Where an NFS version 4 implementation supports operation over the
IP network protocol, the supported transport layer between NFS and IP network protocol, the supported transport layer between NFS and
IP MUST be an IETF standardized transport protocol that is IP MUST be an IETF standardized transport protocol that is
specified to avoid network congestion; such transports include TCP specified to avoid network congestion; such transports include TCP
and the Stream Control Transmission Protocol (SCTP). and the Stream Control Transmission Protocol (SCTP).
Section 2.9.1 of [RFC5661] also states: Section 2.9.1 of [RFC5661] also states:
Even if NFS version 4.1 is used over a non-IP network protocol, it Even if NFS version 4.1 is used over a non-IP network protocol, it
is RECOMMENDED that the transport support congestion control. is RECOMMENDED that the transport support congestion control.
It is permissible for a connectionless transport to be used under It is permissible for a connectionless transport to be used under
NFS version 4.1; however, reliable and in-order delivery of data NFS version 4.1; however, reliable and in-order delivery of data
combined with congestion control by the connectionless transport combined with congestion control by the connectionless transport
is REQUIRED. As a consequence, UDP by itself MUST NOT be used as is REQUIRED. As a consequence, UDP by itself MUST NOT be used as
an NFS version 4.1 transport. an NFS version 4.1 transport.
RPC-over-RDMA Version One is constructed on a platform of RDMA RPC-over-RDMA version 1 is constructed on a platform of RDMA Reliable
Reliable Connections [I-D.ietf-nfsv4-rfc5666bis] [RFC5041]. RDMA Connections [RFC8166] [RFC5041]. RDMA Reliable Connections are
Reliable Connections are reliable, connection-oriented transports reliable, connection-oriented transports that guarantee in-order
that guarantee in-order delivery, meeting all above requirements for delivery, meeting all above requirements for NFS version 4
NFS version 4 transports. transports.
5.7.2. Retransmission and Keep-alive 6.7.2. Retransmission and Keep-alive
NFS version 4 client implementations often rely on a transport-layer NFS version 4 client implementations often rely on a transport-layer
keep-alive mechanism to detect when an NFS version 4 server has keep-alive mechanism to detect when an NFS version 4 server has
become unresponsive. When an NFS server is no longer responsive, become unresponsive. When an NFS server is no longer responsive,
client-side keep-alive terminates the connection, which in turn client-side keep-alive terminates the connection, which in turn
triggers reconnection and RPC retransmission. triggers reconnection and RPC retransmission.
Some RDMA transports (such as Reliable Connections on InfiniBand) Some RDMA transports (such as Reliable Connections on InfiniBand)
have no keep-alive mechanism. Without a disconnect or new RPC have no keep-alive mechanism. Without a disconnect or new RPC
traffic, such connections can remain alive long after an NFS server traffic, such connections can remain alive long after an NFS server
skipping to change at page 14, line 23 skipping to change at page 14, line 34
o If there is a transport error indicated (ie, RDMA_ERROR) before o If there is a transport error indicated (ie, RDMA_ERROR) before
the disconnect or instead of a disconnect, the requester MUST the disconnect or instead of a disconnect, the requester MUST
respond to that error as prescribed by the specification of the respond to that error as prescribed by the specification of the
RPC transport. Then the NFS version 4 rules for handling RPC transport. Then the NFS version 4 rules for handling
retransmission apply. retransmission apply.
o If there is a transport disconnect and the responder has provided o If there is a transport disconnect and the responder has provided
no other response for a request, then only the NFS version 4 rules no other response for a request, then only the NFS version 4 rules
for handling retransmission apply. for handling retransmission apply.
6. Extending NFS Upper Layer Bindings 7. Extending NFS Upper Layer Bindings
RPC Programs such as NFS are required to have an Upper Layer Binding RPC Programs such as NFS are required to have an Upper Layer Binding
specification to interoperate on RPC-over-RDMA Version One transports specification to interoperate on RPC-over-RDMA version 1 transports
[I-D.ietf-nfsv4-rfc5666bis]. Via standards action, the Upper Layer [RFC8166]. Via standards action, the Upper Layer Binding specified
Binding specified in this document can be extended to cover versions in this document can be extended to cover versions of the NFS version
of the NFS version 4 protocol specified after NFS version 4 minor 4 protocol specified after NFS version 4 minor version 2, or
version 2, or separately published extensions to an existing NFS separately published extensions to an existing NFS version 4 minor
version 4 minor version, as described in [I-D.ietf-nfsv4-versioning]. version, as described in [RFC8178].
7. Security Considerations 8. Security Considerations
RPC-over-RDMA Version One supports all RPC security models, including RPC-over-RDMA version 1 supports all RPC security models, including
RPCSEC_GSS security and transport-level security [RFC7861]. The RPCSEC_GSS security and transport-level security [RFC7861]. The
choice of what Direct Data Placement mechanism to convey RPC argument choice of what Direct Data Placement mechanism to convey RPC argument
and results does not affect this, since it changes only the method of and results does not affect this, since it changes only the method of
data transfer. Specifically, the requirements of data transfer. Specifically, the requirements of [RFC8166] ensure
[I-D.ietf-nfsv4-rfc5666bis] ensure that this choice does not that this choice does not introduce new vulnerabilities.
introduce new vulnerabilities.
Because this document defines only the binding of the NFS protocols Because this document defines only the binding of the NFS protocols
atop [I-D.ietf-nfsv4-rfc5666bis], all relevant security atop [RFC8166], all relevant security considerations are therefore to
considerations are therefore to be described at that layer. be described at that layer.
8. IANA Considerations 9. IANA Considerations
The use of direct data placement in NFS introduces a need for an The use of direct data placement in NFS introduces a need for an
additional port number assignment for networks that share traditional additional port number assignment for networks that share traditional
UDP and TCP port spaces with RDMA services. The iWARP protocol is UDP and TCP port spaces with RDMA services. The iWARP protocol is
such an example [RFC5041] [RFC5040]. such an example [RFC5041] [RFC5040].
For this purpose, a set of transport protocol port number assignments For this purpose, a set of transport protocol port number assignments
is specified by this document. IANA has assigned the following ports is specified by this document. IANA has assigned the following ports
for NFS/RDMA in the IANA port registry, according to the guidelines for NFS/RDMA in the IANA port registry, according to the guidelines
described in [RFC6335]. described in [RFC6335].
nfsrdma 20049/tcp Network File System (NFS) over RDMA nfsrdma 20049/tcp Network File System (NFS) over RDMA
nfsrdma 20049/udp Network File System (NFS) over RDMA nfsrdma 20049/udp Network File System (NFS) over RDMA
nfsrdma 20049/sctp Network File System (NFS) over RDMA nfsrdma 20049/sctp Network File System (NFS) over RDMA
This document should be listed as the reference for the nfsrdma port This document should be listed as the reference for the nfsrdma port
assignments. This document does not alter these assignments. assignments. This document does not alter these assignments.
9. References 10. References
9.1. Normative References
[I-D.ietf-nfsv4-rfc5666bis]
Lever, C., Simpson, W., and T. Talpey, "Remote Direct
Memory Access Transport for Remote Procedure Call, Version
One", draft-ietf-nfsv4-rfc5666bis-11 (work in progress),
March 2017.
[I-D.ietf-nfsv4-rpcrdma-bidirection] 10.1. Normative References
Lever, C., "Bi-directional Remote Procedure Call On RPC-
over-RDMA Transports", draft-ietf-nfsv4-rpcrdma-
bidirection-08 (work in progress), March 2017.
[RFC1833] Srinivasan, R., "Binding Protocols for ONC RPC Version 2", [RFC1833] Srinivasan, R., "Binding Protocols for ONC RPC Version 2",
RFC 1833, DOI 10.17487/RFC1833, August 1995, RFC 1833, DOI 10.17487/RFC1833, August 1995,
<http://www.rfc-editor.org/info/rfc1833>. <http://www.rfc-editor.org/info/rfc1833>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 16, line 24 skipping to change at page 16, line 24
March 2015, <http://www.rfc-editor.org/info/rfc7530>. March 2015, <http://www.rfc-editor.org/info/rfc7530>.
[RFC7861] Adamson, A. and N. Williams, "Remote Procedure Call (RPC) [RFC7861] Adamson, A. and N. Williams, "Remote Procedure Call (RPC)
Security Version 3", RFC 7861, DOI 10.17487/RFC7861, Security Version 3", RFC 7861, DOI 10.17487/RFC7861,
November 2016, <http://www.rfc-editor.org/info/rfc7861>. November 2016, <http://www.rfc-editor.org/info/rfc7861>.
[RFC7862] Haynes, T., "Network File System (NFS) Version 4 Minor [RFC7862] Haynes, T., "Network File System (NFS) Version 4 Minor
Version 2 Protocol", RFC 7862, DOI 10.17487/RFC7862, Version 2 Protocol", RFC 7862, DOI 10.17487/RFC7862,
November 2016, <http://www.rfc-editor.org/info/rfc7862>. November 2016, <http://www.rfc-editor.org/info/rfc7862>.
9.2. Informative References [RFC8166] Lever, C., Ed., Simpson, W., and T. Talpey, "Remote Direct
Memory Access Transport for Remote Procedure Call Version
1", RFC 8166, DOI 10.17487/RFC8166, June 2017,
<http://www.rfc-editor.org/info/rfc8166>.
[I-D.ietf-nfsv4-versioning] [RFC8167] Lever, C., "Bidirectional Remote Procedure Call on RPC-
Noveck, D., "Rules for NFSv4 Extensions and Minor over-RDMA Transports", RFC 8167, DOI 10.17487/RFC8167,
Versions", draft-ietf-nfsv4-versioning-09 (work in June 2017, <http://www.rfc-editor.org/info/rfc8167>.
progress), December 2016.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <http://www.rfc-editor.org/info/rfc8174>.
10.2. Informative References
[RFC1094] Nowicki, B., "NFS: Network File System Protocol [RFC1094] Nowicki, B., "NFS: Network File System Protocol
specification", RFC 1094, DOI 10.17487/RFC1094, March specification", RFC 1094, DOI 10.17487/RFC1094, March
1989, <http://www.rfc-editor.org/info/rfc1094>. 1989, <http://www.rfc-editor.org/info/rfc1094>.
[RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS [RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS
Version 3 Protocol Specification", RFC 1813, Version 3 Protocol Specification", RFC 1813,
DOI 10.17487/RFC1813, June 1995, DOI 10.17487/RFC1813, June 1995,
<http://www.rfc-editor.org/info/rfc1813>. <http://www.rfc-editor.org/info/rfc1813>.
skipping to change at page 17, line 14 skipping to change at page 17, line 19
[RFC5666] Talpey, T. and B. Callaghan, "Remote Direct Memory Access [RFC5666] Talpey, T. and B. Callaghan, "Remote Direct Memory Access
Transport for Remote Procedure Call", RFC 5666, Transport for Remote Procedure Call", RFC 5666,
DOI 10.17487/RFC5666, January 2010, DOI 10.17487/RFC5666, January 2010,
<http://www.rfc-editor.org/info/rfc5666>. <http://www.rfc-editor.org/info/rfc5666>.
[RFC5667] Talpey, T. and B. Callaghan, "Network File System (NFS) [RFC5667] Talpey, T. and B. Callaghan, "Network File System (NFS)
Direct Data Placement", RFC 5667, DOI 10.17487/RFC5667, Direct Data Placement", RFC 5667, DOI 10.17487/RFC5667,
January 2010, <http://www.rfc-editor.org/info/rfc5667>. January 2010, <http://www.rfc-editor.org/info/rfc5667>.
[RFC8178] Noveck, D., "Rules for NFSv4 Extensions and Minor
Versions", RFC 8178, DOI 10.17487/RFC8178, July 2017,
<http://www.rfc-editor.org/info/rfc8178>.
[XNFS] The Open Group, "Protocols for Interworking: XNFS, Version [XNFS] The Open Group, "Protocols for Interworking: XNFS, Version
3W", February 1998. 3W", February 1998.
Appendix A. Changes Since RFC 5667 Appendix A. Changes Since RFC 5667
Corrections and updates made necessary by new language in Corrections and updates made necessary by new language in [RFC8166]
[I-D.ietf-nfsv4-rfc5666bis] have been introduced. For example, have been introduced. For example, references to deprecated features
references to deprecated features of RPC-over-RDMA Version One, such of RPC-over-RDMA version 1, such as RDMA_MSGP, and the use of the
as RDMA_MSGP, and the use of the Read list for handling RPC replies, Read list for handling RPC replies, have been removed. The term
have been removed. The term "mapping" has been replaced with the "mapping" has been replaced with the term "binding" or "Upper Layer
term "binding" or "Upper Layer Binding" throughout the document. Binding" throughout the document. Material that duplicates what is
Material that duplicates what is in [I-D.ietf-nfsv4-rfc5666bis] has in [RFC8166] has been deleted.
been deleted.
Material required by [I-D.ietf-nfsv4-rfc5666bis] for Upper Layer Material required by [RFC8166] for Upper Layer Bindings that was not
Bindings that was not present in [RFC5667] has been added. A present in [RFC5667] has been added. A complete discussion of reply
complete discussion of reply size estimation has been introduced for size estimation has been introduced for all protocols covered by the
all protocols covered by the Upper Layer Bindings in this document. Upper Layer Bindings in this document.
Technical corrections have been made. For example, the mention of Technical corrections have been made. For example, the mention of
12KB and 36KB inline thresholds have been removed. The reference to 12KB and 36KB inline thresholds have been removed. The reference to
a non-existant NFS version 4 SYMLINK operation has been replaced. a non-existant NFS version 4 SYMLINK operation has been replaced.
The discussion of NFS version 4 COMPOUND handling has been completed. The discussion of NFS version 4 COMPOUND handling has been completed.
Some changes were made to the algorithm for matching DDP-eligible Some changes were made to the algorithm for matching DDP-eligible
results to Write chunks. results to Write chunks.
Requirements to ignore extra Read or Write chunks have been removed Requirements to ignore extra Read or Write chunks have been removed
from the NFS version 2 and 3 Upper Layer Binding, as they conflict from the NFS version 2 and 3 Upper Layer Binding, as they conflict
with [I-D.ietf-nfsv4-rfc5666bis]. with [RFC8166].
A section discussing NFS version 4 retransmission and connection loss A section discussing NFS version 4 retransmission and connection loss
has been added. has been added.
The following additional improvements have been made, relative to The following additional improvements have been made, relative to
[RFC5667]: [RFC5667]:
o An explicit discussion of NFS version 4.0 and NFS version 4.1 o An explicit discussion of NFS version 4.0 and NFS version 4.1
backchannel operation has replaced the previous treatment of backchannel operation has replaced the previous treatment of
callback operations. callback operations.
o A binding for NFS version 4.2 has been added. o A section describing considerations when an NFS session is in use
has been added.
o An Upper Layer Binding for NFS version 4.2 has been added.
o A section suggesting a mechanism for periodically assessing o A section suggesting a mechanism for periodically assessing
connection health has been introduced. connection health has been introduced.
o Ambiguous or erroneous uses of RFC2119 terms have been corrected. o Ambiguous or erroneous uses of RFC2119 terms have been corrected.
o References to obsolete RFCs have been updated. o References to obsolete RFCs have been updated.
o An IANA Considerations Section has been added, which specifies the o An IANA Considerations Section has been added, which specifies the
port assignments for NFS/RDMA. This replaces the example port assignments for NFS/RDMA. This replaces the example
assignment that appeared in [RFC5666]. assignment that appeared in [RFC5666].
o Code excerpts have been removed, and figures have been modernized. o Code excerpts have been removed, and figures have been modernized.
Appendix B. Acknowledgments Acknowledgments
The author gratefully acknowledges the work of Brent Callaghan and The author gratefully acknowledges the work of Brent Callaghan and
Tom Talpey on the original NFS Direct Data Placement specification Tom Talpey on the original NFS Direct Data Placement specification
[RFC5667]. Tom contributed the text of Section 5.4.2. [RFC5667]. Tom contributed the text of Section 6.4.2.
Dave Noveck provided excellent review, constructive suggestions, and Dave Noveck provided excellent review, constructive suggestions, and
consistent navigational guidance throughout the process of drafting consistent navigational guidance throughout the process of drafting
this document. Dave contributed the text of Section 5.6 and this document. Dave contributed the text of Section 6.6 and
Section 6, and insisted on precise discussion of reply size Section 7, and insisted on precise discussion of reply size
estimation. estimation.
Thanks to Karen Deitke for her sharp observations about idempotency, Thanks to Karen Deitke for her sharp observations about idempotency,
NFS COMPOUNDs, and NFS sessions. NFS COMPOUNDs, and NFS sessions.
Special thanks go to Transport Area Director Spencer Dawkins, nfsv4 Special thanks go to Transport Area Director Spencer Dawkins, NFSV4
Working Group Chair Spencer Shepler, and nfsv4 Working Group Working Group Chair and Document Shepherd Spencer Shepler, and NFSV4
Secretary Thomas Haynes for their support. The author also wishes to Working Group Secretary Thomas Haynes for their support. The author
thank Bill Baker and Greg Marsden for their support of this work. also wishes to thank Bill Baker and Greg Marsden for their support of
this work.
Author's Address Author's Address
Charles Lever (editor)
Charles Lever
Oracle Corporation Oracle Corporation
1015 Granger Avenue 1015 Granger Avenue
Ann Arbor, MI 48104 Ann Arbor, MI 48104
USA United States of America
Phone: +1 248 816 6463 Phone: +1 248 816 6463
Email: chuck.lever@oracle.com Email: chuck.lever@oracle.com
 End of changes. 89 change blocks. 
187 lines changed or deleted 200 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/