zanog-discuss July 2026

zanog-discuss@lists.nog.net.za

2 participants
2 discussions

Registration Opens for AFRINIC IPv6 & RPKI Deployathon in Johannesburg
by Willy Manga 17 Jul '26

17 Jul '26

Dear colleagues, AFRINIC in collaboration with All ISPs Matter is organising a Deployathon in Johannesburg from 04 to 06 August 2026. AFRINIC has 662,272 IPv4 addresses left in its available pool. This, as you can tell, is grossly inadequate to meet Africa’s current IP address needs, making IPv6 the only sustainable way to continue to grow the potential of the Internet in Africa. In 2018, we designed and organised the world’s first Deployathon as a mechanism to bridge the gap between learning about IPv6 and actually implementing it. Since its inception we’ve run 17 (e-)Deployathons with 224 organisations from 26 countries participating. They were able to accomplish 241 deployment milestones; among them : - 50 valid route6 object - 45 address plans in IPAMS - 32 validated RPKI ROA objects - 24 advertised IPv6 prefix - 21 Initial address plan - 16 IPv6 prefix PI - 12 IPv6-enabled core - 9 IPv6 from test VLAN - 8 IPv6 domain objects - 4 IPv6-enabled DNS - 3 IPv6-enabled customer We invite you to register for the upcoming Deployathon in Johannesburg. If selected, you will get the same step-by-step guidance, tools, and techniques we have perfected in 17 (e-)Deployathons, and +100 helpdesk calls to help realise your IPv6 deployment project for your organisation. This is clearly a measurable step forward in accordance with your network change management processes. Date: 04 August - 06 August 2026 Time: 9:00 AM to 4:00 PM local time Main Language: English Eligibility: Qualified engineers based in Johannesburg or able to travel to Johannesburg in that period. If you are an engineer who runs a network and believes that you can make one concrete visible step towards IPv6 deployment (or advance your stalled IPv6 deployment) for your organisation , apply for a spot here [ https://learn.afrinic.academy/?fluent-form=78 ] - (Only 30 spots available) Deadline for application: *27 July 2026*. For more information and queries about Deployathons, please contact: do(a)afrinic.net Sincerely, -- Willy MANGA AFRINIC Team t: +230 403 51 00 | f: +230 466 6758 | tt: @afrinic | w: www.afrinic.net

1 0

RTBH Support Across the Industry
by James Bensley 07 Jul '26

07 Jul '26

Dear Community, We see that RTBH is not as effective as it could be, for various reason, just a few include: * Not all networks support RTBH. * Networks that do support RTBH implement it differently to each other. * There is no one place where one can easily find the info for how to use RTBH with a given network. * Operators have different ideas about how / when / where / why someone should / shouldn’t use RTBH. To this end, we have created the first of two surveys. This first one is quantitative and captures how networks have implemented RTBH and provides (1) a public repository which anyone can use to look-up the RTBH details for their peers/upstreams, and (2) an insight into the (mis-)alignment of RTBH implementations across the industry. Please take the time to fill out the short survey for your own network (even if you don’t support RTBH!), and if you can, please fill it out for other networks where you know how they have implemented RTBH (e.g., peers you use RTBH with): https://docs.google.com/forms/d/e/1FAIpQLScg2Bvr_14onOtZRdoK2SNd0kCHFtqsdw-… (^ No login required) The data ends up in this public repository (you can of course make a pull request directly if you want): https://remotely-triggered-black-hole.github.io/rtbh/ The second survey we are working on will be qualitative, to gather information from the industry community on why you do / don’t support RTBH, when do you use it, how do you think the routing should be secured, etc. The long term goal is to use the data from both surveys as input in to a community effort to improve RTBH alignment across the industry and improve it’s effectiveness for all (e.g. maybe we produce a new BCOP for implementing RTBH, or usage guidelines for blackholing, or maybe a new RFC is required to secure the filtering; regardless, the first step is to gather data about the status quo and review that data to get a baseline of where we are at today). Any questions, please let me know, and thank you for your time and help, it is appreciated. With kind regards, James.

1 0

2026

2025

2024

zanog-discuss July 2026