[db-wg] Temporary origins
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Deal with "non-breaking-space"-characters in updates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Wiesinger
sebastian at karotte.org
Thu Jul 9 14:03:47 CEST 2015
* Alex Band <alexb at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 581 bytes Desc: Digital signature URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20150709/6f9aa654/attachment.sig>
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Deal with "non-breaking-space"-characters in updates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]