End-to-end Data Integrity For NFSv4
draft-cel-nfsv4-end2end-data-protection-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chuck Lever | ||
| Last updated | 2014-04-21 (Latest revision 2013-10-18) | ||
| 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
End-to-end data integrity protection provides a strong guarantee that data an application reads from durable storage is exactly the same data it wrote previously to durable storage. This document specifies possible additions to the NFSv4 protocol enabling it to convey end- to-end data integrity information between client and server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)