On 23 Sep 2009, at 12:37, Simon Wilkinson wrote:
In the interests of moving forward, I'd like to propose a last call for comments. Please take the time to review the document, and make comments for and against to this list by Fri 23rd October.
The only issue that's been raised, to date, is that of how this interacts with RPC refresh. As far as I can see, the pertinent issue is whether we ship a draft, and assign code points to its RPCs, which we then revise a couple of months afterwards.
I think the key issue here is whether anyone is likely to ship code implementing extended callbacks before they implement the forthcoming RPC refresh. I've CC'd the OpenAFS gatekeepers on this email - if there are any other public (or private) AFS implementors here, it would be good to get a feeling of where we stand on this.
Also, if anyone else has comments, even if its just to say "I read the draft, I think its fine", those would be gratefully appreciated.
Thanks, Simon. _______________________________________________ AFS3-standardization mailing list [email protected] http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
