<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EstiloCorreo18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple style='word-wrap:break-word;-webkit-nbsp-mode: space;line-break:after-white-space'><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>That’s the point, we don’t have that problem in the IETF or any other RIR.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>So, I think is fair that you look for solutions where you have problems or you may have them.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Anyway, I know that other RIRs are watching the verification process in AFRINIC so to implement also themselves, just as preventive measure, and I think it is very smart doing so.<o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 24/1/22 9:46, "Mike Silber" <<a href="mailto:silber.mike@gmail.com">silber.mike@gmail.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>Andrew<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>You make some good points. Not sure if the IETF also has an issue with sock-puppets, astroturfing and posters using pseudonyms?Maybe you can enlighten us?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>My personal view is that the key point that is missing [and the *real* issue on the mailing list] is not identity verification, but failure to disclose affiliation.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Along with the suggestions you made [code of conduct, well enforced] is a disclosure requirement [see ICANN’s SOI / statement of interest process for all working groups as an example].<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>I have no issue with comments from users using pseudonyms - provided they have a complete SOI setting out their affiliations to avoid the *real* concern with such users, namely sock-puppets and astroturfing.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Looking forward to your feedback.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Mike<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'>On 24 Jan 2022, at 09:22, Andrew Alston via Community-Discuss <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><div><div><div><div><div><p class=MsoNormal style='margin-left:35.4pt'>If AfriNIC chooses to remove me from the lists because I refuse to hand over ID documents – while they are quite ok with taking my money as an authorized admin contact – then in effect, they are no longer providing the service that a full RIR providers to other members, based on a requirement that they have no mandate to implement.<o:p></o:p></p></div></div><div id=mail-editor-reference-message-container><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>AfriNIC cannot guarantee the security of information provided.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>AfriNIC has no way to verify that the documents submitted are valid<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>AfriNIC has no mandate from its member base to request for and hold sensitive personal information.<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>To be blunt – I will be giving AfriNIC no such documents – if they choose to remove me from the lists and remove my say in this community and in their processes as a result – either admit at that point that AfriNIC is no more than a book keeper to me – and discount my fees accordingly – or – I will take whatever action I deem necessary to deal with what I view as a flagrant, unsanctioned move by an organization that is meant to be bottom up but has now just lost the plot.<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>I might point out that – no other RIR has such a requirement. Nor does the IETF. What they do to solve the issues on their lists is they enforce a code of conduct, complete with an appeal process and a sergeant at arms who’s job it is to deal with violations of the code of conduct. They sure as hell don’t ask for sensitive documents to prove who people are – that’s insane.<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>Andrew<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><div><p class=MsoNormal style='margin-left:35.4pt'><b>From:</b> Owen DeLong via Community-Discuss <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a>> <br><b>Sent:</b> Thursday, January 20, 2022 9:51 PM<br><b>To:</b> AFRINIC Communication <<a href="mailto:comms@afrinic.net">comms@afrinic.net</a>><br><b>Cc:</b> Community Discuss <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a>><br><b>Subject:</b> Re: [Community-Discuss] ID verification on the Database Working Group mailing list<o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>The form requires one to agree to submit to an unspecified online identity verification process. This is not reasonable. The process should be spelled out in detail prior to demanding that someone agree to submit to it. <o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>While I favor a reasonable identity verification process, the document linked has no relationship to such a thing and is, instead a contract of attainder which should not be allowed. <o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>Owen<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><o:p> </o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>On Jan 20, 2022, at 10:46, Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<o:p></o:p></p></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>The requirements are expressed in sexist terms. Arguably a violation of the very CoC it alleges to bind one to strict adherence. <o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>Perhaps this should be reviewed and amended?<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>Owen<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><o:p> </o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>On Jan 20, 2022, at 04:52, AFRINIC Communication <<a href="mailto:comms@afrinic.net">comms@afrinic.net</a>> wrote:<o:p></o:p></p></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'>Dear colleagues,<br><br>AFRINIC is now introducing an ID verification process for our mailing lists. This is part of our “Know Your Customer” (KYC) measures that aims at addressing any abuses on the AFRINIC community mailing lists and making our online community a place where people can better engage and learn from and with their peers.<br><br>The ID verification will start its application with the Database Working Group mailing list and will follow a simple process, before embarking on the other AFRINIC community mailing lists. Thank you for your constructive feedback as we seek to continue improving the process.<br><br>You are kindly invited to start the process by filling out this form: <a href="https://verification.afrinic.net/">https://verification.afrinic.net/</a><br><br>Subscribers to this mailing list have until the 20th of February 2022 to complete their ID verification.<br><br>We encourage all subscribers to take necessary steps before the above timeframe has elapsed.<br><br>Kindly note that after the 20th of February 2022, the messages of the subscribers who have not completed the KYC check will be automatically rejected.<br><br>Regards,<br>AFRINIC Team<br><br>………………………………………………..<br><br>Chers collègues,<br><br>AFRINIC introduit un processus de vérification d'identité pour nos listes de diffusion. Ceci fait partie de nos mesures "Know Your Customer" (KYC) qui visent à traiter tout abus sur les listes de diffusion de la communauté AFRINIC et à faire de notre communauté en ligne un lieu où les gens peuvent mieux s'engager et apprendre de et avec leurs collègues.<br><br>La vérification d'identité commencera par la liste de diffusion du Groupe de travail sur les bases de données (DBWG) et suivra un processus simple, avant de s'étendre aux autres listes de diffusion de la communauté AFRINIC. Nous vous remercions de vos commentaires constructifs, car nous cherchons à continuer à améliorer le processus.<br><br>Vous êtes cordialement invités à commencer le processus en remplissant ce formulaire : <a href="https://verification.afrinic.net/">https://verification.afrinic.net/</a>.<br>Les abonnés à cette liste de diffusion ont jusqu'au 20 février 2022 pour procéder à la vérification de leur identité.<br><br>Nous encourageons tous les abonnés à prendre les mesures nécessaires avant que le délai ci-dessus ne soit écoulé. <br><br>Veuillez noter qu'après le 20 février 2022, les messages des abonnés qui n'auront pas effectué la vérification KYC seront automatiquement rejetés.<br><br>Cordialement,<br>L'équipe AFRINIC_______________________________________________<br>Community-Discuss mailing list<br><a href="mailto:Community-Discuss@afrinic.net">Community-Discuss@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo/community-discuss">https://lists.afrinic.net/mailman/listinfo/community-discuss</a><o:p></o:p></p></div></div></blockquote></div></blockquote></div></div></div></div><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________<br>Community-Discuss mailing list<br><a href="mailto:Community-Discuss@afrinic.net">Community-Discuss@afrinic.net</a><br>https://lists.afrinic.net/mailman/listinfo/community-discuss<o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________ Community-Discuss mailing list Community-Discuss@afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss <o:p></o:p></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>