July 2004 - Ris-int - mailman.ripe.net

bgpd dies
by James Aldridge 31 Aug '04

31 Aug '04

http://bugzilla.quagga.net/show_bug.cgi?id=103 We seem to be seeing this bug too. Don't know whether it's a Linux thing or a Quagga version 0.96.5 thing... worth keeping an eye on the quagga-users and quagga-dev lists. James

2 2

new features
by Alexis Yushin 05 Aug '04

05 Aug '04

Hi, I finished xml.html please try it out, the templates are now provided in the form. I also have an experimental version of retromatch but it still needs some premission granting action from Arife. Everything else that was on the wish-list is finished, plus some extra's like myasn-admin delete to delete an entire registry and deleting all alarms in a group. I'm pretty much done. Since the project is finished, as far as my contract is concerned, I'd like to invite everybody to have a Columbus beer with me at 't IJ brewery. Suggestions for a specific date? Alexis

4 12

myASn admin doc draft
by Alexis Yushin 02 Aug '04

02 Aug '04

Hi, This is a draft of the admin doc. Any comments/suggestions/critique or unrelated remarks are welcome :) Alexis 1. Overview This overview implies that the reader has familirized her/himself with the myASn user documentation and frequently asked questions. http://www.ris.ripe.net/myasn/help.html http://www.ris.ripe.net/myasn/faq.html myASn system internally consists basically of three parts: - frontend (web interface presently running on halfweg.ripe.net ) - backend (two perl demon scripts running on weesp.ripe.net ) - database (presently resided on weesp.ripe.net) Frontend consist of collection of Mason enabled web pages and help files that use perl libraries to access myASn database to configure the system and view the results of the processing done by backend. There are two versions of frontend: standalone and LIR Portal. The LIR Portal version of the frontend is not deployed at this moment and will be documented elsewhere. Everything below applies to the standalone version. Backend consist of two perl demon scripts: myasn-scan - that does the processing of the data and generates alarms that are stored in the myasn database myasn-send - that send the email notifications of the alarms that are generated by myasn-scan Both frontend and backend use the same set of perl modules. 2. myASn Installation pre-required modules: Alzabo::MethodMaker Alzabo::Runtime::Schema Apache::DBI DBI Exception::Class IO::Socket Lingua::EN::Inflect Mail::RFC822::Address Net::IP Socket Text::ASCIITable URI XML::Parser myASn installation on both frontend and backend servers should be as simple as checking the myASn package out of master CVS repository. export CVS_RSH=ssh export CVSROOT :ext:cow.ripe.net:/ncc/cvsroot cvs co myasn Further updates of myasn system can be simply done by issuing cvs up in the myasn directory. (use cvs -n up first, to see what's about to happen :) myASn system should be installed on both frontend and backend server into /home/risops/myasn directory. This directory is hard-coded into use lib statements of the following files in the distribution: ./backend/myasn-scan.perl ./backend/myasn-send.perl ./lib/RIPE/NCC/myASn.pm ./www/syshandler as long as it might be specified in myasn.conf configuration file. Once myasn check out the following symbolic links should be made on frontend server (halfweg.ripe.net) ln -s /home/risops/myasn/www /home/risops/www/ris/myasn ln -s /home/risops/myasn/alzabo/schemas/myasn /var/www/alzabo/schemas/myasn XXX Arife might want to add here comments about ris.rc file she made. 3. Configuring myASn Once myASn is installed the configuration of myasn is done via master configuration file, /home/risops/myasn/etc/myasn.conf It basically consists of line with name = value, where in most cases name is the same as a command line arguement of myasn scripts without leading dashes. For example, one could put risdb-username = myasn which would be similar to issuing myasn-scan --risdb-username myasn There are a number of variables that are common to all myASn components, example values are given: risdb_hostname = 193.0.0.210 Hostname or ip address of the RIS database. risdb_username = myasn Username to use for connecting to RIS database. risdb_password = ticvdkjw Password to go with the username above. myasn_database = myasn Hostname or ip address of the myASn database. myasn_hostname = 193.0.0.210 myasn_username = myasn Username to use for connecting to myASn database. myasn_password = tiablkdfd;akj The password to use to connect to myASn datbase. myasn_port = 3306 Port to use to connect to myASn database. pidfile_dir = /home/risops/myasn/log The directory where all the pid/lockfiles will be created. Must be writable to myasn-scan and myasn-send invoking users. The pid files will be created in the format of: $pidfile_dir/myasn-scan.$rrc.pid $pidfile_dir/myasn-send.pid This option can be overwritten with pidfile option that doesnt do rrc name expansion like shown above. The same rules apply to logfile_dir and logfile variables. logfile_dir = /home/risops/myasn/log The directory where all the logfiles will be stored. Same requirement as above. rrc_list = rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 White-space separated list of the route collectors. Once a new RRC is added it should be added here as well and myasn related tables should be created. XXX Arife more on this? # wait these many seconds for myasn-send loop wait = 900 This one is myasn-send specific. myasn-send will wait this many seconds before starting sending a new serious of alarm notifications by email. # wait these many seconds for myasn-scan loop loop-wait = 300 This is a similar variable for myasn-scan. myasn-scan will wait this many seconds before processing new series of bgp updates. # delay this many seconds before forking next child fork-delay = 30 myasn-scan will wait this many seconds before forking another child process. This is done to desyncronize processing of rrc to avoid peak mysql workloads. To configure the frontend, the Apache's httpd.conf needs the following lines added: <Location /myasn> AuthType Basic AuthName "MyASN Login" AuthUserFile /home/risops/myasn/etc/myasn-passwords Require valid-user SetHandler perl-script PerlHandler HTML::Mason::ApacheHandler PerlSetVar MasonAllowGlobals $User PerlSetVar MasonAutohandlerName autohandler.html </Location> The first section is responsible for authenticating users, and the second one makes sure that the myASn files are handled by Mason. 4. Accounts and users myASn account in standalone version is the same thing as LIR registry in the original LIR portal version. myASn account might have a number of users that share the same alarm configuration and have access to the same information. As a matter of fact myASn doesn't know anything about users, it only cares about the accounts or registries. Usernames are used solely for access authorization purposes and welcome text. As far as user accounts are concerned they are created automatically based on the $User->username and $User->regid global variables. These variables are either initialized by LIR Portal (for LIR Portal version) or by syshandler in the standalone version. In standalone version $User->username and $User->regid are produced by splitting Apache username into username@regid parts. Therefore Apache username alexis@55555 will result in $User->username = 'alexis' and $User->regid = '55555' If myasn account 55555 does not exist yet, it will be created automatically. Therefore to create a new myasn account a new user should be added into /home/risops/myasn/etc/myasn-passwords file. It can be done with htpasswd /home/risops/myasn/etc/myasn-passwords username@accountname password, for example: htpasswd /home/risops/myasn/etc/myasn-passwords alexis@55555 alexis123 will create an account 55555 with username alexis that will have password 123 To change user password the same command as above should be used. XXX - User management, put e-mail template of user request XXX I'm not sure what kind of template I must provide?!? 5. Logging myASn logfiles go into the location specified by --logfile or --logfile-dir options specified either in myasn.conf configuration file or at command line. When myasn-scan is invoked with --logfile-dir, logfile name expansion is being made in a form of: $logfile_dir/myasn-scan.$rrc.log So ig logfile_dir is /home/risops/myasn/log, then for every rrc there will be a separate logfile created. For example for rrc05: /home/risops/myasn/log/myasn-scan.rrc05.log The same applies to --pidfile and --pidfile-dir directives. 6. Backend demon's invokation As mentioned above, two myasn demons are running on weesp.ripe.net (or whatever backend server is in use): myasn-scan myasn-send myasn-scan needs to know to which databases to connect and which credentials to use, location of its logfile and pidfile directory, and loop-wait, fork-delay. All of which is normally specified in myasn.conf file. The only command line myasn-scan should require if myasn.conf is properly setup is: myasn-scan.perl --fork --loop This command tells that myasn-scan should loop, that is keep on waiting on an processing incoming data, and that it should fork a separate process for every rrc. It is important that fork-delay variable is configured, so that not all the processes will be accessing the database exactly at the same time, but with some offset. myasn-send will fork by default so it doesn't require any command line. 7. Maintenance XXX To be developed

2 1

RE: RIS Info Page
by Matthew Williams 29 Jul '04

29 Jul '04

This looks fine. Please link the rrc12 news flash to http://www.ripe.net/ris/risintro.html (page edited) Cheers, Matthew > -----Original Message----- > From: Adrian Bedford [mailto:adrian@ripe.net] > Sent: 29 July 2004 14:56 > To: Matthew Williams > Cc: webmaster(a)ripe.net > Subject: RIS Info Page > > > Hey Matthew > > Sorry for not getting back sooner. I'm really snowed under > right now again. > > The RIS Page text will be used on the new website, which is > supposed to be > launching at the end of August, but in the meantime, if you > want to use the > text we talked about, I've taken on board your comments and > this is the > definitive text...can you create/edit the page you talked > about. When the > new site goes live, we will be able to easily edit it anyway > and save you > the hassle.... > > > > The Routing Information Service (RIS) started as a RIPE NCC > project in > 1999. Currently there are over 300 IPv4 and IPv6 peers at 12* data > collection points in Europe, Japan and North America > > The project aims to collect and store Border Gateway Protocol > (BGP) routing > information and make it publicly available for the Internet > community. > Network operators troubleshoot routing problems by looking at data > collected over time without being limited to a single BGP > view. Archived > raw RIS data is also available, which can be used for > research purposes. > > You can support the RIS by providing a BGP feed. You can find > a list of RIS > peering locations at: > http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Peering requests can be sent to <rispeering(a)ripe.net> or through a web form, you can find at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi * RRC09 was decommissioned in May, 2004

1 0

RIS contact addresess
by Arife Vural 29 Jul '04

29 Jul '04

Hi guys, What about changing RIS contact info from The contact persons for RIS Project are: * Arife Vural <arife(a)ripe.net> * Daniel Karrenberg <dfk(a)ripe.net> * Henk Uijterwaal <henk(a)ripe.net> * James Aldridge <james(a)ripe.net> * Matthew Williams <matthew(a)ripe.net> To mail the whole group, please use ris(a)ripe.net. to something like that: Contact address for RIS Project: Peering: rispeering(a)ripe.net Questions/feedback/comments: ris(a)ripe.net Arife

2 1

myASN handover meeting
by Arife Vural 29 Jul '04

29 Jul '04

Hi all, This is the summary of our meeting today: - Alexis will prepare the system maintenance documentation. This doc will include the following items, - User management, put e-mail template of user request - How to installation of myASN - Adding new RRC - Log files - Deamons that are running Alexis will get back to Ziya and Arife today about timeline, after his talk with Henk and Matthew. - Developers documentation will be written by Alexis and Ziya. It's a half-day work. This will be scheduled after system maintenance doc is ready. - Arife will look at the myASN SQLs, all in myasn-scan code. Beyond those issues, today Alexis gave Ziya and me introduction to myASN code, and also we created the master copy of the source and put into CVS. Arife

2 1

Re: FW: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay)
by James Aldridge 29 Jul '04

29 Jul '04

"Matthew Williams" wrote: > Hi James, > > > - Recent RRCs have been specified as: > > > > Dell PowerEdge 1750 (1U server) > > 1 GByte RAM > > 3 x 73 GByte Disk (configured as RAID5) > > 2.4 GHz Xeon CPU > > Please send me a spec from Dell's web site that's intelligible for MSK-IX fol k (should also give us an estimate on price excl BTW). Below. I'm not sure this is any more intelligible though ;-) James ---------- cut here ---------- ------------------------------------------------------------------------------- Dell Computer Corporation Limited - De Dell Store Samenvatting van het mandje gedownload op 7/29/2004 ------------------------------------------------------------------------------- De prijzen zijn alleen geldig tot en met het einde van de werkdag op de dag dat de samenvatting van het mandje was gedownload. ------------------------------------------------------------------------------- =============================================================================== Dell raadt Microsoft^® Windows^® XP Professional aan =============================================================================== -* PowerEdge? 1750 August Promotion *- ====================================== Aantal : 1 Totaal excl. : 2319.00 EUR Totaal incl. : 2759.61 EUR Standard Features ================= Serverworks Grand Champion LE chipset with 2:1 memory interleaving and a five peer PCI bus architecture for excellent I/O throughput Up to two Intel® Xeon Processors with NetBurst Micro-architecture with Hyper-Threading support. Up to 8GB ECC DDR SDRAM for expandable performance. Chipkill support Online Spare Row capabilities provide improved memory availability. Optional activation of PERC 4/di embedded dual channel Ultra 320 RAID controller with 128MB of battery backed cache to protect your data. Hot-plug hard drives, optional hot-plug redundant power supplies and hot plug non-redundant fans for high availability. Support for 3 hard drives, giving 438GB maximum internal data storage. Embedded dual channel Ultra320 SCSI controllers Tool-less chassis and cable-less motherboard design for ease of maintenance & upgrade Dual embedded Copper Gigabit NIC Rapid rack rail design for fast deployment in a rack. The Dell OpenManage suite to enable automated/rapid operating system installation, and complete network management with IT Assistant. Special Promotion ================= Promotion : 300- special promotional discount Premier Enterprise Support ========================== 3 Years Bronze On-Site Service with Next Business Day Response (-EUR - 700.00 EUR) Packaged Installation Services ============================== No installation Chassis ======= 3rd Party Rack Rails Kit (+ EUR 20.00 EUR) Processor ========= Single Intel® Xeon processor 2.4GHz with 512K cache, 533MHz Front Side Bus Memory - Special Promotion ========================== 1GB DDR SDRAM (2x512MB 266MHz DIMMs) - including promotional saving Hot-Plug Power Supplies ======================= One Non-Redundant Power Supply Riser ===== Riser 2X64-Bit/133MHz PCIX included Bezel ===== PE1750 Bezel Assembly Monitor ======= Not Included Storage Device and Recordable Media =================================== 24x Max IDE CD-ROM Keyboard ======== Not Included Mouse ===== Not Included 1st Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 100.00 EUR) 2nd Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 290.00 EUR) 3rd Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 290.00 EUR) 1st RAID or SCSI Controller Card ================================ PERC 4/Di embedded RAID (with 128MB of battery backed Cache). 2 channels (1 internal and 1 external) (+ EUR 220.00 EUR) 2nd RAID or SCSI Controller Card ================================ Not Included Internal Hard Drive RAID Configuration ====================================== RAID 5 - hard drives connected to PERC4/Di RAID controller (requires 3 identical drives) (+ EUR 50.00 EUR) External PowerVault Tape Backup enclosures ========================================== Not Included Tape BackUp Software ==================== None 2nd Network Card ================ Not Included Communications ============== Not Included Network PowerConnect Switch =========================== Not Included Uninterruptible Power Supplies (UPS) ==================================== Not Included OpenManage Subscription Service =============================== No OpenManage Subscription Factory Installed Operating System ================================== Not Included System Documentation ==================== Paper documents not included (electronic version on Dell OpenManage CD) Software & Storage Support ========================== No Software & Storage support included ------------------------------------------------------------------------------- System ====== Prijs excl. : 2319.00 EUR BTW tarief : 19% Prijs incl. : 2759.61 EUR Levering ======== Prijs excl. : 82.00 EUR BTW tarief : 19% Prijs incl. : 97.58 EUR =============================================================== Totaal excl. : 2401.00 EUR Totaal incl. : 2857.19 EUR Prijs exclusief B.T.W. : 2401.00 EUR Prijs inclusief B.T.W. : 2857.19 EUR =============================================================== Inhoud uitsluitend ontworpen en juist voor Nederland klanten en gebruikers. De voorwaarden van Dell zijn van toepassing. Alle systeemprijzen en -specificaties kunnen zonder voorafgaande vermelding worden gewijzigd. Afgebeelde foto's van producten kunnen afwijken van de op deze webpagina genoemde specificaties. Systemen getoond met optionele extra's. WEERGEGEVEN PRIJZEN BEVATTEN NIET DE CORRECTE LOKALE BTW, VRACHTKOSTEN, IMPORTHEFFINGEN EN BELASTINGEN VOOR LUXEMBURG en worden opnieuw bevestigd nadat uw internet order is ontvangen. Language : nl Currency : eur Store : nlpad

1 0

FYI: RISwhois usage statistics
by Rene Wilhelm 28 Jul '04

28 Jul '04

RISwhois was announced early december 2003 and presented in the january 2004 RIPE47 meeting. After that we didn't do any marketing (other than provide pointers on ris webpages) I just had a rough look at the access statistics (as logged to /var/log/local.log and archived in /var/log/ARCHIVE/local.log*.gz) and found it nice to see there's continued intereset for RISwhois from external users. Excluding any of the RIPE NCC and RIPE meeting addresses (193.0.[0-9].*) RISwhois had 2,325,338 connections[*] from 815 distinct hosts. Top 10 users: IP #connections 213.19.146.13 932354 145.89.193.200 478159 128.223.6.40 363763 207.172.7.46 345502 213.186.35.102 58583 212.126.218.123 45000 202.12.29.252 37448 210.25.133.26 21005 146.115.9.21 15348 212.126.218.122 14242 halfweg.ripe.net made 16150 connections, which I take should all be attributed to the CGI web interface on www.ris.ripe.net So although started from a perspective of improving TTM's IP<>AS mapping, it seems we did add something useful/interesting to the RIS service portfolio. -- Rene [*] like whois.ripe.net, riswhoisd can keep a connection open on user request, thus #connections is not necessarily equal to #queries answered.

2 1

Three things...
by Matthew Williams 28 Jul '04

28 Jul '04

Hi Dave, 1. Flashing RIS (~we need peers etc etc) in K-anycast peering ack (SED do RIS peering reqs) 2. myASn accounts (also by SED in the future) sync w/ K-anycast peering requests (monitor no-export compliance) 3. When will you announce me to contacts ? ;) Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

2 4

[arife@ripe.net: [ris-int] myASN handover meeting]
by Arife Vural 28 Jul '04

28 Jul '04

Alexis, Could you also add which modules are required for myASN in system maintenance doc? Just remembered. Arife ----- Forwarded message from Arife Vural <arife(a)ripe.net> ----- From: Arife Vural <arife(a)ripe.net> To: Matthew Williams <matthew(a)ripe.net>, Ziya Suzen <ziya(a)ripe.net>, Alexis Yushin <alexis(a)ripe.net> Subject: [ris-int] myASN handover meeting Date: Wed, 28 Jul 2004 17:06:31 +0200 Cc: ris-int(a)ripe.net Hi all, This is the summary of our meeting today: - Alexis will prepare the system maintenance documentation. This doc will include the following items, - User management, put e-mail template of user request - How to installation of myASN - Adding new RRC - Log files - Deamons that are running Alexis will get back to Ziya and Arife today about timeline, after his talk with Henk and Matthew. - Developers documentation will be written by Alexis and Ziya. It's a half-day work. This will be scheduled after system maintenance doc is ready. - Arife will look at the myASN SQLs, all in myasn-scan code. Beyond those issues, today Alexis gave Ziya and me introduction to myASN code, and also we created the master copy of the source and put into CVS. Arife ----- End forwarded message -----

2 3

FW: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay)
by Matthew Williams 28 Jul '04

28 Jul '04

Hi James, > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU Please send me a spec from Dell's web site that's intelligible for MSK-IX folk (should also give us an estimate on price excl BTW). Cheers Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of James Aldridge > Sent: 28 July 2004 16:21 > To: ris-int(a)ripe.net > Subject: [ris-int] Draft minutes from Monday's RIS meeting > (apologies for the delay) > > > RIS Meeting - 26 July 2004 > > Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco > > Scribe: James > > Agenda: > - RRC Status > - RRC Moves/New RRCs > - myASn > - AOB > > RRC Status > > Q. Are there any existing tools to monitor BGP sessions? > A. Not that are directly relevent to the RIS. The current tools > compare BGP sessions against the registered peering > policy (the > AS3333 aut-num object). > > What to monitor? > - percentage of peers up/down? > - peer down for a "long time"? > > Should there be automatic or manual notification of peers when a > session is down? > > Who to contact at peers? > - We mostly use the IRR (RIPE, etc. databases) > - encourage peers to keep their own information up to date > - Current "addpeer" script records contact information > in a log file > - need to keep our own information up to date > - useful for historical data (e.g. who was the > responsible person at > the peer when the peering was first established, etc.) > > Action: monitor peering sessions in Nagios (OPS) > > peering sessions which are neither up nor > administratively > disabled should generate alerts. > > Action: document procedure for handling peering > sessions which are > down. (SED) > > 1. Nagios notifies SED, SED contacts peer > 2. After two weeks (?), session is > administrively disabled > ("neighbor ... shutdown"), (peer is contacted?) > 3. After a peering session is down for a > further period with no > response from the peer then the peering is > removed from the > RRC ("no neighbor ...") > > > RRC Moves/New RRCs > > * RRC08 (MAE West) has very few peers and more networks > are pulling out > of MAE West. We need to investigate alternative > locations for a route > collector on the US West Coast > > - PAIX > - Seattle > - LAIIX (Telehouse) > - ... > > Action: compare member lists of each West Coast exchange point > (Matthew) > > How to move RRC? Simply get MCI to ship box to new > location (or wait > for NCC staff to be in the vicinity of San Jose). > > * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new > peerings. > > Action: Contact George Michaelson (APNIC). Henk and > Shane will be at > IETF and can meet up with him there. > > * RRC13 (new RRC in Moscow) > > - Matthew has been in touch with RIPN (Russian > Institute for Public > Networks). > > - To simplify customs issues, it may be better for the host > organisation to order machine to our specification (see below) > directly from Dell in Russia. We would want to see > the quote before > agreeing to the purchase. > > - We need to know the IP configuration for the box so > we can configure > and ship the installation CD once the box is ordered. > > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU > > myASn > > Meeting with Alexis last week didn't happen (Alexis out > of town?) > > Action: contact Alexis to set up meeting (Arife) > > Matthew's slide "On the road to myASn v.1": > - Automate account creation > - bring together AS3333/K-Root/RIS peering setup and > myASn account > creation > - For each peering confirmation, the peer should be > made aware of > the other RIPE NCC peering opportunities, etc. > where appropriate. > > Action: Check with Dave Knight what, if anything, > is mentioned > about other NCC services when K-Root peering is > established (Bruce) > > - Would be easier if all NCC peerings were handled by the same > group. > - K-Root peerings are more restrictive than RIS peerings. > > AOB > > RIPE49 (Manchester) > > RIS Update presentation > myASn Tutorial > > Action: Speak to Shane and get back to Matthew > et al. (Arife) > [Shane had already left the meeting at > this point] > > Inventory > > Ruud asks for Dell Service Tags for each RRC to > add to the > inventory. > > Ops Interaction > > Reminder to use <ops(a)ripe.net> as first point of contact > instead of sending email to Bruce/James directly. >

1 0

Draft minutes from Monday's RIS meeting (apologies for the delay)
by James Aldridge 28 Jul '04

28 Jul '04

RIS Meeting - 26 July 2004 Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco Scribe: James Agenda: - RRC Status - RRC Moves/New RRCs - myASn - AOB RRC Status Q. Are there any existing tools to monitor BGP sessions? A. Not that are directly relevent to the RIS. The current tools compare BGP sessions against the registered peering policy (the AS3333 aut-num object). What to monitor? - percentage of peers up/down? - peer down for a "long time"? Should there be automatic or manual notification of peers when a session is down? Who to contact at peers? - We mostly use the IRR (RIPE, etc. databases) - encourage peers to keep their own information up to date - Current "addpeer" script records contact information in a log file - need to keep our own information up to date - useful for historical data (e.g. who was the responsible person at the peer when the peering was first established, etc.) Action: monitor peering sessions in Nagios (OPS) peering sessions which are neither up nor administratively disabled should generate alerts. Action: document procedure for handling peering sessions which are down. (SED) 1. Nagios notifies SED, SED contacts peer 2. After two weeks (?), session is administrively disabled ("neighbor ... shutdown"), (peer is contacted?) 3. After a peering session is down for a further period with no response from the peer then the peering is removed from the RRC ("no neighbor ...") RRC Moves/New RRCs * RRC08 (MAE West) has very few peers and more networks are pulling out of MAE West. We need to investigate alternative locations for a route collector on the US West Coast - PAIX - Seattle - LAIIX (Telehouse) - ... Action: compare member lists of each West Coast exchange point (Matthew) How to move RRC? Simply get MCI to ship box to new location (or wait for NCC staff to be in the vicinity of San Jose). * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new peerings. Action: Contact George Michaelson (APNIC). Henk and Shane will be at IETF and can meet up with him there. * RRC13 (new RRC in Moscow) - Matthew has been in touch with RIPN (Russian Institute for Public Networks). - To simplify customs issues, it may be better for the host organisation to order machine to our specification (see below) directly from Dell in Russia. We would want to see the quote before agreeing to the purchase. - We need to know the IP configuration for the box so we can configure and ship the installation CD once the box is ordered. - Recent RRCs have been specified as: Dell PowerEdge 1750 (1U server) 1 GByte RAM 3 x 73 GByte Disk (configured as RAID5) 2.4 GHz Xeon CPU myASn Meeting with Alexis last week didn't happen (Alexis out of town?) Action: contact Alexis to set up meeting (Arife) Matthew's slide "On the road to myASn v.1": - Automate account creation - bring together AS3333/K-Root/RIS peering setup and myASn account creation - For each peering confirmation, the peer should be made aware of the other RIPE NCC peering opportunities, etc. where appropriate. Action: Check with Dave Knight what, if anything, is mentioned about other NCC services when K-Root peering is established (Bruce) - Would be easier if all NCC peerings were handled by the same group. - K-Root peerings are more restrictive than RIS peerings. AOB RIPE49 (Manchester) RIS Update presentation myASn Tutorial Action: Speak to Shane and get back to Matthew et al. (Arife) [Shane had already left the meeting at this point] Inventory Ruud asks for Dell Service Tags for each RRC to add to the inventory. Ops Interaction Reminder to use <ops(a)ripe.net> as first point of contact instead of sending email to Bruce/James directly.

1 0

myASn - Last check list
by Matthew Williams 28 Jul '04

28 Jul '04

Fix errors, addtional features no in wp4. /Matthew - minED - minEC - ADW ++++ Clean out manual/auto - set dbase clean out time in alarm gr page ++++ You'll send email w/ xml example, import/export ++++ Optional: Experimental retromatch (not in wp4!) ++++ Breadcrumbs - Help ++++ Emails - change HDT, HDE, TTL ++++ Customer alarm - alarm 742 - no asns Customer alarm 742 (Default), 217.145.48.0/20 (exceptions not shown), MyASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 .=------+-----------------+--------------+--------------------------+-------------------------=. | RRC | Prefix | Peer | First Seen | Last Seen | |=------+-----------------+--------------+--------------------------+--- |----------------------=| | rrc10 | 217.145.48.0/20 | 217.29.66.65 | Wed Jul 7 02:02:01 2004 | Wed Jul 7 02:02:01 2004 | '=------+-----------------+--------------+--------------------------+-------------------------=' ++++ Add rrc12, tell SED about myasn.conf ++++ Remove alarms in uk.bt account ++++ Delete _all_ alarms in alarm groups ++++ Error handling when importing xml, cancel, fix error, try again --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

1 0

O: I need James or Bruce to come up with specs for PowerEdge 1750 intended as RRC13 at MSK-IX
by Matthew Williams 27 Jul '04

27 Jul '04

Hereby I wish to notify Operations of something uncategorised. Detailed description: --------------------- Pls see subline Cheers, Matthew Regards, Matthew Williams

1 0

Re: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group
by Rene Wilhelm 27 Jul '04

27 Jul '04

> > Matthew, > > > > We're working with Jeroen on updating the RIS pages for the new web server > > now, and I'd prefer not to have multiple people working on the site. > > > > What is the basic idea and/or scope behind this risintro page? > > This came up when the announcement for rrc12 was put online. The text > there assumes that one knows what the RIS is. Somebody then suggested to > have a short 1 page intro to the RIS for people who get the announcement > but haven't heard of the project. Linking the news flash on www to the risintro page is fine with me, better than diving immediately to the RRC12 specific page, but to set the record straight, all I suggested was to have a page with text similar to the announcement that was send out to the ris-users mailing list. Visitors to www.ripe.net see a news flash "Route Collector deployed at xyz-IX" and when they want to read more on this, the link should bring them to a page with relevant information. (which, next to details on deployement at the specific location, could have some words on RIS in general too). As such a page can easily be reused when a next RRC comes online, maybe it's an idea to design some template in the context of the current RIS pages restructuring work? Cheers, -- Rene P.S. All this was triggered by an external user pointing out to me the date on the announcement at www.ripe.net was wrong :)

3 2

RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group
by Matthew Williams 27 Jul '04

27 Jul '04

Hi Henk, I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html Will this do? Basic stuff... Feedback welcome though :) Cheers, Matthew *) VoS only ;) > -----Original Message----- > From: Henk Uijterwaal via RT [mailto:ops@ripe.net] > Sent: 26 July 2004 16:28 > To: matthew(a)ripe.net > Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian > bedford to the projects group > > > Hi, > > > Otherwise add webmaster to np and/or tt groups. > > That won't allow you to edit RIS files :-) > > Seriously, there is a ris group for RIS, the ris is run by > different department these days, so simply putting the > webmaster in the RIS group and changing ownership of the > files, should solve the problem. > > Henk > > > -------------------------------------------------------------- > ---------------- > Henk Uijterwaal Email: > henk.uijterwaal(at)ripe.net > RIPE Network Coordination Centre > http://www.amsterdamned.org/~henk > P.O.Box 10096 > Singel 258 Phone: +31.20.5354414 > 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 > The Netherlands The Netherlands Mobile: +31.6.55861746 > -------------------------------------------------------------- > ---------------- > > Process and Procedure are the last hiding place of people > without the wit > and wisdom to do their job properly. > (David Brent). >

3 7

RIS work items
by Henk Uijterwaal (RIPE NCC) 26 Jul '04

26 Jul '04

Hi all, (By popular request in ASCII). Here is the list of to-do-items that are still open in the RIS move. All items that were completed (=80 to 90% of the work) are not on the list. Henk - - - - Integration with OPS (98% done) - Software Sync for RRC01-13 Few hours Bruce Procedures - Maintain operations draft Sep-Dec'04 Arife (background task) Routing Training - Stalled, looking for trainer. Ongoing work - MyASN handover 28/7 Matthew/Arife/Alexis/SED - MyASN documentation Now-R49 Matthew - RRC installation UAE ?? Matthew, Henk Integration with SED - Move III pages out of NP area 1 day Arife/James/Katie/Engin - Review docs on iii 1 week Arife/James/Katie/Engin Software move - Document existing software 4 weeks (50% done) Arife, James - Review documentation 2 weeks Engin, Katie - Prtraceroute with RISwhois 11/2004, 1 wk Katie - Maintain documents All Research Issues - Analysis of Beacon Data Fall'2004 Arife, Henk - BGP Stability Index Fall'2004 James - Website restructuring Summer Matthew, Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent).

1 0

myASn status slide for Mon's meeting
by Matthew Williams 26 Jul '04

26 Jul '04

Hi Gang, Discussion fodder? ;) Cheers, Matthew

3 4

Re: RIS Statistics Report
by Arife Vural 26 Jul '04

26 Jul '04

It looks I missed to update Weekly Report, I will add it. Arife On Mon, Jul 26, 2004 at 08:53:28AM +0200, Henk Uijterwaal (RIPE NCC) wrote: > > I just noticed that RRC12 is not in the table yet. > > Henk > > > On Mon, 26 Jul 2004, Generic RIS account wrote: > > > > > RIS Statistics Report (20040719-20040726) > > > > This report was generated at Mon Jul 26 00:15:01 UTC 2004. It analyses the BGP > > Routing Tables which are collected by RIS Remote Collectors at different locations > > around the world. Check http://www.ris.ripe.net/weekly-report/ for more info. > > > > o Prefix Distribution > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > APNIC 27343 26793 26079 15703 27061 20508 26186 26433 26368 13545 25282 19216 > > ARIN 62135 61390 59038 24057 61836 58807 60725 59804 60640 9111 58800 54355 > > LACNIC 7015 5982 5959 3310 6998 5664 5983 5976 5959 1455 5930 5215 > > RIPE NCC 31065 25503 24552 14214 30629 20246 24976 24851 24651 6889 24454 19356 > > OLD 31546 30909 29342 13460 31184 27157 29943 30174 29430 6630 29076 26023 > > IANA 1733 973 889 601 1714 796 909 882 915 166 881 689 > > RFC1918 4 0 0 0 4 0 0 0 0 0 0 0 > > OTHER 0 0 0 0 0 0 0 0 0 0 0 0 > > TOTAL 160841 151550 145859 71345 159426 133178 148722 148120 147963 37796 144423 124854 > > > > > > AS number distributions wrt RIR and single-homed/multi-homed. > > > > o ASes per RIR region > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 10119 10078 10000 254 10076 9838 10041 10020 9999 2982 9973 9218 > > APNIC 2051 2050 2028 35 2050 1706 2038 2030 2023 1242 2020 1543 > > RIPE NCC 5725 5702 5672 2322 5715 5029 5497 5664 5625 2130 5685 4877 > > LACNIC 62 62 57 7 61 61 62 62 57 25 57 56 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 22 10 6 3 16 2 11 3 5 2 5 6 > > Others 1 0 0 1 1 0 0 0 0 0 0 0 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Number of single-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 2948 3675 4762 160 3266 4842 4068 5892 4086 1787 4781 4348 > > APNIC 526 612 706 28 593 673 704 1134 759 610 826 687 > > RIPE NCC 1586 1973 2113 1433 1739 2079 2058 3346 2106 1199 2481 2251 > > LACNIC 30 31 30 7 30 31 32 39 28 18 31 30 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 15 10 6 1 13 2 9 3 5 2 4 6 > > Others 0 0 0 1 0 0 0 0 0 0 0 0 > > Total 5106 6302 7618 1630 5642 7628 6872 10415 6985 3617 8124 7323 > > > > > > o Number of multi-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 7171 6403 5238 94 6810 4996 5973 4128 5913 1195 5192 4870 > > APNIC 1525 1438 1322 7 1457 1033 1334 896 1264 632 1194 856 > > RIPE NCC 4139 3729 3559 889 3976 2950 3439 2318 3519 931 3204 2626 > > LACNIC 32 31 27 0 31 30 30 23 29 7 26 26 > > IANA 0 0 0 0 0 0 0 0 0 0 0 0 > > Private 7 0 0 2 3 0 2 0 0 0 1 0 > > Others 1 0 0 0 1 0 0 0 0 0 0 0 > > Total 12875 11601 10146 992 12278 9009 10778 7365 10725 2765 9617 8378 > > > > IANA : AS65535 > > > > Others: AS65535 > > > > Distribution of AS number wrt Leaf, Transit. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Leaf 14834 14916 14872 1980 14863 13925 14701 15177 14882 4960 14967 13148 > > Transit 3041 2885 2783 440 2956 2516 2823 2515 2719 927 2681 2293 > > Transit-only 106 102 109 202 101 196 126 88 109 495 93 260 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Average ASPATH length. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Avg 6.14 5.91 5.94 5.68 6.13 6.01 6.23 6.12 6.43 5.89 5.85 6.04 > > Std 2.73 2.65 2.81 3.20 2.76 2.42 2.85 2.37 2.63 2.82 2.44 2.24 > > > > o List of martians appearing throughout the week. > > > > Prefix Origin AS > > 192.168.90.0/24 5417 > > 192.168.91.0/24 5417 > > 192.168.191.0/24 5417 > > > > > > o List of hot-spots during the week. > > > > Prefix Origin AS Number of updates > > 209.182.81.0/24 19071 203706 > > 209.114.254.0/24 14359 157276 > > 195.239.204.0/24 3216 134771 > > 195.218.176.0/24 3216 132598 > > 139.91.40.0/24 8522 121002 > > 139.91.252.0/24 8522 110100 > > 202.140.156.0/22 9910 80133 > > 209.205.84.0/24 15066 73047 > > 209.205.81.0/24 15066 73044 > > 194.133.184.0/21 0 67260 > > > > > > Total number of RIS BGP peering sessions: 416 > > > > ------------------------------------------------------------------------------ > Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net > RIPE Network Coordination Centre http://www.amsterdamned.org/~henk > P.O.Box 10096 Singel 258 Phone: +31.20.5354414 > 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 > The Netherlands The Netherlands Mobile: +31.6.55861746 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent).

1 0

Re: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Rene Wilhelm 25 Jul '04

25 Jul '04

> > No, but people tend to reply to the last mail they have in their files, > > if you use something like hm-ack(a)r.n it looks as if a human will read > > it. > > We have an address for this, called <unread(a)ripe.net>. Why does the autoresponse have to come from an unread email account? If I were a user and needed to add info to a ticket or query it's status, it would be most convenient if I could reply to the first (auto)reply to my initial message, as that ensures I get the ticket number right. This is how the OPS & TT-OPS ticketing systems work. (ok the tt ticketing system, currently doesn't autoreply, but if it would, it would send one "From: tt-ops") -- Rene

4 3

Re: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Rene Wilhelm 23 Jul '04

23 Jul '04

>> Why does the autoresponse have to come from an unread email account? > For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more about > these mysteries than I do). ah, right! loops should indeed be avoided in automated response systems, mail servers could quickly come to a grinding halt. (IIRC, NCC has had it's shares of loop problems with the hostmaster robot in the past) > For hostmasters, the "From:" is actually <hostmaster(a)ripe.net>. I guess it > makes sense for the "From:" to be <ris(a)ripe.net> in this case. If it cannot create loops, from (or reply-to for that matter) <ris(a)ripe.net> would be great for tickets coming in to ris. -- Rene

1 0

FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Matthew Williams 23 Jul '04

23 Jul '04

Peering requests hasn't worked very well in the past. Good work :) Cheers, Matthew > -----Original Message----- > From: RIPE NCC Acknowledgements [mailto:hm-ack@ripe.net] > Sent: 23 July 2004 14:48 > To: RIS Peering Request > Subject: NCC#2004073298 Re: rrc01:PEERING 8210 > > > Greetings, > > This message has been automatically generated in response to the > e-mail: > > To: RIS Peerings<rispeering(a)ripe.net> > From: RIS Peering Request <risops(a)ripe.net> > Date: Fri, 23 Jul 2004 12:47:44 GMT > Message-ID: <200407231247.i6NCli3U013164(a)halfweg.ripe.net> > Subject: rrc01:PEERING 8210 > > There is no need to reply to this message right now. Your > ticket has been assigned an ID of "NCC#2004073298". Please > include this string in the subject line of any further > correspondence on this matter. > > For more information about the RIPE NCC RIS Project, please > refer to http://www.ripe.net/ris/. > > Thank you, > > RIPE NCC Software Department >

5 6

RIS move status
by Henk Uijterwaal (RIPE NCC) 23 Jul '04

23 Jul '04

Arife, Can I have a few minutes on Monday's agenda to go over the status of the move, see attached MPP file with details? Thx, Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent).

3 2

FW: [ris-int] Re: RRC12 announcement on www.ripe.net
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Adrian, Rene came up with the idea to link announcements to a little RIS intro page with a few links. Is that something you can help us with? Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 23 July 2004 15:49 > To: Matthew Williams > Cc: ris-int(a)ripe.net; 'Rene Wilhelm' > Subject: Re: [ris-int] Re: RRC12 announcement on www.ripe.net > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > * Sure, we could do that. Mind you, what is Adrian up to > nowadays? Great opportun > * ity to dig into the RIS aspect of IS... ;) > > Talk to Adrian. BTW, if you want him to change RIS pages, > make sure you add him to the projects group. > > -J > > * > * Cheers, > * Matthew > * > * > -----Original Message----- > * > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > * > On Behalf Of RIPE NCC Webmaster > * > Sent: 23 July 2004 13:25 > * > To: Rene Wilhelm > * > Cc: ris-int(a)ripe.net > * > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net > * > > * > > * > > * > Rene Wilhelm <wilhelm(a)ripe.net> writes: > * > * > * > * I didn't keep track of it myself, but an external user noticed > * > * this announcement on www.ripe.net yesterday, JULY 22. The date > * > * seems wrong :( > * > > * > Damn.. I changed it to 20 July. > * > > * > * > * > * RIPE NCC Announcements > * > * > * > * [22 June 2004] > * > * RIPE NCC Remote Route Collector Deployed at German > * > Internet Exchange (DE-CIX > * > * ) > * > * > * > * > * > * I was also wondering if it wouldn't be better to make the link > * > * point to a page with the announcement that was send out to > * > ris-users, > * > * (copied below) rather than jump deep down into the > RIS web tree. > * > * The announcement puts things more into context with a > paragraph > * > * summarizing the project and pointers to more RIS info > at the end. > * > * The http://www.ripe.net/ris/rrc12.html page seems more > * > * targeted at people who already familiar with RIS and just > * > * want to learn where the box is, what the peering policy and > * > * peering details are. > * > * > * > > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > > * > -J > * > > * > > * > * > * > * -- Rene > * > * > * > * > * > * > From: ris-users-admin(a)ripe.net > * > * > [mailto:ris-users-admin@ripe.net] On Behalf Of > Matthew Williams > * > * > Sent: 07 July 2004 19:11 > * > * > To: ris-users(a)ripe.net > * > * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > * > * > DE-CIX (RRC12) > * > * > > * > * > [Apologies for duplicate mails] > * > * > > * > * > Dear All, > * > * > > * > * > The RIPE NCC is pleased to announce that the RIS Project's > * > * > twelth* Remote Route Collector, RRC12, is now ready to peer > * > * > with members at the German Internet Exchange (DE-CIX). > * > * > > * > * > RRC12 is located at the German Internet Exchange (DE-CIX), > * > * > and has been operational since July 2004. The RRC has an > * > * > interface on the shared DE-CIX fabric, running both > IPv4 and > * > * > IPv6, and collects routing information from all exchange > * > * > members, who are willing to peer with us. > * > * > > * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is > * > * > supported on all RIS Route Collectors. MD5, however, is not > * > * > supported on IPv6 sessions. > * > * > > * > * > Details: > * > * > -------- > * > * > - Peering address: 80.81.192.152 (IPv4); > * > 2001:7f8::316e:0:1 (IPv6) > * > * > - Autonomous system: 12654 > * > * > - Policy: http://www.ripe.net/ris/rrc12.html > * > * > - Peering requests: > * > * > * Email: rispeering(a)ripe.net > * > * > * Web form at URL: > * > http://www.ris.ripe.net/cgi-bin/peerreg.cgi > * > * > > * > * > The > * > Routing Information Service (RIS), which started as a > * > * > modest RIPE NCC project in 1999, has gradually > grown to over > * > * > 300 IPv4 and IPv6 peers at now twelve* data > collection points > * > * > in Europe, Japan and North America. Our mission is > to collect > * > * > BGP routing information over a function of time, > and make it > * > * > available to the Internet community. In essence, this means > * > * > devising tools that can help ISPs debug problems over time > * > * > without being limited to one BGP view and providing RIS raw > * > * > data regarding the Internet's historical development. > * > * > > * > * > Useful Links: > * > * > ------------- > * > * > RIS Info: http://www.ripe.net/ris/ > * > * > RIS Tools: http://www.ripe.net/ris/query.html > * > * > List of RRC Locations: > * > http://www.ris.ripe.net/cgi-> bin/rrcstatus.cgi > * > * > > * > * > > * > Please send your comments to > * > ris-int(a)ripe.net. > * > * > > * > * > Best regards, > * > * > The RIS Team > * > * > > * > * > *) RRC09 has been decommissioned > * > * > > * > * > --- > * > * > > Matthew Williams (MW243-RIPE) > * > * > > Customer Liaison Engineer > * > * > > RIPE NCC - http://www.ripe.net/np/ > * > * > * > > * >

1 0

RRC12 announcement on www.ripe.net
by Rene Wilhelm 23 Jul '04

23 Jul '04

I didn't keep track of it myself, but an external user noticed this announcement on www.ripe.net yesterday, JULY 22. The date seems wrong :( RIPE NCC Announcements [22 June 2004] RIPE NCC Remote Route Collector Deployed at German Internet Exchange (DE-CIX) I was also wondering if it wouldn't be better to make the link point to a page with the announcement that was send out to ris-users, (copied below) rather than jump deep down into the RIS web tree. The announcement puts things more into context with a paragraph summarizing the project and pointers to more RIS info at the end. The http://www.ripe.net/ris/rrc12.html page seems more targeted at people who already familiar with RIS and just want to learn where the box is, what the peering policy and peering details are. -- Rene > From: ris-users-admin(a)ripe.net > [mailto:ris-users-admin@ripe.net] On Behalf Of Matthew Williams > Sent: 07 July 2004 19:11 > To: ris-users(a)ripe.net > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering(a)ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int(a)ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/

3 3