< draft-ietf-nfsv4-mv0-trunking-update-04.txt   draft-ietf-nfsv4-mv0-trunking-update-05.txt >
Network File System Version 4 C. Lever, Ed. Network File System Version 4 C. Lever, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Updates: 7530 (if approved) D. Noveck Updates: 7530 (if approved) D. Noveck
Intended status: Standards Track NetApp Intended status: Standards Track NetApp
Expires: August 5, 2019 February 1, 2019 Expires: August 5, 2019 February 1, 2019
NFS version 4.0 Trunking Update NFS version 4.0 Trunking Update
draft-ietf-nfsv4-mv0-trunking-update-04 draft-ietf-nfsv4-mv0-trunking-update-05
Abstract Abstract
The file system location-related attribute in NFS version 4.0, The file system location-related attribute in NFS version 4.0,
fs_locations, informs clients about alternate locations of file fs_locations, informs clients about alternate locations of file
systems. An NFS version 4.0 client can use this information to systems. An NFS version 4.0 client can use this information to
handle migration and replication of server filesystems. This handle migration and replication of server filesystems. This
document describes how an NFS version 4.0 client can additionally use document describes how an NFS version 4.0 client can additionally use
this information to discover an NFS version 4.0 server's trunking this information to discover an NFS version 4.0 server's trunking
capabilities. This document updates RFC 7530. capabilities. This document updates RFC 7530.
skipping to change at page 12, line 5 skipping to change at page 12, line 5
NFS version 4.0 may be implemented using a number of different types NFS version 4.0 may be implemented using a number of different types
of connections: of connections:
Stream connections may be used to provide RPC service, as Stream connections may be used to provide RPC service, as
described in [RFC5531]. described in [RFC5531].
RDMA-capable connections may be used to provide RPC service, as RDMA-capable connections may be used to provide RPC service, as
described in [RFC8166]. described in [RFC8166].
Because of the need to support multiple connections, clients face the Because of the need to support multiple connection types, clients
issue of determining the proper connection type to use when face the issue of determining the proper connection type to use when
establishing a connection to a server network address. The establishing a connection to a server network address. The
fs_locations attribute provides no information to support connection fs_locations attribute provides no information to support connection
type selection. As a result, clients supporting multiple connection type selection. As a result, clients supporting multiple connection
types need to attempt to establish a connection on various connection types need to attempt to establish a connection on various connection
types allowing it to determine, via a trial-and-error approach, which types allowing it to determine, via a trial-and-error approach, which
connection types are supported. connection types are supported.
If a client strongly prefers one connection type, it can perform If a client strongly prefers one connection type, it can perform
these attempts serially in order of declining preference. Once there these attempts serially in order of declining preference. Once there
is a successful attempt, the established connection can be used. is a successful attempt, the established connection can be used.
 End of changes. 2 change blocks. 
3 lines changed or deleted 3 lines changed or added

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