This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Whois changes
- Previous message (by thread): [db-wg] Whois changes
- Next message (by thread): [db-wg] Whois changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rimas Janusauskas
Rimas.Janusauskas at sc.vu.lt
Wed May 11 17:56:33 CEST 2005
On Wed, 11 May 2005, Shane Kerr wrote: > Date: Wed, 11 May 2005 13:50:36 +0200 > From: Shane Kerr <shane at ripe.net> > To: Mark Prior <mrp at mrp.net> > Cc: Rimas Janusauskas <Rimas.Janusauskas at sc.vu.lt>, db-wg at ripe.net > Subject: Re: [db-wg] Whois changes > > Mark Prior wrote: > > > Rimas Janusauskas wrote: > > > >> IMHO preferable solution is to modify "changed:" attribute format: > >> changed: <e-mail address> > >> with automatically generated timestamp. > > > > > > The software, at least IRRd, does this. I never add timestamps. I also > > use nobody at aarnet.edu.au as the email address to avoid SPAM reports > > sent to the poor DB updater. > > > The RIPE Whois software also works like this. > > changed: shane at ripe.net > > Will become: > > changed: shane at ripe.net 20050511 > > If added today. If... The key idea of my suggestion was do not allow "pour updater" ((C)Mark Prior :) set timestamps or ignore them (your previous message proves) Shane> A user can put almost any "changed:" value that they want. I could Shane> update my person object today to have this value: Shane> Shane> changed: ripe-dbm at ripe.net 19901215 Best regards, Rimas Janusauskas
- Previous message (by thread): [db-wg] Whois changes
- Next message (by thread): [db-wg] Whois changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]