Hi all, Sorry for the delay, I was on vacation,
AS3333 was/is still announcing all the prefixes to the Falcon RS. They were in the RIB of the RS. The prefixes that did not have valid route objects were then either filtered or tagged with communities by the RS, depending on the other RS participants session configs. In addition, the number of users of the Falcon route servers is much less than the legacy route servers - today, the Falcon RS3 has ~160 established v4 BGP peers, compared to ~700 on the legacy RS1. So, a combination of the new RS filtering the prefixes that do not have route objects, and the prefixes (even the IRR-valid ones) being advertised to a much smaller set of peers, caused the drop in reachibility. Cheers, Colin On 11/07/2017 17:12, Stephen D. Strowes wrote: > Colin has most insight here, since he did the legwork to spot precisely > what changed on those dates. > > S. > > > > On 11/07/2017 04:33, Randy Bush wrote: >> as i said in the comment, >> >> Nice work! When AS3333 stopped propagating longer prefixes due to >> switch to AMSIX Falcon RS, was it the RS, lack of RPKI, ...? >> >> randy >> > > -- Colin Petrie Systems Engineer RIPE NCC
