Remote Procedure Call Encryption By Default
draft-cel-nfsv4-rpc-tls-02
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Trond Myklebust , Chuck Lever | ||
| Last updated | 2019-02-11 | ||
| Replaced by | draft-ietf-nfsv4-rpc-tls | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews |
SECDIR Early review
by Alan DeKok
Not ready
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-nfsv4-rpc-tls | |
| 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
This document describes a mechanism that enables encryption of in- transit Remote Procedure Call (RPC) transactions with minimal administrative overhead and full interoperation with RPC implementations that do not support this mechanism. This document updates RFC 5531.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)