- mat-wg - mailman.ripe.net

New on RIPE Labs: A Tale of BGP Collectors and Customer Cones
by Mirjam Kuehne 05 Oct '15

05 Oct '15

Dear colleagues, When operators and researchers use data from BGP route collectors such as RIS and Route Views, it's not easy to tell if a path announced to a collector is an ISP's customer cone, an internal route, or one learned from peering or transit. In this new RIPE Labs post we look at what information we can currently get from BGP communities in RIS: https://labs.ripe.net/Members/emileaben/a-tale-of-bgp-collectors-and-custom… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Iran and K-root - The Rest of the Story
by Mirjam Kuehne 30 Sep '15

30 Sep '15

Dear colleagues, We took a look at the effect of the K-root node in Iran in order to augment the picture provided by Dyn Research in a recent blog post. Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/iran-and-k-root-the-rest-of-the-sto… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Real-time BGP Visualisation with BGPlay
by Mirjam Kuehne 30 Sep '15

30 Sep '15

Dear colleagues: Please find this new article on RIPE Labs describing a new feature in BGPlay - real-time BGP visualisation (submitted by Massimo Candela): https://labs.ripe.net/Members/massimo_candela/real-time-bgp-visualisation-w… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Join RIPE Atlas Hackathon - 14-15 November - Bucharest
by Vesna Manojlovic 29 Sep '15

29 Sep '15

Calling all software developers, designers and network operators! The next RIPE Atlas hackathon takes place 14-15 November in Bucharest, right before RIPE 71. We're looking for creative thinkers to help us find new ways to use RIPE Atlas data to monitor networks and troubleshoot issues as well as ways to improve the existing toolset. Is this you? Then we want to hear from you! ----------------------- How to Apply ----------------------- The application form is online at: https://atlas.ripe.net/hackathon/tools-2015/#!application-form *The deadline to apply is Tuesday, 6 October* Successful applicants will: - Work alongside RIPE Atlas engineers - Get to know others in your field - Contribute to the shared code - Exchange knowledge and experience All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. ---------------------- Hackathon details --------------------- Date: 14-15 November 2015 Time: Saturday 09:00-19:00, Sunday 09:00-21:00 (including party) Location: JW Marriott Bucharest Grand Hotel, Bucharest, Romania Applicants will hear back from the jury on 12 October so that travel arrangements can be made on time. Find out more on RIPE Labs: https://labs.ripe.net/Members/becha/join-the-ripe-atlas-tools-hackathon -------------------- Call for Sponsors ------------------- We are still looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly – thank you! I look forward to seeing you there! Regards, Vesna

1 0

Requested Feature: RIS Prefixes
by Christian Teuschel 29 Sep '15

29 Sep '15

Dear colleagues, In May this year there was a feature request from Job Snijders to have RIPEstat provide transitted prefixes for an ASN. See [0] for more details. Over the summer we worked on this feature. As a result we now have a new data call in the RIPEstat API called RIS Prefixes. This data call reports the prefixes for a given ASN that are seen on the AS paths between the origin and RIS. You can see an example using the RIPE NCC's ASN (AS3333): http://stat.ripe.net/data/ris-prefixes/data.json?resource=AS3333&list_prefi… The data call supports the additional parameter of tailoring the output to your needs. See [1] for more details. The data is based on data collected by the RIPE NCC's RIS network (see [2]), and the output therefore reflects the perspective of RIS. Important to interpreting the data correctly is the definition of a transit: for this dataset, a transit is defined as any ASN appearing on the AS path for a route that is not the origin. We understand that the term “transit" can also imply the business relationship between networks, which would provide a list of prefixes that could be referred to as prefixes in the customer cone of a network. At this point in time, the customer cone itself cannot be extracted from the RIS data in a way that is exact and reliable. The RIS Prefixes data call provides a SUPERSET of prefixes considered the customer cone. During the coming months we will further investigate the possibilities of determining customer prefixes with RIS/RIPEstat. Meanwhile, we welcome suggestions from the community for approaches to solve this issue. We look forward to hearing from you, Christian Teuschel & Romeo Zwart RIPE NCC [0] https://www.ripe.net/ripe/mail/archives/mat-wg/2015-May/000588.html [1] https://stat.ripe.net/docs/data_api#RISPrefixes [2] https://www.ripe.net/ris

1 0

Save the date: RIPE Atlas Hackathon - 14-15 November - Bucharest
by Vesna Manojlovic 25 Sep '15

25 Sep '15

Dear all, It’s official: we will hold a new RIPE Atlas hackathon on the weekend before RIPE 71 in Bucharest. Join us, along with network operators and software developers from the Internet community, to work on RIPE Atlas tools. You'll have the chance to work alongside RIPE Atlas developers, meet others in your field, and exchange knowledge and experience. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. Details: Date: 14-15 November 2015 Time: Saturday 09:00-19:00, Sunday 09:00-21:00 (including party) Location: JW Marriott Bucharest Grand Hotel, Bucharest, Romania We are looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly – thank you! Finally, stay tuned - this is a pre-announcement. We will publish more details, along with the application form, early next week. I look forward to seeing you there! Regards, Vesna

1 0

New on RIPE Labs: Time Travel with RIPE Atlas
by Mirjam Kuehne 25 Sep '15

25 Sep '15

Dear colleagues, Please find another new RIPE Atlas related article on RIPE Labs: RIPE Atlas users can now travel back in time to access all of the historical data collected by RIPE Atlas. https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-time-travel-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Looking at France-IX with RIPE Atlas and RIS
by Mirjam Kuehne 24 Sep '15

24 Sep '15

Dear colleagues, Please find a new article on RIPE Labs describing our recent collaborations with France-IX on collecting data plane and control plane Internet data with RIPE Atlas and the RIPE NCC's Routing Information Service (RIS): https://labs.ripe.net/Members/emileaben/looking-at-france-ix-with-ripe-atla… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: New RIPE Atlas Tool: LatencyMON
by Mirjam Kuehne 23 Sep '15

23 Sep '15

Dear colleagues, LatencyMON is a new RIPE Atlas web application that you can use to easily visualise and compare multiple latency trends collected by groups of RIPE Atlas probes. Please find more details on RIPE Labs: https://labs.ripe.net/Members/massimo_candela/new-ripe-atlas-tool-latencymon Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Mapping the Internet in Serbia
by Mirjam Kuehne 23 Sep '15

23 Sep '15

Dear colleagues, Please find a new article on RIPE Labs. Andrej Petrovksi describes how mapping and visualising the Internet in Serbia informed the law-making process: https://labs.ripe.net/Members/andrej_petrovski/mapping-the-internet-infrast… Kind regards, Mirjam Kuehne RIPE NCC

2 1

New on RIPE Labs: Checking your Internet Connectivity with RIPE Atlas Anchors
by Mirjam Kuehne 17 Sep '15

17 Sep '15

Hi, Please find a new article on RIPE Labs, submitted by Stephane Bortzmeyer: Checking your Internet Connectivity with RIPE Atlas Anchors https://labs.ripe.net/Members/stephane_bortzmeyer/checking-your-internet-co… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Eleven new RIPE Atlas anchors have joined the community
by Michela Galante 11 Sep '15

11 Sep '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 143: * mv-mle-as7642 hosted by DHIRAAGU in Male, Maldive, and sponsored by APNIC. * bd-dac-as24122 hosted by BDIX in Dhaka, Bangladesh, and sponsored by APNIC. * sg-sin-as18106 hosted by ViewQwest in Singapore, Singapore. * Three anchors hosted by Aflilias in United States: us-qas-as393246 in Ashburn (Virginia), us-lax-as63403 in Los Angeles (California), and us-mia-as33280 in Miami (Florida) * Three anchors hosted by Booking.com: de-fra-as43996 in Frankfurt am Main (Germany), us-abn-as43996 in Ashburn (Virginia), United States, and hk-hkg-as43996 in Hong Kong. * ca-van-as852 hosted by Telus in Vancouver, Canada. * nl-haa-as60781 hosted by Leaseweb Network in Haarlem, The Netherlands. 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 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, Michela Galante Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: Enabling Data Compression in RIPE Atlas
by Vesna Manojlovic 01 Sep '15

01 Sep '15

Dear colleagues, We’d like to enable gzip compression on all of RIPE Atlas' measurement API calls — but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements — including the small number of measurements not marked as “public”. We believe the drawbacks are negligible, but we’re looking for community support. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/daniel_quinn_39/enabling-data-compression-in-… Regards, Vesna Manojlovic

2 1

New on RIPE Labs: The Internet in North Korea - Hanging by a Single Thread?
by Mirjam Kuehne 26 Aug '15

26 Aug '15

Dear colleagues, Please find a new article on RIPE Labs: The Internet in North Korea - Hanging by a Single Thread? We used RIPE Atlas and RIPEstat to investigate North Korea's Internet connectivity in light of recent outages and discuss the fragile nature of its setup. https://labs.ripe.net/Members/emileaben/the-internet-in-north-korea-hanging… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Network Neutrality - Latest on Regulation
by Gordon Lennox 14 Jul '15

14 Jul '15

http://www.consilium.europa.eu/en/press/press-releases/2015/07/08-roaming-c… There is a link to the regulation as PDF. "How will this become a law? The agreed text will undergo technical finalisation. It then needs to be formally approved by the Council and the Parliament. The Council is expected to formally adopt it in the autumn 2015. This does not need to take place in the Telecom Council: any Council configuration has the power to adopt the legal act. The regulation will enter into force 20 days after its publication in the EU Official Journal.”

2 3

New on RIPE Labs: Visualisation of a New Node in LACTLD Anycast Service
by Mirjam Kuehne 10 Jul '15

10 Jul '15

Dear colleagues, Please read on RIPE Labs how RIPE Atlas was used to measure improvements to the LACTLD infrastructure (by Hugo Salgado): https://labs.ripe.net/Members/hugo_salgado/visualisation-of-a-new-node-in-l… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Mirjam Kuehne 02 Jul '15

02 Jul '15

Dear colleagues, In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see what eyeball networks are missing out on RIPE Atlas probes: https://labs.ripe.net/Members/emileaben/improving-ripe-atlas-coverage-what-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Probe and measurement archives vs. the APIs
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear All, We've observed recently that some users are using scripts to "crawl" through all the metadata provided by the probe and measurement APIs. This means that some people out there download basically the entire probe and/or measurement meta data set the system provides. As you can imagine, this is highly inefficient and keeps our servers busy. We believe that there could be better solutions. We have been providing the downloadable archive for probe metadata for some time now, and recently we've added the measurement metadata too. You can now reach these at http://ftp.ripe.net/ripe/atlas/ This way one can even get complete sets of metadata as far back as January 2015 for measurement specifications and March 2014 for probe data. Given the existence of these archives, we will apply a sane limit on how much metadata can be reached via the APIs. In practice this means that the API will not allow fetching results beyond, say, 10.000 (i.e. 500 pages of 20) entries. This is after the application of filters, so for example with no filters at all you could still access metadata of the 10k newest measurements, while if you filter for DNS measurements only, you could get the 10k newest of those, and so on. We believe this keeps the metadata API useful for the majority of the users, while the existence of the archive serves the remaining cases. Our plan is to make this change around the end of July. Regards, Robert Kisteleki

1 0

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

Eleven new RIPE Atlas anchors have joined the community
by Michela Galante 24 Jun '15

24 Jun '15

Dear colleagues, More and more organisations from all over the world are hosting RIPE Atlas anchors: in the last 6 weeks, on average, 2 anchors were 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 132: * us-els-as40528 located in El Segundo, California and us-rtv-as16876 located in Reston, Virginia, hosted by ICANN. * nl-dro-as51430, hosted by ALTUSHOST B.V. in Dronten, The Netherlands. * us-pou-as6124 hosted by Marist College in Poughkeepsie, New York. * pk-isb-as7590 hosted by COMSATS Internet Services in Islamabad, Pakistan, and sponsored by APNIC. * ph-qzt-as9821 hosted by ASTI in Quezon City, Philippines, and sponsored by APNIC. * nl-hrd-as34612 hosted by Matrix DATA in Harderwijk, The Netherlands. * at-szg-as5404 hosted by conova communications GmbH in Salzburg, Austria. * fr-ysd-as201958 hosted by ADP in Saint-Denis, France. * de-fra-as49024 hosted by FHE3 GmbH in Frankfurt am Main, Germany. * de-ham-as201709 hosted by Netzwerge Hamburg eK in Hamburg, Germany. 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, Michela Galante Measurements Community Building RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 18 Jun '15

18 Jun '15

Dear colleagues, We are pleased to announce the dates for the RIPE NCC Webinars for the coming quarter. These interactive on-line learning sessions take about one hour, and give you the opportunity to learn and interact with our trainers without leaving your desk. In the next 3 months you can participate in the following Webinars: - Advanced RIPE Atlas Usage (NEW!) - Introduction to the RIPE Database - RIPE Database - Advanced Topics - IPv6 in the RIPE Database - IPv6 Addressing Plan - Webinar for New LIRs - Resource Certification (RPKI) Register now at https://www.ripe.net/support/training/learn-online/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have any questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Service

1 0

New on RIPE Labs: HTTP Measurements with RIPE Atlas
by Mirjam Kuehne 16 Jun '15

16 Jun '15

Dear colleagues, After a discussion with the community about HTTP measurements, we'll start implementing this as a publicly available measurement type. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas Kind regards, Mirjam Kuehne RIPE NCC

1 0

problems with RIPE Atlas website
by Romeo Zwart 08 Jun '15

08 Jun '15

dear colleagues, We are currently investigating issues with the RIPE Atlas service that cause the RIPE Atlas web pages to fail. We will update you of any further developments through https://www.ripe.net/support/service-announcements/service-and-security-ann…. We apologise for the inconvenience caused. Kind regards, Romeo Zwart RIPE NCC

1 0

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