Subject: New NFSv4 draft available

From: Spencer Shepler <[email-masked]>
Date: Tue, 26 Oct 1999 15:57:16 -0500

The latest draft in txt and html forms is also available at:
http://playground.sun.com/nfsv4/draft02/

Summary of changes in this recent draft:

ACL proposal - 	I have included Carl Beame's proposal.  Since it came in
		at the last minutes I did not have a chance to integrate
		a couple of changes he made based on feedback from the alias.
		Coming in the next version.

CREATE op -	The create op has been corrected so that symlinks and CHR/BLK
		file types can be created.  The operation was just broken
		previously. (NOTE that the operation description has not
		been updated; just the .x file)

READDIR op -	Based on a discussion at the bakeoff, a new attribute has been
		added (rdattr_error).  There is instance where the server
		may be unable to obtain attributes for a file within a directory
		when doing a READDIR.  It would be nice if the server had a
		way to return the rest of the READDIR information (directory
		listing and other file attributes) instead of failing the
		entire operation.  The server may now do this by returning
		the error in the rdattr_error attribute for the specific file
		for which the attribute get failed.  The client must ask
		for the rdattr_error attribute on the READDIR to obtain
		this behavior.  If the rdattr_error has not been requested,
		the server will fail the entire READDIR operation and return
		an error.

Other gratuitous changes in the .x file for name consistency/symmetry.

Spencer

[email-masked] wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 Working Group of the IETF.
> 
>         Title           : NFS version 4
>         Author(s)       : S. Shepler, B. Callaghan, M. Eisler,  D. Robinson,
>                           R. Thurlow,  D. Noveck, C.Beame
>         Filename        : draft-ietf-nfsv4-02.txt
>         Pages           : 212
>         Date            : 25-Oct-99
> 
> NFS version 4 is a distributed file system protocol which owes
> heritage to NFS versions 2 [RFC1094] and 3 [RFC1813].  Unlike earlier
> versions, NFS version 4 supports traditional file access while
> integrating support for file locking and the mount protocol.  In
> addition, support for strong security (and its negotiation), compound
> operations, and internationlization have been added.  Of course,
> attention has been applied to making NFS version 4 operate well in an
> Internet environment.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-02.txt
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-ietf-nfsv4-02.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         [email-masked].
> In the body type:
>         "FILE /internet-drafts/draft-ietf-nfsv4-02.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
>                                                   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Content-Type: text/plain
> Content-ID:     <[email-masked]>