Identifying Implementations in NFSv4
draft-eisler-nfsv4-impid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mike Eisler | ||
| Last updated | 2005-08-22 | ||
| 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
NFSv4.0 has no method for allowing clients and servers to provide to each other their implementation identities. An implementation identity might contain the name of the software that embodies the NFSv4 client or server, and the version number of the software. This proposal describes how a future minor version of NFSv4.0 could allow clients and servers to exchange implementation identities.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)