February 2008 - council - lists.icann.org

Interview with Rita
by Avri Doria Feb. 26, 2008

Feb. 26, 2008

Hi, For those, like me, who cannot make the interview with Rita, but who have questions, I suggest that we send Rita our question(s), with a copy to the Council. And then leave it up to Chuck to slot the question in wherever he thinks it fits. Does this seem OK to others? thanks a.

2 1

Rita Rodin's Candidate Statement
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Feb. 25, 2008

Feb. 25, 2008

Dear All, Rita Rodin's candidate statement for the ICANN Board seat 14 is posted on pages: http://gnso.icann.org/index.html http://gnso.icann.org/elections/index.html Rita will be interviewed on Thursday 28 February 2008 at 19:00 UTC. Let me know if you would like the call details to join the call. Thank you very much. Kind regards, Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

RE: [gnso-dt-wg] Rework of motion
by Mike Rodenbaugh Feb. 25, 2008

Feb. 25, 2008

Thanks Liz. In response to this report four months ago, the Council essentially voted to handle these terms of reference itself, rather than form a Task Force to do so. I believe we did this because a majority felt we had enough evidence about the effects, judged that the effects justify measures be taken to impede domain tasting, and had much information about potential impacts of various resolutions but also would get Constituency Impact statements about such potential impacts. We then got those Impact Statements. The Council then voted to have an open, volunteer design team to suggest next steps, and that team unanimously recommended a measure designed to impede domain tasting -- which the Council should be deliberating, if we can get past the process roadblock of the Registries. How did we get here? Here's a brief history of the ICANN process wrt to domain tasting, and specifically wrt to the 'excess delete fee' resolution: PIR request to SSAC in March 2006, http://www.pir.org/PDFs/SSAC-ICANN_ORG_Tasting_3-26-06.pdf Sept. 2006, PIR proposal to implement 'excess delete fee service'. Nov. 2006 the ICANN Board: Resolved, (06.84), the President and the General Counsel are authorized to enter into an amendment of the .ORG Registry Agreement to implement the proposed excess deletion fee service At least five ICANN public meetings and workshops on the domain tasting issue, links to full transcripts of those meeting are at this page, http://public.icann.org/issues/domain-name-tasting: * 27 June 2006: Domain tasting workshop * 6 December 2006: Domain name marketplace. * 25 March 2007: How the Marketplace for Expiring Names Has Changed * 25 March 2007: Domain name secondary market * 24 June 2007: Domain tasting tutorial June 2007, PIR implements excess deletion fee, tasting immediately and drastically reduced in .org June 2007: In response to ALAC request and GNSO vote, ICANN staff prepared an issues paper on domain tasting, which discussed the PIR implementation of the excess delete fee. http://gnso.icann.org/issues/domain-tasting/gnso-domain-tasting-report-14jun 07.pdf. The report also shows the ICANN General Counsel's opinion that policy development wrt to domain tasting is "within scope of the ICANN policy process and within scope of the GNSO." This report also had a public comment period. June 2007, GNSO voted to form a working group to examine the facts and recommend further action, with a report created in October 2007: http://gnso.icann.org/drafts/gnso-domain-tasting-adhoc-outcomes-report-final ..pdf. The working group contained reps from all Constituencies and from other stakeholders. Their consensus report included discussion of excess delete fee (including PIR's implementation), suggestion of it as a potential resolution, and documented the widespread community discussion about it as a resolution. This report included much public input both via an open questionnaire, and also one designed by the Intellectual Property Constituency for trademark owners. October 2007, GNSO voted to move forward with the PDP by requesting Constituency Impact Statements with respect to the information and proposed resolutions contained in the Outcomes report, including the excess delete fee. GNSO rejected option of forming a Task Force, deciding instead that the issue was ripe for Council deliberation and resolution. BC, NCUC, ALAC and Registrars Constituency each give view on excess delete fees. The statements are incorporated in the "Initial Report" http://gnso.icann.org/issues/domain-tasting/gnso-initial-report-domain-tasti ng-07jan08.pdf, which had a public comment period. November 2007, GNSO voted to form a 'design team' to review all the reports and public comments, and recommend next steps in the PDP. January 2008, Design Team of 3 Councilors and ALAC Advisor unanimously agreed on proposed Council resolution recommending excess delete fee for all registries with an AGP, which is the same proposal put forth by Afilias and Neustar for .info and .biz. The Design Team finds this the most reasonable and potentially achievable compromise among the various options. January 29, 2008, ICANN Board suggests action to address domain tasting: http://www.icann.org/announcements/announcement-29jan08.htm." The Internet Corporation for Assigned Names and Numbers is looking to effectively end domain tasting with a proposal to start charging the annual ICANN fee on registrar domain registrations." It is unclear whether this will actually become part of the ICANN budget beginning July, 2008. February 2008, Registries filibuster substantive Council deliberation by arguing there has not been enough process to address the proposed Council resolution. Registry Constituency representative argues that any Council resolution could not become Consensus Policy unless the Registries Constituency agrees to the resolution. Respectfully submitted, Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Liz Gasster Sent: Sunday, February 24, 2008 5:47 PM To: Gomes, Chuck; Rosette, Kristina; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion All, The three draft terms of reference that were suggested in the October 2007 Domain Tasting Outcomes Report that Chuck refers to below are copied for your reference. Liz 1. Review and assess all the effects of domain tasting activities that have been identified. 2. Judge whether the overall effects justify measures to be taken to impede domain tasting. 3. If the answer to 2 is affirmative, then consider the potential impacts of various measures on the Constituencies, and recommend measures designed to impede domain tasting. -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Gomes, Chuck Sent: Sunday, February 24, 2008 12:57 PM To: Rosette, Kristina; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Thanks for the questions Kristina. I attempted to answer them as best I can below with the understanding that what I say is my personal interpretation because I have not cleared it with the RyC. I certainly encourage Jeff as the RyC representative on this WG to confirm or correct anything I say, and I of course will communicate any differences of opinion from RyC members if and when I become aware of any. Chuck -----Original Message----- From: Rosette, Kristina [mailto:krosette@cov.com] Sent: Sunday, February 24, 2008 1:12 PM To: Gomes, Chuck; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Chuck, It would be helpful to me (and perhaps others) if you could provide some clarification of one point made in the RyC constituency statement. Paragraph 3.1.2 states that "The RyC believes that a one-size-fits-all approach will not work for all registries and sponsors. The RyC therefore suggests that consideration of variations of this approach should be evaluated by individual registries and sponsors. It should also be noted that what is successful for one gTLD may not have the same results in another gTLD." Paragraph 3.2.1 indicates that this position has supermajority support within the RYC. I read this paragraph to mean that the RyC will not support a "one-size-fits-all approach." Is that interpretation correct? CG: Yes, but it may be helpful to qualify what I believe the position means. I attempt that below. If it is, I am having difficulty understanding how it is possible for the design team (or the Council, for that matter) to develop any policy, which will inherently be a one-size-fits-all approach", that will have any support from the RyC. (I am excluding "policies" that recommend no action be taken or recommend the status quo, namely, each registry do its own thing.) Is it possible? If so, I would appreciate some clarification. CG: If a policy is proposed that does not take into consideration the differences among registries and sponsors with regard to the AGP and the impacts the proposed policy might have on various registries and sponsors, then it is highly unlikely that the RyC would support the proposed policy. In my opinion though, that does not mean that the RyC would oppose any proposed policy. What I believe we are saying is that any such policy needs to adequately deal with any applicable differences that exist among registries and sponsors. In other words, the policy development process needs to attempt to address any applicable differences that exist among registries and sponsors. If that is done in a reasonable manner, then I do not think that the RyC would oppose any resulting policy recommendations on the basis of the issue of 'one size fits all'. The fact that this did not happen yet should not be taken as a criticism of the 'design team', because I do not believe they were tasked with developing policy but rather, as Avri pointed out, to suggest next steps forward. But, to the extent that the 'design team' takes on a broader role that includes proposing a possible policy, then it is essential that the one-size fits all issue be dealt with. This to me would best be handled by an open working group with clear terms of reference that delineate tasks as those suggested in the Domain Tasting Outcomes Report. Many thanks. K -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Gomes, Chuck Sent: Saturday, February 23, 2008 8:51 AM To: Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion A few corrections and clarifications below Mike. Chuck -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Mike Rodenbaugh Sent: Friday, February 22, 2008 3:34 PM To: gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion I would prefer to vote on the proposal ASAP. Council has already decided not to have a Task Force, and had commissioned an open WG already, and has taken Constituency Impact Statements. This proposal has been thoroughly vetted through open process. I see no hope of coming to a solution that RyC will accept, because their position appears to be that ICANN can't make policy that binds them, unless they agree. And they haven't agreed to any policy development the last 3 years, except for newTLDs which will make them more money and Inter-Registrar Transfer which will save them money via less disputes. Seems to me that RyC is again trying to delay policy development for as long as they can, by throwing up bogus arguments about lack of process. CG: The open WG was an information gathering WG. The impact statements were not based on any policy recommendations developed by a PDP. What proposal was "thoroughly vetted"? Certainly not the proposal in the motion. While we won't have a SuperMajority (if indeed we even have a majority), it will be clear why, and the Board can do as it likes. And we can move onto other issues as we will have done our job. I simply have no confidence that 3 more months will produce anything different in the situation we have today. I have lost patience on this issue because the practice is so facially wrong and has garnered almost unanimous antipathy from the non-contracting community, yet Council have spun our wheels endlessly for about a year now, fruitlessly trying to do anything about it. Process like this gives ICANN a bad name. CG: Whether or not you think additional time will produce what you want is not the issue. The issue is whether or not we have a legitimate policy development process. -Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Neuman, Jeff Sent: Friday, February 22, 2008 12:04 PM To: Avri Doria; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Avri, Is your question to the ICANN GC on whether the ICANN Board can act? If that is the question, the answer is yes. If your question is whether the ICANN's Board decision is binding on the registries, that is a totally separate issue. Irrespective of the answer, whether we call it a new PDP or jus opening a new WG, I guess I am neutral. I would just clarify that rather than having the WG determine a solution, in order to narrow that down, and speed up the times lines, I would propose that the WG just focus on the solution presented by the Design Team which I believe is the NeuStar/Afilias solution (unless people think that would be too narrow). Design Team -- Does this sound like a way forward? If so, I could take the substance of the motion that has been reworked (minus all of the Whereas clauses) and try to come up with a draft charter and proposed time-line to send to the group. (To that end, if someone has a form charter to use as a template, that would help). If not, I am sure I can wing it. Jeffrey J. Neuman, Esq. Sr. Director, Law, Advanced Services & Business Development NeuStar, Inc. e-mail: Jeff.Neuman(a)Neustar.us -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Avri Doria Sent: Friday, February 22, 2008 2:50 PM To: gnso-dt-wg(a)icann.org Subject: Re: [gnso-dt-wg] Rework of motion Hi, Two quick comments: - The issue of whether this would or would not be a consensus policy is one for legal counsel. I can certainly check with legal counsel to find out the status of a decision according to 13f. - We are already in a PDP. As opposed to trying to begin yet another PDP, I would would think a suggestion for an open WG to come up with a solution that could get a supermajority would be a more feasible route. Assuming others in the DT and the council, agree with you. If this is the path the DT suggests, it would be good for the DT to propose the charter and timings. a. On 22 Feb 2008, at 13:45, Neuman, Jeff wrote: > > A couple of notes: > > 1. A majority of the Council as opposed to Supermajority is not > "deemed to reflect the view of the Council". See Section 12. > > 2. Yes, the Board can act, but again, that Board decision, in my view > (and in the view of the other registries) would not be binding on the > gTLD Registry Operators because that would not be viewed as "consensus > of Internet stakeholders". After all, if a majority is not even > deemed to reflect the view of the Council, then how can it represent a > Consensus of Internet stakeholder. > > 3. The reason I am using the phrase "consensus of Internet > stakeholders" is because that is the phrase that is used in the gTLD > contracts. See below which is taken from Section 3.1(b)(iv) of the > .com agreement (See > http://www.icann.org/tlds/agreements/verisign/registry-agmt-com-01mar06 > . > htm) which states: > > "Consensus Policies and the procedures by which they are developed > shall be designed to produce, to the extent possible, a consensus of > Internet stakeholders, including the operators of gTLDs. Consensus > Policies shall relate to one or more of the following: (1) issues for > which uniform or coordinated resolution is reasonably necessary to > facilitate interoperability, Security and/or Stability of the Internet > or DNS; > (2) > functional and performance specifications for the provision of > Registry Services (as defined in Section 3.1(d)(iii) below); (3) > Security and Stability of the registry database for the TLD; (4) > registry policies reasonably necessary to implement Consensus Policies > relating to registry operations or registrars; or (5) resolution of > disputes regarding the registration of domain names (as opposed to the > use of such domain names). Such categories of issues referred to in > the preceding sentence shall include, without limitation: > > Particularly important is the phrase "including the operators of > gTLDs". > Now before you try to argue that it is modified by the phrase "to the > extent possible", let me state that the following: > > 1. "To the extent possible" does not mean that if the registries are > on the losing side of the vote it is not "possible" to achieve gTLD > operator support for a proposal on domain tasting. > > 2. The gTLD Registries have indicated on a number of occasions that > we do believe a proposal to eliminate tasting (in TLDs where tasting > has > occurred) can garner the registry operators support. We are committed > to working with you to achieve that. We just need to find a solution > that takes into consideration the differences of each of the > registries. > > Now if we are done talking about process, lets get down to business: > > 1. There is a proposed solution on the table; namely I believe the > NeuStar/Afilias proposal (which by the way should be officially posted > for public comment today). > > 2. My recommendation is to take those proposals, get the GNSO Council > to initiate a PDP, and launch a Task Force (or Working Group) open to > the community whose sole purpose and charter is to study the > implications of this proposal. I would gladly help ICANN staff in the > drafting of that charter. > > 3. We follow the strict timing in the Bylaws on the formation of the > Task Force/Working Group, elect a chair, and get constituency > statements getting them to focus solely on the proposal. This should > be very easy, quick and painless. > > 4. Have a Task Force report that analyzes the constituency statements > and public input and modifies the proposal (if necessary). Put that > out for comment and draft the final report (all included in the > Bylaws). > > If we follow the strict timing in the Bylaws, which I believe we can, > we can have this done, wrapped up and to the Board within 90 days and > still before the Paris meeting. > > This will require some diligent efforts, but let's show that this is > possible. > > > Jeffrey J. Neuman, Esq. > Sr. Director, Law, Advanced Services & > > Business Development > > NeuStar, Inc. > e-mail: Jeff.Neuman(a)Neustar.us > > > -----Original Message----- > From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] > On > Behalf Of Avri Doria > Sent: Friday, February 22, 2008 12:15 PM > To: gnso-dt-wg(a)icann.org > Subject: Re: [gnso-dt-wg] Rework of motion > > > > On 22 Feb 2008, at 11:41, Rosette, Kristina wrote: > >> eff, good question. I'd appreciate clarification of that, too, to >> make sure we're all on the same page. The transcripts of the GNSO >> Council meeting and Thursday wrap-up are far from crystal clear. As >> for your other point, I had understood that the bylaws do not require >> supermajority support of Council before Board can vote. If there's >> language elsewhere that controls, I'd appreciate if you would point >> me in the right direction so that I'm working from the same baseline. > > Hi, > > As I read the by-laws, appended below, the Council does not need to > achieve a supermajority in order to forward on a decision (note 11b). > A non supermajority view, though, is treated differently by the board > (13b vs. 13f). > > In terms of this DT, the purpose is still to present a way forward for > the council to discuss. That can be a motion, a motion plus update of > constituency statements, or a WG charter. The motion can be based on > the reworked version Alan has presented, or another motion all > together, e.g. the elimination of a required AGP as was suggested by > many of the comments or some other motion. > > I think it is best if the way forward leads to a supermajority > position. If we can't get a motion that would be able to garner > supermajority support, then perhaps we need to do more work and a WG > charter might be the right way forward. > > a. > > > from the by-laws > ----------------------- > > 11. Council Report to the Board > > The Staff Manager will be present at the final meeting of the Council, > and will have five (5) calendar days after the meeting to incorporate > the views of the Council into a report to be submitted to the Board > (the "Board Report"). The Board Report must contain at least the > following: > > a. A clear statement of any Supermajority Vote recommendation of > the Council; > > b. If a Supermajority Vote was not reached, a clear statement of > all positions held by Council members. Each statement should clearly > indicate (i) the reasons underlying each position and (ii) the > constituency(ies) that held the position; > > c. An analysis of how the issue would affect each constituency, > including any financial impact on the constituency; > > d. An analysis of the period of time that would likely be > necessary to implement the policy; > > e. The advice of any outside advisors relied upon, which should be > accompanied by a detailed statement of the advisor's (i) > qualifications and relevant experience; and (ii) potential conflicts > of interest; > > f. The Final Report submitted to the Council; and > > g. A copy of the minutes of the Council deliberation on the policy > issue, including the all opinions expressed during such deliberation, > accompanied by a description of who expressed such opinions. > > 12. Agreement of the Council > > A Supermajority Vote of the Council members will be deemed to reflect > the view of the Council, and may be conveyed to the Board as the > Council's recommendation. Abstentions shall not be permitted; thus all > Council members must cast a vote unless they identify a financial > interest in the outcome of the policy issue. Notwithstanding the > foregoing, as set forth above, all viewpoints expressed by Council > members during the PDP must be included in the Board Report. > > 13. Board Vote > > a. The Board will meet to discuss the GNSO Council recommendation > as soon as feasible after receipt of the Board Report from the Staff > Manager. > > b. In the event that the Council reached a Supermajority Vote, the > Board shall adopt the policy according to the Council Supermajority > Vote recommendation unless by a vote of more than sixty- six (66%) > percent of the Board determines that such policy is not in the best > interests of the ICANN community or ICANN. > > c. In the event that the Board determines not to act in accordance > with the Council Supermajority Vote recommendation, the Board shall > (i) articulate the reasons for its determination in a report to the > Council (the "Board Statement"); and (ii) submit the Board Statement > to the Council. > > d. The Council shall review the Board Statement for discussion > with the Board within twenty (20) calendar days after the Council's > receipt of the Board Statement. The Board shall determine the method > (e.g., by teleconference, e-mail, or otherwise) by which the Council > and Board will discuss the Board Statement. > > e. At the conclusion of the Council and Board discussions, the > Council shall meet to affirm or modify its recommendation, and > communicate that conclusion (the "Supplemental Recommendation") to the > Board, including an explanation for its current recommendation. In the > event that the Council is able to reach a Supermajority Vote on the > Supplemental Recommendation, the Board shall adopt the recommendation > unless more than sixty-six (66%) percent of the Board determines that > such policy is not in the interests of the ICANN community or ICANN. > > f. In any case in which the Council is not able to reach > Supermajority, a majority vote of the Board will be sufficient to act. > > g. When a final decision on a GNSO Council Recommendation or > Supplemental Recommendation is timely, the Board shall take a > preliminary vote and, where practicable, will publish a tentative > decision that allows for a ten (10) day period of public comment prior > to a final decision by the Board. > > >

2 1

FW: [gnso-dt-wg] Rework of motion
by Mike Rodenbaugh Feb. 25, 2008

Feb. 25, 2008

Rita, I, and I suspect others on the Council, would appreciate your view of the position stated below by Jeff Neuman, as you are an exceptional attorney who assisted in drafting the PDP provisions, have been nominated by the Registry Constituency, and are a member of ICANN's Board Governance Committee (including GNSO Reform subcommittee) and the Board's Executive Committee. Oh yes, and we are all asked to vote on your reappointment very shortly :) Thanks, Mike Rodenbaugh -----Original Message----- From: Mike Rodenbaugh [mailto:mxrodenbaugh@yahoo.com] Sent: Sunday, February 24, 2008 9:11 PM To: 'Council GNSO' Subject: FW: [gnso-dt-wg] Rework of motion I think it important for the entire Council to see the reasoning of the Registry Constituency representative to the domain tasting 'design team', as it applies to any policy development work of the Council. Essentially I think this boils down to a position that the ICANN Board cannot enforce any Consensus Policy unless the Registry Constituency has agreed to it. This came as a surprise to me. Perhaps I am misinterpreting and will be corrected by Jeff or another RyC representative. Perhaps we should have an opinion of ICANN Counsel on this issue as well? -Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Neuman, Jeff Sent: Friday, February 22, 2008 10:45 AM To: Avri Doria; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion A couple of notes: 1. A majority of the Council as opposed to Supermajority is not "deemed to reflect the view of the Council". See Section 12. 2. Yes, the Board can act, but again, that Board decision, in my view (and in the view of the other registries) would not be binding on the gTLD Registry Operators because that would not be viewed as "consensus of Internet stakeholders". After all, if a majority is not even deemed to reflect the view of the Council, then how can it represent a Consensus of Internet stakeholder. 3. The reason I am using the phrase "consensus of Internet stakeholders" is because that is the phrase that is used in the gTLD contracts. See below which is taken from Section 3.1(b)(iv) of the .com agreement (See http://www.icann.org/tlds/agreements/verisign/registry-agmt-com-01mar06. htm) which states: "Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible, a consensus of Internet stakeholders, including the operators of gTLDs. Consensus Policies shall relate to one or more of the following: (1) issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, Security and/or Stability of the Internet or DNS; (2) functional and performance specifications for the provision of Registry Services (as defined in Section 3.1(d)(iii) below); (3) Security and Stability of the registry database for the TLD; (4) registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars; or (5) resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). Such categories of issues referred to in the preceding sentence shall include, without limitation: Particularly important is the phrase "including the operators of gTLDs". Now before you try to argue that it is modified by the phrase "to the extent possible", let me state that the following: 1. "To the extent possible" does not mean that if the registries are on the losing side of the vote it is not "possible" to achieve gTLD operator support for a proposal on domain tasting. 2. The gTLD Registries have indicated on a number of occassions that we do believe a proposal to eliminate tasting (in TLDs where tasting has occurred) can garner the registry operators support. We are committed to working with you to achieve that. We just need to find a solution that takes into consideration the differences of each of the registries. Now if we are done talking about process, lets get down to business: 1. There is a proposed solution on the table; namely I believe the NeuStar/Afilias proposal (which by the way should be officially posted for public comment today). 2. My recommendation is to take those proposals, get the GNSO Council to initiate a PDP, and launch a Task Force (or Working Group) open to the community whose sole purpose and charter is to study the implications of this proposal. I would gladly help ICANN staff in the drafting of that charter. 3. We follow the strict timing in the Bylaws on the formation of the Task Force/Working Group, elect a chair, and get constituency statements getting them to focus solely on the proposal. This should be very easy, quick and painless. 4. Have a Task Force report that analyzes the constituency statements and public input and modifies the proposal (if necessary). Put that out for comment and draft the final report (all included in the Bylaws). If we follow the strict timing in the Bylaws, which I believe we can, we can have this done, wrapped up and to the Board within 90 days and still before the Paris meeting. This will require some diligent efforts, but let's show that this is possible. Jeffrey J. Neuman, Esq. Sr. Director, Law, Advanced Services & Business Development NeuStar, Inc. e-mail: Jeff.Neuman(a)Neustar.us -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Avri Doria Sent: Friday, February 22, 2008 12:15 PM To: gnso-dt-wg(a)icann.org Subject: Re: [gnso-dt-wg] Rework of motion On 22 Feb 2008, at 11:41, Rosette, Kristina wrote: > eff, good question. I'd appreciate clarification of that, too, to > make > sure we're all on the same page. The transcripts of the GNSO Council > meeting and Thursday wrap-up are far from crystal clear. As for your > other point, I had understood that the bylaws do not require > supermajority support of Council before Board can vote. If there's > language elsewhere that controls, I'd appreciate if you would point me > in the right direction so that I'm working from the same baseline. Hi, As I read the by-laws, appended below, the Council does not need to achieve a supermajority in order to forward on a decision (note 11b). A non supermajority view, though, is treated differently by the board (13b vs. 13f). In terms of this DT, the purpose is still to present a way forward for the council to discuss. That can be a motion, a motion plus update of constituency statements, or a WG charter. The motion can be based on the reworked version Alan has presented, or another motion all together, e.g. the elimination of a required AGP as was suggested by many of the comments or some other motion. I think it is best if the way forward leads to a supermajority position. If we can't get a motion that would be able to garner supermajority support, then perhaps we need to do more work and a WG charter might be the right way forward. a. from the by-laws ----------------------- 11. Council Report to the Board The Staff Manager will be present at the final meeting of the Council, and will have five (5) calendar days after the meeting to incorporate the views of the Council into a report to be submitted to the Board (the "Board Report"). The Board Report must contain at least the following: a. A clear statement of any Supermajority Vote recommendation of the Council; b. If a Supermajority Vote was not reached, a clear statement of all positions held by Council members. Each statement should clearly indicate (i) the reasons underlying each position and (ii) the constituency(ies) that held the position; c. An analysis of how the issue would affect each constituency, including any financial impact on the constituency; d. An analysis of the period of time that would likely be necessary to implement the policy; e. The advice of any outside advisors relied upon, which should be accompanied by a detailed statement of the advisor's (i) qualifications and relevant experience; and (ii) potential conflicts of interest; f. The Final Report submitted to the Council; and g. A copy of the minutes of the Council deliberation on the policy issue, including the all opinions expressed during such deliberation, accompanied by a description of who expressed such opinions. 12. Agreement of the Council A Supermajority Vote of the Council members will be deemed to reflect the view of the Council, and may be conveyed to the Board as the Council's recommendation. Abstentions shall not be permitted; thus all Council members must cast a vote unless they identify a financial interest in the outcome of the policy issue. Notwithstanding the foregoing, as set forth above, all viewpoints expressed by Council members during the PDP must be included in the Board Report. 13. Board Vote a. The Board will meet to discuss the GNSO Council recommendation as soon as feasible after receipt of the Board Report from the Staff Manager. b. In the event that the Council reached a Supermajority Vote, the Board shall adopt the policy according to the Council Supermajority Vote recommendation unless by a vote of more than sixty- six (66%) percent of the Board determines that such policy is not in the best interests of the ICANN community or ICANN. c. In the event that the Board determines not to act in accordance with the Council Supermajority Vote recommendation, the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. d. The Council shall review the Board Statement for discussion with the Board within twenty (20) calendar days after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, e-mail, or otherwise) by which the Council and Board will discuss the Board Statement. e. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for its current recommendation. In the event that the Council is able to reach a Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than sixty-six (66%) percent of the Board determines that such policy is not in the interests of the ICANN community or ICANN. f. In any case in which the Council is not able to reach Supermajority, a majority vote of the Board will be sufficient to act. g. When a final decision on a GNSO Council Recommendation or Supplemental Recommendation is timely, the Board shall take a preliminary vote and, where practicable, will publish a tentative decision that allows for a ten (10) day period of public comment prior to a final decision by the Board.

2 1

RE: [gnso-dt-wg] Rework of motion
by Mike Rodenbaugh Feb. 25, 2008

Feb. 25, 2008

The answer is "MANY TIMES." An excess delete fee proposal was put out for public comment when PIR suggested it. It was the subject of public comment during five different ICANN open meetings and workshops. It again was subject of public comment after the initial Staff Report. Then it was the focus of much public comment during preparation of the Outcomes Report. Then again there was a public comment after the Staff's "Initial Report." Finally, there has been opportunity for public comment at the GNSO meeting in Delhi. To my recollection after all of this public input, no group or individual other than the Registries Constituency (as opposed to many of the individual registries including Neustar) are substantively opposed to the concept of an excess delete fee. We have seen the experience in .org, we have seen .biz and .info propose the same proposal the Design Team has made. We have had a ton of discussion, analysis and public comment. And now we are seeing the Registry Constituency argue only that there is no solution that can apply to them all, and they will not accept (and the Board cannot enforce) any solution they do not agree with. Those arguments need to be tested, as otherwise they give the RyC complete control over GNSO policy development, and the rest of us should just quit wasting our time. I would like ICANN Counsel's view on the latter argument, as I feel it is also core to the debate about GNSO reform, since the proposal from the Board Governance Committee would give the RyC still more power over the process (if that is even possible under their interpretation of the Consensus Policy provisions of their contracts). Given the long history of this issue, I cannot agree to yet another working group and more than 3 more months of delay just within GNSO. The reality is that if GNSO ever does make a recommendation, it would be at least 3-6 more months before the Board could vote on it and it could be implemented, and quite possibly longer. (Note that it took PIR six months to implement its proposal, after Board approval.) -Mike Rodenbaugh -----Original Message----- From: Neuman, Jeff [mailto:Jeff.Neuman@neustar.us] Sent: Monday, February 25, 2008 5:26 AM To: Mike Rodenbaugh; gnso-dt-wg(a)icann.org; Council GNSO Subject: RE: [gnso-dt-wg] Rework of motion Again, you use the term Filibuster, which is completely inappropriate. Please answer the following simple question: QUESTION: At what point in time was the proposal mentioned in the "motion" by the Design Team EVER put out for public comment? Even in looking at your recitation of history (which I am not going to take the time to check the accuracy), the answer is clearly "NEVER". Jeffrey J. Neuman, Esq. Sr. Director, Law, Advanced Services & Business Development NeuStar, Inc. e-mail: Jeff.Neuman(a)Neustar.us -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Mike Rodenbaugh Sent: Monday, February 25, 2008 12:11 AM To: gnso-dt-wg(a)icann.org; 'Council GNSO' Subject: RE: [gnso-dt-wg] Rework of motion Thanks Liz. In response to this report four months ago, the Council essentially voted to handle these terms of reference itself, rather than form a Task Force to do so. I believe we did this because a majority felt we had enough evidence about the effects, judged that the effects justify measures be taken to impede domain tasting, and had much information about potential impacts of various resolutions but also would get Constituency Impact statements about such potential impacts. We then got those Impact Statements. The Council then voted to have an open, volunteer design team to suggest next steps, and that team unanimously recommended a measure designed to impede domain tasting -- which the Council should be deliberating, if we can get past the process roadblock of the Registries. How did we get here? Here's a brief history of the ICANN process wrt to domain tasting, and specifically wrt to the 'excess delete fee' resolution: PIR request to SSAC in March 2006, http://www.pir.org/PDFs/SSAC-ICANN_ORG_Tasting_3-26-06.pdf Sept. 2006, PIR proposal to implement 'excess delete fee service'. Nov. 2006 the ICANN Board: Resolved, (06.84), the President and the General Counsel are authorized to enter into an amendment of the .ORG Registry Agreement to implement the proposed excess deletion fee service At least five ICANN public meetings and workshops on the domain tasting issue, links to full transcripts of those meeting are at this page, http://public.icann.org/issues/domain-name-tasting: * 27 June 2006: Domain tasting workshop * 6 December 2006: Domain name marketplace. * 25 March 2007: How the Marketplace for Expiring Names Has Changed * 25 March 2007: Domain name secondary market * 24 June 2007: Domain tasting tutorial June 2007, PIR implements excess deletion fee, tasting immediately and drastically reduced in .org June 2007: In response to ALAC request and GNSO vote, ICANN staff prepared an issues paper on domain tasting, which discussed the PIR implementation of the excess delete fee. http://gnso.icann.org/issues/domain-tasting/gnso-domain-tasting-report-1 4jun 07.pdf. The report also shows the ICANN General Counsel's opinion that policy development wrt to domain tasting is "within scope of the ICANN policy process and within scope of the GNSO." This report also had a public comment period. June 2007, GNSO voted to form a working group to examine the facts and recommend further action, with a report created in October 2007: http://gnso.icann.org/drafts/gnso-domain-tasting-adhoc-outcomes-report-f inal ...pdf. The working group contained reps from all Constituencies and from other stakeholders. Their consensus report included discussion of excess delete fee (including PIR's implementation), suggestion of it as a potential resolution, and documented the widespread community discussion about it as a resolution. This report included much public input both via an open questionnaire, and also one designed by the Intellectual Property Constituency for trademark owners. October 2007, GNSO voted to move forward with the PDP by requesting Constituency Impact Statements with respect to the information and proposed resolutions contained in the Outcomes report, including the excess delete fee. GNSO rejected option of forming a Task Force, deciding instead that the issue was ripe for Council deliberation and resolution. BC, NCUC, ALAC and Registrars Constituency each give view on excess delete fees. The statements are incorporated in the "Initial Report" http://gnso.icann.org/issues/domain-tasting/gnso-initial-report-domain-t asti ng-07jan08.pdf, which had a public comment period. November 2007, GNSO voted to form a 'design team' to review all the reports and public comments, and recommend next steps in the PDP. January 2008, Design Team of 3 Councilors and ALAC Advisor unanimously agreed on proposed Council resolution recommending excess delete fee for all registries with an AGP, which is the same proposal put forth by Afilias and Neustar for .info and .biz. The Design Team finds this the most reasonable and potentially achievable compromise among the various options. January 29, 2008, ICANN Board suggests action to address domain tasting: http://www.icann.org/announcements/announcement-29jan08.htm." The Internet Corporation for Assigned Names and Numbers is looking to effectively end domain tasting with a proposal to start charging the annual ICANN fee on registrar domain registrations." It is unclear whether this will actually become part of the ICANN budget beginning July, 2008. February 2008, Registries filibuster substantive Council deliberation by arguing there has not been enough process to address the proposed Council resolution. Registry Constituency representative argues that any Council resolution could not become Consensus Policy unless the Registries Constituency agrees to the resolution. Respectfully submitted, Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Liz Gasster Sent: Sunday, February 24, 2008 5:47 PM To: Gomes, Chuck; Rosette, Kristina; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion All, The three draft terms of reference that were suggested in the October 2007 Domain Tasting Outcomes Report that Chuck refers to below are copied for your reference. Liz 1. Review and assess all the effects of domain tasting activities that have been identified. 2. Judge whether the overall effects justify measures to be taken to impede domain tasting. 3. If the answer to 2 is affirmative, then consider the potential impacts of various measures on the Constituencies, and recommend measures designed to impede domain tasting. -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Gomes, Chuck Sent: Sunday, February 24, 2008 12:57 PM To: Rosette, Kristina; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Thanks for the questions Kristina. I attempted to answer them as best I can below with the understanding that what I say is my personal interpretation because I have not cleared it with the RyC. I certainly encourage Jeff as the RyC representative on this WG to confirm or correct anything I say, and I of course will communicate any differences of opinion from RyC members if and when I become aware of any. Chuck -----Original Message----- From: Rosette, Kristina [mailto:krosette@cov.com] Sent: Sunday, February 24, 2008 1:12 PM To: Gomes, Chuck; Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Chuck, It would be helpful to me (and perhaps others) if you could provide some clarification of one point made in the RyC constituency statement. Paragraph 3.1.2 states that "The RyC believes that a one-size-fits-all approach will not work for all registries and sponsors. The RyC therefore suggests that consideration of variations of this approach should be evaluated by individual registries and sponsors. It should also be noted that what is successful for one gTLD may not have the same results in another gTLD." Paragraph 3.2.1 indicates that this position has supermajority support within the RYC. I read this paragraph to mean that the RyC will not support a "one-size-fits-all approach." Is that interpretation correct? CG: Yes, but it may be helpful to qualify what I believe the position means. I attempt that below. If it is, I am having difficulty understanding how it is possible for the design team (or the Council, for that matter) to develop any policy, which will inherently be a one-size-fits-all approach", that will have any support from the RyC. (I am excluding "policies" that recommend no action be taken or recommend the status quo, namely, each registry do its own thing.) Is it possible? If so, I would appreciate some clarification. CG: If a policy is proposed that does not take into consideration the differences among registries and sponsors with regard to the AGP and the impacts the proposed policy might have on various registries and sponsors, then it is highly unlikely that the RyC would support the proposed policy. In my opinion though, that does not mean that the RyC would oppose any proposed policy. What I believe we are saying is that any such policy needs to adequately deal with any applicable differences that exist among registries and sponsors. In other words, the policy development process needs to attempt to address any applicable differences that exist among registries and sponsors. If that is done in a reasonable manner, then I do not think that the RyC would oppose any resulting policy recommendations on the basis of the issue of 'one size fits all'. The fact that this did not happen yet should not be taken as a criticism of the 'design team', because I do not believe they were tasked with developing policy but rather, as Avri pointed out, to suggest next steps forward. But, to the extent that the 'design team' takes on a broader role that includes proposing a possible policy, then it is essential that the one-size fits all issue be dealt with. This to me would best be handled by an open working group with clear terms of reference that delineate tasks as those suggested in the Domain Tasting Outcomes Report. Many thanks. K -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Gomes, Chuck Sent: Saturday, February 23, 2008 8:51 AM To: Mike Rodenbaugh; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion A few corrections and clarifications below Mike. Chuck -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Mike Rodenbaugh Sent: Friday, February 22, 2008 3:34 PM To: gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion I would prefer to vote on the proposal ASAP. Council has already decided not to have a Task Force, and had commissioned an open WG already, and has taken Constituency Impact Statements. This proposal has been thoroughly vetted through open process. I see no hope of coming to a solution that RyC will accept, because their position appears to be that ICANN can't make policy that binds them, unless they agree. And they haven't agreed to any policy development the last 3 years, except for newTLDs which will make them more money and Inter-Registrar Transfer which will save them money via less disputes. Seems to me that RyC is again trying to delay policy development for as long as they can, by throwing up bogus arguments about lack of process. CG: The open WG was an information gathering WG. The impact statements were not based on any policy recommendations developed by a PDP. What proposal was "thoroughly vetted"? Certainly not the proposal in the motion. While we won't have a SuperMajority (if indeed we even have a majority), it will be clear why, and the Board can do as it likes. And we can move onto other issues as we will have done our job. I simply have no confidence that 3 more months will produce anything different in the situation we have today. I have lost patience on this issue because the practice is so facially wrong and has garnered almost unanimous antipathy from the non-contracting community, yet Council have spun our wheels endlessly for about a year now, fruitlessly trying to do anything about it. Process like this gives ICANN a bad name. CG: Whether or not you think additional time will produce what you want is not the issue. The issue is whether or not we have a legitimate policy development process. -Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Neuman, Jeff Sent: Friday, February 22, 2008 12:04 PM To: Avri Doria; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion Avri, Is your question to the ICANN GC on whether the ICANN Board can act? If that is the question, the answer is yes. If your question is whether the ICANN's Board decision is binding on the registries, that is a totally separate issue. Irrespective of the answer, whether we call it a new PDP or jus opening a new WG, I guess I am neutral. I would just clarify that rather than having the WG determine a solution, in order to narrow that down, and speed up the times lines, I would propose that the WG just focus on the solution presented by the Design Team which I believe is the NeuStar/Afilias solution (unless people think that would be too narrow). Design Team -- Does this sound like a way forward? If so, I could take the substance of the motion that has been reworked (minus all of the Whereas clauses) and try to come up with a draft charter and proposed time-line to send to the group. (To that end, if someone has a form charter to use as a template, that would help). If not, I am sure I can wing it. Jeffrey J. Neuman, Esq. Sr. Director, Law, Advanced Services & Business Development NeuStar, Inc. e-mail: Jeff.Neuman(a)Neustar.us -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Avri Doria Sent: Friday, February 22, 2008 2:50 PM To: gnso-dt-wg(a)icann.org Subject: Re: [gnso-dt-wg] Rework of motion Hi, Two quick comments: - The issue of whether this would or would not be a consensus policy is one for legal counsel. I can certainly check with legal counsel to find out the status of a decision according to 13f. - We are already in a PDP. As opposed to trying to begin yet another PDP, I would would think a suggestion for an open WG to come up with a solution that could get a supermajority would be a more feasible route. Assuming others in the DT and the council, agree with you. If this is the path the DT suggests, it would be good for the DT to propose the charter and timings. a. On 22 Feb 2008, at 13:45, Neuman, Jeff wrote: > > A couple of notes: > > 1. A majority of the Council as opposed to Supermajority is not > "deemed to reflect the view of the Council". See Section 12. > > 2. Yes, the Board can act, but again, that Board decision, in my view > (and in the view of the other registries) would not be binding on the > gTLD Registry Operators because that would not be viewed as "consensus > of Internet stakeholders". After all, if a majority is not even > deemed to reflect the view of the Council, then how can it represent a > Consensus of Internet stakeholder. > > 3. The reason I am using the phrase "consensus of Internet > stakeholders" is because that is the phrase that is used in the gTLD > contracts. See below which is taken from Section 3.1(b)(iv) of the > .com agreement (See > http://www.icann.org/tlds/agreements/verisign/registry-agmt-com-01mar06 > . > htm) which states: > > "Consensus Policies and the procedures by which they are developed > shall be designed to produce, to the extent possible, a consensus of > Internet stakeholders, including the operators of gTLDs. Consensus > Policies shall relate to one or more of the following: (1) issues for > which uniform or coordinated resolution is reasonably necessary to > facilitate interoperability, Security and/or Stability of the Internet > or DNS; > (2) > functional and performance specifications for the provision of > Registry Services (as defined in Section 3.1(d)(iii) below); (3) > Security and Stability of the registry database for the TLD; (4) > registry policies reasonably necessary to implement Consensus Policies > relating to registry operations or registrars; or (5) resolution of > disputes regarding the registration of domain names (as opposed to the > use of such domain names). Such categories of issues referred to in > the preceding sentence shall include, without limitation: > > Particularly important is the phrase "including the operators of > gTLDs". > Now before you try to argue that it is modified by the phrase "to the > extent possible", let me state that the following: > > 1. "To the extent possible" does not mean that if the registries are > on the losing side of the vote it is not "possible" to achieve gTLD > operator support for a proposal on domain tasting. > > 2. The gTLD Registries have indicated on a number of occasions that > we do believe a proposal to eliminate tasting (in TLDs where tasting > has > occurred) can garner the registry operators support. We are committed > to working with you to achieve that. We just need to find a solution > that takes into consideration the differences of each of the > registries. > > Now if we are done talking about process, lets get down to business: > > 1. There is a proposed solution on the table; namely I believe the > NeuStar/Afilias proposal (which by the way should be officially posted > for public comment today). > > 2. My recommendation is to take those proposals, get the GNSO Council > to initiate a PDP, and launch a Task Force (or Working Group) open to > the community whose sole purpose and charter is to study the > implications of this proposal. I would gladly help ICANN staff in the > drafting of that charter. > > 3. We follow the strict timing in the Bylaws on the formation of the > Task Force/Working Group, elect a chair, and get constituency > statements getting them to focus solely on the proposal. This should > be very easy, quick and painless. > > 4. Have a Task Force report that analyzes the constituency statements > and public input and modifies the proposal (if necessary). Put that > out for comment and draft the final report (all included in the > Bylaws). > > If we follow the strict timing in the Bylaws, which I believe we can, > we can have this done, wrapped up and to the Board within 90 days and > still before the Paris meeting. > > This will require some diligent efforts, but let's show that this is > possible. > > > Jeffrey J. Neuman, Esq. > Sr. Director, Law, Advanced Services & > > Business Development > > NeuStar, Inc. > e-mail: Jeff.Neuman(a)Neustar.us > > > -----Original Message----- > From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] > On > Behalf Of Avri Doria > Sent: Friday, February 22, 2008 12:15 PM > To: gnso-dt-wg(a)icann.org > Subject: Re: [gnso-dt-wg] Rework of motion > > > > On 22 Feb 2008, at 11:41, Rosette, Kristina wrote: > >> eff, good question. I'd appreciate clarification of that, too, to >> make sure we're all on the same page. The transcripts of the GNSO >> Council meeting and Thursday wrap-up are far from crystal clear. As >> for your other point, I had understood that the bylaws do not require >> supermajority support of Council before Board can vote. If there's >> language elsewhere that controls, I'd appreciate if you would point >> me in the right direction so that I'm working from the same baseline. > > Hi, > > As I read the by-laws, appended below, the Council does not need to > achieve a supermajority in order to forward on a decision (note 11b). > A non supermajority view, though, is treated differently by the board > (13b vs. 13f). > > In terms of this DT, the purpose is still to present a way forward for > the council to discuss. That can be a motion, a motion plus update of > constituency statements, or a WG charter. The motion can be based on > the reworked version Alan has presented, or another motion all > together, e.g. the elimination of a required AGP as was suggested by > many of the comments or some other motion. > > I think it is best if the way forward leads to a supermajority > position. If we can't get a motion that would be able to garner > supermajority support, then perhaps we need to do more work and a WG > charter might be the right way forward. > > a. > > > from the by-laws > ----------------------- > > 11. Council Report to the Board > > The Staff Manager will be present at the final meeting of the Council, > and will have five (5) calendar days after the meeting to incorporate > the views of the Council into a report to be submitted to the Board > (the "Board Report"). The Board Report must contain at least the > following: > > a. A clear statement of any Supermajority Vote recommendation of > the Council; > > b. If a Supermajority Vote was not reached, a clear statement of > all positions held by Council members. Each statement should clearly > indicate (i) the reasons underlying each position and (ii) the > constituency(ies) that held the position; > > c. An analysis of how the issue would affect each constituency, > including any financial impact on the constituency; > > d. An analysis of the period of time that would likely be > necessary to implement the policy; > > e. The advice of any outside advisors relied upon, which should be > accompanied by a detailed statement of the advisor's (i) > qualifications and relevant experience; and (ii) potential conflicts > of interest; > > f. The Final Report submitted to the Council; and > > g. A copy of the minutes of the Council deliberation on the policy > issue, including the all opinions expressed during such deliberation, > accompanied by a description of who expressed such opinions. > > 12. Agreement of the Council > > A Supermajority Vote of the Council members will be deemed to reflect > the view of the Council, and may be conveyed to the Board as the > Council's recommendation. Abstentions shall not be permitted; thus all > Council members must cast a vote unless they identify a financial > interest in the outcome of the policy issue. Notwithstanding the > foregoing, as set forth above, all viewpoints expressed by Council > members during the PDP must be included in the Board Report. > > 13. Board Vote > > a. The Board will meet to discuss the GNSO Council recommendation > as soon as feasible after receipt of the Board Report from the Staff > Manager. > > b. In the event that the Council reached a Supermajority Vote, the > Board shall adopt the policy according to the Council Supermajority > Vote recommendation unless by a vote of more than sixty- six (66%) > percent of the Board determines that such policy is not in the best > interests of the ICANN community or ICANN. > > c. In the event that the Board determines not to act in accordance > with the Council Supermajority Vote recommendation, the Board shall > (i) articulate the reasons for its determination in a report to the > Council (the "Board Statement"); and (ii) submit the Board Statement > to the Council. > > d. The Council shall review the Board Statement for discussion > with the Board within twenty (20) calendar days after the Council's > receipt of the Board Statement. The Board shall determine the method > (e.g., by teleconference, e-mail, or otherwise) by which the Council > and Board will discuss the Board Statement. > > e. At the conclusion of the Council and Board discussions, the > Council shall meet to affirm or modify its recommendation, and > communicate that conclusion (the "Supplemental Recommendation") to the > Board, including an explanation for its current recommendation. In the > event that the Council is able to reach a Supermajority Vote on the > Supplemental Recommendation, the Board shall adopt the recommendation > unless more than sixty-six (66%) percent of the Board determines that > such policy is not in the interests of the ICANN community or ICANN. > > f. In any case in which the Council is not able to reach > Supermajority, a majority vote of the Board will be sufficient to act. > > g. When a final decision on a GNSO Council Recommendation or > Supplemental Recommendation is timely, the Board shall take a > preliminary vote and, where practicable, will publish a tentative > decision that allows for a ten (10) day period of public comment prior > to a final decision by the Board. > > >

1 0

FW: [gnso-dt-wg] Rework of motion
by Mike Rodenbaugh Feb. 24, 2008

Feb. 24, 2008

I think it important for the entire Council to see the reasoning of the Registry Constituency representative to the domain tasting 'design team', as it applies to any policy development work of the Council. Essentially I think this boils down to a position that the ICANN Board cannot enforce any Consensus Policy unless the Registry Constituency has agreed to it. This came as a surprise to me. Perhaps I am misinterpreting and will be corrected by Jeff or another RyC representative. Perhaps we should have an opinion of ICANN Counsel on this issue as well? -Mike Rodenbaugh -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Neuman, Jeff Sent: Friday, February 22, 2008 10:45 AM To: Avri Doria; gnso-dt-wg(a)icann.org Subject: RE: [gnso-dt-wg] Rework of motion A couple of notes: 1. A majority of the Council as opposed to Supermajority is not "deemed to reflect the view of the Council". See Section 12. 2. Yes, the Board can act, but again, that Board decision, in my view (and in the view of the other registries) would not be binding on the gTLD Registry Operators because that would not be viewed as "consensus of Internet stakeholders". After all, if a majority is not even deemed to reflect the view of the Council, then how can it represent a Consensus of Internet stakeholder. 3. The reason I am using the phrase "consensus of Internet stakeholders" is because that is the phrase that is used in the gTLD contracts. See below which is taken from Section 3.1(b)(iv) of the .com agreement (See http://www.icann.org/tlds/agreements/verisign/registry-agmt-com-01mar06. htm) which states: "Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible, a consensus of Internet stakeholders, including the operators of gTLDs. Consensus Policies shall relate to one or more of the following: (1) issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, Security and/or Stability of the Internet or DNS; (2) functional and performance specifications for the provision of Registry Services (as defined in Section 3.1(d)(iii) below); (3) Security and Stability of the registry database for the TLD; (4) registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars; or (5) resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). Such categories of issues referred to in the preceding sentence shall include, without limitation: Particularly important is the phrase "including the operators of gTLDs". Now before you try to argue that it is modified by the phrase "to the extent possible", let me state that the following: 1. "To the extent possible" does not mean that if the registries are on the losing side of the vote it is not "possible" to achieve gTLD operator support for a proposal on domain tasting. 2. The gTLD Registries have indicated on a number of occassions that we do believe a proposal to eliminate tasting (in TLDs where tasting has occurred) can garner the registry operators support. We are committed to working with you to achieve that. We just need to find a solution that takes into consideration the differences of each of the registries. Now if we are done talking about process, lets get down to business: 1. There is a proposed solution on the table; namely I believe the NeuStar/Afilias proposal (which by the way should be officially posted for public comment today). 2. My recommendation is to take those proposals, get the GNSO Council to initiate a PDP, and launch a Task Force (or Working Group) open to the community whose sole purpose and charter is to study the implications of this proposal. I would gladly help ICANN staff in the drafting of that charter. 3. We follow the strict timing in the Bylaws on the formation of the Task Force/Working Group, elect a chair, and get constituency statements getting them to focus solely on the proposal. This should be very easy, quick and painless. 4. Have a Task Force report that analyzes the constituency statements and public input and modifies the proposal (if necessary). Put that out for comment and draft the final report (all included in the Bylaws). If we follow the strict timing in the Bylaws, which I believe we can, we can have this done, wrapped up and to the Board within 90 days and still before the Paris meeting. This will require some diligent efforts, but let's show that this is possible. Jeffrey J. Neuman, Esq. Sr. Director, Law, Advanced Services & Business Development NeuStar, Inc. e-mail: Jeff.Neuman(a)Neustar.us -----Original Message----- From: owner-gnso-dt-wg(a)icann.org [mailto:owner-gnso-dt-wg@icann.org] On Behalf Of Avri Doria Sent: Friday, February 22, 2008 12:15 PM To: gnso-dt-wg(a)icann.org Subject: Re: [gnso-dt-wg] Rework of motion On 22 Feb 2008, at 11:41, Rosette, Kristina wrote: > eff, good question. I'd appreciate clarification of that, too, to > make > sure we're all on the same page. The transcripts of the GNSO Council > meeting and Thursday wrap-up are far from crystal clear. As for your > other point, I had understood that the bylaws do not require > supermajority support of Council before Board can vote. If there's > language elsewhere that controls, I'd appreciate if you would point me > in the right direction so that I'm working from the same baseline. Hi, As I read the by-laws, appended below, the Council does not need to achieve a supermajority in order to forward on a decision (note 11b). A non supermajority view, though, is treated differently by the board (13b vs. 13f). In terms of this DT, the purpose is still to present a way forward for the council to discuss. That can be a motion, a motion plus update of constituency statements, or a WG charter. The motion can be based on the reworked version Alan has presented, or another motion all together, e.g. the elimination of a required AGP as was suggested by many of the comments or some other motion. I think it is best if the way forward leads to a supermajority position. If we can't get a motion that would be able to garner supermajority support, then perhaps we need to do more work and a WG charter might be the right way forward. a. from the by-laws ----------------------- 11. Council Report to the Board The Staff Manager will be present at the final meeting of the Council, and will have five (5) calendar days after the meeting to incorporate the views of the Council into a report to be submitted to the Board (the "Board Report"). The Board Report must contain at least the following: a. A clear statement of any Supermajority Vote recommendation of the Council; b. If a Supermajority Vote was not reached, a clear statement of all positions held by Council members. Each statement should clearly indicate (i) the reasons underlying each position and (ii) the constituency(ies) that held the position; c. An analysis of how the issue would affect each constituency, including any financial impact on the constituency; d. An analysis of the period of time that would likely be necessary to implement the policy; e. The advice of any outside advisors relied upon, which should be accompanied by a detailed statement of the advisor's (i) qualifications and relevant experience; and (ii) potential conflicts of interest; f. The Final Report submitted to the Council; and g. A copy of the minutes of the Council deliberation on the policy issue, including the all opinions expressed during such deliberation, accompanied by a description of who expressed such opinions. 12. Agreement of the Council A Supermajority Vote of the Council members will be deemed to reflect the view of the Council, and may be conveyed to the Board as the Council's recommendation. Abstentions shall not be permitted; thus all Council members must cast a vote unless they identify a financial interest in the outcome of the policy issue. Notwithstanding the foregoing, as set forth above, all viewpoints expressed by Council members during the PDP must be included in the Board Report. 13. Board Vote a. The Board will meet to discuss the GNSO Council recommendation as soon as feasible after receipt of the Board Report from the Staff Manager. b. In the event that the Council reached a Supermajority Vote, the Board shall adopt the policy according to the Council Supermajority Vote recommendation unless by a vote of more than sixty- six (66%) percent of the Board determines that such policy is not in the best interests of the ICANN community or ICANN. c. In the event that the Board determines not to act in accordance with the Council Supermajority Vote recommendation, the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. d. The Council shall review the Board Statement for discussion with the Board within twenty (20) calendar days after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, e-mail, or otherwise) by which the Council and Board will discuss the Board Statement. e. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for its current recommendation. In the event that the Council is able to reach a Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than sixty-six (66%) percent of the Board determines that such policy is not in the interests of the ICANN community or ICANN. f. In any case in which the Council is not able to reach Supermajority, a majority vote of the Board will be sufficient to act. g. When a final decision on a GNSO Council Recommendation or Supplemental Recommendation is timely, the Board shall take a preliminary vote and, where practicable, will publish a tentative decision that allows for a ten (10) day period of public comment prior to a final decision by the Board.

1 0

[Fwd: Candidate Statement]
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Feb. 24, 2008

Feb. 24, 2008

Dear Council Members, Please find the Rita Rodin's candidate statement for the position of ICANN Director, seat 14. A reminder: there will be the opportunity for the Council and constituency members to interview Rita on the Thursday, 28 February call at 19:00 UTC. Thank you, Glen Candidate Name: Rita A. Rodin Citizenship: United States of America Employer: Skadden Arps Slate Meagher & Flom LLP Criteria for Selection of Directors 1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and a demonstrated capacity for thoughtful group decision-making; I am a partner in the Intellectual Property and Technology Group in the New York office of the law firm of Skadden, Arps, Slate, Meagher & Flom LLP. I received a Bachelor of Science (magna cum laude) from Boston College in 1990, and Juris Doctor from St. John's University in 1993. I served as a federal law clerk to the Honorable Thomas C. Platt, Chief Judge of the Eastern District of New York, from 1993-1994. I joined Skadden in 1994, as our internet practice was beginning. Our practice permits me to represent both multi-national and start-up companies, in a diverse range of industries and countries. I have worked with clients such as Merck KGaA, Richemont SA, Skype Technologies, IBM, Deloitte and Touche and Banco Itau. My practice today is diverse and international, and I focus on mergers and acquisitions, joint ventures and strategic alliances and outsourcing arrangements. I regularly lecture and write on various intellectual property and technology topics, including outsourcing, trademark and domain name developments and open source software. My clients rely on me to identify, understand and negotiate complex positions and arrangements. I believe to be successful in that role, I must listen to and respect all points of view, and work to facilitate compromise and agreement. I further believe that skills of this nature can and should be employed within the ICANN community to foster trust, consensus and progress on some of the difficult issues facing ICANN today. 2. Persons with an understanding of ICANN's mission and the potential impact of ICANN decisions on the global Internet community, and committed to the success of ICANN. I have been fortunate to serve on the ICANN Board since June of 2006, and to work with ICANN and members of the ICANN community since 1998. In my various roles, I have developed an understanding of the issues and touch points of many of ICANNs stakeholders, and also understand now from a Directors point of view, the challenges that the organization has faced and continues to face. I decided to run for the Board seat again because I believe that we are entering a critical phase of ICANNs growth and development, and am committed to assist in any way that I can to the continued improvement of the organization. 3. Persons who will produce the broadest cultural and geographic diversity on the Board consistent with meeting the other criteria set forth in this Section; I am from the United States, so generally will approach my Director duties from a US perspective, but I have worked and traveled quite extensively throughout the world and still have close family living in other countries. I believe that this enables me to understand and appreciate different cultures and points of view. I also believe that it is important to maintain a gender balanced Director slate, as there are relatively few women currently serving on the Board. Finally, I think that being the tallest Board member (even when not in heels) also contributes to diversity. 4. Persons who, in the aggregate, have personal familiarity with the operation of gTLD registries and registrars; with ccTLD registries; with IP address registries; with Internet technical standards and protocols; with policy-development procedures, legal traditions, and the public interest; and with the broad range of business, individual, academic, and non-commercial users of the Internet; As I mentioned above, I worked with ICANN and different constituencies since the organization's inception in 1998. Following are some details. UDRP In 1998, my firm was asked to represent register.com and AOL in connection with drafting an effective and streamlined policy to deal with disputes between trademark and domain name owners. We worked with the World Intellectual Property Organization, registrars, Network Solutions (then, the sole .com/net/org registry) and ICANN to create a draft of the UDRP. After I presented the draft at the ICANN meeting in Santiago, Chile, I was asked to participate in a small drafting committee consisting of members of the non-commercial and intellectual property interests, in addition to members of WIPO and ICANN. This committee finalized the policy that is still in use today. .INFO/.NAME./.TEL I worked with the group of registrars that formed Afilias, Ltd., operators of the .info registry, through the (i) formation of Afilias, (ii) ICANN bid process, (iii) ICANN contract negotiations, and (iv) start-up of its operations. I also represented the Global Name Registry in connection with its ICANN contract negotiations and start-up operations. I currently represent Telnic, Ltd., the entity that was recently awarded the .tel sTLD. POLICY DEVELOPMENT PROCESS In 2002, I was appointed by ICANN to chair an international task force that drafted the Policy Development Process that is currently used by ICANN to develop and implement future ICANN policies. As discussed above, I am a transactional lawyer with a diverse and global practice. As such, my job consists of identifying issues and proposing resolutions for clients with different points of view and cultural backgrounds. In addition, my work requires that I interface with an organization at all levels - - from advising Boards and senior management to addressing issues facing those responsible for the execution of day-to-day operations. In this role, I cannot only advocate the position of my client, because without a mutually acceptable solution, no agreement will be reached. Rather, I must listen to, and understand, all sides of an issue in order to facilitate reaching agreement. I view these skills as very important for a member of ICANN's Board. Given the diverse nature of the global internet community, I think that it is critical for the Board to listen to, and appreciate, all voices and opinions. I believe that the Board must assist constituencies in seeking and reaching consensus, to enable all involved to benefit from the resolution of issues. I also view my experience with multiple constituencies within the ICANN community as providing me with unique insight into the often competing concerns and issues of many of the community stakeholders. I would seek to use this experience to accommodate the interests of as many ICANN stakeholders as possible. 5. Persons who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and I am willing to serve in the absence of compensation other than the reimbursement of certain expenses. 6. Persons who are able to work and communicate in written and spoken English. English is my native language. Section 4. ADDITIONAL QUALIFICATIONS 1. Notwithstanding anything herein to the contrary, no official of a national government or a multinational entity established by treaty or other agreement between national governments may serve as a Director. As used herein, the term "official" means a person (i) who holds an elective governmental office or (ii) who is employed by such government or multinational entity and whose primary function with such government or entity is to develop or influence governmental or public policies. I am not such an official. 2. No person who serves in any capacity (including as a liaison) on any Supporting Organization Council shall simultaneously serve as a Director or liaison to the Board. If such a person accepts a nomination to be considered for selection by the Supporting Organization Council to be a Director, the person shall not, following such nomination, participate in any discussion of, or vote by, the Supporting Organization Council relating to the selection of Directors by the Council, until the Council has selected the full complement of Directors it is responsible for selecting. In the event that a person serving in any capacity on a Supporting Organization Council accepts a nomination to be considered for selection as a Director, the constituency group or other group or entity that selected the person may select a replacement for purposes of the Council's selection process. I have not served on any Supporting Organization Council. 3. Persons serving in any capacity on the Nominating Committee shall be ineligible for selection to positions on the Board as provided by Article VII, Section 8. I have not served on the Nominating Committee. ------------------------------------------------------------------------------ **************************************************** To ensure compliance with Treasury Department regulations, we advise you that, unless otherwise expressly indicated, any federal tax advice contained in this message was not intended or written to be used, and cannot be used, for the purpose of (i) avoiding tax-related penalties under the Internal Revenue Code or applicable state or local tax law provisions or (ii) promoting, marketing or recommending to another party any tax-related matters addressed herein. **************************************************** **************************************************** This email and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this email, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify me at (212) 735-3000 and permanently delete the original copy and any copy of any email, and any printout thereof. Further information about the firm, a list of the Partners and their professional qualifications will be provided upon request. **************************************************** ============================================================================== -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

GNSO response to ccNSO GAC Issues report on IDNs
by Olof Nordling Feb. 22, 2008

Feb. 22, 2008

Dear Board Members, Please find attached the GNSO response to the ccNSO/GAC Issues Report regarding IDNs at the top-level, on behalf of and with kind regards from the GNSO Council Chair, Avri Doria. Very best regards Olof

1 0

RE: GNSO response to Issues Report on IDN ccTLDs
by Olof Nordling Feb. 21, 2008

Feb. 21, 2008

Dear all, Attached is the final version of the GNSO response. The only modifications in relation to the version sent 15 February are that minority statements from the NCUC regarding "confusingly similar" and from Avri Doria have been attached as annex 1 and 2, respectively, and referenced with footnotes in the summary. This version is now in FINAL CALL on the Council list for 48 hours, thus until 22 February 21.00 UTC (there were some slight delays, hence the current timing...). The text will then be submitted as GNSO's response (provided no objections surface on the list in the meantime). Very best regards Olof -----Original Message----- From: Olof Nordling Sent: den 15 februari 2008 06:20 To: 'Council GNSO' Subject: GNSO response to Issues Report on IDN ccTLDs Dear all, The attached version of the GNSO response reflects the state of this document at the end of the ICANN New Delhi meeting, following the GNSO discussions on Thursday 14 February. The NCUC will provide a minority statement on "confusingly similar" before Wednesday 20 February 17.00 UTC - and any other comments/modifications have the same deadline. Please send any comments to me. A final version will be sent to the list very soon thereafter for a 48 hour final call and subsequent lodging by the 22 February deadline for submissions. Very best regards Olof

2 1

Some clarifications on meetings.
by Avri Doria Feb. 19, 2008

Feb. 19, 2008

Hi, After some more discussion on meetings, and partially due to the schedule we set collided with May 1, which for many is a holiday, the schedule of meetings is suggested as follows: 28 Feb - Informal meeting with Rita prior to voting which begins on 29 Feb. 6 March - regular council meeting 27 March- regular council meeting 17 April- regular council meeting 8 May- regular council meeting 29 May- regular council meeting I also believe we will need to schedule a fair number of other meetings for Drafting Teams, Improvement implementation teams, new gTLD clarification efforts, WGs, etc - but that will be done later. a.

3 4