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
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Band
alexb at ripe.net
Thu Jul 2 11:42:12 CEST 2015
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? Cheers, Alex > On 26 Jun 2015, at 06:43, George Michaelson <ggm at apnic.net> wrote: > > > > On 25 June 2015 at 21:42, Job Snijders <job at 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 >
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]