Dear colleagues, In response to previous requests from community members, the RIPE NCC has implemented support for creating and managing BGPsec Router Key Certificates (RFC 8209) through the RPKI API. Documentation on how to use the API is available at: https://github.com/RIPE-NCC/rpki-core/blob/main/Documentation/BGPSec%20API.m... In a nutshell, BGPsec allows holders of AS numbers to authorise a key for their router which can then be used to sign BGP updates. This allows BGPsec-aware routers to validate that the BGP path is unaltered (on BGPsec-enabled sessions). Please note that BGPsec is complementary to ROAs/ROV and ASPA. BGPsec focuses specifically on preventing spoofing of the path. It does not check the route origins, as ROAs/ROV do, or detect route leaks, as ASPA does. While BGPsec support in (hardware) routers is currently lagging, and there are challenges regarding incremental deployment and performance, we hope that enabling the support for BGPsec Router Key Certificates through RPKI API will help drive its development forward. Kind regards, Tim Bruijnzeels Principal Engineer RPKI RIPE NCC