idnits 2.17.1 draft-ietf-nfsv4-rfc3010bis-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3530 5 Title: Network File System (NFS) version 4 Protocol 6 Author(s): S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, 7 C. Beame, M. Eisler, D. Noveck 8 Status: Standards Track 9 Date: April 2003 10 Mailbox: spencer.shepler@sun.com, beame@bws.com, 11 brent.callaghan@sun.com, mike@eisler.com, 12 dnoveck@netapp.com, david.robinson@sun.com, 13 robert.thurlow@sun.com 14 Pages: 275 15 Characters: 600986 16 Obsoletes: 3010 18 I-D Tag: draft-ietf-nfsv4-rfc3010bis-05.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3530.txt 22 The Network File System (NFS) version 4 is a distributed filesystem 23 protocol which owes heritage to NFS protocol version 2, RFC 1094, and 24 version 3, RFC 1813. Unlike earlier versions, the NFS version 4 25 protocol supports traditional file access while integrating support 26 for file locking and the mount protocol. In addition, support for 27 strong security (and its negotiation), compound operations, client 28 caching, and internationalization have been added. Of course, 29 attention has been applied to making NFS version 4 operate well in an 30 Internet environment. 32 This document replaces RFC 3010 as the definition of the NFS version 4 33 protocol. 35 This document is a product of the Network File System Version 4 36 Working Group of the IETF. 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.