NFSv4.0 migration: Implementation experience and spec issues to resolve
draft-dnoveck-nfsv4-migration-issues-02

Document Type Expired Internet-Draft (individual)
Last updated 2012-07-30 (latest revision 2012-01-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-dnoveck-nfsv4-migration-issues-02.txt

Abstract

The migration feature of NFSv4 provides for moving responsibility for a single filesystem from one server to another, without disruption to clients. Recent implementation experience has shown problems in the existing specification for this feature. This document discusses the issues which have arisen and explores the options available for curing the issues via clarification and correction of the NFSv4.0 specification.

Authors

Bill Baker (bill.baker@oracle.com)
Chuck Lever (chuck.lever@oracle.com)
David Noveck (david.noveck@emc.com)
Piyush Shivam (piyush.shivam@oracle.com)

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