- ispcp - lists.icann.org

Fwd: [council] WEBINAR: ICANN Strategy Panel on ICANN Multistakeholder Innovation
by Mike O'Connor Jan. 27, 2014

Jan. 27, 2014

hi all, i’ve been tracking this one fairly closely and spraying comments all over their idea-collecting site. my primary goal has been to set the record straight on some of the comment threads, which have proposed some pretty “edgy” stuff. my sense is that: a) the “crowdsourced” ideas are pretty thin b) the panel is composed of people who aren’t very close to what we actually do down here at the bottom of the bottom-up process. so i’m going to be very interested to see what they propose in this webinar a week from today. mikey Begin forwarded message: > From: Marika Konings <marika.konings(a)icann.org> > Subject: [council] WEBINAR: ICANN Strategy Panel on ICANN Multistakeholder Innovation > Date: January 24, 2014 at 1:46:42 AM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > http://www.icann.org/en/news/announcements/announcement-23jan14-en.htm > > ________________________________ > WEBINAR: ICANN Strategy Panel on ICANN Multistakeholder Innovation > > 23 January 2014 > > Join the Strategy Panel on ICANN Multistakeholder Innovation<http://www.icann.org/en/about/planning/strategic-engagement/multistakeholde…> for an update and interactive discussion. > > Date: Friday, 31 January 2014 > Time: 16:30-17:30 UTC (time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=MSI+Strategy+Panel…) > > You are invited to an update on the activities of the Strategy Panel on ICANN Multistakeholder Innovation. The work of the ICANN Strategy Panels<http://www.icann.org/en/news/announcements/announcement-15jul13-en.htm> will inform ICANN's new, overarching vision and five-year strategic plan. > > As it prepares to offer its advice to the ICANN President and CEO, the Multistakeholder Innovation Strategy Panel wishes to walk you through the work it has undertaken and to seek your input on the preliminary set of conclusions it has reached. This webinar will also be the opportunity for you to ask questions. ICANN Strategy Panels serve as an integral part of a framework for cross-community dialogue: your feedback and contributions are key to this project and will be carefully considered. Panel output will be posted for community consideration and public comment. > > Webinar Details > > The webinar will be run in an Adobe Connect room with a slide presentation along with a dial-in conference bridge for audio. The session will be conducted in English. > > Participants will be given the opportunity to offer comments and to ask questions during the Q&A section. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you cannot join the live session, the recording of the session will be made available shortly after the meeting. > > Please register via email to alice.jansen(a)icann.org<mailto:alice.jansen@icann.org> by Thursday, 30 January 2014 – 23:59 UTC to receive the dial-in details. A reminder with log-in and dial-in details will be sent to you prior to the call. > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 2

Draft definitions - FINAL - 16 January 2013 with Gomes input
by WUKnoben Jan. 27, 2014

Jan. 27, 2014

All, attached are the “draft definitions” discussed at the time being within the policy & implementation WG. In order to – for the time being – close the discussion this – for the time being! - is the last call for input/amendments/comments. Any “fresh-minded” contribution by COB Jan 29 would be helpful. Thanks and best regards Wolf-Ulrich

1 0

string delegations
by Mike O'Connor Jan. 25, 2014

Jan. 25, 2014

hi all here are all the strings delegated last week. mikey DATE STRING REGISTRY 18 January 2014 .CLUB .Club Domains, LLC 18 January 2014 .BUILD Plan Bee, LLC 18 January 2014 .PICS Uniregistry, Corp. 18 January 2014 .PINK Afilias Limited 18 January 2014 .LUXURY Luxury Partners, LLC 18 January 2014 .PHOTO Uniregistry, Corp. 18 January 2014 .GIFT Uniregistry, Corp. 18 January 2014 .网络 (xn--io0a7i) – Chinese for "network" Computer Network Information Center of Chinese Academy of Sciences (China Internet Information Center) 18 January 2014 .公司 (xn--55qx5d) – Chinese for "company" Computer Network Information Center of Chinese Academy of Sciences (China Internet Information Center) 18 January 2014 .MONASH Monash University 18 January 2014 .RICH I-REGISTRY Ltd. Niederlassung Deutschland 18 January 2014 .RED Afilias Limited 18 January 2014 .SHIKSHA Afilias Limited 18 January 2014 .中信 (xn--fiq64b) – Chinese for "CITIC" CITIC Group Corporation 18 January 2014 .LINK Uniregistry, Corp. 18 January 2014 .GUITARS Uniregistry, Corp. 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 _______________________________________________ gTLD-delegations mailing list - sponsored by ICANN's ISP and Connectivity Provider constituency (www.ISPCP.info) gTLD-delegations(a)ispcp.info http://ispcp.info/mailman/listinfo/gtld-delegations - click this link to subscribe, or review list information and prior posts

1 0

Interesting BCG analysis, sponsored by ICANN, "Greasing the Wheels of the Internet Economy: The Connected World"
by Mike O'Connor Jan. 25, 2014

Jan. 25, 2014

hi all, i’m finding this to be a nice combination of my two policy hobbies (ICANN and Minnesota broadband). http://www.bcg.com/expertise_impact/PublicationDetails.aspx?id=tcm:12-15288… To help “grease the wheels” of the digital economy, the BCG e-Friction Index measures the four types of friction that prevent consumers, companies, and countries from realizing the full benefits of the digital economy. Smart policy can address e-friction and speed the development of Internet use and individual countries’ Internet economies. PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 1

Fwd: [council] New gTLD update webinar presentation
by Mike O'Connor Jan. 24, 2014

Jan. 24, 2014

Begin forwarded message: > From: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> > Subject: [council] New gTLD update webinar presentation > Date: January 23, 2014 at 11:54:20 PM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > Hello All, > > From: http://newgtlds.icann.org/en/announcements-and-media/webinars > > Attached is the presentation from the new gTLD update webinar held > > Date/Time: 22 January 2014, 17:00 - 18:30 UTC > > General information on the current status of the Program. Topics include Evaluation, Contracting, Pre-Delegation Testing, Objections & Dispute Resolution, GAC Advice, Name Collision, Trademark Clearinghouse, etc. > > 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

Fwd: [council] GNSO Project List
by Mike O'Connor Jan. 21, 2014

Jan. 21, 2014

hi all, this is a great summary of status the various PDP and non-PDP working groups currently under way in the GNSO mikey Begin forwarded message: > From: Glen de Saint Géry <Glen(a)icann.org> > Subject: [council] GNSO Project List > Date: January 21, 2014 at 2:45:36 AM CST > To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > > > Dear Councillors, > > Attached please find the updated Project List, both red line and clean versions, for your review in preparation for the Council meeting on 23 January 2014. The clean version will be posted on the website http://gnso.icann.org/meetings/projects-list.pdf > > 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.)

1 0

Fwd: [council] Revised Proposed Agenda for the GNSO Council Teleconference 23 January 2013
by Novoa, Osvaldo Jan. 21, 2014

Jan. 21, 2014

Dear all, Do you have any objections to the proposed chairs, co-chairs and vice-chairs for the Privacy & Proxy Services Accreditation Issues PDP working group and the Translation and Transliteration of Contact Information PDP Working Group? Thank you for your comments. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>> Fecha: 20 de enero de 2014 20:59:35 GMT-2 Para: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Asunto: [council] Revised Proposed Agenda for the GNSO Council Teleconference 23 January 2013 Dear Councillors, Please find the updated draft agenda for the GNSO Council Teleconference 23 January 2013 at 18:00 UTC. The latest updates are as follows. 1. The time allotted to each item has been revised. 2. The Consent agenda has two more items added, namely: 3.2 Confirm Don Blumenthal – RySG as Chair and Steve Metalitz - IPC and Graeme Bunton - RrSG as Vice-Chairs for the Privacy & Proxy Services Accreditation Issues PDP working group. 3.3 Confirm Chris Dillon – NCSG and Rudi Vansnick – NPOC as co-chairs of the Translation and Transliteration of Contact Information PDP Working Group. Thank you for sharing this among your constituency and stakeholder groups. Please let me know if you have any questions. Kind regards, Glen Proposed Agenda for the GNSO Council Teleconference 23 January 2013 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.1 Approve Council Recommendations Report on protection of IGO-INGO names and acronyms to the ICANN Board. 3.2 Confirm Don Blumenthal – RySG as Chair and Steve Metalitz - IPC and Graeme Bunton - RrSG as Vice-Chairs for the Privacy & Proxy Services Accreditation Issues PDP working group. 3.3 Confirm Chris Dillon – NCSG and Rudi Vansnick – NPOC as co-chairs of the Translation and Transliteration of Contact Information PDP Working Group. 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-16jan14-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 (15 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 (15 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: DISCUSSION – International Internet Governance Issues (15 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 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) 9.2 – Discussion 9.3 – Next steps Item 10: Any Other Business (10 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.…>) 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(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

2 2

[gTLD-delegations] string delegations
by Mike O'Connor Jan. 18, 2014

Jan. 18, 2014

hi all Mikey's list interesting strings delegated this week -- from a name-collisions standpoint. purely a gut-feel reaction, there's no science behind this list just the eye of a system admin making a guess that these names are more likely to show as names for internal resources on networks. .ZONE here are all the strings delegated last week. mikey DATE STRING REGISTRY 14 January 2014 .ZONE Outer Falls, LLC 14 January 2014 .CHEAP Sand Cover, LLC 14 January 2014 .MARKETING Fern pass, LLC 14 January 2014 .DEMOCRAT United TLD Holdco Ltd. 14 January 2014 .SOCIAL United TLD Holdco Ltd. 14 January 2014 .AGENCY Steel Falls, LLC 14 January 2014 .MODA United TLD Holdco Ltd. 14 January 2014 .DANCE United TLD Holdco Ltd. 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 _______________________________________________ gTLD-delegations mailing list - sponsored by ICANN's ISP and Connectivity Provider constituency (www.ISPCP.info) gTLD-delegations(a)ispcp.info http://ispcp.info/mailman/listinfo/gtld-delegations - click this link to subscribe, or review list information and prior posts

1 0

Fwd: ICANN News Alert -- WEBINAR: ICANN Strategy Panel on Identifier Technology Innovation
by Mike O'Connor Jan. 18, 2014

Jan. 18, 2014

Begin forwarded message: > From: "ICANN News Alert" <communications(a)icann.org> > Subject: ICANN News Alert -- WEBINAR: ICANN Strategy Panel on Identifier Technology Innovation > Date: January 17, 2014 at 6:41:59 PM CST > To: <mike(a)haven2.com> > > > News Alert > > http://www.icann.org/en/news/announcements/announcement-17jan14-en.htm > > WEBINAR: ICANN Strategy Panel on Identifier Technology Innovation > 17 January 2014 > Join the Strategy Panel on Identifier Technology Innovation for an update and interactive discussion. > > Date: Wednesday, 22 January 2014 > Time: 03:00-04:30 UTC (Time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Strategy+Panel+on+…) > > Date: Thursday, 23 January 2014 > Time: 19:00-20:30 UTC (Time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Strategy+Panel+on+…) > > > You are invited to an update on the activities of the Strategy Panel on Identifier Technology Innovation. ICANN Strategy Panels' work will inform ICANN's new, overarching vision and five-year strategic plan. > > As it prepares to offer its advice to the ICANN President and CEO, the Strategy Panel wishes to walk you through the work it has undertaken and to seek your input on the preliminary set of conclusions it has reached. This webinar will also be the opportunity for you to ask questions. ICANN Strategy Panels serve as an integral part of a framework for cross-community dialogue: your feedback and contributions are key to this project and will be carefully considered. > > Webinar Details > > Please join the webinar either on Wednesday, 22 January 2014 at 03:00-04:30 UTC (duration: 90 minutes) or on Thursday, 23 January 2014 at 19:00-20:30 UTC (duration: 90 minutes). The two sessions are duplicates, scheduled to accommodate different time zones. The meetings will be run in an Adobe Connect room with a slide presentation along with a dial-in conference bridge for audio. The sessions will be conducted in English. > > Participants will be given the opportunity to offer comments and to ask questions during the Q&A section. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you cannot join the live session, the recording of the session will be made available shortly after the meeting. > > Please register via email to alice.jansen(a)icann.org by Tuesday, 21 January 2014 – 23:59 UTC to receive the dial-in details. Please indicate which call you wish to join. A reminder with log-in and dial-in details will be sent to you prior to the call. > > > > 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

RV: [council] Request for input from the GNSO Policy & Implementation Working Group
by Novoa, Osvaldo Jan. 17, 2014

Jan. 17, 2014

Dear all, We should answer this request. How should we do it? Best regards, Osvaldo [cid:293105216@17012014-0667]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ De: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] En nombre de Jonathan Robinson Enviado el: Viernes, 17 de Enero de 2014 14:22 Para: council(a)gnso.icann.org CC: Gomes, Chuck; jscottevans(a)outlook.com Asunto: [council] Request for input from the GNSO Policy & Implementation Working Group Importancia: Alta All, Please be aware of the Request for input from the GNSO Policy & Implementation Working Group (see below). This is a working group of substantial interest and importance as evidenced by: 1. The level of interest that related topics have attracted during the roll-out of the new gTLD programme 2. The level of interest indicated by the sheer number of participants in the working group. Notwithstanding that, the Working Group has not received much in the way of input in response to its call for input (first sent out in October 2013). Therefore, this note is to draw your attention to this and to ask you to please encourage your respective groups / constituencies to provide such input to the WG as soon as possible. For information and completeness, the questions from the working group are copied below AND attached in long form (as sent to SO & ACs) to this note. Thank-you. Jonathan --- This Working Group (P&I WG) has been tasked with providing the GNSO Council with a set of recommendations on the following issues: - A set of principles that would underpin any GNSO policy implementation related discussions, taking into account existing GNSO procedures; - A process for developing gTLD policy, perhaps in the form of "Policy Guidance," including criteria for when it would be appropriate to use such a process (for a process developing something other than "Consensus Policy") instead of the GNSO Policy Development Process; - A framework for implementation related discussions associated with GNSO Policy recommendations; - Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation; and - Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate. >From the onset of this process, the WG would like to gain input. In this regard, the WG would ask organizations to consider and provide input on the following questions which are set out in the WG's Charter. 1. What guidance do the ICANN core values (Bylaws Article 1, Sec. 2) directly provide with regard to policy development work and policy implementation efforts? 2. What guidance do other ICANN core values provide that relate indirectly to policy development and policy implementation? 3. "Questions for Discussion" contained in the Policy and Implementation Draft Framework prepared by ICANN staff. (See, http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-e…) 4. What lessons can be learned from past experience? * What are the consequences of action being considered "policy" or "implementation"? * Does it matter if something is "policy" or "implementation"? If so, why? * Under what circumstances, if any, should the GNSO Council make recommendations or state positions to the Board on matters of policy and implementation as a representative of the GNSO as a whole? * How do we avoid the current morass of outcome-derived labeling (i.e., I will call this "policy" because I want certain consequences or "handling instructions" to be attached to it?) * Can we answer these questions so the definitions of "policy" and "implementation" matter less, if at all? 5. What options are available for policy ("Consensus Policy" or other) and implementation efforts and what are the criteria for determining which should be used? * Are "policy" and "implementation" on a spectrum rather than binary? * What are the variations of policy and what consequences should attach to each variation? * What happens if you change those consequences? 6. Who determines the choice of whether something is "policy" or "implementation"? * How is policy set/recommended/adopted and do different paths lead to different variations? * How is the "policy" and "implementation" issue reviewed and approved? * What happens if reviewing bodies come to a deadlock? 7. What is the process by which this identification, analysis, review and approval work is done? * How are "policy and implementation" issues first identified (before, during and after implementation)? * What is the role of the GNSO in implementation? * In order to maintain the multi-stakeholder process, once policy moves to implementation, how should the community be involved in a way that is meaningful and effective? * Should policy staff be involved through the implementation process to facilitate continuity of the multi-stakeholder process that already occurred? ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0