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

[Derrick Brashear]

On Thu, Jul 28, 2011 at 10:00 AM, Steven Jenkins
<steven.jenkins@gmail.com> wrote:
> On Wed, Jul 27, 2011 at 11:34 PM, Matt W. Benjamin <matt@linuxbox.com> wr=
ote:
>> Hi Steven,
>>
>> It seems as if the natural interop scenarios with NFSv4 involve converti=
ng 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.
>

well, in a universe where we have defined extended unions, perhaps a
non-fixed-size time, allowing additional precision without requiring
it, would be the answer?
i still think it's would be preferable to, at this time, discard
precision than to bloat every use of time in an RPC.

--=20
Derrick