- mat-wg - mailman.ripe.net

Two weeks left to join RIPE NCC IXP Tools Hackathon, 22-23 October, Madrid
by Vesna Manojlovic 02 Sep '16

02 Sep '16

Dear colleagues, together with Euro-IX, Comcast and ISOC, the RIPE NCC is hosting a hackathon focused on developing tools for Internet Exchange Points (IXPs), in the weekend before RIPE73, in Madrid: https://atlas.ripe.net/hackathon/ixp-tools/#!the-event While the past three hackathons have specifically focused on RIPE Atlas, this event will include other data sources as well, such as: the Routing Information Service (RIS) and the PeeringDB. We will work on existing software tools that deal with IXP-data-integration in order to solve some of the challenges that operators have when making peering decisions, and to illustrate the impact of IXPs on the Internet routing and connectivity. We are looking for designers and developers, students and network operators, and of course colleagues from IXPs, to work together on hacking the new & old toolsets and visualizations! 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. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://atlas.ripe.net/hackathon/ixp-tools/#!application-form *The application deadline is 15 September* Thanks to our generous sponsors, there is a (limited) travel funding available for certain categories of applicants. Please find more information in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-ixp-tool… We look forward to seeing you there! Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

New on RIPE Labs: Another Look at RIPE Atlas Probe Lifetimes
by Mirjam Kuehne 25 Aug '16

25 Aug '16

Dear colleagues, We took another, more detailed look at probe lifetimes and the dynamics of probes connecting and disconnecting from the RIPE Atlas infrastructure to try to understand how to keep the network growing in the long term. https://labs.ripe.net/Members/wilhelm/another-look-at-ripe-atlas-probe-life… Kind regards, Mirjam Kuehne RIPE NCC

1 0

2nd call for presentations RIPE 73
by Benno Overeinder 22 Aug '16

22 Aug '16

Dear colleagues, Please note the approaching deadline of 28 August 2016 for RIPE 73 plenary programme submissions. You can find the CFP for RIPE 73 below or at https://ripe73.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 73 will take place from 24-28 October 2016 in Madrid, Spain. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 73. See the full descriptions of the different presentation formats, https://ripe73.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 28 August 2016. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Internet of Things (IoT) Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe73.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe73.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

RIPE Atlas "Commercial use" policy
by Robert Kisteleki 17 Aug '16

17 Aug '16

Dear colleagues, A few different organisations have approached us about using RIPE Atlas data for commercial products, services, reports, etc. We’ve now published conditions for the commercial use of RIPE Atlas data: https://atlas.ripe.net/get-involved/commercial-use/ Please read these conditions carefully if you plan on using RIPE Atlas data for any commercial purpose, and don’t hesitate to contact us if you have any questions. Regards, Robert Kisteleki RIPE NCC

1 0

New on RIPE Labs: Detecting IXPs in Traceroute Paths Using traIXroute
by Suzanne Taylor Muzzin 03 Aug '16

03 Aug '16

Dear colleagues, Is observing an IP address from an IXP prefix sufficient evidence to conclude that a traceroute path crossed an IXP? In this latest RIPE Labs article, George Nomikos and Xenofontas Dimitropoulos explain why they don't think so - and then show how using the traIXroute tool can help: https://labs.ripe.net/Members/george_nomikos/detecting-ixps-in-traceroute-p… Kind regards, Suzanne Taylor Muzzin RIPE NCC

1 0

New on RIPE Labs: Internet Access Disruption In Turkey - July 2016
by Mirjam Kuehne 19 Jul '16

19 Jul '16

Dear colleagues, With the attempted coup in Turkey, reports went out about social media being throttled and/or blocked. We analysed data about this that we collected with RIPE Atlas and the Open Observatory of Network Interference (OONI). Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/internet-access-disruption-in-turke… Kind regards, Mirjam Kuehne RIPE NCC

1 0

More than 200 RIPE Atlas anchors now online
by Michela Galante 29 Jun '16

29 Jun '16

Dear colleagues, Thanks to thirteen new RIPE Atlas anchors being activated over the last two months, we have now reached an important milestone: more than 200 anchors online! Learn more about what anchor measurements can do for you: https://atlas.ripe.net/anchors/about/ We have also started decommissioning anchors with older hardware and working with hosts to replace them with updated hardware. We'd like to thank Nick Hilliard for helping us test our decommissioning procedure and becoming the first anchor host to update to the new hardware for as2128, hosted by INEX in Dublin, Ireland. Since our last announcement, the following anchors have become active: - cz-brq-as24971, hosted by Master Internet s.ro.o in Brno, Czech Republic - nl-ams-as1200, hosted by AMS-IX B.V. in Amsterdam, Netherlands - ca-wtl-as4508, hosted by NeuStyle Corporation in Waterloo, Canada - ie-ork-as2128, second anchor for INEX, hosted in Cork, Ireland - lv-rix-as52048, hosted by DATACLUB S.A. in Riga, Latvia - dk-taa-as51468, hosted by One.com in Tastrup, Denmark - ie-dub-as2128, hosted by INEX in Dublin, Ireland (replaces older hardware) - us-rno-as3851, hosted by University of Nevada in Reno, United States - nl-dft-as31019, hosted by Meanie in Delft, Netherlands - ru-mot-as13238, hosted by Yandex LLC in Mytishchi, Russia - de-bwe-as680, hosted by TU Braunschweig, Gauss-IT-Zentrum in Braunschweig, Germany - nl-ams-as35733, hosted by EURid VZW in Amsterdam, Netherlands - us-abn-as51468, hosted by One.com in Ashburn, United States - kh-pnh-as7712, hosted by Sabay Digital Coperation (sponsored by APNIC) in Phnom Penh, Cambodia 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 all of the anchor hosts: 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, and 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. To apply for your own RIPE Atlas anchor, please visit: https://atlas.ripe.net/get-involved/become-an-anchor-host/ It’s also possible to sponsor an anchor for organisations that want to host one but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0

Results from RIPE Atlas Interface Hackathon
by Vesna Manojlovic 17 Jun '16

17 Jun '16

Dear colleagues, The third RIPE Atlas hackathon took place in Copenhagen the weekend before RIPE 72. In this article, we share the details about the hackathon: https://labs.ripe.net/Members/becha/ripe-atlas-interface-hackathon-results?… Direct link to all the code contributed by the community: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob/m… Regards, Vesna

1 0

Keep All RIPE Atlas Data Accessible in the Standard Way
by Daniel Karrenberg 25 May '16

25 May '16

At today's meeting the RIPE NCC raised the question whether RIPE Atlas Data could be "archived" and longer be accessible by the 'standard API'. I consider this a bad idea because we will loose the ability to access the data with current and future tools, both RIPE NCC tools and those developed by the community using the Atlas API. Long baselines are useful not only for scientific research, but also for developing robust tools and applied research. We have not heard why the RIPE NC has raised the question. So I propose that we ask the RIPE NCC to prepare a detailed proposal including the motivation for proposing this. Until that happens we should keep all RIPE Atlas Data accessible as usual and not spend any time discussing this. Daniel

1 0

Proposal: Discontinue Private Measurements in RIPE Atlas
by Daniel Karrenberg 25 May '16

25 May '16

Keeping measurements and results private in RIPE Atlas comes at a significant cost. Latest case in point is the streaming interface where the developers tell me a significant part of the effort was filtering out results from private measurements. This surprises me because iirc we already decided that results from private measurements were indeed public and only the measurement specifications and meta data would be private. Be that as it may I propose that we ask the RIPE NCC to make a plan to remove private measurements from RIPE Atlas altogether and present it well before the next meeting. We can then have a discussion, build consensus and maybe arrive at consensus about this at the next RIPE meeting. Daniel

1 0