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] Email issues with RIPE NCC for new LIRs
- Previous message (by thread): [members-discuss] Email issues with RIPE NCC for new LIRs
- Next message (by thread): [members-discuss] Email issues with RIPE NCC for new LIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ingrid Wijte
ingrid at ripe.net
Thu Nov 9 11:44:25 CET 2017
Dear Yuri, As we explained yesterday in our email to you, there has indeed been a misunderstandingwhich we have clarifiedinternally. It is not a problem if the email address for the SSO account is a role account. However, we do need a person's name associatedwith the SSO account. Some examples: SSO: John Doe email address: johndoe at ripe.net <mailto:johndoe at ripe.net> This is acceptable SSO: John Doe email address: department at ripe.net <mailto:department at ripe.net> This is acceptable SSO: IT department email address: johndoe at ripe.net <mailto:johndoe at ripe.net> This is not acceptable The RIPE NCC communicates with individuals and we need to understand who is submitting the requests to us. We have always required the name of an individual in our communications with LIRs. Before SSO Accounts were introduced, the RIPE NCC had always asked LIR contacts to be registered in the LIR Portal with their personal name. This requirementis there for security reasons. For example, in case of a disputed transfer itis crucial to know who submitted the request. I hope this clarifies? Best Regards, Ingrid Wijte RIPENCC On 07/11/2017 14:26, Staff wrote: > Dear all! > > I would like to bring one new issue with RIPE NCC to public. > > This situation mostly rely on new members and new LIRs. RIPE NCC started > to censor email names and filter them as much as they want. And that > also depends from RIPE NCC staff that take a ticket. > > This makes delays in ticket processing because we spend about 1-2 weeks > already for new company LIRs because RIPE NCC staff refuse to continue > until they see the email name they like and we have to create email by > email so they like it > > I found this completely inconvenient, useful and unfriendly. > This situation should be changed. Last months RIPE NCC changed a lot of > things in the usual work and become harder to do simplest things with > RIPE NCC staff. > > Currently RIPE stopped to accept my personal email that I use for almost > 10 years. This email contains from one symbol in it's name. > > Please see some examples > > ------- > In order for our Registration Department to be able to process resources > requests, LIRs must first have a personal SSO account. Generic role SSO > accounts such as info at ripe.net etc. cannot be accepted. We require a > personal SSO account such as: Johnsmith at ripe.net for example. > > The email provided 1 at ntx.ru cannot be accepted. > ... > Nicole Castaibert (RIPE NCC Support) > --------- > > All nicknames, short names, names of the company in email also not > accepted by RIPE NCC anymore. So we have to create new emails and use > new emails with some name in it. > > But the main useless of all of that - that new LIR can change > registration account email after LIR registration done. > So this all they require is useless. > > That takes my time, time of my staff, time of RIPE NCC staff that get > paid from LIR members fees. I found that RIPE NCC work does not comply > with the proper quality standards and not members oriented. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20171109/bcca228d/attachment.html>
- Previous message (by thread): [members-discuss] Email issues with RIPE NCC for new LIRs
- Next message (by thread): [members-discuss] Email issues with RIPE NCC for new LIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]