[At-Large] ICANN Accountability Mechanisms
Jeff Neuman
jeff at jjnsolutions.com
Sun Jan 2 22:44:15 UTC 2022
Parminder,
Since I am not one to shy away from a legitimate debate:
1. Perhaps you should read the description of the roles for both the (a) GNSO Liaison to the GAC and the (b) GNSO Liaison to the ODP for subsequent procedures.
* ODP Liaison: https://gnso.icann.org/en/announcements/announcement-31aug21-en.htm
* Liaison to GAC - https://gnso.icann.org/sites/default/files/filefield_48865/request-liaison-gac-30mar16-en.pdf and My latest report - https://gnso.icann.org/sites/default/files/filefield_48865/request-liaison-gac-30mar16-en.pdf
1. Here were my applications to each post:
* Application for GNSO Liaison to GAC (2020): https://community.icann.org/display/GSSC/GAC+Liaison+-+2020?preview=/144376613/146736255/GNSO%20Liaison%20to%20the%20GAC%20Application%20-%20Neum<https://community.icann.org/display/GSSC/GAC+Liaison+-+2020?preview=/144376613/146736255/GNSO%20Liaison%20to%20the%20GAC%20Application%20-%20Neuman.doc>
* ODP (2021): https://community.icann.org/display/GSSC/GNSO+Council+Liaison+to+SubPro+ODP+-+2021?preview=/174456844/175245267/Neuman%20Application.pdf
registry o
More specifically, please take a look at my application for the ODP Liaison at page 8 (which was really page 11 of my application) under number 7. That disclosure was true then and remains true as of today. So although I did not name .hiphop specifically (as I was not allowed to), i do reference that some of my clients are gTLD Registries and Registrars, I am not representing any of them in connection with the next round.
Yes, I forgot to change from SOI with the ALAC and GNSO, and apologize for that. But the decision makers who appointment me to these roles know all of the relevant facts and made their own determination about whether or not there was a conflict.
So, aside from the generalized statement that you believe there is a conflict, can you please point to something specific that has been asked of me, or something that I have actually done where there was a conflict that was not disclosed.
As previously states, both of these positions are voluntary for me and the if the community asks me to step down because of an actual conflict, i would do so. But honestly, I believe that that would be a bigger loss for the community given my knowledge, experience and work already performed in these subject areas.
I am always open for a debate, but facts are important.
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
Jeff at JJNSolutions.com
+1.202.549.5079
Http://www.jjnsolutions.com
________________________________
From: At-Large <at-large-bounces at atlarge-lists.icann.org> on behalf of parminder via At-Large <at-large at atlarge-lists.icann.org>
Sent: Sunday, January 2, 2022 5:57 AM
To: At-Large Worldwide
Subject: Re: [At-Large] ICANN Accountability Mechanisms
On 31/12/21 4:26 am, Jeff Neuman via At-Large wrote:
1. 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.
As I said, this is really funny .. you need to disclose not after your commercial interests are served, but even as you begin to pursue those commercial interests which have a nexus with any public interest position you have or are seeking .. In the public sector, you'd have not just been dismissed, but subject to further serious inquiries and possibly penalties.
1. 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,
This you know is an absolutely meaningless statement in this context.. a red herring that no one is taken in by.
1. 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.
Again, a red herring vis a vis the issue of not disclosing conflict of interest when it was due for disclosure.
1. 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)
It is absolutely astonishing that someone who doesnt make due disclosure of conflict of interest to public interest governance bodies directly related to commerical interests that one is actively pursuing is actually able to declare that he doesnt believe in secrets.
And ah yes, you said if someone believes there is a conflict of interest -- let me be direct - yes, I believe there is a huge and unsustainable conflict in interest Let me know your response to this.
Though , not to be too harsh on you, it this airy, poorly conceived multistakeholderist governance that creates the conditions for such things, and maybe to that extent any particular individuals is less to blame.
Meanwhile, I must also answer a direct question you asked this group -- Yes, I full oppose ICANN being vindictive with someone who has used its accountability mechanisms. Happy to support you on that procedural front.
Best, parminder
1. LOL on 4 months vs 4 years. THe average turnaround time for an assignment request for the big players is less than 60 days.
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
Jeff at JJNSolutions.com<mailto:Jeff at JJNSolutions.com>
+1.202.549.5079
Http://www.jjnsolutions.com
________________________________
From: At-Large <at-large-bounces at atlarge-lists.icann.org><mailto:at-large-bounces at atlarge-lists.icann.org> on behalf of Hank Nussbacher via At-Large <at-large at atlarge-lists.icann.org><mailto:at-large at atlarge-lists.icann.org>
Sent: Thursday, December 30, 2021 1:01:41 PM
To: at-large at atlarge-lists.icann.org<mailto:at-large at atlarge-lists.icann.org> <at-large at atlarge-lists.icann.org><mailto:at-large at atlarge-lists.icann.org>
Subject: Re: [At-Large] ICANN Accountability Mechanisms
On 30/12/2021 17:46, Jeff Neuman via At-Large wrote:
I have no opinion on this matter but have a few newbie questions:
1. Based on https://icannwiki.org/.hiphop - what is the issue with
.hiphop?
2. Based on
https://www.jjnsolutions.com/post/jeffrey-j-neuman-appointed-to-internet-leadership-positions-at-icann-72
isn't it a conflict of interest on your part?
3. Based on
https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only
you state "following ICANN staff inaction (for its over four-month
delay) of its Assignment Request for the .hiphop Registry Agreement." -
based on my experience with ICANN processes, a 4 month delay is a mere
second in ICANN time. I would start complaining only after 4 years.
Regards,
Hank
NB The opinions or lack of opinions expressed above are solely my own
> All,
>
> I thought this was important enough of an issue to be discussed and I
> am happy to answer any questions you may have.
>
> Please
> seehttps://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only
> <https://circleid.com/posts/20211230-icannas-accountability-mechanisms-in-name-only>.
>
>
>
> This article covers ICANN’s taking retaliatory action against a
> company I am involved in for daring to use the Reconsideration
> Process. We alleged ICANN’s inaction was a violation of the Bylaws
> (and you can read about that separately).
>
>
> What does ICANN do? It “pauses” its consideration of what it has
> failed to act on in retaliation against my company thereby compounding
> the original issue. In other words, we complained ICANN was moving to
> slow in our request for the assignment of a TLD Agreement - and that
> was a violation of the Bylaws. ICANN has responded by stating that it
> now needs to halt all consideration of the assignment request because
> we filed the Reconsideration Action in order to investigate the basis
> of our claims that it was moving too slow.
>
>
> ———————
>
>
> There will be a follow up post on why our initial request for urgent
> reconsideration was denied. In short, ICANN has taken the position that:
>
>
> A). Only ICANN Board Action can be challenged on an Urgent Basis.
> ICANN staff Action or inaction may not be.
>
>
> B). And ICANN Board Inaction cannot be challenged where the basis for
> the “Inaction” is ICANN’s failure to pass a Board Resolution. In other
> words, if you are angry at the Board for not passing a resolution, you
> cannot file an urgent reconsideration request…..why…..because in order
> to have an urgent Reconsideration Request, there needs to be an actual
> Board Resolution. Thus, if the board fails to pass a resolution, by
> definition, there is no resolution on which to basis the urgent action.
>
>
> ————-
>
> This case also covers ICANN’s misguided fight against the blockchain.
> Although the request to assign .hiphop has nothing to do with the
> blockchain, ICANN has decided (wrongfully) that it does.
>
>
> ——————
>
>
> If you want to cover any of this in an open session, I am more than
> happy to discuss. I believe all of this should be done in the open
> and if ICANN Org is not going to be completely open and transparent,
> then there is no reason we cannot be.
>
>
> Sincerely,
>
>
>
> Jeffrey J. Neuman
> Founder & CEO
> JJN Solutions, LLC
> Jeff at JJNSolutions.com<mailto:Jeff at JJNSolutions.com>
> +1.202.549.5079
> Http://www.jjnsolutions.com
>
>
>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org<mailto:At-Large at atlarge-lists.icann.org>
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org
> _______________________________________________
> 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.
_______________________________________________
At-Large mailing list
At-Large at atlarge-lists.icann.org<mailto:At-Large at atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.icann.org
_______________________________________________
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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.
_______________________________________________
At-Large mailing list
At-Large at atlarge-lists.icann.org<mailto:At-Large at atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.icann.org
_______________________________________________
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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://atlarge-lists.icann.org/pipermail/at-large/attachments/20220102/c5c18805/attachment-0001.html>
More information about the At-Large
mailing list