[routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)

Dear collegues,

*chair hat on* 

    I discussed with my co-chair Paul that it would be best if he
    handles judging the consensus on the 2019-08 policy proposal later
    on, this allows me to freely share my views in the process!

*chair hat off*

I question the benefits of this policy proposal, but am willing to be
convinced. There are a few questions that come to mind about whether
this mechanism is productive.

1/ What is the ROI? I think there is only a few prefixes in the
default-free zone that are managed by RIPE NCC, but not assigned or
allocated by RIPE NCC. So putting this machinery in place might not have
that much benefit, while the cost of 'getting it wrong' could be
substantial.

2/ Have the policy proposers considered offering this functionality
through a separate RPKI TAL rather than the current main RIPE NCC RPKI
TAL? This way folks would explicitly opt-in to obtain this data feed in
an automated fashion.

3/ Once the resource is assigned, the resource holder can create a ROA.
In the lifecycle of a resource it isn't clear to me what the benefit is
to have a ROA covering it when it is not yet assigned/allocated.

Thanks!

Kind regards,

Job

On Thu, Oct 31, 2019 at 03:28:59PM +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.
> 
> You can find the full proposal at:
> 
> https://www.ripe.net/participate/policies/proposals/2019-08
> 
> 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 proposer.
> 
> At the end of the Discussion Phase, the proposer, with the agreement of
> the WG Chairs, will decide how to proceed with the proposal.
> 
> We encourage you to review this proposal and send your comments to
> <routing-wg at ripe.net> before 29 November 2019.
> 
> Kind regards,
> 
> --
> Petrit Hasani
> Policy Officer
> RIPE NCC
> 
> 
> 
> 
>