[routing-wg] Notification/authorisation of references to aut-num from other RPSL objects

Moving this to the routing wg list only to minimise noise. Also Subject change to reflect the topic.


On 09 Jun 2014, at 15:53, Hank Nussbacher <hank at efes.iucc.ac.il> wrote:

> At 14:49 09/06/2014 +0200, João Damas wrote:
>> Dear all,
>> at the recent RIPE 68 meeting there was a discussion about issues concerning the re-issue of recovered 16-bit ASNs by the RIPE NCC and possible modifications to the content of routing-related attributes in RIPE Database objects, namely the routing policy attributes of autnum and as-set objects.
>> 
>> The observed consensus during the meeting was that:
>> 
>> - the RIPE NCC should not to remove references to recovered ASNs from import and export lines, and neither from as-set objects; routing policies are the realm of the object owner and are not related to allocation data.
> 
> On a related matter, is it possible currently to setup my aut-num that if anyone adds my autnum to their import/export/as-set objects I would receive a notification about it?  Currently the "notify" field only informs me of changes to the specific aut-num, not people who reference my aut-num w/o my permission?
> 
> If  this is not feasible with the system today, would it be possible to add this feature?  I'll explain the rationale: we have recently discovered that hostile aut-num's that intend to perform a BGP hijack, will add the victims aut-num to their routing policy or to their unsuspecting upstream.  This policy is then picked up as legitimate and propogated.  By having a "notify-on-policy" email address field, I would be able to quickly see who is planning on hijacking my IP ranges.

This sounds like a reasonable thing to do to me. In fact, now that this has been mentioned it does sound like an obvious thing and I wonder what took the hostile aut-num’s so long to subvert the intent of the those fields.

Joao
-------------- 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: </ripe/mail/archives/routing-wg/attachments/20140609/4c65f63f/attachment.sig>