- mat-wg - mailman.ripe.net

New on RIPE Labs: Stopping Support for Internet Explorer 8 on Windows XP in RIPE Atlas and RIPEstat
by Mirjam Kuehne 24 Feb '15

24 Feb '15

Dear colleagues, Microsoft ended support for Windows XP as of April 2014. We're about to change RIPE Atlas and RIPEstat to stop support for Internet Explorer 8 running on these systems. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/stopping-support-for-internet-explorer… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: NTP Measurements with RIPE Atlas
by Mirjam Kuehne 19 Feb '15

19 Feb '15

Dear colleagues, This new RIPE Labs article describes how RIPE Atlas probes and anchors maintain their clocks, and how accurate these clocks are. We also plan to make the NTP measurements we describe here available as an additional measurement type for RIPE Atlas users: https://labs.ripe.net/Members/philip_homburg/ntp-measurements-with-ripe-atl… Kind regards, Mirjam Kuehne RIPE NCC

3 3

New on RIPE Labs: Visualising Network Outages with RIPE Atlas using CartoDB
by Mirjam Kuehne 03 Feb '15

03 Feb '15

Dear colleagues, This new article on RIPE Labs shows some prototypes of visualising network outages with RIPE Atlas using CartoDB: https://labs.ripe.net/Members/emileaben/visualising-network-outages-with-ri… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Moving forward with proposed RIPE Atlas Service Terms and Conditions
by Christian Kaufmann 30 Jan '15

30 Jan '15

Dear MAT-WG, As Vesna recently announced on this list, the RIPE NCC is seeking final comments on the draft RIPE Atlas Service Terms and Conditions. There has been some positive feedback on the latest draft, and if there are no further comments, I would like to encourage the RIPE NCC to move forward with finalising these terms and conditions. They can then begin the implementation plan that Vesna explained in her email on 1 December: http://www.ripe.net/ripe/mail/archives/mat-wg/2014-December/000517.html <http://www.ripe.net/ripe/mail/archives/mat-wg/2014-December/000517.html> The draft RIPE Atlas Service Terms and Conditions are available here: https://atlas.ripe.net/legal/terms-conditions-draft/ <https://atlas.ripe.net/legal/terms-conditions-draft/> I would encourage you to please take the time to look over both the draft document and the implementation plan if you have not already done so. best regards, Christian Kaufmann MAT-WG Chair

2 2

#facebookdown? Read on RIPE Labs What Internet Measurement Data Shows
by Mirjam Kuehne 27 Jan '15

27 Jan '15

Dear colleagues, While at this point it is still unclear what exactly happened at Facebook on 27 January, we collect data on the Internet control plane (BGP) and data plane that allows us to provide some insight into what happened with Facebook's connectivity to the rest of the Internet. Please find more details on RIPE Labs: https://labs.ripe.net/Members/emileaben/facebookdown-and-what-internet-data Kind regards, Mirjam Kuehne RIPE NCC

1 0

Portolan/Desktop
by Luciano Lenzini 23 Jan '15

23 Jan '15

Dear Colleague, The University of Pisa and IIT, an Institute of the Italian National Research Council, have designed and developed a crowdsourcing-based system, named PORTOLAN, which initially employed smartphones as mobile monitors probing the Internet. The aim of PORTOLAN is to enhance the current topology of the Internet at the Autonomous System level of abstraction - all with the contribution of volunteers. Find out more on our website (http://portolan.iet.unipi.it). Portolan was initially deployed in 2012 and since then it has been available on smartphone clients running Android. In order to increase the number of users, Portolan IS NOW available for desktop operating systems Linux, Windows and OS X. In this way we hope to obtain a more precise Internet structure with respect to the one now available. PORTOLAN works in the background, it is designed not to interfere in any way with users' activities and does not affect the smartphone/desktop's overall performance. In order to motivate users to contribute to the PORTOLAN project, we have added several services, which include diagnostic network tools (such as Ping, Paris Traceroute with Multipath Detection Algorithm, Maximum Throughput achievable along a path, etc.) and coverage measurement tools (available on smartphones only). All the tools are totally under the user's control. Data collected by these tools are stored in our server located in Pisa, in a completely anonymous way. The PORTOLAN component that runs on Android smartphones can be downloaded by users from Google play (https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracero ute). The PORTOLAN component for desktop, available for Windows 7/8, Linux and OS X, can be downloaded at our website http://portolan.iet.unipi.it/download. The success of Portolan depends upon the number of users who join the experiment. Feel free to share this message with your colleagues students and friends!. Many thanks in advance for your cooperation. All the best, Luciano On behalf of the Portolan Development Team ------------------------------------------------ Prof. Luciano Lenzini Associate Researcher IIT/CNR lenzini44(a)gmail.com Former Full Professor Department of Information Engineering School of Engineering University of Pisa, Italy http://www.iet.unipi.it/~lenzini and Research Director CNUCE/CNR

1 0

Proposal for public HTTP measurements
by Robert Kisteleki 21 Jan '15

21 Jan '15

Dear RIPE Atlas users, The topic of publicly available HTTP measurements in RIPE Atlas comes up from time to time. There were a number of discussions about pros and cons for this feature over the years (including exposing probe hosts to unnecessary risks of other users "measuring" just about any kind of HTTP content out there), with no firm outcome. While we understand that this feature would come handy for some of our users, it does not benefit everyone. Therefore our proposal is the following: 1. We'll enable HTTP measurements to be performed by all atlas users, from any probes. 2. The targets of such measurements can only be RIPE Atlas anchors (these already run HTTP servers, see https://atlas.ripe.net/docs/anchors/). 3. Parameters like costs, minimum frequency, maximum number of probes involved, etc. will be set by the development team, just as with the other measurements. 4. The RIPE NCC will still be able to support other, vetted HTTP measurements as long as it benefits the community, as well as other HTTP measurements that we deem operationally useful. These will be evaluated on a case by case basis. Please speak up at the MAT working group list (mat-wg(a)ripe.net) if you support / don't support this proposal, of if you have any other opinion about it. Regards, Robert Kisteleki RIPE NCC R&D manager, for the RIPE Atlas team

8 14

Six new RIPE Atlas anchors, and that makes one hundred total!
by Vesna Manojlovic 16 Jan '15

16 Jan '15

Dear colleagues, We are proud to announce that six new RIPE Atlas anchors have been activated since our previous announcement: * uk-lon-as8676 hosted by PRT Systems Ltd in London, United Kingdom * br-sao-as22548 hosted by Núcleo de Informação e Coordenação do Ponto BR - NIC.br in Sao Paulo, Brazil * us-qas-as10745 hosted by ARIN on behalf of RIPE NCC in Ashburn, United States * us-phx-as53824 hosted by Liquid Web in Phoenix, United States * se-sln-as49515 hosted by Nordiska Servercentralen in Solna, Sweden * dk-blp-as39839 hosted by DK Hostmaster A/S in Ballerup, Denmark This brings the total number of anchors to 100! We wrote an article on RIPE Labs to cover all the details, which includes some changes to the anchoring measurements: https://labs.ripe.net/Members/suzanne_taylor_muzzin/one-hundred-ripe-atlas-… 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 Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Call For Presentations RIPE 70, submission deadline 1 March 2015
by Benno Overeinder 13 Jan '15

13 Jan '15

Dear colleagues, Please find the CFP for RIPE 70 below. The deadline for submissions is 1 March 2015. 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 for the RIPE Programme Committee http://www.ripe.net/ripe/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 70 will take place from 11-15 May 2015 in Amsterdam, The Netherlands. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 70. 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 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. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe70.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 1 March 2015, using the meeting submission system at https://ripe70.ripe.net/submit-topic/submission-form/. Proposals submitted after this date will be considered on a space-available basis. Important Dates regarding RIPE 70 can be found at: https://ripe70.ripe.net/programme/important-dates/ - Lightning talks should also be submitted using the meeting submission system (https://ripe70.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe70.ripe.net/submit-topic/presentation-formats/. - Proposals for talks 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, it is expected that most, if not all, presenters/panellists will 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

Deprecating the old measurement UI
by Robert Kisteleki 09 Jan '15

09 Jan '15

Dear all, In October last year, we introduced a new UI for browsing and scheduling measurements. For details, see: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Your feedback about this was predominantly positive, and we’d like to thank everyone who helped this development with suggestions and bug reports. As stated at the time, we plan to deprecate and eventually remove the old interface (both the UI and the "API" it used). Our timeline is the following: 1. We'll make the new UI the default, and remove links to the old UI from the RIPE Atlas main menu, around 21 January. The old pages will still be accessible if one reaches them from somewhere else, such as a browser bookmark or hard-coded scripts. 2. Around the beginning of March, we'll remove the old pages from the system (/atlas/udm.html and related pages). This step will include the "deep links" that some of our users directly access to schedule and manage measurements from scripts (notably /atlas/*udm*.json). We'd like to encourage all of our users to switch to the new UI and API in the following weeks, if you haven't already done so. As always, we're happy to answer any questions or hear any feedback you might have. Regards, Robert Kisteleki, for the RIPE Atlas team

1 0