> On May 22, 2019, at 7:28 AM, Marco Schmidt <[email protected]> wrote:
>
> Dear colleagues,
>
> A new version of 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.
>
> The proposal has been updated following the last round of discussion and is
> now at version v2.0. Some of the differences from version v1.0 include:
> - Added reference to RFC 6811
> - Clarification for Legacy Internet Resource Holders
>
>
> 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
> <[email protected]> before 20 June 2019.
I support this proposal. We (Akamai) have invested considerable time in the
past month to clean up our RIPE-NONAUTH objects (all the IPv4 ones are now
gone).
(IPv6 ones still need some cleanup, I should go check on the process here.. my
goal was to have them all gone by RIPE78 but that did not happen).
- Jared
