Search RPD Archives
[rpd] RPD Digest, Vol 222, Issue 127
Mendie
mendie5205 at gmail.com
Tue Jul 21 11:26:55 UTC 2026
Good day,
I agree with Fundiswa's point.
I do not understand her argument to be that using the PDP is prohibited by
the bylaws or that repeating an objection automatically overturns rough
consensus. Rather, the point is narrower: the fact that policy is
procedurally available does not, by itself, establish that it is the
appropriate instrument.
Likewise, the fact that neither the staff assessment nor earlier
participants argued that policy was unnecessary does not demonstrate that
it is necessary. That question still requires a substantive justification.
I also believe this concern is appropriate for Last Call. If the
distinction between an operational implementation and a binding policy was
not sufficiently examined before consensus was declared, then identifying
that potential weakness is precisely what Last Call is intended to do.
The central question therefore remains:
What technical requirement can only be met through binding policy rather
than a transparent, community-reviewed operational implementation?
The examples from LACNIC, RIPE NCC, and ARIN are not offered to suggest
AFRINIC should copy other RIRs. They simply demonstrate that an operational
alternative exists. If the same technical outcome can be achieved through
an open operational process, then the additional technical value of a
binding policy should be clearly explained.
Kind regards,
On Tue, 21 Jul 2026, 13:21 , <rpd-request at afrinic.net> wrote:
> Send RPD mailing list submissions to
> rpd at afrinic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.afrinic.net/mailman/listinfo/rpd
> or, via email, send a message with subject or body 'help' to
> rpd-request at afrinic.net
>
> You can reach the person managing the list at
> rpd-owner at afrinic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of RPD digest..."
>
>
> Today's Topics:
>
> 1. Re: RPD Digest, Vol 222, Issue 126 (Fundiswa Nadia Maseko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 21 Jul 2026 13:20:51 +0200
> From: Fundiswa Nadia Maseko <fundiswanadia2 at gmail.com>
> To: rpd at afrinic.net
> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 126
> Message-ID:
> <
> CABV0QcSyVH-Om4eB8ZiR_RHq5Hf6uOpckQ870WPpWkAV1ej7CA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Dear Jordi,
>
> Thank you for your response.
>
> I agree that simply repeating an argument does not, by itself, justify
> revisiting consensus.
>
> 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.
>
> 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.
>
> 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.
>
> I appreciate your explanation of the procedural perspective, even though we
> may differ on whether this concern has been fully addressed.
>
> Kind regards,
> Fundiswa
>
> On Tue, 21 Jul 2026, 13:19 , <rpd-request at afrinic.net> wrote:
>
> > Send RPD mailing list submissions to
> > rpd at afrinic.net
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.afrinic.net/mailman/listinfo/rpd
> > or, via email, send a message with subject or body 'help' to
> > rpd-request at afrinic.net
> >
> > You can reach the person managing the list at
> > rpd-owner at afrinic.net
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of RPD digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: RPD Digest, Vol 222, Issue 122 (Taye Medoye)
> > 2. Re: RPD Digest, Vol 222, Issue 124 (Nia Petronella)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 21 Jul 2026 13:16:30 +0200
> > From: Taye Medoye <daniel.medoye at gmail.com>
> > To: rpd at afrinic.net
> > Subject: Re: [rpd] RPD Digest, Vol 222, Issue 122
> > Message-ID:
> > <CACXLxYeq_nhj_i9o9_=
> > kSBazfyhWoAq5AgKzR9RWFk0wkNMV+g at mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Dear All,
> >
> > I think the clarification made by Fundiswa regarding the seemingly fluid
> > interconnection between the stage of consensus and Last Call in reaching
> a
> > policy statement suffices. It is understood that if, at the point of Last
> > Call on a policy proposal process, there arises an intervening factor,
> the
> > need for a further review can be allowed.
> >
> > Besides, l have taken note of the relevance of the possible effect of
> > diversities in the different Registries on the development of policy
> action
> > on any subject-matter for consideration. And l think this should be
> > accorded the recognition it deserves.
> >
> > Therefore, l align with the perspective as suggested by Fundiswa, and
> hope
> > for an understanding of the Community participants on the same.
> >
> > Taye Medoye.
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/359c5247/attachment-0001.html
> > >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Tue, 21 Jul 2026 13:18:25 +0200
> > From: Nia Petronella <nonhlanhlapetronella85 at gmail.com>
> > To: rpd at afrinic.net, jordi.palet at consulintel.es
> > Subject: Re: [rpd] RPD Digest, Vol 222, Issue 124
> > Message-ID:
> > <
> > CA+mDOg07VG92t_JQUKjAbmSCYWcKXfnOa4KTFU5q6DwkSOaaxg at mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Dear Jordi,
> >
> > You are answering whether policy is procedurally permitted. That is not
> the
> > question being raised.
> >
> > The fact that the bylaws and PDP allow a policy does not prove that
> policy
> > is necessary, proportionate, or the best instrument. Likewise, the
> absence
> > of a staff statement saying ?policy is not needed? is not evidence that
> it
> > is needed. Silence cannot manufacture necessity.
> >
> > Kone?s examples remain relevant because they show that the same technical
> > outcome can be achieved operationally. The unanswered question is what
> > binding policy adds beyond rigidity and registry enforcement.
> >
> > A procedural route does not justify itself merely because it is familiar.
> > That is how process becomes mandate: the PDP permits policy, therefore
> > policy is treated as necessary, and the resulting enforcement is then
> > called community authority.
> >
> > Last Call exists precisely to test unresolved concerns, including the
> > choice of instrument. Consensus is not protected by declaring that it was
> > already reached before those concerns were answered.
> >
> > I therefore support Kone?s questions and remain opposed to the policy
> > route.
> >
> > Regards,
> > Nonhlanhla
> >
> >
> >
> > On Tue, 21 Jul 2026, 1:05 pm <rpd-request at afrinic.net> wrote:
> >
> > > Send RPD mailing list submissions to
> > > rpd at afrinic.net
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > https://lists.afrinic.net/mailman/listinfo/rpd
> > > or, via email, send a message with subject or body 'help' to
> > > rpd-request at afrinic.net
> > >
> > > You can reach the person managing the list at
> > > rpd-owner at afrinic.net
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of RPD digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. Re: RPD Digest, Vol 222, Issue 122 (jordi.palet at consulintel.es)
> > >
> > >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Tue, 21 Jul 2026 13:03:53 +0200
> > > From: "jordi.palet at consulintel.es" <jordi.palet at consulintel.es>
> > > To: rpd at afrinic.net
> > > Subject: Re: [rpd] RPD Digest, Vol 222, Issue 122
> > > Message-ID: <3071913E-7C72-49BC-BEDD-B7F26DE20A96 at consulintel.es>
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Well ? that?s incorrect. Nobody in the community, neither the staff
> > impact
> > > assessment, said that a policy is not needed and many folks already
> > > contested several times, that doing it by means of a policy is valid
> > > according to the bylaws and PDP and it has not been demonstrated by
> > > objections that following this path, with is the most regular one in
> > > AFRINIC, creates any harm or problem.
> > >
> > > So repeating the argument, by many folks, many times, doesn?t
> demonstrate
> > > ?per se" that it is a valid objection to revert the already reached
> > > consensus. Of course, this is a decision that need to be taken by PDP
> > > chairs, but this is my view point from an exclusive ?procedural? basis.
> > >
> > > Regards,
> > > Jordi
> > >
> > > @jordipalet
> > >
> > > > El 21 jul 2026, a las 12:46, Fundiswa Nadia Maseko <
> > > fundiswanadia2 at gmail.com> escribi?:
> > > >
> > > > Dear Jordi,
> > > >
> > > > Thank you for your clarification.
> > > >
> > > > I understand your point that the proposal has already reached
> consensus
> > > and that Last Call is intended to identify any weaknesses that may have
> > > been overlooked.
> > > >
> > > > My concern is precisely that if the choice of mechanism was not
> > > sufficiently examined during the earlier discussions, then it remains a
> > > valid point to raise during Last Call. If a proposal introduces policy
> > > where an operational approach could achieve the same objective, that
> > > affects whether policy is the appropriate solution in the first place.
> > > >
> > > > I appreciate that consensus was declared, but consensus does not
> > prevent
> > > the community from identifying a concern that may not have received
> > enough
> > > attention. Last Call exists to give the community one final opportunity
> > to
> > > do exactly that.
> > > >
> > > >
> > > > Kind regards,
> > > >
> > > > Fundiswa
> > > >
> > > > On Tue, 21 Jul 2026, 12:30 , <rpd-request at afrinic.net <mailto:
> > > rpd-request at afrinic.net>> wrote:
> > > >> Send RPD mailing list submissions to
> > > >> rpd at afrinic.net <mailto:rpd at afrinic.net>
> > > >>
> > > >> To subscribe or unsubscribe via the World Wide Web, visit
> > > >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> or, via email, send a message with subject or body 'help' to
> > > >> rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>
> > > >>
> > > >> You can reach the person managing the list at
> > > >> rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>
> > > >>
> > > >> When replying, please edit your Subject line so it is more specific
> > > >> than "Re: Contents of RPD digest..."
> > > >>
> > > >>
> > > >> Today's Topics:
> > > >>
> > > >> 1. Re: RPD Digest, Vol 222, Issue 119 (
> jordi.palet at consulintel.es
> > > <mailto:jordi.palet at consulintel.es>)
> > > >>
> > > >>
> > > >>
> ----------------------------------------------------------------------
> > > >>
> > > >> Message: 1
> > > >> Date: Tue, 21 Jul 2026 12:29:07 +0200
> > > >> From: "jordi.palet at consulintel.es <mailto:
> jordi.palet at consulintel.es
> > >"
> > > <jordi.palet at consulintel.es <mailto:jordi.palet at consulintel.es>>
> > > >> To: rpd at afrinic.net <mailto:rpd at afrinic.net>
> > > >> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 119
> > > >> Message-ID: <D895F390-7813-4560-98A7-EEA806F6136A at consulintel.es
> > > <mailto:D895F390-7813-4560-98A7-EEA806F6136A at consulintel.es>>
> > > >> Content-Type: text/plain; charset="utf-8"
> > > >>
> > > >> Hi Fundiswa,
> > > >>
> > > >> Is not a matter of what is practical and what not.
> > > >>
> > > >> It is a matter that, during the discussion of the policy proposal
> > > (which is not the same as the Last Call), the community reached
> consensus
> > > on making it this way. RIRs follow the same procedures for reaching
> > > consensus as IETF, this has been said several times. The Last Call is a
> > > last opportunity to discover any weak point in a proposal that already
> > > reached consensus, and was OVERLOOKED before. Is not about discussing
> if
> > > the proposal should be a proposal or an operational decision. This is
> no
> > > longer the moment to discuss that (it should have done when the
> proposal
> > > was being discussed before reaching consensus), and many folks in this
> > > discussing are ignoring that, probably because they are not used to
> IETF
> > > procedures.
> > > >>
> > > >> Otherwise, you can remain silent during the proposal discussion,
> > during
> > > the presentation in the PPM and object to it after reached consensus,
> > which
> > > is an incorrect procedure.
> > > >>
> > > >> One more example: we could have asked AFRINIC many years ago to
> write
> > > the Soft Landing as an operational thing, instead we as a community,
> > > decided to make it a policy proposal. Same here. However, the community
> > > decided to do it as a proposal and it was accepted that way at the
> right
> > > time, not in the Last Call.
> > > >>
> > > >> By the way, I love cooking so from time to time follow some
> > > documentaries about that. Are you the same person as the famous chef? I
> > > think I saw you in a TV program some months ago or I?m confused.
> > > >>
> > > >> Regards,
> > > >> Jordi
> > > >>
> > > >> @jordipalet
> > > >>
> > > >> > El 21 jul 2026, a las 12:03, Fundiswa Nadia Maseko <
> > > fundiswanadia2 at gmail.com <mailto:fundiswanadia2 at gmail.com>> escribi?:
> > > >> >
> > > >> > Dear Jordi,
> > > >> >
> > > >> > Thank you for your response.
> > > >> >
> > > >> > I agree that AFRINIC is not required to follow the same approach
> as
> > > other RIRs. Every region should make decisions that suit its own
> > community.
> > > >> >
> > > >> > My point, however, is slightly different. I wasn't suggesting that
> > > AFRINIC should copy another RIR simply because they did it that way.
> > > >> >
> > > >> > Rather, I'm asking what specific problem is solved by making this
> a
> > > policy instead of implementing it operationally. If both approaches
> > achieve
> > > the same technical outcome, then what additional value does the policy
> > > itself provide?
> > > >> >
> > > >> > I think that's an important distinction. The fact that the
> community
> > > can choose policy doesn't necessarily mean policy is the most
> appropriate
> > > mechanism in every case.
> > > >> >
> > > >> > I'd be interested to hear what practical or technical benefit you
> > > believe is only possible through policy and not through an operational
> > > implementation.
> > > >> >
> > > >> > Kind regards,
> > > >> >
> > > >> > Fundiswa
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Tue, 21 Jul 2026, 11:57 , <rpd-request at afrinic.net <mailto:
> > > rpd-request at afrinic.net> <mailto:rpd-request at afrinic.net <mailto:
> > > rpd-request at afrinic.net>>> wrote:
> > > >> >> Send RPD mailing list submissions to
> > > >> >> rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>
> > > >> >>
> > > >> >> To subscribe or unsubscribe via the World Wide Web, visit
> > > >> >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> or, via email, send a message with subject or body 'help' to
> > > >> >> rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>
> > > <mailto:rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>>
> > > >> >>
> > > >> >> You can reach the person managing the list at
> > > >> >> rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>
> > > <mailto:rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>>
> > > >> >>
> > > >> >> When replying, please edit your Subject line so it is more
> specific
> > > >> >> than "Re: Contents of RPD digest..."
> > > >> >>
> > > >> >>
> > > >> >> Today's Topics:
> > > >> >>
> > > >> >> 1. Re: RPD Digest, Vol 222, Issue 111 (Nia Petronella)
> > > >> >>
> > > >> >>
> > > >> >>
> > > ----------------------------------------------------------------------
> > > >> >>
> > > >> >> Message: 1
> > > >> >> Date: Tue, 21 Jul 2026 11:56:49 +0200
> > > >> >> From: Nia Petronella <nonhlanhlapetronella85 at gmail.com <mailto:
> > > nonhlanhlapetronella85 at gmail.com> <mailto:
> > nonhlanhlapetronella85 at gmail.com
> > > <mailto:nonhlanhlapetronella85 at gmail.com>>>
> > > >> >> To: Andrew Alston <aa at alstonnetworks.net <mailto:
> > > aa at alstonnetworks.net> <mailto:aa at alstonnetworks.net <mailto:
> > > aa at alstonnetworks.net>>>
> > > >> >> Cc: rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > rpd at afrinic.net
> > > <mailto:rpd at afrinic.net>>
> > > >> >> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 111
> > > >> >> Message-ID:
> > > >> >> <CA+mDOg0DqqBO74UVnd9mEr-P=
> > > itGtjGx5Uh4vYJ8e95YZ1ooRg at mail.gmail.com <mailto:
> > > itGtjGx5Uh4vYJ8e95YZ1ooRg at mail.gmail.com> <mailto:
> > > itGtjGx5Uh4vYJ8e95YZ1ooRg at mail.gmail.com <mailto:
> > > itGtjGx5Uh4vYJ8e95YZ1ooRg at mail.gmail.com>>>
> > > >> >> Content-Type: text/plain; charset="utf-8"
> > > >> >>
> > > >> >> Dear Andrew,
> > > >> >>
> > > >> >> I do not accept the binary you have presented.
> > > >> >>
> > > >> >> No one is suggesting that AFRINIC should make operational changes
> > in
> > > secret
> > > >> >> or without community input. An operational change can be
> published,
> > > >> >> consulted on, tested, documented, and reviewed. The real question
> > is
> > > >> >> whether that input must be converted into binding policy enforced
> > by
> > > the
> > > >> >> registry.
> > > >> >>
> > > >> >> Calling AFRINIC ?community-driven? does not answer who the
> > community
> > > is or
> > > >> >> what it is authorised to bind. A self-selecting group of
> > mailing-list
> > > >> >> participants can provide expertise, support, and objection. It
> does
> > > not
> > > >> >> automatically represent every member, resource holder, network,
> > > customer,
> > > >> >> or other affected party.
> > > >> >>
> > > >> >> The institutional reality also remains unchanged: participants
> > > discuss the
> > > >> >> policy, but AFRINIC interprets and enforces it. Community
> > > participation
> > > >> >> therefore does not eliminate registry power. It can become the
> > > language
> > > >> >> used to legitimise that power.
> > > >> >>
> > > >> >> This is why Kone?s examples matter. If LACNIC, RIPE NCC, and ARIN
> > can
> > > >> >> achieve the same technical outcome through operational
> mechanisms,
> > > then
> > > >> >> policy is not technically inevitable. Proponents should explain
> > what
> > > >> >> additional technical result binding policy provides, beyond
> > > converting an
> > > >> >> IRR setting into an enforceable obligation.
> > > >> >>
> > > >> >> I also disagree that an objection is valid only if it proves
> > > immediate
> > > >> >> operational harm or implementation failure. The choice of
> > instrument,
> > > >> >> proportionality, reversibility, and expansion of enforcement
> > > authority are
> > > >> >> legitimate policy concerns. Last Call is not limited to asking
> > > whether
> > > >> >> software will break. It must also ask whether the proposed power
> is
> > > greater
> > > >> >> than the problem requires.
> > > >> >>
> > > >> >> Rough consensus does not require every objection to be
> > accommodated.
> > > But an
> > > >> >> objection is not ?addressed? merely because supporters repeat
> that
> > > the
> > > >> >> community prefers policy. That is the very assumption being
> > > challenged.
> > > >> >> Procedure cannot be used to prove its own mandate.
> > > >> >>
> > > >> >> The fact that the RIR system has operated this way for decades
> > > demonstrates
> > > >> >> continuity of practice. It does not establish unlimited
> legitimacy
> > > of scope.
> > > >> >>
> > > >> >> I support Kone?s questions and remain opposed to
> > > AFPUB-2026-ASN-001-DRAFT02.
> > > >> >>
> > > >> >> Regards,
> > > >> >> Nonhlanhla
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >> On Tue, 21 Jul 2026, 10:26 am Andrew Alston <
> aa at alstonnetworks.net
> > > <mailto:aa at alstonnetworks.net> <mailto:aa at alstonnetworks.net <mailto:
> > > aa at alstonnetworks.net>>> wrote:
> > > >> >>
> > > >> >> > 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.
> > > >> >> >
> > > >> >> > Without policy, the discretion and rules are entirely in the
> > hands
> > > of the
> > > >> >> > registry, and the community voice is removed.
> > > >> >> >
> > > >> >> > 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.
> > > >> >> >
> > > >> >> > 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.
> > > >> >> >
> > > >> >> > 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.
> > > >> >> >
> > > >> >> > Again, I support the policy and I see no technical or
> > > evidence/fact-based
> > > >> >> > arguments against said policy.
> > > >> >> >
> > > >> >> > Andrew
> > > >> >> >
> > > >> >> > On Tue, Jul 21, 2026 at 09:34, Nia Petronella <
> > > >> >> > nonhlanhlapetronella85 at gmail.com <mailto:
> > > nonhlanhlapetronella85 at gmail.com> <mailto:
> > nonhlanhlapetronella85 at gmail.com
> > > <mailto:nonhlanhlapetronella85 at gmail.com>>> wrote:
> > > >> >> >
> > > >> >> >> Dear PDWG,
> > > >> >> >>
> > > >> >> >> Kone is asking the right question.
> > > >> >> >>
> > > >> >> >> 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.
> > > >> >> >>
> > > >> >> >> 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.
> > > >> >> >>
> > > >> >> >> 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.
> > > >> >> >>
> > > >> >> >> 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.
> > > >> >> >>
> > > >> >> >> The proponents should therefore answer Kone directly: what
> > > technical
> > > >> >> >> outcome can mandatory policy achieve here that an operational
> > > >> >> >> implementation cannot?
> > > >> >> >>
> > > >> >> >> Until that is clearly demonstrated, I support Kone?s questions
> > > and remain
> > > >> >> >> opposed to the policy route.
> > > >> >> >>
> > > >> >> >> Regards,
> > > >> >> >> Nonhlanhla
> > > >> >> >>
> > > >> >> >>
> > > >> >> >>
> > > >> >> >> On Tue, 21 Jul 2026, 8:20 am <rpd-request at afrinic.net
> <mailto:
> > > rpd-request at afrinic.net> <mailto:rpd-request at afrinic.net <mailto:
> > > rpd-request at afrinic.net>>> wrote:
> > > >> >> >>
> > > >> >> >>> Send RPD mailing list submissions to
> > > >> >> >>> rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> To subscribe or unsubscribe via the World Wide Web, visit
> > > >> >> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> or, via email, send a message with subject or body 'help' to
> > > >> >> >>> rpd-request at afrinic.net <mailto:
> > rpd-request at afrinic.net>
> > > <mailto:rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> You can reach the person managing the list at
> > > >> >> >>> rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>
> > > <mailto:rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> When replying, please edit your Subject line so it is more
> > > specific
> > > >> >> >>> than "Re: Contents of RPD digest..."
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> Today's Topics:
> > > >> >> >>>
> > > >> >> >>> 1. Re: RPD Digest, Vol 222, Issue 110 (Tshepo Masuku)
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > ----------------------------------------------------------------------
> > > >> >> >>>
> > > >> >> >>> Message: 1
> > > >> >> >>> Date: Tue, 21 Jul 2026 06:19:05 +0000
> > > >> >> >>> From: Tshepo Masuku <TshepoMasuku26 at hotmail.com <mailto:
> > > TshepoMasuku26 at hotmail.com> <mailto:TshepoMasuku26 at hotmail.com
> <mailto:
> > > TshepoMasuku26 at hotmail.com>>>
> > > >> >> >>> To: "rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>" <rpd at afrinic.net <mailto:
> > > rpd at afrinic.net> <mailto:rpd at afrinic.net <mailto:rpd at afrinic.net>>>
> > > >> >> >>> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 110
> > > >> >> >>> Message-ID:
> > > >> >> >>> <
> > > >> >> >>>
> > >
> >
> VI2PR04MB10545A0FC740F5DC6041F6C75CAC22 at VI2PR04MB10545.eurprd04.prod.outlook.com
> > > <mailto:
> > >
> >
> VI2PR04MB10545A0FC740F5DC6041F6C75CAC22 at VI2PR04MB10545.eurprd04.prod.outlook.com
> > >
> > > <mailto:
> > >
> >
> VI2PR04MB10545A0FC740F5DC6041F6C75CAC22 at VI2PR04MB10545.eurprd04.prod.outlook.com
> > > <mailto:
> > >
> >
> VI2PR04MB10545A0FC740F5DC6041F6C75CAC22 at VI2PR04MB10545.eurprd04.prod.outlook.com
> > > >>
> > > >> >> >>> >
> > > >> >> >>>
> > > >> >> >>> Content-Type: text/plain; charset="windows-1252"
> > > >> >> >>>
> > > >> >> >>> Dear All,
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> The unanswered question remains: what technical necessity
> > > requires
> > > >> >> >>> policy rather than operational implementation?
> > > >> >> >>>
> > > >> >> >>> Until that is answered, Kone?s objection stands, and I
> support
> > > it.
> > > >> >> >>>
> > > >> >> >>> Regards,
> > > >> >> >>> Tshepo
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> ________________________________
> > > >> >> >>> From: rpd-request at afrinic.net <mailto:
> rpd-request at afrinic.net>
> > > <mailto:rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>> <
> > > rpd-request at afrinic.net <mailto:rpd-request at afrinic.net> <mailto:
> > > rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>>>
> > > >> >> >>> Sent: Monday, July 20, 2026 11:10:57 pm
> > > >> >> >>> To: rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>> <rpd at afrinic.net <mailto:
> > > rpd at afrinic.net> <mailto:rpd at afrinic.net <mailto:rpd at afrinic.net>>>
> > > >> >> >>> Subject: RPD Digest, Vol 222, Issue 110
> > > >> >> >>>
> > > >> >> >>> Send RPD mailing list submissions to
> > > >> >> >>> rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> To subscribe or unsubscribe via the World Wide Web, visit
> > > >> >> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> or, via email, send a message with subject or body 'help' to
> > > >> >> >>> rpd-request at afrinic.net <mailto:
> > rpd-request at afrinic.net>
> > > <mailto:rpd-request at afrinic.net <mailto:rpd-request at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> You can reach the person managing the list at
> > > >> >> >>> rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>
> > > <mailto:rpd-owner at afrinic.net <mailto:rpd-owner at afrinic.net>>
> > > >> >> >>>
> > > >> >> >>> When replying, please edit your Subject line so it is more
> > > specific
> > > >> >> >>> than "Re: Contents of RPD digest..."
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> Today's Topics:
> > > >> >> >>>
> > > >> >> >>> 1. Re: Writing tools (Ben Roberts - AfriNIC)
> > > >> >> >>> 2. Re: [Last Call] Draft Policy Proposal - Hierarchical
> > Names
> > > >> >> >>> for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Kone)
> > > >> >> >>> 3. Re: [Last Call] Draft Policy Proposal - Hierarchical
> > Names
> > > >> >> >>> for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
> > > >> >> >>> (jordi.palet at consulintel.es <mailto:
> > > jordi.palet at consulintel.es> <mailto:jordi.palet at consulintel.es
> <mailto:
> > > jordi.palet at consulintel.es>>)
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > ----------------------------------------------------------------------
> > > >> >> >>>
> > > >> >> >>> Message: 1
> > > >> >> >>> Date: Mon, 20 Jul 2026 21:26:40 +0200
> > > >> >> >>> From: Ben Roberts - AfriNIC <ben.roberts at afrinic.net
> <mailto:
> > > ben.roberts at afrinic.net> <mailto:ben.roberts at afrinic.net <mailto:
> > > ben.roberts at afrinic.net>>>
> > > >> >> >>> To: Nonjabulo Sphilile <nonjabulosphilile at gmail.com <mailto:
> > > nonjabulosphilile at gmail.com> <mailto:nonjabulosphilile at gmail.com
> > <mailto:
> > > nonjabulosphilile at gmail.com>>>
> > > >> >> >>> Cc: rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>
> > > >> >> >>> Subject: Re: [rpd] Writing tools
> > > >> >> >>> Message-ID: <
> 09EB63D0-2FBC-48F9-B752-43E842D85096 at afrinic.net
> > > <mailto:09EB63D0-2FBC-48F9-B752-43E842D85096 at afrinic.net> <mailto:
> > > 09EB63D0-2FBC-48F9-B752-43E842D85096 at afrinic.net <mailto:
> > > 09EB63D0-2FBC-48F9-B752-43E842D85096 at afrinic.net>>>
> > > >> >> >>> Content-Type: text/plain; charset="us-ascii"
> > > >> >> >>>
> > > >> >> >>> An HTML attachment was scrubbed...
> > > >> >> >>> URL: <
> > > >> >> >>>
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260720/33c3ac9e/attachment-0001.html
> > > >> >> >>> >
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> Message: 2
> > > >> >> >>> Date: Mon, 20 Jul 2026 20:34:20 +0000
> > > >> >> >>> From: Kone <bakenon.kone at sancfis.net <mailto:
> > > bakenon.kone at sancfis.net> <mailto:bakenon.kone at sancfis.net <mailto:
> > > bakenon.kone at sancfis.net>>>
> > > >> >> >>> To: Seun Ojedeji <seun.ojedeji at gmail.com <mailto:
> > > seun.ojedeji at gmail.com> <mailto:seun.ojedeji at gmail.com <mailto:
> > > seun.ojedeji at gmail.com>>>
> > > >> >> >>> Cc: rpd <rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>>
> > > >> >> >>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal -
> > > Hierarchical
> > > >> >> >>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
> > > >> >> >>> Message-ID:
> > > >> >> >>> <CADHquJpYPT91G8hHPsnXDJKp=
> > > >> >> >>> 3cyspC-xR5t8iHs0EN4tTMhwQ at mail.gmail.com <mailto:
> > > 3cyspC-xR5t8iHs0EN4tTMhwQ at mail.gmail.com> <mailto:
> > > 3cyspC-xR5t8iHs0EN4tTMhwQ at mail.gmail.com <mailto:
> > > 3cyspC-xR5t8iHs0EN4tTMhwQ at mail.gmail.com>>>
> > > >> >> >>> Content-Type: text/plain; charset="utf-8"
> > > >> >> >>>
> > > >> >> >>> Hello Seun,
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> To help close the ongoing discussions, I believe addressing
> the
> > > >> >> >>> questions I
> > > >> >> >>> raised would bring clarity:
> > > >> >> >>> * LACNIC enforces hierarchical AS?SET naming operationally,
> as
> > > part of
> > > >> >> >>> their IRR design from inception.
> > > >> >> >>> * RIPE NCC handles IRR changes through their Numbered Work
> > Items
> > > (NWI)
> > > >> >> >>> process, not through policy.
> > > >> >> >>> * ARIN uses the ACSP (Consultation and Suggestion Process)
> for
> > > IRR
> > > >> >> >>> operational matters, again without policy.
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> These examples show that other RIRs (except APNIC) treat
> AS?SET
> > > naming as
> > > >> >> >>> an operational IRR matter, not a policy obligation.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> Thanks.
> > > >> >> >>> ---
> > > >> >> >>> Kone
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji <
> > > seun.ojedeji at gmail.com <mailto:seun.ojedeji at gmail.com> <mailto:
> > > seun.ojedeji at gmail.com <mailto:seun.ojedeji at gmail.com>>> a
> > > >> >> >>> ?crit :
> > > >> >> >>>
> > > >> >> >>> > Hello Bakenon,
> > > >> >> >>> >
> > > >> >> >>> > Do refer to the proposal as it references URL to other
> RIR's
> > > policies
> > > >> >> >>> for
> > > >> >> >>> > thiis:
> > > >> >> >>> >
> > > >> >> >>> > https://www.afrinic.net/afpub-2026-asn-001-draft02.html
> > > >> >> >>> >
> > > >> >> >>> > Regards
> > > >> >> >>> >
> > > >> >> >>> > ----
> > > >> >> >>> > Sent from my mobile
> > > >> >> >>> > kindly excuse typos
> > > >> >> >>> >
> > > >> >> >>> > On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE, <
> > > bakenon.kone at sancfis.net <mailto:bakenon.kone at sancfis.net> <mailto:
> > > bakenon.kone at sancfis.net <mailto:bakenon.kone at sancfis.net>>>
> > > >> >> >>> > wrote:
> > > >> >> >>> >
> > > >> >> >>> >> Dear PDWG,
> > > >> >> >>> >>
> > > >> >> >>> >> I have been following the discussions on the hierarchical
> > > AS?SET
> > > >> >> >>> naming
> > > >> >> >>> >> scheme and would like clarification on a few points:
> > > >> >> >>> >>
> > > >> >> >>> >> 1. Could this matter be addressed operationally, as is
> done
> > > in ARIN,
> > > >> >> >>> >> LACNIC, and RIPE NCC, without requiring policy changes?
> > > >> >> >>> >>
> > > >> >> >>> >> 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?
> > > >> >> >>> >>
> > > >> >> >>> >> 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?"
> > > >> >> >>> >>
> > > >> >> >>> >> Thank you.
> > > >> >> >>> >> ---
> > > >> >> >>> >> Kone
> > > >> >> >>> >>
> > > >> >> >>> >>
> > > >> >> >>> >>
> > > >> >> >>> >> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal <
> > > hytham at tra.gov.eg <mailto:hytham at tra.gov.eg> <mailto:hytham at tra.gov.eg
> > > <mailto:hytham at tra.gov.eg>>> a
> > > >> >> >>> >> ?crit :
> > > >> >> >>> >>
> > > >> >> >>> >>> Dear PDWG,
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> 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.
> > > >> >> >>> >>>
> > > >> >> >>> >>> * Proposal Name: Hierarchical Names for New AS-SETs
> > > >> >> >>> >>>
> > > >> >> >>> >>> * Proposal ID: AFPUB-2026-ASN-001-DRAFT02
> > > >> >> >>> >>>
> > > >> >> >>> >>> * Proposal URL:
> > > >> >> >>> >>> https://www.afrinic.net/afpub-2026-asn-001-draft02.html
> > > >> >> >>> >>>
> > > >> >> >>> >>> Last Call closes on: July 31, 2026, at 23:59 UTC.
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> 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.
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> As always, we kindly request that all participants adhere
> > to
> > > the
> > > >> >> >>> AFRINIC
> > > >> >> >>> >>> Code of Conduct<https://www.afrinic.net/code> to
> maintain
> > a
> > > >> >> >>> respectful
> > > >> >> >>> >>> and professional environment on the mailing list.
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> Kind regards,
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> Haitham el Nakhal
> > > >> >> >>> >>>
> > > >> >> >>> >>> AFRINIC PDWG Co-Chair
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> _______________________________________________
> > > >> >> >>> >>> RPD mailing list
> > > >> >> >>> >>> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > > RPD at afrinic.net <mailto:RPD at afrinic.net>>
> > > >> >> >>> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> >>>
> > > >> >> >>> >> _______________________________________________
> > > >> >> >>> >> RPD mailing list
> > > >> >> >>> >> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > > RPD at afrinic.net <mailto:RPD at afrinic.net>>
> > > >> >> >>> >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> >>
> > > >> >> >>> >
> > > >> >> >>> -------------- next part --------------
> > > >> >> >>> An HTML attachment was scrubbed...
> > > >> >> >>> URL: <
> > > >> >> >>>
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260720/4563e1d5/attachment-0001.html
> > > >> >> >>> >
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> Message: 3
> > > >> >> >>> Date: Mon, 20 Jul 2026 23:10:04 +0200
> > > >> >> >>> From: "jordi.palet at consulintel.es <mailto:
> > > jordi.palet at consulintel.es> <mailto:jordi.palet at consulintel.es
> <mailto:
> > > jordi.palet at consulintel.es>>" <jordi.palet at consulintel.es <mailto:
> > > jordi.palet at consulintel.es> <mailto:jordi.palet at consulintel.es
> <mailto:
> > > jordi.palet at consulintel.es>>>
> > > >> >> >>> To: rpd <rpd at afrinic.net <mailto:rpd at afrinic.net> <mailto:
> > > rpd at afrinic.net <mailto:rpd at afrinic.net>>>
> > > >> >> >>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal -
> > > Hierarchical
> > > >> >> >>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
> > > >> >> >>> Message-ID: <
> > F22A09CF-A827-4D7F-B077-E0B9C774AF00 at consulintel.es
> > > <mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00 at consulintel.es> <mailto:
> > > F22A09CF-A827-4D7F-B077-E0B9C774AF00 at consulintel.es <mailto:
> > > F22A09CF-A827-4D7F-B077-E0B9C774AF00 at consulintel.es>>>
> > > >> >> >>> Content-Type: text/plain; charset="utf-8"
> > > >> >> >>>
> > > >> >> >>> Hi Kone,
> > > >> >> >>>
> > > >> >> >>> And what is the relevance of that?
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> Regards,
> > > >> >> >>> Jordi
> > > >> >> >>>
> > > >> >> >>> @jordipalet
> > > >> >> >>>
> > > >> >> >>> > El 20 jul 2026, a las 22:34, Kone <
> bakenon.kone at sancfis.net
> > > <mailto:bakenon.kone at sancfis.net> <mailto:bakenon.kone at sancfis.net
> > > <mailto:bakenon.kone at sancfis.net>>> escribi?:
> > > >> >> >>> >
> > > >> >> >>> > Hello Seun,
> > > >> >> >>> > 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.
> > > >> >> >>> >
> > > >> >> >>> > To help close the ongoing discussions, I believe addressing
> > the
> > > >> >> >>> questions I raised would bring clarity:
> > > >> >> >>> > * LACNIC enforces hierarchical AS?SET naming operationally,
> > as
> > > part of
> > > >> >> >>> their IRR design from inception.
> > > >> >> >>> > * RIPE NCC handles IRR changes through their Numbered Work
> > > Items (NWI)
> > > >> >> >>> process, not through policy.
> > > >> >> >>> > * ARIN uses the ACSP (Consultation and Suggestion Process)
> > for
> > > IRR
> > > >> >> >>> operational matters, again without policy.
> > > >> >> >>> >
> > > >> >> >>> >
> > > >> >> >>> > These examples show that other RIRs (except APNIC) treat
> > > AS?SET naming
> > > >> >> >>> as an operational IRR matter, not a policy obligation.
> > > >> >> >>> >
> > > >> >> >>> > 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.
> > > >> >> >>> >
> > > >> >> >>> > Thanks.
> > > >> >> >>> > ---
> > > >> >> >>> > Kone
> > > >> >> >>> >
> > > >> >> >>> >
> > > >> >> >>> >
> > > >> >> >>> > Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji <
> > > seun.ojedeji at gmail.com <mailto:seun.ojedeji at gmail.com> <mailto:
> > > seun.ojedeji at gmail.com <mailto:seun.ojedeji at gmail.com>>
> > > >> >> >>> <mailto:seun.ojedeji at gmail.com <mailto:
> seun.ojedeji at gmail.com>
> > > <mailto:seun.ojedeji at gmail.com <mailto:seun.ojedeji at gmail.com>>>> a
> > ?crit
> > > :
> > > >> >> >>> >> Hello Bakenon,
> > > >> >> >>> >>
> > > >> >> >>> >> Do refer to the proposal as it references URL to other
> RIR's
> > > policies
> > > >> >> >>> for thiis:
> > > >> >> >>> >>
> > > >> >> >>> >> https://www.afrinic.net/afpub-2026-asn-001-draft02.html
> > > >> >> >>> >>
> > > >> >> >>> >> Regards
> > > >> >> >>> >>
> > > >> >> >>> >> ----
> > > >> >> >>> >> Sent from my mobile
> > > >> >> >>> >> kindly excuse typos
> > > >> >> >>> >>
> > > >> >> >>> >> On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE, <
> > > bakenon.kone at sancfis.net <mailto:bakenon.kone at sancfis.net> <mailto:
> > > bakenon.kone at sancfis.net <mailto:bakenon.kone at sancfis.net>>
> > > >> >> >>> <mailto:bakenon.kone at sancfis.net <mailto:
> > > bakenon.kone at sancfis.net> <mailto:bakenon.kone at sancfis.net <mailto:
> > > bakenon.kone at sancfis.net>>>> wrote:
> > > >> >> >>> >>> Dear PDWG,
> > > >> >> >>> >>>
> > > >> >> >>> >>> I have been following the discussions on the hierarchical
> > > AS?SET
> > > >> >> >>> naming scheme and would like clarification on a few points:
> > > >> >> >>> >>>
> > > >> >> >>> >>> 1. Could this matter be addressed operationally, as is
> done
> > > in ARIN,
> > > >> >> >>> LACNIC, and RIPE NCC, without requiring policy changes?
> > > >> >> >>> >>>
> > > >> >> >>> >>> 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?
> > > >> >> >>> >>>
> > > >> >> >>> >>> 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?"
> > > >> >> >>> >>>
> > > >> >> >>> >>> Thank you.
> > > >> >> >>> >>> ---
> > > >> >> >>> >>> Kone
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>>
> > > >> >> >>> >>> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal <
> > > hytham at tra.gov.eg <mailto:hytham at tra.gov.eg> <mailto:hytham at tra.gov.eg
> > > <mailto:hytham at tra.gov.eg>>
> > > >> >> >>> <mailto:hytham at tra.gov.eg <mailto:hytham at tra.gov.eg>
> <mailto:
> > > hytham at tra.gov.eg <mailto:hytham at tra.gov.eg>>>> a ?crit :
> > > >> >> >>> >>>> Dear PDWG,
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> 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.
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> * Proposal Name: Hierarchical Names for New AS-SETs
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> * Proposal ID: AFPUB-2026-ASN-001-DRAFT02
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> * Proposal URL:
> > > >> >> >>> https://www.afrinic.net/afpub-2026-asn-001-draft02.html
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> Last Call closes on: July 31, 2026, at 23:59 UTC.
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> 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.
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> As always, we kindly request that all participants
> adhere
> > > to the
> > > >> >> >>> AFRINIC Code of Conduct<https://www.afrinic.net/code> to
> > > maintain a
> > > >> >> >>> respectful and professional environment on the mailing list.
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> Kind regards,
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> Haitham el Nakhal
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> AFRINIC PDWG Co-Chair
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>>
> > > >> >> >>> >>>> _______________________________________________
> > > >> >> >>> >>>> RPD mailing list
> > > >> >> >>> >>>> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > > RPD at afrinic.net <mailto:RPD at afrinic.net>> <mailto:RPD at afrinic.net
> > <mailto:
> > > RPD at afrinic.net> <mailto:RPD at afrinic.net <mailto:RPD at afrinic.net>>>
> > > >> >> >>> >>>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> >>> _______________________________________________
> > > >> >> >>> >>> RPD mailing list
> > > >> >> >>> >>> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > > RPD at afrinic.net <mailto:RPD at afrinic.net>> <mailto:RPD at afrinic.net
> > <mailto:
> > > RPD at afrinic.net> <mailto:RPD at afrinic.net <mailto:RPD at afrinic.net>>>
> > > >> >> >>> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>> > _______________________________________________
> > > >> >> >>> > RPD mailing list
> > > >> >> >>> > RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > > RPD at afrinic.net <mailto:RPD at afrinic.net>>
> > > >> >> >>> > https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> **********************************************
> > > >> >> >>> IPv4 is over
> > > >> >> >>> Are you ready for the new Internet ?
> > > >> >> >>> http://www.theipv6company.com <
> http://www.theipv6company.com/>
> > <
> > > http://www.theipv6company.com/>
> > > >> >> >>> The IPv6 Company
> > > >> >> >>>
> > > >> >> >>> 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.
> > > >> >> >>>
> > > >> >> >>> -------------- next part --------------
> > > >> >> >>> An HTML attachment was scrubbed...
> > > >> >> >>> URL: <
> > > >> >> >>>
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260720/b6777fa7/attachment.html
> > > >> >> >>> >
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> Subject: Digest Footer
> > > >> >> >>>
> > > >> >> >>> _______________________________________________
> > > >> >> >>> RPD mailing list
> > > >> >> >>> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > RPD at afrinic.net
> > > <mailto:RPD at afrinic.net>>
> > > >> >> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> End of RPD Digest, Vol 222, Issue 110
> > > >> >> >>> *************************************
> > > >> >> >>>
> > > >> >> >>> -------------- next part --------------
> > > >> >> >>> An HTML attachment was scrubbed...
> > > >> >> >>> URL: <
> > > >> >> >>>
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e492c668/attachment.html
> > > >> >> >>> >
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> Subject: Digest Footer
> > > >> >> >>>
> > > >> >> >>> _______________________________________________
> > > >> >> >>> RPD mailing list
> > > >> >> >>> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > RPD at afrinic.net
> > > <mailto:RPD at afrinic.net>>
> > > >> >> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> ------------------------------
> > > >> >> >>>
> > > >> >> >>> End of RPD Digest, Vol 222, Issue 111
> > > >> >> >>> *************************************
> > > >> >> >>>
> > > >> >> >> _______________________________________________
> > > >> >> >> RPD mailing list
> > > >> >> >> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:
> > RPD at afrinic.net
> > > <mailto:RPD at afrinic.net>>
> > > >> >> >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >> >>
> > > >> >> >
> > > >> >> -------------- next part --------------
> > > >> >> An HTML attachment was scrubbed...
> > > >> >> URL: <
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/9c41424a/attachment.html
> > > >
> > > >> >>
> > > >> >> ------------------------------
> > > >> >>
> > > >> >> Subject: Digest Footer
> > > >> >>
> > > >> >> _______________________________________________
> > > >> >> RPD mailing list
> > > >> >> RPD at afrinic.net <mailto:RPD at afrinic.net> <mailto:RPD at afrinic.net
> > > <mailto:RPD at afrinic.net>>
> > > >> >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >> >>
> > > >> >>
> > > >> >> ------------------------------
> > > >> >>
> > > >> >> End of RPD Digest, Vol 222, Issue 119
> > > >> >> *************************************
> > > >> > _______________________________________________
> > > >> > RPD mailing list
> > > >> > RPD at afrinic.net <mailto:RPD at afrinic.net>
> > > >> > https://lists.afrinic.net/mailman/listinfo/rpd
> > > >>
> > > >>
> > > >>
> > > >> **********************************************
> > > >> IPv4 is over
> > > >> Are you ready for the new Internet ?
> > > >> http://www.theipv6company.com <http://www.theipv6company.com/>
> > > >> The IPv6 Company
> > > >>
> > > >> 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.
> > > >>
> > > >> -------------- next part --------------
> > > >> An HTML attachment was scrubbed...
> > > >> URL: <
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/0ba797a1/attachment.html
> > > >
> > > >>
> > > >> ------------------------------
> > > >>
> > > >> Subject: Digest Footer
> > > >>
> > > >> _______________________________________________
> > > >> RPD mailing list
> > > >> RPD at afrinic.net <mailto:RPD at afrinic.net>
> > > >> https://lists.afrinic.net/mailman/listinfo/rpd
> > > >>
> > > >>
> > > >> ------------------------------
> > > >>
> > > >> End of RPD Digest, Vol 222, Issue 122
> > > >> *************************************
> > > > _______________________________________________
> > > > RPD mailing list
> > > > RPD at afrinic.net
> > > > https://lists.afrinic.net/mailman/listinfo/rpd
> > >
> > >
> > >
> > > **********************************************
> > > IPv4 is over
> > > Are you ready for the new Internet ?
> > > http://www.theipv6company.com
> > > The IPv6 Company
> > >
> > > 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.
> > >
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > > URL: <
> > >
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/d5daa838/attachment.html
> > > >
> > >
> > > ------------------------------
> > >
> > > Subject: Digest Footer
> > >
> > > _______________________________________________
> > > RPD mailing list
> > > RPD at afrinic.net
> > > https://lists.afrinic.net/mailman/listinfo/rpd
> > >
> > >
> > > ------------------------------
> > >
> > > End of RPD Digest, Vol 222, Issue 124
> > > *************************************
> > >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/fe3cdcf4/attachment.html
> > >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > RPD mailing list
> > RPD at afrinic.net
> > https://lists.afrinic.net/mailman/listinfo/rpd
> >
> >
> > ------------------------------
> >
> > End of RPD Digest, Vol 222, Issue 126
> > *************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/124f7b1b/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd
>
>
> ------------------------------
>
> End of RPD Digest, Vol 222, Issue 127
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260721/b86d155d/attachment-0001.html>
More information about the RPD
mailing list