<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi Richard,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">per our conversation in today's webinar, please find below the answers I had promised to you questions.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Cheers,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Gonzalo<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In response to expressed concerns about .ORG, Ethos Capital made certain commitments (including limiting annual price increases to no more than 10% per year) that they were prepared to place into their corporate governing documents.
This received negative feedback partly, we think, because it was an obscure mechanism many did not understand, and, we think, because it was possible for Ethos to change their governing documents unilaterally (though not easily). After listening to additional
feedback and concerns, Ethos responded with a different mechanism: Public Interest Commitments (PICs) that will be attached to the .ORG registry agreement and will be legally enforceable and not subject to unilateral modification.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Your analysis of the PICs concluded they are not acceptable to you and you have asked the ISOC Board of Trustees to comment. We hope this message addresses your concerns.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Does the PIC replace the plan for a B-Corp?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Not really. Ethos still intends to work within a Public Benefit Corporation framework and to consider seeking B Corp certification. The specific commitments in the PICs will not be part of the benefit corporation, but the Public Benefit
Corporation will make other additional public benefit commitments. We believe the complaints that the previous approach did not provide enforcement through the ICANN community convinced Ethos that using a PIC mechanism would better address the community’s
concerns. Details about the plans for a Public Benefit Corporation and B Corp certification are best directed to Ethos.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What do the PICs actually say?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It is important to be clear about one detail. In your analysis, section II.A, you describe the ceiling on prices in every year. Ethos is not saying that that prices will rise with that schedule; this simply sets forth maximum prices.
PIR’s experience is that it was not always desirable to raise prices. The other sections of your analysis describe the commitments plainly.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Is Ethos “reneging” on its commitment?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In fact Ethos is responding to the feedback regarding the Public Benefit Corporation approach by putting the commitments into a mechanism that are enforceable by the community, and that cannot be altered by Ethos. Because this changes
the enforcement mechanism, the proposal itself is different.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Ethos is prepared to commit to this framework for 8 years. That is longer than the period of price caps in the only other gTLDs with such a cap, .COM and .NET. The commitment in the PIC is also greater contractual price protection
than what any .ORG registrant has today. As the Internet Society said when we announced the sale, we always believed in the market price mechanism to keep .ORG prices from rising unreasonably, but we are pleased to see Ethos make this offer. Moreover, since
registrants can renew their registrations at current prices for up to 10 years, they can build in protections for themselves that will live longer than the period Ethos is offering and in fact past the end of the life of the current .ORG registry agreement.
Ethos says it is confident that its actions in the 8 years of this commitment will assure people of their desire to be a responsible operator that will not enact wild and indiscriminate price increases, and we believe them.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Is the Stewardship Council effective?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It is hard to understand the complaint that the “concerned communities” were not consulted, since the PIC is a direct result of Ethos listening to and addressing objections to the approach Ethos had previously proposed.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It is true that the Stewardship Council will initially be populated by Ethos, although two of the members will be picked by the Council itself. This is a bootstrapping mechanism, and it is not clear why other mechanisms would be more
legitimate. After that, the Council members must indeed be confirmed by PIR’s Board. It is hard to see how any corporation, including today’s PIR or Internet Society, could agree to give control over certain key policies without board confirmation: it would
violate the duties of the board members.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In your comments, you suggest that only a full algorithm defining how Council members are selected, and how they will consult, would be acceptable. However, the fact that the details are not spelled out gives the Council a great deal
of latitude. They could consult however they wanted, and could select new members in any way they saw fit, thereby allowing this tool to adjust to changing circumstances. You also seem to have preferences about how to define the power of the Council, but
don’t appear to argue for why your approach is better.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In regards to the worry that “applicable law” might not be restricted to US law, that should not be surprising. When PIR does business in Europe, for instance, it is subject to EU law as well as to US law. As an example, PIR must comply
with EU privacy laws that protect EU residents. There is no change in this respect compared to today and it is not acceptable for businesses working internationally to ignore the laws of the countries they do business in.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Will Ethos need to report beyond its PIC reporting commitments?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Your note seems to suggest that there is reporting beyond the commitments made in the PICs that you would like. It is not clear what the desired outcome of the reporting that you want is; but since Ethos is planning to create a Public
Benefit Corporation and seek B-Corp status anyway, the reporting mechanism for such corporations is clearly stated in the governing laws.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">How does enforcement work?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">You are correct that, by moving the commitments from the Public Benefit Corporation to the PIC, the mechanism of enforcement changes. The community was pretty vocal in preferring something attached to ICANN contracts that would be enforceable
by ICANN community members, so that’s what Ethos has done. If the complaint is now that ICANN does not enforce its contracts, then why did people want the ICANN contract to be the mechanism of enforcement in the first place?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What about consultations?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Given that Ethos is listening to its critics and addressing many of their concerns, the claim of non-consultation is odd. The reference to George Sadowsky’s proposed meeting is particularly strange, as it was explicitly not supposed
to be a consultation that would lead to changes (i.e. not a negotiation). It was also not something you were willing to attend and not something that would have qualified as an open consultation.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Conclusion<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">While there might have been a bumpy start, Ethos is listening to the community and squarely addressing many of their concerns. It is also pretty obvious that there are many people who will not accept the transaction regardless of what
commitments are made. <o:p></o:p></p>
<p class="MsoPlainText">Many of our chapters don’t have information on how PIR operates or the Domain Name marketplace. Part of the reason some oppose it is because they don’t like the way the transaction has been handled, and we understand that.
<o:p></o:p></p>
<p class="MsoPlainText">We recognize the importance of having an open dialogue with our community where concerns can be raised and opinions shared. We welcome the diverse range of opinions, but we also want to ensure that everyone understands how this transaction
will help us all continue our work together in support of our common mission. We remain convinced that this transaction will bring long-term value to the Internet Society, the work of our members, and ultimately the Internet.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Richard Hill <rhill@hill-a.ch> <br>
<b>Sent:</b> Tuesday, February 25, 2020 19:44<br>
<b>To:</b> Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>; 'Chapter Delegates' <Chapter-delegates@elists.isoc.org><br>
<b>Subject:</b> RE: Call on 28 February re PIR sale<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Please find below my comparison of Ethos' recently announced ICANN Public<br>
Interest Commitments (PIC) with their previously announced Benefit<br>
Corporation (B-Corp) commitments. <br>
<br>
The Ethos announcement does not state explicitly whether the PIC is<br>
replacing the B-Corp commitments, but, for the reasons given in section<br>
III(a) below, it appears to me that the PIC is intended to replace the<br>
B-Corp commitments. I would appreciate clarification on this point,<br>
because, as explained below, it appears to me that the PIC is walking back<br>
the B-Corp commitment regarding price increases.<br>
<br>
The PIC does have a stronger commitment regarding freedom of speech and<br>
use of data, but it is a process commitment, not a substantive commitment,<br>
and, for the reasons given in section III(b) below, it appears to me to be<br>
an inadequate commitment.<br>
<br>
All things considered, I find that the PIC does not meet my expectations:<br>
it was not consulted with the concerned communities, the price protection<br>
is insufficient, the composition of the Stewardship Council remains<br>
problematic, the powers of the Stewardship Council are inadequate, the<br>
reporting requirements for the new PIR are inadequate, and the enforcement<br>
mechanism (ICANN) is not sufficiently transparent nor strong.<br>
<br>
Therefore, I continue to oppose the proposal to sell PIR/.ORG to Ethos.<br>
<br>
Warning: what follows is long. It is structured as follows:<br>
<br>
I - Benefit Corporation Commitments<br>
II - Public Interest Commitments<br>
III - Comparison of the two commitments<br>
(a) Pricing<br>
(b) Stewardship Council<br>
(c) Reporting<br>
(d) Enforcement<br>
IV - Comments on the press release<br>
V - Pennsylvania Benefit Corporation reporting requirements<br>
<br>
I - Benefit Corporation commitments<br>
Ethos had previously stated that it would incorporate public benefit<br>
commitments in the new PIR's Certificate of Formation as a Pennsylvania<br>
Benefit Corporation (B-Corp). I copy-paste in section V below the<br>
reporting requirements for such a corporation. <br>
<br>
Ethos' statement is at:<br>
<br>
<br>
<a href="https://www.keypointsabout.org/blog/commitments-in-certificate-of-formatio">https://www.keypointsabout.org/blog/commitments-in-certificate-of-formatio</a><br>
n <br>
<br>
The B-Corp commitments can be summarized as follows:<br>
<br>
1) PIR will promote and support the purpose-driven and other organizations<br>
and individuals that use the .ORG top-level by committing to: (a) provide<br>
high-quality domain services and related products and services, (b) found<br>
and support a charitable foundation and (c) promote a culture of<br>
accountability and transparency for the registry, employees and customers.<br>
<br>
2) PIR will not increase annual fees a .ORG domain name by more than 10%<br>
per year on average.<br>
<br>
3) PIR will establish a Stewardship Council from which it will seek<br>
strategic advice and recommendations to help guide PIR management and the<br>
board in considering the interests of .ORG stakeholders. PIR will delegate<br>
to the Stewardship Council rights to oversee and appropriate a portion of<br>
the PIR charitable foundation's funds to finance initiatives undertaken in<br>
support of the .ORG community. <br>
<br>
II - Public Interest Commitments<br>
Ethos has now announced that it will add Public Internet Commitment (PIC)<br>
to the contract between PIR and ICANN. The PIC is at:<br>
<br>
<a href="https://www.keypointsabout.org/s/20200220-PIC.pdf">https://www.keypointsabout.org/s/20200220-PIC.pdf</a>
<br>
<br>
The commitments in the PIC can be summarized as follows:<br>
<br>
A) The annual fees for a .ORG domain name will be capped for eight years,<br>
as follows:<br>
<br>
Maximum price<br>
2019: 9.93<br>
2020: 10.92<br>
2021: 12.02<br>
2022: 13.22<br>
2023: 14.54<br>
2024: 15.99<br>
2025: 17.59<br>
2026: 19.35<br>
2027: 21.29<br>
2028: No cap, that is, no limitation on price increases<br>
<br>
B) There will be a Stewardship Council. No employee, director or member of<br>
PIR shall serve on the Council. The Council shall gave the binding right<br>
to veto modifications<br>
of PIR policies regarding censorship and freedom of expression, and use of<br>
.ORG registrant and user data.<br>
<br>
C) PIR will establish a community enablement fund. Grants from the fund<br>
will be approved by the PIR Board upon recommendation of the Stewardship<br>
Council.<br>
<br>
D) PIR will produce and publish annually a report that assesses its<br>
compliance with A), B), and C) above.<br>
<br>
III - Comparison of the two commitments<br>
The recent Ethos announcement does not explicitly say whether the new PIC<br>
is replacing the previous B-Corp commitment. For the reasons given below,<br>
I suspect that it is.<br>
<br>
a) Pricing<br>
In the B-Corp commitment price increases would be limited to 10% per year,<br>
on average, with no time limitation.<br>
<br>
In the PIC, the price increases are capped until 2027, unlimited after<br>
that.<br>
<br>
So it appears to me that Ethos is reneging its B-Corp commitment and that<br>
price increases may be larger than what it said it would commit to.<br>
<br>
This leads me to believe that the B-Corp commitments have been withdrawn.<br>
<br>
b) Stewardship Council<br>
The Charter of the Stewardship Council is at:<br>
<br>
<br>
<a href="https://www.keypointsabout.org/s/20200220-ORG-Stewardship-Council-Charter.">https://www.keypointsabout.org/s/20200220-ORG-Stewardship-Council-Charter.</a><br>
pdf <br>
<br>
As far as I can tell, there was no consultation with the concerned<br>
communities regarding this charter.<br>
<br>
Responsibility 2 refers to "Recommendwations" [sic] which makes me wonder<br>
whether this document was slapped together in a hurry, without careful<br>
review.<br>
<br>
According to Responsibility 3, the Stewardship Council cannot provide<br>
advice or recommendations regarding day-to-day operational matters,<br>
financial or budgeting matters, or pricing of PIR services.<br>
<br>
From the information provided to date, it appears that the initial members<br>
of the Stewardship Council will be appointed by Ethos (and might include<br>
people such as Vint Cerf or Steve Crocker). The Council will then renew<br>
its own composition as members leave it. This is spelled out in Principle<br>
4: the inaugural Council will consist of 5 members appointed by the PIR<br>
Board (which will be controlled by Ethos) and 2 members nominated by the<br>
PIR Board and a to-be-established Nominating Committee. <br>
<br>
The PIC states that no employee, director or member of PIR shall serve on<br>
the Council. I'm not sure what is meant by "member of PIR", however it<br>
appears that the principals of Ethos, or the owners of the owners of PIR<br>
and/or Ethos could serve on the Council.<br>
<br>
We don't anything more about how the members of the Council will be<br>
selected, nor how they will consult the concerned communities (in<br>
particular the .ORG registrants).<br>
<br>
The PIC gives veto rights to the Stewardship Council with respect to<br>
changes in policies regarding censorship and freedom of expression, and<br>
use of .ORG registrant and user data. But the veto requires a two-thirds<br>
majority of the Council, see Principle 12 of the Council's Charter.<br>
<br>
Note that this is a process commitment: Ethos commits to submit any such<br>
changes to a process, but the changes can take place unless they are<br>
blocked by a two-thirds majority of the Stewardship Council.<br>
<br>
It seems to me that a substantive commitment would have been more<br>
appropriate, something like "PIR will not modify current policies<br>
regarding censorship and freedom of expression, and use of .ORG registrant<br>
and user data."<br>
<br>
The Stewardship Council's veto powers are limited by Principle 12, which<br>
states that PIR and the PIR Board reserve the right at all times in their<br>
sole judgment to take actions consistent with PIR's Anti-Abuse Policy and<br>
to ensure compliance with applicable laws, policies and regulations.<br>
<br>
Note that this clause does not refer to US law. Maybe I'm being paranoid,<br>
but it seems to me that this clause would authorize PIR to, say, revoke<br>
the registration of a domain name for a Chinese entity if the entity had<br>
violated Chinese restrictions on freedom of speech, or violated Russian<br>
obligations to register as a non-profit entity, or violated US sanctions<br>
against Iran, Cuba, Venezuela, etc.<br>
<br>
I conclude that the proposed Stewardship Council is not an effective<br>
mechanism to safeguard the interests of the concerned communities: it has<br>
nothing to say about operational matters or prices, it requires a<br>
two-thirds majority to veto a change in freedom of speech or data<br>
protection policies, and anyway PIR reserves its right to comply with laws<br>
that may be different from US law.<br>
<br>
c) Reporting<br>
Under the B-Corp commitments, PIR would have to publish a pretty<br>
comprehensive annual report, see section V below.<br>
<br>
Under the PIC, PIR only has to report with respect to pricing, changes in<br>
policies, and the community enablement fund.<br>
<br>
d) Enforcement<br>
B-Corp commitments can be enforced in the Pennsylvania courts, where<br>
proceedings are public.<br>
<br>
Enforcement of PIC is up to ICANN, and not all parts of its proceedings<br>
are public.<br>
<br>
I know the PIC, and its enforcement process, fairly well because I was one<br>
of the first PIC DRP panelists. I did not hear any cases: there have been<br>
only two cases to date.<br>
<br>
Here is information on the PIC and its enforcement:<br>
<br>
<a href="https://icannwiki.org/Public_Interest_Commitments">https://icannwiki.org/Public_Interest_Commitments</a>
<br>
<br>
<br>
<a href="https://newgtlds.icann.org/en/applicants/agb/base-agreement-specs-pic-faqs">https://newgtlds.icann.org/en/applicants/agb/base-agreement-specs-pic-faqs</a><br>
<br>
<br>
<a href="https://www.icann.org/resources/pages/picdrp-2014-01-09-en">https://www.icann.org/resources/pages/picdrp-2014-01-09-en</a>
<br>
<br>
As can be seen from the FAQ, the decision of a PICDRP panel is not<br>
binding. It is a recommendation to ICANN, who will then decide what, if<br>
anything, to do about the alleged violation of the PIC. That is, the<br>
PICDRP panel's role is essentially to provide advice to ICANN, who may<br>
(normally will) tell the offending registry to comply with its PIC. If the<br>
offending registry fails to comply ICANN could, as a last resort, revoke<br>
its registry contract.<br>
<br>
It appears to me that enforcement of B-Corp commitments in the<br>
Pennsylvania courts would be preferable to enforcement of PIC through the<br>
ICANN PICDRP.<br>
<br>
<br>
IV - Comments on the press release<br>
Regarding Ethos' announcement, Andrew Sullivan has stated: "They [Ethos]<br>
listened, and responded."<br>
<br>
I disagree. One of the key points that has been made repeatedly by many<br>
critics of the proposed deal is that there was insufficient consultation<br>
with the concerned communities, and that nothing should be cast in stone<br>
until it was consulted with the communities.<br>
<br>
I'm not aware of any consultations prior to Ethos publishing the PIC. <br>
<br>
It's worth recalling that George Sadowsky attempted to organize a<br>
consultation, but that Ethos finally declined, on the grounds that a<br>
weekend-long meeting was not feasible given schedules and other events<br>
already in motion. I infer that given schedules and other events were more<br>
important than the consultation that George was trying to organize. To me,<br>
this provides an unflattering view of the importance that Ethos gives to<br>
hearing the views of the concerned communities.<br>
<br>
Regarding the PIC, Andrew Sullivan has stated: "With this in place, and as<br>
the Internet Society and PIR advance their missions, the Internet will<br>
become stronger, more secure, and more accessible."<br>
<br>
Since the deal in question involves the sale of one gTLD, I fail to see<br>
how it it could make the Internet stronger or more secure. <br>
<br>
Regarding accessibility, the main issue is lack of affordable access in<br>
much of the developing world. <br>
<br>
The reasons for the relatively high cost of access include lack of<br>
competition, lack of infrastructure, and the high cost of international<br>
connectivity. <br>
<br>
I fail to see how moving the PIR/.ORG revenue stream from the non-profit<br>
sector to the private equity sector will make the Internet more<br>
accessible, but perhaps I'm missing something.<br>
<br>
V - Pennsylvania Benefit Corporation reporting requirements<br>
The reporting requirements for Pennsylvania Benefits Corporations are<br>
outlined here:<br>
<br>
<br>
<a href="https://www.dos.pa.gov/BusinessCharities/Business/Resources/Pages/Pennsylv">https://www.dos.pa.gov/BusinessCharities/Business/Resources/Pages/Pennsylv</a><br>
ania-Benefit-Corporation.aspx <br>
<br>
Each year, the benefit corporation must prepare and distribute to its<br>
shareholders an Annual Benefit Report describing its efforts to create<br>
public benefit during the preceding year. The report must be filed with<br>
the Department of State, thus making it a matter of public record. The<br>
report must also be posted on any public website maintained by the<br>
corporation. The fee for this filing is $70. The report must:<br>
<br>
Describe the general public benefit and any specific public benefit<br>
pursued and created during the year and any circumstances that may have<br>
hindered the creation of these benefits;<br>
<br>
Assess the overall social and environmental performance of the benefit<br>
corporation against a third-party standard and state the process and<br>
rationale for selecting the third-party standard;<br>
<br>
Give the name and contact information of the benefit director and the<br>
benefit officer, if any;<br>
<br>
Provide the compensation paid to each director;<br>
<br>
Give the name of each person that owns 5% or more of the outstanding<br>
shares of the benefit corporation; and<br>
<br>
Contain the annual compliance statement of the benefit director<br>
described in Section 3322(c)<br>
<br>
Contain a statement of any connection between the organization that<br>
established the third-party standard and the benefit corporation, or their<br>
directors, officers or any holder of 5% or more of the governance<br>
interests/outstanding shares in either organization, including any<br>
financial or governance relationship which might materially affect the<br>
credibility of the use of the third-party standard<br>
<br>
If the benefit corporation has restricted the powers of the board of<br>
directors, a description of the persons who exercise those powers and of<br>
the benefit director.<o:p></o:p></p>
<div>
<p class="MsoNormal">On February 25, 2020 6:13:19 PM GMT+01:00, Gonzalo Camarillo <<a href="mailto:gonzalo.camarillo@ericsson.com">gonzalo.camarillo@ericsson.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<pre style="margin-bottom:12.0pt">Hi Richard,<br><br>sure, we can talk about all that. Could you please summarize the criticism on the PIC you would like to discuss?<br><br>Cheers,<br><br>Gonzalo<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt">
<pre>-----Original Message-----<br>From: Richard Hill <<a href="mailto:rhill@hill-a.ch">rhill@hill-a.ch</a>><br>Sent: Monday, February 24, 2020 09:17<br>To: Gonzalo Camarillo <<a href="mailto:gonzalo.camarillo@ericsson.com">gonzalo.camarillo@ericsson.com</a>>; 'Chapter<br>Delegates' <<a href="mailto:Chapter-delegates@elists.isoc.org">Chapter-delegates@elists.isoc.org</a>><br>Subject: Call on 28 February re PIR sale<br><br>Dear Gonzalo,<br><br>Would it be possible for you to comment, during the call on 28 February, on<br>the advice that the Chapters Advisory Council has submitted regarding the<br>sale of PIR and the role of Chapters, and also to comment on the criticism<br>that has been posted regarding Ethos' proposed Public Interest<br>Commitments (PIC)?<br><br>Thanks and best,<br>Richard<o:p></o:p></pre>
</blockquote>
<pre style="margin-bottom:12.0pt"><o:p> </o:p></pre>
</blockquote>
</div>
<p class="MsoNormal"><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.<o:p></o:p></p>
</div>
</div>
</body>
</html>