RE: NFSv4 at Proposed Standard (was Re: downgrade/upgrade)

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

From: Noveck, Dave (Dave.Noveck@netapp.com)
Date: 11/07/00-12:51:09 PM Z


Message-ID: <BC0FBE708897D4118C5500902745938E21E439@black.eng.netapp.com>
From: "Noveck, Dave" <Dave.Noveck@netapp.com>
Subject: RE: NFSv4 at Proposed Standard (was Re: downgrade/upgrade)
Date: Tue, 7 Nov 2000 10:51:09 -0800 


> I don't feel comfortable changing NFSv4 in an incompatible way after
> it reaches Proposed state.  IMHO, if the WG decides that the protocol
> needs to be changed in an incompatible way then it needs to make the
> decision to retract the draft and reapply for IESG approval after we
> have made the appropriate changes.

That works for this time (assuming we can agree on what a stateid means 
and how big it is).  But, what about next time?

The assumption seems to be that the spec is perfect (except for 
clarifications) and that we will not need to make further changes.
While that is possible, I don't think we should count on it.

I think implementation experience is going to show problems.  Be
prepared for incidents of "What could we have been thinking?".  
If they don't happen, consider it a bonus.






 


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-01:48:23 AM Z CST