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/routing-wg@ripe.net/
[routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals
- Previous message (by thread): [routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals
- Next message (by thread): [routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Wed May 29 01:20:21 CEST 2019
> On May 28, 2019, at 7:09 PM, Delacruz, Anthony B <Anthony.DeLaCruz at CenturyLink.com> wrote: > > I’m very appreciative for the efforts here to clean out the IRR. I am a major resource holder with IP’s and ASN’s from all the RIR and we also run an IRR. I am often frustrated that when I open a ticket with the NCC and even place an entry in whois on space I own that is clearly listed wrong in RIPE-NONAUTH IRR that it is a multi week struggle to get entries removed and they have me chase the contact that put in the entry which is often not responsive. > > Since not all of my space right now is easily taken care of using RPKI for this, I would very much like to suggest additional methods be available for the NCC to consider a valid request for removal. Other IRR’s I work with we usually send the request from the MNT or POC that is on the account/orgid/lir listed with the RIR and in some cases I go as far as to set whois on the blocks with various messages like “please clear, IRR BAD, Hijacked, Recovered Space” and several other messages to make it understood the range has some reason we don’t want an IRR entry to be showing for it. Many of the dozen other IRR are quick and a pleasure to work with but the NCC is not ever easy or prompt on the cases I have put in. > This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. Is this just with RIPE-NONAUTH, or in the regular source: RIPE objects? RIPE-NONAUTH is a bit of a wild-west and I suspect most people would be best served if they stopped building filters with that set unless their customers specifically requested it. I’ll also make note that the Level3 (now CTL?) IRR has not had an owner for many years and people have had a hard time communicating about issues with objects there. I understand why cleanup is hard or unpopular (it’s like picking up litter, there’s little reward or notice that the trash was taken away). - Jared
- Previous message (by thread): [routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals
- Next message (by thread): [routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]