May 2019 - NA-Discuss - lists.icann.org

IMPORTANT: ATLAS III Webinar: Onboarding: Country Code Names Supporting Organization (ccNSO)
by ICANN At-Large Staff May 3, 2019

May 3, 2019

NOTE – dates for the webinars are posted here: NOTA: las fechas de los seminarios web se publican aquí: A NOTER: les dates des webinaires sont affichées ici: https://community.icann.org/display/ATLAS3/Online+Training+Courses https://community.icann.org/x/wh1IBg ********************* Español después de la version en inglés Version francaise en bas du mail ********************* Dear All, On behalf of Joanna Kulesza and Alfredo Calderon, Co-Chairs of the ATLAS III Capacity Building Sub Group, we would like to invite you to join the third webinars of the mandatory ATLAS III Webinars<https://community.icann.org/display/ATLAS3/Online+Training+Courses>: Onboarding: Country Code Names Supporting Organization (ccNSO), which will be held in English with French and Spanish interpretation. The trainers are: Session 1 on Tuesday: Joke Braeken<https://www.icann.org/profiles/39799> Session 2 on Wednesday: Bart Boswinkel<https://www.icann.org/profiles/81> The replicated webinars are scheduled on: 1. Tuesday, 07 May at 21:00 UTC – for other times: https://tinyurl.com/y3vzu7k4 * Presenter: Joke Braeken<https://www.icann.org/profiles/39799> * Call details: https://community.icann.org/x/q4iGBg c. Zoom URL:https://icann.zoom.us/j/452605306[icann.zoom.us<https://icann.zoom.us/j/452605306%5bicann.zoom.us> 1. Wednesday, 08 May at 12:00 UTC – for other times: https://tinyurl.com/y4qaq9fn * Presenter: Bart Boswinkel<https://www.icann.org/profiles/81> * Call details: https://community.icann.org/x/v4iGBg * Zoom: Join URL: https://icann.zoom.us/j/456885967 To meet the attendance requirements for ATLAS III, participants must join the ZOOM Room (as well as the ADIGO Bridge for French or Spanish)no more than 10 minutes after the scheduled start time. If you join later, your participation will not be valid for ATLAS III Criteria. (note Application Guidelines<https://community.icann.org/x/cgB1Bg> under ATLAS III Prep Courses). ALL English speakers are able to take the ICANN Learn courses instead. Conference IDs: EN: 1638 ES: 1738 FR: 1838 If you require a dial-out, please contact At-Large Staff at staff(a)atlarge.icann.org<applewebdata://7A10FE21-3394-495B-A5F0-7E30855046D9/staff@atlarge.icann.org> (do not reply to all) with: * date and time of the webinar * language channel * your preferred telephone number. Thank you. Kind regards, ******************* Queridos todos, En nombre de Joanna Kulesza y Alfredo Calderón, Co-presidentes del Subgrupo de Desarrollo de Capacidades de ATLAS III, nos gustaría invitarlos a participar en el tercero seminarios web de los seminarios web obligatorios de ATLAS III: Onboarding: Country Code Names Supporting Organization (ccNSO) que se celebrarán en inglés y la interpretación en español y en francés. Los presentadores estaràn: - Session uno el martes: Joke Braeken<https://www.icann.org/profiles/39799> - Session dos el jueves: Bart Boswinkel<https://www.icann.org/profiles/81> Los webinars replicados están programados en: 1. Martes, 07 May a la 21:00 UTC - para otros horarios: https://tinyurl.com/y3vzu7k4 a. Presentadores: Joke Braeken<https://www.icann.org/profiles/39799> b. Detalles de la llamada: https://community.icann.org/x/q4iGBg c. Zoom URL:https://icann.zoom.us/j/452605306[icann.zoom.us<https://icann.zoom.us/j/452605306%5bicann.zoom.us> 2. Miercoles, 08 May a las 12:00 UTC - para otros horarios: https://tinyurl.com/y4qaq9fn * Presentadores: Bart Boswinkel<https://www.icann.org/profiles/81> * Detalles de la llamada: https://community.icann.org/x/v4iGBg * Zoom URL:https://icann.zoom.us/j/456885967[icann.zoom.us<https://icann.zoom.us/j/456885967%5bicann.zoom.us>] Para cumplir con los requisitos de asistencia para ATLAS III, los participantes deben unirse tanto a Adigo Bridge (para audio español o frances)como a ZOOMRoom (audio en ingles) no más de 10 minutos después de la hora de inicio programada. (tome nota de las Pautas de aplicación<https://community.icann.org/x/cgB1Bg> bajo los cursos de preparación ATLAS III). Si se une más tarde, su participación no será válida para los criterios de ATLAS III. ID de conferencia para ADIGO Audio EN: 1638 ES: 1738 FR: 1838 Si necesita una llamada de salida, comuníquese con el personal de At-Large enstaff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> (no responda a todos) con: * fecha y hora del webinar * canal de idioma * Su número de teléfono preferido. Gracias. Saludos cordiales, ******************* Chers tous, Au nom de Joanna Kulesza et Alfredo Calderon, co-présidents du sous-groupe de renforcement des capacités d'ATLAS III, nous vous invitons à participer au troisième webinaires des webinaires obligatoires d'ATLAS III: Onboarding: Country Code Names Supporting Organization (ccNSO), qui se dérouleront en anglais avec interpretation en français et espagnol. Les présentateurs seront: - Session un le mardi: Joke Braeken<https://www.icann.org/profiles/39799> - Session deux le jeudi: Bart Boswinkel<https://www.icann.org/profiles/81> Les webinaires répliqués sont programmés: 1. Mardi 07 mai à 21h00 UTC - pour les autres heures: https://tinyurl.com/y3vzu7k4 * Presentateur: Joke Braeken<https://www.icann.org/profiles/39799> * Détails de l'appel:https://community.icann.org/x/q4iGBg c. Zoom URL:https://icann.zoom.us/j/452605306[icann.zoom.us<https://icann.zoom.us/j/452605306%5bicann.zoom.us> 1. Mercredi 08 mai à 12h00 UTC - pour les autres heures: https://tinyurl.com/y663tmye * Presentateur: Bart Boswinkel<https://www.icann.org/profiles/81> * Détails de l'appel:https://community.icann.org/x/v4iGBg * Zoom URL:https://icann.zoom.us/j/456885967 Pour répondre aux critères de participation à ATLAS III, les participants doivent se joinder à la sale ZOOM (qui sera en ANGLAIS) et pour l’audio en francais, IMPERATIVEMENT se joindre au canal francais sur l’audio ADIGO et ceci au plus tard 10 minutes après l'heure de début prévue. Si vous vous connectez apres les 10 première minutes, votre participation ne sera pas validée selon les critères de participation pour l’ATLAS III(notez les directives d’application<https://community.icann.org/x/cgB1Bg> dans les cours de préparation au ATLAS III) ID de conference pour l’Audio ADIGO EN: 1638 ES: 1738 FR: 1838 Si vous avez besoin qu’une opératrice vous connecte, veuillez contacter le personnel At-Large à staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> (ne pas répondre à tous) avec: * La date et heure du wébinaire * Langue * Votre numéro de téléphone préféré. Nous vous en remercions. Cordialement, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

I am leaving the At-Large, as it appears to me to be captured
by George Kirikos May 3, 2019

May 3, 2019

Hi folks As I discussed on the CPWG mailing list: https://mm.icann.org/pipermail/cpwg/2019-May/001180.html I was strongly concerned about capture of the At Large, and my concerns have been ignored and dismissed, given the statement that ALAC sent to the .org public comments yesterday, after the CPWG call. I submitted my own additional comment a few minutes ago, arguing why that statement should be given little weight (see below). As such, I am now leaving the At Large. Please remove me from all the relevant mailing lists and notification lists. Sincerely, George Kirikos 416-588-0269 http://www.leap.com/ On Fri, May 3, 2019 at 8:48 AM George Kirikos <icann(a)leap.com> wrote: > > Submitted by: George Kirikos > Company: Leap of Faith Financial Services Inc. > Website: http://www.leap.com/ > Date: May 3, 2019 > > In addition to our prior comments (below), we would like to point out > that the submission by ALAC at: > > https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003297.h… > > (and in similar comments for .biz, .info, .asia) > > should be given very little weight, as it appears to be > unrepresentative of the billions of users of the internet (which At > Large purports to represent). Rather, it reflects the views of a small > number of individuals, many of whom have current or past associations > with Internet Society or its various chapters. > > This was pointed out by me in the thread at: > > https://mm.icann.org/pipermail/cpwg/2019-May/001180.html > > of the Consolidated Policy Working Group of the At Large: > > ----- start of snippet -------- > Look at the actual history of this matter. At the last meeting, it > was decided that At-Large would not be making a statement. What "new > information" exists since that decision, to justify change? There is > none, other than the fact that thousands of others have made comments, > and so presumably some of ISOC's friends and/or allies feel the need > to help ISOC. That's not a good justification at all. > > Remember, Jonathan even wrote on Friday: > > https://mm.icann.org/pipermail/cpwg/2019-April/001099.html > > "Let's table this discussion until we can have a more thorough > exploration of the issues. Email is a terrible way in which to have > such a discussion. " > > But then some people ignored that, wanting to relitigate a decided > issue. And, many of those people were present at last week's meeting > too, so they already had their chance. Again, what new information did > they have? None. Did Jonathan rebuke them for not tabling the > discussion? Nope. > > Indeed, look at Greg Shatan's email at: > > https://mm.icann.org/pipermail/cpwg/2019-April/001094.html > > "I believe that PIR was hoping for a comment along the lines of our > first draft (which I believe they saw on our site) or our second > draft." > > That is again entirely consistent with capture. > > 5. It's obvious that many folks have some past or present connection > to ISOC or one of its chapters, or perhaps even aspirational future > connections with them. e.g. Greg Shatan's is obvious, via the NYC > chapter of ISOC. > > Maureen Hilyard's SOI: > > https://community.icann.org/display/atlarge/Maureen+Hilyard+SOI > > mentions the "Pacific Islands Chapter of the Internet Society" > > Marita Moll has a history with the Canadian chapter: > > http://www.maritamoll.ca/content/about-site > > Cheryl Landon-Orr's SOI: > > https://community.icann.org/display/atlarge/Cheryl+Langdon-Orr+SOI > > mentions "Internet Australia (IA) formally known as the Internet > Society of Australia ( ISOC-AU)" > > John Laprise's LinkedIn profile: > > https://www.linkedin.com/in/jplaprise > > mentions "cofounding Qatar's Internet Society chapter" as well as > "Faculty" of Internet Society in May 2014. > ---- end of snippet ----------- > > There are even more than those, e.g. > > Evan Leibovitch's involvement with the Canadian chapter of the Internet Society: > > https://www.itworldcanada.com/article/canadian-chapter-of-internet-society-… > > and Glenn McKnight: > > https://www.internetsociety.org/author/mcknight/ > > "co-founder of Internet Society Canada Chapter and held positions for > three years as Treasurer, Secretariat and Board member. In 2017, > Glenn was elected to the Internet Society Board of Trustees by the > Chapters for a 3-year term from 2017-2020." > > Indeed, at yesterday's CPWG meeting (where that ALAC position was > finalized for .org), Maureen Hilyard (the penholder for the .asia > statement, and current Chair of ALAC) casually mentioned that she was > on the Board of Dot-Asia,. She even circulated her draft to the > Dot-Asia folks for comments to see if there were any problems with it! > Apparently no one but myself within the CPWG call yesterday saw how > that would be unusual. > > Indeed, Maureen Hilyard is on the Advisory Council of PIR itself: > > https://pir.org/about-us/advisory-council/maureen-hilyard-ngo-ong-cook-isla… > > Given the lack of diversity and low participation in At Large, it's > prone to capture (as others have pointed out, in the email I sent to > the CPWG mailing list). It's clear to me that the ALAC statement is a > product of such capture. > > Sincerely, > > George Kirikos > 416-588-0269 > http://www.leap.com/ > > On Mon, Apr 29, 2019 at 4:51 PM George Kirikos <icann(a)leap.com> wrote: > > > > Submitted by: George Kirikos > > Company: Leap of Faith Financial Services Inc. > > Website: http://www.leap.com/ > > Date: April 29, 2019 > > > > We write to oppose the proposed contract renewals posted by ICANN for > > the .org, .info, .biz and .asia contracts, as posted for public > > comments at: > > > > https://www.icann.org/public-comments/org-renewal-2019-03-18-en > > https://www.icann.org/public-comments/info-renewal-2019-03-18-en > > https://www.icann.org/public-comments/biz-renewal-2019-04-03-en > > https://www.icann.org/public-comments/asia-renewal-2019-03-27-en > > > > While our arguments are focused on the .org TLD, to the extent that > > the contractual terms are similar for the other TLDs, we repeat the > > same comments for .info, .biz and .org. Indeed, while the majority of > > the thousands of public comments to date have focused on .org, ICANN > > should read those comments as also applying to .info, .biz and .org, > > even if the submitters did not explicitly submit their comments to all > > 4 email addresses. > > > > 1. We support and endorse the great groundswell of opposition as > > expressed in the thousands of thoughtful public comments opposed to > > these proposed agreements. It is shocking that ICANN did not learn its > > lesson from 2006, when similar massive opposition existed for > > comparable contracts which would have allowed for unlimited fee > > increases: > > > > https://forum.icann.org/lists/org-tld-agreement/ > > > > The proposed contracts are simply unconscionable, and ICANN should > > instead simply extend the existing contracts by another 6 or 10 years, > > rather than make any other changes. > > > > 2. Within the At-Large, we had a video discussion/debate, archived at: > > > > https://freespeech.com/2019/04/10/impact-of-the-urs-and-unlimited-fee-incre… > > > > https://youtu.be/KW3I1oFGbv0 > > > > where many of the points below are discussed, and I include them here > > by reference. > > > > 3. We particularly agree with the comments and/or blogs submitted/posted by: > > > > a) Nat Cohen / Telepathy: > > > > https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003067.h… > > http://www.circleid.com/posts/20190423_spurious_justifications_for_eliminat… > > > > b) NameCheap: > > > > https://www.namecheap.com/blog/keep-domain-prices-in-check/ > > > > c) Zak Muscovitch / Internet Commerce Association: > > > > https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/000006.h… > > > > d) Jay Chapman / Digimedia: > > > > https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/002967.h… > > > > e) Andrew Allemann: > > > > https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003091.h… > > > > 4. It should be noted that in the past ICANN trumpeted lower fees as > > one of its main achievements. For example, the testimony of ICANN > > General Counsel and Secretary John Jeffrey at: > > > > https://www.govinfo.gov/content/pkg/CHRG-109hhrg30233/html/CHRG-109hhrg3023… > > > > "STATEMENT OF JOHN JEFFREY, INTERNET CORPORATION FOR ASSIGNED NAMES > > AND NUMBERS (ICANN) > > ... > > Among ICANN's main achievements are the following: > > ... > > Market competition. Market competition for generic top-level > > domain registrations established by ICANN has ****lowered > > domain name cost in some instances as much as 80 percent with savings > > for both consumers and businesses.****" (emphasis added) > > > > It is not consistent with those past statements for ICANN to abrogate > > its responsibilities, and permit unlimited fee increases by registry > > operators. Unlimited fee increases are not in the public interest, and > > do not even attempt to balance the needs of registrants against those > > of registry operators. ICANN was handed a responsibility to balance > > the interest of affected stakeholders when it achieved (against our > > wishes) independence from US government oversight, and it's now clear > > that it is not living up to those commitments given such one-sided > > contracts that have been presented here for public comment. Unlimited > > fee increases are not balanced, and do not promote stability of the > > internet or competition. ICANN is engaging in corporate welfare and/or > > crony capitalism through such anti-competitive proposals as are here > > before us. > > > > 5. As has been pointed out by others, under competition the cost of > > providing registry services (really just the management of a central > > database plus the operation of various nameservers) would be under USD > > $1.00 per domain name per year. This is evidenced by the .IN (India) > > tender, where Neustar beat Afilias with a winning bid of USD $0.70 per > > domain name per year (70 cents/domain/yr): > > > > http://domainincite.com/23364-afilias-sues-india-to-block-12-million-neusta… > > > > A similar competitive tender process happened in France: > > > > https://www.thedomains.com/2012/08/07/afnic-awarded-new-contract-to-run-fr-… > > > > where AFNIC had to lower the wholesale fees for .FR domain names, and > > the contract was for 5 years. > > > > Similar competitions are held for the .US ccTLD: > > > > https://www.ntia.doc.gov/legacy/ntiahome/press/2007/Neustar_101907.html > > > > You'll note that registry operators do not have presumptive renewal in > > those ccTLD contracts, yet are more than willing and able to compete > > effectively and make investments. It was a major policy blunder of > > ICANN to have agreed in the past to presumptive renewal, a decision > > that has had a multi-billion dollar negative impact upon registrants, > > compared to a situation where there are regular competitive tenders. > > Even the US government has argued for those competitive tenders for > > both initial agreements and for renewals of agreements: > > > > https://www.ntia.doc.gov/files/ntia/publications/icann_081218.pdf > > > > (Ms. Garza's analysis begins on the 3rd page of the PDF, after the > > covering letter by Ms. Baker of the NTIA) > > > > The absence of such competitive tenders can only be rectified through > > the protective fee caps which have been long established, and which > > the registry operators themselves have agreed to since the times they > > entered into their respective agreements. If current registry > > operators are not prepared to renew the existing contracts (which have > > fee caps in place), then there would be no shortage of other > > prospective registry operators who would be prepared to step in and > > replace them (and at a much lower cost, with fee caps in place). > > > > Indeed, ICANN themselves have argued (in court) that such caps are > > *pro-competitive*, see: > > > > https://www.icann.org/en/system/files/files/icann-reply-on-cfit-26may06-en.… > > > > "....in a single supplier market, price caps are, if anything, > > procompetitive (Mot. at 13-14);" > > > > (line 13, page 6 of 15) > > > > 6. We would like to openly make ICANN the following offer: We will run > > the .org registry for USD $5 per domain name per year, and keep all > > other existing terms the same. [We would then simply subcontract it to > > one of the many registry operators who would bid for the job at USD $1 > > per domain per year or less, and pocket the difference!] This is lower > > than the $9.93 per domain name per year that PIR currently charges. > > ICANN cannot of course accept this improved deal, even if it wanted > > to, because its hands are tied by the foolish decision to agree to > > presumptive renewal in the past. > > > > Looking forward, an agreement to permit unlimited fee increases in the > > future (far beyond the already generous 10% per year permitted > > increases) would similarly hamper ICANN's ability to negotiate future > > "win-win" deals, giving it no negotiating leverage in the future, as > > it would have already given away the farm if it entered into this > > proposed agreement. > > > > Agreeing to permit unlimited fee increases is like letting the genie > > out of the bottle, as there's no way that registry operators will ever > > agree to voluntarily undo such a change in the future. Presumptive > > renewal means that registry operators can safely ignore any future > > attempts by ICANN to renegotiate. This is why these contractual > > changes are so important, because they'll be impossible to fix in the > > future (without giving up even more to registry operators, e.g. via a > > buyout or something). This alone should be reason for caution. Given > > there's no urgency to making a change (i.e. registry operators have > > *falling* costs, not increasing costs), then the status quo should > > prevail. > > > > 6. Some have suggested that the Internet Society and/or PIR would > > never raise fees by a large amount. However, "hope is not a strategy." > > Past performance is no guarantee of the future. Leadership can change, > > as can priorities/missions. It's clear from section 7.5 of the the > > draft contract itself: > > > > https://www.icann.org/sites/default/files/tlds/org/org-proposed-renewal-18m… > > > > that ISOC/PIR could simply sell or assign the registry contract to > > another entity (e.g. Private Equity, just as registry operator Donuts > > was sold by its founders), and that new owner/entity could take the > > heat for future egregious fee increases. ICANN would not be able to > > stop such a deal. Such a sale would allow ISOC to create a huge > > endowment for itself worth billions of dollars, given that .org is > > arguably the second most desirable gTLD, after only .com. > > > > 7. The ability to renew a domain name for 10 years is not sufficient > > protection for registrants. Eventually the bill will come due, and > > nothing can offset the enormous switching costs. Any > > goodwill/links/etc. built up will be reduced to zero, totally > > destroying one's investment in one's web identity that may have been > > built up over 20+ years (even longer than ICANN has existed, in many > > cases). URLs that have been printed in offline media such as books, > > DVDs, etc. can't be updated, thus it's impossible for many to simply > > stop renewing after 10 years and switch, as some people will still see > > the old URL. E-mails aren't forwarded by the new registrants to those > > of past registrants, meaning that all existing email addresses can't > > easily transition to a new domain name without risk. Business cards > > would need to be reprinted (and can't be "recalled" from past > > recipients). Registrants expect URLs to be permanent, not transitory. > > Registrants of legacy gTLDs like com/net/org own their domain names, > > and are not temporary tenants (like those in the failed new gTLDs). > > > > 8. One of the reasons prospective registrants rationally avoid new > > gTLDs is the lack of certainty over potential future fee increases. As > > one submission pointed out, they are "leery" of such one-sided > > contracts, and for good reason. Those failures of the new gTLDs > > experiment should not be allowed to contaminate the successful and > > proven legacy gTLDs like .com/net/org. Indeed, if there is to be any > > harmonization of contracts, the "base agreement" should be that of the > > successful .com/net/org TLDs which included fee caps, rather than have > > the future be modeled on the the failed new gTLDs program. Registrants > > of new gTLDs knew the problems with the lack of price caps, and > > foolishly agreed to them before registration. Changing the rules for > > existing registrants of legacy gTLDs is unacceptable, as this amounts > > to changing the rules in the middle of the game, rules which would > > never have been acceptable to most prior to registration. > > > > One submission suggested that as each new gTLD matures, or reaches a > > critical mass, it should then transition to the legacy contracts. That > > was a wise suggestion, to bridge the failed new gTLD program with the > > successful legacy gTLDs. > > > > 9. Even ISOC/PIR doesn't enter into such one-sided agreements, given > > that its own supplier/subcontractor (Afilias) had to win a competitive > > tender to retain the contract for managing the back-end of the > > registry (presumably at an even lower fee than it agreed to years ago > > -- fees would be able to be estimated once the relevant IRS Form 990 > > forms become public). > > > > https://domainnamewire.com/2016/02/16/32-million-org-contract-up-for-bids/ > > https://domainnamewire.com/2016/11/14/org-sticks-afilias-backend/ > > > > It's entirely inconsistent that Internet Society doesn't give > > presumptive renewal and/or permits unlimited fee increases for its own > > suppliers, yet wants such things for themselves. > > > > 10. We oppose the ability for the registry operators to unilaterally > > create and impose their own mandatory RPMs upon registrants. See, for > > example: > > > > https://www.icann.org/sites/default/files/tlds/org/org-proposed-addendum-18… > > > > "Specification 7, § 1 The terms of Section 1 of Specification 7 are > > hereby amended and restated in their entirety as follows: “Rights > > Protection Mechanisms. Registry Operator shall implement and adhere to > > the rights protection mechanisms (“RPMs”) specified in this > > Specification. In addition to such RPMs, Registry Operator ******may > > develop and implement RPMs that discourage or prevent registration of > > domain names that violate or abuse another party’s legal rights.****** > > Registry Operator will include all RPMs required by this Specification > > 7 and any additional RPMs developed and implemented by Registry > > Operator in the Registry-Registrar Agreement entered into by > > ICANN-accredited registrars authorized to register names in the TLD.” > > (page 6, emphasis added) > > > > This should be left to the GNSO, to develop only policies that have > > consensus, and which balance the needs of both rights holders and > > registrants. For example, suppose PIR (or another registry operator) > > was allowed to unilaterally create a RPM on their own which allowed > > for complaints to be filed for a fee of $100, but which required > > registrants post a $1 million bond if they wish to file any response > > to the complaint. Such a one-sided policy could be created by a > > registry operator under the proposed terms, and would ignore the > > requirement that ICANN policies need to balance the concerns of all > > affected stakeholders (including registrants). > > > > 11. We also oppose the searchable WHOIS, which ignores the ongoing > > EPDP on WHOIS: > > > > https://www.icann.org/sites/default/files/tlds/org/org-proposed-renewal-18m… > > (page 37) > > > > "Notwithstanding anything else in this Agreement, Registry Operator > > must offer a searchable Whois service compliant with the requirements > > described in Section 1.10 of Specification 4 of this Agreement." > > > > as it doesn't properly balance the privacy rights of registrants > > against those who would go on fishing expeditions. A searchable WHOIS > > system should only ever be adopted, if and only if the Trademark > > Clearinghouse (TMCH) equally becomes public and searchable, in return. > > If the TMCH is kept secret and non-searchable, then the WHOIS should > > not be searchable either. > > > > 12. Additional RPMs that were developed for new gTLDs were the result > > of bad predictions that were made of massive cybersquatting prior to > > the adoption of the program. For example, in testimony before the US > > government: > > > > https://www.govinfo.gov/content/pkg/CHRG-112shrg74251/html/CHRG-112shrg7425… > > > > "First, the immediate costs imposed on business is likely to be in the > > multi billions of dollars." > > > > "This Program in aggregate has multi-billion dollar implications for > > all marketers, both in the commercial and the nonprofit sectors, and > > their brands. It would cause irreparable harm and damage to the entire > > online business community. It would throw the domain name universe > > into substantial confusion for both marketers and consumers." > > > > "So there are billions of dollars that are going to be spent and it's > > not going to be providing a use for the economy." > > > > "And when we're talking about billions of dollars here, when we're > > talking about companies with 3,000 or more brands, even big companies > > will be facing really large expenses. So this is a very, very > > significant economic issue for this country and for the world." > > > > "An unlimited expansion of the TLDs will cost the business community > > billions of dollars." > > > > "The unlimited expansion of TLDs would dramatically increase the cost > > and complexity for trademark holders to protect their rights. The > > immediate cost imposed on businesses is likely to be in the billions > > of dollars." > > > > "We believe ICANN's gTLD program would impose billions of dollars in > > unnecessary costs on the restaurant industry at a time when restaurant > > operators are looking forward to investing in their businesses and > > hiring employees after the worst recession in decades." > > > > These predictions exaggerated and overestimated the actual risk that > > was realized by the launch of new gTLDs. Thus, the justification for > > the adoption of the URS and other RPMs turned out to be false > > predictions, and should now be undone. They were never intended for, > > nor should be imposed upon, registrants of legacy gTLDs. > > > > Prospective registry operators at the time were willing to accept such > > terms, as the trademark lobby threatened to thwart and delay the > > release of new gTLDs unless their demands were met. Registry operators > > were blinded by dollar signs in their eyes, for example, predictions > > by Name.Space: > > > > "Name.Space, whose business has a potential value of over 1 billion > > dollars, has been deprived the opportunity to fully launch and operate > > its portfolio of gTLD properties under what we believe is the most > > responsible, fair, and ethical practices yet to be employed in the > > commercial domain name industry." (same link as above for testimony) > > > > 13. Given that the RPM PDP of the GNSO is actively reviewing the URS, > > including determining whether or not it should be a consensus policy, > > no steps should be taken by ICANN staff and/or the registry operators > > to unilaterally impose it upon registrants. Indeed, there are numerous > > proposals to actively change the URS (including a proposal to > > explicitly eliminate it), see: > > > > https://community.icann.org/display/RARPMRIAGPWG/URS+Proposals > > > > (click the "Individual URS Proposal" tab to see the 33 individual > > proposals, 14 of them from us) > > > > The current URS is deeply flawed. For example of just one of the > > defects, currently complaints are required to be in English (unlike > > the language rules for the UDRP, where complaints must be in the > > language of the registration agreement, which varies by registrar). > > Thus, many registrants defending a URS dispute have no idea what the > > actual URS complaint is about, if they do not understand English. This > > is particularly egregious, given that new gTLDs are most popular in > > China. > > > > Such flawed RPMs whose creation was rushed before the launch of new > > gTLDs, and which are tilted in favour of large multinational > > companies, need to be reviewed and corrected before they are ever > > adopted for legacy gTLDs like .com/net/org. > > > > 14. In conclusion, ICANN's proposed contracts represent a failure of > > the multi-stakeholder model, and are instead evidence that ICANN has > > been captured by registry operators. ICANN claims these contracts are > > the result of a negotiation, yet what did registrants receive in > > return for these contractual changes? We received absolutely nothing > > in return, except for higher fees and higher regulatory burdens (via > > the imposition of the URS), with all the gains being received by the > > registry operators at the expense of registrants. That's not a > > negotiation -- that's a giveaway. > > > > We expect and demand that ICANN and the registry will simply extend > > the current contracts, rather than enter into these one-sided > > arrangements. > > > > Sincerely, > > > > George Kirikos > > 416-588-0269 > > http://www.leap.com/

2 5

WEBCAST THU-FRI: 15th Caribbean Internet Governance Forum #CIGF2019
by Joly MacFie May 2, 2019

May 2, 2019

The longest running annual IGF is underway. Introductions are just about done and the first multistakeholder panel will examine the tricky topic 'Imperatives and Contemporary Approaches for Effective Management or Regulation of Social Media' [image: livestream] <https://livestream.com/internetsociety/cigf2019>Today* Thursday 2nd May* to tomorrow *Friday 3rd May 2019* the *15th annual Caribbean Internet Governance Forum <https://www.ctu.int/event/15th-caribbean-internet-governance-forum/>* (CIGF2019) organized by the* Caribbean Telecommunications Union <https://www.ctu.int/> *(CTU) is taking place in *Trinidad and Tobago.* The longest running IGF in the world, as a part of the CTU’s wider *30th Anniversary Week <https://www.ctu.int/event/30th-anniversary-celebration/>*, CIGF 2019 has the theme '*Planning and sustaining the future development of Caribbean Internet Governance*' and will address contemporary topics such as data protection, network and service resilience and appropriate policies for navigating this age of social media. However, consistent with the headlined theme, there will be a special focus on enabling sustainability of the CIGF in its roles as the Caribbean’s primary multistakeholder consensus-building forum on IG matters, in fostering the development of national IGFs and in strengthening liaisons with wider regional, extra regional and global IGFs. The event will be webcast live via the *Internet Society Livestream Channel <https://livestream.com/internetsociety/>*. *VIEW ON LIVESTREAM: https://livestream.com/internetsociety/cigf2019 <https://livestream.com/internetsociety/cigf2019>* *VIEW ON YOUTUBE: https://www.youtube.com/user/TheCtunion/videos <https://www.youtube.com/user/TheCtunion/videos>* *VIEW ON FACEBOOK: https://www.facebook.com/pg/CaribbeanTelecommunicationsUnion/videos/ <https://www.facebook.com/pg/CaribbeanTelecommunicationsUnion/videos/>* *PROVISIONAL AGENDA: http://bit.ly/2Wkm6iA <http://bit.ly/2Wkm6iA>* *TWITTER #CIGF2019 https://bit.ly/cigf2019 <https://bit.ly/cigf2019> | #15CIGF http://bit.ly/2Wi6zjl <http://bit.ly/2Wi6zjl>* Comment <https://isoc.live/11042/#respond> See all comments <https://isoc.live/11042/#comments> *Permalink* https://isoc.live/11042/ -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

IMPORTANT - SECOND ATLAS III Webinars in EN with ES, FR interpretation
by ICANN At-Large Staff May 2, 2019

May 2, 2019

Español después de la version en inglés Version francaise en bas du mail ********************* Dear All, On behalf of Joanna Kulesza and Alfredo Calderon, Co-Chairs of the ATLAS III Capacity Building Sub Group, we would like to invite you to join the second webinars of the mandatory ATLAS III Webinars<https://community.icann.org/x/wh1IBg>: Introduction to the GNSO, which will be held in English with French and Spanish interpretation. The trainers are: Session 1 on Tuesday: either Steve Chan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> or Caitlin Tubergen [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> Session 2 on Thursday: Marika Konings [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> The replicated webinars are scheduled on: 1. Tuesday 30 April at 21:00 UTC – for other times: https://tinyurl.com/yysohbo8 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yysohbo8&d…> * Presenters: Steve Chan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> * Call details: https://community.icann.org/x/x4OGBg * Zoom:Join URL: https://icann.zoom.us/j/507967406 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_507967…> 1. Thursday 02 May at 12:00 UTC – for other times: https://tinyurl.com/y3os2btg [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y3os2btg&d…> * Presenter: Marika Konings [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> * Call details: https://community.icann.org/x/1IOGBg * Zoom: Join URL: https://icann.zoom.us/j/557921180 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_557921…> To meet the attendance requirements for ATLAS III, participants must join the ZOOM Room (as well as the ADIGO Bridge for French or Spanish) no more than 10 minutes after the scheduled start time. If you join later, your participation will not be valid for ATLAS III Criteria. (note Application Guidelines<https://community.icann.org/x/cgB1Bg> under ATLAS III Prep Courses). ALL English speakers are able to take the ICANN Learn courses instead. Conference IDs: EN: 1638 ES: 1738 FR: 1838 If you require a dial-out, please contact At-Large Staff at staff(a)atlarge.icann.org<applewebdata://7A10FE21-3394-495B-A5F0-7E30855046D9/staff@atlarge.icann.org> (do not reply to all) with: * language channel * your preferred telephone number. Thank you. Kind regards, ******************* Queridos todos, En nombre de Joanna Kulesza y Alfredo Calderón, Copresidentes del Subgrupo de Desarrollo de Capacidades de ATLAS III, nos gustaría invitarlos a participar en el segundos seminarios web de los seminarios web obligatorios de ATLAS III: Introducción a la GNSO que se celebrarán en inglés y la interpretación en español y en francés. Los presentadores estaràn: - Session uno el martes: Steve Chan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> - Session dos el jueves: Marika Konings [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> Los webinars replicados están programados en: 1. Martes 30 de abril a las 21:00 UTC - para otros horarios: https://tinyurl.com/yysohbo8 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yysohbo8&d…> 1. Presentadores: Steve Chan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> or Caitlin Tubergen [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> 2. Detalles de la llamada: https://community.icann.org/x/x4OGBg 3. Zoom URL: https://icann.zoom.us/j/507967406 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_507967…> 1. Jueves 02 de mayo a las 12:00 UTC, para otros horarios: https://tinyurl.com/y3os2btg [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y3os2btg&d…> * Presentadores: Marika Konings [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> * Detalles de la llamada: https://community.icann.org/x/1IOGBg * Zoom URL: https://icann.zoom.us/j/557921180 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_557921…> Para cumplir con los requisitos de asistencia para ATLAS III, los participantes deben unirse tanto a Adigo Bridge (para audio español o frances) como a ZOOM Room (audio en ingles) no más de 10 minutos después de la hora de inicio programada. (tome nota de las Pautas de aplicación<https://community.icann.org/x/cgB1Bg> bajo los cursos de preparación ATLAS III). Si se une más tarde, su participación no será válida para los criterios de ATLAS III. ID de conferencia para ADIGO Audio EN: 1638 ES: 1738 FR: 1838 Si necesita una llamada de salida, comuníquese con el personal de At-Large en staff(a)atlarge.icann.org (no responda a todos) con: * canal de idioma * Su número de teléfono preferido. Gracias. Saludos cordiales, ******************* Chers tous, Au nom de Joanna Kulesza et Alfredo Calderon, co-présidents du sous-groupe de renforcement des capacités d'ATLAS III, nous vous invitons à participer au deuxiemes webinaires des webinaires obligatoires d'ATLAS III: Introduction au GNSO, qui se dérouleront en anglais avec interpretation en français et espagnol. Les présentateurs seront: - Session un le mardi: Steve Chan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> - Session deux le jeudi: Marika Konings [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_profiles…> Les webinaires répliqués sont programmés: 1. Mardi 29 avril à 21h00 UTC - pour les autres heures: https://tinyurl.com/yysohbo8 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yysohbo8&d…> * Détails de l'appel: https://community.icann.org/x/x4OGBg * Zoom URL: https://icann.zoom.us/j/507967406 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_507967…> 1. Jeudi 02 mai à 12h00 UTC - pour les autres heures: https://tinyurl.com/y3os2btg [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y3os2btg&d…> * Détails de l'appel: https://community.icann.org/x/1IOGBg * Zoom URL: https://icann.zoom.us/j/557921180 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_557921…> * Pour répondre aux critères de participation à ATLAS III, les participants doivent se joinder à la sale ZOOM (qui sera en ANGLAIS) et pour l’audio en francais, IMPERATIVEMENT se joindre au canal francais sur l’audio ADIGO et ceci au plus tard 10 minutes après l'heure de début prévue. Si vous vous connectez apres les 10 première minutes, votre participation ne sera pas validée selon les critères de participation pour l’ATLAS III (notez les directives d’application<https://community.icann.org/x/cgB1Bg> dans les cours de préparation au ATLAS III) ID de conference pour l’Audio ADIGO EN: 1638 ES: 1738 FR: 1838 Si vous avez besoin qu’une opératrice vous connecte, veuillez contacter le personnel At-Large à staff(a)atlarge.icann.org (ne pas répondre à tous) avec: * Langue * Votre numéro de téléphone préféré. Nous vous en remercions. Cordialement, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

PLEASE READ: Transitioning to Zoom
by ICANN At-Large Staff May 1, 2019

May 1, 2019

Español después de la version en inglés Version francaise en bas du mail Dear All, As you may already know [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>, ICANN is replacing the Adobe Connect tool with Zoom. As with all transitions, there will be a learning curve for community members as well as for staff. However, through the tools, information and proposed next steps outlined below, we hope we can make this transition as smooth as possible. The complete roll out is expected to be finalized by ICANN65, Marrakech, however many groups will be noticing their calls scheduled on Zoom as of next week. Please see below a few pointers which we hope will help as we transition to Zoom. How is staff preparing for the transition? * Staff have received training and viewed training videos as well as have had the opportunity to complete practice runs in Zoom rooms. We are confident that this will facilitate our assistance with the At-Large community as we transition to Zoom. What is available to the community to prepare for the transition? * Staff will present Zoom to community members at the beginning of each conference call to ensure all At-Large participants understand the different functions of Zoom and how to use them. Staff will open the Zoom room 30min prior to the start of the call so please feel free to join early to familiarise yourself with new tool! * The attached Welcome to Zoom! document will be presented at the same time. As usual, At-Large support staff will be present during each call to assist. What stays the same? (please open the Welcome to Zoom! document for a visual) * Zoom rooms still show participant and chat pods. The public chat pods will be archived and circulated as per usual, the private chat content remains inaccessible to ICANN Org staff. * Documents can still be viewed in the Zoom room but please note that this sharing is a screen share which means it is no longer possible to scroll through documents unless the person who is sharing their screen does so. At-Large support staff will work with presenters to ensure their documents are displayed when requested. * It is possible to join the audio via Adigo audio bridge (telephone) or via the computer. Zoom VoIP quality is excellent. * It will still be possible to get a dial out for the Adigo audio bridge for those unable to connect to the Zoom room. What changes? (please open the Welcome to Zoom! And the FAQ documents) * Participants will need to click on the participant list and the chat to activate them. This just takes two seconds. * Please note, the content of the chat ONLY appears from participant connection time. This means that if you joins 4 mins late, you will not be able to access the first 4 mins of the chat. Zoom is notified of this and is looking into resolving the issue. The entire content of the chat transcript will however be available immediately after the end of the call, once it gets posted on the relevant wiki page. * Documents will be able to be shared via the chat to allow all to download materials to their computers during the call. * The mobile app does not require you to remain in the app in order to hear the zoom room audio. * Action Items will be noted on the “Closed Caption” pod. Please open the attached FAQ document for any additional queries you may have. If you have any comments, questions or suggestions, please let us know – our objective is to make sure this transition is as smooth as possible. Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> **************************** Queridos todos, Como ya sabrá [icann.org] ICANN está reemplazando la herramienta Adobe Connect con Zoom. Al igual que con todas las transiciones, habrá una curva de aprendizaje para los miembros de la comunidad, así como para el personal. Sin embargo, a través de las herramientas, la información y los próximos pasos que se describen a continuación, esperamos que podamos hacer esta transición lo más fácil posible. Se espera que el lanzamiento completo sea finalizado por ICANN65, Marrakech, sin embargo, muchos grupos notarán sus llamadas programadas en Zoom a partir de la próxima semana. Por favor, vea a continuación algunos consejos que esperamos que ayuden mientras hacemos la transición a Zoom. ¿Cómo se está preparando el personal para la transición? • El personal ha recibido capacitación y visto videos de capacitación, así como la oportunidad de completar sesiones de práctica en las salas Zoom. Estamos seguros de que esto facilitará nuestra asistencia con la comunidad de At-Large en la transición a Zoom. ¿Qué hay disponible para que la comunidad se prepare para la transición? • El personal presentará a los miembros de la comunidad Zoom al comienzo de cada llamada de conferencia para garantizar que todos los participantes de At-Large comprendan las diferentes funciones de Zoom y cómo usarlas. El personal abrirá la sala Zoom 30 minutos antes del inicio de la llamada, así que no dude en unirse pronto para familiarizarse con la nueva herramienta. • El adjunto Bienvenido a Zoom! El documento será presentado al mismo tiempo. Como de costumbre, el personal de soporte de At-Large estará presente durante cada llamada para ayudarlo. ¿Qué permanece igual? (Por favor, abra el documento ¡Bienvenido a Zoom! para una visualización) • Las salas de zoom todavía muestran las pods de participantes y chat. Los pods de chat públicos se archivarán y circularán como de costumbre, el contenido del chat privado sigue siendo inaccesible para el personal de la organización de la ICANN. • Los documentos aún se pueden ver en la sala de Zoom, pero tenga en cuenta que esta compartición es una pantalla compartida, lo que significa que ya no es posible desplazarse por los documentos a menos que la persona que comparte su pantalla lo haga. El personal de soporte de At-Large trabajará con los presentadores para garantizar que sus documentos se muestren cuando se soliciten. • Es posible unir el audio a través del puente de audio Adigo (teléfono) o a través de la computadora. La calidad del zoom VoIP es excelente. • Todavía será posible obtener una marcación para el puente de audio de Adigo para aquellos que no puedan conectarse a la sala de Zoom. ¿Que cambios? (por favor, abra la bienvenida a Zoom! y los documentos de preguntas frecuentes) • Los participantes deberán hacer clic en la lista de participantes y en el chat para activarlos. Esto sólo lleva dos segundos. • Tenga en cuenta que el contenido del chat SOLO aparece desde el tiempo de conexión del participante. Esto significa que si se une 4 minutos tarde, no podrá acceder a los primeros 4 minutos del chat. Se notifica a Zoom de esto y está buscando resolver el problema. Sin embargo, todo el contenido de la transcripción del chat estará disponible inmediatamente después del final de la llamada, una vez que se publique en la página wiki correspondiente. • Los documentos se podrán compartir a través del chat para permitir que todos descarguen materiales a sus computadoras durante la llamada. • La aplicación móvil no requiere que permanezca en la aplicación para escuchar el audio de la sala de zoom. • Los elementos de acción se anotarán en el pod «Closed Caption». Abra el documento de Preguntas Frecuentes adjunto para cualquier consulta adicional que pueda tener. Si tiene algún comentario, pregunta o sugerencia, háganoslo saber. Nuestro objetivo es asegurarnos de que esta transición sea lo más fácil posible. Gracias. Saludos cordiales, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> ************************** Chers tous, Comme vous le savez peut-être déjà [icann.org] l'ICANN remplace l'outil Adobe Connect par Zoom. Comme pour toutes les transitions, il y aura une courbe d'apprentissage pour les membres de la communauté ainsi que pour le personnel. Cependant, grâce aux outils, aux informations et aux prochaines étapes proposées décrites ci-dessous, nous espérons pouvoir effectuer cette transition le plus facilement possible. Le déploiement complet devrait être finalisé par ICANN65 à Marrakech. Vous verrez cette transition des a present. Veuillez trouver ci-dessous quelques indications qui, nous l’espérons, nous aideront dans notre transition vers Zoom. Comment le personnel se prépare-t-il pour la transition? • Les membres du personnel ont reçu une formation et visionné des vidéos de formation et ont également eu la possibilité d'effectuer des exercices pratiques dans les salles Zoom. Nous sommes convaincus que cela facilitera notre assistance à la communauté At-Large lors de la transition vers Zoom. De quoi dispose la communauté pour se préparer à la transition? • Le personnel présentera Zoom aux membres de la communauté au début de chaque téléconférence pour s’assurer que tous les participants At-Large comprennent les différentes fonctions de Zoom et comment les utiliser. Les salles Zoom seront ouvertes 30 minutes avant le début de la téléconference. N'hésitez donc pas à vous joindre plus tôt afin de vous familiariser avec l’outil et poser des questions. • La pièce jointe “Bienvenue à Zoom! “ sera présenté en même temps. Comme d'habitude, le personnel de soutien d'At-Large sera présent à chaque appel. Qu'est-ce qui reste pareil? (veuillez ouvrir le document Bienvenue dans Zoom! pour un visuel) • Les salles de zoom affichent toujours les modules des participant et les discussion. Les modules de discussion publics seront archivés et distribués comme d'habitude, le contenu de la discussion privée reste inaccessible au personnel de l'ICANN Org. • Les documents peuvent toujours être consultés dans la salle Zoom, mais veuillez noter que ce partage est un partage d'écran, ce qui signifie qu'il n'est plus possible de faire défiler les documents à moins que la personne qui partage l'écran ne le fasse. Le personnel At-Large travaillera avec les présentateurs pour s'assurer que leurs documents soient affichés sur demande. • Il est possible de se joinder soit sur l’audio Adigo (téléphone) ou via l'ordinateur. La qualité VoIP sur Zoom est excellente. • Il sera toujours possible de se joinder à l’audio Adigo pour ceux qui ne peuvent pas se connecter à la salle Zoom. Quels changements? (merci d’ouvrir le “Bienvenue à Zoom!” et les documents de la FAQ) • Les participants devront cliquer sur la liste des participants et sur le chat pour les activer. Cela prend juste deux secondes. • Veuillez noter que le contenu du chat apparaît UNIQUEMENT à partir du moment de la connexion du participant. Cela signifie que si vous vous joignez avec 4 minutes de retard, vous ne pourrez pas accéder aux 4 premières minutes du chat. Zoom en est informé et étudie la possibilité de résoudre le problème. L'intégralité du contenu de la transcription du chat sera toutefois disponible immédiatement après la fin de l'appel, une fois qu'il aura été posté sur la page wiki correspondante. • Les documents pourront être partagés via le chat pour permettre à tous de télécharger des documents sur leur ordinateur pendant l'appel. • L'application mobile ne vous oblige pas à rester dans l'application pour pouvoir écouter le son de la salle zoom. • Les actions à entreprendre (Action Items) seront notées dans le module «Closed Caption». Veuillez ouvrir le document FAQ ci-joint pour toute question supplémentaire. Si vous avez des commentaires, des questions ou des suggestions, merci de nous le faire savoir - notre objectif est de nous assurer que cette transition se déroule dans les meilleures conditions. Nous vous en remercions. Cordialement, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

3 2

Fwd: [arin-announce] Apply Now for NEW ARIN Community Grant Program
by Alfredo Calderon May 1, 2019

May 1, 2019

FYI. Please share. > > Alfredo Calderon > eLearning Consultant > calderon.alfredo(a)gmail.com |http://aprendizajedistancia.blogspot.com | Skype: Alfredo_1212| wiseintro.co/alfredocalderon > > > > > > > > > Get your own email signature > Begin forwarded message: > From: ARIN <info(a)arin.net> > Date: May 1, 2019 at 10:38:42 AM AST > To: arin-announce(a)arin.net > Subject: [arin-announce] Apply Now for NEW ARIN Community Grant Program > > We are pleased to announce a new ARIN Community Grant Program that provides financial grants to support projects that advance ARIN’s mission and benefit the Internet community within the ARIN region. > > For 2019, the ARIN Board of Trustees has approved a total expenditure of up to $60,000 (USD) for grants of varying amounts, starting at $1,000 (USD) and based on project need. > > Projects must fit into one or more of these broad categories: > > - Internet technical improvements: Promotes and facilitates the expansion, development, and growth of the infrastructure of the Internet consistent with the public interest > - Registry processes & technology improvements: Help maintain a globally consistent and highly usable Internet number registry system > - Informational outreach: Advances the Internet by covering topics such as, but not limited to: IPv6 deployment, Internet research, and Internet governance > > We invite you to learn more about ARIN’s new Community Grant Program at: > > https://www.arin.net/about/community_grants/program/ > > Grant applications will be accepted 1 May – 11 June 2019. A link to the application is available on the webpage. > > Regards, > > Communications and Member Services > American Registry for Internet Numbers (ARIN)

1 0

Meeting invitation: NARALO Monthly call on Monday, 13 May 2019 at 19:00 UTC
by ICANN At-Large Staff May 1, 2019

May 1, 2019

******We will not be using Adobe Connect anymore, we will be using Zoom, please see link below***** If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number.  Dear All, The next NARALO Monthly Call is scheduled for Monday, 13 M ay 2019 at 19:00 UTC. For other times: https://tinyurl.com/y66bghaf The agenda and call details can be found at: https://community.icann.org/x/YoaGBg ADIGO Conference Bridge: EN 1638 Toll-free access number (US and Canada): 800 550 6865 Other tollfree numbers: http://adigo.com/icann/ ZOOM ROOM: https://icann.zoom.us/j/766172151 NARALO Wiki Space: https://community.icann.org/x/N5Qi If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<applewebdata://D0C9D8AD-F5F9-47D1-8000-12B5977AB503/staff@atlarge.icann.org> Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/@ICANNAtLarge>

1 0

NARALO Monthly Call
by ICANN Policy Calendar May 1, 2019

May 1, 2019

******We will not be using Adobe Connect anymore - we will now be using Zoom, see link below***** If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number.? Dear All, The next NARALO Monthly Call is scheduled for Monday, 13 May 2019 at 19:00 UTC. For other times: https://tinyurl.com/y66bghaf The agenda and call details can be found at: https://community.icann.org/x/YoaGBg ADIGO Conference Bridge: EN 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll free numbers: http://adigo.com/icann/ ZOOM ROOM: https://icann.zoom.us/j/766172151 NARALO Wiki Space: https://community.icann.org/x/N5Qi If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<applewebdata://D0C9D8AD-F5F9-47D1-8000-12B5977AB503/staff@atlarge.icann.org> Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/@ICANNAtLarge>

1 0