@techreport{ietf-nfsv4-referrals-00,
    number =    {draft-ietf-nfsv4-referrals-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-nfsv4-referrals/00/},
    author =    {David Noveck and Rodney Burnett},
    title =     {{Implementation Guide for Referrals in NFSv4}},
    pagetotal = 24,
    year =      2005,
    month =     jul,
    day =       8,
    abstract =  {RFC3530 describes a migration feature using the NFS4ERR\_MOVED error code and the fs\_locations attribute. The description focuses on the case of migration (i.e. relocation) of a file system already known to the client. The simpler limiting case in a which a file system not previously known to the client was located elsewhere, which we here call a referral, was not clearly described. Because of this and also because of some inconsistencies and ambiguities in the text of RFC3530, there has been confusion about how the client and server should interact in performing a referral. This document provides a guide to the implementation of referrals, and in so doing, addresses the relevant problems in RFC3530.},
}