February 2014 - ispcp - lists.icann.org

Fwd: ICANN News Alert -- ICANN Future Meetings Strategy
by Mike O'Connor Feb. 25, 2014

Feb. 25, 2014

the public comment period for this is just opening up. does somebody want to take the lead on drafting a response? at first read, it seems reasonable to me — but the meetings are less important to me, since most of my work is in weekly working-group calls. mikey Begin forwarded message: > From: "ICANN News Alert" <communications(a)icann.org> > Subject: ICANN News Alert -- ICANN Future Meetings Strategy > Date: February 25, 2014 at 4:06:52 PM CST > To: <mike(a)haven2.com> > > > News Alert > > http://www.icann.org/en/news/announcements/announcement-25feb14-en.htm > > ICANN Future Meetings Strategy > 25 February 2014 > > Forum Announcement: Comment Period Opens on Date: 25 February 2014 > Categories/Tags: > Participation > Events/Conferences > Purpose (Brief): The purpose of this document is to help guide the Community through a proposed new strategy for the structure, purpose and locations of the ICANN public meetings to support broad, informed participation and reflect the functional, geographic, and cultural diversity of the Internet at all levels of policy development and decision-making. > Public Comment Box Link: http://www.icann.org/en/news/public-comment/meetings-strategy-25feb14-en.htm > > > This message was sent to mike(a)haven2.com from: > ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 > Email Marketing by > > Manage Your Subscription > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fwd: [council] Guiding the Evolution of the IANA Protocol Parameter Registries
by Mike O'Connor Feb. 25, 2014

Feb. 25, 2014

Begin forwarded message: > From: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> > Subject: [council] Guiding the Evolution of the IANA Protocol Parameter Registries > Date: February 25, 2014 at 3:01:16 PM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > > For info: > > The IETF is trying to document a set of principles for Evolution of the IANA Protocol Parameter Registries, as part of input into the current Internet Governance debates: > > From: IAB Chair > > To: IETF Announce > > Subject: Guiding the Evolution of the IANA Protocol Parameter Registries > > Existing IETF and IAB consensus concerning Internet registry functions > and IANA are documented in a variety of RFCs and IAB communications > [RFC2860,RFC6220,IAB1,IAB2]. Since registry functions and IANA are > likely to be the subject of discussion in a number of venues outside the > IETF over the coming months and years, the IAB is seeking community > feedback about operating principles to use when they find themselves > involved in those discussions. > > While dealing with these issues the IAB has consistently approached the > issues from a set of (implicit) principles. Since the registry functions > are subject of discussion in various fora, the IAB has tried to make > these operating principles explicit and seeks to confirm these with the > community. > > The IAB are planning to use part of the time in the IGOVUPDATE session at > IETF 89 (6 March 2014, 17:00-18:30 GMT) for a discussion of such operating > principles. But we wanted to kick-start that discussion with a few > thoughts about principles that the IAB and IETF have articulated in > various documents already and some that have emerged over time but may > not have been written down. What we are interested in is an articulation > of what the IETF community values. What other parties (ICANN, RIRs, > governments, etc.) value when they think about registry functions is > interesting, but we want to focus this discussion on the IETF and not > those other parties. > > This is a first cut of making the principles more explicit for which we > seek your views. > > Some of these might seem a bit generic, but it is difficult to predict > the nature of future discussions in which IETF and IAB leaders might find > themselves, so generality helps in that regard. > > On behalf of the IAB, > Russ Housley > IAB Chair > > = = = = = = = = > > Principles Guiding the Evolution of the IANA Protocol Parameter Registries > > 1. The IETF protocol parameters function has been and continues to be > capably provided by the Internet community. > > The strength and stability of the function and its foundation within the > Internet community are both important given how critical protocol > parameters are to the proper functioning of IETF protocols. > > We think the structures that sustain the protocol parameters function > needs be strong enough that they can be offered independently by the > Internet community, without the need for backing from external parties. > And we believe we largely are there already, although the system can be > strengthened further, and continuous improvements are being made. > > > 2. The administration of the protocol parameters function by ICANN is > working well for the Internet and the IETF. > > We are pleased with the publication and maintenance of the protocol > parameter function and the coordination of the evaluation of > registration requests through the IANA function provided by ICANN. > > > 3. The IETF protocol parameters function requires openness, > transparency, and accountability. > > Existing documentation of how the function is administered and overseen > is good [RFC2860,RFC6220], but further articulation and clarity may be > beneficial. It is important that the whole Internet community can > understand how the function works, and that the processes for > registering parameters and holding those who oversee the protocol > parameter function accountable for following those processes are > understood by all interested parties. We are committed to making > improvements here if necessary. > > > 4. Any contemplated changes to the protocol parameters function should > use the current RFCs and model as the starting point. > > The protocol parameters function is working well, and as a result > wholesale changes to the role of the IETF vis a vis the function are not > warranted. The IETF/IANA Memorandum of Understanding [RFC2860] is a good > model to work from in the event that other parties do want to contemplate > changes. Put quite simply: evolution, not revolution. > > > 5. The Internet architecture requires and receives capable service by > Internet registries. > > The stability of the Internet depends on capable provision of not just > IETF protocol parameters, but IP numbers, domain names, and other > registries. Furthermore, DNS and IPv4/IPv6 are IETF-defined protocols. > Thus we expect the role of the IETF in standards development, architectural > guidance, and allocation of certain name/number parameters to continue. > IP multicast addresses and special-use DNS names are two examples where > close coordination is needed. The IETF will continue to coordinate with > ICANN, the RIRs, and other parties that are mutually invested in the > continued smooth operation of the Internet registries. We fully > understand the need to work together. > > > 6. The IETF will continue its direction and stewardship of the protocol > parameters function as an integral component of the IETF standards > process and the use of resulting protocols. > > RFC 6220 specifies the role and function of the protocol parameters > registry, which is critical to IETF standards processes and IETF > protocols. We see no need to revisit or reconsider our current approach > with regard to protocol parameters, including the ability to delegate > operational responsibility for registries to other organizations. > > [RFC2860] http://www.rfc-editor.org/rfc/rfc2860.txt > [RFC6220] http://www.rfc-editor.org/rfc/rfc6220.txt > [IAB1] http://www.iab.org/wp-content/IAB-uploads/2011/03/2009-06-08-IAB-NTIA-NOI-f… > [IAB2] http://www.iab.org/wp-content/IAB-uploads/2011/07/IANA-IAB-FNOI-2011.pdf > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fwd: [council] SAC065: SSAC Advisory on DDoS Attacks using the DNS
by Mike O'Connor Feb. 22, 2014

Feb. 22, 2014

Begin forwarded message: > From: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> > Subject: [council] SAC065: SSAC Advisory on DDoS Attacks using the DNS > Date: February 22, 2014 at 3:47:21 PM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > Hello All, > > Attached is an advisory from SSAC on DDoS attacks: > > > Specifically, the SSAC strongly recommends that: > > 1. ICANN should help facilitate an Internet-wide community effort to reduce the number of open resolvers and networks that allow network spoofing. This effort should involve measurement efforts and outreach. > > 2. All network operators should take immediate steps to prevent network address spoofing. > > 3. Recursive DNS server operators should take immediate steps to secure open recursive DNS servers. > > 4. Authoritative DNS server operators should support efforts to investigate authoritative response rate limiting. > > 5. DNS server operators should put in place operational processes to ensure that their DNS software is regularly updated and communicate with their software vendors to keep abreast of the latest developments. > > 6. Manufacturers and/or configurators of customer premise networking equipment, including home networking equipment, should take immediate steps to secure these devices and ensure that they are field upgradable when new software is available to fix security vulnerabilities, and aggressively replace the installed base of non-upgradeable devices with upgradeable devices. > > Regards, > Bruce Tonkin > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

string delegations
by Mike O'Connor Feb. 22, 2014

Feb. 22, 2014

hi all here are all the strings delegated last week. mikey DATE STRING REGISTRY 21 February 2014 .FISH Fox Woods, LLC 21 February 2014 .삼성 (xn―cg4bki) – Korean for "Samsung/Samseong" Samsung SDS Co., LTD 21 February 2014 .VACATIONS Atomic Tigers, LLC 21 February 2014 .INDUSTRIES Outer House, LLC 21 February 2014 .SUPPLY Half Falls, LLC 19 February 2014 .XYZ XYZ.COM, LLC 19 February 2014 .WIKI Top Level Design, LLC 19 February 2014 .NEUSTAR NeuStar, Inc, 18 February 2014 .بازار (xn--mgbab2bd) – Arabic for "bazaar/bazar" CORE Association 16 February 2014 .MANGO Punto FA S.L. Description of the name-collision problem and link to mitigation research project -- http://www.haven2.com/index.php/archives/name-collision-research ICANN's "Name Collision Resources and Information" page - http://www.icann.org/en/help/name-collision ICANN's list of all delegated new gTLDs - http://newgtlds.icann.org/en/program-status/delegated-strings ICANN’s list of scheduled “sunrise” and “trademark claims” periods for new gTLDs - http://newgtlds.icann.org/en/program-status/sunrise-claims-periods Follow this link if you would like to subscribe to this weekly bulletin — http://ispcp.info/mailman/listinfo/gtld-delegations Follow this link if you would like to learn more about the Internet Service Provider and Connectivity Provider (ISPCP) constituency of ICANN’s Generic Name Supporting Organization (GNSO) — www.ispcp.info

1 0

Updated Proposed Agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC
by Mike O'Connor Feb. 22, 2014

Feb. 22, 2014

hi all, here’s the current agenda for the Council meeting (11:00 UTC Thursday, 27-Feb) — there are no issues that require a vote, but please comment on anything that you would like Osvaldo and me to focus attention on during the discussion. unfortunately, our next ISPCP call is scheduled a few days after this Council meeting, so we’ll have to have this conversation via the list. thanks, mikey Begin forwarded message: > From: Glen de Saint Géry <Glen(a)icann.org> > Subject: [council] Updated Proposed Agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC > Date: February 20, 2014 at 4:09:37 PM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > Dear Councillors, > Please find the updated proposed agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC. > http://gnso.icann.org/en/meetings/agenda-council-27feb14-en.htm > https://community.icann.org/display/gnsocouncilmeetings/Agenda+27+February+… > The updates relate to a change in the order of the updates and discussions that have been changed to accommodate Sally Costerton who will address the Council on GNSO Engagement with the work of the ICANN Strategy Panels, and under Any Other Business: Two items have been added, namely: > ICANN Board Seat 14 – NCPH - additional Council meeting Thursday, 10 April 2014 at 14:00 UTC > Note the Root Server System Advisory Committee (RSSAC) presence in Singapore > Proposed Agenda for the GNSO Council Teleconference 27 February 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 11:00 UTC > http://tinyurl.com/nkaf7dk > > Coordinated Universal Time 11:00 UTC > 03:00 Los Angeles; 06:00 Washington; 11:00 London; 12:00 Brussels; 19: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 > Maria Farrell > https://community.icann.org/display/gnsosoi/Maria+Farrell+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 23 January 2014 were posted as approved on 17 February 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 and Action List. > Comments or questions arising. > > Item 3: Consent agenda (0 mins) > > Item 4: UPDATE & DISCUSSION – GNSO Engagement with the work of the ICANN Strategy Panels (15 mins) > 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. > > 4.1 – Status update (Sally Costerton) > 4.2 – Discussion > 4.3 – Next steps > > > Item 5: UPDATE – PDP Working Group on Translation & Transliteration of Contact Information (10 mins) > 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. > 5.1 – Update (Ching Chiao) > 5.2 – Discussion > 5.3 – Next steps > Item 6: UPDATE & DISCUSSION – International Internet Governance Issues (20 mins) > 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. > Item 7: UPDATE & DISCUSSION – GAC Engagement – the work of the Joint GAC / GNSO Consultation Group (15 mins) > Here the Council will receive an update and discuss any action going forward. > 7.1 – Status update > 7.2 – Discussion > 7.3 – Next steps > Item 8: UPDATE & DISCUSSION – 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. > > 8.1 – Update (Jennifer Wolfe) > 8.2 – Discussion > 8.3 – Next steps > > Item 9: UPDATE & DISCUSSION – Planning for Singapore (15 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. > 9.1 – Update (David Cake & Jonathan Robinson) > 9.2 – Discussion > 9.3 – Next steps > > Item 10: Any Other Business (10 mins) > > Community budget requests > ICANN Board Seat 14 – NCPH - additional Council meeting Thursday, 10 April 2014 at 14:00 UTC > Note the Root Server System Advisory Committee (RSSAC) presence in Singapore > > 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): 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) > 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 11:00 > ---------------------------------------------------------------------------- > California, USA (PDT) UTC-7+1DST 03:00 > Iowa City, USA (CST) UTC-6+1DST 05:00 > New York/Washington DC, USA (EST) UTC-4+1DST 06:00 > Rio de Janiero, Brazil (BRST) UTC-2+1DST 08:00 > Montevideo, Uruguay (UYST) UTC-2+1DST 09:00 > Buenos Aires, Argentina (ART) UTC-3+0DST 08:00 > London, United Kingdom (BST) UTC+0DST 11:00 > Bonn, Germany (CET) UTC+1+0DST 12:00 > Stockholm, Sweden (CET) UTC+1+0DST 12:00 > Cairo, Egypt, (EET) UTC+2+0DST 13:00 > Istanbul, Turkey (EEST) UTC+2+0DST 13:00 > Ramat Hasharon, Israel(IST) UTC+2+0DST 13:00 > Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00 > Perth, Australia (WST) UTC+8+0DST 19:00 > ---------------------------------------------------------------------------- > 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/nkaf7dk > > Please let me know if you have any questions. > Thank you. > Kind regards, > > Glen > > Glen de Saint Géry > GNSO Secretariat > gnso.secretariat(a)gnso.icann.org > http://gnso.icann.org > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 3

Fw: ISPCP comment
by WUKnoben Feb. 22, 2014

Feb. 22, 2014

From: WUKnoben Sent: Friday, February 21, 2014 9:52 PM To: comments-atrt2-recommendations-09jan14(a)icann.org Subject: ISPCP comment The Internet Services Provider and Connectivity Provider Constituency (ISPCP) is pleased to provide comments to the Second Accountability and Transparency Review Team (ATRT 2) Final Report & Recommendations (see attached). Best regards Wolf-Ulrich Knoben

2 1

Fwd: ICANN 48 Business Digest available in 7 languages
by Mike O'Connor Feb. 21, 2014

Feb. 21, 2014

Begin forwarded message: > From: ICANN for Business <groups-noreply(a)linkedin.com> > Subject: ICANN 48 Business Digest available in 7 languages > Date: February 20, 2014 at 8:19:25 PM CST > To: Mikey O'Connor <mike(a)haven2.com> > > LinkedIn Groups > > Group: ICANN for Business > Subject: ICANN 48 Business Digest available in 7 languages > Dear Group Members, > > The ICANN 48 Business Digest is now available online on our slideshare page: http://goo.gl/5XJTqi > The document is available in Arabic, Chinese, English, French, Portuguese, Russian, and Spanish. > > Please feel free to share it with your respective networks in the language that is most appropriate. > > If you have any feedback on the Digest you can email businessengagement(a)icann.org > > Best, > Your Group Manager > Posted By Riccardo Ruffolo > View or add comments » > > Don't want to hear from the manager? Unsubscribe here > > > This email was intended for Mikey O'Connor (Working hard at working less). Learn why we included this. © 2014, LinkedIn Corporation. 2029 Stierlin Ct. Mountain View, CA 94043, USA > > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fwd: [council] [soac-discussion] CEO/Community Leaders Conference Call - 18 February 2014
by Mike O'Connor Feb. 20, 2014

Feb. 20, 2014

Begin forwarded message: > From: "Jonathan Robinson" <jrobinson(a)afilias.info> > Subject: [council] FW: [soac-discussion] CEO/Community Leaders Conference Call - 18 February 2014 > Date: February 20, 2014 at 3:22:29 AM CST > To: <council(a)gnso.icann.org> > Reply-To: <jrobinson(a)afilias.info> > > All. FYI. Jonathan. > > From: owner-soac-discussion(a)icann.org [mailto:owner-soac-discussion@icann.org] On Behalf Of David Olive > Sent: 19 February 2014 23:32 > To: soac-discussion(a)icann.org > Cc: Fadi Chehade; Cassia Oliveira; Tina Shelebian; Sally Costerton; Xavier J. Calvez; Theresa Swinehart; Tarek Kamel; Duncan Burns; Robert Hoggarth; John Jeffrey; Akram Atallah; Susanna Bennett; Susie Johnson > Subject: [soac-discussion] CEO/Community Leaders Conference Call - 18 February 2014 > > Dear SO/AC/SG Leaders: > > Attached please find the Chat and Transcript of Tuesday’s CEO/Community Leaders conference call. > Below is the link to the MP3 file. > > http://audio.icann.org/so-ac-leaders-18feb14-en.mp3 > > These documents are posted at: https://community.icann.org/display/soaceinputfdback/Event+Calendar > > Regards, David > -- > David A. Olive > Vice President, Policy Development Support > General Manager, ICANN Regional Headquarters –Istanbul > > Internet Corporation for Assigned Names and Numbers (ICANN) > Hakki Yeten Cad. Selenium Plaza No:10/C K:5 > 34349 Fulya, Besiktas, Istanbul, Turkey > > Tel: +90.212.381.8727 - Fax: +90.212.381.8731 - Mobile: +1. 202.341.3611 > > > > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fwd: [council] ICANN Board resolution from meeting held 17 Feb 2014
by Mike O'Connor Feb. 20, 2014

Feb. 20, 2014

Begin forwarded message: > From: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> > Subject: [council] ICANN Board resolution from meeting held 17 Feb 2014 > Date: February 19, 2014 at 11:51:12 PM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > http://www.icann.org/en/groups/board/documents/resolutions-17feb14-en.htm > > Approved Board Resolutions | Special Meeting of the ICANN Board > > 17 February 2014 > > > President's Globalization Advisory Groups > > Whereas, the multistakeholder model has matured in response to the many challenges of exponential growth in the Internet, so ICANN must continue to evolve and grow in response to those challenges. > > Whereas, ICANN's mission and responsibilities are to the global community and stakeholders worldwide. > > Whereas, as a multistakeholder organization ICANN must evolve to fully execute its narrow mission, which is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and be in a position to meet new challenges whether operational, policy, political or technical. > > Whereas, in order for ICANN to fully execute its mission as a multistakeholder organization and be in a position to meet operational, policy, political, or technical challenges, there must be an evolution of the globalization of ICANN. > > Whereas, the globalization of ICANN includes, among other things: strengthening and continuing to evolve and improve ICANN as a multistakeholder organization; and contributing as a partner in the Internet eco-system to strengthen awareness and the evolution of multistakeholder Internet governance and cooperation in a manner that ensures the continued flexibility to adapt to emerging issues. > > Whereas, on 28 September 2013, the ICANN Board authorized the CEO to, among other things, "work with other key organizations and leaders to establish a coalition towards the formation of a movement or initiative" ("Coalition"), in order to address increasing concerns regarding the effectiveness of a "global, open, multi-stakeholder Internet governance system." > > > Whereas, the President and CEO has executed the mandate of the 28 September 2013 Board resolution and has helped facilitate a number of activities, including: > > (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" > > (ii) development of and participation in the "1net initiative"; and > > (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. > > > Whereas, on 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the President and CEO to continue supporting the three emerging and evolving initiatives and recognizing that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following three initiatives: > > (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; > > (ii) development and participation in the "1net initiative"; and > > (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. > > Whereas, in Resolution 2013.11.17.01, the Board noted that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." > > Whereas, the continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. > > Whereas, given the nature and breadth of issues involved with the continued globalization efforts, ICANN has recognized the importance of the timely establishment of groups of Board members to focus on given topic areas, and then report and make recommendations to the President and CEO, and the full Board, for consideration. > > Whereas, as part of its continued globalization efforts, ICANN should establish certain "President's Globalization Advisory Groups" composed of Board members to address the following areas: Affirmation of Commitments ("AOC"), policy structures, legal structure, root server system, the IANA multistakeholder accountability, and Internet governance. > > Resolved (2014.02.17.01), the Board approves the creation of several President's Globalization Advisory Groups in order to support further ICANN globalization. These Advisory Groups of Board members are being set up to provide guidance to the full Board in support of ICANN's globalization work led by the President and CEO. The President's Globalization Advisory Groups will meet with the community during ICANN 49 Singapore Meeting, and around IETF 89, and other community meetings to discuss the ICANN globalization issues. The President's Globalization Advisory Groups will then make recommendations to the Board, which the Board will report during ICANN 50 London Meeting. > > These Advisory Groups will deal with the following topics: > > Affirmation of Commitments ("AOC"); > > policy structures; > > legal structure; > > root server system; > > the IANA multistakeholder accountability; and, > > Internet governance. > > The President and CEO will announce the composition of these Advisory Groups within two days following the posting of this resolution at http://www.icann.org/en/groups/other/globalization-19feb14-en.pdf [see attached]; the President and CEO shall have the authority to change the Advisory Groups and their composition from time to time, without requiring a further resolution. > > > > RATIONALE FOR RESOLUTION 2014.02.17.01 > > This resolution is a continuation of the Board's 28 September 2013 and 17 November resolutions providing ICANN's President and CEO with a mandate to explore how ICANN could coordinate with stakeholders from across the globe to address the pressing issue of the future of Internet governance. On 28 September 2013, the Board directed the President and CEO to work towards the establishment of a coalition to start an effort to form an Internet cooperation agenda, and to do so in a manner consistent with ICANN's mission. Following the September meeting, the President and CEO executed the mandate of the 28 September 2013 Board resolution and helped facilitate a number of activities, including: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" (ii) development of and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. > > On 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the CEO to continue supporting the three emerging and evolving initiatives and recognizes that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following initiatives: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; (ii) development and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. The Board also noted in Resolution 2013.11.17.01 that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." > > ICANN and the multistakeholder model have been exposed to many challenges, and ICANN must evolve to face the challenges. ICANN's mission and responsibilities are to the global community and stakeholders worldwide. To remain accountable to ICANN's mission and community, the Board recognizes that as a multistakeholder organization ICANN must evolve to fully execute on its mission, and be in a position to meet the challenges whether operational, political or technical. > > The continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. > > This is an Organizational Administrative Function for which public comment is not required. > > > > Published on 19 February 2014 PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fw: [Soac-infoalert] Approved Board Resolutions | Special Meeting of the ICANN Board | ICANN - 17 February 2014
by WUKnoben Feb. 20, 2014

Feb. 20, 2014

FYI Best regards Wolf-Ulrich From: David Olive Sent: Thursday, February 20, 2014 7:05 AM To: soac-infoalert(a)icann.org Subject: [Soac-infoalert] Approved Board Resolutions | Special Meeting of the ICANN Board | ICANN - 17 February 2014 http://www.icann.org/en/groups/board/documents/resolutions-17feb14-en.htm Approved Board Resolutions | Special Meeting of the ICANN Board 17 February 2014 President's Globalization Advisory Groups Whereas, the multistakeholder model has matured in response to the many challenges of exponential growth in the Internet, so ICANN must continue to evolve and grow in response to those challenges. Whereas, ICANN's mission and responsibilities are to the global community and stakeholders worldwide. Whereas, as a multistakeholder organization ICANN must evolve to fully execute its narrow mission, which is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and be in a position to meet new challenges whether operational, policy, political or technical. Whereas, in order for ICANN to fully execute its mission as a multistakeholder organization and be in a position to meet operational, policy, political, or technical challenges, there must be an evolution of the globalization of ICANN. Whereas, the globalization of ICANN includes, among other things: strengthening and continuing to evolve and improve ICANN as a multistakeholder organization; and contributing as a partner in the Internet eco-system to strengthen awareness and the evolution of multistakeholder Internet governance and cooperation in a manner that ensures the continued flexibility to adapt to emerging issues. Whereas, on 28 September 2013, the ICANN Board authorized the CEO to, among other things, "work with other key organizations and leaders to establish a coalition towards the formation of a movement or initiative" ("Coalition"), in order to address increasing concerns regarding the effectiveness of a "global, open, multi-stakeholder Internet governance system." Whereas, the President and CEO has executed the mandate of the 28 September 2013 Board resolution and has helped facilitate a number of activities, including: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" (ii) development of and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. Whereas, on 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the President and CEO to continue supporting the three emerging and evolving initiatives and recognizing that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following three initiatives: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; (ii) development and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. Whereas, in Resolution 2013.11.17.01, the Board noted that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." Whereas, the continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. Whereas, given the nature and breadth of issues involved with the continued globalization efforts, ICANN has recognized the importance of the timely establishment of groups of Board members to focus on given topic areas, and then report and make recommendations to the President and CEO, and the full Board, for consideration. Whereas, as part of its continued globalization efforts, ICANN should establish certain "President's Globalization Advisory Groups" composed of Board members to address the following areas: Affirmation of Commitments ("AOC"), policy structures, legal structure, root server system, the IANA multistakeholder accountability, and Internet governance. Resolved (2014.02.17.01), the Board approves the creation of several President's Globalization Advisory Groups in order to support further ICANN globalization. These Advisory Groups of Board members are being set up to provide guidance to the full Board in support of ICANN's globalization work led by the President and CEO. The President's Globalization Advisory Groups will meet with the community during ICANN 49 Singapore Meeting, and around IETF 89, and other community meetings to discuss the ICANN globalization issues. The President's Globalization Advisory Groups will then make recommendations to the Board, which the Board will report during ICANN 50 London Meeting. These Advisory Groups will deal with the following topics: Affirmation of Commitments ("AOC"); policy structures; legal structure; root server system; the IANA multistakeholder accountability; and, Internet governance. The President and CEO will announce the composition of these Advisory Groups within two days following the posting of this resolution at http://www.icann.org/en/groups/other/globalization-19feb14-en.pdf [see attached]; the President and CEO shall have the authority to change the Advisory Groups and their composition from time to time, without requiring a further resolution. RATIONALE FOR RESOLUTION 2014.02.17.01 This resolution is a continuation of the Board's 28 September 2013 and 17 November resolutions providing ICANN's President and CEO with a mandate to explore how ICANN could coordinate with stakeholders from across the globe to address the pressing issue of the future of Internet governance. On 28 September 2013, the Board directed the President and CEO to work towards the establishment of a coalition to start an effort to form an Internet cooperation agenda, and to do so in a manner consistent with ICANN's mission. Following the September meeting, the President and CEO executed the mandate of the 28 September 2013 Board resolution and helped facilitate a number of activities, including: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" (ii) development of and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. On 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the CEO to continue supporting the three emerging and evolving initiatives and recognizes that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following initiatives: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; (ii) development and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. The Board also noted in Resolution 2013.11.17.01 that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." ICANN and the multistakeholder model have been exposed to many challenges, and ICANN must evolve to face the challenges. ICANN's mission and responsibilities are to the global community and stakeholders worldwide. To remain accountable to ICANN's mission and community, the Board recognizes that as a multistakeholder organization ICANN must evolve to fully execute on its mission, and be in a position to meet the challenges whether operational, political or technical. The continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. This is an Organizational Administrative Function for which public comment is not required. Published on 19 February 2014 -- David A. Olive Vice President, Policy Development Support General Manager, ICANN Regional Headquarters –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Hakki Yeten Cad. Selenium Plaza No:10/C K:5 34349 Fulya, Besiktas, Istanbul, Turkey Tel: +90.212.381.8727 - Fax: +90.212.381.8731 - Mobile: +1. 202.341.3611  -------------------------------------------------------------------------------- _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 1