[DBWG] RIPE proposed changes to the routing registry
job at ntt.net
Fri Jun 8 11:23:36 UTC 2018
On Fri, Jun 08, 2018 at 03:06:48PM +0400, Madhvi Gokool wrote:
> *In regard to the checks that are conducted internally - we determine
> whether the org holding the prefix in the AFRINIC registry is also the
> holder of the ASN in another RIR registry. *
Why is this check done? With RPKI no such check exists either. RIPE
(soon), NTTCOM, RADB and others do not perform this check either. It
seems to me that this check adds no value and delays the process.
When an African company contracts NTT to originate a prefix on their
behalf and staticly route the prefix to their circuit - the ASN (2914)
and the prefix (the African customer) will not be the same organisation.
In such cases a route-object should still exist in the AFRINIC IRR
because that is the only IRR where a chain of trust can exist.
Can you elaborate on this validation and why it exists?
More information about the DBWG