This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Previous message (by thread): [routing-wg] RPKI Validator 3: disable fetching from certain repos?
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Thu Oct 11 15:15:48 CEST 2018
Dear colleagues, A new RIPE Policy proposal, 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now available for discussion. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-06 As per the RIPE Policy Development Process (PDP), the purpose of this four-week 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 Working Group Chairs, decides how to proceed with the proposal. We encourage you to review this proposal and send your comments to <routing-wg at ripe.net> before 9 November 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [routing-wg] RPKI Validator 3: disable fetching from certain repos?
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]