NFSv4 Migration and Trunking: Implementation and Specification Issues
draft-ietf-nfsv4-migration-issues-16
Document | Type |
Expired Internet-Draft
(nfsv4 WG)
Expired & archived
|
|
---|---|---|---|
Authors | David Noveck , Piyush Shivam , Chuck Lever , Bill Baker | ||
Last updated | 2019-02-23 (Latest revision 2018-08-22) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Spencer Dawkins | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses a range of implementation and specification issues concerning features related to the use of location-related attributes in NFSv4. These include migration, which transfers responsibility for a file system from one server to another, and trunking which deals with the discovery and control of the set of server endpoints to use to access a file system. The focus of the discussion, which relates to multiple minor versions, is on defining the appropriate clarifications and corrections for existing specifications.
Authors
David Noveck
Piyush Shivam
Chuck Lever
Bill Baker
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)