[routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Previous message (by thread): [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ben Maddison
benm at workonline.africa
Thu Oct 31 17:08:05 CET 2019
Hi all, On Thu, 2019-10-31 at 15:28 +0100, Petrit Hasani wrote: > Dear colleagues, > > A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and > Unassigned RIPE NCC Address Space" > is now available for discussion. > > This proposal aims to instructs the RIPE NCC to create ROAs with > origin AS0 for all unallocated and unassigned address space under its > control. > I support this proposal. We are one of the "not many operators" that try to maintain bogon filters at our eBGP edge, and we have also been rejecting rpki-ov invalids since earlier this year. This policy would therefore simplify our operations considerably. Cheers, Ben Maddison
- Previous message (by thread): [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]