Re: TSTTime definition

[Peter Sylvester <Peter.Sylvester@xxxxxxxxxx>]

Good morning. Here it is still yesterday :-)

I fully agree with you. I do not see any benefit to code
anything else than just GeneralizedTime with all its
features. Anyway, I believe if something is missing in
that format the right way is to get that changed.  

Furthermore: Copying just the subseconds of the NTP stuff
and leaving GeneralizedTime may create problems with
leap seconds when you actually want to compare two dates.
(Not that I believe that this is going to happen).

If someone needs such kind of authenticated time, then
one should choose the complete format, and not mixture
of two pieces of different worlds.  

/P

> 
> Peter Sylvester <Peter.Sylvester@EdelWeb.fr> writes:
> 
> >TSTTime ::= SEQUENCE {
> >  genTime GeneralizedTime ,
> >  subsecond NumericString OPTIONAL
> >}
> >
> >GeneralizedTime is used with seconds or milliseconds.  Subsecond is a 
> >chain of decimal digits, the leftmost digit expresses 1/10th of a second, 
> >the second 1/100th.
> 
> OK, this time I will jump in first... given that GeneralizedTime *already
> includes* the subsecond facility in exactly the format described above, why
> is it necessary to add a second way to specify it?  Is there some secret
> annex to X.680 which says that you're not allowed to use GeneralizedTime to
> encode a generalised time which I'm missing?
> 
> Peter.
> 
>