* Alex Band <alexb@ripe.net> [2015-07-02 11:45]:
Thanks for sharing your experiences George.
I'm curious to hear from our Community about what they think about this mode of operation; simply create the route object on the inetnum holder's authorisation alone, inform the ASN holder that it was created and only remove the object if they object.
It would simplify the authorisation model tremendously and save a lot of frustration and customer support tickets.
Hello Alex, I would support that. Could there be a mechanism to block "repeat offenders" from creating route: objects with my AS? I'm just envisioning an "edit war" of people adding a route object and me requesting it to be removed. Or am I just too paranoid/pesimistic? Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant