RFC 8587: NFS Version 4.0 Trunking Update

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

In NFS version 4.0, the fs_locations attribute informs clients about alternate locations of file systems. An NFS version 4.0 client can use this information to handle migration and replication of server file systems. This document describes how an NFS version 4.0 client can also use this information to discover an NFS version 4.0 server's trunking capabilities. This document updates RFC 7530.

Document record

Document ID

RFC8587

Published

May 2019

Authors

C. Lever; D. Noveck

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

22

Also known as

—

Updates:

RFC 7530

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

Topics

• NFSv4.0
• migration
• replication
• trunking
• fs_locations
• transparent state migration

Related documents

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

• RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent

  January 2021

• RFC 9566Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IPCurrent

  April 2024

• RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent

  August 2014

• RFC 6459IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS)Current

  January 2012

• RFC 5947Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)Current

  September 2010

• RFC 2334Server Cache Synchronization Protocol (SCSP)Current

  April 1998

• RFC 8586Loop Detection in Content Delivery Networks (CDNs)Current

  April 2019

• RFC 8613Object Security for Constrained RESTful Environments (OSCORE)Current

  July 2019

Also filed under

• PROPOSED STANDARD
• 2019
• IETF stream
• wit area