[13688] in North American Network Operators' Group
Re: Announcing new route (What besides BGP?)
daemon@ATHENA.MIT.EDU (Mike Leber)
Fri Nov 14 03:34:34 1997
Date: Fri, 14 Nov 1997 00:28:23 -0800 (PST)
From: Mike Leber <mleber@he.net>
Reply-To: Mike Leber <mleber@he.net>
To: Gerald Winters <gerald@merit.edu>
cc: Kevin Oberman <oberman@es.net>,
Bradley Reynolds <brad@b63695.student.cwru.edu>,
"Forrest W. Christian" <forrestc@iMach.com>, nanog@merit.edu
In-Reply-To: <199711121840.NAA23269@merit.edu>
On Wed, 12 Nov 1997, Gerald Winters wrote:
> I do agree with you that it would be nice to implement a system
> that would allow the registry administator some power to take
> corrective action to remove/update obsolete/incorrect db objects.
> I really believe that if the user community really wants to
> do something about obsolete information (and I do believe this
> is true) then the registries need to have limited power to fix the
> situation. The question is what should the power be and under what
> situation?
A nondestructive and possibly sufficient mechanism would be to send PAIR
errors/warnings to the appropriate maintainers monthly by email. People
with clean RADB entries wouldn't be sent anything. This would be a good
periodic reminder for engineering groups that have it in the back of their
mind to clean up their RADB entries but never get around to it unless a
peer or customer opens a trouble ticket.
Heck, the warnings could even have the appropriate RADB object (or mail
command) preformatted and ready to email. This way the maintainer has
final control.
Mike.
+------------------- H U R R I C A N E - E L E C T R I C -------------------+
| Mike Leber Direct Internet Connections Voice 408 282 1540 |
| Hurricane Electric Web Hosting & Co-location Fax 408 971 3340 |
| mleber@he.net http://www.he.net |
+---------------------------------------------------------------------------+
