<div dir="auto">The answer to this is simple. AfriNiC is a community driven organisation - and anything done with regard to address allocation and management is done as per policy provided by the community. It is through policy that the community tells AfriNIC how to do things in regards to the allocation and handling of resources.</div><div dir="auto"><br></div><div dir="auto">Without policy, the discretion and rules are entirely in the hands of the registry, and the community voice is removed. </div><div dir="auto"><br></div><div dir="auto">This has been the way the RIR system has operated for decades and it works. The community exercises its voice and its right as to how things are done in relation to resource management through policy. </div><div dir="auto"><br></div><div dir="auto">Arguing that just because something can be done another way, is not in my view a valid argument against policy. Objections to policy need to be technically grounded and demonstrate that the policy would either cause harm or alternatively be impractical to implement. Anything else is simply arguing that policy should not exist because someone doesn’t like AfriNIC being told how the community wants things done - and that isn’t an argument that I believe rises to the level of a block on consensus.</div><div dir="auto"><br></div><div dir="auto">Please note - consensus does not require that the issue you raise have been fixed, it requires that they have been addressed, and should the community feel that despite the objections, the policy is something that should proceed based on the fact that the questions have been addressed if not necessarily accommodated, rough consensus still exists.</div><div dir="auto"><br></div><div dir="auto">Again, I support the policy and I see no technical or evidence/fact-based arguments against said policy.</div><div dir="auto"><br></div><div dir="auto">Andrew </div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Jul 21, 2026 at 09:34, Nia Petronella <<a href="mailto:nonhlanhlapetronella85@gmail.com">nonhlanhlapetronella85@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Dear PDWG,<div dir="auto"><br></div><div dir="auto">Kone is asking the right question.</div><div dir="auto"><br></div><div dir="auto">The issue is no longer whether hierarchical AS-SET naming is technically possible or useful. It already exists. The issue is why AFRINIC needs a binding policy to enforce what other RIRs largely treat as an operational IRR matter.</div><div dir="auto"><br></div><div dir="auto">That distinction matters. An operational change adjusts how a service is implemented. A policy creates an enforceable obligation and enlarges the registry’s authority. If the same technical result can be achieved through a community-reviewed implementation plan, then policy is not the minimum necessary instrument.</div><div dir="auto"><br></div><div dir="auto">Saying that “the community prefers policy” is not enough. Participation may guide technical work, but it does not turn every preference into a mandate. A mailing list is not a legislature, and the availability of the PDP should not make policy the default answer to every operational setting.</div><div dir="auto"><br></div><div dir="auto">This is how gatekeeping expands: the registry begins with a useful technical function, then policy converts that function into permission and enforcement. The recordkeeper gradually becomes the rule-maker.</div><div dir="auto"><br></div><div dir="auto">The proponents should therefore answer Kone directly: what technical outcome can mandatory policy achieve here that an operational implementation cannot?</div><div dir="auto"><br></div><div dir="auto">Until that is clearly demonstrated, I support Kone’s questions and remain opposed to the policy route.</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"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 8:20 am <<a href="mailto:rpd-request@afrinic.net" target="_blank">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" rel="noreferrer" target="_blank">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 110 (Tshepo Masuku)<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" rel="noreferrer" target="_blank">TshepoMasuku26@hotmail.com</a>><br>
To: "<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a>" <<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 110<br>
Message-ID:<br>
<<a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" rel="noreferrer" target="_blank">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a>><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 can implement hierarchical AS-SET naming through operational mechanisms, then proponents must explain why AFRINIC needs a binding policy to achieve the same technical result.<br>
<br>
Saying that each RIR works differently does not answer that question. Nor does saying that ?the community is on top of the RIR.? A community may advise, object, and coordinate. It does not acquire unlimited authority to convert every operational preference into policy. A mailing list is not a legislature.<br>
<br>
If AFRINIC can solve this through an operational change, policy adds governance where technical administration would be sufficient. Speed and preference do not create mandate.<br>
<br>
Kone provided specific examples. Those should be answered with evidence, not by questioning whether he has worked in every RIR for many years. Experience is relevant, but it is not authority and it is not a substitute for argument.<br>
<br>
The unanswered question remains: what technical necessity requires policy rather than operational implementation?<br>
<br>
Until that is answered, Kone?s objection stands, and I support it.<br>
<br>
Regards,<br>
Tshepo<br>
<br>
<br>
________________________________<br>
From: <a href="mailto:rpd-request@afrinic.net" rel="noreferrer" target="_blank">rpd-request@afrinic.net</a> <<a href="mailto:rpd-request@afrinic.net" rel="noreferrer" target="_blank">rpd-request@afrinic.net</a>><br>
Sent: Monday, July 20, 2026 11:10:57 pm<br>
To: <a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a> <<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" rel="noreferrer" target="_blank">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: 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" rel="noreferrer" target="_blank">jordi.palet@consulintel.es</a>)<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" rel="noreferrer" target="_blank">ben.roberts@afrinic.net</a>><br>
To: Nonjabulo Sphilile <<a href="mailto:nonjabulosphilile@gmail.com" rel="noreferrer" target="_blank">nonjabulosphilile@gmail.com</a>><br>
Cc: <a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a><br>
Subject: Re: [rpd] Writing tools<br>
Message-ID: <<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" rel="noreferrer" target="_blank">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: <<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>
Message: 2<br>
Date: Mon, 20 Jul 2026 20:34:20 +0000<br>
From: Kone <<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer" target="_blank">bakenon.kone@sancfis.net</a>><br>
To: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" rel="noreferrer" target="_blank">seun.ojedeji@gmail.com</a>><br>
Cc: rpd <<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
Message-ID:<br>
<CADHquJpYPT91G8hHPsnXDJKp=<a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" rel="noreferrer" target="_blank">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 LACNIC, RIPE<br>
NCC, and ARIN do not require policy to enforce hierarchical AS?SET naming.<br>
<br>
To help close the ongoing discussions, I believe addressing the questions I<br>
raised would bring clarity:<br>
* LACNIC enforces hierarchical AS?SET naming operationally, as part of<br>
their IRR design from inception.<br>
* RIPE NCC handles IRR changes through their Numbered Work Items (NWI)<br>
process, not through policy.<br>
* ARIN uses the ACSP (Consultation and Suggestion Process) for IRR<br>
operational matters, again without policy.<br>
<br>
<br>
These examples show that other RIRs (except APNIC) treat 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 operationally rather<br>
than through policy, and why Last Call discussions would benefit from 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 <<a href="mailto:seun.ojedeji@gmail.com" rel="noreferrer" target="_blank">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 policies 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, <<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer" target="_blank">bakenon.kone@sancfis.net</a>><br>
> wrote:<br>
><br>
>> Dear PDWG,<br>
>><br>
>> I have been following the discussions on the hierarchical AS?SET naming<br>
>> scheme and would like clarification on a few points:<br>
>><br>
>> 1. Could this matter be addressed operationally, as 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 because AFRINIC<br>
>> currently lacks a defined process for handling operational issues that<br>
>> affect IRR services?<br>
>><br>
>> 3. Given that the hierarchical naming scheme is already supported and<br>
>> currently exists within the IRR, this proposal represents an enforcement<br>
>> change rather than the introduction of a new technical standard. Why is a<br>
>> formal policy required to change an operational enforcement setting, 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 <<a href="mailto:hytham@tra.gov.eg" rel="noreferrer" target="_blank">hytham@tra.gov.eg</a>> a<br>
>> ?crit :<br>
>><br>
>>> Dear PDWG,<br>
>>><br>
>>><br>
>>> The Policy Development Working Group (PDWG) Chairs have initiated a Last<br>
>>> Call for this proposal, following rough consensus at the AFRINIC-37 Public<br>
>>> Policy Meeting held in hybrid format in Nairobi, Kenya on 24 June 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 constraints:<br>
>>> due to the current prioritization of the MyAFRINIC v2 deployment, physical<br>
>>> database implementation of this policy will be scheduled once the MyAFRINIC<br>
>>> v2 deployment is concluded.<br>
>>><br>
>>><br>
>>> As always, we kindly request that all participants adhere to the 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 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" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">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: <<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>
Message: 3<br>
Date: Mon, 20 Jul 2026 23:10:04 +0200<br>
From: "<a href="mailto:jordi.palet@consulintel.es" rel="noreferrer" target="_blank">jordi.palet@consulintel.es</a>" <<a href="mailto:jordi.palet@consulintel.es" rel="noreferrer" target="_blank">jordi.palet@consulintel.es</a>><br>
To: rpd <<a href="mailto:rpd@afrinic.net" rel="noreferrer" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - 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" rel="noreferrer" target="_blank">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 know that each RIR has their own ways to do things. In many senses they act very similarly and in general we end up with very similarly policies, but not always. Some RIRs have decided that some aspects are operational and don?t need a policy proposal.<br>
<br>
However, despite that, the community is on top of the RIR, and the community sometimes, may decide that they prefer a policy if the RIR hasn?t been proactive in advance in any specific topic, or even if the RIR was proactive, the community may prefer to speed up things, or to show the way the community prefers.<br>
<br>
For example, if AFRINIC has any specific operational aspect already in place, and the community prefer to manage that in a different way, the community may opt either for suggesting the RIR to modify that operational aspect or to do actually enforce it by means of a policy proposal.<br>
<br>
I think is important to know, by personal experience, how the other 4 RIRs work before stating something that is not correct, because if you don?t work in all the RIRs for many years, it will be difficult for you to know the past and I?m sure IA will not be able to be precise as 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" rel="noreferrer" target="_blank">bakenon.kone@sancfis.net</a>> escribi?:<br>
><br>
> Hello Seun,<br>
> You may have misread my earlier mail. I clearly stated that LACNIC, RIPE NCC, and ARIN do not require policy to enforce hierarchical AS?SET naming.<br>
><br>
> To help close the ongoing discussions, I believe addressing the questions I raised would bring clarity:<br>
> * LACNIC enforces hierarchical AS?SET naming operationally, as part of their IRR design from inception.<br>
> * RIPE NCC handles IRR changes through their Numbered Work Items (NWI) process, not through policy.<br>
> * ARIN uses the ACSP (Consultation and Suggestion Process) for IRR operational matters, again without policy.<br>
><br>
><br>
> These examples show that other RIRs (except APNIC) treat AS?SET naming as an operational IRR matter, not a policy obligation.<br>
><br>
> This is why I asked whether AFRINIC could address this operationally rather than through policy, and why Last Call discussions would benefit 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 <<a href="mailto:seun.ojedeji@gmail.com" rel="noreferrer" target="_blank">seun.ojedeji@gmail.com</a> <mailto:<a href="mailto:seun.ojedeji@gmail.com" rel="noreferrer" target="_blank">seun.ojedeji@gmail.com</a>>> a ?crit :<br>
>> Hello Bakenon,<br>
>><br>
>> Do refer to the proposal as it references URL to other RIR's policies 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, <<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer" target="_blank">bakenon.kone@sancfis.net</a> <mailto:<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer" target="_blank">bakenon.kone@sancfis.net</a>>> wrote:<br>
>>> Dear PDWG,<br>
>>><br>
>>> I have been following the discussions on the hierarchical AS?SET naming scheme and would like clarification on a few points:<br>
>>><br>
>>> 1. Could this matter be addressed operationally, as is done in ARIN, LACNIC, and RIPE NCC, without requiring policy changes?<br>
>>><br>
>>> 2. If yes, why are we taking the policy route? Is it because AFRINIC currently lacks a defined process for handling operational issues that affect IRR services?<br>
>>><br>
>>> 3. Given that the hierarchical naming scheme is already supported and currently exists within the IRR, this proposal represents an enforcement change rather than the introduction of a new technical standard. Why is a formal policy required to change an operational enforcement setting, rather 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 <<a href="mailto:hytham@tra.gov.eg" rel="noreferrer" target="_blank">hytham@tra.gov.eg</a> <mailto:<a href="mailto:hytham@tra.gov.eg" rel="noreferrer" target="_blank">hytham@tra.gov.eg</a>>> a ?crit :<br>
>>>> Dear PDWG,<br>
>>>><br>
>>>><br>
>>>> The Policy Development Working Group (PDWG) Chairs have initiated a Last Call for this proposal, following rough consensus at the AFRINIC-37 Public Policy Meeting held in hybrid format in Nairobi, Kenya on 24 June 2026.<br>
>>>><br>
>>>> * Proposal Name: Hierarchical Names for New AS-SETs<br>
>>>><br>
>>>> * Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
>>>><br>
>>>> * Proposal URL: <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 constraints: due to the current prioritization of the MyAFRINIC v2 deployment, physical database implementation of this policy will be scheduled once the MyAFRINIC v2 deployment is concluded.<br>
>>>><br>
>>>><br>
>>>> As always, we kindly request that all participants adhere to the AFRINIC Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to maintain a 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" rel="noreferrer" target="_blank">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" rel="noreferrer" target="_blank">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" rel="noreferrer" target="_blank">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 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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<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>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer" target="_blank">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: <<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>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer" target="_blank">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>
</blockquote></div>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div></div>