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]/
[members-discuss] Registry Services Ticket Response Time
- Previous message (by thread): [members-discuss] Registry Services Ticket Response Time
- Next message (by thread): [members-discuss] Registry Services Ticket Response Time
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurtis Lindqvist
kurtis at linx.net
Thu Sep 23 09:43:22 CEST 2021
> On 22 Sep 2021, at 11:58, Elvis Daniel Velea <elvis at v4escrow.net> wrote: > > No, I am not making this assumption. What I am saying is that the NCC is basing the security of those resources and the ‘holdership’ of a resource based on the SSO owner and the documents they receive from him/her. They evaluate these documents by comparing them visually, but they don’t really have any real training in identifying a fake signature, they can suspect it, maybe. > The NCC RS dept. has never had people specialized in identifying fake documentation. It is very hard to identify abuse or faked documentation considering the large service region it covers. Deregistering resources or refusing services based on suspicion is just an invitation to the NCC being sued and losing more time in a court than evaluating requests. > All the NCC is basing its decisions on is that by catching the bad guys those will not have the knowledge or willingness to take it to court. > That is why it is very important that the NCC focuses it’s effort in ensuring the members have secure access to the LIR Portal and the tools available. > > Ever wondered why we have only heard of a handful of deregistrations in almost 30 years? > Why the NCC has rarely gone (or been taken) to court? It’s because it is not their job to prove fraud and even when they do, the NCC should first report it to LEAs and let them investigate. I don’t have insight into what checks or processes the NCC follows, but in most internal audits and audits this is not just based on signature verification but on cross referencing documents and historical records so not sure to what extent just a signature is really at play. >> You seem to focus on the easy of the transfer market only but the that is not the NCCs goal, far from it. NCC has other, and in my view much more important objectives they need to fulfil to protect us all. To do this they need to uphold processes that might impact the speed of the transfer market, but I personally think that is a price worth paying for a robust system and community trust. That said, the checks should be streamlined and effective, but not compromise the integrity of the data. >> > I am not talking only about transfers here. ALL tickets are delayed, even those where people just want to open an LIR. You see that I’m an IPv4 Broker an guess that’s my only concern. That’s not correct and you are wrong here to make that assumption. > The Registration Services department is failing to reply within the agreed SLA and some tickets take months to resolve (see Felipe’s presentation showing that there are over 100-150 tickets opened monthly that take more than 8 weeks or/and 10 replies to be resolved, at least 1/3rd of these are improvable so something is wrong with some of the processes or communication, see slide 7 *) I wasn’t referring to the time of ticket resolution, but to the process. I absolutely agree that the SLAs should be met. I wanted to separate the discussion of what process checks the NCC does and make sure this is as robust as possible and not eroded because of a wish of speedy ticket resolutions or a desire to meet the SLA. > I am not asking for any compromise or anything that would compromise the accuracy of the registry. Good that we could clarify that! - kurtis - -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Message signed with OpenPGP URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20210923/2c8a35a9/attachment.sig>
- Previous message (by thread): [members-discuss] Registry Services Ticket Response Time
- Next message (by thread): [members-discuss] Registry Services Ticket Response Time
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]