"The point where I currently disagree with Rob and Randy is on the granularity of the timer. Whatever granularity is chosen bounds the maximum signing rate. Thus, if you use a 1-second clock, you can't sign more than 1 object/sec. (Well, you can cheat and "borrow" from future seconds, up to the actual clock skew, but that does cut your margin.) If we go with a nanosecond timer, we're limited to 10^9 objects/sec, ever. I'm not convinced we can predict the future well enough to know that that's reasonable, so I've suggested that the spec support fractional seconds -- we can always extend the number of significant digits to the right of the radix point without a protocol change.
I could live with a 10^9 message/sec limitation (it's not a system global, but per client/server relation)... If that's not enough, the <timestamp seconds>.<sequence-within-the-same-second> tuple solves all issues, I think.
Robert(K) _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
