[db-wg] Announcement on parent notifications

[Denis Walker <]

Colleagues,

Notification on more-specific object creation authorisation
-----------------------------------------------------------

The latest dbupdate binary to be put into production has implemented the change
regarding parent notifications that was proposed to the Database Working Group
in March 2003. This will cause some users to receive additional notifications. 
A summary of the change is outlined below.

When the creation of an object requires authorisation by a less-specific 
object, normal notification rules apply to the mntner(s) in the less-specific 
object. In other words, "upd-to:" is notified of failure, and "mnt-nfy:" is 
notified of  success.  Where there are multiple maintainers, only one is 
needed to successfully authorise the creation, but all the maintainers in the 
list will be notified.  

For example:

inetnum:    192.168.0.0 - 192.168.255.255
   .
   .
   .
mnt-by:     EXAMPLE-MNT
mnt-lower:  ANOTHER-MNT
mnt-lower:  YET-ANOTHER-MNT

If the successful creation of the more specific inetnum:

inetnum:    192.168.201.0 - 192.168.201.255
   .
   .
   .
mnt-by:     SOME-MNT

Is authorised by YET-ANOTHER-MNT in the less specific inetnum, notifications 
will be sent to the "mnt-nfy:" listed in both ANOTHER-MNT and YET-ANOTHER-MNT
in addition to the "mnt-nfy:" listed in SOME-MNT.

In the case of route creation, the parent may be a route or an inetnum, and 
it may also be an exact match. Also notifications will also be sent to the 
mntner(s) listed in the origin aut-num of the route object being created. 

The original proposal can be found here:

http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00034.html


Regards

Denis Walker
Database Engineer
RIPE NCC