On Thu, Jul 02, 2015 at 11:42:12AM +0200, Alex Band wrote:
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.
Seeing that APNIC has positive experiences, would our Community support such an approach considering the up and downsides?
Works for me. It's within the authority of the prefix holder to decide whom to allow to advertise the prefix. If the ASN holder doesn't want to advertise it, don't. Out of interest, do you propose to automate the removal of disputed route: objects? How would that be authorised if maintained solely by the inetnum: maintainer? rgds, Sascha Luck