[db-wg] Proposed change 2003.1: notification for more-specific

> 
> Change:
> 
> When the creation of an object requires authorisation by a
> less-specific object, normal mntner notification will apply; "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.  
> 

  My comment is not specifically related to this proposal, but
I have long been concerned about the optional status of the
mnt-nfy: attribute.  This means if someone cracks a mntner password
and begins submitting updates (which naturally will be successful
since they have the password), no notification will be sent
to the mntner.

   I'm not sure of the best way to handle this.
I suppose there are some people who don't want to be bothered
by notification of successful updates and if they're using
PGP that might be okay.  It also seems the upd-to attribute name was
very poorly chosen as it is difficult to differentiate it's
function from that of mnt-nfy (I often get the two confused
and I deal with this stuff every day).   I personally feel
that the mnt-nfy should be mandated in RPSL
and those mntner's who do not have one should have
it replicated from their upd-to attribute value.  For
those who really don't care to see the results of successful
updates, they could simply direct the email address to
/dev/null.

 -Larry Blunk
  Merit