Last Call Review of draft-ietf-nfsv4-mv0-trunking-update-02

Request Review of draft-ietf-nfsv4-mv0-trunking-update
Requested rev. no specific revision (document currently at 05)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-11-27
Requested 2018-11-05
Authors Chuck Lever, David Noveck
Draft last updated 2018-11-27
Completed reviews Opsdir Last Call review of -02 by Shwetha Bhandari (diff)
Secdir Last Call review of -02 by Christopher Wood (diff)
Assignment Reviewer Shwetha Bhandari 
State Completed
Review review-ietf-nfsv4-mv0-trunking-update-02-opsdir-lc-bhandari-2018-11-27
Reviewed rev. 02 (document currently at 05)
Review result Ready
Review completed: 2018-11-27


I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This document is an update to NFSv4.0 RFC 7530 to address migration issues with NFSv4.0 listed in draft-ietf-nfsv4-migration-issues. Specifically this document describes procedure for NFSv4.0 client to :
1. Do "trunking discovery" i.e a means of determining a set of alternate IP addresses that might be used to access the same server as an existing IP address. This is done using  the file system location-related attribute in NFS version 4.0 : fs_locations.
2. Handle the presence of multiple network addresses associated to the same server when recovering from a replication and migration event.
3. Handle changes in the contents of returned fs_locations attributes
In terms of network impact with the proposed trunking discovery NFSv4.0 client can send additional DNS queries to discover multiple addresses associated with the same server and attempt multiple connections with various connection types supported by NFSv4.0 protocol until the one preferred by the client is successfully established.
The proposed update to NFSv4.0 RFC7530 does not have any significant operational impact on the network.