I would suggest that we want to use the same cut over time as is used by
X509 certificates -- that is 2015 rather than the end of this time zone.
-----Original Message-----
From: Blake Ramsdell [SMTP:BlakeR(_at_)deming(_dot_)com]
Sent: Wednesday, September 17, 1997 12:14 AM
To: 'Paul Hoffman / IMC'; 'ietf-smime(_at_)imc(_dot_)org'
Subject: Signing time format
On Tuesday, September 16, 1997 8:33 PM, Paul Hoffman / IMC
[SMTP:phoffman(_at_)imc(_dot_)org] wrote:
** signing time**
Currently, signing time in 2.5.1 says it must be UTCTime, which is
not Year
2000 compliant. (Can we all say "duh"?) The proposed solution is to
use the
same method that PKIX part 1 does for certificates. I propose that
the
wording in our draft be:
Sending agenst shall always encode signing time through the year
2049 as
UTCTime; signing times in 2050 or later shall be encoded as
GeneralizedTime.
We should also clarify when you should add 1900 to the year digits for
UTCTime, and at when you should add 2000.
The wording from PKIX part 1 for UTCTime (from section 4.1.2.5.1) is:
Conforming systems shall interpret the year field (YY) as follows:
Where YY is greater than or equal to 50, the year shall be interpreted
as 19YY; and
Where YY is less than 50, the year shall be interpreted as 20YY.
Blake
--
Blake C. Ramsdell
Worldtalk Corporation
For current info, check http://www.deming.com/users/blaker
Voice +1 425 882 8861 x103 Fax +1 425 882 8060