Hi, All ! David Kessens answered this question, but on another mailing list. Here is his answer: --------- [preceeding text deleted]

It would be interesting to know why RIPE changed it from someone at RIPE who knows, assuming someone does :-)

It's usually best to ask the guilty party ... The reason is quite stupid: It was a bug. All specs (old and new ones) say that the withdrawn attribute should only contain the date. So when I discovered this, I switched back to the correct (and 1.xx) behavior. To be honest, I would prefer to get rid of the attribute all together. Hardly anybody is using it. David K. --------- Thank you, David, for explaining this. Regards, A. M. R. Magee ----------------------- RIPE NCC Database Group Gerald Winters <gerald@merit.edu> writes: * Hello All, * * Does someone from Ripe know the story on the "withdrawn" * attribute for route objects? The value in the v2 ripe * shows date plus email address whereas v1 had date only. * * 1. What is the rationale for the change? * * Thanks, * * --jerry * * * ------- Forwarded Message * * Date: Tue, 19 May 1998 10:02:57 +0930 * From: Mark Prior <mrp@connect.com.au> * To: cengiz@isi.edu * cc: Gerald Winters <gerald@merit.edu>, rps@isi.edu, merit-ie@merit.edu, * cengiz@cat.isi.edu * Subject: Re: RPSL phase ii software announcement * * Mark Prior on Tue, 19 May 1998 08:57:31 +0930 said: * > Onto something completely different, I notice that the withdrawn * > attribute under RIPE DB v1 was only a date, then RIPE DB v2 made it a * > date and email address and finally RPSL has changed it back to just a * > date again. What's the rationale for the changes? I'm just curious as * > I have to deal with all three formats now :-( * * * [snip...] * * It would be interesting to know why RIPE changed it from someone at * RIPE who knows, assuming someone does :-) * * Mark. * * ------- End of Forwarded Message * *