bortzmeyer at gitoyen
Jan 7, 2003, 1:26 AM
Post #9 of 9
On Monday 6 January 2003, at 23 h 53,
Re: automating peering filters / RPSL, etc.
[In reply to]
Arnold Nipper <arnold [at] nipper> wrote:
> I second Stephane that quality of DB data is very low. People simply forget
> to start garbage collection now and then. Thereby is it really simple to
> have an up-to-date routing db. Erase all routes and then dump your bgp
> config to the DB.
Another approach, that we use at Gitoyen, is to produce the aut-num object
automatically from the same database that holds your peering agreements. That
way, you can have an automatically up-to-date aut-num, an automatically
up-to-date list of peers on the Web site, etc.
A small ISP has few objects to maintain and therefore has no problem keeping
them up-to-date, even by hand.
A large ISP uses a database, anyway, either a toolchain built internally or a
packaged software like RoboBijal or Northern Star and therefore has no problem
keeping the objects up-to-date (it is easy to automate the updates to the
RIPE-NCC database, may be with EPP <URL:http://www.ietf.org/html.charters/provr
eg-charter.html>, it will be even simpler and synchronous).
So, I do not see why some ISP still pretend they have no time to maintain the
IRR, but the fact is many do not keep it up-to-date.
Tip of the day: a zsh (should work with all Bourne-like shells) function to
sign and send an update to the RIPE-NCC database. Next version will add the
changed: line automatically :-)
if [ "$1" = "" ]; then
echo "Usage: $0 file"
if [ ! -e $1 ]; then
echo "$1 does not exist"
gpg --clearsign --armor --output - --default-key gitoyen $1 | \
command mutt -s MODIFY \
-e 'set from=bortzmeyer [at] gitoyen; my_hdr X-NCC-Regid: fr.gitoyen' \
auto-dbm [at] ripe