-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I agree, there is in practice (at least for the moment, when everyone is trying to put a TSA together, more or less draft compliant), no reason for having such flags.
But, it is also not stupid.
Let's imagine that some day the TSP will be really used
by everyone. :) Hard to imagine, but let's try.
This will rise the problem of DOS attack, and some
people, (as I have done myself) will implement the TSA
and limit the number of parallel requests (and let's understand
by this the number of spawn processes, or threads) to a fix number. So
they will
just return an error back. This is actually not a nice thing
to do. And I presume, people there, writing the draft,
tried to be nice: well, if I get a request, but,
I don't have time to give a response right away, because
I am busy, let's store the request and tell the person to try
again sometimes later.
Perhaps there is also the possibility
that your clock is at that moment not available, (I would
like to believe that there will be TSA's out there that won't read
the time from the local system, like I do at the moment...) or maybe
some
other resource... how could I know?? :) In any case you have to take cautions about the overflooding with
requests (or even pending requests, that havn't been answered yet)
Well, at least this is the reason I can imagine. Perhaps there are also some other (dark!) reasons, but I would like to hear/read about them from the TSP gurus. :))
Kindly regards, Cristian