On Fri, 29 Apr 2011 10:29:43 +0100 Simon Wilkinson <[email protected]> wrote:
> We discussed this at the hackathon. One of the things that came up > (and that has been reiterated by the RPC refresh work) is that the > difference between AFSTime and AFSTimestamp is unclear from the name, > and people get confused about what they are specifying. > > How about AFSTime (no resolution), AFSRelTime (relative, no > resolution) and AFSTimeRes (absolute, with resolution) I think I heard someone may have wanted something for 'absolute' in the first type name... would AFSAbsTime, AFSRelTime, and AFSTimeRes be okay? Also, should I put the "this is not an IETF standard" paragraph somewhere in the front matter? Does it go in an existing section, or should I make a new one? That is, this paragraph from the ISE discussions: >> "This document was produced by the AFS3-standardization group as >> extensions and updates to the existing AFS protocols. The existing >> AFS protocols are not IETF standard protocols and these extensions to >> that protocol are not to be considered IETF standards, they simply >> record the work of the AFS3-Standardization group." -- Andrew Deason [email protected] _______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
