Feedback Requested: Routing Resilience Manifesto

David Hofstee david at
Thu Jul 3 07:30:07 UTC 2014

About #3... I had a little discussion on abuse-wg at RIPE a while ago about keeping records up to date and relevant. See below. 

Nobody at RIPE cares much at the moment (to actually pick up this subject). Maybe they need a push with a TerexRH400.

David Hofstee

Deliverability Management
MailPlus B.V. Netherlands (ESP)
Hi Frederik,

Who has an interest in a clean database? The sloppy Org or Ripe? The answer is Ripe, therefore it should also spend energy [via Ripe Ncc] in (making sure that Orgs are) keeping it clean.

Kids do not grow up themselves, it requires an active process. Organisations are not much different.


-----Oorspronkelijk bericht-----
Van: Fredrik Widell [mailto:fredrik at] 
Verzonden: vrijdag 15 maart 2013 10:37
Aan: MailPlus| David Hofstee
CC: anti-abuse-wg at
Onderwerp: RE: [anti-abuse-wg] Abuse Reporting Issues

On Fri, 15 Mar 2013, MailPlus| David Hofstee wrote:

Well, that is probably more a sign of a sloppy organisation, it is up to the LIR to keep the ripedb up to date, this is not the role of RIPE. You probably dont expect RIPE to keep track of your old DNS-entrys and give you a phone-call if it seems that a customer-name is wrong do you?

> Hi Frederik,
> I am such a person (DH3195-RIPE). I entered my email a long time ago. Unlike passwords that expire and accounts that get locked when not used, this vital contact info is never re-validated. We never get mail that says: "Ripe wants to confirm that you are still having Role X in your organisation. Click here to confirm.". A full-inbox bounce could trigger a phone call. Etc.  Ripe should charge money for not keeping records up to date.
> In my (ESP) world, an email address that has not been used by the list-owner for over a year is a risk for a spam trap ;-).
> Bye,
> David

-----Oorspronkelijk bericht-----
Van: NANOG [mailto:nanog-bounces at] Namens Andrei Robachevsky
Verzonden: Wednesday, July 2, 2014 4:24 PM
Onderwerp: Feedback Requested: Routing Resilience Manifesto


A small group of network operators has been working on defining a minimal, but feasible package of recommended measures that, if deployed on a wide scale, could result in visible improvements to the security and resilience of the global routing system.

Many operators are ahead of the curve and already implement much more than the proposed recommendations. But we believe that gathering support for these relatively small steps could pave the road to more significant actions on a global scale.

We called this set of recommendations a Routing Resilience Manifesto - you can find a draft document here:

This initial version of the Manifesto was drafted by a small group, but we need a wider community review, your feedback, and, ultimately, your support to make this initiative fly. It was already presented at several venues, like RIPE and NANOG, and now we open it for a more detailed review. Please note that this is very much a work in progress.

Please review the document and provide your feedback and text suggestions online or via routingmanifesto at by 31 August 2014.


Andrei Robachevsky
Internet Society

More information about the NANOG mailing list