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/
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
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
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
>
>
