[council] Draft Agenda for the GNSO Council Teleconference 23 January 2013.
Klaus Stoll
kdrstoll at gmail.com
Wed Jan 15 08:05:27 UTC 2014
Dear Friends
Greetings. I would like to second this suggestion, but I would ask if we
could find adequate time and format for this discussion. I am afraid
half an hour here or there will not result in much.
Yours
Klaus
On 1/14/2014 11:24 PM, john at crediblecontext.com wrote:
> Glen & Councillors:
> There has been quite a lot of discussion inside the Business
> Constituency about the three ongoing initiatives wrapped around the
> issue of Internet Governance. Normally, I would not seek to raise
> such a seemingly parochial matter, but a report from the BC Chair
> about a recent meeting Fadi had with SO and AC leaders suggests there
> is reason for us to take up the matter. According to the report, there
> is concern that the representation is not international enough; that
> the volunteer base is too U.S. and/or European.
> Personally, I don't think you can force people to participate (witness
> the working group conundrum), but if the eyes of the world are
> looking, it might be best if the eyes of the world were looking back.
> Can we add a discussion about Internet Governance to this agenda?
> Cheers,
> Berard
>
> --------- Original Message ---------
> Subject: [council] Draft Agenda for the GNSO Council
> Teleconference 23 January 2013.
> From: "Glen de Saint Géry" <Glen at icann.org>
> Date: 1/14/14 1:08 pm
> To: "council at gnso.icann.org" <council at gnso.icann.org>
>
> Dear Councillors,
>
> Please find the proposed Agenda for the GNSO Council
> Teleconference 23 January 2013.
> https://community.icann.org/display/gnsocouncilmeetings/Agenda+23+January+2014
>
> This agenda was established according to the GNSO Council
> Operating Procedures approved 13 September 2012 for the GNSO
> Council and updated.
> <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf >
> For convenience:
>
> * An excerpt of the ICANN Bylaws defining the voting thresholds
> is provided in Appendix 1 at the end of this agenda.
> * An excerpt from the Council Operating Procedures defining the
> absentee voting procedures is provided in Appendix 2 at the
> end of this agenda.
>
> Meeting Times 18:00 UTC
> *http://tinyurl.com/otro8aq*
>
> Coordinated Universal Time 18:00 UTC
> 10:00 Los Angeles; 13:00 Washington; 18:00 London; 19:00 Brussels;
> 02:00 Perth
>
> Dial-in numbers will be sent individually to Council members.
> Councillors should notify the GNSO Secretariat in advance if a
> dial out call is needed.
>
> *GNSO Council meeting audiocast*
> http://stream.icann.org:8000/gnso.m3u
>
> Item 1: Administrative matters (10 mins)
>
> 1.1 Roll Call
> 1.2 Statement of interest updates
> Bret Fausett
> https://community.icann.org/display/gnsosoi/Bret+Fausett+SOI
> 1.3 Review/amend agenda
> 1.4. Note the status of minutes for the previous Council meeting
> per the GNSO Operating Procedures:
> Minutes of the GNSO Council meetings 20 November 2013
> <http://gnso.icann.org/mailing-lists/archives/council/msg15531.html>
> part 1 and part 2
> <http://gnso.icann.org/mailing-lists/archives/council/msg15532.html>
> will be posted as approved on 23 January 2014.
> Minutes of the Council meeting 12 December 2013
> <http://gnso.icann.org/mailing-lists/archives/council/msg15533.html>
> will be posted as approved on 23 January 2014.
>
> *Item 2: Opening Remarks / Review of Projects & Action List (10 mins)*
>
> Review focus areas and provide updates on specific key themes / topics
>
> Include review of Projects List
> <http://gnso.icann.org/meetings/projects-list.pdf>and Action List
> <https://community.icann.org/display/gnsocouncilmeetings/Action+Items>.
>
> Comments or questions arising.*
>
>
> ***
>
> *
> *
>
> *Item 3: Consent agenda (5 mins)
>
> *
>
> 3.1Approve Council Recommendations Report on protection of
> IGO-INGO names and acronyms to the ICANN Board
>
>
> Item 4: MOTION – Metrics and Reporting Working Group Charter
> (15 mins)
>
> 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
> <http://gnso.icann.org/en/issues/uofr-final-31mar13-en.pdf>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.
>
> Here the Council vote on whether to approve the Charter of the
> Metrics and Reporting Working Group.
>
> 4.1 - Review the Motion
> 4.2 - Discussion
> 4.3 - Vote (voting threshold – simple majority vote of each house)
>
> **
>
> *Item 5: INPUT & DISCUSSION – Prospective improvements to the
> Policy Development Process (15 mins)*
>
> 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
> <http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf>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. Here the Council will aim to agree
> concrete next steps including the requirement to form a group to
> continue this work, particularly with a focus on items 3 & 5 in
> the table.
>
> 5.1 – Review of table of prospective PDP Improvements
> <http://gnso.icann.org/en/drafts/pdp-improvements-table-08jan14-en.pdf>(Marika
> Konings)
> 5.2 – Discussion
> 5.3 – Next steps
>
> *Item 6: UPDATE – GAC Engagement – the work of the Joint GAC /
> GNSO Consultation Group (10 mins)*
>
> Here the Council will receive an update and discuss any action
> going forward.**
>
> 6.1 – Status update (Jonathan Robinson)
> 6.2 – Discussion
> 6.3 – Next steps**
>
> *Item 7: Update – Forthcoming review of the GNSO (10 mins)*
>
> 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.
>
> 7.1 – Update (Jennifer Wolfe)
> 7.2 – Discussion
> 7.3 – Next steps*
>
> Item 8: UPDATE & DISCUSSION – Planning for Singapore (10 mins) *
>
> 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.
>
> 8.1 – Update (David Cake)
> 8.2 – Discussion
> 8.3 – Next steps
>
> *Item 9: Any Other Business (5 mins)*
>
> * Proposal to review SSAC reports and determine whether or not
> any recommendations impact on GNSO Consensus Policy*
> Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws,
> Article X, Section 3)
> *9. Except as otherwise specified in these Bylaws, Annex A
> hereto, or the GNSO Operating Procedures, the default
> threshold to pass a GNSO Council motion or other voting action
> requires a simple majority vote of each House. The voting
> thresholds described below shall apply to the following GNSO
> actions:
>
> a. Create an Issues Report: requires an affirmative vote of more
> than one-fourth (1/4) vote of each House or majority of one House.
>
> b. Initiate a Policy Development Process ("PDP") Within Scope (as
> described in Annex A
> <http://www.icann.org/en/about/governance/bylaws#AnnexA>):
> requires an affirmative vote of more than one-third (1/3) of each
> House or more than two-thirds (2/3) of one House.
>
> c. Initiate a PDP Not Within Scope: requires an affirmative vote
> of GNSO Supermajority.
>
> d. Approve a PDP Team Charter for a PDP Within Scope: requires an
> affirmative vote of more than one-third (1/3) of each House or
> more than two-thirds (2/3) of one House.
>
> e. Approve a PDP Team Charter for a PDP Not Within Scope: requires
> an affirmative vote of a GNSO Supermajority.
>
> f. Changes to an Approved PDP Team Charter: For any PDP Team
> Charter approved under d. or e. above, the GNSO Council may
> approve an amendment to the Charter through a simple majority vote
> of each House.
>
> g. Terminate a PDP: Once initiated, and prior to the publication
> of a Final Report, the GNSO Council may terminate a PDP only for
> significant cause, upon a motion that passes with a GNSO
> Supermajority Vote in favor of termination.
>
> h. Approve a PDP Recommendation Without a GNSO Supermajority:
> requires an affirmative vote of a majority of each House and
> further requires that one GNSO Council member representative of at
> least 3 of the 4 Stakeholder Groups supports the Recommendation.
>
> i. Approve a PDP Recommendation With a GNSO Supermajority:
> requires an affirmative vote of a GNSO Supermajority,
>
> j. Approve a PDP Recommendation Imposing New Obligations on
> Certain Contracting Parties: where an ICANN contract provision
> specifies that "a two-thirds vote of the council" demonstrates the
> presence of a consensus, the GNSO Supermajority vote threshold
> will have to be met or exceeded.
>
> k. Modification of Approved PDP Recommendation: Prior to Final
> Approval by the ICANN Board, an Approved PDP Recommendation may be
> modified or amended by the GNSO Council with a GNSO Supermajority
> vote.
>
> l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the
> Council members of each House, or (b) three-fourths (3/4) of one
> House and a majority of the other House."
>
> *Appendix 2: Absentee Voting Procedures (**GNSO Operating
> Procedures 4.4
> <http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>**)
> *4.4.1 Applicability
> Absentee voting is permitted for the following limited number of
> Council motions or measures.
> a. Initiate a Policy Development Process (PDP);
> b. Approve a PDP recommendation;
> c. Recommend amendments to the GNSO Operating Procedures (GOP) or
> ICANN Bylaws;
> d. Fill a Council position open for election.
>
> 4.4.2 Absentee ballots, when permitted, must be submitted within
> the announced time limit, which shall be 72 hours from the
> meeting’s adjournment. In exceptional circumstances, announced at
> the time of the vote, the Chair may reduce this time to 24 hours
> or extend the time to 7 calendar days, provided such amendment is
> verbally confirmed by all Vice-Chairs present.
>
> 4.4.3 The GNSO Secretariat will administer, record, and tabulate
> absentee votes according to these procedures and will provide
> reasonable means for transmitting and authenticating absentee
> ballots, which could include voting by telephone, e- mail,
> web-based interface, or other technologies as may become available.
> 4.4.4 Absentee balloting does not affect quorum requirements.
> (There must be a quorum for the meeting in which the vote is
> initiated.)
> ----------------------------------------------------------------------------
>
> Local time between October and March, Winter in the NORTHERN
> hemisphere
> ----------------------------------------------------------------------------
>
> Reference (Coordinated Universal Time) UTC 15:00
> ----------------------------------------------------------------------------
> California, USA (PDT
> <http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>)
> UTC-7+1DST 10:00
> Iowa City, USA (CST
> <http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+1DST 12:00
>
> New York/Washington DC, USA (EST) UTC-4+1DST 13:00
> Rio de Janiero, Brazil (BRST) UTC-2+1DST 16:00
> Montevideo, Uruguay (UYST
> <http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>)
> UTC-2+1DST 16:00
> Buenos Aires, Argentina (ART
> <http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>)UTC-3+0DST
> 15:00
> London, United Kingdom (BST) UTC+0DST 18:00
> Bonn, Germany (CET) UTC+1+0DST 19:00
> Stockholm, Sweden (CET) UTC+1+0DST 19:00
> Cairo, Egypt, (EET) UTC+2+0DST 20:00
> Istanbul, Turkey (EEST) UTC+2+0DST 20:00
> Ramat Hasharon, Israel(IST
> <http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
> UTC+2+0DST 20:00
> Beijing/Hong Kong, China (HKT ) UTC+8+0DST 02:00 next day
> Perth, Australia (WST
> <http://timeanddate.com/library/abbreviations/timezones/au/wst.html>)
> UTC+8+0DST 02:00 next day
> ----------------------------------------------------------------------------
>
> DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local
> time (with exceptions)
> ----------------------------------------------------------------------
>
> For other places see
> http://www.timeanddate.com*http://tinyurl.com/otro8aq*
>
> Glen de Saint Géry
> GNSO Secretariat
> *gnso.secretariat at gnso.icann.org
> <mailto:gnso.secretariat at gnso.icann.org>*
> *http://gnso.icann.org <http://gnso.icann.org/>*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20140115/d8621b6e/attachment.html>
More information about the council
mailing list