Comment Close
Date
Statement
Name 

Status

Assignee(s)

Call for
Comments Open
Call for
Comments
Close 
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number
31.07.2015

Draft Report: Review of the Generic Names Supporting Organization

ADOPTED 11Y, 0N, 0AOlivier Crepin-Leblond     
Larisa Gurnick
AL-ALAC-ST-0815-01-01-EN


For information about this Public Comment, please click here 

 

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Click here to download the Final Version



FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

Download the Final Draft Statement here



FIRST DRAFT SUBMITTED

The Public Consultation provides a template for input in Docx format. Unfortunately, restrictions on the document appear to make it impossible to cut/paste its contents. Parts of the document template appear to be locked and some parts have pull-down menus. It also appears to be impossible to insert comments (using document review) in the document itself. Due to these difficulties, I have also generated a PDF copy of the document. Please comment on it by noting recommendation number + your comment.

Please also note that I have not filled the overall comments box and following on my concerns expressed in my comment below, please make suggestions for an overall comment about anything not included in the current recommendations. For example, can you think of any recommendation that's missing from the list?

  • No labels

22 Comments

  1. I am disturbing that 43 days in to this PC and 7 days from it closing, there are no comments here!

    Perhaps this will be  a start.

     

    Recommendation 2: Develop and fund more targeted programmes to recruit volunteers and broaden participation in PDP WGs, given the vital role volunteers play in Working Groups and policy development.

    Recommendation 3: Review the level, scope and targeting of financial assistance to ensure volunteers are able to participate on a footing comparable with those who participate in GNSO as part of their profession.

    Both of these correspond to things that the ALAC has been saying for ages. Recommendation 8 is an echo of ATRT2 Recommendation 10.5. When we raised the subject at ICANN 53 (and pointed out that nothing had been done), we received feedback that all we ever do is complain that we need more money.

    Perhaps in this form, the the idea may become more acceptable. I note that the only announced "outcome of 10.5 is the CROPP program, a program that was initiated prior to the ATRT2 recommendations being delivered and that does virtually nothing to support involvement in the policy processes.

    Recommendation 4: Explore a tailored incentive system to increase the motivation of volunteers. (For example, this may include training & development opportunities or greater recognition of individuals).

     This is an innovative suggestion and it deserves out strong support.

    Recommendation 10: That a professional facilitator/moderator is used in certain situations (for example, when policy issues are complex, where members of the WG are generally inexperienced and/or where WG members have interests that conflict), and that the GNSO develop guidelines for the circumstances in which professional facilitators/moderators are used for Working Groups.

    This is inline with suggestion that the ALAC has made. It is particularly applicable where the Public Interest and User issues are pitted against the interests of Contracted Parties.

    As an added benefit, if done for the GNSO, there is increased chances that we could benefit as well.

    Recommendation 36: That, when approving the formation of a PDP WG, the GNSO Council require that its membership represent as far as reasonably practicable the geographic, cultural and gender diversity of the Internet as a whole. Additionally, that when approving GNSO Policy, the ICANN Board explicitly satisfy itself that the GNSO Council undertook these actions when approving the formation of a PDP WG.

    This is interesting, but it also requires an assessment of how successful it is in practice. It is unclear hoe one does this in a WG where all participation is voluntary. But regardless, just adding people to the mailing list does not say anything about how much these people participate or contribute. If it is just a "tick off the boxes" exercise.

     

    1. I have read the full report and am preparing a fuller response. The great majority of recommendations are very similar to what the ALAC has been asking for both in past reviews, but also in ATLAS II recommendations and in meetings with GSE, the Board and the ICANN CEO. I can therefore say that we fully support all of the recommendations - but will propose comments for each recommendation in order to explain our support.

      I am concerned that some of the outreach recommendations from the ATRT2 and other reviews have been ignored by GNSO Council at implementation since it was deemed that Global Stakeholder Engagement (GSE) was taking care of that. Councillors have not yet understood that GSE is a wider stakeholder engagement program (Sally Costerton's department) that does not focus specifically on Policy (David Olive's department). Perhaps should we note this and suggest that the two departments work closer together.

      There are a couple of recommendations where I am unsure of implementation.

      For example, recommendation #23, approving new GNSO Constituencies. (and other new GNSO Constituency recommendations)

      I am concerned about the creation of more Constituencies, all of which might probably end up in the Non-Contracted Party House, thus further fragmenting the Non-Contracted Party House and increasing tension between Constituencies. We all know about the tension between NCUC and NPOC. Having more Consituencies might only continue to strengthen the Contracted Party House since their vote will be more homogeneous and they will be able to "pick and mix" within the Non-Contracted Party House in order to obtain a majority.

      Finally, I am very concerned that none of the recommendations address the wider malaise about the balance of power in the GNSO and the potential for capture caused by a fragmented Non-Contracted Party House and a solid Contracted Party House. We keep on hearing "the GNSO is broken and needs to be reformed" and yet there is not one line in the report that actually investigates the validity of this assertion. I see this as an opportunity missed.

      As I said, I'll soon put a fuller document online.

       

      1. The strategic objective for the ALAC is that given the role of GNSO in names and numbers policy making and reflecting on the brief for the ALAC in the ICANN ecosystem, its immediate action is to double down on anything in this report that tends to recommend expanding coverage of end user interests before Council, enabling equitable access to the policy development process for informed end user representatives and interests and all that allows early and sustained intervention in the policy making process.

        Yes as well to all recommendations suggesting more measurement of outcomes; on the principle that that which is measured inevitably gets managed.

        I have finally read thru the report and its a +1 to Alan's choices for emphasizing concurrence with the recommendations. Specifically:

        Referencing Participation & Representation, the ALAC should trumpet Recommendations #s 1 - 4, 6, 7, 12, 32-36.

        Referencing  Continuous Development, the ALAC should trumpet Recommendations #s 8, 10, 11,14, 16-18 

        Referencing  Transparency, the ALAC should trumpet Recommendations #s 24, 26 - 28

        I would endorse OCL's ruminations on the balance of power in the GNSO by writing an entire section that caution the adoption of new constituencies without a change in the formula - and formulation! - for voting rights.

        It is always the results that matter.  And some of the recommendations pertaining look innocuous enough. But when analyzed in current dispensation, they present real risks to dilution of impact of the non-contracted parties.  It seems reflexive to me that given what we know of the history of the non-contracted house in the ICANN ecosystem and regardless of the prospects for a set of newly-enabled contracted parties - see the EWG's contemplations, for example - vote splintering sometimes result in exactly less impact of smaller less powerful entities than anticipated.  Lots of examples exist in politics politics to underscore this fact. 

        -Carlton

    2.  

      Recommendation 8 is an echo of ATRT2 Recommendation 10.5.

       

      I think you mean Recommendation 3 is an echo of ATRT2 Recommendation 10.5.

       

      I have taken this comment into account in the response, as well as the other points you have made in your comment. Please check whether more needs to be added.

  2. I have been going through the recommendations as they relate to the Working groups (Recs 1-8) and have the following comments:

    I agree with Alan that there are a lot of WG and engagement issues raised that the ALAC has been trying to deal with for ages:

    • for example, the perennial small pool of people who are actively involved in WGs
    • ALAC tries to ensure that there is diversity among the WG members (regions, gender, backgrounds, etc) but that does not necessarily mean that the members selected actually turn up to meetings
    • Sometimes WG leaders assume that everyone is on the same page with regards to the knowledge that is required in order to participate effectively, this can lead to people dropping out of WGs because they don't feel capable enough. Sometimes people whose profession is related to the topic and who already come with expertise to contribute tend to think everyone is on the same level of understanding so that some participants become swamped. The use of acronyms, etc can be a little overpowering for newbies - even those who want to learn more about the topic or who don't speak English and there are no translation services in their home language
    • APAC and APRALO (and I know LACRALO as well) have been offering webinars to help people gain a better understanding of even the basics of knowledge to help them cope with WG activities - but these have been poorly attended at the actual webinar, and we are trying to find some way of ascertaining who accesses the transcripts etc later, because of timing issues
    • Targetting financial assistance and offering incentives may not necessarily attract the right people to WGs. Many of us have raised the inhospitable hours of meetings and the cost of internet access - particularly in my country. These are a personal cost which those of us who are on already heavy meeting schedules take on because of our commitment to what we are doing. But timing of meetings and the cost of the internet could preclude some from participating in online meetings and webinars. 
    • I didn't realise just how many outreach programmes ICANN has in place to try to attract more people in order to fill the WG and other spaces in order to give the user community more of a voice - but how effective are these programmes for actually increasing WG participation - if that is the purpose of the CROPP activity? We are still short on the ground when it comes to active participation in WGs.

    • Trying to involve non-English speakers is a problem. In Bejing, the Chinese community, led by Hong, met together to discuss ICANN and their involvement in it. It could be of benefit for cross-community non-English language WGs to be formed, in different language groups and led by a strong ICANN leader in that language, to discuss public consultation topics, with a transcript in their home language and English provided afterwards. Any costs could be covered by ICANN
      .
    • Rec 17 has merit - but there should be regular on-going self-evaluation of WGs (not just at the completion of their work). We are finding some of our own WGs which are not as active as they could be
    • Rec 22 - orientation training of new members to the GNSO (and ALAC) - with training and development based on the needs of the member with metrics and assessment procedures attached. Good idea.
    • Rec 26 - interesting - asking for SOIs for those who apply for WGs - possibly for closed  membership WGs (ALAC WGs generally have open membership)
    • The recommendations related to Stakeholder groups and Constituencies appear to imply that there is little consistency or transparency about their application process - increasing possible capture as suggested by OCL especially where some information is withheld.  Rec 27 could use the model that ALAC has for its ALSes, where information about each of the member organisations is online and available for all to see. Their ROPs should clearly state mandatory information.
    • Rec 34 - rotating meeting times was a procedure that helped the ccNSO FOIWG carry out its work over the 4 years of its fortnightly meetings 

    • Recs 35 and 36 - INCLUSION should be incorporated into the GNSO Rules of Procedure rather than creating a WG to ensure that all members of GNSO are able to participate in all WGs regardless of language and other diversity criteria. It should be a right for all members of the GNSO.
    1. Hello Maureen,

       

      Thanks very much for your comments. I'll share a few comments on your comments:

       

      • Targetting financial assistance and offering incentives may not necessarily attract the right people to WGs. Many of us have raised the inhospitable hours of meetings and the cost of internet access - particularly in my country. These are a personal cost which those of us who are on already heavy meeting schedules take on because of our commitment to what we are doing. But timing of meetings and the cost of the internet could preclude some from participating in online meetings and webinars.

       

      OCL: please bear in mind these are GNSO Working Groups which have specific tasks. I do not think that the aim of attracting diversity in GNSO working groups has quite the same flexibility as ALAC working groups which are generally standing working groups

       

      • I didn't realise just how many outreach programmes ICANN has in place to try to attract more people in order to fill the WG and other spaces in order to give the user community more of a voice - but how effective are these programmes for actually increasing WG participation - if that is the purpose of the CROPP activity? We are still short on the ground when it comes to active participation in WGs.

      OCL: fully agree. We can comment on how the CROPP was used by At-Large, but I personally do not know how the GNSO has used CROPP and whether it has been successful - and would therefore rather refrain from commenting specifically about CROPP. In At-Large, CROPP has been specifically outreach and not engagement.

      • Trying to involve non-English speakers is a problem. In Bejing, the Chinese community, led by Hong, met together to discuss ICANN and their involvement in it. It could be of benefit for cross-community non-English language WGs to be formed, in different language groups and led by a strong ICANN leader in that language, to discuss public consultation topics, with a transcript in their home language and English provided afterwards. Any costs could be covered by ICANN

      OCL: I would refrain from proposing non English Language PDP Working Groups in the GNSO. I have suggested, as a first step, interpretation to be provided on a trial basis, for some GNSO calls and/or Working Group calls.
      .

      • Rec 17 has merit - but there should be regular on-going self-evaluation of WGs (not just at the completion of their work). We are finding some of our own WGs which are not as active as they could be

      OCL: GNSO PDP Working Groups have a chartering stage, start & end with deliverables. At-Large Working Groups are, for the most, standing working groups. I think that what's applicable to At-Large working Groups - and I really support your suggestion there - might not be applicable to the GNSO working groups since their lifetime is shorter and often the work is so intense that ongoing self-evaluation might divert scarce resources thus hindering progress.

      • Rec 22 - orientation training of new members to the GNSO (and ALAC) - with training and development based on the needs of the member with metrics and assessment procedures attached. Good idea.

      OCL: Have I reflected this well in the suggested response?

      • Rec 26 - interesting - asking for SOIs for those who apply for WGs - possibly for closed  membership WGs (ALAC WGs generally have open membership)

      OCL: GNSO WGs are open to everyone to participate in but you need to register and provide an SoI. I think that this recommendation will formalise this and make it mandatory.

       

  3. I'd like to support many of the comments made, as follows:

    I'd particularly like to support the comments made by Alan and Maureen in relation to recommendations 1-8 on participation in WG.  And sorry, OCL, but language is a barrier and for policies that impact particularly on end users, there should be at least a trial on the provision of interpretation.  I also support Maureen in pointing to the hours held - and the fact that it can make participation a challenge if they are held when it is VERY early morning in the Asia Pacific region.  Once a week maybe okay, but only CLO can regularly manage those hours and then do a day's work.  One recommendation that was not made, but picked up by Maureen is for a webinar at the time of calling for volunteers so that those not familiar with the issues can better understand what the WG will be doing. 

    I agree and really don't have anything to add on the financial issues - enough has been said already.  And CROPP - that is being worked through, but I would like to see at least part of its metrics a better - or better informed - participation in ICANN.

    Also participation, some people can't attend the actual meetings, but do read the transcripts and participate in the discussion on the mailing list, so be careful of metrics used to measure participation

    PLEASE no more constituencies.  I agree with OCL's concerns.  It was MM who stood up in a public forum (forget which meeting - Costa Rica, I think) and pleaded for no more consumer constituencies.  In his words, it is already broken!

    The Policy and Implementation issues are being looked at and I support continuing involvement of WG members in the implementation phase.  My example is the Whois conflicts implementation WG that has to deal with a policy that was stated in general terms - followed by an Implementation WG that translated the general policy into rules that cannot be implemented by registrars in countries with strong privacy laws (lots). So we are now in the middle of a WG to review the work of the original Implementation WG!

    1. Dear Holly,

       

      I'd like to support many of the comments made, as follows:

      I'd particularly like to support the comments made by Alan and Maureen in relation to recommendations 1-8 on participation in WG.  And sorry, OCL, but language is a barrier and for policies that impact particularly on end users, there should be at least a trial on the provision of interpretation. 

       

      OCL: OK I'll add this and make it a bit more explicit.

       

       

      I also support Maureen in pointing to the hours held - and the fact that it can make participation a challenge if they are held when it is VERY early morning in the Asia Pacific region.  Once a week maybe okay, but only CLO can regularly manage those hours and then do a day's work.  One recommendation that was not made, but picked up by Maureen is for a webinar at the time of calling for volunteers so that those not familiar with the issues can better understand what the WG will be doing. 

       

      OCL: the GNSO already practices time rotation as standard. (or at least should do)

       

       

      I agree and really don't have anything to add on the financial issues - enough has been said already.  And CROPP - that is being worked through, but I would like to see at least part of its metrics a better - or better informed - participation in ICANN.

      Also participation, some people can't attend the actual meetings, but do read the transcripts and participate in the discussion on the mailing list, so be careful of metrics used to measure participation

      PLEASE no more constituencies.  I agree with OCL's concerns.  It was MM who stood up in a public forum (forget which meeting - Costa Rica, I think) and pleaded for no more consumer constituencies.  In his words, it is already broken!

      The Policy and Implementation issues are being looked at and I support continuing involvement of WG members in the implementation phase.  My example is the Whois conflicts implementation WG that has to deal with a policy that was stated in general terms - followed by an Implementation WG that translated the general policy into rules that cannot be implemented by registrars in countries with strong privacy laws (lots). So we are now in the middle of a WG to review the work of the original Implementation WG!

      OCL: Noted. I do not think we can add anything else, as this is a process that's already going on.

      Thanks!

       

      1. Thanks Olivier

         

        Just one comment - we all know there should be time rotation.  However, for both the IRTP-D and the PPSAI the calls were never rotated and ALWAYS in the wee hours of the morning.  So a gentle reminder that, if broader participation is a priority, then some attention should be paid to the Asia-Pacific region

         

         

  4. Comment from Christopher Wilkinson sent on 22 July 19:00 UTC. 

    ==

    More generally, I consider that much of the CWG and CCWG attack on the ICANN Board's accountability can be traced back to self-interested and indefensible GNSO positions which the Board has endorsed uncritically on the basis of 'bottom up' policy developoment. Several aspects of the new gTLD program which have proved to be unsustainable and indefensible can be traced back to positions espoused by the Registry and Registrar community.

    Regarding the structure of GNSO, I can only say that the NCUC etc. members, although claiming Civil Society affiliation have serially failed to identify and support the public interest or to rein in the commercial objectives of the Registries and Registrars.  Nom-com and other liaisons with GNSO appear not to have the necessary leverage. 

    ICANN's primary responsibility is the regulation of the conditions of fair competition in the DNS market. It has become clear that the community will not get anything like that from GNSO as presently structured. 

    I trust that this is clear and useful

  5. I prepared the following comment in response to Olivier's request for thoughts on the bicameral structure of the GNSO.

    Tom Lowenhaupt

    ---------------

    Olivier,

    I've not had the opportunity to read the Westlake document, only the comments about it as presented on the At-Large wiki workspace. But having read your request about raising possible concerns now, I offer the following comment.

    My ICANN involvement stems from an interest in the effective utilization of the Internet in cities. When I hear about a fixed bicameral GNSO structure, it raises a fundamental question: How are the concerns of city residents (now comprising more than 1/2 the world's population) to be heard within that structure?

    For example, are the interests and concerns of New York City's 8.5 million residents adequately represented through the contractual "house"? While I'm not familiar with the minutia of the legal relationship between the city of New York and ICANN, it appears that today our city's residents are to address their concerns about the operation of the .nyc TLD to a city contractor based in the state of Virginia. When I explain the extant state of oversight of our city's TLD to fellow residents I get that "You gotta be kidding?" look.

    At the ICANN 53 meeting I addressed the Board of Directors to suggest that, going forward, "informed consent" and "multistakeholder governance" be standard components of the city-TLD application process, and that the public interest would be found therein.

    For now I've no conclusive answer to put forward as to how 1/2 the world's population should have their interests represented at ICANN and other digital venues. As you are aware, our organization is exploring the At-Large as a possible route for representation of our city's individual Internet users. But where in the GNSO?

    Getting back to today's question about the current bicameral GNSO. At this stage of the Internet's development - with the Net becoming more important to our lives every day - it is essential that welcoming passageways to participation in the GNSO be provided for in the upcoming transition, both for cities and other stakeholders needing voice in the Net's governance.

    Sincerely,

    Thomas Lowenhaupt, Director

    Connecting.nyc Inc.

     

    -------- Original Message --------
    Subject: Re: [At-Large] [ALAC] [ALAC-Announce] CALL FOR COMMENTS: ALAC
    Statement on the Draft Report: Review of the Generic Names Supporting
    Organization
    From: Olivier MJ Crepin-Leblond <ocl@gih.com>
    Date: Wed, July 22, 2015 12:50 pm
    To: alac@atlarge-lists.icann.org, At-Large Worldwide
    <at-large@atlarge-lists.icann.org>

    Hello all,

    just a kind reminder, a few hours away from the At-Large Comments closing.
    I have heard in corridors that some people were concerned about the lack of overall review of the GNSO's structure and most of the recommendations focussed on GNSO Working Groups and small adjustments rather than taking a serious look at the GNSO's bicameral structure. Yet, I have not seen any actual written confirmation of this concern here. Could you please all take a short moment to write your concerns, if any, that should be part of an overall comment that falls outside the (narrow) scope of the actual recommendations made by Westlake Consultants?
    Kindest regards,

    Olivier
  6. Like Tom, I haven't had time to digest the whole report, but I"ll expand on my concern with the call for more constituencies.

    The ICANN core value cited as the reason the Report provides for more constituencies is about broad participation in policy making.  The formation of more constituences is not the only way to expand participation, and it ignores the existence and role of the ALAC.  ALAC, with its representives from five regions, from a wide range of  language groups and myriad internet user groups is far better placed to provide that broad participation. A better and more achievable way to achieve the broad participation sought is to support and encourage ALAC members to engage in policy processes.

     

    1. Holly,

      I'm all for meaningful engagement through At-Large. And if the Transition provides for a real say for the At-Large, equal if not superior to the GNSO, I'm for cities working through them.

      To my understanding, in Westlake, the GNSO is the presumed upper hand in decision making, with At-Large, GAC, etc. advisory. If that doesn't change, than cities need a role in GNSO to effectively participate in ICANN processes.

      But to be clear, I'm for the At-Large assuming the leading role in the ICANN's decision making process. The Transition should provide a route for that eventuality.

      Best,

      Tom

  7. Comment from Christian de Larrinaga sent on 22 July 2015 at 22:02 UTC. 

    ==

    I have an observation based on the observation in the Westlake materials. The case is made that the GNSO is largely North American or European and male. Quite a bit of the follow on has been discussing how to increase participation from a broader section of the global community and so on, and whether GNSO has really engaged with that as a core agenda. All very worthy and important.  

    What is not mentioned or if it is has, is buried in the vast amount of guff; is that the entire gtld process in recent years has been dominated by the views, interests and expectations of that "constituency".

    What would I think be a useful response for an At Large body to make is to ask (remind) how many gtld registries and tld's are domiciled both legally and operationally in each of the ICANN regions both before and after the recent expansion of gtld space under the GNSO's auspices.  

    The underlying question to ask is whether the Westlake report may reveal a hidden pattern that ICANN GNSO is self-reinforcing the domain name business geo politically and whether that is underpinning the Westlake observation of the concentration of the GNSO constituency as North American and European. If so that would have deep consequences for ICANN to work towards a more balanced global distribution if gtld's are to be perceived as a global resource. 

  8. i did not comment before beaches my views related to GNSO review is maybe too radical to have any value. But I can share it here

    besides agree with Maureen  and many of your comments related to WG, my view is: this review  haven't touch the main problem which is the whole division of SO in ICANN. hence inside GNSO -

    I have talked about this at the alumni ( group of former board members) some time ago when this review started, but normally people are a little afraid about changes...

    I believe we should create one more SO for commercial users to allow the general business community to join ICANn with a more relevant status ( a place for other that are impact individual users but has no accountability to the society, as facebook, google , microsoft, apple, IBM etc etc etc  and become independent from the DNS business.  

    as USERS , they also depend, like individual users, on DNS industry services and shall be independent from them.  in this new community  we would have  non commercial together with them.  But even Non commercial needs a very important review. being for so many years in ICANN I do not see any really good work from NCUC.  

    I also believe NPOC- which is trying to do a better job,  shall be independent of NCUC, since they have no authority to select their members, for instance.

    As you see, fro me the whole work was very weak and had none or few value to GNSO.  Sorry for being not constructive.   kisses to all

  9. Comment from Roberto Gaetano sent on 23 Jul 2015 at 21:47 UTC. 

    ==

    If I remember correctly (and I really should, as I was the Chair of the GNSO Review WG as well as the Chair of the Structural Improvements Committee) one of the clauses of the deal was that the structure of the GNSO (i.e. the creation of the “Stakeholder Groups”) was going to be reviewed at the next iteration.

    R.

  10. Hello everyone,

    thank you very much for your comments which have been very helpful.

    I suggest appending the following text to the reply to Recommendation #23

     

    • The ICANN core value cited as the reason the Report provides for more constituencies is about broad participation in policy making.  The formation of more constituencies is not the only way to expand participation, and it ignores the existence and role of the ALAC.  ALAC, with its representatives from five regions, from a wide range of language groups and myriad internet user groups is far better placed to provide that broad participation. A better and more achievable way to achieve the broad participation sought is to support and encourage ALAC members to engage in policy processes.



    Also adding the following main text in the General Comments Section:

    --- cut here ---

    Whilst the ALAC support almost all of the recommendations made in the Westlake Report, the ALAC is concerned that the vast majority of the recommendations focus on GNSO Working Groups and suggest making small adjustments rather than taking a serious look at the GNSO Council's bicameral structure.

    Examples of areas for review are numerous and not limited to:

    • The current structure of the GNSO Council provides the ability for a more united vote in the Contracted Party House whilst fragmenting the Non-Contracted Party house to the point of imbalance. The unprecedented growth of Contracted Parties caused by the new gTLD Program has not been addressed. What might have been a homogeneous Constituency might now be more heterogeneous and the potential consequences of this change have not been studied. For example, City TLDs are an entirely new breed of Registry; so are Brand TLDs. How does this affect the current status quo? How would the people using City TLDs have their voice heard
    • Other commenters in the At-Large Community have noted that the proposals for more geographically balanced representation appeared to be focused on finding new participants from outside the GNSO’s usual territory. A question to ask is how many gTLD registries and gTLDs are domiciled both legally and operationally in each of the ICANN regions both before and after the recent expansion of gTLD space under the GNSO's auspices. The Westlake Review misses on the opportunity to potentially reveal a hidden pattern that the ICANN GNSO is self-reinforcing the domain name business geopolitically and whether that is underpinning the Westlake observation of the concentration of the GNSO’s constituencies as North American and European.
    • GNSO Working Groups are open for all participants including non-GNSO Constituency members – but the GNSO Council, thanks to its very structure, has the ability to affect a working group’s results. Voting is one of the ways to support or halt recommendations from a bottom-up PDP.

    The ALAC believes that the complex issues of GNSO structure and processes need to be studied now. The ALAC reminds the Reviewers of the At-Large Future Challenges Working Group R3 White Paper (http://www.atlarge.icann.org/correspondence/correspondence-01oct12-en.htm ) drafted in 2012 and containing proposals that should be explored.

     

    Reinforcing ALAC’s view is its recollection of several of its members that during the first GNSO Review, it was understood that Constituencies and the creation of “Stakeholder Groups” were going to be reviewed at the next iteration. Tragically, this is missing from the current report.


    --- cut here ---

    As we only have 24 hours until the closing of the comment period, please let me know ASAP if this is satisfactory.

    Kindest regards,

    Olivier

    1. Comment from Christopher Wilkinson sent on 24 July 2015 at 17:03 UTC 

      ==

      Olivier. Supporting your text, as a whole. Thankypu. +1 CW

  11. Comment from William Drake sent on 24 July 2015 at 19:52 UTC. 

    ==

    Hi 

    On Jul 23, 2015, at 12:02 AM, Christian de Larrinaga wrote:

    The case is made that the GNSO is largely North American or

    European and male.

    This applies only to the business parts of the GNSO, not civil society.  The authors of the report systematically demonstrated an inability to even bother to look at the web pages or mail list archives of NCSG, NCUC, and NPOC before making generalizations about them, relying instead on bits of hearsay from not quite disinterested actors who’ve been “on the other side” on various issues.  

    NCUC has 428 members from 101 countries, including 108 noncommercial organizations and 320 individuals http://www.ncuc.org/about/members/   We’ve not done a demographic breakdown lately but believe about half are from the global South.  NPOC lists about 60 organizational members, many from the global South http://www.npoc.org/?p=members2015june.   And there are some people who've joined the SG but neither constituency, I don’t have their numbers handy.  In any event, the numbers indicate that the CS part of the GNSO is not largely North American or European and male.

    Best

    Bill

  12. I suggest adding a new paragraph at the end.

    The ALAC is disappointed that the review has not evaluated to what extent the current GNSO Structure meets the GNSO and ICANN needs. The structure, with contracted parties representing half of the Council voting power, was invented as a result of the last GNSO review, prior to the New gTLD Program and before registries could own registrars. The ALAC is very concerned that the current structure may not be able to adequately address issues where the public interest is in conflict with the interests of contracted parties. This is essential in light of:

    ICANN's increased focus on the Public Interest (PI);

    the increased desire and need to be demonstrably accountable; and

    the recommendations of the Policy and Implementation WG which will require ALL policy issues to go back to the GNSO for resolution instead of being addressed at the Board level where Board members have a duty to balance stakeholder desires vs the PI.

    1. I'm happy with this - but please correct the second word - I think we are ALAC

      1. I think we are too. But my fingers apparently are not fully aware.

        Fixed.