<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <tt>Dear Janos As Job pointed out we can phase in such a change. So if it is decided to remove the "changed:" atribute, as well as communicating such a change by various means, we could adjust the software so that any object submitted for update containing a "changed:" attribute will have it stripped out by the software with a Warning message added to the ack response. This would prevent any update script from failing. If anyone has scripts that read the "changed:" values and expect to find them, these scripts would break anyway if the attribute is made optional and someone chooses to remove them from their data. Regards Denis Walker Business Analyst RIPE NCC Database Team </tt> <div class="moz-cite-prefix">On 17/04/2014 15:25, Janos Zsako wrote: </div> <blockquote cite="mid:534FD667.2050308@iszt.hu" type="cite">Dear all, <blockquote type="cite">Making changed: entirely optional, and possibly recommend against using it for new entries, that is something I would be fine with. </blockquote> I fully agree with Gert here. I am sure deleting the "changed:" attribute would break quite a few scripts. Best regards, Janos <blockquote type="cite">Gert Doering -- NetMaster </blockquote> </blockquote> </body> </html>