<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-nfsv4-rfc3530-migration-update" target="https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-rfc3530-migration-update-00">
   <front>
      <title>NFSv4.0 migration: Specification Update</title>
      <author initials="D." surname="Noveck" fullname="David Noveck">
         </author>
      <author initials="P." surname="Shivam" fullname="Piyush Shivam">
         </author>
      <author initials="C." surname="Lever" fullname="Chuck Lever">
         </author>
      <author initials="B." surname="Baker" fullname="Bill Baker">
         </author>
      <date month="November" day="20" year="2012" />
      <abstract>
	 <t>   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 the NFSv4.0 specification (RFC3530 and
   possible successors) to address these problems.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nfsv4-rfc3530-migration-update-00" />
   
</reference>
