1) Your Name:


Jeffrey J. Neuman

Picture/Image:
(Instructions: Click in the field to the right to open up the text input window. Then click the <Insert> menu button, select <Image>, then choose (or browse) to locate an image file (e.g., JPG, PNG, BMP) from your local computer to upload. After insertion, please click on the picture and adjust the size to no larger than 200 pixels).

2) Stakeholder Group:Not Applicable

3) Constituency:

Intellectual Property (IPC)

4) ICANN Affiliation (if not covered by item 2 or 3):


I am also a participant in the Registries Stakeholder Group on behalf of .hiphop and a participant in the At-Large in my personal capacity.

5) Please identify your current employer(s):


JJN Solutions, LLC

6) Please identify your current position(s):


Founder & CEO

7) Please identify the type(s) of work performed:


JJN Solutions provides legal and policy consulting services in the fields of Intellectual Property, Internet Governance, domain name services, cybersecurity, privacy, identity management, and other corporate transactional issues. We may provide such consulting services to Contracted Parties as well as other organizations within the ICANN ecosystem.

8) Please identify your declared country of primary residence (e.g., country to which you pay taxes):


USA

9) Please list any financial relationship beyond de minimis stock ownership you may have with any company that to your knowledge has a financial relationship or contract with ICANN:


I am the Chief Legal Officer and minority owner of Dot Hip Hop, LLC the proposed Assignee for the .hiphop TLD.

10) Do you believe you are participating in the GNSO policy process as a representative of any individual or entity, whether paid or unpaid?

No
If the answer is “Yes,” please provide the name of the represented individual or entity. (If professional ethical obligations prevent you from disclosing this information, please enter "Private"):
11) Please identify any other relevant arrangements, interests, or benefits as requested in the following two questions:

a) Do you have any type of material interest in ICANN GNSO policy development processes and outcomes?


Yes

If the answer is “yes,” please describe the material interest in ICANN GNSO policy development processes and outcomes:


I am an officer of a gTLD Registy. Other than that, I am participating in the IPC and At-Large in my personal capacity.

b) Are there any arrangements/agreements between you and any other group, constituency or person(s) regarding your participation as a work team member?


Yes

If the answer is “yes,” please describe the arrangements/agreements and the name of the group, constituency, or person(s):


I may provide legal and consulting services to various entities within the ICANN ecosystem, but I am not officially representing any one organization in any PDP or ICANN working group.

12) Please identify any Working Groups or other chartered teams in which you are participating (include acronyms, if applicable):


On 21 October 2020, I was appointed by the GNSO to serve as the GNSO Liaison to the GAC.  I was reappointed in October 2021 and September 2022 and my term expires at the annual meeting in 2024.  In addition, I am participating in the Name Collision Analysis Project discussion group, the Rights Protection Phase 1 IRT and the IDN ePDP.   

I also served as the ODP Liaison for SubPro in 2022 and am participating in the Closed Generics discussion in that capacity.  Prior to that I was one of the co-chairs of the SubPro PDP which ran from 2016-2021.  

I previously served in a number of positions in the ICANN community including,  as Chair of the RySG, member and Vice Chair of the GNSO Council (2 terms), Chair of the PDP Working Group (PDP 2.0), a co-chair of the New gTLDs Discussion Group, RySG member of the legal negotiating team for the Registry Agreement, the Intellectual Property IRT (2009), and a number of other ICANN committees and working groups involving rights protection mechanisms, reserved names, the policy-development process, transfers, whois, domian name abuse, and ICANN accountability.



13) Additional Information (optional):


14) Page last revised:


06-Jul-2020


===========================

SOI Template v5 (6 Feb 2014)

  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers