[db-wg] Route Polict Verification
- Previous message (by thread): [db-wg] Route Polict Verification
- Next message (by thread): [db-wg] Korrektion: RIPE67 DB-WG Draft Agenda V2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alexander Azimov
aa at highloadlab.com
Thu Oct 17 11:12:49 CEST 2013
Hi, Rob. Understood. However, updating RPSL (for example by abstracting the > import/export attributes into a single separate peering object -- not my > idea, I hasten to add), could make it easier to maintain accurate policies > than having to ensure two different aut-num objects agree with each other. > I agree that it would be signficant improvement in the quality of data. But problems with link completeness and wrong priorities could still occur. I think it would be a good first step but it isn't sufficient. -- | Alexander Azimov | HLL l QRATOR | tel.: +7 499 241 81 92 | mob.: +7 915 360 08 86 | skype: mitradir | mailto: aa at highloadlab.com | visit: www.qrator.net -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20131017/cebee127/attachment.html>
- Previous message (by thread): [db-wg] Route Polict Verification
- Next message (by thread): [db-wg] Korrektion: RIPE67 DB-WG Draft Agenda V2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]