Migration Issues for NFSv4
draft-noveck-nfsv4-migration-issues-00

Document Type Expired Internet-Draft (individual)
Last updated 2004-07-06
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-noveck-nfsv4-migration-issues-00.txt

Abstract

RFC3530 described an fs_locations attribute which can be used to allow an fs to migrate between servers without disrupting client access and to refer a client to another server providing access to a specified file system. Initial implementation work for this feature has exposed a number of areas where RFC3530's handling of the issues leaves something to be desired. This document makes a number of suggestions to remedy these issues when the NFSv4 spec next undergoes a significant revision, most likely in connection with implementing a new minor revision, such as NFSv4.1.

Authors

David Noveck (dnoveck@netapp.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)