Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Last Call - RPKI ROAs for Unallocated and Unassigned AFRINIC Address Space AFPUB-2019-GEN-006-DRAFT03.

Noah noah at
Sun Aug 1 14:30:21 UTC 2021

On Tue, Jul 27, 2021 at 7:38 AM Owen DeLong via RPD <rpd at> wrote:



> > On Jul 24, 2021, at 08:48 , Nishal Goburdhan <nishal at>

> wrote:

> >

> > On 22 Jul 2021, at 16:53, Owen DeLong via RPD wrote:

> >>

> >> This was not true. Because of the way they modified whois, multiple

> providers started rejecting LOAs as invalid and disconnecting customers.

> >

> > in my experience it takes quite a lot to (sometimes, even legitimately!)

> get an operator to disconnect a client that is paying them. so, i’m

> curious; what, specifically, was it about the change of a descriptor field

> in whois that caused your clients to start to be disconnected from their

> fee-inducing providers? in your answer, i’d like you to focus on the

> elements that network operators care about please - we don’t need any more

> arm-chair jurors, nor judges.


> I am neither an arm chair juror nor judge. I will state that an actual

> judge (in fact, the Chief Justice of the Supreme Court of Mauritius) issued

> an order asking AFRINIC to immediately correct the WHOIS entries and

> restore Cloud Innovation’s membership on July 13th. Clearly he felt that

> CI’s claims of harm and the merits of the case were sufficient to grant

> such relief.


> Upon the announcement, several providers proactively reached out to CI

> clients and told them that in light of the AFRINIC announcement, they felt

> that their LOAs for the space were no longer valid and that they were

> beginning termination procedures. I don’t know whether this was a passive

> response to the announcement by AFRINIC or whether AFRINIC reached out to

> upstreams to further undermine CI’s client base. Clearly, AFRINIC

If you were receiving IP Transit Services from AS37100, our policy is that
we will maintain provision of service whilst there is a verifiable IRR
object and/or a valid ROA.

The change that is described here would not have revoked your services with

In fact, most IPT operate in this manner fwiw.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the RPD mailing list