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

On 14 Nov 2014, at 03:05, Job Snijders <job at instituut.net> wrote:

> On Fri, Nov 14, 2014 at 11:15:22AM +0000, Nick Hilliard wrote:
>> <snip>
>> 
>> Would this be feasible for the RIPE DB software?
> 

Hello,

It should be doable in a reasonable amount of time.

> If we implement such a RIPE-NONAUTH source, I'd expect a query
> structered like this:
> 
>    $ whois -h whois.ripe.net -- "-K -s RIPE -Troute 210.57.192.0/20"
> 
> to return "%ERROR:101: no entries found".
> 
> Maybe another way of phrasing the feature request: anything created due
> to authorisation against the RIPE-NCC-RPSL-MNT object will have "source:
> RIPE-NONAUTH" set, instead "source: RIPE”.?

Job, the query you have outlined is very similar to the queries that IRRToolset sends. Doing that will basically result in a much smaller filter list which some providers might not even notice (depending on filtering strategy). This eventually might result in a less “secure” (for a lack of better word) routing table.

If that is the desired outcome, why not. This is a clear example of the decision I am trying to put forward for the community in my last post to routing-wg.

> 
> Do we expect a different split file on the FTP site for RIPE-NONAUTH
> objects?

In my opinion, to be consistent, we should.

All the best,
Kaveh.


> Kind regards,
> 
> Job
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/db-wg/attachments/20141114/580dd740/attachment.sig>