I think that with local peering on the increase throughout New Zealand a
RADB or similar would be extremly useful.
At NZIX for instance we should all be running BGP, with filters to prevent
unauthorised advertisments arriving from someone elses router. While a RADB
would only be as good as the information it held and how well you could
trust someone to enter data into it. It would still be better than what we
have at the moment (almost nothing).
I think almost everybody has had to change a metric at Waikato because
someone has accidently advertised the wrong Network. I know I did it when
we multi-homed a netlink customer several years ago. And I know it has
happened to me serveral times. I actually remember a 4am 6 way conversation
with Sandy yourself, KC and Iprolink trying to work out a OSPF routing error
that turned out to be a Cisco bug, which was only preventable by adding a
access-list.
We don't have to invest in a server or nominate someone to maintain one, we
could all use the merit radb today.
The issue arrises (as you have mentioned) when we register "our" IP
Addresses against our AS. Most ISPs still have legacy IP space which
"belongs" to the larger /16, /15 etc that netway currently advertise, this
usually comes from companies which don't want to change.
I would like to have the addresses which these organisations have been
allocated by Apnic (nznic at the time), routed with our AS number. And as
such stored in a database with my AS so that other local bodies that I peer
with may use this information to build reliable filter-lists.
This would be advantageous to a company like ICONZ, where by if a major
international outage occured (heaven forbid :), with our supplier then we
would be able to come to some arrangement with another ISP that we peer with
to use their international capacity albeit at a decreased performance level,
this could be acheived simply by changing some routing filters, assuming
that all the appropriate entries were in the RADB(s).
Education is required to ensure that people don't think that they own a
certain IP address range indefinitely. As the internet requires the
addresses to be aggregated organisations need to know this, and understand
why. I think that this has been shown by the recent campaign to bring the
190.xx (or what ever it was) range back into some real size perspective.
-Rowan
-----Original Message-----
From: Arron Scott <arrons(a)netgate.net.nz>
To: nznog(a)list.waikato.ac.nz <nznog(a)list.waikato.ac.nz>
Date: Tuesday, 2 June 1998 17:58
Subject: Re: Route Policy Database/Filters
>Hi all,
>
>I would be interested to know what scenarios people have for using such a
>database. NetGate currently has a fairly complex routing table, and yet our
>boundary routing inside New Zealand still remains fairly simple.
>
>I am also slightly concerned that having these entries in a database would
>infer some "right of ownership" for certain address space, which would do
>the concept of hierarchical routing a server disservice. From my
>experience, any time someone enters a new entry in the RADB, even if it is
>a "black hole" from someone elses CIDR block they feel it gives them a
>right to use that given address space indefinately. We may also have to
>consider asking for the right to administer sub-delegations of our APNIC
>registered addresses ourselves.
>
>I am not against a router server, I am however keen to ensure it offers
>tangible benefits to the users, and improves things for the Internet
>society at large.
>
>Arron Scott
>Telecom NZ
>
>At 05:03 PM 2/06/98 +1200, John Houlker wrote:
>>I understand a number of ISPs in NZ would be interested in using a route
>>policy database to allow communication of this information and, in
>>particular, to enable automated maintenance of filters to control route
>>policies. Recently we have had a Computer Science student run an informal
>>survey of some ISPs on this issue and again there was an interested
>>response from most; he has also been revisiting the situation in respect
to
>>running a database using the "Route Arbiter" code. I didn't get to the
>>NZNOG meeting (perhaps this was discussed there), but could "NZNOG"
>>consider this question and perhaps encourage the application of such
>>coordinated controls on route information?
>>
>>In principle I believe the IRR could be used for such a purpose, and it
may
>>be good practise to load AS/route object information in there in any case
>>(it is especially important for multi-homed networks), but maybe there
>>should be a NZ based service for NZ information.
>>
>>Thoughts?
>>
>>John
>>
>>
>>---------
>>To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
>>where the body of your message reads:
>>unsubscribe nznog
>>
>>
>_________________________________________________________________________
>Arron Scott Phone: ++64-9-3569687
>Service Specialist Fax: ++64-9-3794790
>Service Implementation & Management Group Cell: ++64-25-883163
>Telecom NZ Ltd eMail: arrons(a)netgate.net.nz
>---------
>To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
>where the body of your message reads:
>unsubscribe nznog
>
---------
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog