Next Steps for NFSv4 Migration/Replication
draft-noveck-nfsv4-migrep-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Noveck , Rodney Burnett | ||
| Last updated | 2005-10-06 (Latest revision 2005-10-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The fs_locations attribute in NFSv4 provides support for fs migration, replication and referral. Given the current work on supporting these features, and the new needs such as support for global namespace, it is time to look at this area and see what further development of this protocol area may be required. This document makes suggestions for the further development of these features in NFSv4.1 and also presents ideas for work that might be done as part of future minor versions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)