Changing rrdb objects in the future

At 02:46 PM 4/08/97 -0400, you wrote:
>At the last ripe meeting it was agreed to track object history
>including UTC time zone, although I'm not entirely clear what this
>means.  Presumebly it means that the changed field will be stamped
>automatically by the db software with utc time and the from
>line of the email.

That would certainly sort it out.

>  I think another holdup is the issue of the millenium approaching.  
>The current date format (ie, YYMMDD) will be insufficient for those
>future dates.  And so this problem must be fixed too.
>  I would think that YYYYMMDD is an obvious solution.

That will take care of the y2k problem, but won't help those of us in
unusual time zones... For that we would need something like YYYYMMDDHHMMZZZ
(ZZZ=time zone). This is a bit more of a mouthful, of course.

>The db software
>will be converted from ripe181 to rpsl over the coming 6 months.
>Maybe when the db's are officially changed to rpsl we can update
>the objects from YYMMDD --> YYYYMMDD format.
>
>ps  Yes, this is exactly the correct forum to bring this up.

Good :)


Joe
--
Joe Abley <jabley at clear.co.nz>                  CLEAR Communications Ltd
Systems Engineer, ISD                            http://www.clear.co.nz/