Subject: [nfsv4] Fwd: I-D ACTION:draft-talpey-nfs-rdma-problem-statement-01.txt

From: "Talpey, Thomas" <[email-masked]>
Date: Fri, 13 Feb 2004 13:28:54 -0800

FYI the NFS/RDMA Problem statement has been updated.
The changes are minor, largely updating the references.
Comments are welcome.

Tom Talpey and Chet Juszczak.

> ---------- Forwarded Message ----------
>Subject: I-D ACTION:draft-talpey-nfs-rdma-problem-statement-01.txt
>Date: Fri, 13 Feb 2004 16:10:05 -0500
>From: <[email-masked]>
>Reply-To: <[email-masked]>
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>	Title		: NFS RDMA Problem Statement
>	Author(s)	: T. Talpey
>	Filename	: draft-talpey-nfs-rdma-problem-statement-01.txt
>	Pages		: 15
>	Date		: 2004-2-12
>	
>This draft addresses applying Remote Direct Memory Access to the
>NFS protocols.  NFS implementations historically incur significant
>overhead due to data copies on end-host systems, as well as other
>sources.  The potential benefits of RDMA to these implementations
>are explored, and the reasons why RDMA is especially well-suited to
>NFS and network file protocols in general are evaluated.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-talpey-nfs-rdma-problem-statement-
>01.txt
>
>To remove yourself from the IETF Announcement list, send a message to 
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>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-talpey-nfs-rdma-problem-statement-01.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-talpey-nfs-rdma-problem-statement-01.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.
>
>
> ---------- End of Forwarded Message ----------