I support this proposal as it addresses a "missing" lifecycle part for more reliable function of the RPKI ecosystem.
In our team, we are sometimes faced with the question of whether an unreachable or invalidly configured RPKI repository is indeed non-functional or just temporarily unavailable.
RIPE NCC may decide to provide a public status dashboard in this matter
This data may be also used in the LIR portal as well.
Best regards,
Fedor Vompe
Dear colleagues,
A new RIPE Policy Proposal, 2025-02, "Revocation of Persistently
Non-functional Delegated RPKI CAs" is now available for discussion.
This proposal suggests providing a mandate to the RIPE NCC to revoke
resource certificates associated with longtime non-functional CAs to
reduce Relying Party workloads.
You can find the full proposal at:
https://www.ripe.net/community/policies/proposals/2025-02/
As per the RIPE Policy Development Process (PDP), the purpose of the
Discussion Phase is to discuss the proposal and provide feedback to the
proposers.
At the end of the Discussion Phase, the proposers, with the agreement of
the WG Chairs, will decide how to proceed with the proposal.
The PDP document can be found at:
https://www.ripe.net/publications/docs/ripe-781
We encourage you to review this proposal and send your comments to
routing-wg@ripe.net before 4 July 2025.
Kind regards,
Angela Dall'Ara
Policy Officer
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/