<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Dear PDWG,</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">I have a separate concern arising from the Impact Assessment.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">The proposal validates an AS-SET only when it is created, but the assessment presents the hierarchical name
as a continuing link to the responsible ASN operator. That link may not remain accurate throughout the object’s lifetime.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">For example, what happens if the leading ASN changes holder, is returned, is reassigned, or receives a new maintainer?
Does the former operator retain control of <code>AS12345:AS-CUSTOMERS</code>, does the new holder inherit it, or is the object suspended? The policy also permits existing objects to be edited, but does not say whether changes to maintainers or parent objects
trigger renewed authorisation checks.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Deletion and recreation create a similar problem. If a hierarchical name is deleted and later recreated, existing
filters or references may silently resolve to a different object using the same name. The proposal provides no tombstone, reservation, restoration period, or conflict-state mechanism.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">These are not questions about whether AS-SET membership is correct. They concern whether the proposal’s claimed
attribution remains technically true after creation.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Before adoption, the policy should define deterministic rules for changes of ASN control, parent-child delegation,
maintainer replacement, deletion, restoration, and name reuse. Otherwise, AFRINIC may enforce a hierarchical label while the label no longer identifies the operator actually controlling the object.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">A creation-time check is not enough for a claim of continuing authorisation.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">For that reason, I object to the proposal as presently written.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Regards,<br>
Tshepo</span></p>
</body>
</html>