[db-wg] Source GRS vs RIPE

On Thu, 12 Jul 2018 at 12:50, Aftab Siddiqui <aftab.siddiqui at gmail.com> wrote:
> Thanks for the detailed response and it means if the source is not RIPE then it shouldn’t be considered as authentic data because the resource belongs to RIPE NCC.

That I am not certain about. Normally I would expect to at least find
an INETNUM object in the RIPE NCC database.

I can only say try contacting fx. support _at_ ripe.net for further
details about why the RIPE NCC database does not hold any inetnum
record for the prefix. When the (commercial) RADB database hold the
routes for it.

> As posted earlier the resource in question is 188.64.224.0/21 which doesn’t result anything from default source i.e RIPE.

I believe RIPE NCC Support Staff (support _at_ ripe.net) is better
suited to answer this question.
On Thu, 12 Jul 2018 at 12:50, Aftab Siddiqui <aftab.siddiqui at gmail.com> wrote:
>
> Hi Christoffer,
> Thanks for the detailed response and it means if the source is not RIPE then it shouldn’t be considered as authentic data because the resource belongs to RIPE NCC.
>
> As posted earlier the resource in question is 188.64.224.0/21 which doesn’t result anything from default source i.e RIPE.
> On Thu, 12 Jul 2018 at 6:20 pm, Christoffer Hansen <netravnen at gmail.com> wrote:
>>
>> On Thu, 12 Jul 2018 at 11:24, Aftab Siddiqui via db-wg <db-wg at ripe.net> wrote:
>> > I would like to understand the difference between these 2 results for the same prefix.
>> >
>> > Source: GRS
>> > https://apps.db.ripe.net/db-web-ui/#/query?bflag=true&source=GRS&searchtext=188.64.224.0%2F21#resultsSection
>>
>> ~ > whois --host whois.ripe.net -rB --resource 188.64.224.0/21 | grep
>> -ve '^[[:space:]]*$' | grep -ve '^[% ]' | grep -v 'remarks:'
>> route:          188.64.224.0/21
>> descr:          Twitter Route
>> origin:         AS13414
>> notify:         noc at twitter.com
>> mnt-by:         MAINT-AS13414
>> source:         RADB-GRS
>>
>> Note the "--resource" parameter being present.
>> Which will include results from other(!) databases apart from the RIPE
>> NCC database. In this case the RADB-GRS database.
>> The 'source:' also denote this fact.
>>
>> Nb: You can see http://www.irr.net/docs/list.html#RIPE which other RIR
>> databases the RIPE NCC mirrors.
>>
>> > Source: RIPE
>> > https://apps.db.ripe.net/db-web-ui/#/query?bflag&searchtext=188.64.224.0%2F21&source=RIPE#resultsSection
>>
>> ~ > whois -h whois.ripe.net -rB 188.64.224.0/21 | grep -ve
>> '^[[:space:]]*$' | grep -ve '^[% ]' | grep -v 'remarks:'
>> inetnum:        188.0.0.0 - 188.255.255.255
>> netname:        EU-ZZ-188
>> descr:          To determine the registration information for a more
>> descr:          specific range, please try a more specific query.
>> descr:          If you see this object as a result of a single IP query,
>> descr:          it means the IP address is currently in the free pool of
>> descr:          address space managed by the RIPE NCC.
>> country:        EU # Country is in fact world wide
>> admin-c:        IANA1-RIPE
>> tech-c:         IANA1-RIPE
>> status:         ALLOCATED UNSPECIFIED
>> mnt-by:         RIPE-NCC-HM-MNT
>> created:        2002-04-08T12:41:20Z
>> last-modified:  2015-09-23T13:18:27Z
>> source:         RIPE
>>
>> By default only results from the RIPE NCC database is included.