- mat-wg - mailman.ripe.net

Call for Presentations: RIPE 68, 12-16 May 2014 in Warsaw, Poland
by Benno Overeinder 14 Jan '14

14 Jan '14

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 68 will take place from 12-16 May 2014 in Warsaw, Poland. 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 68. 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://ripe68.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 2 March 2014, using the meeting submission system at https://ripe68.ripe.net/submit-topic/guidelines/. 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://ripe68.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://ripe68.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 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

New on RIPE Labs: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names?
by Mirjam Kuehne 13 Jan '14

13 Jan '14

Dear colleagues, Please find a new article on RIPE Labs submitted by Stéphane Bortzmeyer: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names? https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-ripe-atlas-probe… Kind regards, Mirjm Kuehne RIPE NCC

1 0

RIPE Atlas 2013: A Year In Review
by Michela Galante 13 Jan '14

13 Jan '14

Dear colleagues, 2013 was an exciting year for RIPE Atlas. Take a look at what you helped us to achieve in 2013, in the new article on RIPE Labs: https://labs.ripe.net/Members/michela_galante/ripe-atlas-2013-year-in-review Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

Proposing more public RIPE Atlas data and clarifying the current situation
by Vesna Manojlovic 10 Jan '14

10 Jan '14

Dear colleagues, Sharing information about Internet performance is at the heart of collaborative efforts such as RIPE Atlas. Most of the RIPE Atlas probes and RIPE Atlas measurements are already public, and we'd now like to suggest opening up the publication of RIPE Atlas data further. We also want to clarify exactly what is and isn't public in the current system. We describe this in more detail in this RIPE Labs article, where we also ask for community feedback about our suggested plan to move forward: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Our proposed plan is to make all *new* measurements and technical information about the *new* probes public from an agreed upon date in the future. We propose implementing this change in mid-April. All probes and measurements that were not marked "public" by April 2014 would remain non-"public". For a detailed description of what this means, please see the RIPE Labs article (above). Although we believe that having public measurement data contributes to the goal of RIPE Atlas, the RIPE NCC greatly values our users' privacy. We want to ensure you that we will continue to protect our probe hosts' personal information. We look forward to your feedback and comments on the MAT Working Group Mailing List. Regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

12 18

Updating the DNS Monitoring Service
by Romeo Zwart 19 Dec '13

19 Dec '13

Dear colleagues, Our DNS Monitoring Service (DNSMON) has been providing an up-to-date service overview of certain DNS root and Top-Level Domain (TLD) name servers for over eight years now, using the Test Traffic Measurement Service (TTM) as the underlying measurement platform. Last week, we sent out an announcement explaining that TTM would be decommissioned and its functions replicated within RIPE Atlas. As DNSMON currently relies on TTM for its data collection, the decommissioning of TTM will impact DNSMON. As announced in the RIPE NCC Activity Plan and Budget 2013, DNSMON in its current state will be shut down and most of its functionality migrated over to RIPE Atlas and RIPEstat, providing an improved and more future-proof DNS Monitoring Service. RIPE Atlas, and specifically the RIPE Atlas anchors, will perform measurements providing the data previously collected by TTM systems. More information is available in the RIPE Labs article, “Future of RIPE NCC Technical Services”, written by Kaveh Ranjbar, Chief Information Officer at the RIPE NCC: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services Some of our current DNSMON users have volunteered to conduct preliminary testing of the new, updated service, in the first quarter of 2014. Partly based on the user feedback from this testing phase, we will develop the new service so that it best meets the needs of current users. We hope to have the migration completed, with the new service fully implemented and available, by the end of the first quarter of 2014. After that, we will start to expand the service and accept applications from new users. You can find the most up-to-date plans on the DNSMON roadmap: http://roadmap.ripe.net/dnsmon/ If you have any questions or feedback, please contact <dnsmon-future(a)ripe.net> or reply to the MAT-WG Mailing List. Regards, Robert Kisteleki Romeo Zwart

1 0

New on RIPE Labs: Infrastructure Geolocation - Plan of Action
by Mirjam Kuehne 19 Dec '13

19 Dec '13

Dear colleagues, At RIPE 67 we presented our ideas on infrastructure geolocation. This new RIPE Labs article by Emile Aben shows the current thinking on how to develop router geolocation further. Any feedback will be appreciated. https://labs.ripe.net/Members/emileaben/infrastructure-geolocation-plan-of-… Kind regards, Mirjam Kuehne RIPE Labs

1 0

Scheduled shutdown of Test Traffic Measurement Service (TTM)
by Romeo Zwart 13 Dec '13

13 Dec '13

Dear colleagues,  We are currently in the process of shutting down our Test Traffic Measurement Service (TTM). These plans were previously announced at RIPE 64 by Daniel Karrenberg in the Measurement Analysis and Tools (MAT) Working Group session, and in section 2.4.5 of the RIPE NCC Activity Plan and Budget 2013: http://www.ripe.net/ripe/docs/ripe-558 This is now scheduled for completion by the end of the first quarter of 2014. The TTM service has been operational for more than ten years. The equipment used to provide this service, as well as the software underlying it, have become outdated and costly to maintain. Several years ago, we introduced our new measurements service, RIPE Atlas. RIPE Atlas and RIPE Atlas anchors can provide almost all of the functionality provided by TTM. This was explained by Kaveh Ranjbar, the RIPE NCC's Chief Information Officer, in the RIPE Labs article, “The Future of RIPE NCC Technical Services”. As noted in this article, one difference is that RIPE Atlas does not support one-way latency measurements; however, these were not used by most TTM users and also required special, expensive equipment. The article is available in full at: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services We will contact individual TTM hosts shortly to make arrangements to decommission their TTM systems. We are also investigating the possibility of creating an archive of TTM measurement results that can be used for research purposes. As previously mentioned, RIPE Atlas, and specifically RIPE Atlas anchors, provide much of the functionality of TTM. More details about the features and benefits of RIPE Atlas anchors, including information about how you can host a RIPE Atlas anchor, are available at: https://atlas.ripe.net/about/anchors/ We look forward to any feedback or questions you may have regarding this development. Regards, Romeo Zwart Global Information Infrastructure Services Manager RIPE NCC

2 2

New on RIPE Labs: Map a RIPE Atlas Anchor
by Mirjam Kuehne 27 Nov '13

27 Nov '13

Dear colleagues, Please find a new article, contributed by Daniel Karrenberg, on RIPE Labs: RIPE Atlas Fun - Map a RIPE Atlas Anchor. https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor It shows some interesting graphs based on RIPE Atlas traceroute measurements. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Updates on Measurements of Typhoon Haiyan Impact
by Mirjam Kuehne 22 Nov '13

22 Nov '13

Dear colleagues, Over the last few days we published a number of updates to the original article "Typhoon Haiyan - What do We see in RIPEstat and RIPE Atlas". Please see the links on top of this page: https://labs.ripe.net/Members/emileaben/typhoon-haiyan-what-we-see-in-ripes… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Network Anomaly Detection Survey
by Mirjam Kuehne 20 Nov '13

20 Nov '13

Dear colleagues, Jan Rejchrt from the Institute of Computer Science at the Masaryk University in Brno, Czech Republic, is conducting a survey that will help develop network anomaly detection tools. Please find some more information and the link to the survey on RIPE Labs: https://labs.ripe.net/Members/jan_rejchrt/network-anomaly-detection-survey Kind regards, Mirjam Kuehne RIPE NCC

1 0