Last Call: <draft-ietf-nfsv4-rfc3530-migration-update-07.txt> (NFSv4.0 migration: Specification Update) to Proposed Standard

The IESG <> Mon, 04 January 2016 15:30 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 644E71A8994; Mon, 4 Jan 2016 07:30:01 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-nfsv4-rfc3530-migration-update-07.txt> (NFSv4.0 migration: Specification Update) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 04 Jan 2016 07:30:01 -0800
Archived-At: <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jan 2016 15:30:01 -0000

The IESG has received a request from the Network File System Version 4 WG
(nfsv4) to consider the following document:
- 'NFSv4.0 migration: Specification Update'
  <draft-ietf-nfsv4-rfc3530-migration-update-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-01-18. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   The migration feature of NFSv4 allows for responsibility for a single
   filesystem to move from one server to another, without disruption to
   clients.  Recent implementation experience has shown problems in the
   existing specification for this feature in NFSv4.0.  This document
   clarifies and corrects RFC7530 (the NFSv4.0 specification) to address
   these problems.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.