[arin-ppml] RPKI for Reallocations

[Delong.com]

You fundamentally misunderstand the situation, then.

ROAs must be delegated according to the way networks are delegated. Lots of ISPs get addresses from upstream ISPs who get them from upstream ISPs who get them from ARIN.

In the case where IP addresses are delegated ARIN->ISP A->ISP B->ISP C, for RPKI to function, it has to be possible for ISP B to get a ROA from ISP A and for ISP C to
Get a ROA from ISP B.

ROAs have to be representative of the ORIGINATOR of the route in BGP or they are useless.

Owen


> On Jun 23, 2023, at 11:24, Fernando Frediani <fhfrediani at gmail.com> wrote:
> 
> I don't think this should be allowed to happen. ROAs are to be created by organizations who receive the allocation from the RIR as ultimatelly they remain responsible for that IP space. If they have allocated a block to a customer they should be the ones responsible for creating any ROAs they need for that IP space (in fact ideally they should create for the whole IP space anyway).
> 
> Fernando
> 
> On 23/06/2023 13:20, Richard Laager wrote:
>> It is my understanding that the downstream Org cannot create RPKI ROAs for Reallocated IP Networks. For example, 206.9.80.0/24 is reallocated to me (OrgID WIKSTR-1), but I cannot make a ROA for it. 
>> 
>> This is obviously suboptimal for adopting RPKI. 
>> 
>> Is this something that we could fix with Policy development, or do I need to bark up some other tree? 
>> 
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20230623/ba89ae32/attachment.htm>