[db-wg] source: field for non RIPE address space

Hi Nick, 

> So, could the RIPE NCC database people consider using a different source:
> value for non RIPE address space, so that it would be possible for irrdb
> users to easily filter out authoritative data from non authoritative data?

> E.g. 185.6.36.0/22 might continue to have "source: RIPE", but a prefix like "210.57.192.0/20" might have "source: RIPE-NONAUTH".

I think this might be a good way to get started on this issue.  

> Would this be feasible for the RIPE DB software?

I'll leave that to the RIPE DB guru's to answer. 

This might be a good way for transit providers who manually or automatically (scripted) check if a prefix AND a route Object was created as a result based on the RIPE-NONAUTH sources, resulting that the request to be flagged with big red flags.  And they should ask their customers directly for proper LOA's ( to get started...) 

> Interesting to note that Mega-Spred has started providing transit for
> Telstra Hong Kong, Sify in Chennai, iWay Africa in Cape Town and others:

> % peval AS201640 
> ({210.57.192.0/20, 210.57.0.0/19, 202.39.112.0/20, 119.227.224.0/19, 105.154.248.0/21, 41.198.224.0/20})

I've been looking at what AS201640 is currently doing and I noticed that they are currently not announcing anything .. At least I don't see it in our DFZ view.. And also RIPE STAT is reporting the same.  

So in short, this would have my support. 

Regards,
Erik Bais