[nfsv4] FW: New Version Notification for draft-dnoveck-nfsv4-migration-issues-02.txt

<david.noveck@emc.com> Tue, 17 January 2012 16:18 UTC

Return-Path: <david.noveck@emc.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD6021F8692 for <nfsv4@ietfa.amsl.com>; Tue, 17 Jan 2012 08:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level:
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.387, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8xKGVSkSpRI for <nfsv4@ietfa.amsl.com>; Tue, 17 Jan 2012 08:18:25 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8244421F8688 for <nfsv4@ietf.org>; Tue, 17 Jan 2012 08:18:25 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q0HGIN10007868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <nfsv4@ietf.org>; Tue, 17 Jan 2012 11:18:23 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <nfsv4@ietf.org>; Tue, 17 Jan 2012 11:18:12 -0500
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q0HGIBQU003798 for <nfsv4@ietf.org>; Tue, 17 Jan 2012 11:18:12 -0500
Received: from mx31a.corp.emc.com ([169.254.1.100]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Tue, 17 Jan 2012 11:18:11 -0500
From: david.noveck@emc.com
To: nfsv4@ietf.org
Date: Tue, 17 Jan 2012 11:18:10 -0500
Thread-Topic: New Version Notification for draft-dnoveck-nfsv4-migration-issues-02.txt
Thread-Index: AczUcPeT6WWtoqAITxueQG65cLj+aAAw6Ycw
Message-ID: <5DEA8DB993B81040A21CF3CB332489F6963D4AB8@MX31A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [nfsv4] FW: New Version Notification for draft-dnoveck-nfsv4-migration-issues-02.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 16:18:26 -0000

 

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, January 16, 2012 12:04 PM
To: Noveck, David
Cc: bill.baker@oracle.com; piyush.shivam@oracle.com; chuck.lever@oracle.com; Noveck, David
Subject: New Version Notification for draft-dnoveck-nfsv4-migration-issues-02.txt

A new version of I-D, draft-dnoveck-nfsv4-migration-issues-02.txt has been successfully submitted by David Noveck and posted to the IETF repository.

Filename:	 draft-dnoveck-nfsv4-migration-issues
Revision:	 02
Title:		 NFSv4.0 migration: Implementation experience and spec issues to resolve
Creation date:	 2012-01-16
WG ID:		 Individual Submission
Number of pages: 37

Abstract:
   The migration feature of NFSv4 provides for moving responsibility for
   a single filesystem from one server to another, without disruption to
   clients.  Recent implementation experience has shown problems in the
   existing specification for this feature.  This document discusses the
   issues which have arisen and explores the options available for
   curing the issues via clarification and correction of the NFSv4.0
   specification.

                                                                                  


The IETF Secretariat