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
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.pdfhttps://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>
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
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
