[AFS3-std] A call for consensus on draft-deason-afs3-type-time-02

[Steven Jenkins]

On Wed, Jul 27, 2011 at 11:34 PM, Matt W. Benjamin <matt@linuxbox.com> wrot=
e:
> Hi Steven,
>
> It seems as if the natural interop scenarios with NFSv4 involve convertin=
g from a common (e.g., lfs) time representation. =A0What am I missing?

I don't know that all interactions would be from a common local
filesystem; for example, what if someone wanted to put AFS on top of
NFSv4?

Also, staying with the main goals of the proposal: i.e., that higher
levels of granularity for time are available and that the additional
information can be useful to various components in AFS, then if other
filesystems already have finer levels of granularity than what is
proposed, then the proposed RFC is already out of date, as a
replacement RFC would need to be done to increase the level of
granularity yet again.

i.e., we should future proof this proposal by taking the finest level
of granularity in existing filesystems.

Thank you,
Steven