On Thu Nov 09, 2017 at 11:25:00AM +0300, Alexandr Gurbo wrote:
RIPE NCC staff is right. Strange to see name like 1@xxx. Who is this? Create alias for you short email by recommendations and continue work on ticket.
While 1@ may be impersonal does it really matter when they can just as easily make up anon.russian@? It's not unreasonable to require them to identify themselves in the email but the email address is no proof
------- 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@ripe.net etc. cannot be accepted. We require a personal SSO account such as: Johnsmith@ripe.net for example.
I find that annoying, I prefer to use role accounts to deal with companies, and don't want them tied to personal details for a few reasons including - extra admin creating personal accounts, having to keep one of them as the master is a nuisance when that master one leaves the company, so you end up making a fake user people change many personal accounts = more scope for hacking, each may be used less often than a shared role account, often crazy login restrictions lead to an unmanagable mess of passwords, many expiring quickly and generating lots of nagging email. personal account = person likely the share passwords with their leaked yahoo account as they have too many logins to change the password on each month I don't want my personal profile influencing adverts on business web sites. RIPE may leak all the details so it adds to the risk of our personal data being leaked and adds to global pool of identity theft data. brandon