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

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4A27C580FE23C3E7E55C905E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 8/1/2011 1:13 PM, Russ Allbery wrote:
> As nice as it would be to be able to represent old timestamps in the fi=
le
> system, we've never been able to before (at least consistently), and I
> think the simplicity benefits for compatibility with current code bases=
 of
> sticking with the POSIX epoch are substantial.
>
> I don't have an opinion on the granularity.  For me, the benefits of
> matching NFS and the POSIX timestamp granularity is fairly evenly balan=
ced
> against the drawbacks of increasing the size of all of our protocol
> packets.

I have a strong desire to ensure that everything that can be represented
in an NTFS file system can be represented in AFS.  I don't care if the
epoch is the same or if the granularity is better than 100ns or not.

I am concerned about the size of status structures given how frequently
they are sent and because the size of the status structure determines
how many FIDs can be specified in a single Bulk Status request.

It would be nice if we could have some form of compressed time
representation that only sent the required number of bits necessary to
represent the required granularity.

Jeffrey Altman


--------------enig4A27C580FE23C3E7E55C905E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJONuTdAAoJENxm1CNJffh4/1EH/2edEyuNmABtPOma63yPvItC
dlmgGYHO5YnJyW7dsoPyE4+wtorPCPFpVIriwIyke7eXhBjDHYod0sE+PjMa00US
elGszsC+O8YFReJQkvCUo6K82sTNmjIDI95tFtTWPuPM4NDniN7HW2IhjqbIZOX1
pArwMylZD2BUk+GjPbpElgWqQoFhB96pHgmS4UK94brY9wGfjo/geMWgN/kLm5OP
pGtiAhj01mDrr5qKYe8l0fQm9EVd2BTB2TI7flshB5foFFx+86LadxQdyhUciDdg
W6NHvqbEbDPoHvOqsrHg4bvxYQnsXBkDGsnC2goeZ3B1pMKt466GHoUbBtEAXXU=
=EWEN
-----END PGP SIGNATURE-----

--------------enig4A27C580FE23C3E7E55C905E--