Alan Greenberg is the GNSO Liaison for 2013-2014, 2012-2013, 2011-2012.
GNSO Council Meeting - 27 February 2014
Motions: https://community.icann.org/display/gnsocouncilmeetings/Motions+27+February+2014 - NOT YET AVAILABLE
MP3: http://audio.icann.org/gnso/gnso-council-20140227-en.mp3 - NOT YET AVAILABLE
Transcript: http://gnso.icann.org/en/meetings/transcript-council-27Feb14-en.pdf - NOT YET AVAILABLE
Minutes: http://gnso.icann.org/en/meetings/minutes-council-27feb14-en.htm - NOT YET AVAILABLE
Items meriting ALAC/At-Large focus: There were no decision items on the agenda, but some very good discussions. Listening to Sally Costerton's Internet Governance overview is worthwhile listening to. The briefing starts at about 10 minutes into the MP3 and runs for about 45 minutes (25 for the briefing and the rest for questions/comments). The translation/transliteration section is also worthwhile (although of less general interest) and quite short. The discussion on the strategy panels also merits review.
UPDATE & DISCUSSION – International Internet Governance Issues: Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. The update was done by Sally Costerton and was a (relatively successful) attempt to summarize all of the Internet Governance issues and putting them into perspective.
UPDATE – PDP Working Group on Translation & Transliteration of Contact Information: The GNSO Council recently initiated a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information. As part of its efforts to obtain broad input from the ICANN Community at an early stage of its deliberations, the Working Group has requested input from the Supporting Organizations (including the GNSO) and Advisory Committees on several questions relating to the issues identified in the PDP Final Issue Report.
UPDATE & DISCUSSION – GNSO Engagement with the work of the ICANN Strategy Panels: Here the Council will receive an update on any relevant interaction with and output from the strategy panels and discuss any appropriate action going forward.There has been considerable concern expressed among GNSO Councillors that the multi-stakeholder panel seems to be oblivious of the GNSO and its mandate.
UPDATE & DISCUSSION – GAC Engagement – the work of the Joint GAC / GNSO Consultation Group: An update and presentation of the recently agreed up charter for the group. The charter can be found at http://mm.icann.org/pipermail/gac-gnso-cg/attachments/20140212/c6e3f7b6/GAC-GNSO-final-0001.pdf.
GNSO Council Meeting - 23 January 2014
Items requiring ALAC/At-Large focus: CCWG Drafting team membership. Membership of Metrics and Reporting WG (name to be changed).
Chair, Review of Action Items: The new CCWG Drafting Team is about to kick off with the first meeting as soon as a week from now, so membership is crucial.
- Approve Council Recommendations Report on protection of IGO-INGO names and acronyms to the ICANN Board
- Confirm Chair and and Vice-Chairs of the Privacy & Proxy Services Accreditation Issues PDP working group namely Don Blumenthal (RySG) as Chair as well as Steve Metalitz (IPC) and Graeme Bunton (RrSG) as Vice-Chairs.
- Confirm Chairs of the Translation and Transliteration of Contact Information PDP Working Group namely Chris Dillon (NCSG) and Rudi Vansnick (NPOC) as co-Chairs..
MOTION – Metrics and Reporting Working Group Charter: The 2010 Registration Abuse Policies Working Group (RAPWG) identified the an issue relating to Uniformity of Reporting which it described as “need for more uniformity in the mechanisms to initiate, track, and analyze policy-violation reports.” The RAPWG recommended in its Final Report that “the GNSO and the larger ICANN community in general, create and support uniform [problem-] reporting [and report-tracking] processes.”
The GNSO Council recommended the creation of an Issue Report to further research metrics and reporting needs with the aim of improving the policy development process. The report created by ICANN Staff outlined accomplishments regarding reporting and metrics by the Contractual Compliance function and it also reviewed other reporting sources that may be of relevance.
The GNSO Council subsequently adopted a recommendation to form a non-PDP Working Group tasked with exploring opportunities for developing reporting and metrics processes and/or appropriate standardized methodologies that could better inform fact-based policy development and decision making.
I raised the issue that the name be changed since it does not reflect what the group will be about. That was accepted and the name will be changed by a small group (including me) in the next day or two prior to announcement and launching. The motion was approved subject to the name change.
INPUT & DISCUSSION – Prospective improvements to the Policy Development Process: The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community.
The Council has previously discussed a paper prepared by ICANN staff on potential improvements to the PDP process. The discussion is now encapsulated in a table form which has been revised through various discussions at council meetings and on email lists. The document now also includes reference to the related recommendations of the ATRT2.
The Council agreed to form a group to continue this work, particularly with a focus on items 3 & 5 in the table. Such a group was approved (without a formal vote).
UPDATE – GAC Engagement – the work of the Joint GAC / GNSO Consultation Group: The group (including the GNSO Chair, Vice-chairs and a few others on the GNSO side) and is working. They have a public mailing list, and so the work is not being conducted in secret (as was feared it would by some).
Update – Forthcoming review of the GNSO: As part of a periodic review process that is built into the ICANN model, ICANN board initiated reviews of the GNSO (and the GNSO Council and related functions) are expected. In order to be informed and effectively prepared for this work, we have begun to engage with the body that commissions such reviews (the structural improvements committee) through its chair, Ray Plazk.
The Council will track the planning work of the SIC and, where appropriate; provide relevant input to the process. We will also prepare to undertake a form of self-review in a similar format to that which we expect to arise out of the work of the SIC. A self-review will ensure that we are not only prepared for the board initiated work but also able to flag areas for potential improvement in as timely as possible a manner.
DISCUSSION – International Internet Governance Issues: Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. There was considerable concern with the volume of work and the difficulty with both keeping up on the governance issues as well as meking sure that other issues are not ignored. Avri volunteered to lead an effort to keep the ccouncil up to date (a summary report perhaps) and either Theresa Swineheart or Sally Costerton will be asked to do a brief presentation at the next Council meeting.
UPDATE & DISCUSSION – Planning for Singapore: Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, David Cake will lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council’s proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board.
There was a substantive discussion, particularly on the merits and utility of WG reports during the weekend session.
Any Other Business: Proposal to review SSAC reports and determine whether or not any recommendations impact on GNSO Consensus Policy.There was also a brief discussion (but no conclusion) on the concept of a Liaison to or from the SSAC.
GNSO Council Meeting - 12 December 2013
Minutes: http://gnso.icann.org/en/meetings/minutes-council-12dec13-en.htm - NOT YET AVAILABLE
Items requiring ALAC/At-Large focus: DSSA and improvements to the PDP process.
This was an extraordinary meeting. In recent years the GNSO Council has been reluctant to take any action without formal approval of the constituent bodies, and this had often meant that the GNSO Council is silent on important issues and/or cannot act in a timely manner. During this meetings, a tacit decision was made to move forward on three substantive issues, and it was done without a formal vote (ATRT2 comments, Geographic Regions and PDP Improvements).
Multi-stakeholder Innovation Panel and a concern that it heavily overlap with the activities of the GNSO, and the group itself may be uninformed of GNSO methodology, resulting in recommendations which may not be appropriate and the GNSO being perceived as reacting negatively. Chair, Review of Action Items: There was a short discussion related to the
MOTION – JIG Final Report on Universal Acceptance of IDN TLDs: The purpose of the joint ccNSO/GNSO Joint IDN Working Group (JIG) is to deal with issues related to the introduction of IDN ccTLDs under the IDN ccTLD Fast Track implementation process and with IDN gTLDs under the new gTLD implementation process which are of common interest to both the GNSO and ccNSO. The JIG was formed by mutual charters between the ccNSO and GNSO councils and then extended (ccNSO: http://ccnso.icann.org/workinggroups/minutes-council-23aug11-en.pdf | GNSO: http://gnso.icann.org/resolutions/#201107) to complete its work on the three identified issues of common interest between the ccNSO and GNSO. One of the three issues relates to the Universal Acceptance of IDN TLDs. The JIG has delivered its Final Report on Universal Acceptance of IDN TLDs on 17 November for GNSO Council consideration.
There was a lot of discussion about the importance of ensuring universal acceptance and its key import to the success of the related gTLDs and the new gTLD program in general. The tone of this discussion was that there is a significant level of concern that this will in fact be done well.
The motion passed unanimously.
MOTION – DNS Security and Stabilty and Analysis (DSSA) Working Group Final Report: In December 2010, the ALAC, ccNSO, GNSO and NRO (acting as ASO in this case) all endorsed the charter of the joint DNS Security and Stability and Analysis working group (DSSA WG) according to each of their own rules and procedures and as a result are the participating SO's and AC's in the DSSA. The DSSA delivered its Final Report to the chartering organisations on 11 November 2013.
The implicit recommendation of the report is that due to a conflicting process initiated by the Board, the DSSA is recommending that stage 2 actions considered by the DSSA NOT go ahead at this time. The suggestion was made that this be made explicit in the motion. This was addressed by modifying the motion to refer to the letter from the co-chairs to the Chairs of the chartering organizations, outlining the rationale for the position. The motion was adopted unanimously.
DISCUSSION – Written final input to the ATRT2: The Second Accountability and Transparency Review Team (ATRT 2), mandated by paragraph 9.1 of the Affirmation of Commitments (AoC), is completing its analysis and holding consultations with Community, staff and Board. To fully inform its work, the ATRT 2 seeks input from the Community on its Draft Report & Recommendations (and the Correction Issued 7 November 2013) compiled for the Community's consideration. Community participation is essential to the success of the review, and all input will be carefully considered. There was no objection to the details of the statement being refined and the statement being submitted on behalf of the Council (not indicating that it had explicit support of all of the SG/Constituencies).
DISCUSSION – Geographic Regions Review Working Group: The Geographic Regions Review Working Group was formed by the ICANN Board to (1) identify the different purposes for which ICANN’s Geographic Regions are used; (2) determine whether the uses of ICANN’s Geographic Regions (as currently defined, or at all) continue to meet the requirements of the relevant stakeholders; and (3) submit proposals for community and Board consideration relating to the current and future uses and definition of the ICANN Geographic Regions. A full record of the Working Group’s past reports and public workshops and presentations can be found at the Working Group's Confluence Wiki space.
At various times over the past few years, the ALAC, ASO, ccNSO, GAC and GNSO communities have supplied representatives to serve on the Working Group. These communities have had the opportunity to review and provide formal comments on the Working Group’s recommendations before being submitted to the ICANN Board. The recommendations are provided a Final Report which is posted here.
The Chair of the working group has now written to the GNSO indicating that the charter of the Working Group, as approved by the ICANN Board, requires that the Chair receive written notification (by 31 December if possible) from each of the organisations that contributed members to the Working Group before the Final Report can be submitted formally to the ICANN Board. The form of the notification could support, oppose or take no position on the recommendations of the working group.
A decision was generally agreed to that the Council will send a letter of support.
INPUT & DISCUSSION – Prospective improvements to the Policy Development Process: The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community. The Council has previously discussed a paper prepared by ICANN staff on potential improvements to the PDP process. The discussion is now encapsulated in a table form and now includes reference to the related recommendations of the ATRT2. Here the Council will discuss the table and aim to agree on concrete next steps.
There was a substantive discussion on many of the issues, and a decision was made to further refine the list and investigate options, likely with a group being formed to work with staff on this between GNSO Council meeting. This would e less formal that a traditional WG though.
GNSO Council Meeting - 31 October 2013
Items requiring ALAC/At-Large focus: None.
Chair: The GNSO Review, which was tentatively postponed, will be going forward next year, as the first of a new series of institutional reviews.
MOTION – Adoption of the Thick Whois Policy Development Process Final Report and Recommendations: The Final Report on Thick Whois has been prepared as required by the GNSO PDP in the ICANN Bylaws. The Final Report is based on the Initial Report of 21 June 2013 and has been updated to reflect the review and analysis of the Public Comments received by the Thick Whois Working Group, in addition to further deliberations. The recommendations are:
- The provision of thick Whois services, with a consistent labelling and display as per the model outlined in specification 3 of the 2013 RAA1, should become a requirement for all gTLD registries, both existing and future.
- Following the adoption of this report and recommendations by the GNSO Council, the subsequent public comment forum (prior to Board consideration) and the notification by the ICANN Board to the GAC, specifically request input on any considerations related to the transition from thin to thick Whois that would need to be taken into account as part of the implementation process.
- As part of the implementation process a legal review of law applicable to the transition of data from a thin to thick model that has not already been considered in the EWG memo2 is undertaken and due consideration is given to potential privacy issues that may arise from the discussions on the transition from thin to thick Whois, including, for example, guidance on how the long-standing contractual requirement that registrars give notice to, and obtain consent, from each registrant for uses of any personally identifiable data submitted by the registrant should apply to registrations involved in the transition. Should any privacy issues emerge from these transition discussions that were not anticipated by the WG and which would require additional policy consideration, the Implementation Review Team is expected to notify the GNSO Council of these so that appropriate action can be taken.
The motion carried unanimously among those present, but there were two Councillors absent who will have an opportunity for absentee voting, but the current threshold is sufficiently high to ensure its passing with a super-majority and thus go to the Board for their ratification.
MOTION – A charter for the Privacy & Proxy Services Accreditation PDP WG: ICANN staff prepared a paper to summarise the outcomes of the 2013 Registrar Accreditation Agreement (RAA) negotiations in order to set the scene for subsequent associated policy development work to be managed by the Council. This is an ICANN Board initiated PDP. The staff paper contained a draft charter for the PDP WG and the Council has discussed this. Refinements to the charter have been proposed as has a title for the PDP WG.
This item originally came out of the joint GNSO/ALAC group that was convened after the 2009 RAA was approved. The motion originally read that this was the last of the items out of that process that were illegible for the PDP process. In fact, it was the last of the items from that group that were deemed to be high priority, with other issues still potentially to be acted on. I requested that the motion be suitably changed to reflect this, and the change was accepted as a friendly.
The motion passed unanimously (among those present), despite some reservations on the part of two NCSG Councillors.
MOTION – To approve a charter for the Translation and Transliteration of Contact Information PDP Working Group: On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information and decided to create a PDP Working Group for the purposes of fulfilling the requirements of the PDP. Following a call for volunteers, a Drafting Team was formed and its members have developed a charter for consideration by the GNSO Council.
This motion was deferred from the last meeting with the understanding that the concerns were raised and discussed prior to this meeting. That was not done, but the concerns were raised at this meeting. They include the need to widen the charter to look at issues of whether such translation and transliteration is needed, who should pay for it, and several other issues.
I pointed out that in the absence of rules, registries and registrars have no basis on which to present IDN registration data in a 7-bit ASCII WHOIS system, The motion was voluntarily withdrawn to allow the charter to be reworked and resubmitted for the Buenos Aires meeting.
GNSO Council Meeting - 10 October 2013
Items requiring ALAC/At-Large focus or action are in red.
MOTION - To approve the report of the Whois Survey Working Group (WSWG): This report was published in response to a request by the GNSO Council for a report and analysis on a survey about possible technical requirements of a future WHOIS Service. The objective of the Working Group was to develop a set of proposed recommendations around the measurement of support of proposed technical requirements. After consideration of community input on a draft survey and the implementation of the Lime Survey software within the ICANN IT infrastructure, the survey was made available to the community in September 2012. ICANN staff compiled and consolidated the survey results and the WSWG completed the WSWG Final Report for delivery to the GNSO Council.
There was a concern raised that the number of respondants was small and could not be considered statistically representative. The report's recommendations were unanimously approved (which was just to pass the results on to other bodies).
Motion to approve the further development of a framework for cross community working groups: This motion seeks further develop a framework for cross community working groups by picking up the work of the drafting team which proposed a set of Draft Principles for Cross Community Working Groups (CCWGs) that were approved by the GNSO Council in March 2012. This work has had the benefit of subsequent review, comments and suggestions provided by the ccNSO. The motion here proposes that, in full cooperation with other SO/ACs,the GNSO Council jointly develops an updated set of principles for CCWGs taking into consideration the feedback provided by the ccNSO and in collaboration with other interested SO/ACs. The aim being to to create a framework applicable across all SO/ACs for the effective future functioning of CCWGs,
The motion was unanimously approved. It will be co-chaired by John Berard and an as yet unnamed ccNSO person. I indicated that the ALAC would be participating.
MOTION – To approve a charter for the Translation and Transliteration of Contact Information PDP Working Group: On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information and decided to create a PDP Working Group for the purposes of fulfilling the requirements of the PDP. Following a call for volunteers, a Drafting Team was formed and its members have developed a charter for consideration by the GNSO Council. The drafting team has submitted the charter and so the GNSO Council, having reviewed the charter, will vote on whether to approve it as submitted by the Drafting Team.
This motion was deferred until the next meeting due to concerns raised by the Registrar SG. It is unclear exactly what those concerns were or why they were not raised earlier in the process.
DISCUSSION – Policy issues surrounding string confusion: The Council previously discussed issues associated with the string confusion decisions that have been made recently e.g. relating to plural and singular versions of the same term and the contradictory decisions on identical strings. The Council agreed to write to the ICANN board and new gTLD programme committee and to consider appropriate additional action.
Christine Willet, VP, gTLD Operations spoke to the Council. The discussion starts at 45 minutes into the MP3 and continues for about 33 minutes.
UPDATE & DISCUSSION – A PDP for relevant policies on issues not dealt with during the course of developing the 2013 RAA: ICANN staff has prepared a paper to summarise the outcomes of the 2013 Registrar Accreditation Agreement (RAA) negotiations in order to set the scene for subsequent, relevant policy development work to be managed by the Council. This will be an ICANN Board initiated PDP.
Staff believes that the only substantive item left from the original GNSO/ALAC list (~2009) of needed RAA changes are those related to privacy and proxy services and this PDP is to address that subject. If the ALAC believes that there are other still pending issues, they should be raised.
GNSO Council Meeting - 13 June 2013
Items requiring ALAC/At-Large focus or action are in red.
MOTION - to Adopt Proposed Modification of the GNSO Operating Procedures Concerning the Deadline for the Submission of Reports and Motions: The change requires that reports and motions submitted for inclusion in a GNSO Council meeting agenda as soon as possible, but no later than 23h59 Coordinated Universal Time (UTC) on the day, 10 calendar days before the GNSO Council meeting. This tightens up the previous rule of "8 business days". The motion passed unanimously.
MOTION - Initiation of a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information: A Final Issue Report on the translation and transliteration of contact information was submitted to the GNSO Council on 21 March 2013 (see http://gnso.icann.org/en/library). Contrary to its initial recommendation, Staff now recommends that a PDP be initiated as it is expected that the work of this PDP will helpfully inform the deliberations of other efforts that are looking into gTLD registration data services such as the Expert Working Group (EWG) and the subsequent PDP. Also, as recommended by the WHOIS Policy Review Team, the Final Issue Report recommends that ICANN should commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to help inform the PDP Working Group in its deliberations. ICANN's General Counsel has confirmed that the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO. The motion carried unanimously.
DISCUSSION – Reconsideration request from the Non-Commercial Stakeholder group relating to decision on the Trademark Clearinghouse:
On the 19th April 2013, the Non-Commercial Stakeholders Group submitted a Reconsideration Request to the ICANN Board Governance Committee (BGC). On the 16 May 2013, the BGC Recommendation on the Reconsideration Request was published. Concerns have been raised within the Council about:
- The nature of the response to this particular request. Specifically in terms of the arguments presented within the response and the perceived or actual implications of these arguments on the workings of the multi-stakeholder model.
- More generally about the effectiveness of the reconsideration process.
I cannot do justice by summarizing the introduction to this discussion, but strongly suggest that everyone either listed to it or read it. The same is true for following discussion that follows. The discussion starts at minute 25 of the MP3 and goes until 1:26, and the transcript covers pages 17-57.
DISCUSSION – Forthcoming reviews of the GNSO and GNSO Council: It now appears that the Board Structural Improvements Committee may be delaying the review process, so a GNSO review may not take place as soon as expected. The GNSO will continue discussing what action, if any they will take at this time.
UPDATE & DISCUSSION – Report on User Experience Implications of Active Variant TLDs & IDN Letter to the Board: During its meeting in Beijing, the ICANN Board requested that, by 1 July 2013, interested Supporting Organizations and Advisory Committees provide staff with any input and guidance they may have to be factored into implementation of the Recommendations from the Report on User Experience Implications of Active Variant TLDs' (see http://www.icann.org/en/groups/board/documents/prelim-report-11apr13-en.htm#2.a). The Report on User Experience Implications of Active Variant TLDs examines potential challenges from a user experience perspective when variants of IDN TLDs are activated and offers recommendations to users to minimize risks and optimize the implementation. The GNSO itself will not provide any input but is suggesting that SG/Constituencies might wish to.
GNSO Council Meeting - 16 May 2013
Items requiring ALAC/At-Large action are in red.
MOTION - To address the Final Issue Report on the Uniformity of Reporting: At its October meeting last year the GNSO Council requested an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyse policy-violation reports. ICANN Staff was also explicitly requested to provide its recommendation(s) on how this issue can be further addressed outside of a PDP if recommendations in relation to this issue do not require consensus policies to implement. The Final Issue Report was presented to the GNSO Council in Beijing. The Council considered a motion to form a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the policy development process as outlined in the Final Issue Report. The GNSO did not initiate a Policy Development Process at this stage but will review at the completion of the ICANN Contractual Compliance three-year plan expected for 31 December 2013. The GNSO Council did create of a drafting team to develop a charter for a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the investigation. (Adopted unanimously)
A call for DT members will be issued.
MOTION - To adopt a revised Policy Development Process (PDP) Manual incorporating modifications to include the suspension of a PDP: Adopted unanimously.
MOTION - Initiation of a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information: A Final Issue Report translation and transliteration of contact information was submitted to the GNSO Council on 21 March 2013 (see http://gnso.icann.org/en/library). The Final Issue Report recommends that the GNSO Council should initiate a Policy Development Process (PDP) limited to the issues discussed in this report but delay the next steps in the PDP until the Expert Working Group (EWG) on gTLD Directory Services completes its recommendations, in May 2013 with a possible extension, in order to ensure that the resulting policy recommendations would be consistent with any new model or approaches to contact data that may result from the Expert Working Group's deliberations. As recommended by the WHOIS Policy Review Team the Final Issue Report also recommends that ICANN should commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to help inform the PDP Working Group in its deliberations.
The EWG indicated while in Beijing that their work would take considerably longer than expected, that there was no reason to delay this work, and in fact the work would help them.
One NCSG Council member felt the PDP should wait for the EWG, a position supported by an IPC Councillor who asked for a deferral until the next meeting, and this deferral was (automatically) granted.
UPDATE & DISCUSSION – Report on User Experience Implications of Active Variant TLDs & IDN Letter to the Board: During its meeting in Beijing, the ICANN Board requested that, by 1 July 2013, interested Supporting Organizations and Advisory Committees provide staff with any input and guidance they may have to be factored into implementation of the Recommendations from the Report on User Experience Implications of Active Variant TLDs' (see http://www.icann.org/en/groups/board/documents/prelim-report-11apr13-en.htm#2.a). The Report on User Experience Implications of Active Variant TLDs examines potential challenges from a user experience perspective when variants of IDN TLDs are activated and offers recommendations to users to minimize risks and optimize the implementation.
Presentation: http://gnso.icann.org/en/correspondence/presentation-variant-tlds-ux-16may13-en.pdf (Presented by Naela Sarras)
Input is requested on:
a) Which recommendations if any, are pre-requisites to the delegation of any IDN variant TLDs (i.e., delegation of IDN Variant TLDs should not proceed until these recommendations are implemented),
b) Which recommendations, if any, can be deferred until a later time, and
c) Which recommendations, if any, require additional policy work by the ICANN community and should be referred to the relevant stakeholder group for further policy work
Buenes Aires: Intent is to use the Friday following the ICANN week to "induct" new Councillors into the Council. Not obvious if open to old Councillors as well.
GNSO Council Meeting - 14 February 2013
Overview: Substantive issues of interest to At-Large included theseveral recent meetings, TMCH, IGO/INGO, Closed generic TLDs, Whois privacy/proxy study and ERRP.
INFORMATION & DISCUSSION – Recent meetings in Amsterdam & LA: Prior to a Ry/Rr briefing in Amsterdam, Council Chair and Vice Chairs met with ICANN staff, and found the process very useful. The discussions focused on Council management as well as the status of various issues and projects. The NCSG met in Los Angeles in the first ever inter-sessional House meeting along with ICANN staff. The long period between Toronto and Beijing was one of the driving rationales.The two SGs also met individually with Fadi.With the CSG, the subjects included the series of Roundtables and the IP rights strawman process.
UPDATE & DISCUSSION - Trademark Clearinghouse (TMCH) Strawman Proposal and Defensive Registrations: ICANN’s CEO has requested GNSO Council input on the Strawman Proposal developed through the TMCH related implementation discussions. The discussion focused on the draft letter to be sent staff on the GNSO position, with a focus on trying to get it to accurately reflect Council (or SG) positions. I did intervened saying that it was good to get that letter out, but Council should start to discuss how to develop policy at least for the issue that even ICANN says is policy.
IUPDATE & DISCUSSION – Board requested advice on second level protections for certain IGO names and acronyms: Council got an extensive update on the PDP. A letter will be drafted in reply. I suspect the ultimate answer will be that there is no consensus from the GNSO on a rationale to stop the Board action, but there are some people who feel that taking interim action while a PDP is running is not in the Public Interest.
INFORMATION & DISCUSSION – The issue of "closed generic" TLDs: The New gTLD Program Committee recently directed the ICANN CEO to request the GNSO to provide guidance on the issue of "closed generic" TLDs, concurrent with the opening of the public comment forum and if the GNSO wishes, to provide such guidance. Guidance on this issue is requested to be provided by the close of the public comment forum. (7 March). It was pointed out that the issue had been discussed and was was closed with the current outcome. Many of the decisions were ultimately made by staff (ie response to question: what if Kraft applies for .food - answer was it was ok).
UPDATE & DISCUSSION - Whois Privacy and Proxy Relay and Reveal Study: At the ICANN Meeting in Toronto, Lyman Chapin presented the results of the survey that evaluated the feasibility of conducting a future in-depth study into communication Relay and identity Reveal requests sent for gTLD domain names registered using Proxy and Privacy services. The Council must consider whether to go ahead with the study. One question is whether the study should be done, but delayed until the Directory Services Expert Working Group does its work. I voiced the opinion that the Expert Panel would lead to a PDP, and the accreditation of privaly/proixy services as well, so might as well start the study - they always take longer than planned.There was some concern expressed about staff making decisions prior to the study being completed wasting the money on the study. Clarification would be sought and the issue discussed in Beijing.
Any Other Business: I raised the issue of the long delays in implementing PEDNR, as asked for a report (almost 4 years since GNSO initiated the PDP, 10 months since GNSO approval, 14 months since Board approval, 2 months since comment period closed). Staff sadi that an announcement will likely be made in about 2 weeks.
GNSO Council Meeting - 21 January 2013
This was a one-topic meeting to formally endorse the GNSO STRT-2 candidates. The rules call for each SG to endorse one candidate and up to two additional candidates endorces by the GNSO as a whole. The candidates are supposed to have no more than half of the nominees from one region and not all of the nominees should be of the same gender. To endorse the additional candidates requires the support of 60% of both houses.
The Registries SG have supported all three applicants but since they can only formally endorse one, they have endorsed Brian Cute.The Registrar SG has endorsed the only candidate that applied to them, Thomas Barrett. The CSG and NCSG has not yet formally endorsed anyone, although some parts of the CSG have selected Michael Roberts.Nominations were due by the 24th, but given that there is a Ry/RR meeting in Amsterdam this week, and a CSG meeting in Los Angeles nest week, the GNSO call was scheduled for today.
The CSG and NCSG have been given until midnight of January 24 to make their endorsements. There will then be an e-mail ballot to potentially endorse any additional candidates. It appears that given the candidate list, the GNSO self-imposed geographic diversity rule will not be met, and it is possible the gender rule will not be met as well.
The overall applicant pool is:
|Thomas Barrett||M||North America||RrSG|
|Brian Cute||M||North America||RySG|
|Avri Doria||F||North America||NCSG|
|Sarah Falvey||F||North America||RySG|
|Scott Blake Harris||M||North America||RySG|
|Marie-Laure Lemineur||F||Latin America||NCSG|
|Michael Roberts||M||North America||CSG|
Full application details can be found at http://www.icann.org/en/about/aoc-review/atrt/2/applications
GNSO Council Meeting - 17 January 2013
Overview: Substantive issues of interest to At-Large included IRTP-D PDP Initiation and Charter, TMCH Strawman, Response to GAC letter on IGO/INGO protections, discussion of ATRT-2 selections and a discusson on Policy vs Implementation. Items requiring ALAC/At-Large action are in red.
Initiation of a Policy Development Process (PDP) on the Inter-Registrar Transfer Policy (IRTP) Part D: IRTP, Part D includes six issues:
- Whether reporting requirements for registries and dispute providers should be developed, in order to make precedent and trend information available to the community and allow reference to past cases in dispute submissions;
- Whether additional provisions should be included in the TDRP (Transfer Dispute Resolution Policy) on how to handle disputes when multiple transfers have occurred;
- Whether dispute options for registrants should be developed and implemented as part of the policy (registrants currently depend on registrars to initiate a dispute on their behalf);
- Whether requirements or best practices should be put into place for registrars to make information on transfer dispute resolution options available to registrants;
- Whether existing penalties for policy violations are sufficient or if additional provisions/penalties for specific violations should be added into the policy;
- Whether the universal adoption and implementation of EPP AuthInfo codes has eliminated the need of FOAs.(Forms of Authorization - standardized forms for registrars to request and confirm transfers)
The Council unanimously approved the PDP.
Approval of a Charter for the Inter-Registrar Transfer Policy (IRTP) Part D Working Group: Normally, when a PDP is initiated, the Council convenes a DT to draft a charter for the work to be carried out. In this instance, in the interest of efficiency and because the issues laid out in the IRTP-D Final Issues Report were very precise, Council adopted the charter as proposed and request that this work be started by a WG asap. A call for WG participants will be made shortly.
UPDATE & DISCUSSION - Trademark Clearinghouse (TMCH) Strawman Proposal and Defensive Registrations Discussion: The discussion started of discussion the draft letter which essentially focused on the concept that the GNSO is the policy formulation body and thus the strawman is to a large extent not relevant, since it was created by an ad hoc group. By the end of the discussion, there was a strong acceptance that for the issues that either staff or large parts of the GNSO deem to be policy, the GNSO does have an obligation to start expedited policy work on those areas. The discussions will continue.
UPDATE & DISCUSSION - Response to the GAC Letter: The GAC has sent a letter to the GNSO Council with regard to the initiation of a PDP on the IGO/INGO issue, and specifically requesting a rationale for undertaking a PDP i.e. an explanation as to why GNSO believes this issue should be evaluated through a PDP rather than simply executed as an implementation process. The Council has sent an initial response and now needs to move ahead with developing a full response. A letter was drafted by Neustar which people generally thinks is a good start (as do I), particularly if some history and background is attached. Work will continue.
UPDATE & DISCUSSION - ATRT2 Developments: There are 8 applications. The GNSO has told the selectors that they would like to see at least 4 selected, giving representation to each SG. The GNSO rules call for them to endorse one candidate per SG, plus up to 2 more If they can get a 60% vote from BOTH houses), no more than half (of the 4 I think) from any one region, and not all of the same gender. A meeting is scheduled for January 21 to finalize selections.
INFORMATION & DISCUSSION – Policy vs. Implementation: The recent letter from the GAC as well as activities relating to work on the Trademark Clearinghouse, highlights a broader issue regarding the boundary between policy development and implementation work as well as the effective integration of policy development and integration work from the outset. Recent discussions on the Council mailing list indicate that there is an interest to undertake further work on this issue. At the same time, ICANN Staff has published a paper that is intended to facilitate further community discussions on this topic.
GNSO Council Meeting - 20 December 2012
Overview: This was a meeting with significant substance and might be worth listening to. Substantive issues of interest to At-Large included RCRC/IOC protections, Consumer Trust, TO BE COMPLETED
Second Level Protections for certain International Olympic Committee/Red Cross Red Crescent (IOC / RCRC) names in the first round of New GTLDs: This is the motion for temporary protection of IOC/RCRC at the second level pending the completion of the longer term PDP. This motion failed at the last GNSO meeting due to a procedural problem. The recommendations is to some extent less important due to the recent Board decision on temporary protections. There was also a substantive discussion of the occurrences of the last meeting including the chair's actions, the concept of conflict of interest, and the in particular the concept of re-submitting a motion that had previously failed. This latter issue was quite divisive and I think merits some discussion within the ALAC (and outside of the rules of procedure revision process). The motion passed with all Councillors voting for the motion, except for the NCSG (5 nos and 1 absent with counts as an abstention which counts as a no).
MOTION - Consumer Trust: The advice letter of the Consumer Choice, Trust, and Competition WG incorporating the changes which caused it to be withdrawn last time was discussed. Wendy Seltzer suggested that the GNSO pass the letter to the Board but not endorse it. Her rationale can be heard at about 1 hour into the MP3 or in the transcript (and can be found in a minority report of the WG). The amendment was not taken as friendly and did not pass. Wendy further made a motion to replace her minority vote with the full version in lieu of the WG summary of it. It was not considered friendly. Jeff suggested that instead of amending the motion, her comments could be included as a Councillors statement and this was accepted.
Jeff, who initiated the changes, thanked the group for its flexibility in revising the report following its original final report.
Suspension of a Policy Development Process – Proposed revision of the GNSO PDP Manual: The PDP process already allows for termination for a variety of reasons (deadlock, changed circumstances, lack of participants). This proposed change added the ability to temporarily suspend a PDP for the same reasons. The motion was withdrawn because it was recently recognized that there were potential problems with suspending (or terminating?) a PDP which had been mandated by the Board. There was some confusion due to an error in recording one vote, but the motion passed with all NCSG Councillors either voting no or being absent.
Trademark Clearinghouse (TMCH) Strawman Proposal and Defensive Registrations Discussion: ICANN’s CEO has requested GNSO Council input on the Strawman Proposal recently developed through the TMCH related implementation discussions, that has been posted for public comment http://www.icann.org/en/news/announcements/announcement-30nov12-en.htm . ICANN’s CEO additionally requested Council input on the joint proposal from the Business Constituency/Intellectual Property Constituency (BC/IPC) for a “limited preventative registration mechanism” which is also currently available for public comment. Related to this discussion is the Staff briefing paper http://gnso.icann.org/en/node/32287 to the GNSO Council on the topic of defensive registrations at the second level, in response to a previous request from the New GLTD Committee (2012.04.10.NG2). The New GTLD Committee requested the GNSO to consider whether additional work on defensive registrations at the second level should be undertaken. The Council is to discuss: (i) a response to the ICANN CEOs request, and (ii) to consider whether to undertake any additional work related to the BC/IPC proposal and/or the Staff briefing paper, on the topic of second level defensive registrations.
Margie Milam summarized the issues. There followed a good discussion with some people supporting the letter that Mason Cole drafted (http://atlarge-lists.icann.org/pipermail/alac/2012/002752.html), some saying that any letter from the GNSO must reflect the entire Council (enen if undivided). I made a statement saying that I and ALAC were not happy with the process followed, but that we felt that the type of flexible and open meetings would be crucial to good decision making on difficult issues (as was demonstrated by STI). But that it was preferable if the initiative came more from the GNSO. This has (reasonably) been described as a critical moment in recognizing (or changing) whether the GNSO is or is not the prime gTLD policy development organization in ICANN. No action was taken, but it looks like there will be a number of outcomes including a short statement on the role of the cCouncil and a more substantive response on the substance.
UPDATE - Response to the GAC Letter: The GAC has sent a letter to the GNSO Council with regard to the initiation of a PDP on the IGO/INGO issue, and specifically requesting a rationale for undertaking a PDP i.e. an explanation as to why GNSO believes this issue should be evaluated through a PDP rather than simply executed as an implementation process. This letter and recent activities related to work on the Trademark Clearinghouse, highlights a broader issue regarding the boundary between policy development and implementation work as well as the effective integration of policy development and integration work from the outset.
Neustar had drafted a possible statement and can be found at http://gnso.icann.org/mailing-lists/archives/council/msg13928.html. There was a good discussion of the content and other options. A formal response from the GNSO is targeted for mid-January, with an immediate heads-up to the GAC Chair saying that the silence so far is not equivalen tothe GNSO ignoring them.
ATRT2 Developments: The call for applicants to serve on the next Accountability and Transparency Review Team (ATRT) has been extended until 14 January 2013. (See: http://www.icann.org/en/news/announcements/announcement-03dec12-en.htm ). The GNSO has asked for 4 members (one per SG) and for additional time to make endorsements. So far, with the delayed application period ending on Jan 15, and the next GNSO COuncil call on Jan 17, the timing is problematic. A special call will likely be held (as it was for ATRT-1).
LIVE EDITING STOPPED HERE - WILL BE COMPLETED LATER
INFORMATION - GNSO Council Review and SIC Update: In Toronto, the Chair of the SIC provided an overview of a new framework for future independent review efforts at ICANN. The GNSO was used as a case study to describe the effort because it is the first Supporting Organization lined-up in the next review cycle. Staff will brief the Council on the set of criteria metrics for GNSO Stakeholder Groups and Constituencies, and the work underway to develop metrics for the Council and the Working Group Model of policy.
Any Other Business: xx
GNSO Council Meeting - 20 July 2012
Overview: Substantive issues of interest to At-Large included 2nd level defensive registrations under the new gTLD, Inter-Governmental Organization name protections, Thick Whois for Verisign registries, The Whois Review team Report, Fake renewal notices and the upcoming GNSO review.
Defensive registrations and IGO names: Discussion of opening a comment period on the briefing paper, merging this with IGO issue into a single IR. No conclusion was reached, and the discussion will continue,on te list and presumably at the next Council meeting. It is conceivable that despite the lack of decision on the part of the GNSO Council to merge the two issues together, staff might include as one option for the PDP to widen it to include the more general 2nd level protection case.
Thick Whois: The DPD on Thick Whois for Verisign had been put on hold pending the signing of the .com contract renewal. Since the Board approved the renewal in Prague, the GNSO has now taken the PDP off hold and is asking for volunteers to draft the PDP WG Charter.
There is the potential that this charter may, instead of being narrowly focused on the original issue, be widened to look at whether all registries should adopt the thin model, or perhaps some other third option apply to all registries. If we do not want that to happen, we need to get involved in the drafting team.
Whois review team board request: The Board has asked for advice regarding how it should respond to the Whois Review Team Report with replies due by 31 August. Opinions on the GNSO variy, with NCSG taking the most extreme position that the recommendations are policy and that requires GNSO Policy development. Others agree that the issues need to be addressed on a one-by-one basis. Staff said that some of the issues might be addressed through multiple means including policy development or contract negotiations or other means.
The ALAC needs to consider whether it replies to the Board or not (over and above the ALAC comment on the report).
Fake Renewal Notices: There was some support for a fast-track PDP on the issue. The current state is that Mason Cole (who supported the fast-track PDP concept) will confer with the registrars and see what options they can offer. In particular what can be done regarding the apparently one bad actor involved.
GNSO Review: A review of the GNSO is scheduled to start next year, and has been the subject of several discussions. Some fee, as I do, that this is about the worst time for a review, given that it will be evaluating the GNSO just before the impact of new gTLDs is felt, and that by the time the review results are implemented, the GNSO may be in a very different situation. Others feel that since change is coming, it is the best time for a review because reviews are the opportunity to change. In my mind, the latter belief puts a bit too much faith in the skills of the reviewers to be able to see into the future.
GNSO Council Meeting - 10 May 2012
Overview: Substantive issues of interest to At-Large included Best Practices for addressing abusive registrations; update on the new PDP process; International Olympic Committee/Red Cross Names Drafting Team; ongoing JAS efforts; cancellation of Friday Board meetings; ICANN Academy and Rework of URS. On an agenda which rarely has substantive Any Other Business, the last three items mentioned here were all AOB. Several items on the agenda were deferred until the next meeting - an increasingly common occurrence.
Best Practices for addressing abusive registrations: Following the recommendation of the Registration Abuse Policies (RAP) Working Group, the GNSO Council requested a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registrations of domain names. The discussion paper recommended the creation of two Working Groups, one to establish the framework for best practices and one to propose candidate best practices to address the abusive registration of domain names. The motion on the table would set up a drafting team to create the charter for these groups. As you can tell from the history, this issue has been discussed for some time now, with Best Practices being the current incarnation.
There was a request to defer this motion to the next GNSO Counsel meeting, but there was a reasonable discussion prior to the deferral. The Registries SG felt that the motion was premature given the large number of other efforts that are underway that are somewhat related to this one. It was also pointed out that once the new gTLD applications are made public, Question 28 asks applicants about their proposed abuse prevention & mitigation - so waiting until this information was available might be wise. All parties agrees that the month delay would give an opportunity for the various factions to talk and perhaps come to a suitable agreement.
Update on the new PDP process: This was a presentation scheduled for Costa Rica and deferred twice due to lack of time. The PDP process is a complex one, and one that some people find a hard time understanding. This presentation is EXCELLENT and serves to make the multi-step PDP process much easier to understand (it was created by graphics designer Tom Hodgson in case we need some spiffy graphics in the future).
A discussion followed largely focused on how long a PDP must take and whether their are any options for fast-tracking a PDP. The current answer is that a PDP can take no less than about 9 months, and now probably closer to 11 months since the Public Comment period minimum duration has been increased. I repeated the position that the ALAC has taken that the Council should develop a faster method for cases where there is little disagreement between the various stakeholders.
International Olympic Committee/Red Cross Names Drafting Team: The issue of whether the current IOC/RC Drafting Group should continue its work or not was up for discussion. The focal point was whether the current drafting team should continue its work (now working on what if any special protections the IOC/RC should have at the 2nd level for the first round of new gTLDs. Some Councillors felt that the PDP that is being discussed on the more general protection of inter-governmental organizations should take the place of the current DT. Others felt the DT should continue its work, since the PDP will not likely result in any outcome soon enough for the first round (see previous item). Among those who felt the work needed to continue, there was some belief that the DT itself was not the correct body to do the work. A letter is being drafted but at the time of this writing (late 10 May), it is not quite clear what that letter will say, and if the DT will continue or not.
Ongoing JAS efforts: The issue was a concern of some Councillors that the JAS WG, by meeting with staff and making recommendations on how the implementation should proceed, and in fact by volunteering some members of the WG to actively participate in the selection process, the JAS WG had overstepped its mandate. I put forward my personal position (since this has not been actively discussed by the ALAC or ExCom) that the JAS group was working properly under its current extended mandate to interact with staff during the implementation, and that the only possible problem was that it should also pass its recommendations back through its chartering bodies. No decision was taken and the discussion will no doubt continue online and at the next GNSO Council meeting.
Cancellation of Friday Board meetings: There was a lively discussion on the issue of the cancellation. Some felt that the shortened week was great. Others thought that if the Board meeting was cancelled, the time should productively be used for other things. There was a great concern over the apparent lack of transparency regarding how the Board makes its decision and concern that without even the token open Board meeting, the ability of the community to judge its Board members (and particularly to judge those who are eligible for reappointment) was compromised.
ICANN Academy: There was minimal time left for this discussion, but there was a general feeling that this was a good thing (after it was explained - again). There was still concern about under whose auspices this is being done, who will fund it, and so forth. A letter is being drafted to be sent by Stéphane that will no doubt identify these concerns.
Rework of URS: The issue is that a rework of the URS to lower its cost to participants was "announced" within the budget document. Since the URS had been created by a GNSO group (with At-Large participation), it was strongly felt that the GNSO should have been explicitly informed ahead of time. The budget document said that "summits" would be held to discuss the issue. A note from Kurt Pritz before the meeting (he could not attend) said that despite the words in the budget document, the revision process would be a bottom-up one and the GNSO would pay a major role in it. A letter will be sent to Steve Crocker making it clear that t he GNSO believes that this should be a GNSO-led operation.
GNSO Council Meeting - 12 April 2012
Overview: Substantive issues on interest to At-Large included the Thick Whois PDP, a request for an Issue Report on the protection of names and acronyms of International Governmental Organizations, the .com contract renewal, a report from ICANN Compliance, and an update on the RAA Final Issue Report and the status of RAA Negotiations.
Thick Whois PDP: At its March 14th meeting, the GNSO Council voted to initiate a PDP on the issue of requiring all registries to implement a Thick Whois (currently all registries and planned registries do use thick Whois with the exception of those operated by Verisign). The intent of the motion was to defer any further work (ie taking a drafting team with developing a PDP charter) until after the .com contract is revised. The rationales included the possibility that Thick Whois might be included in the contact, Council and Staff workload, and the concept that there should not be a PDP to address an issue with one registry operator. On the last item, I pointed out that the Domain Tasting PDP was essentially that, and the Registries had no problem at that time. Staff indicated that resources were available at this time to undertake the PDP. Of particular interest was the comment that although the Registry SG was in favour of the deferral, Verisign was not and would prefer to have the PDP start immediately. After significant revision, the motion defers any further work on the PDP until the first Council meeting after Nov. 30th. The .com contract negotiation was no longer referenced in the motion, although it was implied by the deferral date. The motion passed unanimously. Conceivably, the Council could defer again in December, but I do not think that is too likely (but certainly possible, all the more so if staff resources are tight at that time).
Request for an Issue Report on the protection of names and acronyms of International Governmental Organizations: There were two competing motions on this issue, one from A NomCom appointee and once from the NCSG. Ultimately they were came to an agreement and a single motion was voted on requesting an Issue Report on:
- Definition of the type of organizations that should receive special protection at the top and second level, if any; and
- Policies required to protect such organizations at the top and second level.
I had two comments on this. First, I felt that the word "definition" was too prescriptive, since one of the likely outcomes would be to put that responsibility on the GAC. My other concern was that starting this initiative in parallel with the current one to look at Red Cross/IOC protections at the second level for the first round would be duplicating work, and putting an unreasonable load on the people, many of which would be involved in both groups. There was agreement with changing the word Definition by the motion presenter, but intimately it fell through the cracks (the problem with a Liaison not having the right to move such a change. The motion passed.
Report from ICANN Compliance: This was a report from Maguy Serad on existing systems, improvements and changes made since the reporting group report, improvements and changes foreseen in the near future and gaps. The report can be found at http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-uniformity-16mar12-en.pdf. The presentation can be heard on the MP3, starting at 1 hour and 12 minutes and running for about 14 minutes.
.com Contract Renewal: This was a short discussion raised by Jeff Neuman who felt that the inclusion of the reference to the Thick Whois PDP in the preamble to the .com agreement Public Comment was taken out of context. I tended to agree with him, but there was no general wish in the GNSO Council to make a comment on it.
Update on the RAA Final Issue Report and the status of RAA Negotiations: This was a presentation scheduled for Costa Rica but the Council had run out of time. It starts at 1 hour and 42 minutes into the MP3 and goes for about 16 minutes (somewhat garbled at the end). The report documents are RAA Drafting Team Negotiation Summary-GNSO Final.pdf and raa negotiations progress report 01Mar2012
GNSO Council Meeting - 19 January 2012
Overview: Once again, a very heavy agenda, and although some items significantly exceeding their alloted time, the meeting overall completed a few minutes early. Substantive issues on interest to At-Large included the Whois Review Team Report, two UDRP motions, Cross Constituency Working Groups, a discussion of outreach and time allocation in Costa Rica. Note that Transcripts are now available for GNSO Council meetings in addition to MP3 recordings.
Whois Review Team Report: An interesting presentation. Although Review Team members could not present due to limited access, the Chair, Emily Taylor was present. The presentation is at http://gnso.icann.org/correspondence/presentation-whois-policy-draft-report-19jan12-en.pdf. I would strongly suggest that the ALAC get such a briefing at its February meeting (prior to Costa Rica). As a measure of the level of detail and interest, the agenda item had 10 minutes allocated and 34 used.
IRTP-B PDP - Rec 8: The recommendation related to standardizing and clarifying WHOIS status messages. Staff have provided a proposed implementation. The IPC submitted a comment on it and staff have agreed that it was sufficiently substantive as to warrant a review of the proposed implementation. Accordingly the motion to approve was deferred.
IRTP-B PDP - Rec 9, part 2: This recommendation requested a new provision on when and how domains may be locked or unlocked. Staff prepared a proposed implementation plan and it was unanimously approved.
Cross Constituency Working Group Principles: As has been discussed on At-Large and ALAC lists, many GNSO Council members believe that future Cross Constituency Working Groups (CCWGs) should operate under set rules. In preparation for entering into discussions with other SOs and ACs, the GNSO charged a Drafting Team with developing a set of principles that the GNSO believed were important. The DT (in which I participated at the express wish of the GNSO) fulfilled its mandate and the principles were brought to the Council for discussion and possible approval. Note that if approved, they would simply be a starting point for discussion with other groups and not an end point. One point in particular, wheher multiples charters should be allowed at the start of a WG, has generated significant discussion. Due to the Chair of the DT not being present, and the NCSG being in the midst of a discussion of the issue, the issue was not voted on at this meeting. It will be brought back to the GNSO for face-to-face discussion during the weekend preceding the Costa Rica meeting, and voted on at the Wednesday GNSO Council meeting.
Outreach: The GNSO Improvements Report as approved by the Board Governance Committee required additional outreach to get more people involved in the GNSO. The GNSO charged a working group with coming up with a plan, and after long discussions, it did so. The recommendations were voted on by the GNSO Council on 17 November 2011 and the motion was defeated. This meeting discussion is the follow-on. There was a very lively discussion, regarding what should be done next (if anything). Opinions were very mixed. It was suggested that at the very least, the GNSO needed to formally decide to not do any further outreach as a Council, as it was a SG/Constituency responsibility. The discussion was deferred until a face-to-face discussion in Costa Rica.
AOB: The outline of the agenda for Costa Rica was presented. There was a strong comment made that the weekend had become far to heavily loaded with reports, and insufficient time was devoted to policy discussion and preparation for meetings later in the week. In Dakar that had resulted (to some extent) in the GNSO Council going into several meetings with other groups without sufficient preparation. A personal comment (not made at the meeting (this meeting's deferral of two issues until Costa Rica shows the value of face-to-face discussion and that time needs to be used wisely - a message that At-Large also needs to take to heart).
GNSO Liaison Reports 2010