[rpd] [Last Call] Draft Policy Proposal - Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)

[Hendrik Visage]

Dear Daniel,

Thank you for the considered note, and for recognising the rationale on 
squatting and name overlaps as justifiable.

One clarification on process: this proposal is DRAFT02 at Last Call, 
meaning the PDP discussion phases your message calls for have already 
run their course — Last Call is their conclusion. The earlier rounds 
are in the list archive https://lists.afrinic.net/pipermail/rpd/ should 
they be useful - Reference the first draft call on 
https://lists.afrinic.net/pipermail/rpd/2026/014746.html

You write that you object "subject to alternative and more acceptable 
rationale." Could you say what specific rationale would move you to 
acceptance? Happy to address it directly.
Regards,
Hendrik

---
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 20 Jul 2026, at 11:08, Taye Medoye wrote:

> Whereas the Organization’s guideline on Policy Scope & Exclusions 
> permits
> any desired alteration or amendment to an existing policy framework, 
> it is
> required that such an exercise would require critical deliberations 
> and
> discussion to ensure a convincing and realistic position for the 
> proposed
> policy change or amendment to stand the test of time. This view also 
> aligns
> with the policy statement which guarantees *that Number Resource 
> management
> policies are developed through an open Policy Development Process 
> (PDP).*
>
> In regard to the draft Policy proposal on bordering on the above 
> captioned
> subject-matter, projected for discussions on the Forum, l have taken 
> note
> of the justifiable rationale which forbids the unauthorized creation 
> of
> names that could lead to either a flat or arbitrary name, and its
> consequences of potential squatting or accidental overlaps; and the 
> fact
> that the requirement currently applies strictly to AS-SET objects to 
> the
> exclusion of other IRR objects.
>
> I have equally taken note that the AFPUB-2026-ASN-001-DRAFT02 requires
> newly created AS-SETs to use hierarchical naming to avoid name 
> collisions
> and improve route filtering, the fact remains that any alteration or
> amendment or new creation to existing policy framework would need to 
> be
> subjected to extensive discussions as is the guideline on this forum.
>
> Therefore, l hereby object to a creation of names as is being proposed
> subject to alternative and more acceptable rationale that necessitates
> acceptance of the proposal.
> *Daniel Taye Medoye*

> _______________________________________________
> 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/6a473a32/attachment.html>