Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] RPD Digest, Vol 222, Issue 111

Nia Petronella nonhlanhlapetronella85 at gmail.com
Tue Jul 21 06:33:31 UTC 2026 

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> 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 110 (Tshepo Masuku)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 21 Jul 2026 06:19:05 +0000
> From: Tshepo Masuku <TshepoMasuku26 at hotmail.com>
> To: "rpd at afrinic.net" <rpd at afrinic.net>
> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 110
> Message-ID:
>         <
> 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 <rpd-request at afrinic.net>
> Sent: Monday, July 20, 2026 11:10:57 pm
> To: rpd at afrinic.net <rpd at afrinic.net>
> Subject: RPD Digest, Vol 222, Issue 110
>
> 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: 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)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 20 Jul 2026 21:26:40 +0200
> From: Ben Roberts - AfriNIC <ben.roberts at afrinic.net>
> To: Nonjabulo Sphilile <nonjabulosphilile at gmail.com>
> Cc: rpd at afrinic.net
> Subject: Re: [rpd] Writing tools
> Message-ID: <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>
> To: Seun Ojedeji <seun.ojedeji at gmail.com>
> Cc: rpd <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>
> 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> 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>
> > 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> 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
> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>>
> >> _______________________________________________
> >> RPD mailing list
> >> 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" <jordi.palet at consulintel.es>
> To: rpd <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>
> 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> 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>> 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>> 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>> 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>
> >>>> https://lists.afrinic.net/mailman/listinfo/rpd
> >>> _______________________________________________
> >>> RPD mailing list
> >>> RPD at afrinic.net <mailto:RPD at afrinic.net>
> >>> https://lists.afrinic.net/mailman/listinfo/rpd
> > _______________________________________________
> > 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/20260720/b6777fa7/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 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
> https://lists.afrinic.net/mailman/listinfo/rpd
>
>
> ------------------------------
>
> End of RPD Digest, Vol 222, Issue 111
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260721/4b4b8d61/attachment-0001.html>

More information about the RPD mailing list