Re: automatic DB cleanup proposal
- Date: Tue, 9 Oct 2001 14:07:58 +0200 (CEST)
Somebody @ RIPE NCC, speaking for himself, not for RIPE NCC, writes:
> On 2001-10-08 20:02:38 +0200, Ulf Kieber wrote:
> >
> > The modification timestamp would be updated whenever the object is
> > updated or the link counter changes. The analogy in the UNIX file
> > system would be sort of a mix of ctime and mtime.
>
> <snip/>
>
> > expire: 1 849700000
>
> I suggest that this look more like the timestamp in the changed
> attribute:
>
> expire: 1 20011008
>
> Human-readable == good. :)
Seconded. Daily granularity is good enough, but way more readable.
Make is so.
> Perhaps this attribute should also be present on maintainer and irt
> objects, since they contain contact information as well? Not
> necessarily as important, but possible.
Then we could put it onto key-cert as well. I'm sort of reluctent
to have it placed onto maintainer objects which can not be recreated
without interaction with the NCC. I'd at least ask for an extended
expiration period.
--
Ulf Kieber email: kieber@localhost
Senior Network Engineer voice: +49-69-299896-21
Global Access Telecommunications, Inc. fax : +49-69-299896-40
internet solutions for business www : www.gatel.net
