[nfsv4] I-D ACTION:draft-ietf-nfsv4-repl-mig-proto-01.txt

Internet-Drafts@ietf.org Thu, 29 May 2003 11:42 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28117 for <nfsv4-archive@odin.ietf.org>; Thu, 29 May 2003 07:42:19 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4TBfoj14135 for nfsv4-archive@odin.ietf.org; Thu, 29 May 2003 07:41:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TBfnB14132 for <nfsv4-web-archive@optimus.ietf.org>; Thu, 29 May 2003 07:41:49 -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 HAA28098 for <nfsv4-web-archive@ietf.org>; Thu, 29 May 2003 07:41:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LLlS-0005mf-00 for nfsv4-web-archive@ietf.org; Thu, 29 May 2003 07:40:10 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LLlS-0005mc-00 for nfsv4-web-archive@ietf.org; Thu, 29 May 2003 07:40:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TBfjB14119; Thu, 29 May 2003 07:41:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TBKNB12035 for <nfsv4@optimus.ietf.org>; Thu, 29 May 2003 07:20:23 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26947; Thu, 29 May 2003 07:20:22 -0400 (EDT)
Message-Id: <200305291120.HAA26947@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-repl-mig-proto-01.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/pipermail/nfsv4/>
X-Original-Date: Thu, 29 May 2003 07:20:22 -0400
Date: Thu, 29 May 2003 07:20:22 -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		: A Server-to-Server Replication/Migration Protocol
	Author(s)	: R. Thurlow
	Filename	: draft-ietf-nfsv4-repl-mig-proto-01.txt
	Pages		: 30
	Date		: 2003-5-28
	
NFS Version 4 [RFC3010] provided support for client/server
interactions to support replication and migration, but left
unspecified how replication and migration would be done.  This
document is an initial draft of a protocol which could be used to
transfer filesystem data and metadata for use with replication and
migration services for NFS Version 4.

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