<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Logan,</p>
<p class="isSelectedEnd"><span>The matter has been referred to the
respective internal stakeholders, and we will advise you shortly
on the way forward.</span></p>
<p class="isSelectedEnd"><span>Regards,</span></p>
<p><span>James</span></p>
<div class="moz-cite-prefix">On 03/10/2026 13:11, Loganaden
Velvindron wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOp4FwS=HXWG_b+sHp45=xQHncCfy1pejEF4sCBEM--rEbCEzg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>Dear James,
<div dir="auto"><br>
</div>
<div dir="auto">Can you please confirm the operational aspects
of the feature request ?</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Kind regards,</div>
<div dir="auto"><br>
</div>
<br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 29 Sept 2026,
22:51 Loganaden Velvindron, <<a
href="mailto:loganaden@gmail.com" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">loganaden@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On
Mon, 28 Sept 2026 at 12:50, James Chirwa <<a
href="mailto:james.chirwa@afrinic.net"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">james.chirwa@afrinic.net</a>>
wrote:<br>
><br>
> Hi Logan, all,<br>
><br>
> Thanks for raising this. I'll address it from two
perspectives: what is published today, and where it could
be improved.<br>
><br>
Dear James, thank you for your reply. It is much
appreciated.<br>
> Like the other RIRs, AFRINIC publishes the status of
all Internet number resources daily in the NRO extended
statistics format: <a
href="https://ftp.afrinic.net/stats/afrinic/"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://ftp.afrinic.net/stats/afrinic/</a><br>
><br>
> The file "delegated-afrinic-extended-latest" shows
the status of each resource as allocated, assigned,
available or reserved (definitions are in
README-EXTENDED.txt). Historical files are also kept, so
users can compare snapshots over time and identify status
changes between reporting periods, as SM's script
demonstrated.<br>
><br>
> Reclaimed resources are placed in the reserved state
while they go through the applicable quarantine and
cleanup processes, after which they are returned to the
available pool. It is important to clarify that a reserved
(quarantined) resource does not necessarily imply
contamination. More information on the resource lifecycle
status is available here: <a
href="https://afrinic.net/ip-resources-management"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://afrinic.net/ip-resources-management</a><br>
><br>
> Based on your explanation, I can notice one
limitation of the current data is that the reserved status
covers several scenarios. It includes resources in
quarantine after reclamation as well as resources reserved
for policy or operational reasons (for example, the
policy-reserved <a href="http://102.224.0.0/12"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">102.224.0.0/12</a> block).<br>
><br>
> While I take note the ARIN "cleared blocks" example
you shared, we would like to better understand your
particular requirements, could you clarify:<br>
><br>
> Which transitions are of most interest: delegated →
reserved, reserved → available, or both?<br>
<br>
Both.<br>
<br>
> Would it be important to publish distinct types of
reservation on this webpage (reclaimed, operational,
policy)?<br>
<br>
Yes. I believe that having this information readily
available would<br>
ease automation.<br>
<br>
> Would a structured feed (JSON or CSV) with the
prefix, previous status, new status and effective date
meet your requirements?<br>
<br>
Yes, it would be acceptable.<br>
<br>
> Any additional data points that would be useful.<br>
I believe that based on the following from the web page of
AFRINIC you cited:<br>
<br>
"How do I determine the different cases of reserved?<br>
From the extended statistics file, the reserved resources
cannot be<br>
differentiated.<br>
<br>
Policy reserved resources - These are registered on the
AFRINIC WHOIS<br>
database, for example, <a href="http://196.49.0.0/16"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">196.49.0.0/16</a>, <a
href="http://196.60.0.0/16"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">196.60.0.0/16</a>.<br>
<br>
Quarantine resources - These are currently kept as
internal records.<br>
<br>
Temporary Reservations - These are currently kept as
internal records.",<br>
<br>
This information is already available internally. It would
simply be a<br>
matter of making this information available<br>
externally to the public.<br>
<br>
<br>
><br>
> Your feedback on the questions above, will help us
evaluate the best way forward.<br>
><br>
> Next step<br>
> As pointed out by other forum members, this topic
concerns how resources are represented and published
rather than resource policy, so I am also exceptionally
cross-posting to the DBWG mailing list for the discussion
to proceed there.<br>
<br>
I would be happy to co-author a policy but I believe that
since this<br>
information is already available internally, it's simply
an<br>
operational matter<br>
to make it available externally.<br>
<br>
As a resource member previously said, this information
could be useful<br>
beyond cybersecurity groups.<br>
<br>
><br>
> Regards,<br>
><br>
> James<br>
><br>
><br>
><br>
> On 26/09/2026 11:19, Loganaden Velvindron wrote:<br>
><br>
> Hi All,<br>
><br>
> Recently, I was investigating a cyber security
incident involving IP addresses.<br>
><br>
> A recurring challenge is that even after these IP
ranges are returned<br>
> to AFRINIC for quarantine and cleanup, there is no
quick, centralized<br>
> way for cybersecurity threat intelligence providers
or law enforcement<br>
> agencies to track this status change. I fully
appreciate that the<br>
> AFRINIC team already handles a significant workload.<br>
><br>
> I would therefore kindly request AFRINIC members to
discuss whether<br>
> putting a dedicated page would be a good idea ? The
web page would be<br>
> for quarantined and cleaned up IP ranges so that
Cybersecurity Threat<br>
> Intelligence Providers and Law enforcement agencies
can easily parse<br>
> those to update their blocklists. CSV format is
acceptable but json<br>
> format would be nice to have especially with the rise
of automation.<br>
><br>
> Kind regards,<br>
> Loganaden Velvindron<br>
> (Speaking in my own capacity)<br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">RPD@afrinic.net</a><br>
> <a
href="https://lists.afrinic.net/mailman/listinfo/rpd"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
> --<br>
> James Chirwa<br>
> Head of Member Services<br>
> African Network Information Centre (AFRINIC) Limited<br>
> t: +230 403 51 00 | dir: +230 403 51 42<br>
> f: +230 466 6758<br>
> w: <a href="http://www.afrinic.net"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">www.afrinic.net</a> | tt:
@afrinic<br>
> SM: <a href="http://facebook.com/afrinic"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">facebook.com/afrinic</a> | <a
href="http://flickr.com/afrinic"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">flickr.com/afrinic</a> | <a
href="http://youtube.com/afrinicmedia"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">youtube.com/afrinicmedia</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
James Chirwa
Head of Member Services
African Network Information Centre (AFRINIC) Limited
t: +230 403 51 00 | dir: +230 403 51 42
f: +230 466 6758
w: <a class="moz-txt-link-abbreviated" href="http://www.afrinic.net">www.afrinic.net</a> | tt: @afrinic
SM: facebook.com/afrinic | flickr.com/afrinic | youtube.com/afrinicmedia</pre>
</body>
</html>