[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inclusion of a Status code within a TSAToken
Terry Hayes wrote:
For time-stamps ...
> The token itself should be the "this is a valid token" statement. It is a
> SignedData object, it has the proper content type OID, and is signed correctly
> by a valid TSA. There is no need for an additional status field in the token.
I think there are some cases were warnings might be issued,
without preventing the time-stamp to be granted.
Either these warnings go into free data, or somehow get
a code that fits into the status code.
I prefer a field to encode them.
For error responses ...
> In summary - we need message imprint and/or nonce along with the error code.
> That's it.
Exactly.
Best,
pp
-- --------------------------------------------------------
Prof. Jose A. Manas <jmanas@dit.upm.es>
Dpt. Telematica http://www.dit.upm.es/~pepe
E.T.S.I. Telecomunicacion tel: [+34] 91 336 73 25
Ciudad Universitaria gsm: [+34] 607 73 38 94
E-28040 Madrid, SPAIN fax: [+34] 91 336 73 33