December 2015 - At-Large - lists.icann.org

Fwd: [council] Final Issue Report on New gTLD Subsequent Procedures
by Olivier MJ Crepin-Leblond Jan. 21, 2016

Jan. 21, 2016

FYI the report is attached. ALAC comments have, on the whole, been taken into account. Kindest regards, Olivier MJ Crépin-Leblond ALAC Liaison to the GNSO -------- Forwarded Message -------- Subject: [council] Final Issue Report on New gTLD Subsequent Procedures Date: Fri, 4 Dec 2015 23:15:30 +0000 From: Steve Chan <steve.chan(a)icann.org> To: council(a)gnso.icann.org <council(a)gnso.icann.org> Dear Councilors, Please find attached for your consideration the Final Issue Report on New gTLD Subsequent Procedures, which is also available here: http://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-final-issue…. You may recall that the Council requested an Issue Report on the topic at the Buenos Aires meeting in June 2015. Under the ICANN Bylaws, an Issue Report is a mandatory preceding step to a possible PDP that is initiated by the GNSO Council. The Preliminary Issue Report was published for public comment on 31 August 2015, with the forum closing on 30 October 2015. The Report of Public Comments received is expected to be published on 4 December 2015 and made available here: https://www.icann.org/public-comments/new-gtld-subsequent-prelim-2015-08-31…. In preparing this Final Issue Report, all the public comments received were analyzed and, where relevant, incorporated into the Final Issue Report. The Report of Public Comments has also been added as a separate Annex. The staff recommendation is that the Council initiate a PDP to consider and analyze issues discussed in the Final Issue Report on New gTLD Subsequent Procedures to determine whether changes or adjustments to the existing policy recommendations in the Final Report on the Introduction of New Generic Top-Level Domains are needed. The outcome of the PDP may lead to (i) amending or overriding existing policy principles, recommendations, and implementation guidelines; (ii) developing new policy recommendations, and/or (iii) supplementing or developing new implementation guidance. The relevant motions are currently in preparation for proposal by a GNSO Councilor. If you have any questions or concerns, please let me know. Best, *Steven Chan* Sr. Policy Manager *ICANN *12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 steve.chan(a)icann.org <mailto:steve.chan@icann.org> direct: +1.310.301.3886 mobile: +1.310.339.4410 tel: +1.310.301.5800 fax: +1.310.823.8649

14 34

Weekly posting summary for at-large@atlarge-lists.icann.org
by Thomas Narten Dec. 25, 2015

Dec. 25, 2015

Total of 36 messages in the last 7 days. script run at: Fri Dec 25 00:53:02 EST 2015 Messages | Bytes | Who --------+------+--------+----------+------------------------ 5.56% | 2 | 59.13% | 6875479 | jjs at dyalog.net 5.56% | 2 | 17.94% | 2085388 | vanda at scartezini.org 2.78% | 1 | 17.84% | 2074678 | wafa at ati.tn 13.89% | 5 | 1.14% | 132852 | carlton.samuels at gmail.com 11.11% | 4 | 0.81% | 94159 | cdel at firsthand.net 8.33% | 3 | 0.50% | 58423 | kankaili at gmail.com 8.33% | 3 | 0.47% | 54822 | devtee at gmail.com 8.33% | 3 | 0.28% | 32905 | karl at cavebear.com 5.56% | 2 | 0.43% | 49708 | alan.greenberg at mcgill.ca 5.56% | 2 | 0.37% | 43143 | staff at atlarge.icann.org 5.56% | 2 | 0.28% | 32710 | ocl at gih.com 5.56% | 2 | 0.13% | 15360 | johnl at iecc.com 2.78% | 1 | 0.29% | 34149 | apisan at unam.mx 2.78% | 1 | 0.11% | 12820 | tijani.benjemaa at benjemaa.com 2.78% | 1 | 0.10% | 11128 | vanda at uol.com.br 2.78% | 1 | 0.09% | 9919 | cw at christopherwilkinson.eu 2.78% | 1 | 0.08% | 9340 | narten at us.ibm.com --------+------+--------+----------+------------------------ 100.00% | 36 |100.00% | 11626983 | Total

1 0

I: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary Determination To Grant Registrar Data Retention Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA
by Roberto Gaetano Dec. 24, 2015

Dec. 24, 2015

I am just wondering how much this overhead does cost. Instead of complying with European law, ICANN has chosen to disregard it, and now is obliged to grant waivers one by one to European registrars. Am I the only one who thinks that this is plain silly? Cheers, R. > -----Messaggio originale----- > Da: alac-announce-bounces(a)atlarge-lists.icann.org [mailto:alac-announce- > bounces(a)atlarge-lists.icann.org] Per conto di ICANN At-Large Staff > Inviato: giovedì 10 dicembre 2015 04:03 > A: alac-announce(a)atlarge-lists.icann.org > Oggetto: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary > Determination To Grant Registrar Data Retention Waiver Request for Ascio > Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA > > > [ICANN]<http://www.icann.org/> > News Alert > > https://www.icann.org/news/announcement-2015-12-09-en > > ________________________________ > Notice of Preliminary Determination To Grant Registrar Data Retention > Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio > Technologies, Inc. USA > > 9 December 2015 > > ICANN has made a preliminary determination that it is prepared to grant a > data retention waiver request submitted by Registrar Ascio Technologies, > Inc. Danmark - filial af Ascio Technologies, Inc. USA ("Ascio") under the 2013 > Registrar Accreditation Agreement (the "2013 RAA"). Section 2 of the Data > Retention Specification (the "Specification") of the 2013 RAA provides that > prior to granting any exemption under the Specification, ICANN will post its > determination on the ICANN website for a period of thirty (30) calendar days. > > Pursuant to Section 2 of the Specification, Ascio has submitted to ICANN a > Registrar data retention waiver request ("Waiver Request") on the basis of > Ascio's contention that compliance with the data collection and/or retention > requirements of the Specification violates applicable law in Denmark. > > The Waiver Request was accompanied by a written legal opinion from a > nationally recognized law firm citing section 5 (5) of the Danish Act on > Processing of Personal Data of 31 May 2000 (the "DPPD"). That section > provides as follows (the following is an unofficial English translation from > Danish): > > Section 5 (5). > > The data collected may not be kept in a form which makes it possible to > identify the data subject for a longer period than is necessary for the > purposes for which the data are processed. > > Following receipt of the Waiver Request, and in accordance with the 2013 > RAA, ICANN through its legal counsel and Ascio discussed the matter in good > faith in an effort to reach a mutually acceptable resolution of the matter. > > The outcome of those discussions is that Ascio is seeking a waiver with > respect to Sections 1.1.1 through 1.1.8 of the Specification that seeks to > reduce from two years to one year the period for which these specified data > elements must be retained after the Registrar's sponsorship of the > Registration ends. > > ICANN has determined on a preliminary basis that it is prepared to grant the > Waiver Request. ICANN is posting this preliminary determination for a period > of thirty (30) calendar days to seek feedback and input from the community > on the proposed data retention waiver. After the thirty (30) calendar day > period following this posting has expired, ICANN will consider all feedback > and input received before making a final determination on whether to grant > the Waiver Request. > > The scope of the proposed waiver would be to permit Ascio to maintain the > information specified in Sections 1.1.1 through 1.1.8 of the Specification for > the duration of its sponsorship of the Registration and for a period of one (1) > additional year thereafter rather than two (2) additional years thereafter. In > all other respects the terms of the Specification would remain AS-IS. > > The specific change to the Specification would be that, for the duration of the > Waiver, the retention requirement of Section 1.1 of the Data Retention > Specification be changed from "two additional years" to "one additional > year." > > If ICANN does make a final determination to grant the Waiver Request > sought by Ascio, the provisions of Section 3 of the Specification would apply > to similar waivers requested by other registrars located in Denmark and > subject to Danish law. Section 3 of the Specification provides as follows: > > If (i) ICANN has previously waived compliance with the requirements of any > requirement of this Data Retention Specification in response to a Waiver > Request from a registrar that is located in the same jurisdiction as Registrar > and (ii) Registrar is subject to the same applicable law that gave rise to > ICANN's agreement to grant such waiver, Registrar may request that ICANN > to grant a similar waiver, which request shall be approved by ICANN, unless > ICANN provides Registrar with a reasonable justification for not approving > such request, in which case Registrar may thereafter make an Wavier > Request pursuant to Section 2 of this Data Retention Specification. > > The Registrar's Waiver Request and supporting documents are available > here: https://www.icann.org/en/system/files/files/waiver-request-ascio- > technologies-09dec15-en.pdf [PDF, 6.39 MB] > > A public comment period will remain open until 23:59 UTC, 11 January 2016. > Public comments will be available for consideration by ICANN staff and the > ICANN Board. > > * Comments can be posted to: comments-ascio-technologies- > 09dec15(a)icann.org<mailto:comments-ascio-technologies- > 09dec15(a)icann.org> > * Comments can be viewed at: http://forum.icann.org/lists/comments- > ascio-technologies-09dec15/

18 38

Reminder of ICANN's Expected Standards of Behavior
by ICANN At-Large Staff Dec. 23, 2015

Dec. 23, 2015

Dear All, Please note ICANN's expected standards of behavior (see: https://www.icann.org/resources/pages/expected-standards-2012-05-15-en) Of particular note are the following: * Treat all members of the ICANN community equally, irrespective of nationality, gender, racial or ethnic origin, religion or beliefs, disability, age, or sexual orientation; members of the ICANN community should treat each other with civility both face to face and online. * Act in a reasonable, objective and informed manner when participating in policy development and decision-making processes. This includes regularly attending all scheduled meetings and exercising independent judgment based solely on what is in the overall best interest of Internet users and the stability and security of the Internet's system of unique identifiers, irrespective of personal interests and the interests of the entity to which an individual might owe their appointment. * Listen to the views of all stakeholders when considering policy issues. ICANN is a unique multi-stakeholder environment. Those who take part in the ICANN process must acknowledge the importance of all stakeholders and seek to understand their points of view. * Act fairly and in good faith with other participants in the ICANN process. Kind regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yesim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

Call for Volunteers: Advisory Panel on gTLD Marketplace Health Index
by ICANN At-Large Staff Dec. 23, 2015

Dec. 23, 2015

Dear All, ICANN is calling for community volunteers to participate in the Advisory Panel on gTLD Marketplace Health Index. This Advisory Panel will review the proposed KPIs in the preliminary proposal of gTLD Marketplace Health Index<https://www.icann.org/en/system/files/files/gtld-marketplace-health-index-p…>, as well as the suggested potential updates in light of the public comment<https://www.icann.org/public-comments/gtld-marketplace-health-2015-11-17-en> on this preliminary proposal. The Advisory Panel will also be asked to assist ICANN in finalizing the list of KPIs and in setting proposed benchmarks for measuring the health of the global gTLD marketplace. As an FYI, the ALAC has responded to the public comment on the gTLD Marketplace Health Index Proposal and submitted a Statement: https://newatlarge.icann.org/advice_statements/9745. At-Large members interested in this topic are welcome to join the Advisory Panel. Experience in the global domain name industry, economics, and data analytics will be particularly helpful to the Advisory Panel's work. Perspectives from diverse regions and backgrounds will help ensure that the gTLD Marketplace Health Index presents a holistic view of the global domain name marketplace. If you are interested in volunteering for the Advisory Panel, please email amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> by 22 January 2016. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yesim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

Fwd: Announcement of ICANN Public Comment Improvements Assessment Report
by Carlton Samuels Dec. 22, 2015

Dec. 22, 2015

FYI. I was not following this closely, largely because I still believe the real issue for the At-Large is the lack of bandwidth due to low participation; only a few people still doing the heavy lifting of reading the reports so one could sensibly mount a credible response. To my mind the time is imminent for the ALAC to decide and cherry pick issues meriting response. I recall the arguments linking the lack of timely translation of reports as contributory to the low participation rate from At-Large representatives, never mind the requirement for working knowledge of English. I also recall some position on eliminating the Reply Time Period in favour of a longer Comment Period. Was there a final ALAC position here? CAS ============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment & Turnaround* ============================= Dear Community Leaders: Earlier this year the ICANN Policy Development Support Team took on the implementation of specific ATRT2 recommendations looking to evolve and improve various aspects of the ICANN Public Comments infrastructure and operations. As part of those staff implementation obligations, my team committed to assessing the implementation effort and to producing a report of that analysis for the community by the end of this year. I am pleased to share that the assessment report has now been completed and is posted on the community wiki at this link - https://community.icann.org/pages/viewpage.action?pageId=56987496. A pdf version of the report is available to download from that page. To help staff anticipate, envision and prepare for future improvements regarding how the organization manages, maintains and supports future community input streams, we are forming a staff Public Input Advisory Team pulling in representatives from different staff teams to share their perspectives. I am hopeful that we’ll be able to incorporate input and collaboration opportunities with community members to make that a practical, useful and valuable effort. If you or any member of community would be interested in contributing to such an effort, please drop me a line. We hope to get the group together at least once before the ICANN55 Marrakech meeting. Best Regards and Happy New Year, David David A. Olive Senior Vice President, Policy Development Support General Manager, ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 Mobile: + 1. 202.341.3611 Mobile: +90.533.341.6550 Email: david.olive(a)icann.org www.icann.org

2 1

season greeting to all colleagues around the world.
by Vanda Scartezini Dec. 21, 2015

Dec. 21, 2015

[cid:C5CE70AF-65C1-4CD6-909B-41BAB5B809F8] Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos.

3 2

Weekly posting summary for at-large@atlarge-lists.icann.org
by Thomas Narten Dec. 18, 2015

Dec. 18, 2015

Total of 51 messages in the last 7 days. script run at: Fri Dec 18 00:53:03 EST 2015 Messages | Bytes | Who --------+------+--------+----------+------------------------ 1.96% | 1 | 67.59% | 7843321 | leonfelipe at sanchez.mx 1.96% | 1 | 19.59% | 2273228 | mcknight.glenn at gmail.com 13.73% | 7 | 2.07% | 239886 | roberto_gaetano at hotmail.com 9.80% | 5 | 0.86% | 99226 | ocl at gih.com 7.84% | 4 | 2.39% | 276966 | vanda at scartezini.org 9.80% | 5 | 0.35% | 40444 | johnl at iecc.com 7.84% | 4 | 0.91% | 106051 | kankaili at gmail.com 5.88% | 3 | 0.59% | 68239 | cdel at firsthand.net 5.88% | 3 | 0.48% | 55765 | h.raiche at internode.on.net 3.92% | 2 | 0.48% | 55759 | seun.ojedeji at gmail.com 3.92% | 2 | 0.44% | 51605 | carlton.samuels at gmail.com 3.92% | 2 | 0.25% | 28687 | staff at atlarge.icann.org 3.92% | 2 | 0.13% | 15043 | karl at cavebear.com 1.96% | 1 | 1.07% | 123661 | maureen.hilyard at gmail.com 1.96% | 1 | 1.06% | 122976 | cw at christopherwilkinson.eu 1.96% | 1 | 0.75% | 86955 | adam.peake at icann.org 1.96% | 1 | 0.22% | 25730 | carlosaguirre62 at hotmail.com 1.96% | 1 | 0.20% | 23671 | alan.greenberg at mcgill.ca 1.96% | 1 | 0.17% | 19347 | at-large at atlarge-lists.icann.org 1.96% | 1 | 0.13% | 14520 | garth.graham at telus.net 1.96% | 1 | 0.11% | 12656 | seth.reiss at lex-ip.com 1.96% | 1 | 0.10% | 11659 | derek at aa419.org 1.96% | 1 | 0.08% | 8788 | narten at us.ibm.com --------+------+--------+----------+------------------------ 100.00% | 51 |100.00% | 11604183 | Total

1 0

Fwd: Paving the Way for a Next-Generation gTLD Registration Directory Service
by Carlton Samuels Dec. 17, 2015

Dec. 17, 2015

FYI. Note well, the call for PDP is set for booting on 4th January 2016. This is truly important work and following on the work of the EWG, it is a personal commitment to continue here, if only to valorise the great work (IMHO) coming out of the EWG. I trust we shall see a lot more At-Large participants - other than Holly and me - stepping up and signing up for what must be an extensive series of pdps....and multiple WGs. This usually attracts stellar staff support so I strongly encourage your connivance. CAS ============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment & Turnaround* ============================= h ttps://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-re… <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> Paving the Way for a Next-Generation gTLD Registration Directory Service <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> <https://www.icann.org/news/blog/paving-the-way-for-a-next-generation-gtld-r…> I am pleased to provide you with an update about ICANN's progress on establishing a policy framework for a next-generation gTLD Registration Directory Service (RDS) to replace WHOIS. On 19 November, 2015, the GNSO Council approved a charter <http://gnso.icann.org/en/council/resolutions#201511> for the Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS (Next-Gen RDS) Policy Development Process (PDP) Working Group. This motion culminates a three-year effort to address concerns with WHOIS by creating a new policy framework capable of balancing diverse interests to meet today's needs for gTLD registration data. What's Next The GNSO Council is now proceeding with the Board-requested PDP, using the approved charter's <http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf> [PDF, 628 KB] 3-phase process to (1) establish gTLD registration data requirements to determine if and why a next-generation RDS is needed, (2) design policies that detail functions that must be provided by a next-generation RDS to support those requirements, and (3) provide guidance for how a next-generation RDS should implement those policies, coexisting with and eventually replacing WHOIS. In its motion, the GNSO Council directed that the call for volunteers for the PDP WG be circulated as widely as possible in order to ensure broad representation and participation in the Working Group. This call will be initiated by 4 January 2016 and will remain open until the WG convenes for the first time. At this juncture, it is anticipated that the WG may convene late January to lay the groundwork for an initial face-to-face meeting at ICANN 55. All parties interested in a new policy framework for a next-generation RDS to replace WHOIS are invited to visit the RDS Wiki <https://community.icann.org/display/gTLDRDS/Next-Generation+gTLD+Registrati…> for background information, including the PDP WG's approved charter, inputs already provided by all SG/Cs during the public comment period, and an extensive library of foundational materials to inform the PDP WG's deliberations. In addition, the PDP WG will reach out to all SG/Cs for feedback on any items that they believe should be considered that may not have been specifically called out in the approved charter. As this will be a complex multi-phase PDP, all those interested in helping to shape the policy framework for a next-generation gTLD RDS are encouraged to volunteer for this PDP WG. Only with the help of the entire community can this PDP WG achieve its goal of formally defining an appropriate purpose of gTLD registration data and establishing a new policy framework to enable permissible access to that data with improved privacy and accuracy. Background and Recent Progress Created in the 1980s, WHOIS began as a service to identify and contact entities responsible for the operation of a network resource on the Internet. Over the years, ICANN's requirements for gTLD domain name registration data collection, access and accuracy have undergone some important changes. Yet, after nearly 15 years of task forces, review teams, and studies, comprehensive WHOIS policy reform remains the source of long-running discussion and debate. In 2012, the ICANN Board launched the Expert Working Group on gTLD Registration Directory Services (EWG) to help redefine the purpose of gTLD registration data and consider how to safeguard the data, and to propose a model for gTLD registration directory services (RDS) to address accuracy, privacy, and access issues. Upon publication of the EWG's Final Report in June, 2014, an informal group of GNSO Councilors and ICANN Board Members collaborated to propose a Process Framework for structuring a GNSO PDP to successfully address these challenging issues. This Process Framework was adopted by the Board in 2015, along with a reaffirmation of its 2012 request for a PDP to be convened to define the purpose of collecting, maintaining and providing access to gTLD registration data. The Board also asked that the PDP consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. In preparation for this PDP, a new Preliminary Issue Report <http://whois.icann.org/sites/default/files/files/rds-prelim-issue-13jul15-e…> [PDF, 1.4 MB] was published for public comment <https://www.icann.org/public-comments/rds-prelim-issue-2015-07-13-en> on 13 July 2015. A Final Issue Report <https://whois.icann.org/sites/default/files/files/final-issue-report-next-g…> [PDF, 1.2 MB] was subsequently published on 7 October 2015, including links to all public comments received, along with a draft charter for the PDP WG. This draft charter was approved by the GNSO Council on 19 November 2015 <https://community.icann.org/display/gnsocouncilmeetings/Motions+19+November…>, enabling the formation of a GNSO working group of community volunteers to progress this PDP. Author: Marika Konings, Senior Policy Director, Policy Development Support and Team Leader for the Generic Names Supporting Organization (GNSO) David A. Olive Senior Vice President, Policy Development Support General Manager, ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 Mobile: + 1. 202.341.3611 Mobile: +90.533.341.6550 Email: david.olive(a)icann.org www.icann.org

2 1

New Public Comment: Release of Country and Territory Names within the .STUDY, .COURSES, .LAMBORGHINI, XN--3OQ18VL8PN36A, .VOLKSWAGEN, .BUGATTI, .AUDI and .DELTA TLDs
by ICANN At-Large Staff Dec. 17, 2015

Dec. 17, 2015

Dear All, This is to let you know that the Public Comment on the Release of Country and Territory Names within the .STUDY, .COURSES, .LAMBORGHINI, XN--3OQ18VL8PN36A, .VOLKSWAGEN, .BUGATTI, .AUDI and .DELTA TLDs has now gone live: https://www.icann.org/public-comments/ctn-release-tlds-2015-12-15-en. The dates of the Public Comment will be 15 December 2015 - 27 January 2016 23:59 UTC. During this period, anyone can submit comment via comments-ctn-release-tlds-15dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/6o5lAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

CALL FOR COMMENTS: ALAC Statement on the CCWG-Accountability - Draft Proposal on Work Stream 1 Recommendations
by ICANN At-Large Staff Dec. 15, 2015

Dec. 15, 2015

Dear All, On behalf of the ALAC, Alan Greenberg has developed the first draft ALAC Statement on the CCWG-Accountability - Draft Proposal on Work Stream 1 Recommendations<https://community.icann.org/x/d4NlAw>. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/d4NlAw. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function by 20 December 2015 at 23:59 UTC. You will need to log in to the wiki to use the comment function. If you don't have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation
by Roberto Gaetano Dec. 14, 2015

Dec. 14, 2015

I will be unable to attend the call, but I read the doc and I have one point that I believe is important. There seems to be a misunderstanding about ALAC and the ALSes: either myself, or ICANN staff, have it wrong. I see an ICANN staff comment saying: Been pointed out that some ALS represent business interests, some technical, some may consider their organizations multistakeholder, and of course some civil society, noting "Not for profit organizations that serve for profit/commercial interests would not be within scope" Now, reading the criteria for ALS certification, I see: If an organisation receives corporate or government funding or has members who are government agencies or for-profit entities such members are allowed, provided such members do not interfere with, direct, or otherwise affect the mission, purpose or operations of the organisation This, to me, means that no ALS would serve for profit/commercial interests, because that would be violating certification criteria. If any ALS has members that are representing either governments or for-profit entities, these must be in such position not to affect the mission, purpose or operations of the ALS itself. Therefore, the ALS, when certified, is guaranteed not to be promoting for-profit or government agendas. Can we have this straightened up once and for good? Alternatively, may I know which are the At-Large Structures that allegedly represent business interests? Cheers, Roberto Da: alac-announce-bounces(a)atlarge-lists.icann.org [mailto:alac-announce-bounces@atlarge-lists.icann.org] Per conto di ICANN At-Large Staff Inviato: venerdì 11 dicembre 2015 15:12 A: ALAC Announce Oggetto: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation On behalf of Jean-Jacques Sahel and Adam Peake Dear All, Please find below participation details for Civil Society Engagement Approach: Call to discuss Implementation on Wednesday 16 Dec 2015 at 14:00 UTC This call is for ICANN Staff and the community to start planning together joint activities and other deliverables such as new content production for the coming months, under the new civil society engagement approach. A draft agenda will be circulated for comments shortly. Please remember that you can comment on the draft Civil Society engagement strategy by end of Friday 11 December here: https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlBc qWQ/edit?pli=1 The revised document will be circulated ahead of the call on December 16. This call will be in English only. Thank you. Regards, Jean-Jacques Sahel & Adam Peake ---------------------------------------------------------------------------- ------------------------------------------------------------------- Link to Adobe Connect: <https://icann.adobeconnect.com/gseemea/> https://icann.adobeconnect.com/gseemea/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). If you wish only audio, click on the Connect Me icon or dial in using one of the numbers hereunder: __________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. <https://go.conferencinghub.com/20sll> Connect Me Not at your computer? You can join by dialing one of the access numbers below. Mobile: <tel://1-719-457-6209,*,,3938083611/> tel://1-719-457-6209,*,,3938083611# Phone Only Controls: <https://go.conferencinghub.com/20sll> https://go.conferencinghub.com/20sll Primary Access Number: 1-719-457-6209 Guest Passcode: 393 808 3611 Additional Access: USA 1-719-457-6209 Canada, Calgary +1 403 407 5793 Canada, Montreal +1 514 669 5928 Canada, Toronto +1 647 426 9172 Canada, Vancouver +1 604 222 7836 Argentina (toll free) 0800 800 1223 Argentina, Buenos Aires +54 (0) 11 5172 6003 Australia (toll free) 1 800 804 786 Australia, Brisbane +61 (0) 7 3015 0535 Australia, Melbourne +61 (0) 3 8687 0553 Australia, Sydney +61 (0) 2 8017 6064 Austria (toll free) 0800 8866 3413 Austria, Vienna +43 (0) 1 25302 1785 Bahrain (toll free) 800 04212 Bahrain, Manama +973 1619 8739 Belarus (toll free) 8 820 0011 0341 Belgium (toll free) 0800 39279 Belgium, Brussels +32 (0) 2 400 6928 Brazil (toll free) 0800 887 0233 Brazil, Rio de Janeiro +55 21 4560 0072 Brazil, Sao Paulo +55 11 4935 7169 Bulgaria (toll free) 00800 111 4950 Bulgaria, Sofia +359 (0) 2 491 6045 Canada (toll free) 1 855 950 3717 Chile (toll free) 171 800 835 783 Chile, Santiago +56 (0) 2 2666 0696 China (national) +400 613 8103 China, Beijing +86 10 5667 0003 China, Shanghai +86 21 2039 7081 Colombia (toll free) 01 800 755 0102 Colombia, Bogota +57 1 508 8137 Costa Rica (toll free) 800 542 5328 Croatia (toll free) 0800 805 940 Cyprus (toll free) 800 97424 Czech Republic (toll free) 800 701 532 Czech Republic, Prague +420 225 986 554 Denmark (toll free) 80 70 35 86 Denmark, Copenhagen +45 32 72 78 10 Egypt (toll free) 0800 000 0593 Estonia (toll free) 800 011 1589 Estonia, Tallinn +372 622 6551 Fiji (toll free) 00800 3322 Finland (toll free) 0800 772 236 Finland, Helsinki +358 (0) 9 2310 1677 France (national) 0811 655 100 France (toll free) 0800 946 531 France, Paris +33 (0) 1 70 37 16 56 Germany (national) 01801 003 899 Germany (toll free) 0800 588 9170 Germany, Frankfurt +49 (0) 69 2222 10612 Germany, Munich +49 (0) 89 2030 31207 Greece (toll free) 00800 128 913 Greece, Athens +30 211 181 3824 Hong Kong +852 3018 9111 Hong Kong (toll free) 800 901 787 Hungary (toll free) 068 001 9673 Hungary, Budapest +36 1408 8953 Iceland (toll free) 800 9847 India (toll free) 000 800 1008 367 India, Bangalore +91 (0) 80 6127 6710 India, Chennai +91 (0)44 6688 6061 India, Delhi +91 (0) 11 6641 1394 India, Mumbai +91 (0)22 6187 5028 Indonesia (toll free) 007 803 321 8927 Ireland (national) 1890 907 630 Ireland (toll free) 1800 937 649 Ireland, Dublin +353 (0) 1 526 9421 Israel (toll free) 1809 213 168 Israel, Tel Aviv +972 (0)3 721 7943 Italy (toll free) 800 146 094 Italy, Milan +39 02 3600 8006 Italy, Rome +39 06 8750 0676 Japan (mobile) 0120 632 611 Japan (toll free) 0120 305 211 Japan, Chiba +81 (0) 43 321 6881 Japan, Fukuoka +81 (0) 92 290 6881 Japan, Hiroshima +81 (0) 82 558 6881 Japan, Nagoya +81 (0) 52 850 6881 Japan, Osaka +81 (0) 6 4560 2410 Japan, Sapporo +81 (0) 11 234 6881 Japan, Sendai +81 (0) 22 708 6881 Japan, Shizuoka +81 (0) 54 902 6881 Japan, Tachikawa +81 (0) 42 841 6881 Japan, Tokyo +81 (0) 3 4560 1270 Japan, Toyama +81 (0) 76 408 6881 Japan, Urawa +81 (0) 48 698 6881 Japan, Yokohama +81 (0) 45 677 6881 Kazakhstan (toll free) 8800 333 7554 Latvia (toll free) 8000 4418 Latvia, Riga +371 6601 3627 Lithuania (toll free) 8800 31449 Lithuania, Vilnius +370 5205 5468 Luxembourg +352 2088 1749 Luxembourg (toll free) 800 28433 Malaysia (toll free) 1 800 816 152 Malaysia,Kuala Lumpur +60 (0) 3 7724 8010 Mexico (toll free) 01 800 733 4102 Mexico, Guadalajara +52 33 4162 4504 Mexico, Mexico City +52 55 8421 0326 Mexico, Monterrey +52 81 4162 5648 Morocco (toll free) 0800 091 296 Morocco, Casablanca +212 (0) 520 48 0022 Netherlands (toll free) 0800 020 2597 Netherlands, Amsterdam +31 (0) 20 716 8345 New Zealand (toll free) 0800 452 947 New Zealand, Auckland +64 (0) 9 929 1825 New Zealand, Christchurch +64 (0) 3 974 2596 New Zealand, Wellington +64 (0) 4 909 4674 Nigeria, Lagos +234 1 277 3944 Norway (toll free) 800 56081 Norway, Oslo +47 21 00 48 15 Panama (toll free) 00800 223 1390 Panama, Panama City +507 8 335 913 Peru, Lima +51 (0) 1 700 9571 Philippines (toll free) 1 800 111 013 99 Philippines, Manila +63 (0)2 395 3426 Poland (toll free) 00 800 121 4356 Poland, Warsaw +48 22 295 3570 Portugal (toll free) 800 784 442 Portugal, Lisbon +351 21 316 4093 Qatar (toll free) 00 800 100 491 Romania (toll free) 0800 801 035 Romania, Bucharest +40 (0) 21 529 3992 Russia (toll free) 8 800 500 9241 Russia, Moscow +7 495 646 9181 Saudi Arabia (toll free) 800 844 6641 Saudi Arabia (toll free) 800 850 0219 Serbia (toll free) 0800 190 712 Singapore +65 6622 1957 Singapore (toll free) 800 616 3192 Slovakia (toll free) 0800 002 002 Slovakia, Bratislava +421 (0)2 3321 5498 Slovenia (toll free) 0800 81193 Slovenia, Ljubljana +386 1600 8695 South Africa (toll free) 0800 999 434 South Africa, Johannesburg +27 (0)11 589 8321 South Korea (toll free) 00798 6136 1454 South Korea, Seoul +82 (0) 2 6007 0079 Spain (toll free) 900 828 035 Spain, Barcelona +34 93 800 1946 Spain, Madrid +34 91 114 6653 Sweden (toll free) 0200 125 588 Sweden, Stockholm +46 (0) 8 5065 3956 Switzerland (toll free) 0800 740 360 Switzerland, Geneva +41 (0) 22 595 4795 Switzerland, Zurich +41 (0) 44 580 7207 Taiwan (toll free) 0800 666 596 Taiwan, Taipei +886 (0) 2 2650 7329 Thailand (toll free) 001 800 6136 1473 Turkey (toll free) 00800 4488 26642 Turkey, Istanbul +90 212 375 50 49 UAE (toll free) 8000 3570 2662 UK (03) +44 (0)330 336 6002 UK (national) 0844 581 8062 UK (national) 0845 351 2782 UK (toll free) 0800 358 6385 Ukraine (toll free) 0800 500 896 Uruguay (toll free) 0004 019 0152 USA /Canada (toll free) 1-866-398-2885 Venezuela (toll free) 0 800 162 7451 Venezuela, Caracas +58 212 720 2164 Vietnam (toll free) 1800 9226 Questions? Go to GlobalMeet Support <http://community.globalmeet.com/> Sent on behalf of: Milena TIMUR EMEA Senior Administrative Assistant, GSE ICANN-Internet Corporation for Assigned Names and Numbers Istanbul Hub Office Hakki Yeten Cad. Selenium Plaza No: 10/C K: 10 34349 Fulya, Istanbul, Turkey Direct line : <tel:%2B90%20212%20999%2062%2028> +90 212 999 62 41 Mobile: +90 531 306 51 43 Tel.: <tel:%2B90%20212%20999%2062%2028> +90 212 999 62 22 Email: <mailto:milena.timur@icann.org> milena.timur(a)icann.org Skype: milena.timur.icann Jabber: <mailto:milena.timur@jabber.icann.org> milena.timur(a)jabber.icann.org

7 12

Re: [At-Large] [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation
by Adam Peake Dec. 14, 2015

Dec. 14, 2015

Hi Roberto, My apologies, I made a mistake when I replied to a comment on the draft civil society engagement document. Mistakenly, I thought there were some ALS that represented commercial concerns. I was wrong. Best, Adam Begin forwarded message: From: Roberto Gaetano <roberto_gaetano(a)hotmail.com<mailto:roberto_gaetano@hotmail.com>> Subject: [At-Large] R: R: I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation Date: December 14, 2015 at 08:56:36 GMT+9 To: "'Glenn McKnight'" <mcknight.glenn(a)gmail.com<mailto:mcknight.glenn@gmail.com>> Cc: "'At-Large Worldwide'" <at-large(a)atlarge-lists.icann.org<mailto:at-large@atlarge-lists.icann.org>> Thanks for the document, Glenn. I understand that it is a complicated issue, but my point was just that I consider incorrect the allegation by ICANN Staff that we have in ALAC ALSes that are expression of commercial interests. This is contrary to the criteria for certification, and therefore, if such cases exist (which I honestly doubt), corrective action should be taken. As simple as that. And it is orthogonal to the Civil Society definition issue. However, since you raise the problem, I will add that if the question arises for defining who is “Civil Society” and who is not – that should be the “Uncivil Society” :) - not just for At-Large Structures, but also for all other components of this new group. Besides, the title reads: “ICANN Civil Society and Non-Commercial engagement in FY16 [Civil Society, Non-Commercial, Academic and End-User Engagement in FY16]”. Honestly, I do not understand this suspicion about At-Large Structures, for which, incidentally, there is a fully auditable and publicly known certification process – which is not really the case in a lot of other components of the ICANN multi-stakeholder community. Long story short, it strikes me, as a reader of the document, that what I consider by and large the non-commercial user community is divided in two parts, one (the NCSG) that is considered orthodox ex-officio, the other one (ALAC) that is accepted in bits and pieces, and only after an autodafé. Cheers, R. Da: Glenn McKnight [mailto:mcknight.glenn@gmail.com] Inviato: domenica 13 dicembre 2015 23:07 A: Roberto Gaetano Cc: Seun Ojedeji; At-Large Worldwide Oggetto: Re: [At-Large] R: I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation Hi All The problem with the document starts without a common definition of What is Civil Society. I have added a document that addresses that issue. I fear that if we lack a proper definition we will see ATLARGE being outside the parameters of this measure Attached Glenn Glenn McKnight mcknight.glenn(a)gmail.com<mailto:mcknight.glenn@gmail.com> skype gmcknight twitter gmcknight . On Sun, Dec 13, 2015 at 4:57 PM, Roberto Gaetano <roberto_gaetano(a)hotmail.com<mailto:roberto_gaetano@hotmail.com>> wrote: Seun, In EURALO we have occasionally de-certified ALSes that were no longer compliant. I would assume that this would be the case in all RALOs. There is an issue of credibility of ALAC at stake. R. Da: Seun Ojedeji [mailto:seun.ojedeji@gmail.com<mailto:seun.ojedeji@gmail.com>] Inviato: domenica 13 dicembre 2015 22:43 A: Roberto Gaetano Cc: At-Large Worldwide Oggetto: Re: [At-Large] I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation On Dec 13, 2015 22:14, "Roberto Gaetano" <roberto_gaetano(a)hotmail.com<mailto:roberto_gaetano@hotmail.com>> wrote: > > . Therefore, the ALS, when certified, is guaranteed not to be promoting for-profit or government agendas. > > Can we have this straightened up once and for good? > SO: +1 the wording of staff sure needs to be corrected. I would have thought they are referring to the processes ALS members participate in. For instance some ALS members participate in regional technical meetings et all. Even if that is the intent, a rewording is still required. > Alternatively, may I know which are the At-Large Structures that allegedly “represent business interests”? > SO: Actually this should be looked into at At-Large level (aside this particular subject), there may be need for occasional audit to determine if certified ALS status has indeed changed to being for-profit as I expect that due diligence is usually done during initial application to ensure such is not the case. Regards > Cheers, > > Roberto > > > > > > Da: alac-announce-bounces(a)atlarge-lists.icann.org<mailto:alac-announce-bounces@atlarge-lists.icann.org> [mailto:alac-announce-bounces@atlarge-lists.icann.org<mailto:alac-announce-bounces@atlarge-lists.icann.org>] Per conto di ICANN At-Large Staff > Inviato: venerdì 11 dicembre 2015 15:12 > A: ALAC Announce > Oggetto: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation > > > > On behalf of Jean-Jacques Sahel and Adam Peake > > > > Dear All, > > > > Please find below participation details for Civil Society Engagement Approach: Call to discuss Implementation on Wednesday 16 Dec 2015 at 14:00 UTC > > > > This call is for ICANN Staff and the community to start planning together joint activities and other deliverables such as new content production for the coming months, under the new civil society engagement approach. > > > > A draft agenda will be circulated for comments shortly. > > > > Please remember that you can comment on the draft Civil Society engagement strategy by end of Friday 11 December here: > > https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB… > > > > The revised document will be circulated ahead of the call on December 16. > > > > This call will be in English only. > > > > Thank you. > > Regards, > > Jean-Jacques Sahel & Adam Peake > > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Link to Adobe Connect: https://icann.adobeconnect.com/gseemea/ > > *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). > > If you wish only audio, click on the ‘Connect Me’ icon or dial in using one of the numbers hereunder: > > > > __________________________________________ > > You're Invited. > > You've been invited to a GlobalMeet® phone only meeting. > > Have the meeting call you. > Click the Connect Me link below. No need to dial-in. > > Connect Me > > Not at your computer? > You can join by dialing one of the access numbers below. > > Mobile: > > tel://1-719-457-6209,*,,3938083611#<tel://1-719-457-6209,*,,3938083611> > > Phone Only Controls: > > https://go.conferencinghub.com/20sll > > Primary Access Number: > > 1-719-457-6209<tel:1-719-457-6209> > > Guest Passcode: > > 393 808 3611 > > Additional Access: > > USA > > 1-719-457-6209<tel:1-719-457-6209> > > Canada, Calgary > > +1 403 407 5793<tel:%2B1%20403%20407%205793> > > Canada, Montreal > > +1 514 669 5928<tel:%2B1%20514%20669%205928> > > Canada, Toronto > > +1 647 426 9172<tel:%2B1%20647%20426%209172> > > Canada, Vancouver > > +1 604 222 7836<tel:%2B1%20604%20222%207836> > > Argentina (toll free) > > 0800 800 1223 > > Argentina, Buenos Aires > > +54 (0) 11 5172 6003<tel:%2B54%20%280%29%2011%205172%206003> > > Australia (toll free) > > 1 800 804 786 > > Australia, Brisbane > > +61 (0) 7 3015 0535<tel:%2B61%20%280%29%207%203015%200535> > > Australia, Melbourne > > +61 (0) 3 8687 0553<tel:%2B61%20%280%29%203%208687%200553> > > Australia, Sydney > > +61 (0) 2 8017 6064<tel:%2B61%20%280%29%202%208017%206064> > > Austria (toll free) > > 0800 8866 3413 > > Austria, Vienna > > +43 (0) 1 25302 1785<tel:%2B43%20%280%29%201%2025302%201785> > > Bahrain (toll free) > > 800 04212 > > Bahrain, Manama > > +973 1619 8739<tel:%2B973%201619%208739> > > Belarus (toll free) > > 8 820 0011 0341 > > Belgium (toll free) > > 0800 39279 > > Belgium, Brussels > > +32 (0) 2 400 6928<tel:%2B32%20%280%29%202%20400%206928> > > Brazil (toll free) > > 0800 887 0233 > > Brazil, Rio de Janeiro > > +55 21 4560 0072<tel:%2B55%2021%204560%200072> > > Brazil, Sao Paulo > > +55 11 4935 7169<tel:%2B55%2011%204935%207169> > > Bulgaria (toll free) > > 00800 111 4950 > > Bulgaria, Sofia > > +359 (0) 2 491 6045<tel:%2B359%20%280%29%202%20491%206045> > > Canada (toll free) > > 1 855 950 3717<tel:1%20855%20950%203717> > > Chile (toll free) > > 171 800 835 783 > > Chile, Santiago > > +56 (0) 2 2666 0696<tel:%2B56%20%280%29%202%202666%200696> > > China (national) > > +400 613 8103 > > China, Beijing > > +86 10 5667 0003<tel:%2B86%2010%205667%200003> > > China, Shanghai > > +86 21 2039 7081<tel:%2B86%2021%202039%207081> > > Colombia (toll free) > > 01 800 755 0102 > > Colombia, Bogota > > +57 1 508 8137 > > Costa Rica (toll free) > > 800 542 5328<tel:800%20542%205328> > > Croatia (toll free) > > 0800 805 940 > > Cyprus (toll free) > > 800 97424 > > Czech Republic (toll free) > > 800 701 532 > > Czech Republic, Prague > > +420 225 986 554<tel:%2B420%20225%20986%20554> > > Denmark (toll free) > > 80 70 35 86 > > Denmark, Copenhagen > > +45 32 72 78 10<tel:%2B45%2032%2072%2078%2010> > > Egypt (toll free) > > 0800 000 0593 > > Estonia (toll free) > > 800 011 1589 > > Estonia, Tallinn > > +372 622 6551<tel:%2B372%20622%206551> > > Fiji (toll free) > > 00800 3322 > > Finland (toll free) > > 0800 772 236 > > Finland, Helsinki > > +358 (0) 9 2310 1677 > > France (national) > > 0811 655 100 > > France (toll free) > > 0800 946 531 > > France, Paris > > +33 (0) 1 70 37 16 56<tel:%2B33%20%280%29%201%2070%2037%2016%2056> > > Germany (national) > > 01801 003 899 > > Germany (toll free) > > 0800 588 9170 > > Germany, Frankfurt > > +49 (0) 69 2222 10612<tel:%2B49%20%280%29%2069%202222%2010612> > > Germany, Munich > > +49 (0) 89 2030 31207<tel:%2B49%20%280%29%2089%202030%2031207> > > Greece (toll free) > > 00800 128 913 > > Greece, Athens > > +30 211 181 3824<tel:%2B30%20211%20181%203824> > > Hong Kong > > +852 3018 9111<tel:%2B852%203018%209111> > > Hong Kong (toll free) > > 800 901 787 > > Hungary (toll free) > > 068 001 9673 > > Hungary, Budapest > > +36 1408 8953 > > Iceland (toll free) > > 800 9847 > > India (toll free) > > 000 800 1008 367 > > India, Bangalore > > +91 (0) 80 6127 6710<tel:%2B91%20%280%29%2080%206127%206710> > > India, Chennai > > +91 (0)44 6688 6061<tel:%2B91%20%280%2944%206688%206061> > > India, Delhi > > +91 (0) 11 6641 1394<tel:%2B91%20%280%29%2011%206641%201394> > > India, Mumbai > > +91 (0)22 6187 5028<tel:%2B91%20%280%2922%206187%205028> > > Indonesia (toll free) > > 007 803 321 8927 > > Ireland (national) > > 1890 907 630 > > Ireland (toll free) > > 1800 937 649 > > Ireland, Dublin > > +353 (0) 1 526 9421<tel:%2B353%20%280%29%201%20526%209421> > > Israel (toll free) > > 1809 213 168 > > Israel, Tel Aviv > > +972 (0)3 721 7943<tel:%2B972%20%280%293%20721%207943> > > Italy (toll free) > > 800 146 094 > > Italy, Milan > > +39 02 3600 8006<tel:%2B39%2002%203600%208006> > > Italy, Rome > > +39 06 8750 0676<tel:%2B39%2006%208750%200676> > > Japan (mobile) > > 0120 632 611 > > Japan (toll free) > > 0120 305 211 > > Japan, Chiba > > +81 (0) 43 321 6881<tel:%2B81%20%280%29%2043%20321%206881> > > Japan, Fukuoka > > +81 (0) 92 290 6881<tel:%2B81%20%280%29%2092%20290%206881> > > Japan, Hiroshima > > +81 (0) 82 558 6881<tel:%2B81%20%280%29%2082%20558%206881> > > Japan, Nagoya > > +81 (0) 52 850 6881<tel:%2B81%20%280%29%2052%20850%206881> > > Japan, Osaka > > +81 (0) 6 4560 2410<tel:%2B81%20%280%29%206%204560%202410> > > Japan, Sapporo > > +81 (0) 11 234 6881<tel:%2B81%20%280%29%2011%20234%206881> > > Japan, Sendai > > +81 (0) 22 708 6881<tel:%2B81%20%280%29%2022%20708%206881> > > Japan, Shizuoka > > +81 (0) 54 902 6881<tel:%2B81%20%280%29%2054%20902%206881> > > Japan, Tachikawa > > +81 (0) 42 841 6881<tel:%2B81%20%280%29%2042%20841%206881> > > Japan, Tokyo > > +81 (0) 3 4560 1270<tel:%2B81%20%280%29%203%204560%201270> > > Japan, Toyama > > +81 (0) 76 408 6881<tel:%2B81%20%280%29%2076%20408%206881> > > Japan, Urawa > > +81 (0) 48 698 6881<tel:%2B81%20%280%29%2048%20698%206881> > > Japan, Yokohama > > +81 (0) 45 677 6881<tel:%2B81%20%280%29%2045%20677%206881> > > Kazakhstan (toll free) > > 8800 333 7554 > > Latvia (toll free) > > 8000 4418 > > Latvia, Riga > > +371 6601 3627 > > Lithuania (toll free) > > 8800 31449 > > Lithuania, Vilnius > > +370 5205 5468 > > Luxembourg > > +352 2088 1749<tel:%2B352%202088%201749> > > Luxembourg (toll free) > > 800 28433 > > Malaysia (toll free) > > 1 800 816 152 > > Malaysia,Kuala Lumpur > > +60 (0) 3 7724 8010<tel:%2B60%20%280%29%203%207724%208010> > > Mexico (toll free) > > 01 800 733 4102 > > Mexico, Guadalajara > > +52 33 4162 4504<tel:%2B52%2033%204162%204504> > > Mexico, Mexico City > > +52 55 8421 0326<tel:%2B52%2055%208421%200326> > > Mexico, Monterrey > > +52 81 4162 5648<tel:%2B52%2081%204162%205648> > > Morocco (toll free) > > 0800 091 296 > > Morocco, Casablanca > > +212 (0) 520 48 0022 > > Netherlands (toll free) > > 0800 020 2597 > > Netherlands, Amsterdam > > +31 (0) 20 716 8345<tel:%2B31%20%280%29%2020%20716%208345> > > New Zealand (toll free) > > 0800 452 947 > > New Zealand, Auckland > > +64 (0) 9 929 1825<tel:%2B64%20%280%29%209%20929%201825> > > New Zealand, Christchurch > > +64 (0) 3 974 2596<tel:%2B64%20%280%29%203%20974%202596> > > New Zealand, Wellington > > +64 (0) 4 909 4674<tel:%2B64%20%280%29%204%20909%204674> > > Nigeria, Lagos > > +234 1 277 3944<tel:%2B234%201%20277%203944> > > Norway (toll free) > > 800 56081 > > Norway, Oslo > > +47 21 00 48 15<tel:%2B47%2021%2000%2048%2015> > > Panama (toll free) > > 00800 223 1390 > > Panama, Panama City > > +507 8 335 913 > > Peru, Lima > > +51 (0) 1 700 9571 > > Philippines (toll free) > > 1 800 111 013 99 > > Philippines, Manila > > +63 (0)2 395 3426<tel:%2B63%20%280%292%20395%203426> > > Poland (toll free) > > 00 800 121 4356 > > Poland, Warsaw > > +48 22 295 3570<tel:%2B48%2022%20295%203570> > > Portugal (toll free) > > 800 784 442 > > Portugal, Lisbon > > +351 21 316 4093<tel:%2B351%2021%20316%204093> > > Qatar (toll free) > > 00 800 100 491 > > Romania (toll free) > > 0800 801 035 > > Romania, Bucharest > > +40 (0) 21 529 3992<tel:%2B40%20%280%29%2021%20529%203992> > > Russia (toll free) > > 8 800 500 9241 > > Russia, Moscow > > +7 495 646 9181<tel:%2B7%20495%20646%209181> > > Saudi Arabia (toll free) > > 800 844 6641<tel:800%20844%206641> > > Saudi Arabia (toll free) > > 800 850 0219<tel:800%20850%200219> > > Serbia (toll free) > > 0800 190 712 > > Singapore > > +65 6622 1957<tel:%2B65%206622%201957> > > Singapore (toll free) > > 800 616 3192<tel:800%20616%203192> > > Slovakia (toll free) > > 0800 002 002 > > Slovakia, Bratislava > > +421 (0)2 3321 5498 > > Slovenia (toll free) > > 0800 81193 > > Slovenia, Ljubljana > > +386 1600 8695 > > South Africa (toll free) > > 0800 999 434 > > South Africa, Johannesburg > > +27 (0)11 589 8321<tel:%2B27%20%280%2911%20589%208321> > > South Korea (toll free) > > 00798 6136 1454 > > South Korea, Seoul > > +82 (0) 2 6007 0079<tel:%2B82%20%280%29%202%206007%200079> > > Spain (toll free) > > 900 828 035 > > Spain, Barcelona > > +34 93 800 1946<tel:%2B34%2093%20800%201946> > > Spain, Madrid > > +34 91 114 6653<tel:%2B34%2091%20114%206653> > > Sweden (toll free) > > 0200 125 588 > > Sweden, Stockholm > > +46 (0) 8 5065 3956 > > Switzerland (toll free) > > 0800 740 360 > > Switzerland, Geneva > > +41 (0) 22 595 4795<tel:%2B41%20%280%29%2022%20595%204795> > > Switzerland, Zurich > > +41 (0) 44 580 7207<tel:%2B41%20%280%29%2044%20580%207207> > > Taiwan (toll free) > > 0800 666 596 > > Taiwan, Taipei > > +886 (0) 2 2650 7329<tel:%2B886%20%280%29%202%202650%207329> > > Thailand (toll free) > > 001 800 6136 1473 > > Turkey (toll free) > > 00800 4488 26642 > > Turkey, Istanbul > > +90 212 375 50 49<tel:%2B90%20212%20375%2050%2049> > > UAE (toll free) > > 8000 3570 2662 > > UK (03) > > +44 (0)330 336 6002<tel:%2B44%20%280%29330%20336%206002> > > UK (national) > > 0844 581 8062 > > UK (national) > > 0845 351 2782 > > _______________________________________________ At-Large mailing list At-Large(a)atlarge-lists.icann.org<mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org<http://atlarge.icann.org/> _______________________________________________ At-Large mailing list At-Large(a)atlarge-lists.icann.org<mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org<http://atlarge.icann.org/>

1 0

Fwd: negotiation and consensus-finding styles
by Olivier MJ Crepin-Leblond Dec. 14, 2015

Dec. 14, 2015

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello all, Jari has pointed to some interesting method of finding consensus. I forward them here just for interest, not for any action. Kindest regards, Olivier - -------- Forwarded Message -------- Subject: negotiation and consensus-finding styles Date: Mon, 14 Dec 2015 15:04:10 +0200 From: Jari Arkko <jari.arkko(a)piuha.net> To: IETF <ietf(a)ietf.org> This caught my eye (and some other people’s eye too, got some people asking about it): "This simple negotiation tactic brought 195 countries to consensus" http://tinyurl.com/qb4oyq9 It is about the climate change negotiations. Government negotiations are not my thing in general :-) but this article points to a specific negotiation style, Indaba: https://en.wikipedia.org/wiki/Indaba "Instead of repeating stated positions, each party is encouraged to speak personally and state their “red lines,” which are thresholds that they don’t want to cross. But while telling others their hard limits, they are also asked to provide solutions to find a common ground.” I’ve never heard of this particular technique before, have other people run into it? Any experiences? Any more detailed information? The reason that I’m asking is that it kind of sounds like the way people should be voicing their opinions in an IETF discussion, when that discussion is run in an optimal way. Along with our rough consensus concepts, of course, and drive to understand other people's positions. Just wondering if this is essential what our rough consensus process already is, or if there are further details that we could consider learning from as well. (And: as always, any process can by misused if the participants do not care enough about the common good. I’m sure this never happens in government negotiations :-) but in the rest of the world… one example that I’ve seen in the IETF is overstating hard requirements, e.g., making particular solutions part of the requirements. Next time you discuss something in the IETF, please take a moment to reflect what your true needs are and what are just solution space options. Take also a moment to understand what the other people are saying, and try to build that into what you are suggesting, finding ways for other people’s needs to be also met.) Jari -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWbsBWAAoJEA22tlbHMiYdqw8P/Rox4Gnik+usuQs/glYGuQwW 0ubaTEODz0CjGcchtxMC0yxD4azKB7oMSGhdhWka1YxHICzMcHF1mZG6Q3s3tKaf c8t+BTJpRUEUyAi4NH8+p/aL2LVvohP10YmILNONi3MbJufxQjbtBTGN09yFdl8U ZGzHys5SHM80ptYsxpf/QHBHKsFmKU/NPLF4c7+bhV+S8rEgVSHSl7geCr3IvALm bX4RfefCuFJkzCRPATOVuNVGp2sMV5ZE25BhJaKo2WtDCfKmLmYtd5OaE5OkAe3q YxEDv/JyEZUVdvHiv1KuCjY05utivmrYmsU/+q4SRiKLdfyrve/4fKnTIAPupFiQ f6E3az+XTFr5+7JkPV1j43WCeHijgnM1kraLZKPjPB4HkG4dGyR0anotibXGqy8t TuJHsIqF01Mur8DeaClxUQ5HhlPXvM49233oftZo6sgHJRijc7+pY9q9tMgtMY8d gvIeewwBllPiCUTXpkVA84VVgLqAlNpzQ+zRqrIZKdEkaEFix76GDKR2f9ggOBu0 KGUQHRGJxU0uY+b7IL4EctCAZBOCtyvEs48+TnjySrlOvmNk6yeciBYRDGdG5esT WRCE48+Z5XYq71UWADzYHZDbvGrFUETNDf/iiupY+vVdP0ryFhyER2E/LhkCym4z lJJV640jtqtxuJuOTAFE =VA53 -----END PGP SIGNATURE-----

1 0

Re: [At-Large] R: I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation
by carlos dionisio aguirre Dec. 14, 2015

Dec. 14, 2015

@Olivier clap clap clap. I personally fully agree with your comments. In my case I support the initiative but I agree there are many question made and not made unanswered.I also can see conflictives points between CSI & At Large community. My first negative point was: Why not a translation for the webinar wich try to be for all Civil Society members around the globe? At this moment and having many translations tools is almost discriminatory for who dont speak english. I like the initiative but I think it need time to solve this points in conflict with at large community or at least clarify the proposal, but no in a webinar managed only in english languaje. My two cents from far in the south. Carlos Dionisio AguirrePart of At Large Community and representative of Academia and Civil Society Enviado desde mi smartphone Samsung Galaxy.<div> </div><div> </div><div>-------- Mensaje original --------</div><div>De: Olivier MJ Crepin-Leblond <ocl(a)gih.com> </div><div>Fecha: 14/12/2015 7:49 (GMT-03:00) </div><div>Para: Glenn McKnight <mcknight.glenn(a)gmail.com>, Roberto Gaetano <roberto_gaetano(a)hotmail.com> </div><div>Cc: At-Large Worldwide <at-large(a)atlarge-lists.icann.org> </div><div>Asunto: Re: [At-Large] R: I: [ALAC-Announce] Meeting Invitation - Civil Society Engagement Approach: Call to discuss Implementation </div><div> </div> Hello all, as you know, I am a supporter of the Civil Society initiative. But reading the discussion here, I feel that there are indeed a lot of unanswered questions and I sense a real concern (even worry!) from many in At-Large that the initiative has the potential to weaken the At-Large community by dividing it, especially when it comes to policy issues. We all know that, as a group that incorporates non commercial, commercial, technical and academic communities, we often have different points of view than purely civil society organisations. Indeed, our priorities are sometimes different. I sense that in order to address all of the concerns that we have, our community needs a call with the leaders of this program, Adam Peake and Jean-Jacques Sahel. The currently proposed call on Wed 16 December is unsuitable for this concern as these are purely questions related to At-Large and interpretation will not be provided. (why?) My questions on any such conference call would be based on the imbalance caused within our community if the Civil Society Initiative went ahead without similar initiatives for our commercial, technical & academic At-Large Structures. 1. Are there going to be similar initiatives for Commercial, Technical & Academic communities? (reminder: I was told "yes" a few months ago - I'd like to know where we are on these) 2. Are At-Large Structures that are not classed as Civil Society going to be discriminated against? (in CROPP funding, in IGF workshops, etc.) 3. Is the ALAC itself going to be discriminated against as it is not 100% Civil Society? 4. Are any parts of the proposal aiming to have "Civil Society" come to consensus on policy related matters, irrespective of the current NCSG or At-Large boundaries? Kindest regards, Olivier On 13/12/2015 23:06, Glenn McKnight wrote: > Hi All > The problem with the document starts without a common definition of > What is Civil Society. I have added a document that addresses that > issue. I fear that if we lack a proper definition we will see > ATLARGE being outside the parameters of this measure > Attached > Glenn > > Glenn McKnight > mcknight.glenn(a)gmail.com <mailto:mcknight.glenn@gmail.com> > skype gmcknight > twitter gmcknight > . > > On Sun, Dec 13, 2015 at 4:57 PM, Roberto Gaetano > <roberto_gaetano(a)hotmail.com <mailto:roberto_gaetano@hotmail.com>> wrote: > > Seun, > > In EURALO we have occasionally de-certified ALSes that were no > longer compliant. > > I would assume that this would be the case in all RALOs. > > There is an issue of credibility of ALAC at stake. > > R. > > > > > > *Da:*Seun Ojedeji [mailto:seun.ojedeji@gmail.com > <mailto:seun.ojedeji@gmail.com>] > *Inviato:* domenica 13 dicembre 2015 22:43 > *A:* Roberto Gaetano > *Cc:* At-Large Worldwide > *Oggetto:* Re: [At-Large] I: [ALAC-Announce] Meeting Invitation - > Civil Society Engagement Approach: Call to discuss Implementation > > > > On Dec 13, 2015 22:14, "Roberto Gaetano" > <roberto_gaetano(a)hotmail.com <mailto:roberto_gaetano@hotmail.com>> > wrote: > > > > . Therefore, the ALS, when certified, is guaranteed not to be > promoting for-profit or government agendas. > > > > Can we have this straightened up once and for good? > > > SO: +1 the wording of staff sure needs to be corrected. I would > have thought they are referring to the processes ALS members > participate in. For instance some ALS members participate in > regional technical meetings et all. Even if that is the intent, a > rewording is still required. > > > Alternatively, may I know which are the At-Large Structures that > allegedly “represent business interests”? > > > SO: Actually this should be looked into at At-Large level (aside > this particular subject), there may be need for occasional audit > to determine if certified ALS status has indeed changed to being > for-profit as I expect that due diligence is usually done during > initial application to ensure such is not the case. > > Regards > > > Cheers, > > > > Roberto > > > > > > > > > > > > Da: alac-announce-bounces(a)atlarge-lists.icann.org > <mailto:alac-announce-bounces@atlarge-lists.icann.org> > [mailto:alac-announce-bounces@atlarge-lists.icann.org > <mailto:alac-announce-bounces@atlarge-lists.icann.org>] Per conto > di ICANN At-Large Staff > > Inviato: venerdì 11 dicembre 2015 15:12 > > A: ALAC Announce > > Oggetto: [ALAC-Announce] Meeting Invitation - Civil Society > Engagement Approach: Call to discuss Implementation > > > > > > > > On behalf of Jean-Jacques Sahel and Adam Peake > > > > > > > > Dear All, > > > > > > > > Please find below participation details for Civil Society > Engagement Approach: Call to discuss Implementation on Wednesday > 16 Dec 2015 at 14:00 UTC > > > > > > > > This call is for ICANN Staff and the community to start planning > together joint activities and other deliverables such as new > content production for the coming months, under the new civil > society engagement approach. > > > > > > > > A draft agenda will be circulated for comments shortly. > > > > > > > > Please remember that you can comment on the draft Civil Society > engagement strategy by end of Friday 11 December here: > > > > > https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB… > > > > > > > > The revised document will be circulated ahead of the call on > December 16. > > > > > > > > This call will be in English only. > > > > > > > > Thank you. > > > > Regards, > > > > Jean-Jacques Sahel & Adam Peake > > > > > _______________________________________________ At-Large mailing list At-Large(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org

1 0

Re: [At-Large] I: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary Determination To Grant Registrar Data Retention Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA
by Holly Raiche Dec. 13, 2015

Dec. 13, 2015

And Seth If you read the ALAC statement/response to the Whois Conflicts WG, you will see that we said just that - as did Christopher wilkinson and Stephanie Perrin. It all goes way back to the original Whois protocol, - that served a very different purpose, but was adopted by ICANN - and should not have been. It is why the ICANN board set up the EWG, (and why ALAC wrote to the Chair about the RDAP) Holly On 14 Dec 2015, at 8:12 am, Seth M Reiss <seth.reiss(a)lex-ip.com> wrote: > No, you have lots of company. > > -----Original Message----- > From: at-large-bounces(a)atlarge-lists.icann.org > [mailto:at-large-bounces@atlarge-lists.icann.org] On Behalf Of Roberto > Gaetano > Sent: Sunday, December 13, 2015 10:52 AM > To: at-large(a)atlarge-lists.icann.org > Subject: [At-Large] I: [ALAC-Announce] ICANN News Alert -- Notice of > Preliminary Determination To Grant Registrar Data Retention Waiver Request > for Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. > USA > > I am just wondering how much this overhead does cost. > Instead of complying with European law, ICANN has chosen to disregard it, > and now is obliged to grant waivers one by one to European registrars. > Am I the only one who thinks that this is plain silly? > Cheers, > R. > > > >> -----Messaggio originale----- >> Da: alac-announce-bounces(a)atlarge-lists.icann.org >> [mailto:alac-announce- bounces(a)atlarge-lists.icann.org] Per conto di >> ICANN At-Large Staff >> Inviato: giovedì 10 dicembre 2015 04:03 >> A: alac-announce(a)atlarge-lists.icann.org >> Oggetto: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary >> Determination To Grant Registrar Data Retention Waiver Request for >> Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. >> USA >> >> >> [ICANN]<http://www.icann.org/> >> News Alert >> >> https://www.icann.org/news/announcement-2015-12-09-en >> >> ________________________________ >> Notice of Preliminary Determination To Grant Registrar Data Retention >> Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio >> Technologies, Inc. USA >> >> 9 December 2015 >> >> ICANN has made a preliminary determination that it is prepared to >> grant a data retention waiver request submitted by Registrar Ascio >> Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA >> ("Ascio") under the > 2013 >> Registrar Accreditation Agreement (the "2013 RAA"). Section 2 of the >> Data Retention Specification (the "Specification") of the 2013 RAA >> provides > that >> prior to granting any exemption under the Specification, ICANN will >> post > its >> determination on the ICANN website for a period of thirty (30) >> calendar > days. >> >> Pursuant to Section 2 of the Specification, Ascio has submitted to >> ICANN a Registrar data retention waiver request ("Waiver Request") on >> the basis of Ascio's contention that compliance with the data >> collection and/or > retention >> requirements of the Specification violates applicable law in Denmark. >> >> The Waiver Request was accompanied by a written legal opinion from a >> nationally recognized law firm citing section 5 (5) of the Danish Act >> on Processing of Personal Data of 31 May 2000 (the "DPPD"). That >> section provides as follows (the following is an unofficial English >> translation > from >> Danish): >> >> Section 5 (5). >> >> The data collected may not be kept in a form which makes it possible >> to identify the data subject for a longer period than is necessary for >> the purposes for which the data are processed. >> >> Following receipt of the Waiver Request, and in accordance with the >> 2013 RAA, ICANN through its legal counsel and Ascio discussed the >> matter in > good >> faith in an effort to reach a mutually acceptable resolution of the > matter. >> >> The outcome of those discussions is that Ascio is seeking a waiver >> with respect to Sections 1.1.1 through 1.1.8 of the Specification that >> seeks to reduce from two years to one year the period for which these >> specified > data >> elements must be retained after the Registrar's sponsorship of the >> Registration ends. >> >> ICANN has determined on a preliminary basis that it is prepared to >> grant > the >> Waiver Request. ICANN is posting this preliminary determination for a > period >> of thirty (30) calendar days to seek feedback and input from the >> community on the proposed data retention waiver. After the thirty (30) >> calendar day period following this posting has expired, ICANN will >> consider all > feedback >> and input received before making a final determination on whether to >> grant the Waiver Request. >> >> The scope of the proposed waiver would be to permit Ascio to maintain >> the information specified in Sections 1.1.1 through 1.1.8 of the >> Specification > for >> the duration of its sponsorship of the Registration and for a period >> of > one (1) >> additional year thereafter rather than two (2) additional years > thereafter. In >> all other respects the terms of the Specification would remain AS-IS. >> >> The specific change to the Specification would be that, for the >> duration > of the >> Waiver, the retention requirement of Section 1.1 of the Data Retention >> Specification be changed from "two additional years" to "one >> additional year." >> >> If ICANN does make a final determination to grant the Waiver Request >> sought by Ascio, the provisions of Section 3 of the Specification >> would > apply >> to similar waivers requested by other registrars located in Denmark >> and subject to Danish law. Section 3 of the Specification provides as > follows: >> >> If (i) ICANN has previously waived compliance with the requirements of >> any requirement of this Data Retention Specification in response to a >> Waiver Request from a registrar that is located in the same >> jurisdiction as > Registrar >> and (ii) Registrar is subject to the same applicable law that gave >> rise to ICANN's agreement to grant such waiver, Registrar may request >> that ICANN to grant a similar waiver, which request shall be approved >> by ICANN, > unless >> ICANN provides Registrar with a reasonable justification for not >> approving such request, in which case Registrar may thereafter make an >> Wavier Request pursuant to Section 2 of this Data Retention Specification. >> >> The Registrar's Waiver Request and supporting documents are available >> here: >> https://www.icann.org/en/system/files/files/waiver-request-ascio- >> technologies-09dec15-en.pdf [PDF, 6.39 MB] >> >> A public comment period will remain open until 23:59 UTC, 11 January 2016. >> Public comments will be available for consideration by ICANN staff and >> the ICANN Board. >> >> * Comments can be posted to: comments-ascio-technologies- >> 09dec15(a)icann.org<mailto:comments-ascio-technologies- >> 09dec15(a)icann.org> >> * Comments can be viewed at: http://forum.icann.org/lists/comments- >> ascio-technologies-09dec15/ > > > _______________________________________________ > At-Large mailing list > At-Large(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/at-large > > At-Large Official Site: http://atlarge.icann.org

1 0

Re: [At-Large] I: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary Determination To Grant Registrar Data Retention Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA
by Christian de Larrinaga Dec. 13, 2015

Dec. 13, 2015

This is priceless "ICANN has determined on a preliminary basis that it is prepared to grant the Waiver Request." oh really! Christian Seth M Reiss wrote: > No, you have lots of company. > > -----Original Message----- > From: at-large-bounces(a)atlarge-lists.icann.org > [mailto:at-large-bounces@atlarge-lists.icann.org] On Behalf Of Roberto > Gaetano > Sent: Sunday, December 13, 2015 10:52 AM > To: at-large(a)atlarge-lists.icann.org > Subject: [At-Large] I: [ALAC-Announce] ICANN News Alert -- Notice of > Preliminary Determination To Grant Registrar Data Retention Waiver Request > for Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. > USA > > I am just wondering how much this overhead does cost. > Instead of complying with European law, ICANN has chosen to disregard it, > and now is obliged to grant waivers one by one to European registrars. > Am I the only one who thinks that this is plain silly? > Cheers, > R. > > > >> -----Messaggio originale----- >> Da: alac-announce-bounces(a)atlarge-lists.icann.org >> [mailto:alac-announce- bounces(a)atlarge-lists.icann.org] Per conto di >> ICANN At-Large Staff >> Inviato: giovedì 10 dicembre 2015 04:03 >> A: alac-announce(a)atlarge-lists.icann.org >> Oggetto: [ALAC-Announce] ICANN News Alert -- Notice of Preliminary >> Determination To Grant Registrar Data Retention Waiver Request for >> Ascio Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. >> USA >> >> >> [ICANN]<http://www.icann.org/> >> News Alert >> >> https://www.icann.org/news/announcement-2015-12-09-en >> >> ________________________________ >> Notice of Preliminary Determination To Grant Registrar Data Retention >> Waiver Request for Ascio Technologies, Inc. Danmark - filial af Ascio >> Technologies, Inc. USA >> >> 9 December 2015 >> >> ICANN has made a preliminary determination that it is prepared to >> grant a data retention waiver request submitted by Registrar Ascio >> Technologies, Inc. Danmark - filial af Ascio Technologies, Inc. USA >> ("Ascio") under the > 2013 >> Registrar Accreditation Agreement (the "2013 RAA"). Section 2 of the >> Data Retention Specification (the "Specification") of the 2013 RAA >> provides > that >> prior to granting any exemption under the Specification, ICANN will >> post > its >> determination on the ICANN website for a period of thirty (30) >> calendar > days. >> Pursuant to Section 2 of the Specification, Ascio has submitted to >> ICANN a Registrar data retention waiver request ("Waiver Request") on >> the basis of Ascio's contention that compliance with the data >> collection and/or > retention >> requirements of the Specification violates applicable law in Denmark. >> >> The Waiver Request was accompanied by a written legal opinion from a >> nationally recognized law firm citing section 5 (5) of the Danish Act >> on Processing of Personal Data of 31 May 2000 (the "DPPD"). That >> section provides as follows (the following is an unofficial English >> translation > from >> Danish): >> >> Section 5 (5). >> >> The data collected may not be kept in a form which makes it possible >> to identify the data subject for a longer period than is necessary for >> the purposes for which the data are processed. >> >> Following receipt of the Waiver Request, and in accordance with the >> 2013 RAA, ICANN through its legal counsel and Ascio discussed the >> matter in > good >> faith in an effort to reach a mutually acceptable resolution of the > matter. >> The outcome of those discussions is that Ascio is seeking a waiver >> with respect to Sections 1.1.1 through 1.1.8 of the Specification that >> seeks to reduce from two years to one year the period for which these >> specified > data >> elements must be retained after the Registrar's sponsorship of the >> Registration ends. >> >> ICANN has determined on a preliminary basis that it is prepared to >> grant > the >> Waiver Request. ICANN is posting this preliminary determination for a > period >> of thirty (30) calendar days to seek feedback and input from the >> community on the proposed data retention waiver. After the thirty (30) >> calendar day period following this posting has expired, ICANN will >> consider all > feedback >> and input received before making a final determination on whether to >> grant the Waiver Request. >> >> The scope of the proposed waiver would be to permit Ascio to maintain >> the information specified in Sections 1.1.1 through 1.1.8 of the >> Specification > for >> the duration of its sponsorship of the Registration and for a period >> of > one (1) >> additional year thereafter rather than two (2) additional years > thereafter. In >> all other respects the terms of the Specification would remain AS-IS. >> >> The specific change to the Specification would be that, for the >> duration > of the >> Waiver, the retention requirement of Section 1.1 of the Data Retention >> Specification be changed from "two additional years" to "one >> additional year." >> >> If ICANN does make a final determination to grant the Waiver Request >> sought by Ascio, the provisions of Section 3 of the Specification >> would > apply >> to similar waivers requested by other registrars located in Denmark >> and subject to Danish law. Section 3 of the Specification provides as > follows: >> If (i) ICANN has previously waived compliance with the requirements of >> any requirement of this Data Retention Specification in response to a >> Waiver Request from a registrar that is located in the same >> jurisdiction as > Registrar >> and (ii) Registrar is subject to the same applicable law that gave >> rise to ICANN's agreement to grant such waiver, Registrar may request >> that ICANN to grant a similar waiver, which request shall be approved >> by ICANN, > unless >> ICANN provides Registrar with a reasonable justification for not >> approving such request, in which case Registrar may thereafter make an >> Wavier Request pursuant to Section 2 of this Data Retention Specification. >> >> The Registrar's Waiver Request and supporting documents are available >> here: >> https://www.icann.org/en/system/files/files/waiver-request-ascio- >> technologies-09dec15-en.pdf [PDF, 6.39 MB] >> >> A public comment period will remain open until 23:59 UTC, 11 January 2016. >> Public comments will be available for consideration by ICANN staff and >> the ICANN Board. >> >> * Comments can be posted to: comments-ascio-technologies- >> 09dec15(a)icann.org<mailto:comments-ascio-technologies- >> 09dec15(a)icann.org> >> * Comments can be viewed at: http://forum.icann.org/lists/comments- >> ascio-technologies-09dec15/ > > > _______________________________________________ > At-Large mailing list > At-Large(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/at-large > > At-Large Official Site: http://atlarge.icann.org -- Christian de Larrinaga FBCS, CITP, ------------------------- @ FirstHand ------------------------- +44 7989 386778 cdel(a)firsthand.net -------------------------

1 0

Weekly posting summary for at-large@atlarge-lists.icann.org
by Thomas Narten Dec. 11, 2015

Dec. 11, 2015

Total of 26 messages in the last 7 days. script run at: Fri Dec 11 00:53:02 EST 2015 Messages | Bytes | Who --------+------+--------+----------+------------------------ 3.85% | 1 | 76.72% | 7840890 | seun.ojedeji at gmail.com 7.69% | 2 | 19.78% | 2021485 | ocl at gih.com 19.23% | 5 | 0.72% | 73527 | staff at atlarge.icann.org 15.38% | 4 | 1.01% | 103610 | cw at christopherwilkinson.eu 7.69% | 2 | 0.36% | 36728 | kankaili at gmail.com 7.69% | 2 | 0.15% | 15758 | avri at acm.org 3.85% | 1 | 0.17% | 17428 | vanda at scartezini.org 3.85% | 1 | 0.17% | 17261 | carlton.samuels at gmail.com 3.85% | 1 | 0.17% | 16873 | joly at punkcast.com 3.85% | 1 | 0.15% | 14840 | jjs at dyalog.net 3.85% | 1 | 0.13% | 13782 | roberto_gaetano at hotmail.com 3.85% | 1 | 0.12% | 12361 | karl at cavebear.com 3.85% | 1 | 0.11% | 10999 | evanleibovitch at gmail.com 3.85% | 1 | 0.10% | 10114 | apisan at unam.mx 3.85% | 1 | 0.08% | 8106 | narten at us.ibm.com 3.85% | 1 | 0.07% | 6874 | johnl at iecc.com --------+------+--------+----------+------------------------ 100.00% | 26 |100.00% | 10220636 | Total

1 0

New Public Comment: Launch of Supplementary Registration Proxy Service for gTLDs Operated by XYZ.COM LLC
by ICANN At-Large Staff Dec. 11, 2015

Dec. 11, 2015

Dear All, This is to let you know that the Public Comment on the Launch of Supplementary Registration Proxy Service for gTLDs Operated by XYZ.COM LLC has now gone live: https://www.icann.org/public-comments/supplemental-registration-proxy-2015-…. The dates of the Public Comment will be 10 December 2015 - 19 January 2016 23:59 UTC. During this period, anyone can submit comment via comments-registration-proxy-10dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/ZIplAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Fwd: [CCWG-ACCT] Translated CCWG Webinar Slides
by León Felipe Sánchez Ambía Dec. 9, 2015

Dec. 9, 2015

Dear all, I am forwarding the slides used in the CCWG accountability webinar. Slides have been translated into Arabic, Spanish, Portuguese, Chinese, French and Russian. I hope you find this information useful. Saludos, León Best regards, León > Inicio del mensaje reenviado: > > De: Hillary Jett <hillary.jett(a)icann.org> > Fecha: 8 de diciembre de 2015, 10:39:43 a.m. GMT-6 > Para: CCWG-Accountability <accountability-cross-community(a)icann.org> > Asunto: [CCWG-ACCT] Translated CCWG Webinar Slides > > Hello everyone, > > Please find attached the translated slides from the 2 December 2015 CCWG-Accountability webinars. The slides are also located on the wiki here: https://community.icann.org/x/woJlAw <https://community.icann.org/x/woJlAw> > > Thank you, > Hillary > > -- > Hillary Jett > Communications Coordinator > Internet Corporation for Assigned Names and Numbers (ICANN) > > Mobile: +1 (202) 674-3403 > Email: hillary.jett(a)icann.org <mailto:hillary.jett@icann.org> > > > _______________________________________________ > Accountability-Cross-Community mailing list > Accountability-Cross-Community(a)icann.org > https://mm.icann.org/mailman/listinfo/accountability-cross-community

2 1

LAST DAY - CALL FOR COMMENTS: ALAC Statement on the gTLD Marketplace Health Index Proposal
by ICANN At-Large Staff Dec. 8, 2015

Dec. 8, 2015

Dear All, On behalf of the ALAC, Olivier Crepin-Leblond has developed the first draft ALAC Statement on the gTLD Marketplace Health Index Proposal<https://newatlarge.icann.org/advice_statements/9745>. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/7L5YAw. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function by 08 December 2015. You will need to log in to the wiki to use the comment function. If you don't have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Fwd: [CCWG-ACCT] Translated CCWG Webinar Slides
by Seun Ojedeji Dec. 8, 2015

Dec. 8, 2015

This could be of interest to those who like to follow the work of the ccwg in other languages aside English. Regards ---------- Forwarded message ---------- From: "Hillary Jett" <hillary.jett(a)icann.org> Date: Dec 8, 2015 17:40 Subject: [CCWG-ACCT] Translated CCWG Webinar Slides To: "CCWG-Accountability" <accountability-cross-community(a)icann.org> Cc: Hello everyone, Please find attached the translated slides from the 2 December 2015 CCWG-Accountability webinars. The slides are also located on the wiki here: https://community.icann.org/x/woJlAw Thank you, Hillary -- *Hillary Jett* Communications Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (202) 674-3403 Email: hillary.jett(a)icann.org _______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community(a)icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

1 0

New Public Comment: Label Generation Ruleset for the Root Zone Version 1 (LGR-1)
by ICANN At-Large Staff Dec. 7, 2015

Dec. 7, 2015

Dear All, This is to let you know that the Public Comment on the Label Generation Ruleset for the Root Zone Version 1 (LGR-1) has now gone live: https://www.icann.org/public-comments/lgr-1-2015-12-04-en. The dates of the Public Comment will be 04 December 2015 - 27 February 2016 23:59 UTC. During this period, anyone can submit comment via comments-lgr-1-04dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/GIdlAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

New Public Comment: Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs
by ICANN At-Large Staff Dec. 7, 2015

Dec. 7, 2015

Dear All, This is to let you know that the Public Comment on the Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs has now gone live: https://www.icann.org/public-comments/rdds-output-2015-12-03-en. The dates of the Public Comment will be 03 December 2015 - 18 January 2016 23:59 UTC. During this period, anyone can submit comment via comments-rdds-output-03dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/FIdlAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

New Public Comment: Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars
by ICANN At-Large Staff Dec. 7, 2015

Dec. 7, 2015

Dear All, This is to let you know that the Public Comment on the Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars has now gone live: https://www.icann.org/public-comments/rdap-profile-2015-12-03-en. The dates of the Public Comment will be 03 December 2015 - 18 February 2016 23:59 UTC. During this period, anyone can submit comment via comments-rdap-profile-03dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/JYZlAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

MEETUP TODAY: IANA, ICANN – what it is, why you should care, and what you can do. A bottom-up primer. @CivicHall
by Joly MacFie Dec. 4, 2015

Dec. 4, 2015

Very last minute I know, but we didn't want to pass up the opportunity of Olivier being in NYC for a conference. Happily he was just able to fit us in. All are welcome to show up at Civic Hall at 3pm. If you can't make it you can join via zoom or phone. There will be a webcast, primarily as an archive for those whose timetable precludes attendance. If joining remotely please remember to mute your mic when not speaking. [image: iana_icann] <http://isoc-ny.org/p2/wp-content/uploads/2015/12/iana_icann.png>Today *Friday December 4 2015 at 3pm EST* the *Internet Society New York Chapter <http://isoc-ny.org/>* (ISOC-NY) will hold an informal discussion *IANA, ICANN, - what it is, why you should care, and what you can do <http://isoc-ny.org/p2/8227>* at *Civic Hall* in NYC. Special guest and presenter will be *Olivier Crépin-Leblond*, former Chair of ICANN's *At-Large Advisory Committee <http://atlarge.icann.org/>*. He will give an update of the current IANA transition and the associated ICANN accountability process, and then talk about why and how Internet users can protect their interests and the common good. Remote participation and a webcast will be available. *What: IANA, ICANN, - what it is, why you should care, and what you can do <http://isoc-ny.org/p2/8227>Where: Civic Hall, 156 5th Ave, NYCWhen: Friday December 4 2015 at 3pm-4:30pm EST (20:00-21:30 UTC)Remote Participation: https://zoom.us/j/462488331 <https://zoom.us/j/462488331>Phone bridge: +1 646 558 8656 Meeting ID: 462 488 331Webcast: https://livestream.com/internetsociety3/ianaicann <https://livestream.com/internetsociety3/ianaicann>Twitter: #IANA + #ICANN - https://twitter.com/search?q=%23IANA%20%20%23ICANN <https://twitter.com/search?q=%23IANA%20%20%23ICANN>* Comment <http://isoc-ny.org/p2/8227#respond> See all comments <http://isoc-ny.org/p2/8227#comments> *Permalink* http://isoc-ny.org/p2/8227 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Weekly posting summary for at-large@atlarge-lists.icann.org
by Thomas Narten Dec. 4, 2015

Dec. 4, 2015

Total of 7 messages in the last 7 days. script run at: Fri Dec 4 00:53:04 EST 2015 Messages | Bytes | Who --------+------+--------+----------+------------------------ 28.57% | 2 | 54.53% | 216212 | leonfelipe at sanchez.mx 14.29% | 1 | 31.23% | 123845 | kankaili at gmail.com 28.57% | 2 | 7.33% | 29075 | staff at atlarge.icann.org 14.29% | 1 | 4.86% | 19253 | at-large at atlarge-lists.icann.org 14.29% | 1 | 2.05% | 8136 | narten at us.ibm.com --------+------+--------+----------+------------------------ 100.00% | 7 |100.00% | 396521 | Total

1 0

New Public Comment: Continuous Data-driven Analysis of Root Server System Stability (CDAR) Study Plan
by ICANN At-Large Staff Dec. 3, 2015

Dec. 3, 2015

Dear All, This is to let you know that the Public Comment on the Continuous Data-driven Analysis of Root Server System Stability (CDAR) Study Plan has now gone live: https://www.icann.org/public-comments/cdar-study-plan-2015-12-02-en. The dates of the Public Comment will be 02 December 2015 - 03 February 2016 23:59 UTC. During this period, anyone can submit comment via comments-cdar-study-plan-02dec15(a)icann.org. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/34RlAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 1

New Public Comment: CCWG-Accountability - Draft Proposal on Work Stream 1 Recommendations
by ICANN At-Large Staff Dec. 1, 2015

Dec. 1, 2015

Dear All, This is to let you know that the Public Comment on the CCWG-Accountability - Draft Proposal on Work Stream 1 Recommendations has now gone live: https://www.icann.org/public-comments/draft-ccwg-accountability-proposal-20…. The dates of the Public Comment will be 30 November 2015 - 21 December 2016 23:59 UTC. During this period, anyone can submit comment via As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/d4NlAw. All pertinent resources for this public comment can also be found there. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0