3-4 October 2016, Yerevan, Armenia
The ENOG 12/RIPE NCC Regional Meeting took place from 3-4 October 2016 at the Armenia Marriott Hotel in Yerevan, Armenia. A total of 251 attendees participated in the meeting, 177 of whom were from Armenia.
Monday, 3 October
Opening Plenary 15:00 – 16:30
Welcome to ENOG 12
- Serge Radovcic, RIPE NCC
- Vahan Martirosyan, Minister of Transport, Communication and Information Technologies
- Vahan Hovsepyan, Armix
- Sergey Myasoedov, ENOG PC Chair
DNS as a Defense Vector
IPv6 … Are we there yet?
Hisham Ibrahim, RIPE NCC
Nathalie Trenaman, RIPE NCC, reminded the audience that the meeting had an IPv6 only SSID provided by Ucom, and urged attendees to push packets over IPv6 and try out that SSID during the meeting.
RIPE Academic Cooperation Initiative (RACI)
Gergana Petrova, RIPE NCC
Plenary 17:00 – 18:30
How to Think About IXPs if you are a Regulator
Timothy Denton, Hurricane Electric
Some Thoughts on Vulnerability Risk Management
Alex Smirnoff, Open Network Association
Birds of a Feather Session 18:30 – 19:30
RIPEstat as a Tool
Alex Semenyaka, RIPE NCC
Tuesday, 4 October
Plenary 10:00 – 11:30
DNSSEC Deployment Best Practices, Experiences, Challenges, Stats, etc.
Richard Lamb, ICANN
Kaveh Ranjbar, RIPE NCC, said Richard’s presentation illustrates a project the RIPE NCC took to the DNS Working Group and affected a change through the power of the community.
Rolling the Root Zone DNSSEC KSK
RIPE Site: Hints From Outside
Taras Geychenko, Hostmaster LLC
Kaveh Ranjbar, RIPE NCC, told the meeting there was a lot of legacy still existing in the RIPE NCC’s system, and that the first review started with SSO about five years ago. Kaveh said the second and current review is migrating data from the RIPE NCC’s LIR Portal to new system, and that while the RIPE Database has some support for SSO, it is not full support because there is still a lot of legacy in that system. Kaveh then asked for feedback from the community, as all development in these systems is based on that feedback.
Taras told Kaveh the community needs more tips on how to use the site in its current state.
Kaveh suggested that the audience, when using the site, to think about their own security model and map that to reality – for example, if you are one organisation, use one org object. Another example is to match your role accounts to real people in your organisation. Kaveh also suggested people enable two-factor authentication, as it is important to avoid attacks in this way.
Plenary 12:00 – 13:30
The Case for National CERT/CSIRTs
DDoS Attacks in 2017: Beyond Packet Filtering
Artyom Gavrichenkov, Qrator Labs
IANA Function Transition Roundtable:
IANA Stewardship Transition: Evaluation of the process and outcomes for the Internet community
Oleg Demidov, PIR Center
NTIA Stewardship Transition: Latest update and lessons learnt
Michael Yakushev, ICANN
Plenary 15:00 – 16:30
RIPE NCC Update
Axel Pawlik, RIPE NCC
Vahan Hovsepyan, Armix, asked Axel if he saw a RIPE Meeting in Armenia in the near future.
Axel said the RIPE NCC tries to get around the service region as much as possible. The RIPE Meeting requires a venue for 500-600 people.
Vahan said Armenia would host WCIT next year.
Axel agreed that perhaps the RIPE Meeting could fit in Armenia in the future.
Internet Roads of Caucasus
Alexander Azimov, Qrator Labs
- Moderator: Alexander Isavnin, The Open Net
Martin Semrad, NIX.CZ / NIX.SK
Vahan Hovsepyan, Armix
George Gotoshia, Newtelco Georgia
Eugene Morozov, MSK-IX
Closing Plenary, 17:00 – 18:30
Country Connectivity in ENOG Region
Alexander Isavnin, The Open Net
Kaveh Ranjbar, RIPE NCC, told the audience about a new prototype called “country statistics” being developed by the RIPE NCC, and asked for feedback on what specific data people would like to see from this function.
Dmirtry Kohymanyuk, Hostmaster Ltd, suggested Kaveh send a link to one or more of the RIPE mailing lists.
Alexander Isavnin, the Open Net, told the audience the RIPE NCC is a neutral organisation to collect data. He went on to say that the audience has knowledge of local markets that are interesting at a local level, but not necessarily at an international level.
Non-Optimal Routing Caused by Incompatibility
Talgat Nurlybayev, Kazakhstan Research and Education Network Association
IoT BS: Where do “we” fit in?
Richard Lamb, ICANN
This post is also available in: Russian