<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">So the very simple question is:<div><br></div><div>Where in the bylaws or the PDP state, that a proposal must demonstrate the necessity of using a policy proposal approach vs operational decisions?</div><div><br></div><div>Also, following your argument, if we take the operational approach, we can make the same question reversed. Where the bylaws or PDP state that it must be demonstrated the necessity of the operational approach vs the policy proposal one?</div><div><br></div><div>It is fundamentally a bottom-up approach decision process. Policies always have priority on top of staff decisions, if they reach consensus, consequently that objection can’t revert the consensus otherwise any policy proposal may be rejected for the very same reason.</div><div><br></div><div>This basically means, and repeating myself, that if you are objecting to that, you really need to do that not in any specific policy proposal, but in a generic way in the PDP (or even the bylaws) modification and of course, your proposal on that, must reach consensus.</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Saludos,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 21 jul 2026, a las 13:20, Fundiswa Nadia Maseko <fundiswanadia2@gmail.com> escribió:</div><br class="Apple-interchange-newline"><div><div dir="auto">Dear Jordi,<div dir="auto"><br></div><div dir="auto">Thank you for your response.</div><div dir="auto"><br></div><div dir="auto">I agree that simply repeating an argument does not, by itself, justify revisiting consensus.</div><div dir="auto"><br></div><div dir="auto">However, I believe the concern being raised is not repetition for its own sake. It is whether the proposal has demonstrated the necessity of using a policy mechanism rather than an operational one.</div><div dir="auto"><br></div><div dir="auto">I also agree that a policy does not have to create harm to be questioned. At the same time, policy should generally exist because it provides a clear benefit that cannot reasonably be achieved through a less prescriptive mechanism.</div><div dir="auto"><br></div><div dir="auto">My understanding is that Last Call is an opportunity for the community to determine whether any aspect of a proposal has not been sufficiently justified before it is recommended for ratification. In my view, the choice of mechanism remains one such aspect.</div><div dir="auto"><br></div><div dir="auto">I appreciate your explanation of the procedural perspective, even though we may differ on whether this concern has been fully addressed.</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Fundiswa</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 13:19 , <<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: RPD Digest, Vol 222, Issue 122 (Taye Medoye)<br>
2. Re: RPD Digest, Vol 222, Issue 124 (Nia Petronella)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2026 13:16:30 +0200<br>
From: Taye Medoye <<a href="mailto:daniel.medoye@gmail.com" target="_blank" rel="noreferrer">daniel.medoye@gmail.com</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:<br>
<CACXLxYeq_nhj_i9o9_=<a href="mailto:kSBazfyhWoAq5AgKzR9RWFk0wkNMV%2Bg@mail.gmail.com" target="_blank" rel="noreferrer">kSBazfyhWoAq5AgKzR9RWFk0wkNMV+g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear All,<br>
<br>
I think the clarification made by Fundiswa regarding the seemingly fluid<br>
interconnection between the stage of consensus and Last Call in reaching a<br>
policy statement suffices. It is understood that if, at the point of Last<br>
Call on a policy proposal process, there arises an intervening factor, the<br>
need for a further review can be allowed.<br>
<br>
Besides, l have taken note of the relevance of the possible effect of<br>
diversities in the different Registries on the development of policy action<br>
on any subject-matter for consideration. And l think this should be<br>
accorded the recognition it deserves.<br>
<br>
Therefore, l align with the perspective as suggested by Fundiswa, and hope<br>
for an understanding of the Community participants on the same.<br>
<br>
Taye Medoye.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/359c5247/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/359c5247/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jul 2026 13:18:25 +0200<br>
From: Nia Petronella <<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>, <a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a><br>
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 124<br>
Message-ID:<br>
<<a href="mailto:CA%2BmDOg07VG92t_JQUKjAbmSCYWcKXfnOa4KTFU5q6DwkSOaaxg@mail.gmail.com" target="_blank" rel="noreferrer">CA+mDOg07VG92t_JQUKjAbmSCYWcKXfnOa4KTFU5q6DwkSOaaxg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Jordi,<br>
<br>
You are answering whether policy is procedurally permitted. That is not the<br>
question being raised.<br>
<br>
The fact that the bylaws and PDP allow a policy does not prove that policy<br>
is necessary, proportionate, or the best instrument. Likewise, the absence<br>
of a staff statement saying ?policy is not needed? is not evidence that it<br>
is needed. Silence cannot manufacture necessity.<br>
<br>
Kone?s examples remain relevant because they show that the same technical<br>
outcome can be achieved operationally. The unanswered question is what<br>
binding policy adds beyond rigidity and registry enforcement.<br>
<br>
A procedural route does not justify itself merely because it is familiar.<br>
That is how process becomes mandate: the PDP permits policy, therefore<br>
policy is treated as necessary, and the resulting enforcement is then<br>
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 was<br>
already reached before those concerns were answered.<br>
<br>
I therefore support Kone?s questions and remain opposed to the policy 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 staff impact<br>
> assessment, said that a policy is not needed and many folks already<br>
> contested several times, that doing it by means of a policy is valid<br>
> according to the bylaws and PDP and it has not been demonstrated by<br>
> objections that following this path, with is the most regular one in<br>
> AFRINIC, creates any harm or problem.<br>
><br>
> So repeating the argument, by many folks, many times, doesn?t demonstrate<br>
> ?per se" that it is a valid objection to revert the already reached<br>
> consensus. Of course, this is a decision that need to be taken by PDP<br>
> chairs, but this is my view point from an 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 consensus<br>
> and that Last Call is intended to identify any weaknesses that may have<br>
> 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 remains a<br>
> valid point to raise during Last Call. If a proposal introduces policy<br>
> where an operational approach could achieve the same objective, that<br>
> affects whether policy is the appropriate solution in the first place.<br>
> ><br>
> > I appreciate that consensus was declared, but consensus does not prevent<br>
> the community from identifying a concern that may not have received enough<br>
> attention. Last Call exists to give the community one final opportunity to<br>
> 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> <mailto:<br>
> <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 (<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>
> >> 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> <mailto:<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>>"<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>
> >> 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: <<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 proposal<br>
> (which is not the same as the Last Call), the community reached consensus<br>
> on making it this way. RIRs follow the same procedures for reaching<br>
> consensus as IETF, this has been said several times. The Last Call is a<br>
> last opportunity to discover any weak point in a proposal that already<br>
> reached consensus, and was OVERLOOKED before. Is not about discussing if<br>
> the proposal should be a proposal or an operational decision. This is no<br>
> longer the moment to discuss that (it should have done when the proposal<br>
> was being discussed before reaching consensus), and many folks in this<br>
> discussing are ignoring that, probably because they are not used to IETF<br>
> procedures.<br>
> >><br>
> >> Otherwise, you can remain silent during the proposal discussion, during<br>
> the presentation in the PPM and object to it after reached consensus, which<br>
> is an incorrect procedure.<br>
> >><br>
> >> One more example: we could have asked AFRINIC many years ago to write<br>
> the Soft Landing as an operational thing, instead we as a community,<br>
> decided to make it a policy proposal. Same here. However, the community<br>
> decided to do it as a proposal and it was accepted that way at the right<br>
> 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 chef? I<br>
> think I saw you in a TV program some months ago or I?m 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 approach as<br>
> other RIRs. Every region should make decisions that suit its own community.<br>
> >> ><br>
> >> > My point, however, is slightly different. I wasn't suggesting that<br>
> AFRINIC should copy another RIR simply because they did it that way.<br>
> >> ><br>
> >> > Rather, I'm asking what specific problem is solved by making this a<br>
> policy instead of implementing it operationally. If both approaches achieve<br>
> the same technical outcome, then what additional value does the policy<br>
> itself provide?<br>
> >> ><br>
> >> > I think that's an important distinction. The fact that the community<br>
> can choose policy doesn't necessarily mean policy is the most appropriate<br>
> mechanism in every case.<br>
> >> ><br>
> >> > I'd be interested to hear what practical or technical benefit you<br>
> believe is only possible through policy and not through an operational<br>
> 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> <mailto:<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> <mailto:<br>
> <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>> <mailto:<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>
> <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 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> <mailto:<br>
> <a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>> <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> <mailto:<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> <mailto:<br>
> <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>> <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 111<br>
> >> >> Message-ID:<br>
> >> >> <CA+mDOg0DqqBO74UVnd9mEr-P=<br>
> <a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a> <mailto:<br>
> <a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a>> <mailto:<br>
> <a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a> <mailto:<br>
> <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 changes in<br>
> secret<br>
> >> >> or without community input. An operational change can be published,<br>
> >> >> consulted on, tested, documented, and reviewed. The real question is<br>
> >> >> whether that input must be converted into binding policy enforced by<br>
> the<br>
> >> >> registry.<br>
> >> >><br>
> >> >> Calling AFRINIC ?community-driven? does not answer who the community<br>
> is or<br>
> >> >> what it is authorised to bind. A self-selecting group of mailing-list<br>
> >> >> participants can provide expertise, support, and objection. It does<br>
> not<br>
> >> >> automatically represent every member, resource holder, network,<br>
> customer,<br>
> >> >> or other affected party.<br>
> >> >><br>
> >> >> The institutional reality also remains unchanged: participants<br>
> discuss the<br>
> >> >> policy, but AFRINIC interprets and enforces it. Community<br>
> participation<br>
> >> >> therefore does not eliminate registry power. It can become the<br>
> language<br>
> >> >> used to legitimise that power.<br>
> >> >><br>
> >> >> This is why Kone?s examples matter. If LACNIC, RIPE NCC, and ARIN can<br>
> >> >> achieve the same technical outcome through operational mechanisms,<br>
> then<br>
> >> >> policy is not technically inevitable. Proponents should 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 instrument,<br>
> >> >> proportionality, reversibility, and expansion of enforcement<br>
> authority are<br>
> >> >> legitimate policy concerns. Last Call is not limited to asking<br>
> whether<br>
> >> >> software will break. It must also ask whether the proposed power is<br>
> greater<br>
> >> >> than the problem requires.<br>
> >> >><br>
> >> >> Rough consensus does not require every objection to be accommodated.<br>
> But an<br>
> >> >> objection is not ?addressed? merely because supporters repeat that<br>
> 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 decades<br>
> demonstrates<br>
> >> >> continuity of practice. It does not establish unlimited legitimacy<br>
> 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 <<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> <mailto:<br>
> <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 driven<br>
> 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 through<br>
> policy that<br>
> >> >> > the community tells AfriNIC how to do things in regards to the<br>
> allocation<br>
> >> >> > and handling of resources.<br>
> >> >> ><br>
> >> >> > Without policy, the discretion and rules are entirely in the hands<br>
> of the<br>
> >> >> > registry, and the community voice is removed.<br>
> >> >> ><br>
> >> >> > This has been the way the RIR system has operated for decades and<br>
> it<br>
> >> >> > works. The community exercises its voice and its right as to how<br>
> things<br>
> >> >> > are done in relation to resource management through policy.<br>
> >> >> ><br>
> >> >> > Arguing that just because something can be done another way, is<br>
> not in my<br>
> >> >> > view a valid argument against policy. Objections to policy need<br>
> to be<br>
> >> >> > technically grounded and demonstrate that the policy would either<br>
> cause<br>
> >> >> > harm or alternatively be impractical to implement. Anything else<br>
> is simply<br>
> >> >> > arguing that policy should not exist because someone doesn?t like<br>
> AfriNIC<br>
> >> >> > being told how the community wants things done - and that isn?t an<br>
> 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 you raise<br>
> have<br>
> >> >> > been fixed, it requires that they have been addressed, and should<br>
> 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 been<br>
> 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> <mailto:<br>
> <a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>> <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 is<br>
> technically<br>
> >> >> >> possible or useful. It already exists. The issue is why AFRINIC<br>
> needs a<br>
> >> >> >> binding policy to enforce what other RIRs largely treat as an<br>
> operational<br>
> >> >> >> IRR matter.<br>
> >> >> >><br>
> >> >> >> That distinction matters. An operational change adjusts how a<br>
> service is<br>
> >> >> >> implemented. A policy creates an enforceable obligation and<br>
> 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 not the<br>
> 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 preference<br>
> 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 a useful<br>
> >> >> >> technical function, then policy converts that function into<br>
> permission and<br>
> >> >> >> enforcement. The recordkeeper gradually becomes the rule-maker.<br>
> >> >> >><br>
> >> >> >> The proponents should therefore answer Kone directly: what<br>
> 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 questions<br>
> 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> <mailto:<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> <mailto:<br>
> <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>> <mailto:<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>
> <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 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> <mailto:<br>
> <a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>> <mailto:<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a> <mailto:<br>
> <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>> <mailto:<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>>>" <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<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>
> >> >> >>> 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:<br>
> <a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a>><br>
> <mailto:<br>
> <a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a><br>
> <mailto:<br>
> <a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a><br>
> >><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, and ARIN<br>
> can<br>
> >> >> >>> implement hierarchical AS-SET naming through operational<br>
> mechanisms, then<br>
> >> >> >>> proponents must explain why AFRINIC needs a binding policy to<br>
> achieve the<br>
> >> >> >>> same technical result.<br>
> >> >> >>><br>
> >> >> >>> Saying that each RIR works differently does not answer that<br>
> question.<br>
> >> >> >>> Nor does saying that ?the community is on top of the RIR.? A<br>
> community may<br>
> >> >> >>> advise, object, and coordinate. It does not acquire unlimited<br>
> authority to<br>
> >> >> >>> convert every operational preference into policy. A mailing list<br>
> is not a<br>
> >> >> >>> legislature.<br>
> >> >> >>><br>
> >> >> >>> If AFRINIC can solve this through an operational change, policy<br>
> adds<br>
> >> >> >>> governance where technical administration would be sufficient.<br>
> Speed and<br>
> >> >> >>> preference do not create mandate.<br>
> >> >> >>><br>
> >> >> >>> Kone provided specific examples. Those should be answered with<br>
> evidence,<br>
> >> >> >>> not by questioning whether he has worked in every RIR for many<br>
> years.<br>
> >> >> >>> Experience is relevant, but it is not authority and it is not a<br>
> substitute<br>
> >> >> >>> for argument.<br>
> >> >> >>><br>
> >> >> >>> The unanswered question remains: what technical necessity<br>
> requires<br>
> >> >> >>> policy rather than operational implementation?<br>
> >> >> >>><br>
> >> >> >>> Until that is answered, Kone?s objection stands, and I support<br>
> 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> <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>
> <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>> <mailto:<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>
> >> >> >>> 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>> <mailto:<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>>> <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<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>
> >> >> >>> 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>> <mailto:<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>
> <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: Writing tools (Ben Roberts - AfriNIC)<br>
> >> >> >>> 2. Re: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
> >> >> >>> for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Kone)<br>
> >> >> >>> 3. Re: [Last Call] Draft Policy Proposal - 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> <mailto:<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> <mailto:<br>
> <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> <mailto:<br>
> <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> <mailto:<br>
> <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> <mailto:<br>
> <a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a>> <mailto:<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a> <mailto:<br>
> <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>> <mailto:<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>
> >> >> >>> Subject: Re: [rpd] Writing tools<br>
> >> >> >>> Message-ID: <<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>> <mailto:<br>
> <a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a> <mailto:<br>
> <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> <mailto:<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> <mailto:<br>
> <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> <mailto:<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> <mailto:<br>
> <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>> <mailto:<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>
> >> >> >>> 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> <mailto:<br>
> <a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a>> <mailto:<br>
> <a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a> <mailto:<br>
> <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 that<br>
> LACNIC, RIPE<br>
> >> >> >>> NCC, and ARIN do not require policy to enforce hierarchical<br>
> AS?SET<br>
> >> >> >>> naming.<br>
> >> >> >>><br>
> >> >> >>> To help close the ongoing discussions, I believe addressing the<br>
> >> >> >>> questions I<br>
> >> >> >>> raised would bring clarity:<br>
> >> >> >>> * LACNIC enforces hierarchical AS?SET naming operationally, as<br>
> part of<br>
> >> >> >>> their IRR design from inception.<br>
> >> >> >>> * RIPE NCC handles IRR changes through their Numbered Work Items<br>
> (NWI)<br>
> >> >> >>> process, not through policy.<br>
> >> >> >>> * ARIN uses the ACSP (Consultation and Suggestion Process) for<br>
> IRR<br>
> >> >> >>> operational matters, again without policy.<br>
> >> >> >>><br>
> >> >> >>><br>
> >> >> >>> These examples show that other RIRs (except APNIC) treat AS?SET<br>
> 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 benefit<br>
> 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>> <mailto:<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>>>> a<br>
> >> >> >>> ?crit :<br>
> >> >> >>><br>
> >> >> >>> > Hello Bakenon,<br>
> >> >> >>> ><br>
> >> >> >>> > Do refer to the proposal as it references URL to other RIR's<br>
> 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>> <mailto:<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>
> >> >> >>> > wrote:<br>
> >> >> >>> ><br>
> >> >> >>> >> Dear PDWG,<br>
> >> >> >>> >><br>
> >> >> >>> >> I have been following the discussions on the hierarchical<br>
> AS?SET<br>
> >> >> >>> naming<br>
> >> >> >>> >> scheme and would like clarification on a few points:<br>
> >> >> >>> >><br>
> >> >> >>> >> 1. Could this matter be addressed operationally, as is done<br>
> 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 because<br>
> AFRINIC<br>
> >> >> >>> >> currently lacks a defined process for handling operational<br>
> issues that<br>
> >> >> >>> >> affect IRR services?<br>
> >> >> >>> >><br>
> >> >> >>> >> 3. Given that the hierarchical naming scheme is already<br>
> supported and<br>
> >> >> >>> >> currently exists within the IRR, this proposal represents an<br>
> >> >> >>> enforcement<br>
> >> >> >>> >> change rather than the introduction of a new technical<br>
> standard. Why<br>
> >> >> >>> is a<br>
> >> >> >>> >> formal policy required to change an operational enforcement<br>
> 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>> <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>>>> a<br>
> >> >> >>> >> ?crit :<br>
> >> >> >>> >><br>
> >> >> >>> >>> Dear PDWG,<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> The Policy Development Working Group (PDWG) Chairs have<br>
> initiated a<br>
> >> >> >>> Last<br>
> >> >> >>> >>> Call for this proposal, following rough consensus at the<br>
> AFRINIC-37<br>
> >> >> >>> Public<br>
> >> >> >>> >>> Policy Meeting held in hybrid format in Nairobi, Kenya on 24<br>
> 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 implementation<br>
> >> >> >>> constraints:<br>
> >> >> >>> >>> due to the current prioritization of the MyAFRINIC v2<br>
> deployment,<br>
> >> >> >>> physical<br>
> >> >> >>> >>> database implementation of this policy will be scheduled<br>
> once the<br>
> >> >> >>> MyAFRINIC<br>
> >> >> >>> >>> v2 deployment is concluded.<br>
> >> >> >>> >>><br>
> >> >> >>> >>><br>
> >> >> >>> >>> As always, we kindly request that all participants adhere to<br>
> 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 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>> <mailto:<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>
> >> >> >>> >> 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>> <mailto:<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>
> >> >> >>> -------------- 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> <mailto:<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> <mailto:<br>
> <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> <mailto:<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> <mailto:<br>
> <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>> <mailto:<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>
> >> >> >>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal -<br>
> Hierarchical<br>
> >> >> >>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
> >> >> >>> Message-ID: <<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>> <mailto:<br>
> <a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a> <mailto:<br>
> <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 will<br>
> know that<br>
> >> >> >>> each RIR has their own ways to do things. In many senses they<br>
> act very<br>
> >> >> >>> similarly and in general we end up with very similarly policies,<br>
> but not<br>
> >> >> >>> always. Some RIRs have decided that some aspects are operational<br>
> and don?t<br>
> >> >> >>> need a policy proposal.<br>
> >> >> >>><br>
> >> >> >>> However, despite that, the community is on top of the RIR, and<br>
> the<br>
> >> >> >>> community sometimes, may decide that they prefer a policy if the<br>
> RIR hasn?t<br>
> >> >> >>> been proactive in advance in any specific topic, or even if the<br>
> RIR was<br>
> >> >> >>> proactive, the community may prefer to speed up things, or to<br>
> show the way<br>
> >> >> >>> the community prefers.<br>
> >> >> >>><br>
> >> >> >>> For example, if AFRINIC has any specific operational aspect<br>
> already in<br>
> >> >> >>> place, and the community prefer to manage that in a different<br>
> way, the<br>
> >> >> >>> community may opt either for suggesting the RIR to modify that<br>
> 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, how the<br>
> other 4<br>
> >> >> >>> RIRs work before stating something that is not correct, because<br>
> if you<br>
> >> >> >>> don?t work in all the RIRs for many years, it will be difficult<br>
> for you to<br>
> >> >> >>> know the past and I?m sure IA will not be able to be precise as<br>
> well.<br>
> >> >> >>><br>
> >> >> >>> Regards,<br>
> >> >> >>> Jordi<br>
> >> >> >>><br>
> >> >> >>> @jordipalet<br>
> >> >> >>><br>
> >> >> >>> > El 20 jul 2026, a las 22:34, 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>>>> escribi?:<br>
> >> >> >>> ><br>
> >> >> >>> > Hello Seun,<br>
> >> >> >>> > You may have misread my earlier mail. I clearly stated that<br>
> LACNIC,<br>
> >> >> >>> RIPE NCC, and ARIN do not require policy to enforce hierarchical<br>
> AS?SET<br>
> >> >> >>> naming.<br>
> >> >> >>> ><br>
> >> >> >>> > To help close the ongoing discussions, I believe addressing the<br>
> >> >> >>> questions I raised would bring clarity:<br>
> >> >> >>> > * LACNIC enforces hierarchical AS?SET naming operationally, as<br>
> part of<br>
> >> >> >>> their IRR design from inception.<br>
> >> >> >>> > * RIPE NCC handles IRR changes through their Numbered Work<br>
> Items (NWI)<br>
> >> >> >>> process, not through policy.<br>
> >> >> >>> > * ARIN uses the ACSP (Consultation and Suggestion Process) for<br>
> IRR<br>
> >> >> >>> operational matters, again without policy.<br>
> >> >> >>> ><br>
> >> >> >>> ><br>
> >> >> >>> > These examples show that other RIRs (except APNIC) treat<br>
> 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 discussions would<br>
> 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>> <mailto:<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> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>>>> a ?crit<br>
> :<br>
> >> >> >>> >> Hello Bakenon,<br>
> >> >> >>> >><br>
> >> >> >>> >> Do refer to the proposal as it references URL to other RIR's<br>
> 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>> <mailto:<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:<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> <mailto:<br>
> <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 hierarchical<br>
> AS?SET<br>
> >> >> >>> naming scheme and would like clarification on a few points:<br>
> >> >> >>> >>><br>
> >> >> >>> >>> 1. Could this matter be addressed operationally, as is done<br>
> 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 because<br>
> AFRINIC<br>
> >> >> >>> currently lacks a defined process for handling operational<br>
> issues that<br>
> >> >> >>> affect IRR services?<br>
> >> >> >>> >>><br>
> >> >> >>> >>> 3. Given that the hierarchical naming scheme is already<br>
> supported<br>
> >> >> >>> and currently exists within the IRR, this proposal 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 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>> <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>>><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>> <mailto:<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>>>>> a ?crit :<br>
> >> >> >>> >>>> Dear PDWG,<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> The Policy Development Working Group (PDWG) Chairs have<br>
> initiated a<br>
> >> >> >>> Last Call for this proposal, following rough consensus at the<br>
> AFRINIC-37<br>
> >> >> >>> Public Policy Meeting held in hybrid format in Nairobi, Kenya on<br>
> 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 implementation<br>
> >> >> >>> constraints: due to the current prioritization of the MyAFRINIC<br>
> v2<br>
> >> >> >>> deployment, physical database implementation of this policy will<br>
> be<br>
> >> >> >>> scheduled once the MyAFRINIC v2 deployment is concluded.<br>
> >> >> >>> >>>><br>
> >> >> >>> >>>><br>
> >> >> >>> >>>> As always, we kindly request that all participants adhere<br>
> 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>> <mailto:<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> <mailto:<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>
> >> >> >>> >>>> <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>> <mailto:<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> <mailto:<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>
> >> >> >>> >>> <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>> <mailto:<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>
> <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<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 of this<br>
> >> >> >>> information, even if partially, including attached files, is<br>
> strictly<br>
> >> >> >>> prohibited and will be considered a criminal offense. If you are<br>
> not the<br>
> >> >> >>> intended recipient be aware that any disclosure, copying,<br>
> distribution or<br>
> >> >> >>> use of the contents of this information, even if partially,<br>
> including<br>
> >> >> >>> attached files, is strictly prohibited, will be considered a<br>
> criminal<br>
> >> >> >>> offense, so you must reply to the original sender to inform<br>
> 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>> <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>
> >> >> >>> <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>> <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>
> >> >> >>> <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>> <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>
> >> >> >> <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>
> >> >><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>> <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>
> >> >> <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 privileged or<br>
> confidential. The information is intended to be for the exclusive use of<br>
> the individual(s) named above and further non-explicilty authorized<br>
> disclosure, copying, distribution or use of the contents of this<br>
> information, even if partially, including attached files, is strictly<br>
> prohibited and will be considered a criminal offense. If you are not the<br>
> intended recipient be aware that any disclosure, copying, distribution or<br>
> use of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited, will be considered a criminal<br>
> offense, so 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>
> >><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 privileged or<br>
> confidential. The information is intended to be for the exclusive use of<br>
> the individual(s) named above and further non-explicilty authorized<br>
> disclosure, copying, distribution or use of the contents of this<br>
> information, even if partially, including attached files, is strictly<br>
> prohibited and will be considered a criminal offense. If you are not the<br>
> intended recipient be aware that any disclosure, copying, distribution or<br>
> use of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited, will be considered a criminal<br>
> offense, so 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>
><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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/fe3cdcf4/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/fe3cdcf4/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 126<br>
*************************************<br>
</blockquote></div>
_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<br></div></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>