Hi Again, Let me restate that.
The XCB draft should be read on its own. The only area where there could have been ambiguity was 64-bit time representation, as this was included, but had not been formally defined. The -implementation- happens to regard such timestamps as time values in seconds, but there is no claim in the specification that this is the case, so I would propose the daft should in that regard be read so as to reflect the 100-ns consensus from the hackathon, unless someone objects to that idea itself--which is again separate from XCB. For other areas of overlap, such as 64-bit values for AFSFid components, the draft should be interpreted as specifying no change from existing AFS-3 protocol definitions, because none was intended. The intention of other authors to propose changes to AFSFid is outside the scope of the XCB review, I believe. Matt ----- "Matt W. Benjamin" <[email protected]> wrote: > The expectation is that RPC refresh will affect XCB exactly as it > affects other eligible protocol elements. The use of afs_uint64 > values for timestamps in XCB, for example, will be defined to be > conformant with the time representation specified for RPC refresh. > > ----- "Jeffrey Hutzelman" <[email protected]> wrote: > > > --On Thursday, October 08, 2009 12:51:53 PM -0400 "Matt W. Benjamin" > > > <[email protected]> wrote: > > > > > Yes, there are RPC refresh dependencies. I don't believe any is > a > > > blocker for consensus, however, as evidenced by the request from > > the > > > hackathon to proceed. > > > > It's not a blocker for "we think this is a good idea". > > However, to publish a specification, we must reach rough consensus > on > > that > > specification, including all of the details. We can't leave things > to > > be > > "filled in later"; once we approve a document, there is no later. > > > > -- Jeff > > > > _______________________________________________ > > AFS3-standardization mailing list > > [email protected] > > > http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization > > -- > > Matt Benjamin > > The Linux Box > 206 South Fifth Ave. Suite 150 > Ann Arbor, MI 48104 > > http://linuxbox.com > > tel. 734-761-4689 > fax. 734-769-8938 > cel. 734-216-5309 > > _______________________________________________ > AFS3-standardization mailing list > [email protected] > http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 _______________________________________________ AFS3-standardization mailing list [email protected] http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
