I can also help in this endeavor if required, but I think the /20 should be a bit split into two parts (2 x /21) for example, just to be more specific (in getting the point across). :-)
On 16 Jul 2019, at 19:11, Adam Korab ak@mid.net wrote:
On Jul 16, 2019, at 11:00 AM, Job Snijders job@ntt.net wrote:
To completely cover the 44net block from a BGP perspective, in addition to the existing 44.0.0.0/9 and 44.128.0.0/10 announcement, 44.192.0.0/10 should also be announced (and nullrouted) from some vantage point.
I'm happy to do so if the community accepts my help in this regard. I have facilities to announce the prefix and ignore any traffic received for it.
If this is decided to be a good idea, I can help too - I also have facilities and and submit the routes as a customer route to 3356 and 174 (and 2914 but I expect Job has this well covered <g>) which might help from a “customer routes” vs. “peer routes” perspective.
Adam K0RAB BGP Enthusiast ;-)
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net