Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Dave Taht
On Thu, Jul 6, 2023 at 3:26 PM William Herrin wrote: > > On Thu, Jul 6, 2023 at 1:43 PM John Curran wrote: > > You are correct, insomuch if one intends to alter answers about the > > purported history > > of an address block from what was said the first time, we won’t simply > > disregard the

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread William Herrin
On Thu, Jul 6, 2023 at 1:43 PM John Curran wrote: > You are correct, insomuch if one intends to alter answers about the purported > history > of an address block from what was said the first time, we won’t simply > disregard the > previously supplied story. With due respect John, any given set

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread John Curran
> On Jul 6, 2023, at 3:03 PM, William Herrin wrote: > > On Thu, Jul 6, 2023 at 11:15 AM Tina Morris wrote: >> ARIN is actually staffed by helpful people that can answer many of these >> questions. Call RSD +1.703.227.0660 > > They absolutely are great people, BUT, and this is true of every

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread William Herrin
On Thu, Jul 6, 2023 at 11:15 AM Tina Morris wrote: > ARIN is actually staffed by helpful people that can answer many of these > questions. Call RSD +1.703.227.0660 They absolutely are great people, BUT, and this is true of every regulatory body, you talk to them very carefully before you have

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Tina Morris
ARIN is actually staffed by helpful people that can answer many of these questions. Call RSD +1.703.227.0660 <+1-703-227-0660> On Thu, Jul 6, 2023 at 10:19 AM Dave Taht wrote: > thank you for your research into this on our behalf and the steer to > the right things. > > Yes, these two ip

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Dave Taht
thank you for your research into this on our behalf and the steer to the right things. Yes, these two ip address ranges are erics, and if anything he´s more allergic to paperwork than I am. On Thu, Jul 6, 2023 at 11:03 AM William Herrin wrote: > > On Thu, Jul 6, 2023 at 8:03 AM Dave Taht

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread William Herrin
On Thu, Jul 6, 2023 at 7:29 AM Dave Taht wrote: > Anyway, LibreQos would really like to obtain a BGP AS number from some > RIR (or is there an unused BGP AS transfer market?) The other part of your question was AS numbers. From your starting point, this is easier. You'll need contracts with two

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread William Herrin
On Thu, Jul 6, 2023 at 8:03 AM Dave Taht wrote: > https://bgpview.io/prefix/198.177.242.0/24 This is registered to Thyrsus Enterprises via ARIN, managed by an Eric Raymond of Pennsylvania. Refer to https://search.arin.net/rdap/?query=198.177.242.0 If your friend happens to be Eric Raymond, his

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Dave Taht
Fixing the ausnog cc... more below. On Thu, Jul 6, 2023 at 8:46 AM Bill Woodcock wrote: > > The ASN really isn’t a big deal. There’s no scarcity of them, you can get a > 16-bit one by asking. Heh. Trying to reaquire my old 16 bit AS number is merely a matter of vanity... just navigating

Re: Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Bill Woodcock
The ASN really isn’t a big deal. There’s no scarcity of them, you can get a 16-bit one by asking. The legacy IPv4 space, well, if there’s a clear chain of custody to the current holder, and the current holder is responsive, they can use it or transfer it. But also, IPv4 space isn’t scarce…

Picking a RIR/obtaining an AS/ressurrecting a legacy space

2023-07-06 Thread Dave Taht
I have an old friend still holding onto some legacy IP space that he has not used in 30 years. The origin goes back to the early 90s, and originally through ARIN. In the relevant databases it is a /23, but actually a /22 - but the top 2 addresses are not registered or announced anywhere I can