Alex I think the notification to the ASN holder is a good thing. The notification could include a reference to the inetnum holder so that the ASN holder could make contact more easily, if necessary. If we accept that the inetnum holder has the authority to create, then it is not clear to me why the ASN holder should have the right to delete. If there has been a mistake it is to the detriment only of the inetnum holder's organisation, and they can remove the Route Object and correct it. For clarity - By "ASN holder" we are referring to the origin ASN in the new Route Object, not any other. This policy change would enable a clear and simplified instruction for organisations needing authority to originate temporarily. Thanks Steve

On 26 Jun 2015, at 06:43, George Michaelson <ggm@apnic.net> wrote:

On 25 June 2015 at 21:42, Job Snijders <job@instituut.net> wrote: On Thu, Jun 25, 2015 at 09:33:44PM +0200, George Michaelson wrote:

...

For your information, APNIC Hostmasters have moved to a mode of operation where for inetnum owners where the AS holder is not the same person, and a request is lodged with helpdesk for assistance, the hostmasters manually override and create the object for the inetnum holder, only removing it if an AS holder objects. The inetnum holder needs to be recognised in our systems.

Its a hand-mediated inetnum-only route object. Previous practice was to wait for explicit approval from the AS holder. Now, its created first, and withdrawn if there is an objection.

There have been no complaints. APNIC HM are considering portal changes and other process work to automate this.

What is the benefit of the hand-mediation? Or is that just an artifact of the software implementation?

Its an artefact of the s/w implementation. I imagine once they work out how to do this in the portal, this will be changed.

Does APNIC send a notification to the AS holder that an object was created in which they were referenced?

Yes. The following template is used:

======

Dear (ASN custodian), This is to inform you that the following route/route6 object has been registered in the APNIC Whois Database with your AS number referenced in the "origin" attribute.

--- insert route object ---

The IP addresses holder has asked that APNIC help register this route object in the APNIC Whois database.

If you believe your AS number should not be referenced as the "origin" in this route object, please contact us by replying to this email.

Kind Regards,

======

cheers

-George

Kind regards,

Job

End of db-wg Digest, Vol 47, Issue 1 ************************************