This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Route Polict Verification
- Previous message (by thread): [db-wg] Route Polict Verification
- Next message (by thread): [db-wg] Route Polict Verification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Wed Oct 16 18:05:15 CEST 2013
Dear Alexander, Perhaps I can just clarify what the RIPE Database software does with this data. I presume you are referring to the policy attributes in the aut-num object (import, export, etc). There are syntax checks on all these attributes. These apply the rules defined in RPSL. For example, the keywords and value types and ranges. No checks are done on policy. We don't check for matching import/export. We don't check for any keywords being present or not, or for any values or references being 'correct' by any definition. If the community considers it would be useful to apply checks on the policy content, the RIPE NCC would be happy to work with the community in defining any such checks. Regards Denis Walker Business Analyst RIPE NCC Database Team On 16/10/2013 16:46, Alexander Azimov wrote: > Dear colleagues, > > During current RIPE meeting I have presented my report about > verification of route policy from registries with deeper analysis for > RIPE database. I analysed the customer to provider relations because of > its global visibility. The result are fearful: 60% of link completeness, > less than half of this amount have information about Pref values and > again most of pref values have errors. As a result there is only 10% > likelihood to find real priorities using this dataset. The community > must decide how to change this situation. In my opinion there are only > two ways to overcome this problem: verify this data or delete at all. > > All our data is available on our website <http://radar.qrator.net>. The > collected data is based on imitation mathematical model with use of AS > paths recovered from BGP views and novel active verification abilities > that could detect priorities on every level of BGP decision making > process. We are eager for collaboration and eager to help RIPE Stats or > RIPE DB to verify policy data, highlight errors and give other > aggregated data if community decides that it is needed. > > > -- > | Alexander Azimov | HLL l QRATOR > | tel.: +7 499 241 81 92 > | mob.: +7 915 360 08 86 > | skype: mitradir > | mailto: aa at highloadlab.com <mailto:aa at highloadlab.com> > | visit: www.qrator.net <http://www.qrator.net/>
- Previous message (by thread): [db-wg] Route Polict Verification
- Next message (by thread): [db-wg] Route Polict Verification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]