[ALAC] Board resolutions from ICANN Board meeting in Istanbul on 9 September 2014

Tijani BEN JEMAA tijani.benjemaa at planet.tn
Fri Sep 12 20:53:44 UTC 2014


I find it a good position, and I suppose that people who abstained were
Sebastien + 2 others, but I don’t know who? 

 

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

Tijani BEN JEMAA

Executive Director

Mediterranean Federation of Internet Associations (FMAI)

Phone:  + 216 41 649 605

Mobile: + 216 98 330 114

Fax:       + 216 70 853 376

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

 

 

 

 

-----Message d'origine-----
De : alac-bounces at atlarge-lists.icann.org
[mailto:alac-bounces at atlarge-lists.icann.org] De la part de Rinalia Abdul
Rahim
Envoyé : vendredi 12 septembre 2014 05:22
À : ALAC Working List
Objet : [ALAC] Board resolutions from ICANN Board meeting in Istanbul on 9
September 2014

 

Dear ALAC,

 

See item 3(e) for Board resolution on ATLAS II.

 

Best regards,

 

Rinalia

 

>  https://www.icann.org/resources/board-material/resolutions-2014-09-09-en

> 

> 

> Approved Board Resolutions | Regular Meeting of the ICANN Board

> 

> 09 Sep 2014

> 

> 1. Main Agenda

> 

> a. Appointment of 2015 Nominating Committee Chair and Chair-Elect

> 

> Whereas, the BGC reviewed the Expressions of Interest from candidates for

the 2014 Nominating Committee ("NomCom") Chair and Chair-Elect, considered

the results of a 360-degree evaluation of the 2014 NomCom leadership, and

evaluated response to questions posed by the BGC to each candidate.

> 

> Whereas, the BGC has recommended that Stephane Van Gelder be appointed as

the 2015 NomCom Chair.

> 

> Resolved (2014.09.09.01), the Board hereby appoints Stephane Van Gelder

as the 2015 Nominating Committee Chair.

> 

> 

> 2.Consent Agenda:

> 

> a.  Approval of Board Meeting Minutes

> 

> Resolved (2014.09.09.02), the Board approves the minutes of the 30 July

2014 Meeting of the ICANN Board.

> 

> 

> b.  Appointment of Benedict Addis to the Security & Stability Advisory

Committee (SSAC)

> 

> Whereas, the Security and Stability Advisory Committee (SSAC) does review

its membership and make adjustments from time-to-time.

> 

> Whereas, the SSAC Membership Committee, on behalf of the SSAC, requests

that the Board should appoint Benedict Addis to the SSAC.

> 

> Resolved (2014.09.09.03), that the Board appoints Benedict Addis to the

SSAC.

> 

> 

> 

> c.  Thank You from the Security and Stability Advisory Committee (SSAC)

to David Conrad

> 

> Whereas, the Board appointed David Conrad to the SSAC on 18 March 2011.

> 

> Whereas, Mr. Conrad resigned from the SSAC on 01 August 2014.

> 

> Whereas, ICANN wishes to acknowledge and thank Mr. Conrad for his service

to the community by his membership on the SSAC.

> 

> Resolved (2014.09.09.04), that David Conrad has earned the deep

appreciation of the Board for his service to ICANN by his membership on the

SSAC, and that the Board wishes Mr. Conrad well in all future endeavors.

> 

> 

> 

> 3.  Main Agenda:

> 

> a.  Registry Services Technical Evaluation Panel (RSTEP) Report on Public

Interest Registry's Request to Implement Technical Bundling in .NGO and .ONG

> 

> Whereas, on 12 March 2014, Public Interest Registry (PIR) submitted a

Registry Services Evaluation Policy (RSEP) request [PDF, 24 KB] to offer

mandatory technical bundling of second level domain names for .NGO and .ONG

under Exhibit-A of each respective Registry Agreement.

> 

> Whereas, on 21 May 2014, ICANN staff posted the RSEP request for public

information and conducted its review of the request under the RSEP.

> 

> Whereas, on 4 June 2014, ICANN staff's preliminary determination did not

identify any significant competition issues. Separately, ICANN staff

determined that the proposed registry service might raise significant

stability or security issues, and informed [PDF, 320 KB] PIR of the need to

refer the proposal to the Registry Services Technical Evaluation Panel

(RSTEP) for further evaluation.

> 

> Whereas, on 6 June 2014, ICANN referred PIR's RSEP request [PDF, 952 KB]

to the RSTEP for further evaluation.

> 

> Whereas, on 10 June 2014, ICANN posted PIR's RSEP request for public

comment. The public comment concluded on 30 July 2014 and no public

comments were received.

> 

> Whereas, on 29 July 2014, the RSTEP report was posted for public comment.

The public comment period concluded on 13 August 2014 and no public

comments were received.

> 

> Whereas, the RSTEP report concluded that from a technical evaluation

perspective, the proposal does not create "a reasonable risk of a

meaningful adverse effect on stability or security" as defined in the RSEP

Policy related to the introduction of the registry service to support the

mandatory technical bundling of second level domain names for .NGO and

.ONG. The RSTEP report and staff also identified several potential

technical and implementation questions associated with introducing the

proposed new registry service to the DNS, including: implications of

unbundling of .NGO and .ONG; potential registrant and/or end user

confusion; equivalency issues being discussed within the context of IDN

variants; and other operational concerns.

> 

> Resolved (2014.09.09.05), the Board adopts the findings in the RSTEP

report that PIR's proposal does not create "a reasonable risk of a

meaningful adverse effect on stability or security", and approves PIR's

request related to the introduction of the registry service to support the

mandatory technical bundling of second level domain names for .NGO and .ONG.

> 

> Resolved (2014.09.09.06), the Board authorizes the President and CEO, or

his designee(s), to develop an amendment to implement the new registry

service that takes into account and appropriately addresses the related

outstanding technical and implementation questions.

> 

> 

> 

> b.  Planning for Future gTLD Application Rounds

> 

> No resolution taken.

> 

> 

> c.  FY15 Operating Plan and Budget

> 

> Whereas, the draft FY15 Operating Plan and Budget was posted for public

comment in accordance with the Bylaws on 8 May 2014, which was based upon

community consultations, and consultations throughout ICANN staff and the

Board Finance Committee, during the past fiscal year.

> 

> Whereas, intervening activities and comments received from the public

comment forum were taken into account to determine significant revisions to

the 8 May 2014 draft FY15 Operating Plan and Budget.

> 

> Whereas, in addition to the public comment forum, ICANN actively

solicited community feedback and consultation with the ICANN community by

other means, including online conference calls, meetings in Singapore and

London, and email communications.

> 

> Whereas, the Board Finance Committee has discussed, and guided staff on,

the development of the FY15 Operating Plan and Budget at each of its recent

regularly scheduled meetings.

> 

> Whereas, the Board Finance Committee met on 19 August 2014 to discuss the

final draft FY15 Operating Plan and Budget, and recommended that the Board

adopts the FY15 Operating Plan and Budget.

> 

> Whereas, per section 3.9 of the 2001, 2009 and 2013 Registrar

Accreditation Agreements, respectively, the Board is to establish the

Registrar Variable Accreditation Fees, which must be established in order

to develop the annual budget.

> 

> Whereas, the description of the Registrar fees, including the recommended

Registrar Variable Accreditation Fees, for FY15 has been included in the

FY15 Operating Plan and Budget.

> 

> Resolved (2014.09.09.07), the Board adopts the FY15 Operating Plan and

Budget and in doing so establishes the Variable Accreditation Fees (per

registrar and transaction) as set forth in the FY15 Operating Plan and

Budget.

> 

> 

> d.  Final Draft of the ICANN Five-Year Strategic Plan (FY16-FY20)

> 

> Item removed from Agenda.

> 

> 

> e.  Acknowledgment of Second At-Large Summit Declaration

> 

> Whereas, the Second At-Large Summit (ATLAS II) was held at the ICANN 50

meeting in London, United Kingdom in June 2014.

> 

> Whereas, ATLAS II has built on the first summit organized in March 2009

at the ICANN 34 meeting in Mexico.

> 

> Whereas, the Board has received the Final ATLAS II Declaration (

https://community.icann.org/download/attachments/48338039/ATLAS-II-Declarati
on-with-appendix-RC9.pdf?version=1&modificationDate=1407420726000&api=v2

[PDF, 204 KB]).

> 

> Whereas, the At-Large community continues the Summit's spirit of

engagement and enthusiasm through a set of post-ATLAS II implementation

activities.

> 

> Resolved (2014.09.09.08), the Board acknowledges the Final ATLAS II

Declaration, and extends its congratulations on the successful Summit held

during ICANN 50 in London.

> 

> Resolved (2014.09.09.09), the Board affirms the significance of the ATLAS

II Summit and its outcomes as valuable input from the At-Large community of

individual Internet users towards strengthening ICANN.

> 

> Resolved (2014.09.09.10), the Board expresses its appreciation for the

tremendous effort made by the At-Large community in delivering the At-Large

Summit, the Final ATLAS II Declaration and the post-ATLAS II implementation

activities.

> 

> Resolved (2014.09.09.11), the Board looks forward to following up with

the ALAC on any inputs that are provided to the Board resulting from the

Final ATLAS II Declaration.

> 

> Note: Three voting members of the Board abstained from voting on the

resolutions. They stated for the record that they were supportive of the

work resulting from the ATLAS, but wanted to draw attention to their

encouragement for the Board to take future consideration of plans to

develop the ATLAS into a regularly occurring event.

> 

> 

> f.  AOB

> 

> No resolution taken.

> 

> 

> Published on 11 September 2014

_______________________________________________

ALAC mailing list

ALAC at atlarge-lists.icann.org

https://atlarge-lists.icann.org/mailman/listinfo/alac

 

At-Large Online: http://www.atlarge.icann.org

ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA
C)



---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
http://www.avast.com


More information about the ALAC mailing list