[nfsv4] I-D ACTION:draft-ietf-nfsv4-rfc1832bis-02.txt

Internet-Drafts@ietf.org Fri, 24 October 2003 06:34 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18359 for <nfsv4-archive@odin.ietf.org>; Fri, 24 Oct 2003 02:34:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACvWS-00079I-81 for nfsv4-archive@odin.ietf.org; Fri, 24 Oct 2003 02:34:08 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O6Y8pg027463 for nfsv4-archive@odin.ietf.org; Fri, 24 Oct 2003 02:34:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACvWR-00078o-4Q for nfsv4-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 02:34:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18337 for <nfsv4-web-archive@ietf.org>; Fri, 24 Oct 2003 02:33:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACvWN-0006Tm-00 for nfsv4-web-archive@ietf.org; Fri, 24 Oct 2003 02:34:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACvWM-0006Ti-00 for nfsv4-web-archive@ietf.org; Fri, 24 Oct 2003 02:34:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACvWL-00072O-Iv; Fri, 24 Oct 2003 02:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACfh0-0003gu-0U for nfsv4@optimus.ietf.org; Thu, 23 Oct 2003 09:39:58 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19866; Thu, 23 Oct 2003 09:39:46 -0400 (EDT)
Message-Id: <200310231339.JAA19866@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: nfsv4@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [nfsv4] I-D ACTION:draft-ietf-nfsv4-rfc1832bis-02.txt
Sender: nfsv4-admin@ietf.org
Errors-To: nfsv4-admin@ietf.org
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/nfsv4/>
X-Original-Date: Thu, 23 Oct 2003 09:39:46 -0400
Date: Thu, 23 Oct 2003 09:39:46 -0400

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		: XDR: External Data Representation Standard
	Author(s)	: M. Eisler, et. al.
	Filename	: draft-ietf-nfsv4-rfc1832bis-02.txt
	Pages		: 25
	Date		: 2003-10-22
	
This document describes the External Data Representation Standard
(XDR) protocol as it is currently deployed and accepted.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-rfc1832bis-02.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-ietf-nfsv4-rfc1832bis-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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nfsv4-rfc1832bis-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.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-nfsv4-rfc1832bis-02.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-nfsv4-rfc1832bis-02.txt>