February 2005 - Ris-int - mailman.ripe.net

Announcement: Changes to RIS Routing Beacons
by James Aldridge 25 Feb '05

25 Feb '05

------- Blind-Carbon-Copy To: ris-users(a)ripe.net, ops(a)linx.net, sfinx(a)ml.renater.fr, tech-l(a)ams-ix.net, announce(a)nl-ix.net, tech-users(a)lists.gn-ix.nl, vixoper(a)vix.at, peer.tech(a)mix-it.net Reply-To: ris(a)ripe.net Subject: Announcement: Changes to RIS Routing Beacons From: James Aldridge <james(a)ripe.net> X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 535 4444 X-Fax: +31 20 535 4445 Date: Fri, 25 Feb 2005 13:56:38 +0100 Sender: james(a)x34.ripe.net [Apologies for duplicate messages] The RIPE Routing Information Service has made some alterations to our BGP Routing Beacon announcements. The main changes (since 3 February 2005) are: * Beacon prefixes now come from a new, larger address range 84.205.64.0/19 (instead of 195.80.224.0/20); * We now announce an "anchor prefix" corresponding to each beacon; * For each beacon and anchor prefix there is a "pingable" target at the first address in the range (beaconNN.ris.ripe.net, anchorNN.ris.ripe.net) All prefixes announced by the RIS (AS12654) are listed in the AS12654:RS-RIS 'route-set' and individual 'route' objects in the RIPE Database and are described in more detail at http://www.ripe.net/projects/ris/docs/beaconlist.html RIS peers should set any maximum prefix limit to at least the number of entries listed in the route-set (although it is unlikely that any one RRC will ever advertise more than a small subset of these prefixes). We would also like our peers to treat these prefixes in the same way that they would a customer's prefix and announce them to their other peers and upstream providers. If you have any questions, please contact the RIS team at ris(a)ripe.net. Regards, The RIPE NCC RIS Team ------- End of Blind-Carbon-Copy

1 0

Re: [NCC#2005024029] RIS CGIs are online
by Rene Wilhelm 25 Feb '05

25 Feb '05

Hi Arife, >> I also have a request: once the prefix cgi is returning v6 results >> as expected, could you modify the riswhois cgi to also put up >> a "Query RIS database" button for IPv6 queries? >> James did the first versions of the riswhois cgi, but I guess that after >> the restructuring this is now SED responsibility. > Yes, you're right. I put into ToDo list. > About ETA, I can not say something definite this week. I'm second line > support for RIPE DBM, and it's bit busy. Next week I will get back to you. OK, that's perfectly fine. > Those CGIs are implemented Mason and Perl. One CGI has more than one > components. Form, result, and errors are printed by seperate html/cgi > files. We can easily pass the ARGS from one to another, but the result > page is not the one which is executing CGIs. That means if you copy and > paste and send somebody the result page with arguments, it will not work. > Since the CGI that executes the code is different than the one that > produce the results. Because of that I do not think it's not so useful > to have the ARGs in URL. > When I had a chat with Kevin about it, he suggested to add a link somewhere > on the page giving the URL. I do not know what you think about that. If > you want we can go for that. The most important thing is that by exchanging URLs people can point each other to results of a specific RIS query. Usually, you would go to the top of the browser and copy the URL there, but if that's not possible a link on the results page, something like "The URL for this query is $url" would work too. BTW, nice to see the query form is repeated on the results page! -- Rene

2 1

RIS meeting agenda for Monday
by Arife Vural 25 Feb '05

25 Feb '05

Hi guys, Does anybody have any agenda item for Monday? I do not have any particular agenda item other than RRC13. For RRC13, maybe Gerard will give us short update by e-mail. Arife

2 2

Suggested announcement for as-set stuffing experiments
by Lorenzo Colitti 24 Feb '05

24 Feb '05

Henk Uijterwaal wrote: > (I've no problems with this experiment as such. We should include > it in the announcement about the new beacons though, James?). Ok. What about the following text? It could be added to the beacon announcement, or I can whip up a standalone annoucement if you think it's necessary. (Comments welcome of course.) We also need to ask our peers to accept everything in the route-set *including ASes behind 12654* and not just ^12654$. James, could you add that to the description you are going to send to the peers? =====================8<------------------------- Beacon prefixes 84.205.73.0/24 and 84.205.89.0/24 will be used by researchers at the Computer Networks research group at Roma Tre University to perform studies on network topology discovery. The objective of the experiments is to investigate new methodologies for topology discovery and experimental mechanisms for deducing the routing policies of ISP's, the quality of their connectivity, and more general properties of interdomain topology. The experiments will involve announcing AS-sets of varying lengths behind AS 12654 and are initially scheduled for the last week of February and the first week of March. =====================8<------------------------- -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti(a)dia.uniroma3.it +39-0655173215 ---------------------------------------------------------

3 4

Re: [ris-int] RIS CGIs are online
by Rene Wilhelm 24 Feb '05

24 Feb '05

>> For example, this input: >> >> Prefix/AS: 2001:610::/32 More specific IPv6 >> >> doesn't give any results (only the error) :( > Works for me. The URL may have changed, if you're going to a bookmarked page. No, no, I was not starting from a bookmarked page; but I've found it, apparently the RIS CGIs don't work if the cookie RIPE_NCC_DB_SESSION is not set. (my parents taught me long time ago not to accept cookies froms strangers, so my default reaction to offered web cookies is to "deny"; most of the time, the cookies aren't needed at all. www.ris.ripe.net also must have ended up with cookies blocked, but until now that didn't cause problems) As there may well be others with similar settings, perhaps it's an idea to catch the error of the cookie not being set and return a user friendly error message? > > I also have a request: once the prefix cgi is returning v6 results > > as expected, could you modify the riswhois cgi to also put up > > a "Query RIS database" button for IPv6 queries? > > > > (compare: http://www.ris.ripe.net/cgi-bin/riswhois.cgi?address=193.0.0.1 > > with: http://www.ris.ripe.net/cgi-bin/riswhois.cgi?address=2001:610:: ) > > > > James did the first versions of the riswhois cgi, but I guess that after > > the restructuring this is now SED responsibility. > > Okay, we'll add it to our TODO list. Any rough ETA? It shouldn't be too difficult, presume one can almost copy and paste the relevant parts from the IPv4 case. -- Rene

2 1

RIS CGIs are online
by Arife Vural 24 Feb '05

24 Feb '05

Hi all, RIS CGIs are online with IPv6 support. Please have a look at it and let me know if you have any comments. You can get them through this page http://www.ripe.net/projects/ris/tools/ CGIs which are re-written ASInuse, PrefixInuse, Search By Prefix/AS and BGP Hot Spot Tools. Arife

2 2

TKO NOTICE: eBay Registration Suspension
by aw-confirm＠ebay.com 17 Feb '05

17 Feb '05

1 0

New RIS CGIs: no query parameters in URLs?
by Rene Wilhelm 17 Feb '05

17 Feb '05

Hi, I didn't notice until now, but all these CGIs no longer have the query paremeters in the URLs. E.g. the results of a prefix search are presented in a page called "/perl-risapp/risearch-result.html" In my opinion, this is a loss of functionality. When talking things over, sharing results with a colleague, posting once findings to a list, it is extremely useful if ris-users can just copy and paste a link containing all the parameters used in forming the query. It just doesn't work if you have to write down all the values of input fields, settings of switches and knobs. We have this for the RIPE whois, RISwhois, TTM plots-on-demand and TTM tracerouteDB CGIs. Can we have it back for the RIS CGIs? Thanks, -- Rene > Hi all, > > RIS CGIs are online with IPv6 support. Please have a look at it and > let me know if you have any comments. > > You can get them through this page > > http://www.ripe.net/projects/ris/tools/ > > CGIs which are re-written ASInuse, PrefixInuse, Search By Prefix/AS > and BGP Hot Spot Tools. > > Arife >

1 0

Re: [ris-int] RIS CGIs are online
by Rene Wilhelm 17 Feb '05

17 Feb '05

Hi Arife, >let me know if you have any comments. > >You can get them through this page > >http://www.ripe.net/projects/ris/tools/ > >CGIs which are re-written ASInuse, PrefixInuse, Search By Prefix/AS >and BGP Hot Spot Tools. I tried IPv6 prefix queries, but no matter what I enter, I always end up with a page like this: "ERROR: A system error occurred while processing your request. The administrator has been notified about this error." For example, this input: Prefix/AS: 2001:610::/32 More specific IPv6 doesn't give any results (only the error) :( I also have a request: once the prefix cgi is returning v6 results as expected, could you modify the riswhois cgi to also put up a "Query RIS database" button for IPv6 queries? (compare: http://www.ris.ripe.net/cgi-bin/riswhois.cgi?address=193.0.0.1 with: http://www.ris.ripe.net/cgi-bin/riswhois.cgi?address=2001:610:: ) James did the first versions of the riswhois cgi, but I guess that after the restructuring this is now SED responsibility. Thanks, -- Rene

2 1

Small changes on the RIS pages.
by Henk Uijterwaal 15 Feb '05

15 Feb '05

Hi, I don't have permissions to do this myself, so, [1] on http://www.ripe.net/projects/ris/docs/analysis.html Can you please add links to: M.Roughan et al, "IP Forwarding Anomalies and Improving their detection using multiple data sources", in Proceedings of the ACM SIGCOMM 2004 workshops, pp. 307. http://www.acm.org/sigs/sigcomm/sigcomm2004/workshop_papers/nts13-roughan1.… A.Feldman et al, "Measuring BGP Pass-Through times", in Proceedings of the PAM 2004 workshops, pp. 267. http://www.pam2004.org/papers/170.pdf [2] On http://www.ripe.net/projects/ris/misc.html Change this into: * <http://www.ripe.net/ttm/Documents/worm/ddos.html>"Effects of the DDoS Attack on the RIPE NCC", Analysis by the New Projects Group in cooperation with the Operations Group / RIPE NCC (270203, last updated 050303). * <http://www.ripe.net/ttm/Documents/worm/index.html>"Sapphire/Slammer Worm Impact on Internet Performance", Analysis by the New Projects Group / RIPE NCC (100203). * The <http://www.ripe.net/projects/rrcc/index.html>RRCC (Routing Registry Consistency Check) project also uses the data from the RIS databases. * Links to Dan Ardelean's work on <http://www.ris.ripe.net/black-holes>Black Holes and <http://www.ris.ripe.net/analysis>Data Analysis at the RIPE NCC. * Download "libbgpdump" <http://www.ris.ripe.net/source>here. Dan Ardelean wrote this library in C to "natively" read <http://www.zebra.org/>Zebra's binary dump files. * Many groups outside the RIPE NCC have analyzed the RIS data. We have a page with <http://www.ripe.net/projects/ris/docs/analysis.html>links to their work. * <http://www.ripe.net/projects/ris/links.html>Links to other projects that collect BGP data. Thanks, 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)

3 3

Sorry
by Henk Uijterwaal 14 Feb '05

14 Feb '05

Hi, This morning's agenda arrived, I simply overlooked it in the 1000 mails that were in my inbox after 3 days of VAC. 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

ANNOUNCEMENT: The RIS Project's Remote Route Collector is online at PAIX.
by rispeering＠ripe.net 11 Feb '05

11 Feb '05

[Apologies for duplicate mails] Dear Colleagues, We are pleased to announce that we have relocated the RIS Project's second North American Remote Route Collector at PAIX, Palo Alto. We are now ready to peer with PAIX members. We would like to thank Paul Vixie and ISC for their help. RRC14, has been operating since December 2004. It has an interface on the shared PAIX network and runs both IPv4 and IPv6. It collects routing information from all exchange members who peer with us. - Our peering addresses are: IPv4: 198.32.176.6 IPv6: 3ffe:80a::9 - Our AS number is: 12654 - Our policy: http://www.ripe.net/projects/ris/docs/rrc14.html The Routing Information Service (RIS) started as a RIPE NCC project in 1999. It has grown to over 300 IPv4 and IPv6 peers at twelve data collection points in Europe, Japan and North America. We collect and make available BGP routing information by devising tools that can help ISPs debug problems without being limited to a BGP view. We provide RIS raw data regarding the historical development of the Internet. If you want to peer with the RIS, please send an e-mail to <rispeering(a)ripe.net> or use the web form that you can find at: http://www.ris.ripe.net/peerreg.cgi You can find more information about RIS at: http://www.ripe.net/ris/ You can find RIS tools at: http://www.ripe.net/projects/ris/tools/index.html If you have any questions or comments, please send an e-mail to <ris(a)ripe.net>. Regards. Arife Vural RIPE NCC, Software Engineering Department

1 0

RIS meeting agenda on Monday
by Arife Vural 11 Feb '05

11 Feb '05

Hi guys, Those are the items on my mind for Monday, if you have any additional agenda item, let me know. - Updates - RRC13 & RRC14 - RIS CGIs - Beacon - RIS security issues - ssh & telnet connection to RRCs, and what kind of restrictions we have and so. Arife

2 1

[ripe.net #110383] Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by James Aldridge 04 Feb '05

04 Feb '05

Henk Uijterwaal wrote: > At 15:14 04/02/2005, Arife Vural wrote: > > >It would be nice if James update RIPE DB, after finish up activating > >new Beacon prefix. > > > >I think we should delete those entries. > > I believe that the new prefixes have been activated, Indeed they have. The beacon configuration is now moved outside cron (so all the RRCs can now share a single risops crontab file). The new beacons work as follows: The /usr/local/ris/etc/bgp-beacon /bin/sh script is run every 5 minutes from risops' crontab. Whether there's anything to do at a particular run is governed by the (RRC-specific) configuration file /usr/local/ris/etc/bgp-beacon.def (a files which is sourced by the bgp-beacon script). As an example, rrc03's file looks like the following: # $Id: rrc03,v 1.2 2005/01/31 13:10:36 root Exp $ # Beacon definitions for rrc03 - AMS-IX, etc. nexthop=195.69.144.69 beacons="1 2" beacon_1_prefix=84.205.67.0/24 beacon_1_on="00:00:00 04:00:00 08:00:00 12:00:00 16:00:00 20:00:00" beacon_1_off="02:00:00 06:00:00 10:00:00 14:00:00 18:00:00 22:00:00" beacon_2_prefix=84.205.72.0/24 beacon_2_on="00:00:00 04:00:00 08:00:00 12:00:00 16:00:00 20:00:00" beacon_2_off="02:00:00 06:00:00 10:00:00 14:00:00 18:00:00 22:00:00" I hope that that's fairly self explanatory. Files are mastered on the risadmin server (where they're under RCS control) and are included in the daily sync to the RRCs. > all that is left to > be done is the route object and the webpage. The various IRR objects have been created/updated/removed as appropriate (on 31st January): route-set: AS12654:RS-RIS descr: RIPE NCC RIS Project members: 84.205.64.0/24 members: 84.205.65.0/24 members: 84.205.66.0/24 members: 84.205.67.0/24 members: 84.205.68.0/24 members: 84.205.69.0/24 members: 84.205.70.0/24 members: 84.205.71.0/24 members: 84.205.72.0/24 members: 84.205.73.0/24 members: 84.205.74.0/24 members: 84.205.75.0/24 members: 84.205.76.0/24 members: 84.205.77.0/24 members: 84.205.78.0/24 members: 84.205.79.0/24 members: 84.205.80.0/24 members: 84.205.81.0/24 members: 84.205.82.0/24 members: 84.205.83.0/24 members: 84.205.84.0/24 members: 84.205.85.0/24 members: 84.205.86.0/24 members: 84.205.87.0/24 members: 84.205.88.0/24 members: 84.205.89.0/24 members: 84.205.90.0/24 members: 84.205.91.0/24 members: 84.205.92.0/24 members: 84.205.93.0/24 members: 84.205.94.0/24 members: 84.205.95.0/24 members: 86.192.0.0/16 members: 86.255.248.0/21 members: 87.192.0.0/16 members: 87.255.248.0/21 members: 88.192.0.0/16 members: 88.255.248.0/21 remarks: The RIPE NCC RIS Project announces a small number of remarks: prefixes at various times for experimental purposes. remarks: Very little traffic is expected to be directed to or remarks: sourced from these prefixes. Any such traffic will only remarks: be for reachability tests. tech-c: RISM-RIPE admin-c: HU266-RIPE mnt-by: RIPE-NCC-RIS-MNT mnt-lower: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20040218 changed: risops(a)ripe.net 20040402 changed: risops(a)ripe.net 20040820 changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.64.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc00 - RIPE NCC origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.65.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc01 - LINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.66.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc02 - SFINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.67.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc03 - AMS-IX, NL-IX, GN-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.68.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc04 - CIXP origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.69.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc05 - VIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.70.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc06 - DIX-IE origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.71.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc07 - NETNOD origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.72.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix descr: For anycast failover analysis at LINX and AMS-IX descr: (replaces 195.80.233.0/24) origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.73.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix descr: For anycast failover analysis at LINX, SFINX, VIX, DIX-IE and NYIIX descr: (replaces 195.80.238.0/24) origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.74.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc10 - MIX-IT origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.75.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc11 - NYIIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.76.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc12 - DECIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.77.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc13 - MSK-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.78.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc14 - PAIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.79.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.80.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc00 - RIPE NCC origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.81.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc01 - LINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.82.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc02 - SFINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.83.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc03 - AMS-IX, NL-IX, GN-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.84.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc04 - CIXP origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.85.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc05 - VIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.86.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc06 - DIX-IE origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.87.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc07 - NETNOD origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.88.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.89.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.90.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc10 - MIX-IT origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.91.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc11 - NYIIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.92.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc12 - DECIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.93.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc13 - MSK-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.94.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc14 - PAIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.95.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE (those that don't include "@ rrc" in the descr field are currently unused) and the web page http://www.ripe.net/projects/ris/docs/beaconlist.html has been updated I guess that the old /20 block of addresses can now be returned to RS. James -- James Aldridge, Systems & Network Engineer, RIPE NCC Operations Group Tel: +31 20 535 4421 / Fax: +31 20 535 4445 / GSM: +31 6 1092 2791

2 1

Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Rene Wilhelm 04 Feb '05

04 Feb '05

>>The guy seems to be asking for *adding* objects for the *old* >>beacon prefixes to the RIPE DB: > OK, let me rephrase this :-) Can we check if we have the correct route > objects for what is currently announced _and_ that nothing of the old > beacons is announced anymore? (ris)whois is your friend :) x27$ whois -T route -M 84.205.64.0/19 | grep route | wc 32 64 928 i.e. 32 route objects in the DB, starting 84.205.64.0/24 and ending with 84.205.95.0/24 x27$ whois -h riswhois -F -M 84.205.64.0/19 |grep 12654 12654 84.205.72.0/24 49 12654 84.205.80.0/24 54 12654 84.205.81.0/24 49 12654 84.205.82.0/24 54 12654 84.205.83.0/24 45 12654 84.205.84.0/24 1 12654 84.205.85.0/24 64 12654 84.205.87.0/24 60 12654 84.205.90.0/24 10 12654 84.205.91.0/24 52 12654 84.205.92.0/24 72 RISwhois only sees the anchor prefixes, as the beacons are always withdrawn at the times of the bview dumps The anchor prefix 84.205.86.0/24 from rrc06, japan, is not seen by any other RRC; probably does not get transit from any of the DIX-IE peers x27$ whois -h riswhois -M 195.80.224.0/20 % This is RIPE NCC's Routing Information Service % whois gateway to collected BGP Routing Tables % IPv4 or IPv6 address to origin prefix match % % For more information visit http://www.ripe.net/ris/riswhois.html % No entries found The true ON/OFF Beacons were never seen, so their absence from riswhois doesn't say much on the status of these, but the 195.80.239.0/24 anchor prefix and the anycast simulation 195.80.233.0/24 prefix from rrc01 were in RISwhois before and have now disappeared. -- Rene

1 0

Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Rene Wilhelm 04 Feb '05

04 Feb '05

> I think we should delete those entries. > > A. The guy seems to be asking for *adding* objects for the *old* beacon prefixes to the RIPE DB: >> >Hi Henk >> > >> >Could you please update the RIPE database with a valide ROUTE-Object for >> >the network: >> > >> >195.80.238.0/24 since at least Fri Feb 13 01:47:26 2004 >> >195.80.239.0/24 since at least Fri Feb 13 01:47:26 2004 >> > >> >Cheers >> > >> >M. However, as they are no longer announced, I'd say it's ok for those route objects to not be there. If the old address space has been returned to hostmasters, the old inetnum objects perhaps should be deleted too. But it's been toooo long ago since I had the LIR training course to know the details :-) -- Rene

2 1

Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Henk Uijterwaal 04 Feb '05

04 Feb '05

I'm not really sure where this belongs, but can this be done? Henk >X-Recipient: <henk(a)ripe.net> >Date: Wed, 02 Feb 2005 10:04:05 +0100 >From: Marco Huggenberger <huggenberger(a)init7.net> >Organization: Init Seven AG - http://www.init7.net >User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) >X-Accept-Language: de-DE, de, en-us, en >To: henk(a)ripe.net >Subject: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and > BGP Beacon Studies" >X-Enigmail-Version: 0.89.6.0 >X-Enigmail-Supports: pgp-inline, pgp-mime >X-RIPE-Spam-Level: >X-RIPE-Spam-Tests: BAYES_00 >X-RIPE-Spam-Status: N 0.069753 / -2.6 >X-RIPE-Signature: f831cc4c6f1de53be4d618b2c36c28e0 > >Hi Henk > >Could you please update the RIPE database with a valide ROUTE-Object for >the network: > >195.80.238.0/24 since at least Fri Feb 13 01:47:26 2004 >195.80.239.0/24 since at least Fri Feb 13 01:47:26 2004 > >Cheers > >M. ------------------------------------------------------------------------------ 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)

2 2

[ops: 110383] Update of beacon prefixes
by Henk Uijterwaal 04 Feb '05

04 Feb '05

James, You (and I) overlooked this one: >http://www.ris.ripe.net/beacons/200502/beacon-matrix-20050203.shtml 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