[nfsv4] Some stuff on referrals/migration

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Noveck, Dave (Dave.Noveck@netapp.com)
Date: 05/19/04-08:31:15 AM Z


Message-ID: <C8CF60CFC4D8A74E9945E32CF096548AB80DEE@silver.nane.netapp.com>
From: "Noveck, Dave" <Dave.Noveck@netapp.com>
Subject: [nfsv4] Some stuff on referrals/migration
Date: Wed, 19 May 2004 06:31:15 -0700


At various testing events I've promised to write up my thoughts on how
to do 
referrals in v4, using the existing migration facility.  In many cases,
I
indicated that I would do it in a few weeks.  Well weeks have turned
into
(many) months and still no write-up.  Given that I'm going to see many
of 
you at the bakeathon, I've decided to avoid further embarrassment by
just
doing what I said I would, even though quite a bit late.  

Attached are two html files.  The first is a kind of cookbook that
explains 
how I think referrals should happen and what the client and server
should 
each do about points that are not so clear in RFC3530.  The second is
broadly
consistent with the first (I hope) but has a different focus.  It
explains
how the spec should be modified to be clearer about migration
implementation
issues including referral.  Since RFC3530 is not modifiable any more,
the 
discussion is in terms of the spec for v4.1, even though there are no
actual 
changes to the protocol (at least if one adopts the "correct"
interpretation
of v4.0, i.e. mine, on any unclear points).

   





_______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-02:13:29 AM Z CST