From: Spencer Shepler (shepler@eng.sun.com)
Date: 11/13/01-10:56:14 AM Z
Date: Tue, 13 Nov 2001 10:56:14 -0600 From: Spencer Shepler <shepler@eng.sun.com> Subject: Re: new state model Message-ID: <20011113105614.D100510@dhcp-aus08-184.sun.com> On Tue, Peter ?strand wrote: > > > My guess right now is that the new state model is implementable. But only > > > experience will tell. > > > > Agreed. First order of business on Monday will be to work out the > > details with everyone. I will summarize that discussion and post to > > the WG alias (along with some pictures, hopefully). > > I've been waiting for a summarize for almost four weeks now. How is the > work going? > > Another thing: Some issues, but not all, on > http://www.nfsv4.org/rfc3010updates/issues.html are already introduced in > the protocol definition file > http://www.nfsv4.org/rfc3010updates/nfs4_prot.x. But as far as I > understand, there is no information about which changes are already > introduced and which remains to be done. This makes it very hard to follow > the changes. Is nfs4_prot.x version controlled? In that case, would it be > possible to get access to the Changelog? I apologize for not getting the descriptions out earlier. I am working to generate an IETF draft for the deadline this week; while this will contain a set of changes it will unfortunately not include a large set of descriptive text for the changes to the state model; those will be forthcoming however. The change log for the nfs4_prot.x is somewhat sparse and has been for my own record keeping. For these latest updates, the changelog has no additional information. > If we expect lots more work on the protocol, maybe it would be easier to > use Bugzilla, IssueZilla or something like that instead of the current, > HTML-based TODO-list. Well, once we work through the current issues list, that "should" be it before working the draft to the next version of the NFSv4 RFC. At this point, I would prefer to spend my energies on getting the issues resolved. -- Spencer
This archive was generated by hypermail 2.1.2 : 03/04/05-01:49:21 AM Z CST