[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 ]
Gert Doering
gert at space.net
Wed Oct 16 18:10:53 CEST 2013
Hi On Wed, Oct 16, 2013 at 07:05:15PM +0300, Denis Walker wrote: > 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. 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... 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"). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 306 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20131016/0685f8da/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 ]