RFC 9289: Towards Remote Procedure Call Encryption by Default

In plain English — editorial summary, not part of the RFC

This document describes a mechanism that, through the use of opportunistic Transport Layer Security (TLS), enables encryption of Remote Procedure Call (RPC) transactions while they are in transit. The proposed mechanism interoperates with Open Network Computing (ONC) RPC implementations that do not support it. This document updates RFC 5531.

Document record

Document ID

RFC9289

Published

September 2022

Authors

T. Myklebust; C. Lever

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

21

Also known as

—

Updates:

RFC 5531

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC9289

Topics

• network file system
• remote procedure call
• transport layer security
• X.509

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 5667Network File System (NFS) Direct Data PlacementObsoleted

  January 2010

• RFC 5666Remote Direct Memory Access Transport for Remote Procedure CallObsoleted

  January 2010

• RFC 5661Network File System (NFS) Version 4 Minor Version 1 ProtocolObsoleted

  January 2010

• RFC 3530Network File System (NFS) version 4 ProtocolObsoleted

  April 2003

• RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated

  December 2002

• RFC 2623NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5Current

  June 1999

• RFC 9295Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm IdentifiersCurrent

  September 2022

• RFC 9323A Profile for RPKI Signed Checklists (RSCs)Current

  November 2022

Also filed under

• PROPOSED STANDARD
• 2022
• IETF stream
• wit area