Comment 2 for bug 1722530

As someone who has thought about use of timing systems in data acquisitions, having a 64-bit tag simply to enable a life-of-facility odometer is not compelling. When applied to secPastEpoch, the same argument suggests expanding to 64-bits unsigned. I hope that this suggests some redundancy in these two ideas. IMO, taking as a timestamp the time at which this counter ticks is more generally useful.

For this reason, I would rather see secPastEpoch expanded to 64-bits along with a 32-bit tag.