[DBWG] RIPE proposed changes to the routing registry

[Job Snijders]

On Thu, May 17, 2018 at 08:25:24AM +0000, Job Snijders wrote:
> On Thu, May 17, 2018 at 10:13:22AM +0400, Daniel Shaw wrote:
> > In fact, my understanding is that is actually how the RIPE DB will
> > work in future.
> > 
> > This of course means that any resource holder could then create IRR
> > objects that state their resources are ok to originate from any ASN at
> > all. So the question is then for ASN holders: How does a given ASN
> > feel about route(6) objects existing with their ASN as origin that
> > they have nothing to do with or any control over?
> > 
> > This is an honest question, and not being the operator of a large ASN
> > I truly do not know the answer.

During the database working group session at RIPE 76 a comment was made
where the person appeared skeptical about Level3's ability to use
route-objects stored in the AFRINIC database. Upon further inspection
this appears to work correctly:

    job at vurt ~$ whois -h filtergen.level3.net AFRINIC::AS33764
    Prefix list for policy AFRINIC::AS33764 =
     AFRINIC::AS33764

    Pre-aggregation prefix counts (IPv4,IPv6): 0, 0
    196.2.3.0/24
    196.192.141.0/24
    196.216.2.0/23

If level3's filter generator did not have access to information stored
in the AFRINIC IRR, the returned list would've been empty.

Anyone having any issues with their transit provider should look for
help from that transit provider's respective NOC.

Kind regards,

Job