zanog-discuss September 2026

zanog-discuss@lists.nog.net.za

3 participants
3 discussions

Reminder : ZANOG-KZN : 1 October 2026 @ 18h00
by donald＠nog.net.za 30 Sep '26

30 Sep '26

Hi All Reminder if you have not yet registered for the last in-person event in KZN for the year. Event: ZANOG-KZN When : Thursday, 1 Oct 2026 18:00 – 22:00 Where: Westville Country Club, Durban, South Africa Cost : Free RSVP : https://events.nog.net.za/event.php?slug=zanog-kzn-oct-26 Talk1 : Beyond Monitoring : Sphamandla Dlamini Talk2 : Disconnected South What happens if ZA looses subsea capacity : Edd de Lange Looking forward to seeing you there!

1 0

PCH 2026 global peering survey
by Bill Woodcock 29 Sep '26

29 Sep '26

tl;dr: the survey is at https://pch.net/survey Background: Every five years, beginning in 2011, PCH has conducted a comprehensive global survey characterizing Internet peering agreements. They are the only ones of their kind, and are relied upon not only by network operators, but also by legislators and regulators throughout the world to understand the Internet interconnection landscape. Our write-ups of the prior surveys can be found here: https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011… https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2016… https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2021… …and video of the NANOG presentation of the 2016 results is here: https://www.youtube.com/watch?v=lPuoBmxyXMc At the time of the 2011 survey, we committed to repeating the survey every five years, to provide time-series data about the direction peering trends take. We’re now conducting the fourth iteration of the survey. Among other things, the surveys have helped establish a better understanding of trends in: • The increasingly uniform global norms of interconnection • National preferences within the network operator community for country of governing law • The long tail of small networks which don’t yet support IPv6 routing • The significance of multilateral peering agreements in the density of the interconnection mesh These findings, particularly the first, have been invaluable in giving regulators in the vast majority of the world’s countries a data-driven basis for refraining from prescriptively regulating Internet interconnection. They have demonstrated in objective terms that the Internet self-regulates in a way that’s more globally uniform and closely harmonized than any coordination of national regulatory bodies could accomplish. Participation: The survey is global in scope, and our goal is to reflect the diversity of peering agreements in the world. Your participation ensures that your norms and ways of doing business are represented accurately and proportionately in the dataset. If you don’t participate, the way you do business will be less well-represented in the data, and will seem less normal to regulators and policy-makers. We’re interested in large ISPs and small ISPs, ISPs in Afghanistan and in Zimbabwe, bilateral agreements and multilateral, private and public. Our intent is to be as comprehensive as possible. In 2011, the responses we received represented 41% of the world’s ISPs, across 96 countries; in 2016, 65% of the world’s ISPs, across 148 countries; in 2021, 76% of the world’s ISPs across 192 countries. Our aim is to be equally inclusive this year. Since our principal method of soliciting participation is via NOG mailing lists, I’m afraid many of you will see this message several times, on different lists, for which we apologize in advance. Privacy: In 2011, 2016, and 2021, we promised to collect the smallest set of data necessary to answer the questions, to perform the analysis immediately, and not to retain the data after the analysis was accomplished. In that way, we ensured that the privacy of respondents was fully protected. We did as we said, no data was leaked, and the whole community benefited from the trust that was extended to us. We ask for your trust again now as we make the same commitment to protect the privacy of all respondents, using the same process as was successfully employed the last three times. We are asking for no more data than is absolutely necessary. We will perform the analysis immediately upon receiving all of the data. We will delete the data once the analysis has been performed. The Survey: We would like to know your Autonomous System Number, and the following five pieces of information relative to each other AS you peer with: • Your peer’s ASN (peers only, not upstream transit providers or downstream customers) • Whether a written and signed peering agreement exists (the alternative being a less formal arrangement, such as a "handshake agreement") • Whether the terms are roughly symmetric (the alternative being that they describe an agreement with different terms for each of the two parties, such as one compensating the other, or one receiving more or fewer than full customer routes) • What jurisdiction of governing law is defined, if any • Whether IPv6 routes are being exchanged (this year, we’ll still assume that IPv4 are) The easiest way for us to receive the information is as a tab-text or CSV file or an Excel spreadsheet, consisting of rows with the following columns: Your ASN: Integer Peer ASN: Integer Written agreement: Boolean [true,1,yes,y] or [false,0,no,n] Symmetric: Boolean [true,1,yes,y] or [false,0,no,n] Governing Law: ISO 3166 two-letter country-code, or empty IPv6 Routes: Boolean [true,1,yes,y] or [false,0,no,n] For instance: 42 <tab> 715 <tab> false <tab> true <tab> us <tab> true <cr> 42 <tab> 3856 <tab> true <tab> true <tab> us <tab> true <cr> We need the ASNs so we can avoid double-counting a single pair of peers when we hear from both of them, and so that when we hear about a relationship in responses from both peers we can see how closely the two responses match, an important check on the quality of the survey. As soon as we've collated the data, we'll strip the ASNs to protect privacy, and only the final aggregate statistics will be published. We will never disclose any ASN or any information about any ASN. We'd like to finish collecting data in the first week of October, about two weeks from now. If you’re peering with an MLPA route-server, you’re welcome to include just the route-server’s ASN, if that’s easiest, rather than trying to include each of the peer ASNs on the other side of the route-server. Either way is fine. If all of your sessions have the same characteristics, you can just tell us what those characteristics are once, your own ASN once, and give us a simple list of your peer ASNs. If your number of peers is small enough to be pasted or typed into an email, rather than attached as a file, and that’s simpler, just go ahead and do that. If you have written peering agreements that are covered by non-disclosure agreements, or if your organizational policy precludes disclosing your peers, but you’d still like to participate in the survey, please let us know, and we’ll work with whatever information you’re able to give us and try to ensure that your practices are statistically represented in our results. If you're able to help us, please email me the data in whatever form you can. If you need a non-disclosure, we're happy to sign one. Finally, if there are questions you’d like us to try to answer when we analyze the data, please suggest them, and if there are any additional questions you’d like us to include in future iterations of the survey, please let us know so that we can consider including them in the 2031 survey. Please respond by submitting your survey at https://pch.net/survey or emailing it to me directly (woody(a)pch.net, not replying to the NOG mailing list), by the second week of October. Thank you for considering participating. We very much appreciate it, and we look forward to returning the results to the community. -Bill Woodcock Secretary General Packet Clearing House

1 0

call for volunteers - INX Management Committee (2026-2028)
by Nishal Goburdhan 02 Sep '26

02 Sep '26

[with apologies if you receive multiple copies] Hello everyone, INX-ZA operate community-run Internet exchange points, with the management committee elected from the general Internet community. We hold annual elections to elect new members to the management committee for a 2year term. This is your chance to contribute to the management and operations, of these 100% community operated IXPs, to grow a better peering environment for yourselves. Elected persons are natural persons; ie. they do not represent any particular organisation, and they do not have to be from a participating network at any of the INXes, nor from any particular geography. It is expected that volunteers have a legitimate interest in improving the peering landscape. The terms of reference for INX committee members, is available online at https://www.inx.net.za/display/pub/INX+Committee. Committee member usually meet online once a month, to set policy and provide managerial oversight to the INXs' operations. Committee members may also meet in person, up to twice a year. Are you, or someone else at your organisation willing to stand as a candidate for INX-ZA’s Management Committee for 2026-28? If you'd like to suggest someone, or even nominate yourself, please indicate as follows: I'd like to suggest the following potential candidate: Name: Email address: Have you checked if this person is willing? [ ] Yes [ ] Not yet Is there perhaps someone whom you think INX-ZA should approach to potentially serve on the Management Committee? I'd like to suggest the following potential candidate: Name: Email address: Have you checked if this person is willing? [ ] Yes [ ] Not yet If you feel up to the challenge, and want to contribute to the peering community, please reply to inxcom26(a)inx.net.za, by 23h59 UTC 19 September 2026. Elections will be held online, with details to follow. -- Nishal Goburdhan INX-ZA

1 0

2026

2025

2024

zanog-discuss September 2026