Remote Procedure Call Encryption By Default
draft-cel-nfsv4-rpc-tls-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-02-11 | ||
| Replaced by | draft-ietf-nfsv4-rpc-tls | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Reviews | |||
| 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 | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-cel-nfsv4-rpc-tls-02.txt
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
Trond Myklebust
(trond.myklebust@hammerspace.com)
Chuck Lever
(chuck.lever@oracle.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)