<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Paul,<div><br></div><div>Regarding AFPUB-2026-IPv4-001-DRAFT02. After the PPM and when I was re-reading your proposed amendments, I didn’t saw the need to change anything, because 1) all the CPM and operational decisions are always done “in accordance with adopted community policy”, 2) “final” is defined operationally by the staff. They decide when some IP blocks are actually returned or reclaimed or whatever. If we want to make that explicit, then the community should, for example, define a quarantine procedure step by step, but this is micro-management that only make sense if the existing procedure is not working and the staff don’t want to resolve it, which is not the case.<div><div><br></div><div>The problem we have is that is always in the border line what we can and cannot do in the LC. I think it is clear that a typo, grammar, etc., may be corrected. But changes which can bring different opinions or interpretations on the text change, not. In LACNIC, I proposed to resolve that by ensuring that there is not an interpretation change and the LC is restarted by sending a new version with only that change.</div><div><br></div><div><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 31 jul 2026, a las 22:54, Paul Hjul <hjul.paul@gmail.com> escribió:</div><br class="Apple-interchange-newline"><div><div dir="ltr">Dear Co-Chairs and Members ;)<br><br>I have participated on each of the matters for which last call has been called either on list or at the PPM.<br><br><br><div><b>Soft Landing, Recovered Space and Priority (AFPUB-2026-IPv4-001-DRAFT02) <br></b><div><i>Comment earlier presented</i>:<b> </b><a href="https://lists.afrinic.net/pipermail/rpd/2026/014924.html">https://lists.afrinic.net/pipermail/rpd/2026/014924.html</a> and <i>authors addressing </i>of same: <a href="https://lists.afrinic.net/pipermail/rpd/2026/014925.html">https://lists.afrinic.net/pipermail/rpd/2026/014925.html</a><b><br></b><div><br></div><div>I am of the view that this policy is a good stop gap and avoids falling victim "of perfection is the enemy of the good". I have two concerns, one of which takes the form of an objection. The objection is addressed by two minor amendments to the text. I believe the author is not certain that part of the amendment (adding the phrase "in accordance with adopted community policy") is permissible and regards it as a little superfluous and but the other amendment is satisfactory to the author (adding the term "final"). The concern pertains to the matter of "utilization". Naturally the utilization definition issue is broader than this policy and has both a "what should be in the CPM" and "what is the practice within AFRINIC followed by staff". There has been some movement on at least getting the applicable information on this point.</div><div><br></div><div>The phrase "in accordance with adopted community policy" may appear superfluous but it captures an important factor in what is an ugly issue which this policy touches on and which comes up in various manifestations throughout discussions on this list. The contention which I am advancing is that the role of the RDP and the CPM is to enable community policies which are binding AFRINIC to the extent that such policies do not impair or infringe on entitlements and rights of resource holders or users. </div><div><br></div><div><br></div><div><b>Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) </b><br><div><i>Comments on this policy</i>: <a href="https://lists.afrinic.net/pipermail/rpd/2026/015245.html">https://lists.afrinic.net/pipermail/rpd/2026/015245.html</a> & <a href="https://lists.afrinic.net/pipermail/rpd/2026/015255.html">https://lists.afrinic.net/pipermail/rpd/2026/015255.html</a></div><div><br></div><div>This policy draft has had a whirlwind of peculiar discourse. It is quite clear that a lot of concern touches onto the already mentioned undertone debate around capacity of community policy. It is very clear to me that <b>as written</b> the policy does not introduce any encroachment or risk of encroachment. It is also possible that the policy can be viewed as superfluous but the same reasoning in support of affording specificity as to the responsibility of AFRINIC to act only in accordance with adopted community policy in respect of recovery the same benefit in having the CPM including the proposed text in my view overrides the concern around whether the RPD mailing list is the correct discussion forum. I have noticed that the author has considered an amended text. What I am firmly of the view is that the as written - rather than as proposed to be "clarified" in the staff assessment is apt. A considerable amount of discussion around objections presuppose that the policy proposal is amended from the as written wording into the wording proposed by staff "for clarity".</div><div><br></div><div><br></div><div><b>Amendment of Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02). </b></div><div>I am supportive of this policy notwithstanding many of the implementation and monitoring concerns. I am of the view that the changes to the CPM that would be effected are beneficial.</div><div>I believe the "utilization" metric problem requires a different discussion and process. </div><div><br></div><div><br></div><div>Sincerely</div><div>Paul</div><div><br></div><div><br></div><div>Dear PDWG Members,<br><br><br>A gentle reminder that the deadline for Last Call phase to submit comments on the following policy proposals is 23:59 UTC today;<br><br><br>· Amendment of Utilisation in Soft Landing (AFPUB-2026-IPv4-002-DRAFT02) <a href="https://www.afrinic.net/afpub-2026-ipv4-002-draft02.html">https://www.afrinic.net/afpub-2026-ipv4-002-draft02.html</a><br><br>· Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br><br>· Soft Landing, Recovered Space and Priority (AFPUB-2026-IPv4-001-DRAFT02) <a href="https://www.afrinic.net/afpub-2026-ipv4-001-draft02.html">https://www.afrinic.net/afpub-2026-ipv4-001-draft02.html</a><br><br><br>Co-Chairs encourage you to share your comments and contributions within the remaining hours.<br><br><br>Best regards,<br><br>Haitham el Nakhal<br><br>PDWG Co-Chair</div></div></div></div></div>
_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<br></div></blockquote></div><br></div></div></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
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.<br>
<br>
</body></html>