<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Ronald,<br>
<br>
As of November 2019 the RIPE NCC only provides /24 IPv4
allocations to LIRs that have not previously received an IPv4
allocation from us. As Elvis clarified, the examples you listed
are the results of resource transfers.<br>
<br>
The “netname:” attribute of an INETNUM object in the RIPE Database
indicates whether an IPv4 allocation was received directly from
the RIPE NCC or via a transfer. It includes the date on which that
range was provided by the RIPE NCC, also for smaller ranges that
are part of a previously bigger range. If the date in the
“netname:” and the date on which the object was created differ,
you can deduce that the range concerned was not allocated directly
by the RIPE NCC.<br>
<br>
I hope this helps answer your question.<br>
<br>
Kind regards,<br>
Marco Schmidt<br>
RIPE NCC<br>
</p>
<div class="moz-cite-prefix">On 15/08/2022 10:45, Elvis Daniel Velea
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJZHz-qjabVc26nBh=ZkzbO3Ocp3WRL7ytLNB_Xc0YTcwOjt+g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">hi,</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Aug 15, 2022 at
01:41 Bogdan Rotariu <<a href="mailto:bogdan@rotariu.ro"
moz-do-not-send="true" class="moz-txt-link-freetext">bogdan@rotariu.ro</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="auto">
<div dir="ltr">
<div dir="ltr"><br>
<div dir="ltr">
<blockquote type="cite">On Aug 15, 2022, at 11:19,
Ronald F. Guilmette <<a
href="mailto:rfg@tristatelogic.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">rfg@tristatelogic.com</a>>
wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr"><span>In message <<a
href="mailto:301e0ef8-ed15-67d3-d390-7bea8571c7cb@ripe.net"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">301e0ef8-ed15-67d3-d390-7bea8571c7cb@ripe.net</a>>,
</span><br>
</div>
</blockquote>
</div>
</div>
</div>
<div dir="auto">
<div dir="ltr">
<div dir="ltr">
<blockquote type="cite">
<div dir="ltr"><span>Marco Schmidt <<a
href="mailto:mschmidt@ripe.net"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mschmidt@ripe.net</a>>
wrote:</span><br>
<span></span><br>
<blockquote type="cite"><span>On 15/08/2022 09:16,
Gert Doering wrote:</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Hi,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>On Mon, Aug 15,
2022 at 12:10:49AM -0700, Ronald F.
Guilmette wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>What is the
maximum size for current new IPv4
allocations in the RIPE</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>region?</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>/24 "if there is
something to distribute at all"</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Just to confirm what
Gert said.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>For more information
please feel free to check our website about
IPv4</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="https://www.ripe.net/manage-ips-and-asns/ipv4"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ripe.net/manage-ips-and-asns/ipv4</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>as well the
underlying RIPE policy which was published in
November 2019</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="https://www.ripe.net/publications/docs/ripe-733#51"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ripe.net/publications/docs/ripe-733#51</a></span><br>
</blockquote>
<span></span><br>
<span>Thank you for the confirmation.
Unfortunately, I remain rather mystified</span><br>
<span>by how the following IPv4 blocks, and the
current RIPE WHOIS records that</span><br>
<span>pertain to them, comport with what you and
Gert have just now told me.</span><br>
<span>Perhaps there is something that I am missing
(?)</span><br>
<span></span><br>
<span>ORG-AS976-RIPE:</span><br>
<span></span><br>
<span><a href="http://31.44.32.0/20"
target="_blank" moz-do-not-send="true">31.44.32.0/20</a>
created: 2022-06-24T06:46:34Z</span><br>
<span><a href="http://46.21.16.0/21"
target="_blank" moz-do-not-send="true">46.21.16.0/21</a>
created: 2022-06-24T06:46:34Z</span><br>
<span><a href="http://46.21.28.0/22"
target="_blank" moz-do-not-send="true">46.21.28.0/22</a>
created: 2022-06-24T06:46:34Z</span><br>
<span><a href="http://77.220.64.0/19"
target="_blank" moz-do-not-send="true">77.220.64.0/19</a>
created: 2022-06-23T09:56:04Z</span><br>
<span><a href="http://185.155.176.0/22"
target="_blank" moz-do-not-send="true">185.155.176.0/22</a>
created: 2022-06-23T09:56:04Z</span><br>
<span><a href="http://185.155.184.0/22"
target="_blank" moz-do-not-send="true">185.155.184.0/22</a>
created: 2022-06-24T06:46:34Z</span><br>
<span><a href="http://193.221.216.0/23"
target="_blank" moz-do-not-send="true">193.221.216.0/23</a>
created: 2022-06-24T06:46:33Z</span><br>
<span><a href="http://193.222.104.0/23"
target="_blank" moz-do-not-send="true">193.222.104.0/23</a>
created: 2022-06-24T06:46:33Z</span><br>
<span></span><br>
<span></span><br>
<span>Regards,</span><br>
<span>rfg</span><br>
<span></span><br>
<span></span><br>
<span>P.S. I would still be concerned, although
perhaps a bit less concerned, if</span><br>
<span>this organisation had not elected to place a
fradulent and non-existant</span><br>
<span>comnpany name into its public WHOIS
organisation: record. I would however</span><br>
<span>still remain befuddled by how this
organisation managed to be assigned</span><br>
<span>some 72 times as much IPv4 address space as
anybody else could get, all</span><br>
<span>apparently less than 2 months ago.</span><br>
<span></span><br>
<span>But there must be a reasoable explanation, I
suppose.</span></div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto"><span
style="border-color:rgb(0,0,0);color:rgb(0,0,0)">when the
RIPE NCC processes a transfer and needs to split a block,
all the smaller blocks that are transferred from the
original large block will have the date of the transfer as
creation date</span><br>
</div>
<div dir="auto"><span
style="border-color:rgb(0,0,0);color:rgb(0,0,0)"><br>
</span></div>
<div dir="auto"><span
style="border-color:rgb(0,0,0);color:rgb(0,0,0)">/elvis</span></div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="auto">
<div dir="ltr">
<div dir="ltr">
<blockquote type="cite">
<div dir="ltr"><span></span><br>
</div>
</blockquote>
</div>
</div>
</div>
<div dir="auto">
<div dir="ltr">
<div dir="ltr"><br>
<div>There is, those are transfers, check them here <a
href="https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-statistics/within-ripe-ncc-service-region/ipv4-transfer-statistics"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-statistics/within-ripe-ncc-service-region/ipv4-transfer-statistics</a></div>
</div>
</div>
</div>
-- <br>
<br>
To unsubscribe from this mailing list, get a password
reminder, or change your subscription options, please visit:
<a
href="https://mailman.ripe.net/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://mailman.ripe.net/</a><br>
</blockquote>
</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">This message was sent from a
mobile device. Some typos may be possible. </div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>