NFSv4 Requirements Spencer Shepler spencer.shepler@eng.sun.com - - PowerPoint PPT Presentation

42nd IETF NFSv4 Requirements Slide 1 of 11 Spencer Shepler

42nd IETF

NFSv4 Requirements

Spencer Shepler spencer.shepler@eng.sun.com

42nd IETF NFSv4 Requirements Slide 2 of 11 Spencer Shepler

WG Charter and Requirements

• First Milestone - deliver NFSv4 requirements I-D
• Identify limitations/deficiencies of NFS version 3
• Identify potential solutions for identified deficiencies
• Cost/benefit analysis of solutions
• Include experience or input from other existing distributed

file system work or products

• Schedule: August - first draft / September - final draft

42nd IETF NFSv4 Requirements Slide 3 of 11 Spencer Shepler

Design Philosophy

• NFSv3 protocol functionality is straightforward
• Simple protocol design -> straightforward implementation
• Extensibility or layering
• Managed Extensions or Minor Versioning

42nd IETF NFSv4 Requirements Slide 4 of 11 Spencer Shepler

Reliable and Available

• Simple design -> straightforward implementations
• Quick recovery from client/server/network failure
• Allow for availability solutions to be built (client/server)

42nd IETF NFSv4 Requirements Slide 5 of 11 Spencer Shepler

Scalable Performance

• Thousands of clients
• Throughput and latency of the network
• Server work load or scalability of operations at server
• Client caching
• Disconnected client operation (?)

42nd IETF NFSv4 Requirements Slide 6 of 11 Spencer Shepler

Interoperability

• NFSv3 is Unix centric
• Platform specific behavior in design
• Extended attributes
• Access Control Lists (ACLs)

42nd IETF NFSv4 Requirements Slide 7 of 11 Spencer Shepler

RPC Mechanism

• ONCRPC
• Managed by IETF
• UDP/TCP
• Simple data representation and procedure encoding
• RPCSEC_GSS provides flexibility in security model

42nd IETF NFSv4 Requirements Slide 8 of 11 Spencer Shepler

Security

• User Identification (UID/GID AUTH_SYS)
• Authentication based on RPCSEC_GSS
• Kerberos V5 for private key
• SPKM for public key
• Security Negotiation (automated)

42nd IETF NFSv4 Requirements Slide 9 of 11 Spencer Shepler

Internet Accessibility

• Transports (UDP/TCP or just TCP)
• One protocol (instead of MOUNT, NFS, NLM, ACL)
• Firewall traversal
• Caching Proxy Server usage
• Multiple RPCs and associated latency

42nd IETF NFSv4 Requirements Slide 10 of 11 Spencer Shepler

File Locking

• One protocol for file access and file locking
• Interoperability between operating environments
• Scalable solutions - thousands of clients
• Internet capable (firewall traversal, latency sensitive)
• Timely recovery in the event of client/server failure

42nd IETF NFSv4 Requirements Slide 11 of 11 Spencer Shepler

Internationalization

• More than 7-bit ASCII
• Unicode -> UTF-8 encoding for all strings
• Possible issues with user identification strings