Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Motion       Motion on ICANN Bylaw Recommendation


Made by Jeff Neuman

Seconded by Volker Greimann

 

...

WHEREAS:

  1. The ICANN Bylaws currently state:  There shall be a policy-development body known as the Generic Names Supporting Organization (GNSO), which shall be responsible for developing and recommending to the ICANN Board substantive

...

  1. policies relating to generic top-level domains;
  2. WHEREAS, the The Board Governance Committee has recognized in Reconsideration Request 13-3 that "As of now, there is no defined policy or process within ICANN that requires Board or staff consultation with the GNSO Council if the Board or staff is acting in contravention to a statement made by the GNSO Council outside of the PDP"; and

 

...

  1. The GNSO Council believes that such a defined policy or process is now needed.

  RESOLVED:

...

The GNSO Council recommends that the ICANN Bylaws be amended to:

 

  1. Add a

...

  1. second sentence to Article X, Section 1 such that Section 1 would now read:
    "There shall be a policy-development body known as the Generic Names Supporting Organization (GNSO), which shall be responsible for developing and

...

  1. recommending to the ICANN Board substantive policies relating to generic top-level domains.  The GNSO is also responsible for providing advice to the ICANN Board on the implementation of policies relating to generic top-level domains.";

 

...

  1. Include language requiring a formal consultation process in the event that the ICANN Board determines to take an action that is not consistent with GNSO advice.  Such process shall require the ICANN Board to state the reasons why it

...

  1. decided not to follow GNSO advice, and be followed in a timely manner, with a consultation in which the GNSO and the ICANN Board attempt in good faith to find a mutually acceptable solution.  If no such solution can be found, the

...

  1. ICANN Board will state in its final decision the reasons why the GNSO advice was not followed.

...

  1. And;

 

     2.   FURTHER RESOLVED that :

  1. That the GNSO recommends the above to apply whether or not the policy development process as set forth in Article X, section 6 were followed.

 

2. Motion to adopt the Charter for the Policy & Implementation Working Group

 Made Made by: Wolf Wolf-Ulrich Knoben

Seconded by:

Whereas,WHEREAS:

  1. The GNSO Council decided at its wrap-up session at the ICANN meeting in Beijing to form a drafting team to develop a charter for a Working Group to address the issues that have been raised in the context of the recent discussions on policy & implementation that affect the GNSO.
  2. The drafting team was formed and has now submitted a proposed charter for the Policy & Implementation Working Group to the GNSO Council.
  3. The GNSO Council has reviewed the proposed charter.

    http://gnso.icann.org/en/drafts/policy-implementation-charter-04jul13-en.pdf

     

RESOLVED:RESOLVED,

  1. The GSNO Council approves the charter and appoints [to be confirmed] as the GNSO Council Liaison to the Policy & Implementation Working Group.
  2. The GNSO Council further directs that the call for volunteers to form the Policy & Implementation Working Group be initiated no later

...

  1. than 7 days after the approval of this motion.
    Until such time as the WG can select a chair and that chair can be confirmed by the GNSO Council, the GNSO Council Liaison shall act as interim chair.

Charter

http://gnso.icann.org/en/drafts/policy-implementation-charter-04jul13-en.pdf

 [Include link to charter]