"Changed:" field

Dear Colleagues,

I'd like to propose new behavior of the "Changed:" field of the database
objects.

It would be more convenient if database (or its front-end robot,
processing requests from mail messages) sets value of the "changed:"
field itself using "From:" field of the mail header/envelope. Database
could contain "changed:" information in three modes depending of user
needs:

1. Only one record, reflecting last change.
2. Two records, reflecting event of the creation of the object and "last
changed" event.
3. Full history of the changes. The first record means "created", and
next records reflect every change, sorted by date.

The mode of the "Changed:" field can be described in the "mntner" object
and is applied to all objects controlled by this mntner. The default
behavior of this field applied to objects without mntner. 

In all cases the field(s) "changed:" have form "Changed: <e-address>
<date>", as it is now, but <e-address> is retrieved from mail
header/envelope with appropriate authorization checks (it is being done
now), <date> is current date of the modification. There is no need to
store changes itselves, that is subsequent versions of the object are
not stored.

Best Regards,
--
Andrey Petukhov  (AP9-RIPE)    Phone: +7 095 705 9229
Systems Engineer               Fax:   +7 095 929 9363
Global One Russia (RoSprint)   Mailto:pooh at ipnms.rosprint.net