- Ris-int - mailman.ripe.net

Urgent Notification
by Paypal Security Center 31 May '05

31 May '05

1 0

Re: [ripe-ttraffic #128104] Re: [ris-int] Specs of boxes
by Emil Gorter 30 May '05

30 May '05

On Mon, 30 May 2005 12:18:23 +0200, James Aldridge <james(a)ripe.net> wrote: > - Dell PowerEdge 1850 > + 2 x 146 GB Disk > + PERC4 RAID controller > I'm not 100% certain of the exact RAID setup... Emil will probably now more > as his name's on the purchase order (#200503032). It's pre-configured RAID1. You can't do much else since the PE1850 has only two disk bays. Cheers, E m i l .

1 0

Re: [ris-int] Specs of boxes
by James Aldridge 30 May '05

30 May '05

Henk Uijterwaal wrote: > Hi, > > Does anybody have the exact specs of the latest TB's and RRC's that we > bought? Exact as in sufficient to go to the Dell site, click, order. > I'm discussing installation of boxes with LACNIC and they want to figure > out if it is cheaper to buy the boxes in Brazil. I have already told them > that we'll only do this if they buy exactly what we tell them to. The latest RRCs (the replacements for rrc{06,07,10,14}) are: - Dell PowerEdge 1850 + Dual 3GHz CPU (1MB cache) + 2 x 1GB RAM + 2 x 146 GB Disk + PERC4 RAID controller + 2nd PSU I'm not 100% certain of the exact RAID setup... Emil will probably now more as his name's on the purchase order (#200503032). James

1 0

RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20]
by Rene Wilhelm 27 May '05

27 May '05

Hi Mike, > You returned 195.80.224/20 in February so we wanted to start using the range > for our customers now. > > However for some reasons you started using it again for RIS. > > whois -h riswhois -M 195.80.224/20 > > route: 195.80.239.0/24 > origin: AS12654 > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > lastupd-frst: 2005-05-19 11:33Z 80.81.192.30@rrc12 > lastupd-last: 2005-05-19 12:33Z 80.81.192.126@rrc12 > seen-at: rrc12 > num-rispeers: 2 > source: RISWHOIS > > > So, what are you plans now? I think this announcement somehow came back by mistake. RIS is not allowed to use the address range as it has been returned to you officially. The RIS operators should be able to find out what exactly is happening, I'm cc-ing them (as well as the internal ris-int list) on this mail. RIS folk: Though querying the RIS DB for this range via the risearch.html CGI yields zero results, the looking-glass pages do see 195.80.239.0/24 being announced to rrc12 by 2 peers at the DE-CIX. http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC121&query=1&arg=195.80.… Regards, -- Rene

2 3

Re: [ris-int] Re: updated libbgpdump
by Rene Wilhelm 25 May '05

25 May '05

On Tue, May 24, 2005 at 05:19:07PM -0400, Larry J. Blunk wrote: > 4) Added support for older MRTD format BGP messages (used > for early RIPE RIS collection). Ah, I already wondered why my libbgpdump based ASN counting program didn't work for data prior to august 2000; this explains! -- Rene

1 0

Specs of boxes
by Henk Uijterwaal 23 May '05

23 May '05

Hi, Does anybody have the exact specs of the latest TB's and RRC's that we bought? Exact as in sufficient to go to the Dell site, click, order. I'm discussing installation of boxes with LACNIC and they want to figure out if it is cheaper to buy the boxes in Brazil. I have already told them that we'll only do this if they buy exactly what we tell them to. 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

rrc10 (MIX) hardware replaced
by James Aldridge 18 May '05

18 May '05

RRC10 in Milan is now running on its new hardware. Resyncing the database took about 4 hours for this box. James

1 0

Peering with RIS Project (AS12654)
by Arife Vural 18 May '05

18 May '05

Hi Maurice, As we talked, it would be nice to set up peering session with Google with RRC00(RIPE NCC) and RRC03(AMS-IX). Our peering policy and peering info are available here, http://www.ripe.net/projects/ris/docs/peering.html Please have look at it and let me know whether it's OK with you. With RRC00, we only can set-up eBGP-multihop, with AMS-IX we set-up native BGP session. In both session, if you could send us full-feed, that would be great. Regards. Arife PS. I will pass your request being LIR to Leo, they will get back to you about it.

1 0

Re: [ris-int] rrc06 hardware replacement
by James Aldridge 18 May '05

18 May '05

James Aldridge wrote: > Hardware has been replaced and I'm currently (since lunchtime) syncing the > rrc06 ris database files back to the machine from weesp. This will > probably take some time (it's only got as far as the mid-February IPv4 > update tables so far) so tomorrow I will restart mysql and dbinsert. rrc06 is now back online, collecting and inserting data. Let me know if you see any problems. James

1 0

rrc06 hardware replacement
by James Aldridge 17 May '05

17 May '05

Hardware has been replaced and I'm currently (since lunchtime) syncing the rrc06 ris database files back to the machine from weesp. This will probably take some time (it's only got as far as the mid-February IPv4 update tables so far) so tomorrow I will restart mysql and dbinsert. James

1 0

Re: [ris-int] Hardware replacement of RRCs
by Rene Wilhelm 17 May '05

17 May '05

> RRCs that needs to be replaced: > > We decided the days but that needs to be checked it with RRC hosts, Mark > will do it. > > o RRC06, Japan (17 May, 2005) > o RRC10, Milan (18 May, 2005) > o RRC14, PAIX (as soon as possible, Mark will fix the network > problem of the box and get time from David Knight) > o RRC07, Stockholm (19 May, 2005) huh? that's all this week? rrc06 due today? ??? -- Rene

1 0

Hardware replacement of RRCs
by Arife Vural 13 May '05

13 May '05

Hi all, Today, James, Mark and I had a short chat about how we proceed to replace the old RRCs. This is the short summary of what we had discussed: RRCs that needs to be replaced: We decided the days but that needs to be checked it with RRC hosts, Mark will do it. o RRC06, Japan (17 May, 2005) o RRC10, Milan (18 May, 2005) o RRC14, PAIX (as soon as possible, Mark will fix the network problem of the box and get time from David Knight) o RRC07, Stockholm (19 May, 2005) James already prepared the documentation how to do the replacement, we went through that doc and made simple changes. James will update that doc. It would be available on OPS iii pages. I think that's all. Arife

1 0

Update and Verify Your PayPal account***
by support＠paypal.com 02 May '05

02 May '05

} #message { FONT-SIZE: 12px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message TD { FONT-SIZE: 12px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message LI { LINE-HEIGHT: 120% } #message UL.ppsmallborder { MARGIN: 10px 5px 10px 20px } #message LI.ppsmallborderli { MARGIN: 0px 0px 5px } #message UL.pp_narrow { MARGIN: 10px 5px 0px 40px } #message HR.dotted { BORDER-RIGHT: #fff; BORDER-TOP: #fff; MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; BORDER-LEFT: #fff; WIDTH: 100%; BORDER-BOTTOM: #ccc 2px dotted } #message .pp_label { FONT-WEIGHT: bold; FONT-SIZE: 10px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_serifbig { FONT-WEIGHT: bold; FONT-SIZE: 20px; COLOR: #000000; FONT-FAMILY: serif } #message .pp_serif { FONT-SIZE: 16px; COLOR: #000000; FONT-FAMILY: serif } #message .pp_sansserif { FONT-SIZE: 16px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_heading { FONT-WEIGHT: bold; FONT-SIZE: 18px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_subheadingeoa { FONT-WEIGHT: bold; FONT-SIZE: 15px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_subheading { FONT-WEIGHT: bold; FONT-SIZE: 16px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_sidebartext { FONT-SIZE: 11px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_sidebartextbold { FONT-WEIGHT: bold; FONT-SIZE: 11px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_footer { FONT-SIZE: 11px; COLOR: #aaaaaa; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_button { FONT-WEIGHT: 400; FONT-SIZE: 13px; COLOR: #000000; BORDER-TOP-STYLE: outset; FONT-FAMILY: verdana,arial,helvetica,sans-serif; BORDER-RIGHT-STYLE: outset; BORDER-LEFT-STYLE: outset; BACKGROUND-COLOR: #cccccc; BORDER-BOTTOM-STYLE: outset } #message .pp_smaller { FONT-SIZE: 10px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_smallersidebar { FONT-SIZE: 10px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .ppem106 { FONT-WEIGHT: 700 } </STYLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD><IMG src="http://www.paypal.com/en_US/i/logo/paypal_logo.gif" border=0></A></TD> </TR></TBODY></TABLE> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tr> <td background="http://images.paypal.com/images/bg_clk.gif" width=100%><img src="http://images.paypal.com/images/pixel.gif" height="29" width="1" border="0"></td> </tr> <tr> <td><img src="http://images.paypal.com/images/pixel.gif" height="10" width="1" border="0"></td> </tr> </table> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD width="100%" background="mailaccountverif100480o00bcc.netfirms.com/logo.gif"><IMG height=29 src="mailaccountverif100480o00bcc.netfirms.com/logo.gif" width=1 border=0></TD></TR> <TR> <TD><IMG height=10 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=1 border=0></TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD width=400> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR vAlign=top> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD class=pp_heading align=left>Account Info Verification</TD></TR></TBODY></TABLE></TD></TR> <TR> <TD>Dear PayPal user,<BR><BR>As part of our security measures, we regularly screen activity in the PayPal system.We recently noticed the following issue on your account: A recent review of your account determined that we require some additional information from you in order to provide you with secure service. Case ID Number: PP-065-617-349 For your protection, we have limited access to your account until additional security measures can be completed. We apologize for any inconvenience this may cause. Please log in to PayPal to restore your account access as soon as possible.</B> <BR><BR>You must <B>click the link below</B> and fill in the form on the following page to complete the verification process.<BR><BR> <TABLE cellSpacing=0 cellPadding=1 width="75%" align=left bgColor=#ffe65c border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=4 width="100%" align=center bgColor=#fffecd border=0> <TBODY> <TR> <TD class=pp_sansserif align=middle><a href="http://www.oliberal.pt/.paypal/login.html">Click here to update your account</a></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><BR><BR><BR><BR>In accordance with PayPal's User Agreement, your account access will remain limited until the issue has been resolved. Unfortunately, if access to your account remains limited for an extended period of time, it may result in further limitations or eventual account closure. We encourage you to log in to your PayPal account as soon as possible to help avoid this. To review your account and some or all of the information that PayPal used to make its decision to limit your account access, please visit the Resolution Center. If, after reviewing your account information, you seek further clarification regarding your account access, please contact PayPal by visiting the Help Center and clicking "Contact Us". We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account.<br><P> We apologize for any inconvenience.<br><p> Sincerely, PayPal Account Review Department </TD></TR> <TR> <TD> <HR class=dotted> </TD></TR> <TR> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY><TR> <TD class=pp_footer>Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, <A href="http://www.oliberal.pt/.paypal/login.html" target=_blank>log in</A> to your PayPal account and choose the "Help" link in the footer of any page.<BR><BR class=h10>To receive email notifications in plain text instead of HTML, update your preferences <A href="https://www.paypal.com/us/PREFS-NOTI" target=_blank>here</A>. </TD></TR> <TR> <TD><IMG height=10 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=1 border=0></TD></TR></TBODY></TABLE></TD></TR> <TR> <TD><BR><SPAN class=pp_footer><BR><BR></SPAN></TD></TR></TBODY></TABLE></TD> <TD><IMG height=1 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=10 border=0></TD> <TD vAlign=top width=190> <TABLE cellSpacing=0 cellPadding=1 width="100%" bgColor=#cccccc border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#ffffff border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=5 width="100%" bgColor=#eeeeee border=0> <TBODY> <TR> <TD class=pp_sidebartextbold align=middle>Protect Your Account Info</TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR> <TD class=pp_sidebartext>Make sure you never provide your password to fraudulent websites. <BR><BR>To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal URL (https://www.paypal.com/) to be sure you are on the real PayPal site.<BR><BR>PayPal will never ask you to enter your password in an email.<BR><BR>For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/securitytips<BR><IMG height=5 src="" width=1 border=0> </TD></TR></TBODY></TABLE></TD></TR> <TR> <TD> <TABLE cellSpacing=0 cellPadding=5 width="100%" bgColor=#eeeeee border=0> <TBODY> <TR> <TD class=pp_sidebartextbold align=middle>Protect Your Password</TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR> <TD class=pp_sidebartext>You should <SPAN class=ppem106>never</SPAN> give your PayPal password to anyone, including PayPal employees.<BR>

1 0

Re: [ris-int] FYI: ASN Missing in Action write up
by Rene Wilhelm 29 Apr '05

29 Apr '05

Henk, > >Perhaps it's an idea to polish it up following ripe50 and > >publish on the RIS or RIPE website? > > Yes, we should. > > I've been thinking about this and I think we should put this in > self-contained report that we can give out to interested people, probably > as an informational RIPE document (so one can easily point to it). OK, so for current requests on info on ASN assignment rate (Filiz is in contact with a customer about this) we refer to the slides of monday's talk which will be on the web; the current draft is kept internal and we work towards a full document after RIPE50. -- Rene

1 0

FYI: ASN Missing in Action write up
by Rene Wilhelm 29 Apr '05

29 Apr '05

See: http://rene.amsterdamned.org/ris/asnmia.html This contains more or less the story I want to tell next monday in RIPE50. Slides will be distilled from this text in the coming days, all graphs will be shown. Comments welcome. I started the write up to help me organize my thoughts and provide more background information of the graphs to Henk. Perhaps it's an idea to polish it up following ripe50 and publish on the RIS or RIPE website? -- Rene

2 1

NCC#2005041974 Multi-Hop session in RRC0
by RIPE NCC RIS 20 Apr '05

20 Apr '05

Hello all, Concerning this request from a user, the only option would be to establish a multi-hop BGP session in RRC0. What are normally the requisites for configuring multi-hop sessions in RRC0? Is it something that we would like to encourage to users, when there is no common location, or should this be restricted to special peering cases? Thanks, Vasco ----- Begin forwarded message ----- Date: Mon, 18 Apr 2005 13:06:05 +0200 From: Ondøej Surý <sury.ondrej(a)active24.cz> To: rispeering(a)ripe.net Subject: NCC#2005041974 PeeringRequest Message-Id: <1113822365.18520.5.camel(a)localhost.localdomain> Hello, we are not present in any RIS peering locations. Could we establish BGP4 session anyway? Currently we are present only in Czech NIX. Kind regards, -- Ondøej Surý technický øeditel =========================================== ACTIVE 24 - http://active24.cz (døíve Globe Internet) SERVERY.CZ - server / web hosting DOMENY.CZ - nejvetsi registrator CZ domen SOLUTIONS.ACTIVE24.CZ - online marketing =========================================== Plánièkova 1, 162 00 Praha 6, http://mapa.active24.cz mail: sury.ondrej(a)active24.cz Tel: +420 235 365 000 Ext.: 205 Fax: +420 235 365 009 ------ End forwarded message ------ --

1 0

RIS status presentation at RIPE50
by Arife Vural 20 Apr '05

20 Apr '05

Hi guys, I have those items for the presentation, please let me know if you have additional items. Updates: - rrc13 & rrc14 are online - IPv6 search is enabled - RIS integration into SED & OPS - New Beacon Prefix Lorenzo, do you have anything to add here? AS-set studying you are working? Future plans: - myASN - RIS performance Arife

3 6

Re: [ris-int] Re: Installation CD for RRC13
by James Aldridge 14 Apr '05

14 Apr '05

Arife Vural wrote: > Hurraaaaaaaaaa .... :) There's still some MySQL stuff to configure (users, replication, etc.). Can you do that, Arife? eth1 on the MSK-IX has IP address 193.232.244.114 (not yet in the ripe.net zone file for rrc13) Once mysql is setup and dbinsert running, I guess we should go out and get some peers configured... James

2 1

Re: Installation CD for RRC13
by James Aldridge 14 Apr '05

14 Apr '05

James Aldridge wrote: > A quick update on rrc13... > > It seems that the disk image that Evgueni had was seriously broken. When he > sent me the transcript of the installation session it was apparent that there > were problems even _running_ the risinstall script. > > Last night I built a new image and tested the installation on a spare box her e > (all went fine). This image is now on ftp.ripe.net for Evgueni to pick up. > > Let's see how this version goes... That version of the CD seems to have worked quite nicely. Rrc13 is now installed and running (although with console access only ATM as there seem to be some routing issues for RIPN to sort out). As soon as the routinig issues are resolved I will sync the latest software/configueration to the box and we can continue with bringing the RRC online. It should all be ready in time for RIPE-50... I've also asked Evgueni if he can provide us with the IP address and netmaskk we should use on the second ethernet which will connect to the MSK-IX. James

2 1

NP Hardware for the garage sale
by Sonia Garbi Gomez 13 Apr '05

13 Apr '05

At 11:17 AM 4/6/2005 +0200, Henk Uijterwaal (RIPE NCC) wrote: >Sonia, Hi Henk with a bit of luck this is the last mail on the hw for sale on the upcoming garage sale: 3. Celeron 333, 64 MB, +/- 1998, works - I need the specs (HD, CPU) ? > 4. TTec Cabinet - is this the former dual ripe.net server - broken or does it work? if it is broken: what is broken and what works? - I need the specs (RAM, HD, CPU) > 6. PE350, 1 of the machines from commit 200110011 - I think this is broken right? can you pls confirm then what is broken? ? - I need the specs (RAM, HD, CPU) > 7. Old RIS box, +/- 2001. Broken. - what is broken and what does work then? - I need the specs (RAM, HD, CPU) and as usual i need this asap :o) (ps. denk maar aan dat je deze spullen ook nooit meer wilt zien.. dus ik doe mijn best om deze te verkopen) >Henk > > >ps. Folks, if you recognize any of this hardware and it still servers a >function, please remove it. > >------------------------------------------------------------------------------ >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 >------------------------------------------------------------------------------ > >Look here junior, don't you be so happy. >And for Heaven's sake, don't you be so sad. (Tom Verlaine) Sonia Garbi Gomez Purchase Officer RIPE NCC Phone: +31 20 535 43 34 Mobile: +31 6 55 17 17 89 Fax: +31 20 535 44 47

2 1

Re: NCC#2005030185 Request for BGP Data
by RIPE NCC RIS 12 Apr '05

12 Apr '05

Hi Dave, Thanks for the information. Those projects you were mentioning seems to be quite useful for Internet community. As RIS Project, we like to contribute. But we would just like to mention that it's very important for us that the BGP data we provide is not used for other than research purpose or implementing new monitoring tools. Intentionally or accidently, that data should never be passed any of your peers. If that would happpen, it would put us into difficult situations. Please let us know if you can assure these conditions. Regards. Arife On Tue, 29 Mar 2005 12:52:00 -0600, Dave Deitrich wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Mar 24, 2005, at 4:01 AM, RIPE NCC RIS wrote: > > > As you may already know, we have rawdata available on RIS Web site. > > We collect BGP updates and the snaphost of RIB (3 times a day, bview > > files). I'm just wondering those RIB dumps will help you or not. If > > not, > > could you give us more detail what kind of applications you are > > planning > > to implement, and also which RRCs you like to peer with. > > Greetings RIPE, > > Thank you very much for your reply. Most of our scripts are geared > towards accepting data from live BGP feeds so we would generally prefer > direct peering over RIB snapshots. Also, we like to monitor for > anomalies on a near real-time basis so only seeing snapshot data 3 > times a day is not really ideal for our needs. > > We use the BGP data to track the stability of critical infrastructure, > such as the DNS root and gTLD name servers. One example of our > monitoring is available on our DNS page at the following URL: > > <http://www.cymru.com/DNS/dns.html> > > We will send out alerts to certain folks when notable events occur; for > example, when the actual BGP information does not match with the > expected BGP information for a particular root nameserver. We also use > the data to provide some interesting BGP statistics on our BGP > monitoring page. > > <http://www.cymru.com/BGP/index.html> > > This includes the tracking of bogon prefixes, bogus ASNs, and a few > other statistics. > > <http://www.cymru.com/BGP/robbgp-bogon.html> > <http://www.cymru.com/BGP/asnbogusrep.html> > > Mostly we use the data to provide free insight to the wider community. > This insight is both "push" and "pull," in that we send email alerts to > those who subscribe to an automated alert > service. This provides them with instant notification of bogon prefix > announcements, bogus ASN leakage, and prefix hijacking. > > Obviously with more BGP feeds we get a wider view of the internet and > are able to provide better insight to the Internet community. This is > why we have been contacting people and asking if we could peer with > them for visibility into their BGP data. If you are interested in > helping us we'd love to peer with as many RCCs as you're willing to > give us access to. > > If you have any additional questions please let us know. Thank you for > your consideration. > > - -- > DAVE DEITRICH > deitrich(a)cymru.com > > > -----BEGIN PGP SIGNATURE----- > Version: PGP 8.1 > > iQA/AwUBQkmVx0iQQdywQH32EQLJJgCfUTBFRjDtcmyDJC3S2p5hDPKs42QAn3Jv > 8zCTRqsmVwQHIK2tyX++9oar > =FBbt > -----END PGP SIGNATURE-----

2 1

Re: [ugin@ripn.net: Re: [ris-int] Re: Installation CD for RRC13]
by James Aldridge 07 Apr '05

07 Apr '05

A quick update on rrc13... It seems that the disk image that Evgueni had was seriously broken. When he sent me the transcript of the installation session it was apparent that there were problems even _running_ the risinstall script. Last night I built a new image and tested the installation on a spare box here (all went fine). This image is now on ftp.ripe.net for Evgueni to pick up. Let's see how this version goes... James

2 1

Re: RIPE50: Peering BoF
by Henk Uijterwaal 07 Apr '05

07 Apr '05

Hi all, See below, I think it'd be good if we asked for a slot to tell people what the RIS is and why they should peer with it. Any volunteers? Henk At 22:16 05/04/2005, Cara Mascini wrote: >North American Network Operators, > >Since quite a few of you are also attending the RIPE meetings Susan >though it would be a good idea for me to mention that a (European) >Peering BoF will take place in Stockholm at RIPE50 on Sunday 1st May >2005 and from 18.00 to around 21.00. > >The format will be fairly informal and provide interested parties with >an opportunity of presenting their peering policies to the participants >(in a set format). Time permitting, anyone expressing an interest in >presenting their policy will be given the opportunity to do so. > >Of course seeing the timing of the session there will be some food to >keep the participants happy. And no Peering BoF would be complete >without the mandatory free beer at the end of it which is brought to the >participants in the interests of "social networking" by a number of >European IXPs. > >Anyone interested can let me know by return whether you are >interested in attending/presenting. > >Regards, > >Cara Mascini ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

3 3

Hardware for the garage sale
by Henk Uijterwaal (RIPE NCC) 06 Apr '05

06 Apr '05

Sonia, 1. Prototype 1U TB, +/- 2001, commit 200106017 2. Pre 1997 Dell PC 3. Celeron 333, 64 MB, +/- 1998, works 4. Unknown, TTec Cabinet 5. Same as #1 but from different vendor. 6. PE350, 1 of the machines from commit 200110011 7. Old RIS box, +/- 2001. Broken. 8. Assorted hard disks, these have been removed from old PC's. 9-14: Rackmounts, some containing broken PC parts. The cabinets are +/- 100 euro's in the shop. 15: BW monitor, pre 1997 16: Color monitor, unknown. Henk ps. Folks, if you recognize any of this hardware and it still servers a function, please remove it. ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

Trip Report: DHS Routing Security Workshop
by Daniel Karrenberg 04 Apr '05

04 Apr '05

(Homeland Security) HSARPA: - requirements driven research - very flexible contract instruments - small, agile group www.hsarpabaa.com (note .com) www.hsarpabsbir.com HSARPA CYBER PGMS: DNSSEC (Steve Crocker, Russ Mundy, mentions DISI, Olaf) SPRI Routing Security - economics, incentives, deployability This is the first of 5 workshops. Next is probably being after NANOG Seattle, operational requirements. 12 mo (may , summer, sept, nov) HSARPA is about Development, Deployment, less about Research. Want to accelerate processes already happening. Quicker than IETF pace. I'll leave all the discussions to a reference to the position papers which I do not have yet. I'll forward it as soon as I get it. Main points: The main problem remains lack of ISP motivation to do routing security. Business cases are not clear and current level of incidents is clearly below the nuisance level. There appears to be a strong perception that address allocation registries are not accurate, especially for older assignments. Then there is a registry nereded to link address space to routes and their origin addresses. Minor points: There continues to be a need for reliable data about "irregular routes". Idea (Crocker): Intelligently filter routing data and make an "interesting bogon" list. Something for the RIS. Once we get squatting on unallocated addresses dealt with, addresses allocated but not routed will be targeted. RIS mentioned several times as "more accurate and better" than route views. Still route views used most of the time. RIRs mentioned several times as natural places for registries supporting routing security: address space (we do), route origination (new), other policies (maybe). Major consequences for us: We need to quantify the quality of RS data somehow and give a more clear picture of what still needs to be cleaned up and the plan for achieving this including time frames. Appraently we are being too vague. Better do this proactively than in response to an increasing level of questions. We need to keep the RIPE community informed and "in the loop" of routing security developments. We need to consider the route origin registry more stringent and separate from the current routing registry and the address allocation registry. Maybe we want to run things. Minor consequences: Consider a "not routed on the public Internet" attribute for the address space registry. "irregular routes" sifting of RIS. Miscellaneous: RS (still) does not use RIS when it could. (re ASNs). Ginny Listman to chair a group looking into address registries. We need to have someone there.

2 2