[anti-abuse-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List

Hi Petrit & Brian,  

Could you provide some insight on the status of this proposal ?  

I've seen not much (if at all...) discussion on the topic on the ML.  

I've seen that the discussion phase is already passed and we are more than a month further . . . and even for the AA-WG ML, with no replies, that is probably one of the first ... 

Personally, I'm not in favour of this policy as I don't like the NCC to start to injecting ROA's that are not allocated or assigned to members or end-users.  

I think it sets the wrong precedence for the community and it could open up for scope creep to abuse the system for other usage. 
So on that regards,  I wouldn't mind if the proposal would be dropped.  

Regards,
Erik Bais



On 31/10/2019, 15:40, "anti-abuse-wg on behalf of Petrit Hasani" <anti-abuse-wg-bounces at ripe.net on behalf of phasani at ripe.net> 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 in the Routing Working Group
    
    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
    
    This proposed policy may be of interest to the Anti-Abuse working group as well.
    
    Therefore, 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