<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Firstly, it's worth noting that AS47158 was registered to
ORG-IL649-RIPE, which was not a LIR.</p>
<p>Additionally, LIRs do not assign ASNs to end users whereas RIPE
does. NIR in certain regions is another story.</p>
<p>End user may enter into a sponsorship agreement with LIR to
receive ASN assignment, still directly from NCC.<br>
</p>
<p>It's important to note that ASNs and IP resources have quite
different assignment policies, so the involvement of IP brokers is
not relevant in this particular case.<br>
</p>
<div class="moz-cite-prefix">On 2023-03-21 2:33 p.m., George Toma
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADRs_WO=Rf+PnYsknhT3bA9jYyy4j+MCLp6xQJ2s2=rNwqy4Gg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Well that's for end users. The company in question seems to
be a Telecom operator.</div>
<div>The RIPE model is a very strange and confusing one, where
ISPs basically become LIRs and they themselves assign ASNs and
IPs, and there are 23000 LIRs in ARIN. Basically any ISP ,
webhosting company, datacenter or even a trading company can
become a LIR. </div>
<div><br>
</div>
<div>It's a very strange model which had just cost me 15 minutes
of my time to just dig into and get some basic understanding
of it. I would not put my hand in the fire that the OP is a
LIR or not, but they are an ISP so I would assume they are LIR
and as such can reassign the IPs,a nd if they are not LIR they
can become one. </div>
<div><br>
Anyway many of IP renting companies such as IPXO are
RIPE-based, and those who are ARIN or APNIC based also have
subnets from RIPE region. If RIPE was against subletting,
the whole market would not exist with RIPE subnets.</div>
<div><br>
</div>
<div>Regards</div>
<div>George</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 21, 2023 at
2:17 PM <<a href="mailto:ayang@august.tw"
moz-do-not-send="true" class="moz-txt-link-freetext">ayang@august.tw</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">RIPE NCC Requirements:
End User Assignment Agreement states:<br>
<br>
“End User may not sub-assign resources to third parties.”<br>
<br>
Best regards,<br>
August Yang<br>
<br>
On 2023-03-21 13:12, George Toma wrote:<br>
> I do not believe ASN sharing is illegal or prohibited,
it's not<br>
> prohibited in LACNIC and in APNIC policy I also could
not find<br>
> anything about ASN sharing, only<br>
> <br>
> APNIC policy states:<br>
> "2.3. Autonomous System (AS)An Autonomous System (AS)
is a connected<br>
> group of one or more IP prefixes run by one or more
network operators<br>
> under a single and clearly defined routing policy.<br>
> 2.3.1. Autonomous System Number (ASN)<br>
> An Autonomous System Number (ASN) is a unique two- or
four-byte number<br>
> associated with an AS. The ASN is used as an identifier
to allow the<br>
> AS to exchange dynamic routing information with other
Autonomous<br>
> Systems."<br>
> <br>
> Nothing prohibiting ASN sharing and 2.3 specifically
states "run by<br>
> one or more network operators... single routing policy"<br>
> <br>
> Regards<br>
> George<br>
> <br>
> On Tue, Mar 21, 2023 at 8:00 AM <<a
href="mailto:nanog-request@nanog.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">nanog-request@nanog.org</a>>
wrote:<br>
> <br>
>> Message: 19<br>
>> Date: Mon, 20 Mar 2023 16:24:09 -0400<br>
>> From: <a href="mailto:ayang@august.tw"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">ayang@august.tw</a><br>
>> To: Collider <<a
href="mailto:large.hadron.collider@gmx.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">large.hadron.collider@gmx.com</a>><br>
>> Cc: <a href="mailto:nanog@nanog.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">nanog@nanog.org</a><br>
>> Subject: Re: Spamhaus flags any IP announced by our
ASN as a<br>
>> criminal<br>
>> network<br>
>> Message-ID: <<a
href="mailto:5b7ed1b1fbff65dfc63d188c2e1f95af@august.tw"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">5b7ed1b1fbff65dfc63d188c2e1f95af@august.tw</a>><br>
>> Content-Type: text/plain; charset=UTF-8;
format=flowed<br>
>> <br>
>> Several Huize ASNs, e.g. AS47158 and AS141011, were
revoked due to<br>
>> RIR<br>
>> policy violations, which include prohibited sharing
of ASNs with<br>
>> third<br>
>> parties, IP hijacking, and malicious path
prepending.<br>
>> <br>
>> Given this history, it is not surprising that
Spamhaus would<br>
>> blacklist<br>
>> IP addresses associated with their ASN. In my
opinion, such action<br>
>> is<br>
>> well-justified.<br>
>> <br>
>> Best regards,<br>
>> August Yang<br>
</blockquote>
</div>
</div>
</blockquote>
<div class="moz-signature">-- <br>
Best regards<br>
August Yang
<img referrerpolicy="no-referrer-when-downgrade"
src="https://click.august.tw/matomo.php?idsite=3&rec=1"
style="border:0" alt=""></div>
</body>
</html>