- discuss - enog-apps-2.ripe.net

Reminder: RACI Applications Close on Sunday
by Gergana Petrova 12 Feb '19

12 Feb '19

Dear colleagues, The RIPE Academic Cooperation Initiative (RACI) is accepting applications from students, academics and researchers until this Sunday, 17 February: https://www.ripe.net/raci Successful applicants receive complimentary tickets, travel and accommodation to our upcoming meetings. They will have the opportunity to present their research to attendees who are leaders within the Internet community. You can apply for the following two meetings by submitting an abstract and draft slides by 17 February: RIPE 78 (20-24 May, Reykjavik) ENOG 16 (3-4 June, Tbilisi) At ENOG 16 you can present in either English or Russian. Examples of relevant research topics include: - Network measurements and analyses - IPv6 deployment - BGP routing - Network security - Internet governance - Peering and interconnectivity - Internet of Things RACI mailing list: https://www.ripe.net/raci/mailing-list Twitter: https://twitter.com/raci_ripe RACI LinkedIn Group: https://www.ripe.net/raci/linkedin You can help by spreading the word to your academic networks. For any questions about the initiative or about applying, please email me back. Best regards, Gergana Gergana Petrova External Relations RIPE NCC

1 0

IEEE 802.3 Ethernet Bandwidth Assessment
by John DAmbrosia 08 Feb '19

08 Feb '19

All, I am chairing the IEEE 802.3 New Ethernet Applications ad hoc, which has an activity underway that is looking at doing an update to the IEEE 802.3 Ethernet Bandwidth Assessment (see http://www.ieee802.org/3/ad_hoc/bwa/BWA_Report.pdf) published in 2012. Please note that this effort will focus on gathering information throughout 2019 that will enable an evaluation of the future bandwidth needs of various Ethernet wireline applications. If anyone has any information that they believe is pertinent to this assessment that they would like to share, please contact me. The webpage for the new Bandwidth Assessment Ad hoc is http://www.ieee802.org/3/ad_hoc/bwa2/index.html. The ad hoc wrote a request for information that can be found at http://www.ieee802.org/3/minutes/sep18/outgoing/IEEE_802d3_to_ALL_BWA_0918.p df. Please note that you don't need to attend an IEEE 802.3 meeting to present this data, it can be done via teleconference. Regards, John D'Ambrosia Chair, IEEE 802.3 New Ethernet Applications Ad hoc.

1 1

Upcoming RIPE NCC organised events
by ENOG 06 Feb '19

06 Feb '19

Dear colleagues, Block your calendars and book your flights! We’re pleased to share the calendar of our upcoming events, including RIPE Meetings and more. If you would like to present at our events, please do take a look at the call for presentations. --------------------------------------------------------------------- April 2019: MENOG 19, RIPE NCC Day and SEE 8 --------------------------------------------------------------------- *MENOG 19 Meeting & Peering Forum: Beirut, 3-4 April 2019* Call for Presentations and registration are now open! https://www.menog.org/meetings/menog-19/ *RIPE NCC Day: Moscow, 9 April 2019* Call for Presentations and registration are now open! https://www.ripe.net/ripe-ncc-day-moscow *SEE 8: Sarajevo, 16-17 April 2019* Call for Presentations and registration are now open! https://www.ripe.net/see-8/ --------------------------------------------------------------------- May 2019: RIPE 78 --------------------------------------------------------------------- *RIPE 78: Reykjavík, 20-24 May 2019* Call for Presentations and registration are now open! https://ripe78.ripe.net/ --------------------------------------------------------------------- June 2019: ENOG 16 --------------------------------------------------------------------- *ENOG 16: Tbilisi, 3-4 June 2019* Call for Presentations and registration are now open! https://www.enog.org/enog-15/ --------------------------------------------------------------------- September 2019: RIPE NCC Regional Meeting --------------------------------------------------------------------- *RIPE NCC Regional Meeting: Kiev, 24-25 September 2019* Call for Presentations and registration are now open! https://www.ripe.net/regional-meeting-kiev --------------------------------------------------------------------- Next RIPE Meetings --------------------------------------------------------------------- *RIPE 79: Rotterdam, 14-18 October 2019* *RIPE 80: Berlin, 11-15 May 2020* --------------------------------------------------------------------- If you need any further information or if you are interested in sponsoring any of the above events, please do get in touch with the meetings team at <meeting(a)ripe.net>. We look forward to seeing you! Best regards, Martina de Mas Event Organiser RIPE NCC

1 0

RIPE NCC Day Moscow, 9 April 2019: Registration Now Open
by Sandra Gijzen 28 Jan '19

28 Jan '19

<Версия на русском языке ниже> Dear colleagues, We're pleased to announce that the RIPE NCC Day will take place at the Lotte Hotel in Moscow on Tuesday 9 April 2019. We would like to thank our hosts MSK-IX and Coordination Center for TLD RU/РФ for supporting this meeting and are glad to join the celebration of 25 years of domain .RU The RIPE NCC Day is open for anyone to attend, and attendance is free of charge. You can register for this meeting at: https://www.ripe.net/s/ripe-ncc-day-moscow-2019 The goals of this meeting are to: * Encourage cooperation among operators in this region and facilitate an open dialogue about issues that affect them * Enable the RIPE NCC to further support Local Internet Registries (LIRs) in this region * Present the latest developments in the Internet industry and identify, discuss and solve the specific issues that affect operators working in this region The meeting agenda will consist of plenary presentations, as well as long coffee breaks, lunches and an evening social event on 9 April, thanks to which there will be ample opportunities for attendees to network with one another. We are seeking content proposals from the community for presentations, panels sessions and lightning talks at RIPE NCC Day in Moscow: https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-day-mo… Please submit your talk in English, including the abstract and draft version of the slides, before 16 February 2019. Please check back regularly for the latest information at: https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-day-mo… We look forward to meeting you and your colleagues in Moscow! Regards, Sandra Gijzen On behalf of the RIPE NCC Regional Meeting Team ______________________________ ______________________________ <Версия на русском языке ниже> ______________________________ Уважаемые коллеги, Мы рады сообщить, что во вторник 9 апреля 2019 года в Лотте Отеле в Москве пройдет День RIPE NCC. Мы благодарим наших партнеров MSK-IX и Координационный центр национальных доменов .RU и .РФ за поддержку в организации мероприятия и рады присоединиться к празднованию 25-летия домена .RU. День RIPE NCC открыт для всех желающих. Вы можете бесплатно зарегестрироваться по ссылке: https://www.ripe.net/s/ripe-ncc-day-moscow-2019 Цель этой встречи: * Способствовать сотрудничеству между операторами в регионе и содействоватьnоткрытому диалогу по актуальным для них вопросам; * Предоставить возможность для дальнейшей поддержки локальных интернет-регистратур (LIR) со стороны RIPE NCC; * Представить последние разработки в интернет-индустрии и обсудить вопросы, которые влияют на работающих в регионе операторов. На протяжении дня вас ожидают пленарные доклады, a также перерывы на кофе, обед и неформальный вечерний прием, где вы сможете пообщаться друг с другом в непринужденной обстановке. Мы объявляем прием докладов от членов сообщества для участия в пленарных заседаниях, презентациях и блиц-докладах. Если вы хотите предложить свой доклад, предоставьте пожалуйста тезисы доклада и черновой вариант презентации на английском языке до 16 февраля 2019 года здесь: https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-day-mo… Информация о мероприятии будет регулярно обновляться на этой странице: https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-day-mo… Мы с нетерпением ждем встречи с вами и вашими коллегами в Москве! С Уважением, Сандра Гейзен От имени Региональной команды RIPE NCC

1 0

Приём заявок на ENOG 16 - Тбилиси, Грузия, 3-4 июня 2019.
by Alex Semenyaka 21 Jan '19

21 Jan '19

Уважаемые коллеги! Мы объявляем прием докладов для выступления на конференции ENOG 16, которая пройдет в Тбилиси 3-4 июня 2019 года. Этот документ доступен по адресу: http://www.enog.org/enog-16/cfp/ Для участия с докладом в пленарной части конференции или семинаром просим вас прислать тезисы не позднее 19 апреля. Обращаем ваше внимание, что 10 марта 2019 является датой окончания принятия первоочередных заявок. Доклады, поданные до этой даты, будут оценены Программным комитетом до 25 марта. Главными темами ENOG являются технологии интернет, передовые подходы к управлению сетями, взаимодействие сетей, а также вопросы сотрудничества и координации между игроками рынка. Интересны доклады о проблемах, инструментах, опыте работы и тенденциях в следующих областях: * Тенденции развития интернета - Новые технологии и приложения, развитие интернет-экосистемы - Анализ развития интернета * Вопросы координации и управления интернетом - Законодательство и его влияние - Общественные инициативы и проекты в области внедрения новых технологий, изучения и координации операторов сетей * Сетевое взаимодействие: пиринг и точки обмена трафиком - Коммерческие, технические и социальные аспекты сетевого взаимодействия * Работа сети и безопасность - Рекомендуемые подходы, инновационные подходы, обзоры угроз и рабочий опыт - Технологии и тенденции в области обеспечения безопасности * Ключевые интернет- и сетевые технологии - Последние разработки - Опыт внедрения (например, IPv6 и DNSSEC) и статистика * Доставка контента (CDN) - Технологии, архитектура и бизнес-модели Если вы хотите предложить свой доклад для включения в программу ENOG 16, пожалуйста, предоставьте тезисы доклада и черновой вариант презентации с помощью онлайн-системы: http://www.enog.org/submit-topic/submission-form/. Докладчики должны указать, сколько времени требуется на доклад. Обычно время выделяется согласно формату доклада: - Пленарный доклад: 20-25 минут презентации и 5-10 минут обсуждения - Учебные курсы и мастер-классы: до трех часов (утро понедельника) - BoF-сессия: приблизительно один час в вечернюю сессию - Блиц-доклад: 10 минут всего на презентацию и обсуждение В случае возникновения сомнений, к какому формату относится ваш доклад, не стесняйтесь образаться за уточнениями в Программный комитет. Правила подачи заявок и форматы презентаций опубликованы на http://www.enog.org/enog-16/cfp/submission-guidelines/ Тезисы и доклады принимаются на русском и английском языках. Во время конференции обеспечивается синхронный перевод всех пленарных докладов. Доклады рекламного или коммерческого характера не принимаются. Если вы можете порекомендовать интересный доклад и докладчика, пришлите свое предложение в Программный комитет по адресу pc(a)enog.org. -- С уважением, Алексей Семеняка, от имени Программного комитета ENOG

1 0

ENOG 16 Call for Presentations - Tbilisi, Georgia on 3-4 June 2019.
by Alex Semenyaka 21 Jan '19

21 Jan '19

Dear colleagues, The ENOG 16/RIPE NCC Regional Meeting will take place in Tbilisi, Georgia on 3-4 June 2019. The call for presentations is now online: http://www.enog.org/enog-16/cfp/ Please submit your talk, including the abstract and draft version of the slides before April, 19 for full consideration. Please note that March 10, 2019 is the priority submission deadline: submissions filed before this date will be evaluated by the Program Committee before March 25. Traditionally, key themes for ENOG are peering, operational practices, interconnection and collaboration between Internet service providers (ISPs). We welcome presentations on challenges, tools, experiences and best practices in the following areas: * Internet Development Trends - New technologies and applications, the evolution of the Internet ecosystem - Analytics and prediction of Internet development * Internet Coordination, Governance, and Regulatory Practices - Internet-related legislation and its impact, multistakeholder model, challenges and opportunities - Public initiatives and projects in the areas of Internet governance and coordination, research and deployment of new technologies * Peering and Internet Exchange Points - Business, technical and social aspects of peering and interconnection * Network Operations and Security - Operational experience and best current practices, security trends and technologies, threats overview * Key Internet and Networking Technologies - Bleeding edge development - Real-life deployment experience (eg. for IPv6 and DNSSEC), trends, and statistics * Content Delivery - Technology, architecture and business models If you’d like to suggest a presentation for the ENOG 16 agenda, please submit your talk via the online form: http://www.enog.org/submit-topic/submission-form/ Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minute presentation with 5-10 minute discussion - Tutorials and Workshops: Up to three hours (Monday morning) - BoFs: Approximately one hour during evening sessions - Lightning talks: 10 minutes total for both presentation and any discussion Feel free to ask the Program Committee when not sure which format is more appropriate for your submission. For submission guidelines please see: http://www.enog.org/enog-16/cfp/submission-guidelines/ Please submit your proposal in English or Russian. Presentations can be given in either language as we use simultaneous translation. Please note that marketing or commercial content will not be accepted. If you are aware of a good presentation and would like to recommend the speaker, please contact the Programme Committee at <pc(a)enog.org>. -- Best regards, Alex Semenyaka On behalf of the ENOG Programme Committee

1 0

IANA AS Numbers Registry Update
by Selina Harrington 07 Dec '18

07 Dec '18

Hi, The IANA AS Numbers registry has been updated to reflect the allocation of the following blocks to LACNIC: 268701-269724 Assigned by LACNIC 2018-12-07 269725-270748 Assigned by LACNIC 2018-12-07 You can find the registry at: https://www.iana.org/assignments/as-numbers/ The allocation was made in accordance with the Policy for Allocation of ASN Blocks to Regional Internet Registries: https://www.icann.org/resources/pages/global-policy-asn-blocks-2010-09-21-en Best Regards, -- Selina Harrington Lead IANA Services Specialist

1 0

Network Atlas 2018 Final Update
by Mehmet Akcin 02 Dec '18

02 Dec '18

Dear ENOG Friends, The final month of 2018 is going to be a busy one for Network Atlas <https://www.networkatlas.org/>, and while I still have a few spare hours, I wanted to share some exciting updates and address a few questions. First, I would like to thank all the people who believe in Network Atlas and have helped it get to where it is today. Network Atlas is at its heart a community concept, and it is energizing to see so many of you excited about its potential and interested in making it better. To that end, the Network Atlas team will be spending the next month working feverishly to improve the product and get it ready for 2019. I am very excited to announce the following list of features that should come online early next year: 1. Cable system operation status allows users to see which segments are up/down/partial and their last outage, along with textual details of previous outages with potential for links 2. Cable system information - length, activation date, and estimated end-of-life 3. Fast page load time of <5 secs for users within the US 4. 3D data center locations 5. “Buy capacity” - a form that generates an email to a specified cable owner 6. Report-an-issue on routes for users to send feedback 7. Ability for users to receive email notifications about cable status changes ,Option to show subsea cables only , Option to show active cables only, Option to show future cables only 8. A Time Machine function that will show cables that will be active in the future 9. Ability to add custom fields in select or all cables to show information such as latency3-tiered Network Atlas Cable 10. Management UI: Users can:Add/Delete/Replace I can’t wait to share this next phase of Network Atlas with you all. Once it’s complete, it will truly be “one map to rule them all.” Next up, let me address the elephant in the room. As many of you know, Network Atlas’ Kickstarter for $100K for 2019 funding came up short of meeting its goal(we cancelled it before the time because many of you reached out wanting to support directly not via Kickstart). However, it was an excellent learning experience, as it provided a chance to interact with potential donors and hear their questions. One of those questions was if Network Atlas could show its 3-year plan for the project. In the interest of transparency, I would like to share with you Network Atlas’ proposed 3-year operating budget as of today. You can see this as details in our blog - https://www.networkatlas.org/blog/eoy2018 Month of December, we will freeze adding new fiber routes to Network Atlas, this will allow us to focus on working the 10 feature we have explained above. If you want to upload fiber routes you own and authorized, feel free to go to https://kmzs.networkatlas.org <https://kmzs.networkatlas.org/> and upload them and please include your email address in the file name (or create a colder with readme in it) so we can reach back with questions. Our self-service portal will solve this issue in January :) Now this is not the end. It is not even the beginning of the end. But it is, perhaps, the end of the beginning. Have a wonderful December, and a happy new year! ps: we added some routes in Brazil , go check them out https://dev.networkatlas.org Mehmet

1 0

RACI: Call for Applications
by Gergana Petrova 20 Nov '18

20 Nov '18

Dear colleagues, The RIPE Academic Cooperation Initiative (RACI) is again looking for talented academics in the field of Internet technology. Successful applicants receive complimentary tickets, travel and accommodation to the meetings and the opportunity to present their research. If you are working on something interesting, please apply! If you know someone in your network who is, please forward them this message. https://www.ripe.net/raci --------------------- Application deadlines --------------------- MENOG 19, (TBC): apply by 3 February 2019 SEE 8 (16-17 April, Sarajevo): apply by 3 February 2019 RIPE 78 (20-24 May, Reykjavik): apply by 17 February 2019 ENOG 16 (3-4 June, Tbilisi): apply by 17 February 2019 At ENOG 16 you can present in either Russian or English. --------------------------- Examples of relevant topics --------------------------- - Network measurements and analyses - IPv6 deployment - BGP routing - Network security - Internet governance - Peering and interconnectivity - Internet of Things ------------------------------------------------- Get the latest news on RACI and Internet research ------------------------------------------------- - Subscribe to the RACI mailing list: https://www.ripe.net/raci/mailing-list - Follow us on Twitter: https://twitter.com/raci_ripe - Join our group on LinkedIn: https://www.ripe.net/raci/linkedin Please let me know if you have any questions. Have a lovely day! Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC

1 0

Fwd: Policies and Guidelines for Assignments for Network Infrastructure and End User Networks
by Töma Gavrichenkov 06 Nov '18

06 Nov '18

FYI ---------- Forwarded message --------- From: Töma Gavrichenkov <ximaera(a)gmail.com> Date: Mon, Nov 5, 2018 at 3:36 PM Subject: Policies and Guidelines for Assignments for Network Infrastructure and End User Networks To: <address-policy-wg(a)ripe.net> Cc: <db-wg(a)ripe.net> Hello WG (both, actually), A recent case of a Russian broadband ISP, roughly 6th in size in the country, exposing the personal data of their individual VIP customers by posting said data to RIPE DB(*) highlighted an important issue in RIPE-708, 6.2 "[policies and guidelines for assignments for] Network Infrastructure and End User Networks"(**). To quote: > IP addresses used solely for the connection of an End User to a service provider (e.g. point-to-point links) are considered part of the service provider's infrastructure. These addresses do not have to be registered with the End User's contact details but can be registered as part of the service provider's internal infrastructure. > When an End User has a network using public address space this _must_ be registered separately with the contact details of the End User. Where the End User is an individual rather than an organisation, the contact information of the service provider may be substituted for the End Users. (note the "must", we'll soon get back to it) While it's out of question that posting individual users' personal data to RIPE DB is insane, what's interesting is that small business owners(***), when aware of the leak, seem to also be concerned that their B2B broadband data contract apparently included a clause they've missed, and their mobile telephone number is now published to a public database on the Internet, and, you know, one cannot simply remove an information from the Internet which is already there. But when we try to rely on 6.2 for a definitive advice, we don't get any: - There's no definition of what is exactly meant under "point-to-point links" (PTPL). Some speculate it's a historical term from the times of PPP/SLIP, meaning just "end-user access links", and, as such, includes individual and SMB customer links. Other read it as those IPv4 /30s ASes waste all the time for BGP session establishment, and argue that what's really meant by PTPL is just the IP addresses never ever communicating with the world outside of their own local net (BGP sessions included, SMB access obviously not included). (Personally, the second opinion looks more convincing for me, because this way only those IP addresses which never send or receive packets from the Internet may lack a proper abuse-c, which makes sense, and I like when things make sense, so. But at the same time the first opinion is backed by people I respect.) Anyway, RIPE-708 fails to provide an answer. - Another scary term is "a network using public address space" (NUPAS). Is IPv4 /32 a network? What about /31? What's "using public address space" after all, there's no doubt we won't report our usage of 192.168.0.0/16 to RIPE DB. This sentence was meant to clear our concerns but it just adds up to them. What is also meant to help us but adds to the mess is the RIPE NCC Local Internet Registry Training Course(****), slides 94-95: - Somehow, training material includes more specific definitions and corner cases (e.g. "points of presence") than the policy does. Is it only me, or such a thing should never ever happen? A policy training course must not be different from the policy itself, no matter if the difference is in being either more strict of more relaxed. If an NCC trainer just knows more about the subject than is stated in a policy, they'd better report to the WG first that the policy lacks an important consideration. - However, those definitions don't really clarify what's PTPL and NUPAS are, too. - Slide 95 is even better: it says there's a grey area around. Well, it might be again only me, but personally I feel very uncomfortable seeing "must" and "grey area" in the same sentence. If there's a grey area in an area, it must be "should" there, not "must". - There's apparently a border line between "when the End User has a few addresses out of a larger address block" and "If the End User has a separate subnet". Now again, (an occasional?) /31 is a subnet or just a few addresses? Who's going to check ISPs against this strict ("must") requirement, and how? - What if there's a customer with an pizza store (so, an office within their location) and their own equipment (Mikrotik) connected to a broadband pool? - What if a broadband customer sets up an HTTP server on their point-to-point link's public v4 address and starts serving whatever children drug suicide abuse torrents they have. All in all, RIPE-708 6.2 is a perfect example of an imperfect policy, too strict and too vague at the same time. Which is bad, because a) some ISPs would just prefer to ignore it, no matter the "must", and would be paying less attention to other "musts" they would encounter in other policy documents, b) those ISPs who would choose to be responsible about RIPE DB usage risk losing customers and wouldn't be able to defend their attitude against the customers, let alone courts, based on the RIPE DB policy. So here are two separate things I propose, and I'd prefer them to be discussed and evaluated separately: 1) Ask the author of LIR training material to provide the WG (both) with the historical insight on what was meant in 6.2, and how's that supposed to work. Afterwards, after a heated discussion on the mailing list (both), make a decision and amend a policy towards either a more relaxed, or a more constraining fashion, but do either of things anyway, as there's no SLIP anymore, and such an irresponsible wording of a policy as it stands today undermines the trust in policy process, especially in some Eastern European and Northeast countries where there's hardly any trust even now. My personal suggestion is that the only border line that should be there is between businesses/organizations with public IP addresses, on one side, and individual users/NAT pools, on the other. If a company is using a public IP address space for any purpose at all, it must publish at least an abuse-c contact to a public IP database. Fair enough IMO. 2) Change 6.2 to reflect the fact that the contact information of End Users who are individuals not MAY, but rather MUST be substituted with the contact data of the service provider. This perfectly reflects currently ongoing legislation trends as well as a concern in the society at large, and also would be seen as a responsible attitude of an ISP community towards the personal data safety — an attitude the ISP community hardly used to show before. (*) — https://www.bbc.com/russian/news-46083410. Here's a Google Translate link for your convenience: https://translate.google.com/translate?sl=ru&tl=en&js=n&u=https%3A%2F%2Fwww… (**) — https://www.ripe.net/publications/docs/ripe-708#62 (***) — My definition of a "small business" here might seem too broad, but if's fully grounded: e.g. Main Directorate for Drugs Control of the Ministry of Internal Affairs of Russia, as a business, is definitely not so big; Alfa Bank is a large bank in Russia but Russian banking system is comparatively small when compared to the rest of the world; etc. (****) — https://www.ripe.net/support/training/material/lir-training-course/lir-slid… | Töma Gavrichenkov | gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191 | mailto: ximaera(a)gmail.com | fb: ximaera | telegram: xima_era | skype: xima_era | tel. no: +7 916 515 49 58

1 0