NFSv4 Migration and Trunking: Implementation and Specification Issues
draft-ietf-nfsv4-migration-issues-16
| Document | Type | Expired Internet-Draft (nfsv4 WG) | |
|---|---|---|---|
| Last updated | 2019-02-23 (latest revision 2018-08-22) | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-nfsv4-migration-issues-16.txt
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
(davenoveck@gmail.com)
Piyush Shivam
(piyush.shivam@ibm.com)
Chuck Lever
(chuck.lever@oracle.com)
Bill Baker
(bill.baker@oracle.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)