<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-nfsv4-migration-issues" target="https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-migration-issues-09">
   <front>
      <title>NFSv4 migration: Implementation experience and spec issues to resolve</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="February" day="19" year="2016" />
      <abstract>
	 <t>   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.  It also explains the choices made regarding
   updating the NFSv4.0 specification and those to be made with regard
   to the NFSv4.1 specification, in order to properly address migration.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nfsv4-migration-issues-09" />
   
</reference>
