NFS Version 4 ACLs
draft-ietf-nfsv4-acls-00
| Document | Type |
Expired Internet-Draft
(nfsv4 WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sam Falkner , Lisa Week | ||
| Last updated | 2015-10-14 (Latest revision 2006-02-17) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| 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 | Lars Eggert | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
NFS version 4 (specified in RFC 3530) Access Control Lists (ACLs) provide more fine grained control than previous file permission models, but before the full benefit of the model can be exploited, some changes and clarifications must be made. This document will describe the details that implementors should consider in order to allow implementations to function and interoperate better.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)