Marten,

Just some explanation, the messages sent to assign are first checked to see if they are already in the database, and currently bounced back to the NCC if they are. I think what I will do is create something like auto-assign, which has the same "on-the-fly" features as auto-dbm, but will only ADD new objects, and bounce all objects that are already present. This would mean that also contact people that are already present will not be updated when sent to auto-assign.

...does this mean that we are no longer able to submit *updates* for person objects along with a new network object from the 193,194 address range? If this is the case, then I think we should generally go for a system where *all* objects *with the exception of objects for newly assigned networks* should go to the ripe-dbm mailbox. Wilfried.