Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Lazy Engineers and Viable Excuses

  • From: Mark Borchers
  • Date: Tue Aug 26 12:01:49 2003

During my tenure at a medium-sized ISP, I found that one of the
more painful experiences was trying to assist small or first-time
BGP customers in setting themselves up in the IRR and registering
their routes.  While I would take issue with some posters' comments
that maintaining edge filters does not scale, I would certainly
support the statement that providing IRR 101 tutorials definitely
doesn't scale.

For smaller sites, I feel that explicit permit prefix filters 
are the way to go.  At the same time a filter is updated, if
the customer was assigned space from one of our blocks, off go
both a SWIP and a proxy IRR object.  If the space is PA space
from another provider, we'd submit a route object after verifying
the assignment.  In the case of PI space, we *might* take the
trouble to give the IRR 101 training if the customer seemed
trainable.

Somewhere in the growth curve along which a customer increases in
both size and credibility, I think there is a case for migrating
them from prefix filtering to as-path filtering with a prefix limit.
While not preventing any possibility of an illegitimate announcement,
it does prevent a 7007 type incident along with scalability.







Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.