This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Temporary origins
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Thu Jun 25 21:42:33 CEST 2015
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? Does APNIC send a notification to the AS holder that an object was created in which they were referenced? Kind regards, Job
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]