<div dir="ltr">While I agree with some of your suggestions, I do not agree that we need to know each other to understand each other. I believe that the validity of my arguments should be the main determinant factor and not whether we have met physically before.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 24, 2022 at 2:53 PM Mike Silber <<a href="mailto:silber.mike@gmail.com">silber.mike@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">My request is not disclosure of affiliation - but disclosure of *interest*. Affiliation is but one item.<div><br></div><div>In the world of a small community and face to face meetings, we got to know and understand each other.</div><div><br></div><div>I think we should try retain that situation of being able to know and understand each other.</div><div><br></div><div>An example here: <a href="https://community.icann.org/display/gnsosoi/New+SOIs" target="_blank">https://community.icann.org/display/gnsosoi/New+SOIs</a></div><div><br></div><div> <br><div><br><blockquote type="cite"><div>On 24 Jan 2022, at 16:18, Andrew Alston <<a href="mailto:Andrew.Alston@liquidtelecom.com" target="_blank">Andrew.Alston@liquidtelecom.com</a>> wrote:</div><br><div>
<div>
<div>
<div>
<div dir="ltr">
<div dir="ltr" style="background-color:rgb(255,255,255)">
Let me be clear - the affiliation to me is actually neither hear nor there other than on the members list - where I believe that affiliation is absolutely critical.</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
The members list however is limited to members and anyone posting on there should be a member and should be speaking as such.</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
To be frank though as per my previous comments - what should matter on the lists is the content of the message not the identity of the sender. The RIRs and the ietf etc - and anywhere that engages in the concept of consensus based decision making is meant
to look at the content of the messages.</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
A single objection that is unaddressed (not necessarily resolved - but it has to be adequately addressed) is meant to act as a blocker. Support by a million people is not a gauge of consensus - nor is the affiliation of the person indicating such.</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
For some reason though we all seem to have forgotten the principles of consensus as best defined in rfc 7282 which can be found at <a href="https://datatracker.ietf.org/doc/html/rfc7282" target="_blank">https://datatracker.ietf.org/doc/html/rfc7282</a></div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
This has for years been the basis on which technical consensus is defined.</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
<br>
</div>
<div dir="ltr" style="background-color:rgb(255,255,255)">
Andrew </div>
</div>
</div>
<div id="gmail-m_3310985510108974781ms-outlook-mobile-signature">
<div><br>
</div>
Get <a href="https://aka.ms/o0ukef" target="_blank">Outlook for iOS</a></div>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_3310985510108974781divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> Anthony Ubah <<a href="mailto:ubah.tonyiyke@gmail.com" target="_blank">ubah.tonyiyke@gmail.com</a>><br>
<b>Sent:</b> Monday, January 24, 2022 4:32:17 PM<br>
<b>To:</b> Andrew Alston <<a href="mailto:Andrew.Alston@liquidtelecom.com" target="_blank">Andrew.Alston@liquidtelecom.com</a>>; Mike Silber <<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>>; Ben Maddison <<a href="mailto:benm@workonline.africa" target="_blank">benm@workonline.africa</a>>; JORDI PALET MARTINEZ <<a href="mailto:jordi.palet@consulintel.es" target="_blank">jordi.palet@consulintel.es</a>><br>
<b>Cc:</b> General Discussions of AFRINIC <<a href="mailto:community-discuss@afrinic.net" target="_blank">community-discuss@afrinic.net</a>><br>
<b>Subject:</b> Re: [Community-Discuss] ID verification on the Database Working Group mailing list</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div dir="auto">Hi,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Permit me to barge in into this threesome to add that, while the use of sock puppets and crowd mentality should be discouraged in the community, there is absolutely nothing wrong with the use of pseudonyms, nor cache affiliations, as opinions
and affiliations might not always align. Both can also be on a collision course.
<div dir="auto"><br>
<div dir="auto">Now that I have your attention, I'll like to buttress that.</div>
<div dir="auto"><br>
</div>
<div dir="auto">If an organization has not granted rights to an individual to represent, that member of staff has absolutely no right to state affiliation, use official email domain, or even identify the organization's resources in holding like AS number or
IP ranges. Doing otherwise is illigal.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Still chiming off the reason above, the call for use of organizational email/domain name is absurd. I've enjoyed a good laugh in the background every time some community members call for 'void' on comments for "Gmail" users as against common
sense, on the premise of 'Gmail', and nothing more. This is a very narrow-minded call for a dozen reasons; </div>
<div dir="auto">One, being that, while some members own, or are co-founders of their organizations, some spend a bulk of/their entire career in one, while others are in constant movent across organizations and regions. Different strokes for different folks.</div>
<div dir="auto">Hence such marginalization is not well-thought-out, and baseless. For continuity purposes, members should be allowed to use whatever email address they please.</div>
<div dir="auto">Also switching emails will also put long-standing community members at risk of being disenfranchised in voting within the community, as a new email might not fulfil the longevity clause introduced lately for eligibility to vote in the PDGW voting
processes.</div>
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">That said, I personally have no issues with verifying my own identity (I already have), but I shouldn't be compelled to state my affiliation as a yardstick to gauge my comments. </div>
<div dir="auto">According to Afrinic's guidelines on this mailing list, it is for
<b>'anybody who has an interest in the activities of AFRINIC working groups'</b>, and not for open resource holders, or affiliates.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Don't take my word for it. A quick reference to the Afrinic website will provide some input on this. (<a href="https://afrinic.net/email" target="_blank">https://afrinic.net/email</a>)</div>
<div dir="auto"><br>
</div>
<div dir="auto">An excerpt;</div>
<div dir="auto"><br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
"Most of these mailing lists are open to anybody who has an interest in the activities of AFRINIC working groups and provides space for people to share information for the benefit of the entire community.<br>
While AFRINIC encourages the use of these lists for a healthy, relevant debate and information sharing, we also advise all to ensure that the AFRINIC Community Code of Conduct is respected."</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">In conclusion, the agenda being pushed is against the principles of these guidelines and is simply dancing at the edge of a legal cliff.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best Regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Anthony Ubah</div>
<div><i>Zero Affiliation</i></div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
</div>
<br>
<div>
<div dir="ltr">On Mon, Jan 24, 2022, 6:19 AM Andrew Alston via Community-Discuss <<a href="mailto:community-discuss@afrinic.net" target="_blank">community-discuss@afrinic.net</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="ltr">
<div></div>
<div>
<div>
<div dir="ltr">While affiliation is important - I think it’s relatively easy to solve - enforce a rule in the code of conduct that demands that posts contain either a statement of affiliation in the signature - or the company handle you are speaking on behalf
of.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">If you are speaking in private capacity - the signatures can still be there and a clear statement that you are speaking in private capacity.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">This means the companies can deal with the offenders if they speak without authorization or if the signatures are fake.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Andrew </div>
<div dir="ltr"><br>
</div>
<div id="gmail-m_3310985510108974781x_gmail-m_-1196915510659127941m_-4413846395965270449ms-outlook-mobile-signature">
<div><br>
</div>
Get <a href="https://aka.ms/o0ukef" rel="noreferrer" target="_blank">
Outlook for iOS</a></div>
</div>
<div> </div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_3310985510108974781x_gmail-m_-1196915510659127941m_-4413846395965270449divRplyFwdMsg" dir="ltr">
<font face="Calibri, sans-serif"><b>From:</b> Ben Maddison <<a href="mailto:benm@workonline.africa" target="_blank">benm@workonline.africa</a>><br>
<b>Sent:</b> Monday, January 24, 2022 13:09<br>
<b>To:</b> Mike Silber<br>
<b>Cc:</b> Andrew Alston; General Discussions of AFRINIC<br>
<b>Subject:</b> Re: [Community-Discuss] ID verification on the Database Working Group mailing list
<div> </div>
</font></div>
<font size="2"><span style="font-size:11pt">
<div>Hi Mike,<br>
<br>
On 01/24, Mike Silber wrote:<br>
> [...]<br>
> > On 24 Jan 2022, at 11:35, Ben Maddison <<a href="mailto:benm@workonline.africa" target="_blank">benm@workonline.africa</a>> wrote:<br>
> > <br>
> > [...]<br>
> > <br>
> > If a sender's affiliation is not obvious (From: domain, signature, etc),<br>
> > then the chairs and/or moderators should challenge them to state it.<br>
> > Failure[*] to do so should:<br>
> > A) be an indication to the community (and particularly for the purposes<br>
> > to considering consensus) that any arguments presented should be<br>
> > viewed with great skepticism; and<br>
> > B) be a CoC violation, eventually resulting in a ban.<br>
> <br>
> I accept your point - but think it would be better served on<br>
> subscribing to the mailing list [or to retain your posting rights]<br>
> rather than on a challenge basis. One post escapes the challenge and<br>
> then there are claims of favouritism :-) <br>
<br>
Yup, that also seems a reasonable approach that I could support.<br>
<br>
Assuming such a disclosure would be self asserted(?), that leaves some open<br>
questions:<br>
<br>
- How is that information provided to the reader of a message (perhaps<br>
auto inserting a link to a disclosure webpage at the foot of each<br>
message?)<br>
- How is the provided information maintained to prevent staleness when,<br>
e.g. a subscriber changes job, accepts a new consulting gig, gets<br>
elected to a board somewhere?<br>
- (Most stickily) to what extent is the provided disclosure verified,<br>
and by whom? This is hard enough in the case of positive assertions,<br>
and seems near-impossible in the case of omissions.<br>
- Probably others...<br>
<br>
Cheers,<br>
<br>
Ben<br>
</div>
</span></font></div>
</div>
</div>
_______________________________________________<br>
Community-Discuss mailing list<br>
<a href="mailto:Community-Discuss@afrinic.net" rel="noreferrer" target="_blank">Community-Discuss@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/community-discuss" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/community-discuss</a><br>
</blockquote>
</div>
</div>
</div>
</div></blockquote></div><br></div></div>_______________________________________________<br>
Community-Discuss mailing list<br>
<a href="mailto:Community-Discuss@afrinic.net" target="_blank">Community-Discuss@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/community-discuss" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/community-discuss</a><br>
</blockquote></div>