- mat-wg - mailman.ripe.net

Re: [mat-wg] Using Atlas for commercial services
by Alex Saroyan 06 Sep '13

06 Sep '13

Instead, commercial companies will start hosting many probes in single room not for sake of community but for sake of getting credits. /Alex Saroyan Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote: >On Fri, Sep 06, 2013 at 11:04:44AM +0200, > Peter Koch <pk(a)DENIC.DE> wrote > a message of 11 lines which said: > >> but don't forget credit transfers, even if that doesn't change the >> sum. > >You can get credits through a transfer easily when you are a poor >student having an interesting research project. But I assume >commercial companies selling services over Atlas won't have credits >easily for free :-) >

1 0

New on RIPE Labs: The Seismograph and Other New RIPE Atlas Features
by Mirjam Kuehne 06 Sep '13

06 Sep '13

Dear colleagues, We implemented a number of new features in RIPE Atlas, including the seismograph, an interactive tool to easily visualise multiple ping measurements. Please find more information on RIPE Labs: https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: New RIPEstat Website
by Mirjam Kuehne 28 Aug '13

28 Aug '13

Dear colleagues, We've revamped the RIPEstat website to make it easier to find information. Please read more on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/new-ripestat-website Kind regards, Mirjam

1 0

RIPE 67 CFP extended deadline 9 September 2013
by Benno Overeinder 26 Aug '13

26 Aug '13

Dear Colleagues, A list of currently accepted RIPE 67 Plenary talks, BoFs, Tutorials and Workshops is now published at: https://ripe67.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 67 programme and RIPE Programme Committee will accept new proposals until *9 September 2013*. This is our last call for you to submit your proposals. See https://ripe67.ripe.net/programme/cfp/ or find the original CFP below. Kind regards Filiz Yilmaz for RIPE Programme Committee ------------------ 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 67 will take place from 14-18 October 2013 in Athens, Greece. 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 67. 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://ripe67.ripe.net/programme/i-want-to-present/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 4 August 2013, using the meeting submission system (https://ripe67.ripe.net/submit-topic/) Proposals submitted after this date will be considered on a space-available basis. * Lightning talks should also be submitted using the meeting submission system (https://ripe67.ripe.net/submit-topic/) 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 (https://ripe67.ripe.net/programme/i-want-to-present/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 panelists, presenters and moderators. * Due to potential technical issues, it is expected that most, if not all, presenters/panelists 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

Accessing Routing Information Via RIPEstat
by Vesna Manojlovic 23 Aug '13

23 Aug '13

Dear colleagues, Our Routing Information Service (RIS) has been collecting global BGP routing information for 12 years now. During this period, many different interfaces to analyse and visualise accumulated data have been developed. In line with our long-term goals to provide more consolidated services, we will be integrating the RIS interface's tools and services into RIPEstat. More information about this is detailed in a new RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/improved-routing-information-ava… We invite the community to comment on these upcoming changes: https://www.ripe.net/ripe/groups/wg/mat Please submit any urgent requests for additional features via email to stat(a)ripe.net by 20 September 2013 so that we can implement these along with the planned migration of tools and features. Any feedback received after this date will be considered feature requests, and added to the RIPEstat Roadmap: http://roadmap.ripe.net/ripe-stat/ We look forward to your feedback. Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

Future of RIPE NCC technical services
by Kaveh Ranjbar 20 Aug '13

20 Aug '13

Dear colleagues, In June of this year, I took on a new role at the RIPE NCC and joined the Senior Management team as Chief Information Officer (a role formerly called Head of Science Division). Since that time, I've had a chance to review the technical services we provide to the community, and I’d like to share with you some of my ideas about the planned future direction of these services. To summarise, these plans include: - Focusing on RIPE Atlas as the RIPE NCC’s data collection system - Developing RIPEstat as the RIPE NCC's consolidated point for data retrieval - Service agreements and other plans for hosted services like K-root, authoritative DNS servers and RIS data collectors - A greater focus on data analysis We believe the plans we have in place will allow you to access our services more easily and efficiently, and make better use of the data we collect. You can read the full details on RIPE Labs: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services I hope you'll take the time to read the full article and learn more about the planned future direction of our services. As always, we invite your comments and suggestions, which you can leave in the comments field of the article, or by contacting me directly at kranjbar(a)ripe.net. Our top priority is ensuring we provide you with the most useful services and data possible, and I look forward to hearing your thoughts. Best regards, Kaveh Ranjbar Chief Information Officer RIPE NCC

1 0

Re: [mat-wg] [atlas] RIPE Atlas maintenance on Tuesday, 6 August
by Robert Kisteleki 06 Aug '13

06 Aug '13

Dear All, This work is now done and we believe everything is back to normal (*). Please let us know (preferably via atlas-bugs(a)ripe.net) if you find something not working. Regards, Robert Kisteleki (*) independently of this maintenance, one of the data servers (zpm01) is having some hardware issues, which causes data downloads and RRDs for probes 1-499 to be flaky. We're working on this. On 2013.07.30. 12:19, Robert Kisteleki wrote: > > Dear RIPE Atlas users, > > We'd like to let you know that we plan to perform scheduled maintenance on > the RIPE Atlas central infrastructure on Tuesday, 6 August, for a couple of > hours during the day. In this period, main features including the RIPE Atlas > user interface (atlas.ripe.net) data downloads and measurement scheduling > functions will be unavailable. > > Probes will continue to work and all results will still be collected or > buffered; however, during the maintenance period you will be unable to log > in to the website, manage your probes/measurements, or get to result > data/visualisations. > > We apologise for any inconvenience this may cause. > > Regards, > Robert Kisteleki > >

1 0

RIPE Atlas maintenance on Tuesday, 6 August
by Robert Kisteleki 31 Jul '13

31 Jul '13

Dear RIPE Atlas users, We'd like to let you know that we plan to perform scheduled maintenance on the RIPE Atlas central infrastructure on Tuesday, 6 August, for a couple of hours during the day. In this period, main features including the RIPE Atlas user interface (atlas.ripe.net) data downloads and measurement scheduling functions will be unavailable. Probes will continue to work and all results will still be collected or buffered; however, during the maintenance period you will be unable to log in to the website, manage your probes/measurements, or get to result data/visualisations. We apologise for any inconvenience this may cause. Regards, Robert Kisteleki

1 0

Re: [mat-wg] [atlas] Spoofing the source IP address from a probe?
by Andrei Robachevsky 30 Jul '13

30 Jul '13

Alex Saroyan wrote on 7/18/13 8:53 AM: > Hi, > > I think some hosts would like theirs probes to be used for "source IP > spoofing" check, and only such probes could be used for this particular > type of check. > If RIPE Atlas team implement such features then probably many hosts will > "enable" "Source IP spoofing check ability" on theirs probes and that > can serve for community at the end. I support this point of view. I think controlled (anti-)spoofing measurements performed by the RIPE NCC with the consent of participating probes would be a good service to the community. I understand that a certain percentage of probes is sitting behind NAT where spoofing won't work in most cases, but there is hopefully a significant number of probes that are connected directly. Regarding the problem itself we are tackling here, we published a follow up to the panel we held at RIPE66: http://www.internetsociety.org/doc/anti-spoofing-continuing-dialogue. Hope this helps raising awareness of the issue further. > Of course overall mechanism should be in a way not make anyone to > suspect that probe can do spoofing by default or probe can do any > harmful thing. > Agree, Andrei > Alex Saroyan > > On 06/12/2013 10:37 PM, Daniel Karrenberg wrote: >> On 12.06.2013, at 17:44 , Joe Provo <jzp-ripe(a)rsuc.gweep.net> wrote: >> >>> I would encourage those in the community who wish to be >>> performing individual spoof testing (or instruct others how >>> to do so) to use the easy-peasey pointy-clicky CAIDA/CSAIL >>> tool: http://spoofer.cmand.org/ >>> (also spoofer.csail.mit.edu, spooftest.net, etc etc) >> Seconded. Using this something like this is a conscious decision of >> the user. I have personally run Robert Beverley's probes regularly for >> many years and I am proud to say that both my broadband providers have >> never allowed source address spoofing. This involves a conscious >> decision on my part taking into account local network etiquette, my >> relation to my providers and the local legal situation. It is very >> very different from the RIPE community deciding to use RIPE Atlas to >> do this from my network. >> >> Daniel > >

2 2

Re: [mat-wg] [atlas] Spoofing the source IP address from a probe?
by Alex Saroyan 30 Jul '13

30 Jul '13

Hi, Probably we don't need to spoof all address space, instead only if spoofing enabled just spoof to some predefined address range. Regards. /Alex Sanjeev Gupta <ghane0(a)gmail.com> wrote: >On Tue, Jul 30, 2013 at 11:22 AM, Randy Bush <randy(a)psg.com> wrote: > >> I support this point of view. I think controlled (anti-)spoofing >> measurements performed by the RIPE NCC with the consent of >> participating probes would be a good service to the community. > >perhaps the probe owners are not the only parties with skin in the game >and whose consent would be relevant? > > >Exactly. I host probes, and since you are spoofing others, we need to ask them. > >How you do this is left as an exercise to the reader. > >-- >Sanjeev Gupta >+65 98551208 http://www.linkedin.com/in/ghane > > >

1 0

Atlas UDMs and Probe-Assignments
by Gert Doering 26 Jul '13

26 Jul '13

Hi, I'm wondering about something, maybe one of you can enlighten me here. I have set up a few UDMs (... to eventually get out of Atlas what we had with TTM). A small one with only 10 probes is now showing that actually only 7 probes return data - two more have returned data at some point in the past - "Jul 06, 06:11" in one case - while the 10th assigned problem seems to have never sent anything. (This is UDM 1002000, the "dead" probe is #2760 in AS 3292). The question coming from this is: how do probes get assigned to UDMs, and will dead probes get replaced eventually? Or is the assignment done statically at the beginning of the UDM? The reason why this is relevant: if I am going to set up UDMs to replace what TTM does, the idea is to have a reasonable high number of probes, say "50" or "100", and define our Internet reliability as "more than 2/3rd of the UDM probes have been answered without loss", or something like that - taking into account that somewhere on the Internet, things will always be broken, but that's not our responsibility. This falls apart of probes deteriorate after a given time, and a given UDM measurement will use "less and less probes" (so in the extreme, of the 50 initial probes, 30 might be "dead probe" and thus the result is always "0% reliability, more than 50% of the probes can not reach us"), instead of the system keeping the requested number of probes by replacing dead ones... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

2 4

Atlas UDM and API keys?
by Gert Doering 25 Jul '13

25 Jul '13

Hi, maybe it's too hot today, maybe I'm a bit slow, but just how do I combine the Atlas UDM download links and the API KEY to form a "download will just work" URL? The download URL I want to use is https://atlas.ripe.net/api/v1/measurement/1002000/result/?start=1373972036&… so where does the API key go? Adding "?key=<key data>" or "?apikey=..." or "just the key with no tag" didn't work... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

1 1

New on RIPE Labs: In-widget Comparison and Monitoring in RIPEstat
by Mirjam Kuehne 24 Jul '13

24 Jul '13

Dear colleagues, You can now monitor network events in real time in two RIPEstat widgets: Country Routing Statistics and BGP Update Activity. And we would like to hear from you for which widgets we should provide this functionality next. Please find more details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/new-in-ripestat-in-widg… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Call for Papers: RIPE 67, 14-18 October 2013 in Athens, Greece
by Benno Overeinder 23 Jul '13

23 Jul '13

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 67 will take place from 14-18 October 2013 in Athens, Greece. 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 67. 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://ripe67.ripe.net/programme/i-want-to-present/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 4 August 2013, using the meeting submission system (https://ripe67.ripe.net/submit-topic/) Proposals submitted after this date will be considered on a space-available basis. - Lightning talks should also be submitted using the meeting submission system (https://ripe67.ripe.net/submit-topic/) 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 (https://ripe67.ripe.net/programme/i-want-to-present/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 panelists, presenters and moderators. - Due to potential technical issues, it is expected that most, if not all, presenters/panelists 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

PORTOLAN: A Mobile Crowdsourcing Measurement System
by Luciano Lenzini 08 Jul '13

08 Jul '13

Dear All, The University of Pisa and IIT, an Institute of the Italian National Research Council, have developed a mobile crowdsourcing-based system, named PORTOLAN which uses smartphones as mobile monitors probing the Internet and reporting results to a central server located in Pisa. 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. The PORTOLAN component that runs on smartphones is now available as an app for the Android platform. It can be downloaded by users from Google play ( <https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracero ute> https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracerou te). PORTOLAN works in the background, it is designed not to interfere in any way with users' activities and does not affect the smartphone'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. All the tools are totally under the user's control. Data collected by these tools are stored in our servers, in a completely anonymous way. For details see <http://portolan.iet.unipi.it/> http://portolan.iet.unipi.it/. The success of our experiment depends upon the number of users who join the experiment. But to get people to download the app, we really need to raise as much awareness as possible regarding the PORTOLAN itself. So I would like to ask you if it would be possible for you to forward this message to your colleagues, students and anyone else who you think might be interested. Many thanks in advance for your cooperation. All the best, Luciano TECHNICAL NOTE: In PORTOLAN, each smartphone issues at max 200 traceroutes per day, which means a peak traffic rate never higher than 1 KB/s and an average traffic rate never higher than 2 MB/day. The impact of these activities on the battery consumption is negligible. Signal coverage measurements are completely costless in terms of energy or bandwidth, as the PORTOLAN app passively collects signal strength samples using GPS positions generated by other apps. You have to activate the GPS yourself if you want a coverage map along your route. Given that your route could be up to 50 km or more, then you will obviously use up quite a bit of your battery power. So if you are travelling, then connect your smartphone to a powersource in your car or in the train. In any case, if the battery level goes under 40%, PORTOLAN is automatically suspended. -------------------------------------------------------------- Prof. Luciano Lenzini Department of Information Engineering University of Pisa, Italy e-mail: l.lenzini(a)iet.unipi.it http://www.iet.unipi.it/~lenzini

1 0

New on RIPE Labs: Are All Addresses Equal? (by Stephane Bortzmeyer)
by Mirjam Kuehne 03 Jul '13

03 Jul '13

Dear colleagues, Stephane Bortzmeyer describes another use case for RIPE Atlas: Are IPv4 addresses in which the last byte is zero treated differently than other IPv4 addresses? See his study on RIPE Labs: https://labs.ripe.net/Members/stephane_bortzmeyer/all-ip-addresses-are-equa… Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas Mid-summer community update
by Vesna Manojlovic 01 Jul '13

01 Jul '13

Der colleagues, RIPE Atlas community has been very active recently. I summerized it (ha! pun intended) in the RIPE Labs article, highlighting new community related features for RIPE Atlas anchor hosts, sponsors and "ambassadors". And the article has lots of pretty pictures! Share and enjoy! Warm regards, Vesna https://labs.ripe.net/Members/becha/ripe-atlas-midsummer-2013-community-upd…

1 0

New on RIPE Labs: RIPEstat's Multiple Widget and Resource Comparison
by Mirjam Kuehne 24 Jun '13

24 Jun '13

Dear colleagues, RIPEstat users can now compare results for multiple resources across multiple widgets in a new comparison page - and share the results with others using the permalink feature. In this new article on RIPE Labs we describe several use cases where this new functionality might come in handy: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestats-multiple-widg… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
by Mirjam Kuehne 12 Jun '13

12 Jun '13

Dear colleagues, Please see a new article on RIPE Labs contributed by Stephane Bortzmeyer: How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)? https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-bel… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: RIPEstat Demo Summary
by Mirjam Kuehne 21 May '13

21 May '13

Dear colleagues, For those of you who missed the RIPEstat demo at the recent RIPE 66 meeting, please find a summary on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-demo-summary-r… Kind regards, Mirjam Kuehne RIPE NCC

1 0

[Fwd: Community suggestion for ATLAS spoof test]
by Vesna Manojlovic 21 May '13

21 May '13

Dear colleagues, please take a look at the suggestion from Alexander Isavnin. Since he is here in Dublin, we can talk about it during MAT-WG or, if there is not enough time, at the RIPE Atlas community BoF. However, the opinion of the rest of the community counts too, so I ask you to comment on the mailing list, if you are interested. Regards, Vesna -------- Original Message -------- Subject: Community suggestion for ATLAS spoof test Date: Wed, 15 May 2013 21:16:30 +0200 From: Alexander Isavnin <isavnin(a)netline.ru> To: Vesna Manojlovic <BECHA(a)ripe.net> Dear Vesna! Could you forward this suggestion to mat-wg mailing list (and other appropriate lists). Due to high requirements to mitigate spoofing there is need to detect one. RIPE community have great distributed networking tool - ATLAS. As first step i suggest to select address from RIPE NCC network and allow all probes (if probe is not behind NAT) to send spoofed packet with this address as source. As first and a half step - allow to send packets with source addresses of anchors (if anchor's host agrees) As second step - allow probe host to permit use his address as spoofed source. Best regards, Alexander Isavnin

6 5

Re: [mat-wg] [Fwd: Community suggestion for ATLAS spoof test]
by k claffy 20 May '13

20 May '13

From: Antoin Verschuren <antoin.verschuren(a)sidn.nl> If all we want to know is an oversight of the state of spoofing now, and in a year's time, can't we just ask the Atlas users (AKA the mailinglist) that want to know to do a 1 time spoofing test on http://spoofer.csail.mit.edu/summary.php from their atlas probe network? IMHO that is less work than to ask Atlas users for permission. Antoin, Thanks for suggesting that, we agree that Atlas nodes are a terrific way to increase the scope of visibility of spoofing. I should note that we have spent the last few months updating the 7-year old spoofer code and web site (btw, it's now at http://spoofer.cmand.org/ , jointly managed by Rob Beverly at nps.edu and CAIDA) including adding tests for IPv6 spoofing ability, making graphs on the summary page clearer, classifying spoofing-capable networks into types, and allowing probing to multiple (CAIDA Ark) destintations (which also increases visibility into spoofing, but not nearly as much as 1000+ Atlas nodes would..) we plan to deploy and announce an updated version by 1 June. so if you're going to encourage Atlas nodes to try our spoofer test, it would be ideal to have them do it shortly after 1 June. we will send an announcement to this list when we release the new version. after june we will still be working on better techniques to filter tests for representativeness, and other methodology improvements. please do send us requests for other changes/additions you would like to see. ( http://spoofer.cmand.org/contact.php ) thanks, k (and Rob Beverly and Ryan Koga, current team)

1 0

New on RIPE Labs: RIPE Atlas Code for Analysis and Statistics Reporting
by Mirjam Kuehne 13 May '13

13 May '13

Dear colleagues, We are releasing the code we use to analyse RIPE Atlas measurements and produce summary statistics. This will make processing these measurement results easier for the community. We're also inviting you to participate in improving this further. Please find more information on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ripe-atlas-code-for-analysis-and-stat… Kind regards, Mirjam Kuehne RIPE NCC

1 0

[Fwd: [ipv6-wg] New on RIPE Labs: Implementing Fifth Start IPv6 RIPEness]
by Vesna Manojlovic 13 May '13

13 May '13

Sorry for the cross-posting -- I think the IPv6 measurements that we are doing for the 5th star in IPv6 RIPEness are of interest to MAT-WG. I'll be presenting about this at IPv6-WG in Dublin, and if there is interest & questions from this group I can mention it too. Regards, Vesna -------- Original Message -------- Subject: [ipv6-wg] New on RIPE Labs: Implementing Fifth Start IPv6 RIPEness Date: Mon, 13 May 2013 07:09:34 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: ipv6-wg(a)ripe.net Dear colleagues, In this new article on RIPE Labs we present the first results of a fifth star for IPv6 RIPEness. This is a way to measure real IPv6 deployment in the RIPE NCC service region: https://labs.ripe.net/Members/emileaben/ipv6-ripeness-implementing-the-5th-… We would like to receive your feedback on a number of open question raised in the article. We also hope to see many of you at the IPv6 WG meeting in Dublin later this week where these results will be presented. Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: BGPlay now integrated in RIPEstat
by Mirjam Kuehne 08 May '13

08 May '13

[apologies for duplicates] Dear colleagues, We are proud to present a newly revamped version of the well-known BGPlay tool. It is now integrated into RIPEstat and was developed in partnership with the Compunet Research Lab of Roma Tre University. Please find more information on RIPE Labs: https://labs.ripe.net/Members/vastur/bgplay-v2-integrated-in-ripestat Kind regards, Mirjam Kuehne RIPE NCC

1 0