<div dir="auto"><div dir="auto">Hi Jaco,</div><div dir="auto"><br></div><div dir="auto">I do not accept that every operational decision requires a new policy. AFRINIC necessarily makes technical and service-management decisions every day.</div><div dir="auto"><br></div><div dir="auto">Policy should define narrow, objective boundaries such as uniqueness, proof of control, registry accuracy, security, and continuity. Staff should implement within those boundaries through a transparent plan, consultation, audit, and review.</div><div dir="auto"><br></div><div dir="auto">If AFRINIC cannot adjust an IRR setting without turning it into binding policy, that is a process defect, not proof that policy is necessary. Otherwise, every database configuration can become a permanent expansion of the mandatory layer.</div><div dir="auto"><br></div><div dir="auto">The question remains: what technical outcome requires policy here that an accountable operational implementation cannot provide?</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Nonhlanhla </div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 5:37 pm <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Policy supremacy (Tshepo Masuku)<br>
2. Re: RPD Digest, Vol 222, Issue 124 (Jaco Kroon)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2026 15:15:02 +0000<br>
From: Tshepo Masuku <<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>><br>
To: "<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>" <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>, "<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>"<br>
<<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>><br>
Subject: Re: [rpd] Policy supremacy<br>
Message-ID:<br>
<<a href="mailto:VI2PR04MB105450597B36C498F79CB8243CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB105450597B36C498F79CB8243CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Hi Ben,<br>
<br>
Introductions can provide context, but they should not become a test of whether someone is a ?genuine? community member.<br>
<br>
An open process cannot presume that familiar participants belong while newcomers must prove themselves. If affiliation disclosure is important, it should be a clear and equal rule covering everyone, including employers, clients, funding, and organisational interests.<br>
<br>
Until such a rule exists, contributions should be judged by their substance and conduct, not by whether the established circle recognises the sender.<br>
<br>
Regards,<br>
Tshepo<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e34847f4/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e34847f4/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jul 2026 17:35:58 +0200<br>
From: Jaco Kroon <<a href="mailto:jaco@uls.co.za" target="_blank" rel="noreferrer">jaco@uls.co.za</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 124<br>
Message-ID: <<a href="mailto:fa79d62b-e4c6-4785-8fc7-fe2868380867@uls.co.za" target="_blank" rel="noreferrer">fa79d62b-e4c6-4785-8fc7-fe2868380867@uls.co.za</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Simply put:<br>
<br>
AFRINIC as RIR may not make operational decisions without relevant <br>
POLICY controlled by community.? As such, if AFRINIC were to implement <br>
contemplated restrictions (by way of operational choice) without <br>
relevant policy, they'd be acting outside of their mandate.<br>
<br>
Kind regards,<br>
Jaco<br>
<br>
On 2026/07/21 13:18, Nia Petronella wrote:<br>
<br>
> Dear Jordi,<br>
><br>
> You are answering whether policy is procedurally permitted. That is <br>
> not the question being raised.<br>
><br>
> The fact that the bylaws and PDP allow a policy does not prove that <br>
> policy is necessary, proportionate, or the best instrument. Likewise, <br>
> the absence of a staff statement saying ?policy is not needed? is not <br>
> evidence that it is needed. Silence cannot manufacture necessity.<br>
><br>
> Kone?s examples remain relevant because they show that the same <br>
> technical outcome can be achieved operationally. The unanswered <br>
> question is what binding policy adds beyond rigidity and registry <br>
> enforcement.<br>
><br>
> A procedural route does not justify itself merely because it is <br>
> familiar. That is how process becomes mandate: the PDP permits policy, <br>
> therefore policy is treated as necessary, and the resulting <br>
> enforcement is then called community authority.<br>
><br>
> Last Call exists precisely to test unresolved concerns, including the <br>
> choice of instrument. Consensus is not protected by declaring that it <br>
> was already reached before those concerns were answered.<br>
><br>
> I therefore support Kone?s questions and remain opposed to the policy <br>
> route.<br>
><br>
> Regards,<br>
> Nonhlanhla<br>
><br>
><br>
><br>
> On Tue, 21 Jul 2026, 1:05 pm <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> wrote:<br>
><br>
> Send RPD mailing list submissions to<br>
> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of RPD digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> ? ?1. Re: RPD Digest, Vol 222, Issue 122 (<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 21 Jul 2026 13:03:53 +0200<br>
> From: "<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
> To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 122<br>
> Message-ID: <<a href="mailto:3071913E-7C72-49BC-BEDD-B7F26DE20A96@consulintel.es" target="_blank" rel="noreferrer">3071913E-7C72-49BC-BEDD-B7F26DE20A96@consulintel.es</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Well ? that?s incorrect. Nobody in the community, neither the<br>
> staff impact assessment, said that a policy is not needed and many<br>
> folks already contested several times, that doing it by means of a<br>
> policy is valid according to the bylaws and PDP and it has not<br>
> been demonstrated by objections that following this path, with is<br>
> the most regular one in AFRINIC, creates any harm or problem.<br>
><br>
> So repeating the argument, by many folks, many times, doesn?t<br>
> demonstrate ?per se" that it is a valid objection to revert the<br>
> already reached consensus. Of course, this is a decision that need<br>
> to be taken by PDP chairs, but this is my view point from an<br>
> exclusive ?procedural? basis.<br>
><br>
> Regards,<br>
> Jordi<br>
><br>
> @jordipalet<br>
><br>
> > El 21 jul 2026, a las 12:46, Fundiswa Nadia Maseko<br>
> <<a href="mailto:fundiswanadia2@gmail.com" target="_blank" rel="noreferrer">fundiswanadia2@gmail.com</a>> escribi?:<br>
> ><br>
> > Dear Jordi,<br>
> ><br>
> > Thank you for your clarification.<br>
> ><br>
> > I understand your point that the proposal has already reached<br>
> consensus and that Last Call is intended to identify any<br>
> weaknesses that may have been overlooked.<br>
> ><br>
> > My concern is precisely that if the choice of mechanism was not<br>
> sufficiently examined during the earlier discussions, then it<br>
> remains a valid point to raise during Last Call. If a proposal<br>
> introduces policy where an operational approach could achieve the<br>
> same objective, that affects whether policy is the appropriate<br>
> solution in the first place.<br>
> ><br>
> > I appreciate that consensus was declared, but consensus does not<br>
> prevent the community from identifying a concern that may not have<br>
> received enough attention. Last Call exists to give the community<br>
> one final opportunity to do exactly that.<br>
> ><br>
> ><br>
> > Kind regards,<br>
> ><br>
> > Fundiswa<br>
> ><br>
> > On Tue, 21 Jul 2026, 12:30 , <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>> wrote:<br>
> >> Send RPD mailing list submissions to<br>
> >> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> >><br>
> >> To subscribe or unsubscribe via the World Wide Web, visit<br>
> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> or, via email, send a message with subject or body 'help' to<br>
> >> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
> >><br>
> >> You can reach the person managing the list at<br>
> >> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
> >><br>
> >> When replying, please edit your Subject line so it is more specific<br>
> >> than "Re: Contents of RPD digest..."<br>
> >><br>
> >><br>
> >> Today's Topics:<br>
> >><br>
> >>? ? 1. Re: RPD Digest, Vol 222, Issue 119<br>
> (<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>)<br>
> >><br>
> >><br>
> >><br>
> ----------------------------------------------------------------------<br>
> >><br>
> >> Message: 1<br>
> >> Date: Tue, 21 Jul 2026 12:29:07 +0200<br>
> >> From: "<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>><br>
> >> To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> >> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 119<br>
> >> Message-ID:<br>
> <<a href="mailto:D895F390-7813-4560-98A7-EEA806F6136A@consulintel.es" target="_blank" rel="noreferrer">D895F390-7813-4560-98A7-EEA806F6136A@consulintel.es</a><br>
> <mailto:<a href="mailto:D895F390-7813-4560-98A7-EEA806F6136A@consulintel.es" target="_blank" rel="noreferrer">D895F390-7813-4560-98A7-EEA806F6136A@consulintel.es</a>>><br>
> >> Content-Type: text/plain; charset="utf-8"<br>
> >><br>
> >> Hi Fundiswa,<br>
> >><br>
> >> Is not a matter of what is practical and what not.<br>
> >><br>
> >> It is a matter that, during the discussion of the policy<br>
> proposal (which is not the same as the Last Call), the community<br>
> reached consensus on making it this way. RIRs follow the same<br>
> procedures for reaching consensus as IETF, this has been said<br>
> several times. The Last Call is a last opportunity to discover any<br>
> weak point in a proposal that already reached consensus, and was<br>
> OVERLOOKED before. Is not about discussing if the proposal should<br>
> be a proposal or an operational decision. This is no longer the<br>
> moment to discuss that (it should have done when the proposal was<br>
> being discussed before reaching consensus), and many folks in this<br>
> discussing are ignoring that, probably because they are not used<br>
> to IETF procedures.<br>
> >><br>
> >> Otherwise, you can remain silent during the proposal<br>
> discussion, during the presentation in the PPM and object to it<br>
> after reached consensus, which is an incorrect procedure.<br>
> >><br>
> >> One more example: we could have asked AFRINIC many years ago to<br>
> write the Soft Landing as an operational thing, instead we as a<br>
> community, decided to make it a policy proposal. Same here.<br>
> However, the community decided to do it as a proposal and it was<br>
> accepted that way at the right time, not in the Last Call.<br>
> >><br>
> >> By the way, I love cooking so from time to time follow some<br>
> documentaries about that. Are you the same person as the famous<br>
> chef? I think I saw you in a TV program some months ago or I?m<br>
> confused.<br>
> >><br>
> >> Regards,<br>
> >> Jordi<br>
> >><br>
> >> @jordipalet<br>
> >><br>
> >> > El 21 jul 2026, a las 12:03, Fundiswa Nadia Maseko<br>
> <<a href="mailto:fundiswanadia2@gmail.com" target="_blank" rel="noreferrer">fundiswanadia2@gmail.com</a> <mailto:<a href="mailto:fundiswanadia2@gmail.com" target="_blank" rel="noreferrer">fundiswanadia2@gmail.com</a>>> escribi?:<br>
> >> ><br>
> >> > Dear Jordi,<br>
> >> ><br>
> >> > Thank you for your response.<br>
> >> ><br>
> >> > I agree that AFRINIC is not required to follow the same<br>
> approach as other RIRs. Every region should make decisions that<br>
> suit its own community.<br>
> >> ><br>
> >> > My point, however, is slightly different. I wasn't suggesting<br>
> that AFRINIC should copy another RIR simply because they did it<br>
> that way.<br>
> >> ><br>
> >> > Rather, I'm asking what specific problem is solved by making<br>
> this a policy instead of implementing it operationally. If both<br>
> approaches achieve the same technical outcome, then what<br>
> additional value does the policy itself provide?<br>
> >> ><br>
> >> > I think that's an important distinction. The fact that the<br>
> community can choose policy doesn't necessarily mean policy is the<br>
> most appropriate mechanism in every case.<br>
> >> ><br>
> >> > I'd be interested to hear what practical or technical benefit<br>
> you believe is only possible through policy and not through an<br>
> operational implementation.<br>
> >> ><br>
> >> > Kind regards,<br>
> >> ><br>
> >> > Fundiswa<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > On Tue, 21 Jul 2026, 11:57 , <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>>> wrote:<br>
> >> >> Send RPD mailing list submissions to<br>
> >> >> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> >> >><br>
> >> >> To subscribe or unsubscribe via the World Wide Web, visit<br>
> >> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> or, via email, send a message with subject or body 'help' to<br>
> >> >> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>><br>
> >> >><br>
> >> >> You can reach the person managing the list at<br>
> >> >> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>>><br>
> >> >><br>
> >> >> When replying, please edit your Subject line so it is more<br>
> specific<br>
> >> >> than "Re: Contents of RPD digest..."<br>
> >> >><br>
> >> >><br>
> >> >> Today's Topics:<br>
> >> >><br>
> >> >>? ? 1. Re: RPD Digest, Vol 222, Issue 111 (Nia Petronella)<br>
> >> >><br>
> >> >><br>
> >> >><br>
> ----------------------------------------------------------------------<br>
> >> >><br>
> >> >> Message: 1<br>
> >> >> Date: Tue, 21 Jul 2026 11:56:49 +0200<br>
> >> >> From: Nia Petronella <<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>>>><br>
> >> >> To: Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a><br>
> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a><br>
> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>>>><br>
> >> >> Cc: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> >> >> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 111<br>
> >> >> Message-ID:<br>
> >> >>? ? ? ?<br>
> ?<CA+mDOg0DqqBO74UVnd9mEr-P=<a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a><br>
> <mailto:<a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a>><br>
> <mailto:<a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a><br>
> <mailto:<a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a>>>><br>
> >> >> Content-Type: text/plain; charset="utf-8"<br>
> >> >><br>
> >> >> Dear Andrew,<br>
> >> >><br>
> >> >> I do not accept the binary you have presented.<br>
> >> >><br>
> >> >> No one is suggesting that AFRINIC should make operational<br>
> changes in secret<br>
> >> >> or without community input. An operational change can be<br>
> published,<br>
> >> >> consulted on, tested, documented, and reviewed. The real<br>
> question is<br>
> >> >> whether that input must be converted into binding policy<br>
> enforced by the<br>
> >> >> registry.<br>
> >> >><br>
> >> >> Calling AFRINIC ?community-driven? does not answer who the<br>
> community is or<br>
> >> >> what it is authorised to bind. A self-selecting group of<br>
> mailing-list<br>
> >> >> participants can provide expertise, support, and objection.<br>
> It does not<br>
> >> >> automatically represent every member, resource holder,<br>
> network, customer,<br>
> >> >> or other affected party.<br>
> >> >><br>
> >> >> The institutional reality also remains unchanged:<br>
> participants discuss the<br>
> >> >> policy, but AFRINIC interprets and enforces it. Community<br>
> participation<br>
> >> >> therefore does not eliminate registry power. It can become<br>
> the language<br>
> >> >> used to legitimise that power.<br>
> >> >><br>
> >> >> This is why Kone?s examples matter. If LACNIC, RIPE NCC, and<br>
> ARIN can<br>
> >> >> achieve the same technical outcome through operational<br>
> mechanisms, then<br>
> >> >> policy is not technically inevitable. Proponents should<br>
> explain what<br>
> >> >> additional technical result binding policy provides, beyond<br>
> converting an<br>
> >> >> IRR setting into an enforceable obligation.<br>
> >> >><br>
> >> >> I also disagree that an objection is valid only if it proves<br>
> immediate<br>
> >> >> operational harm or implementation failure. The choice of<br>
> instrument,<br>
> >> >> proportionality, reversibility, and expansion of enforcement<br>
> authority are<br>
> >> >> legitimate policy concerns. Last Call is not limited to<br>
> asking whether<br>
> >> >> software will break. It must also ask whether the proposed<br>
> power is greater<br>
> >> >> than the problem requires.<br>
> >> >><br>
> >> >> Rough consensus does not require every objection to be<br>
> accommodated. But an<br>
> >> >> objection is not ?addressed? merely because supporters<br>
> repeat that the<br>
> >> >> community prefers policy. That is the very assumption being<br>
> challenged.<br>
> >> >> Procedure cannot be used to prove its own mandate.<br>
> >> >><br>
> >> >> The fact that the RIR system has operated this way for<br>
> decades demonstrates<br>
> >> >> continuity of practice. It does not establish unlimited<br>
> legitimacy of scope.<br>
> >> >><br>
> >> >> I support Kone?s questions and remain opposed to<br>
> AFPUB-2026-ASN-001-DRAFT02.<br>
> >> >><br>
> >> >> Regards,<br>
> >> >> Nonhlanhla<br>
> >> >><br>
> >> >><br>
> >> >><br>
> >> >> On Tue, 21 Jul 2026, 10:26 am Andrew Alston<br>
> <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>><br>
> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a> <mailto:<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>>>> wrote:<br>
> >> >><br>
> >> >> > The answer to this is simple.? AfriNiC is a community<br>
> driven organisation<br>
> >> >> > - and anything done with regard to address allocation and<br>
> management is<br>
> >> >> > done as per policy provided by the community.? It is<br>
> through policy that<br>
> >> >> > the community tells AfriNIC how to do things in regards to<br>
> the allocation<br>
> >> >> > and handling of resources.<br>
> >> >> ><br>
> >> >> > Without policy, the discretion and rules are entirely in<br>
> the hands of the<br>
> >> >> > registry, and the community voice is removed.<br>
> >> >> ><br>
> >> >> > This has been the way the RIR system has operated for?<br>
> decades and it<br>
> >> >> > works.? The community exercises its voice and its right as<br>
> to how things<br>
> >> >> > are done in relation to resource management through policy.<br>
> >> >> ><br>
> >> >> > Arguing that just because something can be done another<br>
> way, is not in my<br>
> >> >> > view a valid argument against policy. Objections to policy<br>
> need to be<br>
> >> >> > technically grounded and demonstrate that the policy would<br>
> either cause<br>
> >> >> > harm or alternatively be impractical to implement.?<br>
> Anything else is simply<br>
> >> >> > arguing that policy should not exist because someone<br>
> doesn?t like AfriNIC<br>
> >> >> > being told how the community wants things done - and that<br>
> isn?t an argument<br>
> >> >> > that I believe rises to the level of a block on consensus.<br>
> >> >> ><br>
> >> >> > Please note - consensus does not require that the issue<br>
> you raise have<br>
> >> >> > been fixed, it requires that they have been addressed, and<br>
> should the<br>
> >> >> > community feel that despite the objections, the policy is<br>
> something that<br>
> >> >> > should proceed based on the fact that the questions have<br>
> been addressed if<br>
> >> >> > not necessarily accommodated, rough consensus still exists.<br>
> >> >> ><br>
> >> >> > Again, I support the policy and I see no technical or<br>
> evidence/fact-based<br>
> >> >> > arguments against said policy.<br>
> >> >> ><br>
> >> >> > Andrew<br>
> >> >> ><br>
> >> >> > On Tue, Jul 21, 2026 at 09:34, Nia Petronella <<br>
> >> >> > <a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a><br>
> <mailto:<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>>>> wrote:<br>
> >> >> ><br>
> >> >> >> Dear PDWG,<br>
> >> >> >><br>
> >> >> >> Kone is asking the right question.<br>
> >> >> >><br>
> >> >> >> The issue is no longer whether hierarchical AS-SET naming<br>
> is technically<br>
> >> >> >> possible or useful. It already exists. The issue is why<br>
> AFRINIC needs a<br>
> >> >> >> binding policy to enforce what other RIRs largely treat<br>
> as an operational<br>
> >> >> >> IRR matter.<br>
> >> >> >><br>
> >> >> >> That distinction matters. An operational change adjusts<br>
> how a service is<br>
> >> >> >> implemented. A policy creates an enforceable obligation<br>
> and enlarges the<br>
> >> >> >> registry?s authority. If the same technical result can be<br>
> achieved through<br>
> >> >> >> a community-reviewed implementation plan, then policy is<br>
> not the minimum<br>
> >> >> >> necessary instrument.<br>
> >> >> >><br>
> >> >> >> Saying that ?the community prefers policy? is not enough.<br>
> Participation<br>
> >> >> >> may guide technical work, but it does not turn every<br>
> preference into a<br>
> >> >> >> mandate. A mailing list is not a legislature, and the<br>
> availability of the<br>
> >> >> >> PDP should not make policy the default answer to every<br>
> operational setting.<br>
> >> >> >><br>
> >> >> >> This is how gatekeeping expands: the registry begins with<br>
> a useful<br>
> >> >> >> technical function, then policy converts that function<br>
> into permission and<br>
> >> >> >> enforcement. The recordkeeper gradually becomes the<br>
> rule-maker.<br>
> >> >> >><br>
> >> >> >> The proponents should therefore answer Kone directly:<br>
> what technical<br>
> >> >> >> outcome can mandatory policy achieve here that an operational<br>
> >> >> >> implementation cannot?<br>
> >> >> >><br>
> >> >> >> Until that is clearly demonstrated, I support Kone?s<br>
> questions and remain<br>
> >> >> >> opposed to the policy route.<br>
> >> >> >><br>
> >> >> >> Regards,<br>
> >> >> >> Nonhlanhla<br>
> >> >> >><br>
> >> >> >><br>
> >> >> >><br>
> >> >> >> On Tue, 21 Jul 2026, 8:20 am <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>>> wrote:<br>
> >> >> >><br>
> >> >> >>> Send RPD mailing list submissions to<br>
> >> >> >>> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> To subscribe or unsubscribe via the World Wide Web, visit<br>
> >> >> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> or, via email, send a message with subject or body 'help' to<br>
> >> >> >>> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> You can reach the person managing the list at<br>
> >> >> >>> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> When replying, please edit your Subject line so it is<br>
> more specific<br>
> >> >> >>> than "Re: Contents of RPD digest..."<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> Today's Topics:<br>
> >> >> >>><br>
> >> >> >>>? ? 1. Re: RPD Digest, Vol 222, Issue 110 (Tshepo Masuku)<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>><br>
> ----------------------------------------------------------------------<br>
> >> >> >>><br>
> >> >> >>> Message: 1<br>
> >> >> >>> Date: Tue, 21 Jul 2026 06:19:05 +0000<br>
> >> >> >>> From: Tshepo Masuku <<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a><br>
> <mailto:<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>><br>
> <mailto:<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a><br>
> <mailto:<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>>>><br>
> >> >> >>> To: "<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>>"<br>
> <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>>><br>
> >> >> >>> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 110<br>
> >> >> >>> Message-ID:<br>
> >> >> >>>? ? ? ? ?<<br>
> >> >> >>><br>
> <a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a><br>
> <mailto:<a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a>><br>
> <mailto:<a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a><br>
> <mailto:<a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a>>><br>
> >> >> >>> ><br>
> >> >> >>><br>
> >> >> >>> Content-Type: text/plain; charset="windows-1252"<br>
> >> >> >>><br>
> >> >> >>> Dear All,<br>
> >> >> >>><br>
> >> >> >>> Kone?s point is directly relevant. If LACNIC, RIPE NCC,<br>
> and ARIN can<br>
> >> >> >>> implement hierarchical AS-SET naming through operational<br>
> mechanisms, then<br>
> >> >> >>> proponents must explain why AFRINIC needs a binding<br>
> policy to achieve the<br>
> >> >> >>> same technical result.<br>
> >> >> >>><br>
> >> >> >>> Saying that each RIR works differently does not answer<br>
> that question.<br>
> >> >> >>> Nor does saying that ?the community is on top of the<br>
> RIR.? A community may<br>
> >> >> >>> advise, object, and coordinate. It does not acquire<br>
> unlimited authority to<br>
> >> >> >>> convert every operational preference into policy. A<br>
> mailing list is not a<br>
> >> >> >>> legislature.<br>
> >> >> >>><br>
> >> >> >>> If AFRINIC can solve this through an operational change,<br>
> policy adds<br>
> >> >> >>> governance where technical administration would be<br>
> sufficient. Speed and<br>
> >> >> >>> preference do not create mandate.<br>
> >> >> >>><br>
> >> >> >>> Kone provided specific examples. Those should be<br>
> answered with evidence,<br>
> >> >> >>> not by questioning whether he has worked in every RIR<br>
> for many years.<br>
> >> >> >>> Experience is relevant, but it is not authority and it<br>
> is not a substitute<br>
> >> >> >>> for argument.<br>
> >> >> >>><br>
> >> >> >>> The unanswered question remains: what technical<br>
> necessity requires<br>
> >> >> >>> policy rather than operational implementation?<br>
> >> >> >>><br>
> >> >> >>> Until that is answered, Kone?s objection stands, and I<br>
> support it.<br>
> >> >> >>><br>
> >> >> >>> Regards,<br>
> >> >> >>> Tshepo<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> ________________________________<br>
> >> >> >>> From: <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>> <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>>><br>
> >> >> >>> Sent: Monday, July 20, 2026 11:10:57 pm<br>
> >> >> >>> To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>> <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>>><br>
> >> >> >>> Subject: RPD Digest, Vol 222, Issue 110<br>
> >> >> >>><br>
> >> >> >>> Send RPD mailing list submissions to<br>
> >> >> >>> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> To subscribe or unsubscribe via the World Wide Web, visit<br>
> >> >> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> or, via email, send a message with subject or body 'help' to<br>
> >> >> >>> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> You can reach the person managing the list at<br>
> >> >> >>> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>>><br>
> >> >> >>><br>
> >> >> >>> When replying, please edit your Subject line so it is<br>
> more specific<br>
> >> >> >>> than "Re: Contents of RPD digest..."<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> Today's Topics:<br>
> >> >> >>><br>
> >> >> >>>? ? 1. Re: Writing tools (Ben Roberts - AfriNIC)<br>
> >> >> >>>? ? 2. Re: [Last Call] Draft Policy Proposal -<br>
> Hierarchical Names<br>
> >> >> >>>? ? ? ?for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Kone)<br>
> >> >> >>>? ? 3. Re: [Last Call] Draft Policy Proposal -<br>
> Hierarchical Names<br>
> >> >> >>>? ? ? ?for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
> >> >> >>>? ? ? ?(<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>>)<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>><br>
> ----------------------------------------------------------------------<br>
> >> >> >>><br>
> >> >> >>> Message: 1<br>
> >> >> >>> Date: Mon, 20 Jul 2026 21:26:40 +0200<br>
> >> >> >>> From: Ben Roberts - AfriNIC <<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a><br>
> <mailto:<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>> <mailto:<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a><br>
> <mailto:<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>>>><br>
> >> >> >>> To: Nonjabulo Sphilile <<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a><br>
> <mailto:<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a>><br>
> <mailto:<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a><br>
> <mailto:<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a>>>><br>
> >> >> >>> Cc: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> >> >> >>> Subject: Re: [rpd] Writing tools<br>
> >> >> >>> Message-ID:<br>
> <<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a><br>
> <mailto:<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a>><br>
> <mailto:<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a><br>
> <mailto:<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a>>>><br>
> >> >> >>> Content-Type: text/plain; charset="us-ascii"<br>
> >> >> >>><br>
> >> >> >>> An HTML attachment was scrubbed...<br>
> >> >> >>> URL: <<br>
> >> >> >>><br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/33c3ac9e/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/33c3ac9e/attachment-0001.html</a><br>
> >> >> >>> ><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> Message: 2<br>
> >> >> >>> Date: Mon, 20 Jul 2026 20:34:20 +0000<br>
> >> >> >>> From: Kone <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>>><br>
> >> >> >>> To: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>>><br>
> >> >> >>> Cc: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>>><br>
> >> >> >>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal -<br>
> Hierarchical<br>
> >> >> >>>? ? ? ? ?Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
> >> >> >>> Message-ID:<br>
> >> >> >>> ?<CADHquJpYPT91G8hHPsnXDJKp=<br>
> >> >> >>> <a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a><br>
> <mailto:<a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a>><br>
> <mailto:<a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a><br>
> <mailto:<a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a>>>><br>
> >> >> >>> Content-Type: text/plain; charset="utf-8"<br>
> >> >> >>><br>
> >> >> >>> Hello Seun,<br>
> >> >> >>> You may have misread my earlier mail. I clearly stated<br>
> that LACNIC, RIPE<br>
> >> >> >>> NCC, and ARIN do not require policy to enforce<br>
> hierarchical AS?SET<br>
> >> >> >>> naming.<br>
> >> >> >>><br>
> >> >> >>> To help close the ongoing discussions, I believe<br>
> addressing the<br>
> >> >> >>> questions I<br>
> >> >> >>> raised would bring clarity:<br>
> >> >> >>> * LACNIC enforces hierarchical AS?SET naming<br>
> operationally, as part of<br>
> >> >> >>> their IRR design from inception.<br>
> >> >> >>> * RIPE NCC handles IRR changes through their Numbered<br>
> Work Items (NWI)<br>
> >> >> >>> process, not through policy.<br>
> >> >> >>> * ARIN uses the ACSP (Consultation and Suggestion<br>
> Process) for IRR<br>
> >> >> >>> operational matters, again without policy.<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> These examples show that other RIRs (except APNIC) treat<br>
> AS?SET naming as<br>
> >> >> >>> an operational IRR matter, not a policy obligation.<br>
> >> >> >>><br>
> >> >> >>> This is why I asked whether AFRINIC could address this<br>
> operationally<br>
> >> >> >>> rather<br>
> >> >> >>> than through policy, and why Last Call discussions would<br>
> benefit from<br>
> >> >> >>> clear<br>
> >> >> >>> answers to these points.<br>
> >> >> >>><br>
> >> >> >>> Thanks.<br>
> >> >> >>> ---<br>
> >> >> >>> Kone<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji<br>
> <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>>> a<br>
> >> >> >>> ?crit :<br>
> >> >> >>><br>
> >> >> >>> > Hello Bakenon,<br>
> >> >> >>> ><br>
> >> >> >>> > Do refer to the proposal as it references URL to other<br>
> RIR's policies<br>
> >> >> >>> for<br>
> >> >> >>> > thiis:<br>
> >> >> >>> ><br>
> >> >> >>> > <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
> >> >> >>> ><br>
> >> >> >>> > Regards<br>
> >> >> >>> ><br>
> >> >> >>> > ----<br>
> >> >> >>> > Sent from my mobile<br>
> >> >> >>> > kindly excuse typos<br>
> >> >> >>> ><br>
> >> >> >>> > On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE,<br>
> <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>>><br>
> >> >> >>> > wrote:<br>
> >> >> >>> ><br>
> >> >> >>> >> Dear PDWG,<br>
> >> >> >>> >><br>
> >> >> >>> >> I have been following the discussions on the<br>
> hierarchical AS?SET<br>
> >> >> >>> naming<br>
> >> >> >>> >> scheme and would like clarification on a few points:<br>
> >> >> >>> >><br>
> >> >> >>> >> 1. Could this matter be addressed operationally, as<br>
> is done in ARIN,<br>
> >> >> >>> >> LACNIC, and RIPE NCC, without requiring policy changes?<br>
> >> >> >>> >><br>
> >> >> >>> >> 2. If yes, why are we taking the policy route? Is it<br>
> because AFRINIC<br>
> >> >> >>> >> currently lacks a defined process for handling<br>
> operational issues that<br>
> >> >> >>> >> affect IRR services?<br>
> >> >> >>> >><br>
> >> >> >>> >> 3. Given that the hierarchical naming scheme is<br>
> already supported and<br>
> >> >> >>> >> currently exists within the IRR, this proposal<br>
> represents an<br>
> >> >> >>> enforcement<br>
> >> >> >>> >> change rather than the introduction of a new<br>
> technical standard. Why<br>
> >> >> >>> is a<br>
> >> >> >>> >> formal policy required to change an operational<br>
> enforcement setting,<br>
> >> >> >>> rather<br>
> >> >> >>> >> than a community-vetted technical implementation plan?"<br>
> >> >> >>> >><br>
> >> >> >>> >> Thank you.<br>
> >> >> >>> >> ---<br>
> >> >> >>> >> Kone<br>
> >> >> >>> >><br>
> >> >> >>> >><br>
> >> >> >>> >><br>
> >> >> >>> >> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal<br>
> <<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>><br>
> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>>>> a<br>
> >> >> >>> >> ?crit :<br>
> >> >> >>> >><br>
> >> >> >>> >>> Dear PDWG,<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> The Policy Development Working Group (PDWG) Chairs<br>
> have initiated a<br>
> >> >> >>> Last<br>
> >> >> >>> >>> Call for this proposal, following rough consensus at<br>
> the AFRINIC-37<br>
> >> >> >>> Public<br>
> >> >> >>> >>> Policy Meeting held in hybrid format in Nairobi,<br>
> Kenya on 24 June<br>
> >> >> >>> 2026.<br>
> >> >> >>> >>><br>
> >> >> >>> >>>? ?*? ?Proposal Name: Hierarchical Names for New AS-SETs<br>
> >> >> >>> >>><br>
> >> >> >>> >>>? ?*? ?Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
> >> >> >>> >>><br>
> >> >> >>> >>>? ?*? ?Proposal URL:<br>
> >> >> >>> >>> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
> >> >> >>> >>><br>
> >> >> >>> >>> Last Call closes on: July 31, 2026, at 23:59 UTC.<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> Please note the staff observation regarding<br>
> implementation<br>
> >> >> >>> constraints:<br>
> >> >> >>> >>> due to the current prioritization of the MyAFRINIC<br>
> v2 deployment,<br>
> >> >> >>> physical<br>
> >> >> >>> >>> database implementation of this policy will be<br>
> scheduled once the<br>
> >> >> >>> MyAFRINIC<br>
> >> >> >>> >>> v2 deployment is concluded.<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> As always, we kindly request that all participants<br>
> adhere to the<br>
> >> >> >>> AFRINIC<br>
> >> >> >>> >>> Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to<br>
> maintain a<br>
> >> >> >>> respectful<br>
> >> >> >>> >>> and professional environment on the mailing list.<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> Kind regards,<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> Haitham el Nakhal<br>
> >> >> >>> >>><br>
> >> >> >>> >>> AFRINIC PDWG Co-Chair<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> _______________________________________________<br>
> >> >> >>> >>> RPD mailing list<br>
> >> >> >>> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >>> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> >>><br>
> >> >> >>> >> _______________________________________________<br>
> >> >> >>> >> RPD mailing list<br>
> >> >> >>> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >>> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> >><br>
> >> >> >>> ><br>
> >> >> >>> -------------- next part --------------<br>
> >> >> >>> An HTML attachment was scrubbed...<br>
> >> >> >>> URL: <<br>
> >> >> >>><br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/4563e1d5/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/4563e1d5/attachment-0001.html</a><br>
> >> >> >>> ><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> Message: 3<br>
> >> >> >>> Date: Mon, 20 Jul 2026 23:10:04 +0200<br>
> >> >> >>> From: "<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>>><br>
> >> >> >>> To: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>>><br>
> >> >> >>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal -<br>
> Hierarchical<br>
> >> >> >>>? ? ? ? ?Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
> >> >> >>> Message-ID:<br>
> <<a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a><br>
> <mailto:<a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a>><br>
> <mailto:<a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a><br>
> <mailto:<a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a>>>><br>
> >> >> >>> Content-Type: text/plain; charset="utf-8"<br>
> >> >> >>><br>
> >> >> >>> Hi Kone,<br>
> >> >> >>><br>
> >> >> >>> And what is the relevance of that?<br>
> >> >> >>><br>
> >> >> >>> If you have a good understanding about all the RIRs, you<br>
> will know that<br>
> >> >> >>> each RIR has their own ways to do things. In many senses<br>
> they act very<br>
> >> >> >>> similarly and in general we end up with very similarly<br>
> policies, but not<br>
> >> >> >>> always. Some RIRs have decided that some aspects are<br>
> operational and don?t<br>
> >> >> >>> need a policy proposal.<br>
> >> >> >>><br>
> >> >> >>> However, despite that, the community is on top of the<br>
> RIR, and the<br>
> >> >> >>> community sometimes, may decide that they prefer a<br>
> policy if the RIR hasn?t<br>
> >> >> >>> been proactive in advance in any specific topic, or even<br>
> if the RIR was<br>
> >> >> >>> proactive, the community may prefer to speed up things,<br>
> or to show the way<br>
> >> >> >>> the community prefers.<br>
> >> >> >>><br>
> >> >> >>> For example, if AFRINIC has any specific operational<br>
> aspect already in<br>
> >> >> >>> place, and the community prefer to manage that in a<br>
> different way, the<br>
> >> >> >>> community may opt either for suggesting the RIR to<br>
> modify that operational<br>
> >> >> >>> aspect or to do actually enforce it by means of a policy<br>
> proposal.<br>
> >> >> >>><br>
> >> >> >>> I think is important to know, by personal experience,<br>
> how the other 4<br>
> >> >> >>> RIRs work before stating something that is not correct,<br>
> because if you<br>
> >> >> >>> don?t work in all the RIRs for many years, it will be<br>
> difficult for you to<br>
> >> >> >>> know the past and I?m sure IA will not be able to be<br>
> precise as well.<br>
> >> >> >>><br>
> >> >> >>> Regards,<br>
> >> >> >>> Jordi<br>
> >> >> >>><br>
> >> >> >>> @jordipalet<br>
> >> >> >>><br>
> >> >> >>> > El 20 jul 2026, a las 22:34, Kone<br>
> <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>>> escribi?:<br>
> >> >> >>> ><br>
> >> >> >>> > Hello Seun,<br>
> >> >> >>> > You may have misread my earlier mail. I clearly stated<br>
> that LACNIC,<br>
> >> >> >>> RIPE NCC, and ARIN do not require policy to enforce<br>
> hierarchical AS?SET<br>
> >> >> >>> naming.<br>
> >> >> >>> ><br>
> >> >> >>> > To help close the ongoing discussions, I believe<br>
> addressing the<br>
> >> >> >>> questions I raised would bring clarity:<br>
> >> >> >>> > * LACNIC enforces hierarchical AS?SET naming<br>
> operationally, as part of<br>
> >> >> >>> their IRR design from inception.<br>
> >> >> >>> > * RIPE NCC handles IRR changes through their Numbered<br>
> Work Items (NWI)<br>
> >> >> >>> process, not through policy.<br>
> >> >> >>> > * ARIN uses the ACSP (Consultation and Suggestion<br>
> Process) for IRR<br>
> >> >> >>> operational matters, again without policy.<br>
> >> >> >>> ><br>
> >> >> >>> ><br>
> >> >> >>> > These examples show that other RIRs (except APNIC)<br>
> treat AS?SET naming<br>
> >> >> >>> as an operational IRR matter, not a policy obligation.<br>
> >> >> >>> ><br>
> >> >> >>> > This is why I asked whether AFRINIC could address this<br>
> operationally<br>
> >> >> >>> rather than through policy, and why Last Call<br>
> discussions would benefit<br>
> >> >> >>> from clear answers to these points.<br>
> >> >> >>> ><br>
> >> >> >>> > Thanks.<br>
> >> >> >>> > ---<br>
> >> >> >>> > Kone<br>
> >> >> >>> ><br>
> >> >> >>> ><br>
> >> >> >>> ><br>
> >> >> >>> > Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji<br>
> <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>><br>
> >> >> >>> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a><br>
> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>>>> a ?crit :<br>
> >> >> >>> >> Hello Bakenon,<br>
> >> >> >>> >><br>
> >> >> >>> >> Do refer to the proposal as it references URL to<br>
> other RIR's policies<br>
> >> >> >>> for thiis:<br>
> >> >> >>> >><br>
> >> >> >>> >> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
> >> >> >>> >><br>
> >> >> >>> >> Regards<br>
> >> >> >>> >><br>
> >> >> >>> >> ----<br>
> >> >> >>> >> Sent from my mobile<br>
> >> >> >>> >> kindly excuse typos<br>
> >> >> >>> >><br>
> >> >> >>> >> On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE,<br>
> <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>><br>
> >> >> >>> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>>>> wrote:<br>
> >> >> >>> >>> Dear PDWG,<br>
> >> >> >>> >>><br>
> >> >> >>> >>> I have been following the discussions on the<br>
> hierarchical AS?SET<br>
> >> >> >>> naming scheme and would like clarification on a few points:<br>
> >> >> >>> >>><br>
> >> >> >>> >>> 1. Could this matter be addressed operationally, as<br>
> is done in ARIN,<br>
> >> >> >>> LACNIC, and RIPE NCC, without requiring policy changes?<br>
> >> >> >>> >>><br>
> >> >> >>> >>> 2. If yes, why are we taking the policy route? Is it<br>
> because AFRINIC<br>
> >> >> >>> currently lacks a defined process for handling<br>
> operational issues that<br>
> >> >> >>> affect IRR services?<br>
> >> >> >>> >>><br>
> >> >> >>> >>> 3. Given that the hierarchical naming scheme is<br>
> already supported<br>
> >> >> >>> and currently exists within the IRR, this proposal<br>
> represents an<br>
> >> >> >>> enforcement change rather than the introduction of a new<br>
> technical<br>
> >> >> >>> standard. Why is a formal policy required to change an<br>
> operational<br>
> >> >> >>> enforcement setting, rather than a community-vetted<br>
> technical<br>
> >> >> >>> implementation plan?"<br>
> >> >> >>> >>><br>
> >> >> >>> >>> Thank you.<br>
> >> >> >>> >>> ---<br>
> >> >> >>> >>> Kone<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal<br>
> <<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>><br>
> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>>><br>
> >> >> >>> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>><br>
> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>>>>> a ?crit :<br>
> >> >> >>> >>>> Dear PDWG,<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> The Policy Development Working Group (PDWG) Chairs<br>
> have initiated a<br>
> >> >> >>> Last Call for this proposal, following rough consensus<br>
> at the AFRINIC-37<br>
> >> >> >>> Public Policy Meeting held in hybrid format in Nairobi,<br>
> Kenya on 24 June<br>
> >> >> >>> 2026.<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>>? ?*? ?Proposal Name: Hierarchical Names for New AS-SETs<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>>? ?*? ?Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>>? ?*? ?Proposal URL:<br>
> >> >> >>> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> Last Call closes on: July 31, 2026, at 23:59 UTC.<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> Please note the staff observation regarding<br>
> implementation<br>
> >> >> >>> constraints: due to the current prioritization of the<br>
> MyAFRINIC v2<br>
> >> >> >>> deployment, physical database implementation of this<br>
> policy will be<br>
> >> >> >>> scheduled once the MyAFRINIC v2 deployment is concluded.<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> As always, we kindly request that all participants<br>
> adhere to the<br>
> >> >> >>> AFRINIC Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to<br>
> maintain a<br>
> >> >> >>> respectful and professional environment on the mailing list.<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> Kind regards,<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> Haitham el Nakhal<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> AFRINIC PDWG Co-Chair<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> _______________________________________________<br>
> >> >> >>> >>>> RPD mailing list<br>
> >> >> >>> >>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>>><br>
> >> >> >>> >>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> >>> _______________________________________________<br>
> >> >> >>> >>> RPD mailing list<br>
> >> >> >>> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>>><br>
> >> >> >>> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>> > _______________________________________________<br>
> >> >> >>> > RPD mailing list<br>
> >> >> >>> > <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >>> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> **********************************************<br>
> >> >> >>> IPv4 is over<br>
> >> >> >>> Are you ready for the new Internet ?<br>
> >> >> >>> <a href="http://www.theipv6company.com" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com</a><br>
> <<a href="http://www.theipv6company.com/" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com/</a>> <<a href="http://www.theipv6company.com/" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com/</a>><br>
> >> >> >>> The IPv6 Company<br>
> >> >> >>><br>
> >> >> >>> This electronic message contains information which may<br>
> be privileged or<br>
> >> >> >>> confidential. The information is intended to be for the<br>
> exclusive use of<br>
> >> >> >>> the individual(s) named above and further non-explicilty<br>
> authorized<br>
> >> >> >>> disclosure, copying, distribution or use of the contents<br>
> of this<br>
> >> >> >>> information, even if partially, including attached<br>
> files, is strictly<br>
> >> >> >>> prohibited and will be considered a criminal offense. If<br>
> you are not the<br>
> >> >> >>> intended recipient be aware that any disclosure,<br>
> copying, distribution or<br>
> >> >> >>> use of the contents of this information, even if<br>
> partially, including<br>
> >> >> >>> attached files, is strictly prohibited, will be<br>
> considered a criminal<br>
> >> >> >>> offense, so you must reply to the original sender to<br>
> inform about this<br>
> >> >> >>> communication and delete it.<br>
> >> >> >>><br>
> >> >> >>> -------------- next part --------------<br>
> >> >> >>> An HTML attachment was scrubbed...<br>
> >> >> >>> URL: <<br>
> >> >> >>><br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/b6777fa7/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/b6777fa7/attachment.html</a><br>
> >> >> >>> ><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> Subject: Digest Footer<br>
> >> >> >>><br>
> >> >> >>> _______________________________________________<br>
> >> >> >>> RPD mailing list<br>
> >> >> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> End of RPD Digest, Vol 222, Issue 110<br>
> >> >> >>> *************************************<br>
> >> >> >>><br>
> >> >> >>> -------------- next part --------------<br>
> >> >> >>> An HTML attachment was scrubbed...<br>
> >> >> >>> URL: <<br>
> >> >> >>><br>
> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e492c668/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e492c668/attachment.html</a><br>
> >> >> >>> ><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> Subject: Digest Footer<br>
> >> >> >>><br>
> >> >> >>> _______________________________________________<br>
> >> >> >>> RPD mailing list<br>
> >> >> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> ------------------------------<br>
> >> >> >>><br>
> >> >> >>> End of RPD Digest, Vol 222, Issue 111<br>
> >> >> >>> *************************************<br>
> >> >> >>><br>
> >> >> >> _______________________________________________<br>
> >> >> >> RPD mailing list<br>
> >> >> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >> >><br>
> >> >> ><br>
> >> >> -------------- next part --------------<br>
> >> >> An HTML attachment was scrubbed...<br>
> >> >> URL:<br>
> <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/9c41424a/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/9c41424a/attachment.html</a>><br>
> >> >><br>
> >> >> ------------------------------<br>
> >> >><br>
> >> >> Subject: Digest Footer<br>
> >> >><br>
> >> >> _______________________________________________<br>
> >> >> RPD mailing list<br>
> >> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >> >><br>
> >> >><br>
> >> >> ------------------------------<br>
> >> >><br>
> >> >> End of RPD Digest, Vol 222, Issue 119<br>
> >> >> *************************************<br>
> >> > _______________________________________________<br>
> >> > RPD mailing list<br>
> >> > <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> >> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >><br>
> >><br>
> >><br>
> >> **********************************************<br>
> >> IPv4 is over<br>
> >> Are you ready for the new Internet ?<br>
> >> <a href="http://www.theipv6company.com" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com</a> <<a href="http://www.theipv6company.com/" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com/</a>><br>
> >> The IPv6 Company<br>
> >><br>
> >> This electronic message contains information which may be<br>
> privileged or confidential. The information is intended to be for<br>
> the exclusive use of the individual(s) named above and further<br>
> non-explicilty authorized disclosure, copying, distribution or use<br>
> of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited and will be considered a<br>
> criminal offense. If you are not the intended recipient be aware<br>
> that any disclosure, copying, distribution or use of the contents<br>
> of this information, even if partially, including attached files,<br>
> is strictly prohibited, will be considered a criminal offense, so<br>
> you must reply to the original sender to inform about this<br>
> communication and delete it.<br>
> >><br>
> >> -------------- next part --------------<br>
> >> An HTML attachment was scrubbed...<br>
> >> URL:<br>
> <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/0ba797a1/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/0ba797a1/attachment.html</a>><br>
> >><br>
> >> ------------------------------<br>
> >><br>
> >> Subject: Digest Footer<br>
> >><br>
> >> _______________________________________________<br>
> >> RPD mailing list<br>
> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
> >><br>
> >><br>
> >> ------------------------------<br>
> >><br>
> >> End of RPD Digest, Vol 222, Issue 122<br>
> >> *************************************<br>
> > _______________________________________________<br>
> > RPD mailing list<br>
> > <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
><br>
><br>
> **********************************************<br>
> IPv4 is over<br>
> Are you ready for the new Internet ?<br>
> <a href="http://www.theipv6company.com" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com</a><br>
> The IPv6 Company<br>
><br>
> This electronic message contains information which may be<br>
> privileged or confidential. The information is intended to be for<br>
> the exclusive use of the individual(s) named above and further<br>
> non-explicilty authorized disclosure, copying, distribution or use<br>
> of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited and will be considered a<br>
> criminal offense. If you are not the intended recipient be aware<br>
> that any disclosure, copying, distribution or use of the contents<br>
> of this information, even if partially, including attached files,<br>
> is strictly prohibited, will be considered a criminal offense, so<br>
> you must reply to the original sender to inform about this<br>
> communication and delete it.<br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/d5daa838/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/d5daa838/attachment.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of RPD Digest, Vol 222, Issue 124<br>
> *************************************<br>
><br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e42b4523/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e42b4523/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 222, Issue 146<br>
*************************************<br>
</blockquote></div>