December 2008 - council - lists.icann.org

Notice of Intent to Form Cybersafety Constituency
by Robert Hoggarth March 2, 2009

March 2, 2009

Dear GNSO Council Members; For your information, attached please find a copy of the Notice of Intent to Form a New GNSO Constituency (NOIF) submitted by Cheryl B. Preston of the CP80.org Foundation proposing to form the new Cybersafety Constituency. Board members have also been sent a copy of the document as an FYI. I will also be sending a copy to the constituencies mailing list as an FYI, and we'll be posting the NOIF on the GNSO Improvements Home Page http://gnso.icann.org/en/improvements/. Best regards, Rob Hoggarth +1 424.558.4805

3 5

New gTLD Motion 3 Edits?
by Gomes, Chuck Jan. 7, 2009

Jan. 7, 2009

The following motion was tabled in our 18 Dec 08 Council meeting to allow for some wording edits that a couple people volunteered to submit. This is just a reminder for those who were planning to suggest edits. Chuck Motion 3 (tabled until 8 January meeting) Made by: Chuck Gomes Seconded: Adrain Kinderis Whereas both the GNSO and ccNSO are anticipating implementation of processes to introduce IDN TLDs in 2009, Resolve 1) the GNSO Council strongly believes that neither the New gTLD or ccTLD fast track process should result in IDN TLDs in the root before the other unless both the GNSO and ccNSO so agree, and 2) fast track IDN ccTLDs should not be entered into the root if they do not have an enforceable commitment to do the following as gTLDs must do: i) follow minimal security and stability requirements, IDN Guidelines and IDN standards; ii) pay ICANN fees sufficient to ensure that IDN ccTLDs are fully self-funding and are not cross-subsidized by other ICANN activities.

3 5

FW: [gnso-osc] Motion to Approve OSC Charter
by Gomes, Chuck Dec. 31, 2008

Dec. 31, 2008

I don't think this message ever made it to the Council list so I am resending it. Chuck ________________________________ From: Gomes, Chuck Sent: Tuesday, December 30, 2008 1:43 PM To: Gomes, Chuck; Council GNSO Cc: gnso-osc(a)icann.org; 'Neuman, Jeff' Subject: RE: [gnso-osc] Motion to Approve OSC Charter Please note that the OSC made one substantive change in the membership section of its Charter to improve internal operational efficiencies by expanding the committee to include the Chairs of the various work teams to be created. In the case of the three initial work teams proposed by the OSC (GNSO Operations Work Team, Constituency/Stakeholder Group Operations Work Team and Communications Work Team) the chairs of the three teams would become members of the OSC. While not consenting to be ongoing chairs, three OSC members have volunteered to serve as interim chairs of the three initial work teams until the work teams select their own chair: * GNSO Operations Work Team - Ken Stubbs (RyC) * Constituency/Stakeholder Group Operations Work Team - Olga Cavalli (NomCom Appointee) * Communications Work Team - Mason Cole (RrC) Chuck ________________________________ From: owner-gnso-osc(a)icann.org [mailto:owner-gnso-osc@icann.org] On Behalf Of Gomes, Chuck Sent: Tuesday, December 30, 2008 1:18 PM To: Council GNSO Cc: gnso-osc(a)icann.org Subject: [gnso-osc] Motion to Approve OSC Charter On behalf of the OSC, I am submitting the following motion for approval of the OSC Charter by the Council in its 8 January 2009 meeting. I welcome a second, any friendly amendments and questions. Chuck Gomes Motion to Approve the OSC Charter 30 December 2008 Whereas: * The GNSO Council reviewed and accepted the new GNSO Improvements Implementation Plan <http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-impl ementation-plan-16oct08.pdf> [PDF, 96K] developed by the Planning Team at its 16 October meeting. * That Plan called for the creation of an Operations Steering Committee (OSC) to oversee efforts to enhance the GNSO's structure, constituencies, and communications. * The OSC was formed and held five teleconference meetings and conducted various online discussions as of 30 December 2008. * The OSC reviewed and modified the draft OSC Charter prepared by the GNSO Improvements Planning Team and recommends that the Council approve the revised draft Charter dated 22 Dec 08 and contained at the committee's wiki site at https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_o sc <https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_ osc> . Resolve: * The GNSO Council approves the OSC Charter and directs the OSC to proceed in fulfilling the terms of that Charter.

1 0

FW: Motion to Approve OSC Charter
by Gomes, Chuck Dec. 31, 2008

Dec. 31, 2008

I don't think this message ever made it to the Council list so I am resending it. Chuck ________________________________ From: Gomes, Chuck Sent: Tuesday, December 30, 2008 1:18 PM To: Council GNSO Cc: gnso-osc(a)icann.org Subject: Motion to Approve OSC Charter On behalf of the OSC, I am submitting the following motion for approval of the OSC Charter by the Council in its 8 January 2009 meeting. I welcome a second, any friendly amendments and questions. Chuck Gomes Motion to Approve the OSC Charter 30 December 2008 Whereas: * The GNSO Council reviewed and accepted the new GNSO Improvements Implementation Plan <http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-impl ementation-plan-16oct08.pdf> [PDF, 96K] developed by the Planning Team at its 16 October meeting. * That Plan called for the creation of an Operations Steering Committee (OSC) to oversee efforts to enhance the GNSO's structure, constituencies, and communications. * The OSC was formed and held five teleconference meetings and conducted various online discussions as of 30 December 2008. * The OSC reviewed and modified the draft OSC Charter prepared by the GNSO Improvements Planning Team and recommends that the Council approve the revised draft Charter dated 22 Dec 08 and contained at the committee's wiki site at https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_o sc <https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_ osc> . Resolve: * The GNSO Council approves the OSC Charter and directs the OSC to proceed in fulfilling the terms of that Charter.

1 0

Motion to Approve OSC Charter
by Gomes, Chuck Dec. 31, 2008

Dec. 31, 2008

On behalf of the OSC, I am submitting the following motion for approval of the OSC Charter by the Council in its 8 January 2009 meeting. I welcome a second, any friendly amendments and questions. Chuck Gomes Motion to Approve the OSC Charter 30 December 2008 Whereas: * The GNSO Council reviewed and accepted the new GNSO Improvements Implementation Plan <http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-impl ementation-plan-16oct08.pdf> [PDF, 96K] developed by the Planning Team at its 16 October meeting. * That Plan called for the creation of an Operations Steering Committee (OSC) to oversee efforts to enhance the GNSO's structure, constituencies, and communications. * The OSC was formed and held five teleconference meetings and conducted various online discussions as of 30 December 2008. * The OSC reviewed and modified the draft OSC Charter prepared by the GNSO Improvements Planning Team and recommends that the Council approve the revised draft Charter dated 22 Dec 08 and contained at the committee's wiki site at https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_o sc <https://st.icann.org/icann-osc/index.cgi?operations_steering_committee_ osc> . Resolve: * The GNSO Council approves the OSC Charter and directs the OSC to proceed in fulfilling the terms of that Charter.

2 2

ICANN Board resolution from meeting of 11 Dec 08
by Bruce Tonkin Dec. 26, 2008

Dec. 26, 2008

Hello All, The only adopted Board resolution from the Board teleconference relevant to the GNSO last week was: From: http://www.icann.org/en/minutes/prelim-report-11dec08.htm Role of Individual Users in GNSO - Briefing and Action Approved Resolution Whereas, the Board has received varying recommendations on registrant and user involvement in the GNSO, and the issue of how to incorporate the legitimate interests of individual Internet users in constructive yet non-duplicative ways remains an open issue that affects GNSO restructuring. Resolved, (2008-12-11-02) the Board requests that members of the GNSO community work with members of the ALAC/At-Large community and representatives of potential new "non-commercial" constituencies to jointly develop a recommendation for the composition and organizational structure of a Non-Commercial Stakeholder Group that does not duplicate the ALAC and its supporting structures, yet ensures that the gTLD interests of individual Internet users (along with the broader non-commercial community) are effectively represented within the GNSO. This recommendation should be submitted no later than 24 January 2009 for consideration by the Board. Regards, Bruce Tonkin

6 10

Corrected: US DOC/NTIA comments on new gTLD process
by Alan Greenberg Dec. 26, 2008

Dec. 26, 2008

Sorry - forgot the link - http://forum.icann.org/lists/gtld-guide/msg00175.html. ---------------- If you haven't seen them, the DOC/NTIA and Department of Justice Antitrust Division comments make interesting reading. Alan

5 6

MERRY CHRISTMAS AND HAPPY NEW YEAR
by Anthony Harris Dec. 24, 2008

Dec. 24, 2008

This is to wish you all a very happy holiday season! Tony Harris

1 0

Updated statement of interest
by Glen de Saint Géry Dec. 24, 2008

Dec. 24, 2008

Dear All, Please find Chuck Gomes's updated statement of interest http://gnso.icann.org/council/soi/gomes-soi-23dec08.shtml posted on page http://gnso.icann.org/council/members.shtml Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Updated Statement of Interest
by Gomes, Chuck Dec. 23, 2008

Dec. 23, 2008

Attached and copied below is a revised statement of interest for me. Two changes were made from my previous statement of interest: 1. In the first paragraph, I stated that VeriSign is operator of the .name gTLD whereas previously we were only providing backend registry services for the Global Name Registry. This changed as a result of the VeriSign acquisition of GNR earlier this year. Even though the acquisition was completed some time ago, it should be noted that ICANN has not yet approved the redelegation of .name. 2. I added the last paragraph that says, "VeriSign may apply directly for new gTLDs and also may serve as a registry services provider in support of other applicants for new gTLDs." Chuck Interest Statement from Chuck Gomes for the GNSO RN-WG 23 December 2008 I am Vice President of Policy and Compliance for VeriSign, Inc. VeriSign is the registry operator for the .com, .net and .name gTLDs and also provides backend registry services in support of Employ Media for the .jobs gTLD. VeriSign is also the registry operator for two ccTLDs, .cc for the Cocos and Keelings Islands and .tv for Tuvalu. As an employee who supports VeriSign's naming services business, I do often have access to Registry Sensitive information including information about registrars. With regard to both our gTLD and ccTLD registration services businesses as well as other VeriSign businesses, our customers and business associates have interests in various ICANN policy issues and may be members of other GNSO constituencies and/or supporting organizations. In addition to registry agreements with ICANN for .com and .net, VeriSign also has obligations to the U.S. Department of Commerce through a cooperative agreement that was initiated in 1993 and has been amended many times since then. Those obligations include providing the A and J root servers as well as support to ICANN in implementing changes in the root zone file. As such, VeriSign is a member of the DNS Root Server System Advisory Committee and also works closely with IANA staff in the processing of root zone changes. As a representative elected to the GNSO Council by the unsponsored gTLD registry members of the gTLD Registry Constituency (RyC), I am required by the Constituency's Articles of Operation to represent the views of those members and the full Constituency as applicable, not my own or VeriSign's. In that regard, I will endeavor to always qualify any personal statements as such and will follow-up with the RyC to obtain their position. I own shares of VeriSign stock and hold options to purchase additional shares, but the amount of shares I currently own plus the potential shares I could possibly own if I exercised all options is a miniscule number relative to the total number of VeriSign shares. Regarding the pending introduction of new gTLDs, VeriSign may apply directly for new gTLDs and also may serve as a registry services provider in support of other applicants for new gTLDs.

1 0