Browse Prior Art Database

NFS Version 4 Design Considerations (RFC2624)

IP.com Disclosure Number: IPCOM000003211D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 18 page(s) / 49K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Shepler: AUTHOR

Abstract

The main task of the NFS version 4 working group is to create a protocol definition for a distributed file system that focuses on the following items: improved access and good performance on the Internet, strong security with negotiation built into the protocol, better cross-platform interoperability, and designed for protocol extensions. NFS version 4 will owe its general design to the previous versions of NFS. It is expected, however, that many features will be quite different in NFS version 4 than previous versions to facilitate the goals of the working group and to address areas that NFS version 2 and 3 have not.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group S. Shepler

Request for Comments: 2624 Sun Microsystems, Inc.

Category: Informational June 1999

NFS Version 4 Design Considerations

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

The main task of the NFS version 4 working group is to create a

protocol definition for a distributed file system that focuses on the

following items: improved access and good performance on the

Internet, strong security with negotiation built into the protocol,

better cross-platform interoperability, and designed for protocol

extensions. NFS version 4 will owe its general design to the

previous versions of NFS. It is expected, however, that many

features will be quite different in NFS version 4 than previous

versions to facilitate the goals of the working group and to address

areas that NFS version 2 and 3 have not.

This design considerations document is meant to present more detail

than the working group charter. Specifically, it presents the areas

that the working group will investigate and consider while developing

a protocol specification for NFS version 4. Based on this

investigation the working group will decide the features of the new

protocol based on the cost and benefits within the specific feature

areas.

Key Words

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in RFC 2119.

Table of Contents

1. NFS Version 4 Design Considerations . . . . . . . . . . . . . 2

2. Ease of Implementation or Complexity of Protocol . . . . . . 3

2.1. Extensibility / layering . . . . . . . . . . . . . . . . . 3

2.2. Managed Extensions or Minor Versioning . . . . . . . . . . 3

2.3. Relationship with Older Versions of NFS . . . . . . . . . . 4

3. Reliable and Available . . . . . . . . . . . . . . . . . . . 5

4. Scalable Performance . . . . . . . . . . . . . . . . . . . . 5

4.1. Throughput and Latency via the Network . . . . . . . . . . 6

4.2. Client Caching . . . . . . . . . . . . . . . . . . . . . . 6

4.3. Disconnected Client Operation . . . . . . . . . . . . . . . 7

5. Interoperability . . . . . . . . . . . . . . . . . . . . . . 7

5.1. Platform Specific Behavior . . . . . . . . . . . . . . . . 8

5.2. Additional or Extended Attributes . . . . . . . . . . . . . 8

5.3. Access Control Lists . . . . . . . . . . . . . . . . . . 9

6. RPC Mechanism and Security . . . . . . . . . . . . . . . . 10

6.1. User identification . . . . . . . . . . . . . . . . . . . 10

6.2. Security . . . . . . . . . . . . . . ...