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

Hi,

On Thu, Oct 31, 2019 at 07:10:02PM +0000, Job Snijders wrote:
> 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.

This was my first thought as well, but then I discovered this IPv6 thing :)

> 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.

It does stop people from announcing unassigned space and spam from it
(because the announcement would be "invalid" and no longer "unknown").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/routing-wg/attachments/20191031/124bf2af/attachment.sig>