<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 31/12/21 4:26 am, Jeff Neuman via
At-Large wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BL3P221MB0663C83A74BDD7D95490A967BE459@BL3P221MB0663.NAMP221.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">
<div>
<div dir="ltr">FYI, I have updated my At-Large SOI and GNSO
SOI to disclose the propose future role as Chief Legal
Officer of Dot Hip Hop, LLC the future registry operator for
.hiphop.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I apologize for not having done this before,
but I was waiting for the assignment to be approved. We
filed it 141 days ago.</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>A conflict of interest does not arise when you are actually
officially assigned a position etc, it arises when you start to
engage with an activity -- applying for the assignment in this
instance -- that, as here, directly conflicts with your public
interest roles in At-Large , GNSO etc.To explain further if this
is still unclear to you: At-Large and GNSO need to know it when
you were actively pursing some commercial interests in applying
for a gLTD etc, and not latter when it is already assigned. Is it
not so very simple and straight-forward! </p>
<p>How the 'multistakeholderist community' reads this democratic
vestige of the idea of 'conflict of interest' is absolutely a
disgrace, and dishonor to all those who fought for and built
democracies. As I read Jeff's email below of Dec 30th, my head
spins as to how hallowed concepts like 'conflict of interest' can
be mauled in self-defense. <br>
</p>
<p>(It is the MSist sin when they conflated corporate governance
with public governance, whereby the thin half ethics of the former
are employed as the foundations for what has to be public
governance of some public functions. Although these practices do
not pass even the light corporate governance ethical tests.) <br>
</p>
<p>To have someone so deeply involved with shaping new forms and
business models of gTLD, and making direct money out of it, as
GNSO's liaison to GAC and to ICANN stuff -- nothing personal here,
but it makes my democratic guts retch in sheer horror. This is
multistakeholderism for you! A pall bearer for the elite who have
always felt popular democracy as a thorn in their side!</p>
<p>parminder</p>
<p>PS: As should be obvious, I have nothing against people dong
businesses like Jeff is into, but wanting to then also be one of
the key people in regulation/ governance systems for those
business is what absolutely gets my goat.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:BL3P221MB0663C83A74BDD7D95490A967BE459@BL3P221MB0663.NAMP221.PROD.OUTLOOK.COM">
<div dir="ltr">
<div>
<div dir="ltr"><span></span><span></span></div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
<div style="direction:ltr">Jeffrey J. Neuman</div>
<div style="direction:ltr">Founder & CEO</div>
<div style="direction:ltr">JJN Solutions, LLC</div>
<div style="direction:ltr"><a class="moz-txt-link-abbreviated" href="mailto:Jeff@JJNSolutions.com">Jeff@JJNSolutions.com</a></div>
<div style="direction:ltr">+1.202.549.5079</div>
<div style="direction:ltr"><a class="moz-txt-link-freetext" href="Http://www.jjnsolutions.com">Http://www.jjnsolutions.com</a></div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<div id="id-182af636-f0c8-495b-8930-4939370b6558"
class="ms-outlook-mobile-reference-message">
<hr style="display: inline-block; width: 98%; font-family:
-webkit-standard; font-size: 12pt; color: rgb(0, 0, 0);"
tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri,
sans-serif"><b>From:</b> At-Large
<a class="moz-txt-link-rfc2396E" href="mailto:at-large-bounces@atlarge-lists.icann.org"><at-large-bounces@atlarge-lists.icann.org></a> on behalf
of Jeff Neuman via At-Large
<a class="moz-txt-link-rfc2396E" href="mailto:at-large@atlarge-lists.icann.org"><at-large@atlarge-lists.icann.org></a><br>
<b>Sent:</b> Thursday, December 30, 2021 3:18 PM<br>
<b>To:</b> Hank Nussbacher;
<a class="moz-txt-link-abbreviated" href="mailto:at-large@atlarge-lists.icann.org">at-large@atlarge-lists.icann.org</a><br>
<b>Subject:</b> Re: [At-Large] ICANN Accountability
Mechanisms
<div> </div>
</font></div>
<div>
<div>
<div dir="ltr" style="">
<div dir="ltr" style="color:rgb(0,0,0);
background-color:rgb(255,255,255)">Good Questions
Hank.</div>
<div dir="ltr" style="color:rgb(0,0,0);
background-color:rgb(255,255,255)"><br>
</div>
<div dir="ltr" style="color:rgb(0,0,0);
background-color:rgb(255,255,255)">
<ol>
<li><span> The issues with .hiphop are contained in
the Reconsideration Request found here: <a
href="https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en"
moz-do-not-send="true">https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en</a>.
I am not avoiding answering the question, but
there are 25 pages of issues and an addition
dozen or so other pages of facts. </span></li>
<li><span>I do not believe that my position with Dot
Hip Hop, LLC as its Chief Legal Officer and
owner of a small minority interest of the
company presents a conflict. I was put in those
positions (especially the ODP Liaison) because
of my knowledge, skill, and experience with the
PDP for the next round. (Dot Hip Hop, LLC was
in the 2012 round). One other note, I did not
update my Statement of Interest because I was
waiting for the actual approval of the
assignment request before disclosing. Since Dot
Hip Hop, LLC is a shell entity without any
assets until ICANN approves the assignment, I
didn’t disclose. ICANN was supposed to have
approved the Assignment request in October and
if they had met their own deadline, I would have
disclosed my position prior to getting those
positions. I have committed to performing those
roles with independence, openness an
transparency and believe that I have done that
to date. If anyone believes otherwise, I would
be happy to address, and if required, would step
down. I am not being paid by anyone in serving
in these leadership roles and do them both on a
volunteer basis. I like to serve the ICANN
Community and would like to continue to make it
a better place. But, it is volunteer work that
I would give up if anyone honestly believes
there is a conflict. If you have any concerns,
let me know. I truly am an open book. I think
at one time ICANN called me a “Bad M$#%F#$%”
because I tell everyone exactly what is on my
mind. I dont believe in secrets (unless
required by law or in serving as an attorney)</span></li>
<li style="font-size:inherit"><span
style="font-size:inherit">LOL on 4 months vs 4
years. THe average turnaround time for an
assignment request for the big players is less
than 60 days. </span></li>
</ol>
</div>
</div>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
<div style="direction:ltr">Jeffrey J. Neuman</div>
<div style="direction:ltr">Founder & CEO</div>
<div style="direction:ltr">JJN Solutions, LLC</div>
<div style="direction:ltr"><a class="moz-txt-link-abbreviated" href="mailto:Jeff@JJNSolutions.com">Jeff@JJNSolutions.com</a></div>
<div style="direction:ltr">+1.202.549.5079</div>
<div style="direction:ltr"><a class="moz-txt-link-freetext" href="Http://www.jjnsolutions.com">Http://www.jjnsolutions.com</a></div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
At-Large <a class="moz-txt-link-rfc2396E" href="mailto:at-large-bounces@atlarge-lists.icann.org"><at-large-bounces@atlarge-lists.icann.org></a>
on behalf of Hank Nussbacher via At-Large
<a class="moz-txt-link-rfc2396E" href="mailto:at-large@atlarge-lists.icann.org"><at-large@atlarge-lists.icann.org></a><br>
<b>Sent:</b> Thursday, December 30, 2021 1:01:41 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:at-large@atlarge-lists.icann.org">at-large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:at-large@atlarge-lists.icann.org"><at-large@atlarge-lists.icann.org></a><br>
<b>Subject:</b> Re: [At-Large] ICANN Accountability
Mechanisms</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt">
<div class="PlainText">On 30/12/2021 17:46, Jeff Neuman
via At-Large wrote:<br>
<br>
I have no opinion on this matter but have a few newbie
questions:<br>
<br>
1. Based on <a href="https://icannwiki.org/.hiphop"
moz-do-not-send="true">https://icannwiki.org/.hiphop</a>
- what is the issue with
<br>
.hiphop?<br>
2. Based on <br>
<a
href="https://www.jjnsolutions.com/post/jeffrey-j-neuman-appointed-to-internet-leadership-positions-at-icann-72"
moz-do-not-send="true">https://www.jjnsolutions.com/post/jeffrey-j-neuman-appointed-to-internet-leadership-positions-at-icann-72</a>
<br>
isn't it a conflict of interest on your part?<br>
3. Based on <br>
<a
href="https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only"
moz-do-not-send="true">https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only</a>
<br>
you state "following ICANN staff inaction (for its
over four-month <br>
delay) of its Assignment Request for the .hiphop
Registry Agreement." - <br>
based on my experience with ICANN processes, a 4 month
delay is a mere <br>
second in ICANN time. I would start complaining only
after 4 years.<br>
<br>
Regards,<br>
Hank<br>
<br>
NB The opinions or lack of opinions expressed above
are solely my own<br>
<br>
> All,<br>
><br>
> I thought this was important enough of an issue
to be discussed and I <br>
> am happy to answer any questions you may have.<br>
><br>
> Please <br>
>
seehttps://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only<br>
> <<a
href="https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only"
moz-do-not-send="true">https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only</a>>.
<br>
><br>
><br>
><br>
> This article covers ICANN’s taking retaliatory
action against a <br>
> company I am involved in for daring to use the
Reconsideration <br>
> Process. We alleged ICANN’s inaction was a
violation of the Bylaws <br>
> (and you can read about that separately).<br>
><br>
><br>
> What does ICANN do? It “pauses” its consideration
of what it has <br>
> failed to act on in retaliation against my
company thereby compounding <br>
> the original issue. In other words, we complained
ICANN was moving to <br>
> slow in our request for the assignment of a TLD
Agreement - and that <br>
> was a violation of the Bylaws. ICANN has
responded by stating that it <br>
> now needs to halt all consideration of the
assignment request because <br>
> we filed the Reconsideration Action in order to
investigate the basis <br>
> of our claims that it was moving too slow.<br>
><br>
><br>
> ———————<br>
><br>
><br>
> There will be a follow up post on why our initial
request for urgent <br>
> reconsideration was denied. In short, ICANN has
taken the position that:<br>
><br>
><br>
> A). Only ICANN Board Action can be challenged on
an Urgent Basis. <br>
> ICANN staff Action or inaction may not be.<br>
><br>
><br>
> B). And ICANN Board Inaction cannot be challenged
where the basis for <br>
> the “Inaction” is ICANN’s failure to pass a Board
Resolution. In other <br>
> words, if you are angry at the Board for not
passing a resolution, you <br>
> cannot file an urgent reconsideration
request…..why…..because in order <br>
> to have an urgent Reconsideration Request, there
needs to be an actual <br>
> Board Resolution. Thus, if the board fails to
pass a resolution, by <br>
> definition, there is no resolution on which to
basis the urgent action.<br>
><br>
><br>
> ————-<br>
><br>
> This case also covers ICANN’s misguided fight
against the blockchain. <br>
> Although the request to assign .hiphop has
nothing to do with the <br>
> blockchain, ICANN has decided (wrongfully) that
it does.<br>
><br>
><br>
> ——————<br>
><br>
><br>
> If you want to cover any of this in an open
session, I am more than <br>
> happy to discuss. I believe all of this should
be done in the open <br>
> and if ICANN Org is not going to be completely
open and transparent, <br>
> then there is no reason we cannot be.<br>
><br>
><br>
> Sincerely,<br>
><br>
><br>
><br>
> Jeffrey J. Neuman<br>
> Founder & CEO<br>
> JJN Solutions, LLC<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Jeff@JJNSolutions.com">Jeff@JJNSolutions.com</a><br>
> +1.202.549.5079<br>
> <a class="moz-txt-link-freetext" href="Http://www.jjnsolutions.com">Http://www.jjnsolutions.com</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> At-Large mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a><br>
> <a
href="https://atlarge-lists.icann.org/mailman/listinfo/at-large"
moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
><br>
> At-Large Official Site: <a
href="http://atlarge.icann.org"
moz-do-not-send="true">http://atlarge.icann.org</a><br>
> _______________________________________________<br>
> By submitting your personal data, you consent to
the processing of your personal data for purposes of
subscribing to this mailing list accordance with the
ICANN Privacy Policy (<a
href="https://www.icann.org/privacy/policy"
moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos"
moz-do-not-send="true">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your
membership status or configuration, including
unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation),
and so on.<br>
<br>
<br>
_______________________________________________<br>
At-Large mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a><br>
<a
href="https://atlarge-lists.icann.org/mailman/listinfo/at-large"
moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a
href="http://atlarge.icann.org"
moz-do-not-send="true">http://atlarge.icann.org</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the
processing of your personal data for purposes of
subscribing to this mailing list accordance with the
ICANN Privacy Policy (<a
href="https://www.icann.org/privacy/policy"
moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos"
moz-do-not-send="true">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your
membership status or configuration, including
unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation),
and so on.</div>
</span></font></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
At-Large mailing list
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/at-large">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a class="moz-txt-link-freetext" href="http://atlarge.icann.org">http://atlarge.icann.org</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
</body>
</html>