Statements by Our Constituency

The ISPCP develops statements, position papers and working documents through a process of internal consensus building. Very often an individual member of the constituency offers (or, is assigned) to draft an initial version of an ISPCP statement. This statement is then posted for others in the ISPCP to comment upon. Very often these comments are not posted to the public ISPCP mailing list. Instead, the author completing the draft incorporates the comments from individuals into subsequent drafts. A final draft is then posted for comment. If no comments or objections are heard within a reasonable period of time, the draft is considered a consensus position of the Constituency.

The Constituency drafts statements in response to policy issues within ICANN, in response to external organizations requests for input, and in other settings (notably, during ICANN public meetings).

ISPCP Constituency Statements 2007

ISPCP Statement on the Staff Report concerning whois Implementation: This statement was prepared in response to the October 2007 Staff report on whois. The ISPCP statement reiterates the concerns that the ISP community has with the OPOC proposal for reforming whois.

ISPCP Constituency Statements 2006

ISPCP Statement on the Introduction of New gTLDs: This consensus statement from January 2006, is the ISPCP's most recent position on the Introduction of new gTLDs.
Comments to the US Department of Commerce on ICANN Contract Renewal: During the Summer of 2006 the US Government's Department of Commerce requested comments regarding the renewal of ICANN's contract with the NTIA. The ISPCP was one of the ICANN Constituencies that drafted and submitted comments.
ISPCP Statement on Registry Contract Policy: In June of 2006, the gNSO considered registry contract policy and its implications. The ISPCP participated in the policy development process and submitted this consensus statement to the gNSO Council.
ISPCP Statement on the Proposed Verisign Settlement: In March of 2006, ICANN requested comments on a proposed settlement of lawsuits between Verisign and ICANN. The settlements proposed were complicated and dominated much of the discussion at the Wellington ICANN meetings. THe ISPCP prepared a consensus statement which was read to the Board of Directors at the Wellington ICANN meeting.
Response to "Fact Checking" in LSE Report on gNSO Review: The ISPCP prepared a response to the limited section of the eventual LSE report. The ISPCP was presented with sonly those sections directly mentioning the constituency, rather than seeing them in the context of the entire report. The ISPCP prepared a response to the LSE on this and made concrete recommendations to improve the quality of the report and the LSE's understanding of the operation of the Constituency. The LSE responded to the ISPCP constituency's suggestions with a matrix indicating their understanding of the proposed changes.

Archive of Earlier Statements and Position Papers

ISPCP Statement to Combined whois Task Force - July 2005: In July 2005, the ISPCP provided input to the, then, three task forces that made up the gNSO's work on whois. This is a combined statement that addresses conflict between contractual agreements and national law and whois and privacy.
ISPCP Statement in Luxembourg ICANN Public Forum on ICANN's First Strategic Plan - July 2005: This is the consensus statement of the ISPCP on the topic of the first strategic plan developed by ICANN staff in the Spring of 2005. The ISPCP objected to a variety of the provisions of the strategic plan as well as the process used to develop the plan. This statement was read at the Public Forum during the Luxembourg ICANN meeting in July 2005.