April 2013 - council - lists.icann.org

DRAFT text of letter from Council to Board RE: singular and plural new gTLD applications
by john＠crediblecontext.com April 11, 2013

April 11, 2013

All, Here is my take on the text of a letter from Jonathan to Steve on the subject of singular and plural new gTLD applications as we agreed ought to be written and sent. Cheers, Berard In the course of our meetings this week in Beijing, we have heard and share the concerns expressed about the undesirable consequences of allowing both singular and plural forms of the same word to be delegated in the news gTLD program. On the basis of policy recommendations of the Council to avoid consumer confusion, this letter asks for clarity on why that policy was, effectively, set aside by the panelist that ICANN enrolled to conduct string similarity tests. Specifically, in the new gTLD Report that was adopted by the GNSO Council was “Recommendation 2 Discussion -- Strings must not be confusingly similar to an existing top-level domain” (see http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm) The effect of singular and plurals is already embedded in practice. Note that WIPO mediation rules include this: “Words used in the singular include the plural and vice versa, as the context may require.” At a minimum, the Council requests fuller disclosure about the process by which the panelist made their determination and why the Board accepted this variance from existing practice and gTLD policy. Greater transparency will help the Council evaluate whether the criteria for string similarity were properly conveyed to the panelist, whether the panelist followed that policy advice and how we can address the concerns of the community.

5 4

Draft Statement for Public Forum
by Jonathan Robinson April 11, 2013

April 11, 2013

Draft Statement for Public Forum: The GNSO Council recently provided advice in response to a letter from the CEO to the effect that an issue being considered was a matter of policy, rather than implementation. It was Staff’s view that the issue was implementation and not policy, and accordingly it was the Staff’s decision to proceed with the first steps of implementation. It is the Council’s firmly held view that when there is not an agreement on whether or not such an item is policy, as in this case, that the Staff must refer back to the Council before proceeding further. Indeed, as a general point, it is the Council’s view that should it provide policy advice to the Staff and/or the Board in the future, then in the event that Staff and/or Board seek to act adverse to the Council’s advice, they should certainly not do so without further reference back to the Council.

8 7

GAC Engagement in GNSO PDP
by Marika Konings April 11, 2013

April 11, 2013

As discussed during the wrap up session today, please find attached an overview of the current engagement opportunities in the GNSO PDP for the GAC as well as the methods currently being used to seek such engagement. I've also added a column that allows for suggestions by the GAC to improvements to the current methods for seeking input being used. With best regards, Marika

1 0

Singular and Plurals
by john＠crediblecontext.com April 11, 2013

April 11, 2013

All, Prompted by a spirited discussion last night at the gala about the Council's standing to move to address the singular/plural strings not flagged by the contention review, Marika has unearthed the Council's previous action on confusingly similar strings in the new gTLD program. Perhaps, in our wrap-up, we can talk a bit about whether this is a matter on which we want to act. Cheers, Berard --------- Original Message ---------Subject: Confusingly similar From: Marika Konings <marika.konings(a)icann.org> Date: 4/10/13 6:36 pm To: "john(a)crediblecontext.com" <john(a)crediblecontext.com> Hi John, The only recommendation that I found related to user confusion in the new gTLD Report that was adopted by the GNSO Council is 'Recommendation 2 Discussion -- Strings must not be confusingly similar to an existing top-level domain' (see http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm) It may be worth checking with some of the others involved at that time (Avri, Jeff?) to see if they have any further specific direction on whether there are other recommendations in relation to this issue as this was discussed long before my time at ICANN. With best regards, Marika

1 0

RE: [council] Draft Statement for Public Forum
by Alan Greenberg April 11, 2013

April 11, 2013

If you go with some variation of Jeff's version, the word "it" in the first sentence should be canged to "the GNSO" or "the GNSO COuncil". as it stands it refers back to the previous noun which is the Board. Alan At 10/04/2013 11:19 AM, Neuman, Jeff wrote: >Some revisions: > > >The GNSO Council would like to remind the ICANN staff and Board that >it is the only entity charged with policy development and providing >recommendations to the Board on substantive policies relating to >generic top level domains. The GNSO Council recently provided advice >in response to a letter from the CEO to the effect that an issue >being considered was a matter of policy, rather than implementation. >It was Staff's view that the issue was implementation and not >policy, and accordingly it was the Staff's decision to proceed with >implementation of what the majority of the Council believed was >policy. It is the Council's firmly held view that when there is not >an agreement on whether or not such an item is policy, as in this >case, that the Staff and/or the ICANN Board must refer back to the >Council before proceeding further. > >Indeed, as a general point, it is the Council's view that should it >provide policy advice to the Staff and/or the Board in the future, >then in the event that Staff and/or Board seek to act in a manner >that is not consistent with the Council's advice, then the Staff >and/or Board must consult with the GNSO Council, explain the >rationale behind its decision, and allow the Council, at a minimum, >to respond to the Staff or Board's decision. > > > >Jeffrey J. Neuman >Neustar, Inc. / Vice President, Business Affairs > >From: owner-council(a)gnso.icann.org >[mailto:owner-council@gnso.icann.org] On Behalf Of Jonathan Robinson >Sent: Wednesday, April 10, 2013 6:54 PM >To: GNSO Council List >Subject: [council] Draft Statement for Public Forum > > >Draft Statement for Public Forum: > >The GNSO Council recently provided advice in response to a letter >from the CEO to the effect that an issue being considered was a >matter of policy, rather than implementation. It was Staff's view >that the issue was implementation and not policy, and accordingly it >was the Staff's decision to proceed with the first steps of >implementation. It is the Council's firmly held view that when there >is not an agreement on whether or not such an item is policy, as in >this case, that the Staff must refer back to the Council before >proceeding further. > >Indeed, as a general point, it is the Council's view that should it >provide policy advice to the Staff and/or the Board in the future, >then in the event that Staff and/or Board seek to act adverse to the >Council's advice, they should certainly not do so without further >reference back to the Council.

1 0

Transcriptions posted: GNSO Weekend Working Sessions in Beijing
by Glen de Saint Géry April 10, 2013

April 10, 2013

Dear All, Please note that most of the transcriptions of the GNSO Weekend Working Sessions in Beijing are posted on page http://gnso.icann.org/en/group-activities/calendar#apr Remaining transcriptions will be posted when available. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

FW: GNSO Council Abstention Notification Form [#117]
by Glen de Saint Géry April 10, 2013

April 10, 2013

FYI Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/> From: ICANN [mailto:no-reply@wufoo.com] Sent: lundi 1 avril 2013 10:39 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#117] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Sunday, March 31, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Temporary Alternate Reason(s) for or condition(s) leading to the remedy: * Magaly Pazello will be absent at the April 2013 GNSO Council Meeting in Beijing. Brenden Kuerbis will serve as Magaly's Temporary Alternate in Beijing. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Any and all Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Saturday, April 13, 2013 Please identify the individual (cannot be a current GNSO Councilor) who will serve as the abstaining Councilor's Temporary Alternate. [Note: if not already published and available, a short bio and Statement/Disclosure of Interest should be prepared by the Temporary Alternate and delivered to the GNSO Secretariat in advance of any discussion or voting scheduled to take place]. * Brenden Kuerbis Temporary Alternate Email Address: * bkuerbis(a)internetgovernance.org<mailto:bkuerbis@internetgovernance.org>

1 0

FW: GNSO Council Abstention Notification Form [#118]
by Glen de Saint Géry April 10, 2013

April 10, 2013

FYI Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/> From: ICANN [mailto:no-reply@wufoo.com] Sent: jeudi 4 avril 2013 04:03 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#118] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustic.org<mailto:robin@ipjustic.org> Date Prepared: * Wednesday, April 3, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Temporary Alternate Reason(s) for or condition(s) leading to the remedy: * Maria Farrell will not be in Beijing for ICANN #46 and therefore Milton Mueller will serve as Maria's Temporary Alternate in Beijing. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * any and all Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Thursday, April 11, 2013 Please identify the individual (cannot be a current GNSO Councilor) who will serve as the abstaining Councilor's Temporary Alternate. [Note: if not already published and available, a short bio and Statement/Disclosure of Interest should be prepared by the Temporary Alternate and delivered to the GNSO Secretariat in advance of any discussion or voting scheduled to take place]. * Milton Mueller Temporary Alternate Email Address: * Mueller(a)syr.edu<mailto:Mueller@syr.edu>

1 0

Fwd: [PC-NCSG] memory refreshment on telling you circumventing community consensus policy was wrong
by David Cake April 10, 2013

April 10, 2013

Robin asked that this be forwarded to council. Regards David Begin forwarded message: > From: Robin Gross <robin(a)ipjustice.org> > Subject: [PC-NCSG] memory refreshment on telling you circumventing community consensus policy was wrong > Date: 10 April 2013 11:23:43 PM AWST > To: Fadi Chehade <fadi.chehade(a)icann.org> > Cc: NCSG-Policy Policy <PC-NCSG(a)ipjustice.org>, Ray Plzak <plzakr(a)gmail.com>, Steve Crocker <steve(a)shinkuro.com>, Jonathan Robinson <jonathan.robinson(a)ipracon.com> > > Dear Fadi, > > Since you told the GNSO Council on Sunday that no one had ever told you it would be wrong for you to do an end run around community consensus policy by going forward with the TMCH meetings in Brussels (and then LA), I thought I should refresh your memory of at least 2 people who told you that what you were setting out to do was wrong: a Stakeholder Group Chair and a Constituency Chair. Please see the emails below from myself and Bill Drake warning you about this to refresh your memory. > > Because you told the GNSO Council that no one told you it was wrong, I request that my and Bill's emails below should also be forwarded to the GNSO Council to tell our side of the story. > > Thank you, > Robin Gross > > Begin forwarded message: > >> From: Robin Gross <robin(a)ipjustice.org> >> Date: October 26, 2012 5:11:14 PM PDT >> To: Fadi Chehade <fadi.chehade(a)icann.org> >> Cc: William Drake <william.drake(a)uzh.ch> >> Subject: Re: why holding the meeting in Brussels next week to consider unraveling community consensus policy is a really bad idea for ICANN >> >> Dear Fadi, >> >> Thank you for responding to Bill since much of what you say below is exactly the kind of clarification that I am asking for regarding this Brussels meeting. >> >> I am extremely grateful to your commitment to uphold the proper development process and your commitment that the meeting will not re-open previously negotiated GNSO policy. However it is also important to understand that by "reviewing the IPC/BC proposal", the meeting *is* considering re-opening matters that were decided by the GNSO in the STI. So while you may have no intention of over-riding GNSO-approved policy, that is what several of the points of IPC/BC's proposal ask for and apparently it is on the agenda. >> >> Furthermore, every person I have spoken with who knew about this meeting has stated a different understanding of its purpose, another reason a clarification from you to the community would be appropriate. One participant said his understanding was it was to "deal with only TMCH issues," another said it was only "an educational opportunity for ICANN staff to better understand how the technology and encryption work". When you and I spoke, you said it was "resolve IPR and new gtld issues and hammer out a framework for a solution". I understand that the IPC/BC are busy working now in 3 different working groups this week to develop new proposals to present to you next week on matters beyond technical or implementation details, and on both TMCH and URS. Several of these proposals have already been rejected by the community, but be prepared to see them again next week, when NCSG can't be there. >> >> Once this meeting was scheduled, even if only originally for technical implementation white boarding, certain constituencies have seized upon it as an opportunity to hit you with new demands at a time when NCSG will not be there to present the other side of the argument. Without clear parameters placed around this meeting, aggressive lobbyists will use it accordingly, despite the intentions behind the originator that it not turn into a lobby session. >> >> When you say you were inviting the "impacted constituencies" to Brussels, please understand that non-commercial users are every bit as impacted by these rules as the IPC. These rights are two sides of the same coin, and when you give more rights to the IPC, you are taking them away from the general public including noncommercial users -- and a balance must be struck in that bargain. NCSG is every bit as impacted as IPC on the implementation of these rules and should have equal participation rights in the discussion as commercial users. >> >> Unlike the CSG, NCSG operates on a SG-wide basis on policy matters. It is explicitly stated in the NCSG Charter that policy positions are taken by the NCSG Policy Committee, not individual constituencies within the NCSG. So the NCSG Policy Committee is the proper venue to take policy proposals (such as the IPC-BC proposal) to for consideration in the NCSG. I know CSG operates based on constituencies, but NCSG develops policy positions on a SG-level so that difference should be factored in to how one approaches NCSG on policy. >> >> Unfortunately no one in the CSG shared the IPC-BC's proposals with the NCSG Policy Committee, or with the NCUC, and I haven't seen any discussion of it on the NPOC mailing list either, so any CSG commitments to socialize their proposal with the rest of the GNSO are missing some gigantic holes. NCSG only knows about it because you called to tell me about the Brussels meeting and the related 8-point demand letter a couple days ago. Now we are scrambling to respond and will file a formal response early next week, but the community was circumvented and has yet to be approached by the proponents of last week's proposals. >> >> It is unfortunate the Brussels meeting is happening without a balance of participation from all of the impacted stake-holders. And NCSG definitely will take you up on your offer to meet with us separately about these issues and we agree it is only appropriate for an 'equal time meeting' given these circumstances. We can hold your meeting with NCSG in the US, perhaps a couple weeks after after the Brussels meeting? (as soon as possible, but with many people in Baku I know that will be difficult). >> >> I understand that you are not knowingly going into the Brussels meeting intending to change GNSO Policy, but others will, so I hope you will prepare accordingly, including make a clear announcement in advance that changing GNSO-approved-policy is not on the table for Brussels. >> >> Of course I'm available to discuss this matter further at any time and look forward to scheduling the "equal time meeting" for NCSG at your earliest opportunity. Thank you very much. >> >> Best, >> Robin >> >> >> >> On Oct 26, 2012, at 2:37 PM, Fadi Chehade wrote: >> >>> Hi Bill, >>> >>> Good to hear from you. I truly appreciate your comments. Let me clarify. >>> >>> 1. I am the one who called for the meeting. No one lobbied me on this matter. I received a high-level briefing on complex issues and realized I needed to learn more. >>> >>> 2. This is intended to be an informal white board brainstorming session to generate new thinking that advances TMCH discussions. The aim is to generate straw man proposals that can be shared with the broader community for discussion and consideration. >>> >>> 3. The session will include the following items (accorded equal time/focus): >>> • Design implementation solution for trademark registration >>> • Design implementation solution for trademark sunrise management >>> • Design implementation solution for trademark claims management >>> • Review IPC/BC proposal >>> • Review framework for contract with the Clearinghouse providers with the parties in direct operation with the Clearinghouse. The contract will be publicly posted. >>> >>> 4. Given the informality of the session, I asked representatives of the constituencies directly impacted with the implementation and contractual implications of the Clearinghouse to help me develop a proposal. >>> >>> 5. I am personally facilitating the white board discussion (partly to learn and partly to birth a solution design rapidly). >>> >>> 6. On the issue of the RPMs: I wish to assure you that I am extremely respectful of the policy process and I will not come back with a solution that undermines the multi-stakeholder consensus without following proper process. This is my personal commitment to you and to our great community that has labored very hard to reach this point. >>> >>> 7. The new requests from the IPC/BC constituencies have been made public and I wanted to better understand them - so I used the opportunity we were all together to hear them out. I also personally contacted Robin on Skype to invite someone from your constituency on this item of the agenda -- so your community can participate initially and, more importantly, prepare for the public discussion on the matter. Given that the IPC/BC proposal discussion will only occupy a 1/5 of our two days (3 hours), i suggested that your representative can join via video-link from the ICANN office or Skype. Accommodation of time zones is always difficult and the arrival of certain parties is dictating the agenda timing but we will do our best to accommodate time zones of remote participants. I also offered Robin that if you all wished to meet with me first to share your views without the other stakeholders present, that I would be happy to take the time. >>> >>> I hope the above helps clarify my intent and assure you that your input below was helpful and appreciated. I am here at your service to make this a success. >>> >>> Sincerely, >>> Fadi >>> >>> p.s. if helpful, you are welcome to share my clarifications with your colleagues. >>> >>> >>> From: William Drake <william.drake(a)uzh.ch> >>> Date: Thursday, October 25, 2012 6:42 AM >>> To: Fadi Chehade <fadi.chehade(a)icann.org> >>> Cc: "Gross, Robin" <robin(a)ipjustice.org> >>> Subject: Re: [Kabob] why holding the meeting in Brussels next week to consider unraveling community consensus policy is a really bad idea for ICANN >>> >>> Hello Fadi >>> >>> I couldn't agree more with Robin's message. The repeatedly demonstrated penchant of powerful stakeholders to do end runs around the consensus based community processes whenever they don't get their maximum preferred outcomes has been one of the most sustained and pernicious threats to the multi-equal stakeholder model you champion. People who have issues should bring these back to the community processes from which they came, rather than undermine collective trust internally and leave ICANN (rightfully) open to all kinds of accusations externally. I believe the correct way to deal with such ploys would be to simply turn down requests for such meetings and ask for written inputs to which the community can respond asynchronously and in full. >>> >>> Best, >>> >>> Bill >>> >>> >>> On Oct 25, 2012, at 2:28 AM, Robin Gross wrote: >>> >>>> Dear Fadi, >>>> >>>> Thank you for informing me of a possible meeting in Brussels next week to consider re-opening the issues related to trademark protections for new gtlds that were previously agreed to by the entire community. However, NCSG is extremely concerned about the proposed Brussels meeting and I don't believe any compromise hammered out in Brussels next week will withstand any serious public scrutiny. >>>> >>>> Surely we learned something from the bad IRT experience and won't repeat it in Brussels next week with a one-sided, hastily thrown together at the last minute meeting to unravel years of negotiated compromise from many communities, and all to please a single interest. Changes proposed by the BC and IPC include big substantive changes to existing policy, not purely minor implementation details. It would be a huge mistake for ICANN to go ahead with the Brussels meeting next week and subject ICANN to criticism that GNSO policy is again thrown-out by last-minute, end-run lobbying by the strongest army. >>>> >>>> Even if throwing-out GNSO agreed policy is not a concern, the lack of balance among impacted interests of the participants allowed to participate in Brussels, is another concern. Unbalanced inputs obviously lends to unbalanced outcomes. I understand that at least 4 members of the Intellectual Property Constituency plus several more from the Business Constituency will be present in the Brussels meeting to advocate for making these changes to the Applicant Guidebook. One single member from the Non-Commercial Stakeholders Group (NCSG) has been invited to attend -- that is already an imbalance of at least 7 in the CSG to 1 in the NCSG in the make-up of those invited to participate in the discussion over the expansion of rights of those 7 against that 1. 7 vs. 1 is a long way from equality among stakeholders. The lack of equality of participation in Brussels among the interests who negotiated the compromise this meeting is set to unravel is untenable. >>>> >>>> And realistically, without travel support from ICANN, no members of the NCSG will be able to fly to Brussels next week to engage in these negotiations to re-work the rights of all registrants. Unlike the CSG which advocates for commercial industries, NCSG does not have any industry support that will fly NCSG members around the world to represent the rights of noncommercial users in ICANN policy. NCSG is, by definition, non-industry considerations of policy matters, so cannot match participation levels of enormous industries with huge budgets. NCSG's budget is $0 and always has been. No one pays for the public interest perspective to be at the table. Although NCSG represents the interests of all non-commercial users of the Internet, which is everyone at one moment or another of the day, these considerations won't make their way into the final policy because participation is prohibitively expensive for the noncommercial interest. >>>> >>>> It is theoretically possible for someone from NCSG - on the other side of the world from Brussels - to join the meeting via a remote link in the middle of their night in their pajamas, but it is not possible to be effective when your body is in the middle of its night. You've worked at your real job all day and will have to again tomorrow. How to really participate in a meeting in the middle of the night? We can't. Not in a meaningful way. Thus there will be no meaningful participation by even a single NCSG member to represent the views of 1/4 of the GNSO - the part that represents the public interest in ICANN policy. >>>> >>>> Without any meaningful representation from the public interest, or the rights of registrants, or the rights of nom-commercial users, this meeting is entirely one-sided and will be guaranteed to produce a one-sided result. >>>> >>>> NCSG members have expressed concern to me over the lack of any kind of public announcement of this meeting by ICANN so they don't know if they can talk about it publicly and begin to get the public engaged in the discussion. How can we be considering holding a meeting to decide if we throw out years of hard fought compromises without a public announcement that there will be such a meeting and explaining its purpose and who is invited to participate? It is important for ICANN's commitment to transparency that the public be informed of this proposed discussion and its importance to the new gtld process and allowed to react. >>>> >>>> NCSG members are concerned about the lack of clear purpose for this Brussels meeting - what is the agenda and what on the table for discussion? Is a chance to re-argue old policy battles? The GNSO makes policy recommendations. Not a group of trademark attorneys lobbying staff in such a way that no other voice will be heard, ensuring that the GNSO's policy recommendations will be cast aside. The entire GNSO unanimously approved the trademark recommendations in the STI Report - including the BC and IPC. All sectors of the community participated in those working groups and hammered out those compromises. Everyone lost something - that is supposed to be the nature of compromise. The STI work is now regarded as the cross-community poster-child example for how to do it right to achieve a community consensus. We can't throw that result out in favor of the disaster IRT model, a one-sided effort that produced proposals the community soundly rejected and the poster child example for "how NOT to make policy". Surely we have learned from that experience and won't try to reproduce it next week! >>>> >>>> Going forward with the Brussels meeting only creates an incentive, even rewards those stakeholders who abandon their commitments, while punishes those who are willing to honor their commitments. It is so obvious that is a bad path for ICANN to go down - even with the enormous pressure of the trademark lobby. At some point someone at ICANN has to find the strength to tell the trademark industry "enough" to the constant clawing for greater and greater rights at the expense of other legitimate interests. Otherwise there will be no end to the lobbying and constant manipulations. >>>> >>>> I'm not opposed to discussing these issues. But it shouldn't be in Brussels next week in a way that is sure to return a one-sided result. We can hold calls, video meetings, discussions on mailing lists, etc to hash-out any truly non-substantive implementation details. But by its exclusionary design, the Brussels meeting is sure to produce a one-sided result favoring the IPC and excluding the rights of registrants and non-commercial interests including the public interest. It will open a Pandora's box, set the precedent to lobby the CEO for changes to GNSO-agreed-to policy, and subject ICANN to criticism that things haven't really changed as we'd hoped. Let's learn from past mistakes (the IRT) and uphold community-wide consensus policies (the STI). This is a crucial issue for ICANN to get right and show it can follow its own rules and processes in the face of pressure. >>>> >>>> Of course I'm happy to talk with you further about this proposed meeting and will continue to try to find some way to include a noncommercial user in it is some way. I just wanted to share with you the initial feedback I've received from members while we scramble to react to the IPC/BC proposal. Thanks again for alerting NCSG that this meeting had been proposed for next week, but please try to understand why we think it is a bad idea to actually hold this meeting in this way at this time. Thank you. Now back to the World Series. >>>> >>>> All best, >>>> Robin >>>> >>>> >>>> IP JUSTICE >>>> Robin Gross, Executive Director >>>> 1192 Haight Street, San Francisco, CA 94117 USA >>>> p: +1-415-553-6261 f: +1-415-462-6451 >>>> w: http://www.ipjustice.org e: robin(a)ipjustice.org >>>> >> >> >> >> >> IP JUSTICE >> Robin Gross, Executive Director >> 1192 Haight Street, San Francisco, CA 94117 USA >> p: +1-415-553-6261 f: +1-415-462-6451 >> w: http://www.ipjustice.org e: robin(a)ipjustice.org >> >> >> > > > > > IP JUSTICE > Robin Gross, Executive Director > 1192 Haight Street, San Francisco, CA 94117 USA > p: +1-415-553-6261 f: +1-415-462-6451 > w: http://www.ipjustice.org e: robin(a)ipjustice.org > > > > _______________________________________________ > PC-NCSG mailing list > PC-NCSG(a)ipjustice.org > http://mailman.ipjustice.org/listinfo/pc-ncsg

1 0

Agenda for new gTLD Program Committee meetings in Beijing
by Bruce Tonkin April 9, 2013

April 9, 2013

Hello All, I requested that agendas be posted for the meetings of the new gTLD Program Committee this week. They are now posted: From: http://www.icann.org/en/groups/board/documents/agenda-new-gtld-05apr13-en.h… Agenda - 5 April 2013 Main Agenda * Review of staff paper on 'Closed Generics' * Any other business From: http://www.icann.org/en/groups/board/documents/agenda-new-gtld-11apr13-en.h… Agenda 11 April 2013 Consent Agenda: * Approval of Minutes of 1 February 2013 * Approval of Minutes of 2 February 2013 Main Agenda: * Operational Readiness * IGO Protection issues * 'Closed Generics' * New gTLD agreements * Any other business Regards, Bruce Tonkin

1 1