Dear SpeedIX members, Community-based filtering serves as the standard mechanism enabling route server participants at an Internet Exchange Point (IXP) to manage their routing policies. Since its inception in 2017, SpeedIX has supported this industry standard (https://speed-ix.net/bgp-community-filtering/). This filtering mechanism is crucial for enhancing participation with route servers, as members effectively delegate their routing policies to the IXP. Many members may find it uncomfortable or impractical to do so without these fundamental controls in place. The latest update to SpeedIX Manager introduces a new feature that empowers IXP members to configure route server filtering through a web-based user interface. This feature can be accessed in the SpeedIX portal under "Peering" -> "Route Server Filtering." This enhancement shifts the complexity of configuration from the member and their router to the route servers of the IXP. The fundamental filtering mechanism remains unchanged; however, the location of its execution has been modified: - The route server will now apply community tags to the member's routes upon ingress, rather than the member applying them on egress. - Conversely, the route server will filter the routes to be advertised to the member on egress, instead of the member managing this on ingress. We believe this solution should work for at least 90% of the cases. If your routing policies are more complex, it's a good idea to keep managing those on your own routers. Have a nice peering! Sincerely, SpeedIX NOC Team <noc(a)speed-ix.net> https://speed-ix.net/