Send ARIN-consult mailing list submissions to
arin-consult@arin.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
arin-consult-requ...@arin.net
You can reach the person managing the list at
arin-consult-ow...@arin.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."
Today's Topics:
1. Question/Suggestion on ASN registration (LayerBridge Internal)
2. Re: Question/Suggestion on ASN registration (William Herrin)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 Feb 2024 15:10:29 +0200
From: LayerBridge Internal <inter...@layerbridge.com>
To: "arin-consult@arin.net" <arin-consult@arin.net>
Subject: [ARIN-consult] Question/Suggestion on ASN registration
Message-ID: <8868a30e-34e0-4c21-9384-a83348323...@layerbridge.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hello there,
Hope I sent this mail correctly.. I don't know if I should do anything
before proposing things here... but I'll get straight to the point.
I was wondering if ARIN (and its members) would consider benefical a
different approach towards AS numbers... somewhat similar to how RIPE
works. More specifically I think would be a better way for LIR/ISP to be
able to register AS numbers on behalf of it's customers.
For example, in our situation, we are on a "X-Small" plan; having up to
63 ASNs included in our plan scheme. Almost all companies would agree
that 63 ASNs for a single entity is somehow too much. Most of us really
use 1-5 ASNs at most.
Having the possibility to reallocate ASNs in the way we can reallocate
unused IP space to end-users, would help us somehow to compensate the
yearly fee we pay for membership, by charging a small amount on the
End-User for the object maintenance.
Would that be something @ARIN would consider allowing LIRs to do?
Thank you,
Andrei.
--
Logo <https://www.layerbridge.com>
LayerBridge
*Andrei Cojan* | Co-Founder & Administrator
email: and...@layerbridge.com
BGP Info: AS3280 <https://bgp.he.net/AS3280>
For Europe:
*LayerBridge SRL*
Poligrafiei Blvd., No. 75, WhiteGate Building
1st District, Bucharest, Romania
For US & Non-EU:
*LayerBridge LLC*
8 The Green, STE R, Dover, Delaware 19901
United States
Facebook icon <https://www.facebook.com/layerbridge>
This message and any attachment are confidential and is protected from
disclosure. If you are not the intended recipient, please email the
sender and delete this message and any attachment from your system. This
correspondence and any and all documents attached to it shall not be
qualified in each case as a contract offer unless LayerBridge SRL. has
expressly agreed on the contrary.
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.arin.net/pipermail/arin-consult/attachments/20240223/32e19154/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nqNr9Mk0NbnUZqeB.png
Type: image/png
Size: 9541 bytes
Desc: not available
URL:
<https://lists.arin.net/pipermail/arin-consult/attachments/20240223/32e19154/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fnjj0j5hfCQjPjb4.png
Type: image/png
Size: 1306 bytes
Desc: not available
URL:
<https://lists.arin.net/pipermail/arin-consult/attachments/20240223/32e19154/attachment-0003.png>
------------------------------
Message: 2
Date: Fri, 23 Feb 2024 06:26:27 -0800
From: William Herrin <b...@herrin.us>
To: LayerBridge Internal <inter...@layerbridge.com>
Cc: "arin-consult@arin.net" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Question/Suggestion on ASN registration
Message-ID:
<CAP-guGXbFGuk10w7Bx_MfCq7wAKwFv=s1wpq4ra455zb2fz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Fri, Feb 23, 2024 at 5:10?AM LayerBridge Internal via ARIN-consult
<arin-consult@arin.net> wrote:
> Almost all companies would agree that 63 ASNs for a single entity is somehow
> too much. Most of us really use 1-5 ASNs at most.
Hi Andrei,
It depends how you're using them. If you're anycasting a prefix from a
lot of locations and you do so using different AS numbers, you can
then access routing data from RIS and Routeviews and find out which
announcement reached where without needing active probes. 32-bit AS
numbers aren't especially scarce and the RIB and FIB entries don't
take any more space when you announce with multiple numbers, so
there's no real downside to doing this.
When a separate organization needs AS numbers, I'd personally rather
see them get those numbers directly from ARIN rather than from their
ISP.
Regards,
Bill Herrin
--
William Herrin
b...@herrin.us
https://bill.herrin.us/
------------------------------
Subject: Digest Footer
_______________________________________________
ARIN-consult mailing list
ARIN-consult@arin.net
https://lists.arin.net/mailman/listinfo/arin-consult
------------------------------
End of ARIN-consult Digest, Vol 104, Issue 10
*********************************************
