[ncc-services-wg] Voluntary Transfer Lock Policy
- Previous message (by thread): [ncc-services-wg] Voluntary Transfer Lock Policy
- Next message (by thread): [ncc-services-wg] Voluntary Transfer Lock Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oleg Zinkov
o.zinkov at kyivlink.com
Mon Aug 28 13:02:24 CEST 2023
28.08.2023 10:42, Volodymyr Kuzmin пише: > > Hi working group! > > I support the current policy proposal text. > > -- > Best regards, > Volodymyr Kuzmin > Chief Technical Officer, Web Pro LLC > mob +38(093)-711-92-66 > https://webpro.ua > In my opinion, the procedure should be simplified. For example, the lock button in the RIPE cabinet, which is available for maintainers. After activating the blocking button, a link (include generating code inside) is sent to the contact email and the lock procedure has been started after clicking this link. Of a kind, a variant of automated two-factor verification. -- ---------------------- https://kyivlink.com https://t.me/kyivlink https://fb.com/kyivlink https://instagram.com/kyivlink 044 332 9555 093 332 9555 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ncc-services-wg/attachments/20230828/6680c6a9/attachment.html>
- Previous message (by thread): [ncc-services-wg] Voluntary Transfer Lock Policy
- Next message (by thread): [ncc-services-wg] Voluntary Transfer Lock Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]