[CPWG] [registration-issues-wg] [GTLD-WG] Brainstorming

[Roberto Gaetano]

Hi Evan.
Good points.
Just one note about the non-profit status. There are very tight requirements, scrutinised by the US IRS. Per had it because all profits were either passed on to a non-profit organization like ISOC or used directly for non-profit activities.
I doubt that the subscriber to an investment fund would ever accept this approach.
For this reason PIR will seek B Corporation certification, that would not make sense for a non-profit.
Cheers,
R

> On 25.11.2019, at 01:35, Evan Leibovitch <evan at telly.org> wrote:
> 
> Recall that PIR has already agonized over the restrictions that it would put on orgs to get special status when it created .NGO/.ONG ... Some people thought that this is what .org should have always been, but this is what we have now. Asking for .org to have rules more stringent than the status quo is problematic.
> 
> IMO. Just keeping the current status as PIR being a nonprofit -- even under Ethos -- would be OK for me. WIthout the nonprofit status the pronouncements made are as useless at the Public Interest Commitments tacked onto new gTLD contracts. They are volunteered and can be casually withdrawn at any time. Who's to say that Ethos won't flip PIR to someone else without even the platitudes currently offered? The only thing that would assure the community that PIR would actually *commit* to being mission driven would be to maintain nonprofit status.
> 
> Now.... to make a point that I've expressed poorly until now.
> 
> What makes the discussion about this SO difficult is that there are actually multiple different issues:
> The rationale for ISOC selling PIR
> Selling PIR to a private equity company that turns it from nonprofit to for-profit
> The start-to-end process, from "do we sell?" to "we've done a contract", done out of sight of ISOC members and chapters as well as ICANN
> and three different stakeholder points if view:
> ISOC members, chapters and other members of its community
> Owners of .org domains
> ICANN At-Large and others who care about this transaction and its consequences on public trust in the DNS etc
> To this end I have taken a stab at an issues matrix which tries to offer the differing perspectives where these issues and stakeholders intersect; it's a Google Doc with access public to anyone with this link <https://docs.google.com/document/d/1LUBb9OGizKB-vhKY5aLWhxvpE5IEyNRJEoXjZULLCqo/edit?usp=sharing>. Comments are enabled but I'll delete anything unsigned.
> 
> Please let me know if you find this useful, even as just a strawman that identifies the complexity of the discussion.
> 
> - Evan
> 
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
> 
> _______________________________________________
> 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._______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
> 
> _______________________________________________
> 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: <http://mm.icann.org/pipermail/cpwg/attachments/20191125/53f36435/attachment-0001.html>