Search RPD Archives
[rpd] [Last Call] Draft Policy Proposal ? Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
Thulisile Mazomba
219280444 at mycput.ac.za
Sun Jul 19 20:29:04 UTC 2026
Hi Frank,
You appear to be treating your disagreement with an objection as proof that no technical objection exists.
The proposal prevents one naming collision. It does not establish the correctness of the routing data attached to that name, nor prove that mandatory registry control is the only proportionate remedy.
Those are technical and policy questions. Declaring them invalid does not resolve them.
I remain opposed.
Regards,
Thulisile
________________________________
From: rpd-request at afrinic.net <rpd-request at afrinic.net>
Sent: Sunday, 19 July 2026 20:09
To: rpd at afrinic.net <rpd at afrinic.net>
Subject: RPD Digest, Vol 222, Issue 69
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: [Last Call] Draft Policy Proposal - Hierarchical Names
for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) and Amendment of
Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02)
(Hendrik Visage)
2. Re: RPD Digest, Vol 222, Issue 45 (Gugu Dhlamini)
----------------------------------------------------------------------
Message: 1
Date: Sun, 19 Jul 2026 20:04:03 +0200
From: Hendrik Visage <hvisage at hevis.co.za>
To: Thulisile Mazomba <219280444 at mycput.ac.za>
Cc: rpd-owner at afrinic.net, rpd at afrinic.net
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical
Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) and Amendment of
Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02)
Message-ID: <0B9F65CE-7417-4996-84C6-7E395FB27544 at hevis.co.za>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Dear Thulisile,
Why did you also use an AI to respond?
Claude: `Yes ? and it's the same drafting pipeline again, now writing
a defense of itself. That's the most interesting thing about this one:
the thread has become recursive, and the message quotes my own analysis
back while exhibiting the exact markers that analysis described.a
---
Hendrik Visage
Director/Owner
HeViS.Co Systems t/a Envisage Cloud Solutions
hvisage at hevis.co.za
GSM/SMS/Signal: +27-84-612-5345
InstantMessenger: https://t.me/hvisage
On 19 Jul 2026, at 19:39, Thulisile Mazomba wrote:
> Dear colleagues,
>
> This discussion has moved away from the proposal and toward
> questioning who is allowed to object.
>
> Whether someone operates an ASN, uses drafting assistance, is new to
> the list, or is unfamiliar to long-standing participants does not
> determine whether their argument is valid. The PDP should examine the
> substance of an objection, not attempt to infer authorship from
> writing style or rank participants according to reputation.
>
> Submitting text to another language model does not establish who wrote
> it, who contributed to it, or whether the person posting it agrees
> with it. A probability produced by Claude is not evidence of
> astroturfing. It is an automated opinion about prose.
>
> Hendrik?s own quoted analysis concedes the important point: the
> distinction between authenticating the creator of an AS-SET and
> validating its contents is a real objection that still requires an
> answer. That issue does not disappear because the wording appears
> polished.
>
> The request to identify which ASNs objectors ?represent? also
> misunderstands participation. I am not claiming to represent every
> African operator, nor should any individual participant make that
> claim without authority. I am participating in my own capacity. An ASN
> is not a voting credential, and operating one does not give its holder
> a larger mandate over the policy process.
>
> Frank?s road-rule analogy is also misplaced. Governments impose
> traffic laws through public authority and accept legal accountability
> for doing so. AFRINIC is a private registry operating a technical
> database. The existence of a working group does not turn that registry
> into a legislature or every preferred operational practice into the
> equivalent of public law.
>
> The question before us remains simple: does this proposal solve the
> specific harm claimed, and is mandatory registry enforcement the
> minimum necessary mechanism?
>
> Hierarchical naming may reduce future name collisions. That is a
> useful property. It does not validate the accuracy of AS-SET
> membership, prevent incorrect customer-cone data, or make generated
> filters trustworthy by itself. Those limitations should be assessed
> honestly rather than buried beneath accusations about who wrote which
> paragraph.
>
> If the co-chairs believe several objections raise the same substantive
> issue, they may group them as one issue. That is reasonable. But they
> should then determine whether the issue has been answered on its
> merits. They should not discount it because the participants are
> unfamiliar, share a view, use similar language, or may have used
> writing tools.
>
> Participation provides evidence, criticism, and warning. Familiarity
> does not create mandate. Reputation does not replace proof. A mailing
> list should not become a private club in which established names
> decide which speakers count.
>
> I remain opposed to the proposal and ask that the discussion return to
> the proposal?s technical scope, demonstrated benefit, limitations,
> and proportionality.
>
> Regards,
> Thulisile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260719/421ab07f/attachment-0001.html>
------------------------------
Message: 2
Date: Sun, 19 Jul 2026 20:09:25 +0200
From: Gugu Dhlamini <gugudhlamini343 at gmail.com>
To: Frank Habicht <geier at geier.ne.tz>, rpd-owner at afrinic.net
Cc: rpd at afrinic.net
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 45
Message-ID:
<CADMrvbNHq+u4HTi1r9qNoX4A9LH69czSnPoAAeVPSYq8oai01A at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Dear Frank,
A problem statement establishes that a concern exists. It does not
establish that this proposal is necessary, proportionate, or the only valid
remedy.
Questioning and asking that contributions be disregarded because their
wording appears similar is not consensus assessment. It is #Gatekeeping.
Participation may provide evidence and objection; familiarity and style do
not create or remove mandate.
Please answer the unresolved policy concern rather than analyse the people
raising it.
I remain opposed.
Regards,
Gugu
On Sun, 19 Jul 2026, 3:00 pm Frank Habicht <geier at geier.ne.tz> wrote:
> Hi,
>
> inline...
>
> On 7/18/2026 10:49 PM, Nia Petronella wrote:
> > Dear PDWG,
> >
> > I agree with Asamkele, Gugu, and Tshepo, and I remain opposed to this
> > proposal.
> >
> > Responding to objectors one by one does not resolve the common concern
> > they have raised. A collision between AS-SET labels is not a failure of
> > ASN or prefix uniqueness,
>
> It is a failure of AS-SET uniqueness.
> Which are not among the famous 3 INR that AfriNIC primarily deals with.
> But they are important objects in the IRR. Which AfriNIC operates. And
> thus AfriNIC should set the policies under which it operates the IRR.
>
> > and repeating that characterization does not
> > make it technically correct.
>
> Maybe my above statement is not a repetition, and could be technically
> correct?
>
> > The proposal still has not demonstrated measurable operational harm,
>
> Would it be better if someone would have added this to the proposal:
> "" MANRS documented the incident with AS-AMAZON back in 2022,
>
> https://manrs.org/2022/12/why-network-operators-should-use-hierarchical-as-sets/.
>
> At the time of writing Google's official source for their AS-SET is RADB
> as documented in their PeeringDB entry
> https://www.peeringdb.com/net/433, but AS-GOOGLE currently exists as an
> empty AS-SET in the RIPE DB
>
> https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=AS-GOOGLE&type=as-set.
>
> ""
>
> Would you then agree that the proposal demonstrated harm?
>
> Just because you didn't see it doesn't mean there was no harm.
>
>
> > why
> > voluntary hierarchical naming is insufficient,
>
> the author posted on this mailing list the number of collisions that exist.
>
> > or why mandatory registry
> > intervention is the least restrictive solution.
>
> This is where you can propose a less restrictive solution.
>
> > Adoption by other RIRs
> > is relevant, but institutional uniformity is not proof of technical
> > necessity.
>
> Harm that was documented is the proof of technical necessity.
>
> > A policy process should examine objections on their merits, not treat
> > repeated disagreement as something to be individually overcome.
>
> Thanks. Was the AI asked to produce a certain quantity of text, so that
> this blah had to be included?
>
> > The
> > registry should support accurate routing information without converting
> > every preferred convention into compulsory policy.
>
> Now, I have a question.
>
> If "the registry" (AfriNIC) gets this information:
>
> as-set: AS-GOOGLE
> tech-c: AS156-AFRINIC
> admin-c: AS156-AFRINIC
> mnt-by: google_kenya
> source: AFRINIC # Filtered
> descr: AS-GOOGLE
>
>
> and another registry (RADB) has this information:
>
> as-set: AS-GOOGLE
> descr: Google
> members: AS11344
> members: AS13949
> members: AS15169
> members: AS15276
> members: AS19425
> members: AS22577
> members: AS26910
> members: AS36040
> members: AS36384
> members: AS36492
> members: AS36561
> members: AS394725
> members: AS40873
> members: AS41264
> members: AS43515
> members: AS55023
> members: AS6432
> members: AS19527
> members: AS26684
> members: AS395973
> members: AS36039
> members: AS24424
> members: AS396982
> members: AS139070
> members: AS139190
> members: AS394699
> members: AS-GOOGLE-IT
> members: AS-MEEBO
> members: AS-METAWEB-2
> members: AS32381
> members: AS36383
> members: AS36411
> members: AS36520
> members: AS394089
> mnt-by: MAINT-AS15169
> changed: arturolev at google.com 20231030 #16:36:58Z
> source: RADB
> last-modified: 2023-11-13T16:19:21Z
>
> then what should the person or the software generating a prefix-filter do?
>
> Awaiting this answer.
>
> It's important. Because this is what this discussion is about. Any
> indication that the opponents have understood this will be welcome.
>
> Frank Habicht
>
>
> _______________________________________________
> 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/20260719/a7141280/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 69
************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260719/dcf8e756/attachment-0001.html>
More information about the RPD
mailing list