ASPA support added to the RIPE NCC RPKI Dashboard
Dear colleagues, We enabled ASPA support in the RIPE NCC RPKI Dashboard on 26 November. An ASPA object is a signed RPKI Object that allows the holder of an AS number to authorise one or more other AS numbers to appear as their legitimate upstream providers in BGP. ASPA validation can help to prevent BGP route leaks, and to a degree improves BGP path security. While the IETF standards have not yet reached RFC status, the discussions have been resolved. We therefore consider ASPA signing ready for use. But, before you start we recommend that you read the documentation here: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/aspa/ Or watch the RIPE 91 presentation on ASPA in the RPKI Dashboard: https://ripe91.ripe.net/programme/meeting-plan/sessions/30/VZNKWV/ Please let us know if you have any questions or comments. Kind regards, Tim Bruijnzeels Principal Engineer RPKI RIPE NCC
Dear Tim and the RIPE NCC team, Thank you for this important update and for enabling ASPA support in the RPKI Dashboard! I appreciate a proactive deployment of ASPA signing capabilities ahead of final RFC standardization. The timing, along with the presentation from RIPE 91, demonstrates RIPE NCC's commitment to timely and responsible implementation. I look forward to exploring ASPA implementation and will reach out if I have any questions. Best regards, Fedor Vompe On Tue, Dec 2, 2025 at 12:03 PM Tim Bruijnzeels <tbruijnzeels@ripe.net> wrote:
Dear colleagues,
We enabled ASPA support in the RIPE NCC RPKI Dashboard on 26 November.
An ASPA object is a signed RPKI Object that allows the holder of an AS number to authorise one or more other AS numbers to appear as their legitimate upstream providers in BGP. ASPA validation can help to prevent BGP route leaks, and to a degree improves BGP path security.
While the IETF standards have not yet reached RFC status, the discussions have been resolved. We therefore consider ASPA signing ready for use. But, before you start we recommend that you read the documentation here: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/aspa/
Or watch the RIPE 91 presentation on ASPA in the RPKI Dashboard: https://ripe91.ripe.net/programme/meeting-plan/sessions/30/VZNKWV/
Please let us know if you have any questions or comments.
Kind regards,
Tim Bruijnzeels Principal Engineer RPKI RIPE NCC
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
+1 Best, Libin -----原始邮件----- 发件人:"Fedor Vompe" <routing@fedor.dev> 发送时间:2025-12-03 16:10:27 (星期三) 收件人: "Tim Bruijnzeels" <tbruijnzeels@ripe.net> 抄送: routing-wg@ripe.net 主题: [routing-wg] Re: ASPA support added to the RIPE NCC RPKI Dashboard Dear Tim and the RIPE NCC team, Thank you for this important update and for enabling ASPA support in the RPKI Dashboard! I appreciate a proactive deployment of ASPA signing capabilities ahead of final RFC standardization. The timing, along with the presentation from RIPE 91, demonstrates RIPE NCC's commitment to timely and responsible implementation. I look forward to exploring ASPA implementation and will reach out if I have any questions. Best regards, Fedor Vompe On Tue, Dec 2, 2025 at 12:03 PM Tim Bruijnzeels <tbruijnzeels@ripe.net> wrote: Dear colleagues, We enabled ASPA support in the RIPE NCC RPKI Dashboard on 26 November. An ASPA object is a signed RPKI Object that allows the holder of an AS number to authorise one or more other AS numbers to appear as their legitimate upstream providers in BGP. ASPA validation can help to prevent BGP route leaks, and to a degree improves BGP path security. While the IETF standards have not yet reached RFC status, the discussions have been resolved. We therefore consider ASPA signing ready for use. But, before you start we recommend that you read the documentation here: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/aspa/ Or watch the RIPE 91 presentation on ASPA in the RPKI Dashboard: https://ripe91.ripe.net/programme/meeting-plan/sessions/30/VZNKWV/ Please let us know if you have any questions or comments. Kind regards, Tim Bruijnzeels Principal Engineer RPKI RIPE NCC ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
participants (3)
-
Fedor Vompe -
Libin Liu -
Tim Bruijnzeels