[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 ]
Rob Evans
rhe at nosc.ja.net
Wed Oct 16 21:52:32 CEST 2013
Hi, > Actually, having a *warning* if you send in an aut-num: object that > declares import/export policies that do not match the corresponding > "other AS's" aut-num: policies could useful. Yes, it would create > an impressive amount of warnings, but maybe that leads to sufficient > peer pressure... I wonder if this should be a keyword-driven thing to request the verification of policy rather than generating warnings on updates, as policies may start off right but what you really want is a quick way to check whether another ASN has changed their policy and you need to change your own policy to reflect that. > Making it an *error* is a no-go, as the amount of non-matching policy > documentation is too high (and you'd have an unsolvable conflict when > trying to set up a new peering, as whoever tries to enter the policy > first would be told "error: other end is not there"). Just a quick plug that towards the end of tomorrow's routing working group session Denis is going to present on import-via/export-via and following that is going to ask for some thoughts about new ways of showing peering relationships in RPSL... Cheers, Rob -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 203 bytes Desc: Message signed with OpenPGP using GPGMail URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20131016/ccdcb501/attachment.sig>
- 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 ]