- Ris-int - mailman.ripe.net

ziya is ris-int from now on.
by Arife Vural 02 Aug '04

02 Aug '04

All in subject.

1 0

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