<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: ripe-81 work

  • From: Tony Bates < >
  • Date: Thu, 18 Mar 93 17:45:23 +0100
  • Cc:

Last week I mailed out some statistics about some conflicts between the RIPE
database and what we see in the European BGP routing tables. This is now
totally automated and a job runs once a day which produces both the
RIPE derived networks assigned to an AS and the router derived netwroks
assigned to an AS. The conflicts are then checked between the two pieces of 
information.  

All the information is available from the RIPE filestore at 
ftp.ripe.net in directory ripe/as

This contains three sub-directories:

     db               - AS information derived from RIPE database.
     router           - AS information derived from BGP routing table.
     conflicts        - Comparison of the information in the dbm and router
                        directories.

Here follows the README from each directory.

README  (ripe/as/db/README)                                  15/3/93
------
This directory contains information regarding Autonomous System information
derived from the RIPE database.

The files are as follows:-

status   -- Contains info of time the derivation was done.
as.list  -- Full list of networks and AS numbers

There is also a sub-directory "as-dir". This contains lists of networks
assigned to an AS. Each file is named as follows:-

        AS-<num> where num is the AS number itself.

There are also two special files.

        NONE - This contains networks in the database with a connectivity
               flag and no aut-sys tag.

        NONE-LOCAL - This contains networks  in the database with a
                     connectivity tag of LOCAL in the RIPE database.
                     These networks should not have have an aut-sys entry.


README  (ripe/as/router/README)                                  15/3/93
------
This directory contains information regarding Autonomous System information 
derived from a European routers BGP table.

The files are as follows:-

status   -- Contains info of router used and time the derivation was done.
as.list  -- Full list of networks and AS numbers
bogus    -- Any possible bogus network entries found.
conflict -- Any conflicts found. A network can only originate in one AS.

There is also a sub-directory "as-dir". This contains lists of networks
assigned to an AS (note -- This may contain conflicts). Each file is named 
as follows:-

        AS-<num> where num is the AS number itself.


README  (ripe/as/conflicts/README)                                  15/3/93
------
This directory contains some analysis of the RIPE and Router derived AS
information.

The files are as follows:-

 notin.db     -- European networks in the BGP routing tables and not in the
                 RIPE database.

 local.routed -- Networks being announced in the BGP routing tables and
                 flagged as LOCAL in the RIPE database.

 db-conf-bgp  -- Conflicts between the AS registered for a network in the 
                 RIPE database and what is being announced.


Please can everyone check these to see where simple updates can be made.
It is our intention to eliminate as many of these conflicts or inconsistencies
as possible. My idea behind this is the service providers and local registries
should be able to regularly pull this information to make sure things are 
up to date.

Please let me know if there are other useful peieces of information felt useful
to derive regularly.

--Tony.



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>