Hi Cynthia,

Thanks for you email.

We have investigated, of 1.7M lines in the aut-num split file, the last tag 
appears after 1.3M lines. This is because not all aut-num objects contain tags.
I confirm that split files are well formed and no tags are missing.

There are currently 22997 out of 36481 autumn objects in split file for which 
tag information is available.
Also tagging information is available for roughly 63% of ‘ASSIGNED' autumn 
objects.

We released the tag beta feature  in 2013 but stopped automatically updating 
the tags some time later. 
So all the tags that are present in split files are automatically generated 
during that time period and objects created/updated after that have the tags 
information missing in split files.

We need to ask the community whether we resume the tagging of objects or remove 
the functionality all together.

Is tagging information is useful for you? We can put forward a case to the 
community for resuming this functionality.

Regards,
Mahesh
RIPE NCC

> On 17 Dec 2020, at 09:27, Edward Shryane via db-wg <[email protected]> wrote:
> 
> Hi Cynthia,
> 
> The DB team will investigate further and let you know.
> 
> Regards
> Ed Shryane
> RIPE NCC
> 
> 
>> On 17 Dec 2020, at 03:49, Cynthia Revström via db-wg <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi DB-WG,
>> 
>> I just noticed that the (at the time of writing, serial 49363913) latest 
>> aut-num split db file (possibly elsewhere too) sort of just seems to break 
>> at some point.
>> 
>> The lines like below simply stop appearing:
>> 
>> % Tags relating to 'AS3333'
>> % RIPE-REGISTRY-RESOURCE
>> 
>> Here's a section where you can see it happening: 
>> https://gist.githubusercontent.com/bitcynth/d81688c6b7587e0179d55b8324535ff4/raw/57fcf2829967c0a9c1039180b2fd3e2a2cbb7e09/ripedb.txt
>>  
>> <https://gist.githubusercontent.com/bitcynth/d81688c6b7587e0179d55b8324535ff4/raw/57fcf2829967c0a9c1039180b2fd3e2a2cbb7e09/ripedb.txt>
>> 
>> Any clue why this is occurring? or is it just a bug?
>> 
>> - Cynthia
> 

Reply via email to