May 2015 - mat-wg - mailman.ripe.net

Re: [mat-wg] feature request: have stat report on transitted prefixes
by Christian Teuschel 30 Jun '15

30 Jun '15

Dear colleagues, I wanted to follow-up on Job's feature request, about RIPEstat also displaying prefixes transited by an ASN, since several of you also said you would find this feature useful. Supporting this feature will require some work on RIPEstat's front-end as well as on the back-end (our Hadoop storage platform). Implementing this for all available historic RIS data would have a large impact on our storage capacity. However, we will be able to implement this feature for a sliding window of 30 days, as you suggested. So RIPEstat will be able to show the prefixes for which an ASN provided transit during the previous 30 days. At the moment I don't have a concrete delivery date for this feature, but we will merge the necessary development work into our work plan and let you know before the end of June when we expect to be able to support this feature in RIPEstat. We will make sure it is implemented before RIPE 71 in November. Please let me know if you have any further feedback or questions. Regards, Christian Teuschel & Romeo Zwart RIPE NCC On Mon, May 11, 2015 at 01:15:09PM +0200, Job Snijders wrote: > Hi MAT, > > I'd really like the stat team to implement a tool that tells me > what prefixes are originated AND transitted by a given ASN. The > use-case is that I (before setting up BGP sessions) can make an > automated assessment what amount of prefixes the network will > announce, which prefixes they are likely to announce and if that > matches up with the prefix-filter I would apply on that bgp > session. > > A second use case is that when I want to connect a peer or customer > to which I have never been connected before, I have no idea what > they will announce to me. Should I want to make predictions for > traffic engineering purposes, it would be beneficial if I could > fetch a list of prefixes this peer is likely to announce to other > peers from the stat system. > > A sliding window of say 30 days would be perfect, for my purposes I > do not need the tool to offer data going back to the beginning of > time. > > Do others agree that the above would be a useful feature? > > Kind regards, > > Job >

2 1

Re: [mat-wg] Geoloc API covered_percentage
by Christian Teuschel 28 May '15

28 May '15

Dear Noriyuki, The "covered percentage" value shows how much of the referenced IP space is known in the geoip database (MaxMind's GeoLite City, [1]). This referenced IP space depends on the look-up type: - For a prefix look-up it is the given prefix itself. - For an ASN look-up it is related to the prefixes this ASN originates. A recent update to the documentation makes it more clear, https://stat.ripe.net/docs/data_api#Geoloc. Best regards, Christian [1] http://dev.maxmind.com/geoip/legacy/geolite/ On 19/05/15 12:00, Arai Noriyuki wrote: > > hi all, > > i am trying to do something with the geoloc API and i found there is > an item named "covered percentage" for every location. what does it > mean? > > (i once thought it is the percentage of the IP addresses in that > location among the whole address space of the object resource. but it > sounds i was wrong. :P) > > thanks and regards, > noriyuki >

1 0

Geoloc API covered_percentage
by 荒井則之（ネットワーク本部）- Arai Noriy uki - 19 May '15

19 May '15

hi all, i am trying to do something with the geoloc API and i found there is an item named "covered percentage" for every location. what does it mean? (i once thought it is the percentage of the IP addresses in that location among the whole address space of the object resource. but it sounds i was wrong. :P) thanks and regards, noriyuki

1 0

Eleven new RIPE Atlas anchors joined the community
by Vesna Manojlovic 16 May '15

16 May '15

Dear colleagues, More and more organisations from all over the world are hosting RIPE Atlas anchors - on average one anchor is activated every week! We are proud to announce that eleven new RIPE Atlas anchors have been activated since our previous announcement, bringing the total to 121: * np-ktm-as45170, hosted by the Internet Exchange Nepal (NPIX) in Kathmandu, Nepal, and sponsored by APNIC. * ch-gtg-as20612, by SwissIX Internet Exchange in Glattbrugg,Switzerland * de-ber-as20647, hosted by CarrierColo / IPB GmbH in Berlin, Germany * fr-par-as57734, hosted by FranceIX in Paris, France. * fi-yyv-as30798, hosted by TNNet Oy Ltd in Jyvaskyla, Finland. * rs-ini-as13303, hosted by University of Niš in Niš, Serbia * at-klu-as42473, by Anexia Internetdienstleistungs Gmbh in Klagenfurt, Austria * nz-lyj-as17746, by NZ Registry Services in Aukland, New Zealand * us-sjc-as22300, hosted by Wikia in San Jose (USA) * de-muc-as8767, by M-net Telekommunikations GmbH in Munich, Germany * es-leg-as766, by University Carlos III of Madrid, Leganes, Spain. The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are the logos and links to hosting companies: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from individuals and organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net Regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: AMS-IX Outage during RIPE 70 as Seen with RIPE Atlas
by Mirjam Kuehne 14 May '15

14 May '15

Dear colleagues, Please find this new article on RIPE Labs including some visualisations of yesterday's AMS-IX network outage: https://labs.ripe.net/Members/kistel/the-ams-ix-outage-as-seen-with-ripe-at… Kind regards, Mirjam Kuehne RIPE NCCC

1 0

feature request: have stat report on transitted prefixes
by Job Snijders 14 May '15

14 May '15

Hi MAT, I'd really like the stat team to implement a tool that tells me what prefixes are originated AND transitted by a given ASN. The use-case is that I (before setting up BGP sessions) can make an automated assessment what amount of prefixes the network will announce, which prefixes they are likely to announce and if that matches up with the prefix-filter I would apply on that bgp session. A second use case is that when I want to connect a peer or customer to which I have never been connected before, I have no idea what they will announce to me. Should I want to make predictions for traffic engineering purposes, it would be beneficial if I could fetch a list of prefixes this peer is likely to announce to other peers from the stat system. A sliding window of say 30 days would be perfect, for my purposes I do not need the tool to offer data going back to the beginning of time. Do others agree that the above would be a useful feature? Kind regards, Job

4 3

New on RIPE Labs: On the Diversity of Interdomain Routing in Africa
by Mirjam Kuehne 08 May '15

08 May '15

Dear colleagues, In this new article on RIPE Labs, the authors looked into measuring Interdomain Routing in Africa using the RIPE Atlas infrastructure. This resulted in a paper published at the Passive and Active Measurement (PAM) conference. Here some highlights of this research are presented: https://labs.ripe.net/Members/fanou_roderick/on-the-diversity-of-interdomai… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Call for MAT CoChair candidates
by Christian Kaufmann 08 May '15

08 May '15

Dear MAT WG, now as our new process is in place: >> 1. A call for interested parties is made on the WG mailing list at three yearly intervals, or as needed >> 2. Interested parties have 2 weeks to make their interest known via the mailing list >> 3. The MAT-WG chairs issue a call for discussion as per normal. WG members express their approval or otherwise of the presented candidates. >> 4. After two weeks the chairs declare consensus as they would do for a policy proposal I want to issue a call for a new CoChair which supports me in running and preparing the Meeting. As a remainder our Charter and Website can be found at: https://www.ripe.net/ripe/groups/wg/mat and the Job description at: https://www.ripe.net/ripe/docs/ripe-542 Please feel free to nominate yourself if you are interested or shanghai others ( with their approval:-)) till the 21st April. Thx a lot and best regards, Christian Kaufmann MAT WG (Co)-Chair

6 9