- mat-wg - mailman.ripe.net

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

Apply for the RIPE Atlas data visualisation hackathon
by Vesna Manojlovic 08 Jan '15

08 Jan '15

Dear colleagues, we are happy to invite you to the first RIPE Atlas open data hackathon! In short: various groups will come together during the long weekend in Amsterdam, to make new visualisations (or modify existing ones) based on RIPE Atlas data, and to give that SW back to the community. We are inviting: programers, designers, operators, data-lovers, hackers, students... help us spread the word! Comcast is generously offering prizes and some coverage for travel expenses for several people -- to be awarded/selected by a jury. Dates: 27-28-29 March 2015 (Friday to Sunday) How to apply: https://www.ripe.net/s/XUJy More information in the RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-hackathon-20… Hope to see you there! Regards, Vesna

1 1

MAT-WG proposal for WLAN measurements on RIPE Atlas
by Brook Schofield 26 Dec '14

26 Dec '14

MAT-WG, thankyou for giving me the opportunity to present on "The Value of WLAN Measurements for the R&E Community" at the Measurement and Tools Working Group at RIPE69. You can find my presentation and stenography logs at: https://ripe69.ripe.net/presentations/91-eduroam-and-Atlas-RIPE69.pdf https://ripe69.ripe.net/archives/steno/40 To progress this work within the RIPE NCC Atlas development team I'd like your input into the following five (5) points: #1: For "opt-in" WLAN measurements to be enabled on RIPE Atlas As a point of clarification (and reiterated by Daniel Karrenberg) the intention is that ALL v3 probes will be capable of WLAN measurements - but measurements will ONLY be turned on by a probe host. #2: WLAN measurements will support associating to an "open" or 802.1X protected network for the purposes of performing a measurement As an active monitoring network the Atlas probes WILL NOT scan and report on all/available SSIDs. It will ONLY associate with EXPLICITLY defined SSIDs listed in the measurement. For eduroam quality purposes the success/failure of an 802.1X associations is initially the most interesting part of the measurement in determining whether sites are correctly deploying this service. There will be results related to the authentication process. #3: Any measurements performed over the wireless interface are aligned with a request to associate/authenticate to a particular network. The wireless interface will be connected only for particular tests bundled with the association to an SSID. All other tests will be performed via the wired interface as is currently the case. #4: The schedule for implementation will be determined by the RIPE NCC R&D team ...but hopefully your support for this work will allow them to prioritise this work while not jeopardising the other commitments the team has made to the community. #5: This proposal is inline with your understanding of "WiFi measurements" on the Atlas roadmap I'd be particularly interested in your feedback on whether you thought that the WiFi Measurements listed in the http://roadmap.ripe.net/ripe-atlas/ would accomplish the above or something completely different. My feeling from the room was that the above was largely accepted. I'd appreciate those that voiced their support to also do this on the mailing list again. If there's any confusion I'm willing to clarify further. Thanks, -Brook -- =================================================== Brook Schofield, Project Development Officer GÉANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 www.géant.org <http://www.xn--gant-bpa.org>

8 11

New on RIPE Labs: Visualising RIPE Atlas Probe Distribution
by Mirjam Kuehne 16 Dec '14

16 Dec '14

Dear colleagues, Please find a new article on RIPE Labs showing a visualisation of the distribution of RIPE Atlas probes compared to population: https://labs.ripe.net/Members/emileaben/distribution-of-ripe-atlas-probes Kind regards, Mirjam Kuehne RIPE NCC

1 0

Sixteen new RIPE Atlas anchors joined the community
by Michela Galante 08 Dec '14

08 Dec '14

Dear colleagues, We are proud to announce that sixteen new RIPE Atlas anchors have been activated since our previous announcement: * nl-ams-as12041 hosted by Afilias in Amsterdam, Netherlands. * kz-ala-as21299 hosted by 2Day Telecom LLP in Almaty, Kazakhstan. * Two anchors hosted by Booking.com: nl-ams-as43996 located in Amsterdam, Netherlands and uk-slo-as43996 located in Slough, United Kingdom * sk-bts-as201702 hosted by skHosting.eu in Bratislava, Slovakia. * kz-plx-as21282 hosted by KazNIC Organization in Semey, Kazakhstan. * lk-cmb-as38229 hosted by Lanka Education & Research in Colombo, Sri Lanka and sg-sin-as45494 hosted by openmirror.asia in Singapore, Singapore. These are the first two of ten anchors that APNIC will sponsor. * qa-doh-as8781 hosted by Ooredoo in Doha, Qatar on behalf of RIPE NCC since they are one of our K-root hosts. First anchor in Middle East! * uk-lon-as5459 hosted by LINX in London, United Kingdom on behalf of RIPE NCC since they are one of our K-root hosts and RIS Remote Route Collector locations. * si-lzp-as198644 hosted by the Go6 Institute in Skofja Loka, Slovenia, and sponsored by SIDN, Netherlands. * it-mil-as16004 hosted by Milan Internet eXchange (MIX) in Milan, Italy on behalf of RIPE NCC since they are one of our k-root hosts and RIS Remote Route Collector locations. * Three anchors hosted by Wikimedia Foundation in United States: us-qas-as14907 located in Ashburn, us-cax-as14907 located in Carrollton and us-sfo-as14907 located in San Francisco. * us-lan-as32244 hosted by Liquid Web Inc in Lansing Charter Township, United States. This brings the total number of anchors to 94. You can follow the activation rate on the graph here: https://atlas.ripe.net/results/maps/network-coverage/ The map of all anchor locations: 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/ Kind regards, Michela Galante Measurements Community Building Team RIPE NCC

1 0

Updated Draft RIPE Atlas Service Terms and Conditions, v3.2
by Vesna Manojlovic 01 Dec '14

01 Dec '14

Dear colleagues, Here is an update on RIPE Atlas Service Terms and Conditions: On 15 September, we announced a draft version of new RIPE Atlas Service Terms and Conditions, along with a proposed implementation procedure: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service We published version 3.1 on 29 October, after incorporating feedback received from the community. During RIPE 69 in London last month, more feedback was received, and we’ve now published a third version (3.2), available here: https://atlas.ripe.net/legal/terms-conditions-draft/ Summary of changes: - Extended clarification of point 8.5.a - Minor modifications to grammar and references The revised implementation plan, with adjusted dates, is as follows: - December: last call for comments. If consensus is reached: - In January 2015, existing probe hosts will be notified by email about the upcoming transition to the new terms and conditions. - In addition to email notification, existing users and probe hosts will be presented with a pop-up window when they log in to the RIPE Atlas website, to inform them of the upcoming transition. - From 1 February 2015, RIPE Atlas will become a production service; new probe hosts will be asked to agree to the new terms and conditions when applying for a probe and all existing probe hosts will be subject to the new terms and conditions. We are coordinating with the MAT Working Group Chair to have a final call for comments for both the draft document and the implementation plan. Kind regards, Vesna Manojlovic Senior Community Builder Measurements Community Building

2 1