afrinic rpki issue

2022-11-19 Thread Randy Bush
From: PacketVis Date: Sun, 20 Nov 2022 04:30:44 + Possible TA malfunction or incomplete VRP file: 73.95% of the ROAs disappeared from afrinic See more details about the event:

Re: ipv4/25s and above

2022-11-19 Thread Owen DeLong via NANOG
>> But see the crux above. If your RiR isnt frowning on such behavior then its >> poor strategy to implement it. > > I might have missed the part where RIR's tell me how to operate. Allow me to help: https://afrinic.net/ast/pdf/services/afrinic-rsa-en-201801.pdf afrinic-rsa-en-201801 PDF

Re: ipv4/25s and above

2022-11-19 Thread Rubens Kuhl
On Sat, Nov 19, 2022 at 5:13 PM Douglas Fischer wrote: > > I do not like mikrotik, but I need to say that RouterOS does support /31. > > All that you need to do, beyond set /31 at address for netmask, is check if > the other address is defined at the network address. Is /31 supported only in

Re: ipv4/25s and above

2022-11-19 Thread Bryan Fields
On 11/19/22 3:12 PM, Douglas Fischer wrote: > I do not like mikrotik, but I need to say that RouterOS does support /31. > > All that you need to do, beyond set /31 at address for netmask, is check if > the other address is defined at the network address. Can you show some docs on this? I gave a

Re: ipv4/25s and above

2022-11-19 Thread Douglas Fischer
I do not like mikrotik, but I need to say that RouterOS does support /31. All that you need to do, beyond set /31 at address for netmask, is check if the other address is defined at the network address. Em sáb., 19 de nov. de 2022 15:58, Denis Fondras escreveu: > Le Sat, Nov 19, 2022 at

Re: ipv4/25s and above

2022-11-19 Thread Denis Fondras
Le Sat, Nov 19, 2022 at 01:39:59PM -0500, Bryan Fields a écrit : > On 11/18/22 6:44 AM, Joe Maimon wrote: > >> We could, but many of our DIA customers have all manner of CPE's that > >> may or may not support this. Having unique designs per customer does > >> not scale well. > > its almost 2023.

Re: ipv4/25s and above

2022-11-19 Thread Bryan Fields
On 11/18/22 6:44 AM, Joe Maimon wrote: >> We could, but many of our DIA customers have all manner of CPE's that >> may or may not support this. Having unique designs per customer does >> not scale well. > its almost 2023. /31 support is easily mandatory. You should make it > mandatory.

ipv4/25s and above

2022-11-19 Thread Sylvain Baya
Dear NANOG-ers, Hope this email finds you in good health! Please see my comments below, inline... Thanks. Le samedi 19 novembre 2022, Owen DeLong via NANOG a écrit : > > > >> Either you have lots of fallow ground or very few customers. > > > > A bit of both. > > Regarding the former, perhaps

Re: Alternative Re: ipv4/25s and above

2022-11-19 Thread Mark Tinka
On 11/19/22 05:50, Abraham Y. Chen wrote: Dear Owen: 1) "... Africa ... They don’t really have a lot of alternatives. ...": Actually, there is, simple and in plain sight. Please have a look at the below IETF Draft: It's most amusing, to me, how Africa needs to be told how to be... Some

Re: ipv4/25s and above

2022-11-19 Thread Mark Tinka
On 11/18/22 13:44, Joe Maimon wrote: its almost 2023. /31 support is easily mandatory. You should make it mandatory. I don't make the gear. How many customer addressing designs does that total, 2? So that would be 1 more than you have already? Dont buy it. That's fine. Its 2023,