Bev Crair Engineering Manager Sun Microsystems, Inc. beverly.crair@sun.com

Agenda A little history Current IETF status NFS v4 focus & innovations Where to go for more information

1998 RFC2339 signed between Sun and the Internet Society in May, 1998 Sun Gives NFS Protocol to the IETF NFS defacto file sharing standard in UNIX Commitment to open, interoperable standards RFC2339 signed between Sun and the Internet Society in May, 1998 NFS v4 WG formed in Summer 1998

IETF Status for NFS v4 "NFS Version 4 Design Considerations" (RFC 2624) June 1999 IETF Last call complete on dd mm 2000 NFS v4 is now a Proposed Standard!! Internet Society now owns NFS v4

IETF Status for NFS v4 RFC is coming - editorial delay 7 implementations in progress Sun Solaris & Java Hummingbird Communications Network Appliance EMC University of Michigan (CITI) Linux and OpenBSD

IETF NFS v4 Success NFS v3 NFS v4 2 implementations at specification complete NFS v4 7 implementations in progress at specification complete Achieved wider review of NFS v4 - significantly increased community involvement

IETF NFS v4 Future Draft Standard is next step IETF Requirements from Proposed to Draft 6 months, minimum 2 complete, separately developed, interoperating implementations Test report

How Will We Get There? Bake-Offs 'mini' Connectathons aimed at testing implementations of NFS v4 5 core teams participating Sun, Hummingbird, Network Appliance, EMC, University of Michigan/CITI anyone is welcome 3 bake-offs completed to date 1 being held this week

How Will We Get There? Providing Solaris prototype binaries used for testing both clients & servers Snoop updated for NFS v4 NFSv4Shell TCL-based client test framework provided free Delegation tests from Network Appliance

Future NFS v4 WG Work Implementation RFC Server-to-server transfer protocol for migration/replication support SNMP MIB Name spaces/LDAP schemas Service Location Protocol Disconnected operation

Protocol Design Goals Internet Access Platform Interoperability open standards means heterogeneous environments Strong Security IETF Requirement Extensible Protocol change must become easier

Internet Access Compound Operations Internationalization 'bunches up' a set of operations into a single request Decreases number of round trips Useful in a high-latency network Internationalization Use of Unicode via UTF-8 Firewall Friendly Call backs from server not needed

Platform Interoperability String-based User Identification Scales beyond UNIX UID/GID pairs File Locking Integration into protocol makes stronger implementations Leased based recovery

Platform Interoperability File Attributes Windows and Unix attributes Includes NT-Style ACLs Mandatory, Recommended, and Named types Volatile File Handles Allows for varying server implementations

Security RPC, XDR, RPCSEC_GSS as foundation RFC1831, RFC1832, RFC2203 Security (mandatory to implement) Kerberos V5 currently available in many implementations LIPKEY Low Infrastructure Public Key mechanism Security negotiation Allows flexible security handling

Extensibility Protocol is designed to allow for minor version modifications over time Implementations can progress without waiting for new protocol definitions

NFS v4 Innovations Server Namespace Replication/Migration Enables traversal of all shared file systems from single point on the server Replication/Migration Definition of support and client behavior

NFS v4 Innovations One protocol Delegation MOUNT and NLM functionality integrated into NFS v4 Delegation Allows client to avoid server contact by caching when sharing does not occur

For More Information NFS v4 Website NFS v4 Working Group http://www.nfsv4.org NFS v4 Working Group http://www.ietf.org/html.charters/nfsv4-charter.html Archive: http://playground.sun.com/pub/nfsv4/nfsv4-wg-archive/ NFS v4 White Paper http://www.nfsv4.org/wp.pdf