17 Oct
2013
17 Oct
'13
10:15 a.m.
Hi Alexander,
RIPE DB makes people mistaken and this couldn’t be solved by updating RPSL.
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. Cheers, Rob