From PolicyCalendar at icann.org Mon Sep 2 07:32:56 2024 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 2 Sep 2024 04:32:56 +0000 Subject: [NCSG-PC] NCSG PC Update on Singulars and Plurals Message-ID: Hey All, Please find linked here a zoom invite for a discussion on the supplementary rec on singulars and plurals. https://icann.zoom.us/j/97677430639?pwd=Ofwsbxm4OV3fnbaL3LYszPIZcYiYFE.1 Meeting ID: 976 7743 0639 Passcode(web): pPG4i?Km2m Find your local number: https://icann.zoom.us/u/adjU3M2j65 Passcode(Phone): 4172914347 Thanks, Andrea and Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2815 bytes Desc: not available URL: From Kathy at KathyKleiman.com Tue Sep 3 18:49:35 2024 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Tue, 3 Sep 2024 11:49:35 -0400 Subject: [NCSG-PC] Singular/Plurals - Email [1] in preparation for our NCSG PC meeting tomorrow Message-ID: <3085e2de-1134-4231-b338-bbf99e6824c4@KathyKleiman.com> To our NCSG Councilors, This has been a very difficult summer.? We fought for a fair and balanced creation of exceptions for Singulars and Plurals, and yet almost no one wanted to listen. The only exception everyone on the team wanted to create was one for Brands, and the more Cara and later Rebecca (as our Subject Matter alternates and experts) thought about it, the more dangerous it became. In a few minutes, I'll be able to share the final text of the proposed SubPro Recommendation on Singulars/Plurals. It's still being finalized by Staff based on last wording changes in our final meeting that ended half an hour ago. *But before then, I want to share with you the memo that Professor Rebecca Tushnet (a world expert on international trademark laws and free speech and expression laws and protections), about our utter frustration that few in the Small Team cared about the real and genuine problems of the proposed .BRAND Exceptions.? Almost no one cared about the far higher integrity and credibility of Noncommercial and Non-Profit organizations in their applications for new gTLDs. * History: We (NCSG and NCUC before NCSG existed) fought this battle at second level and now at the top level.? Trademark owners /do not have a better right to words than we do -- /in fact under traditional trademark laws and balances, noncommercial uses of organization and individuals are protection, for example, as our names (Wendy & McDonald), for descriptions of our activities like baseball, art, and poetry - and for our criticisms, concerns, and arguments.? Words like liberty and freedom are also gas stations and blood glucose monitors! In preparation for our meeting tomorrow, I share our final memo to the Small Team after weeks of seeking support for an equal and equivalent exception for noncommercial and non-profit organizations.? We have to share that we felt very beaten up in this process - it was not fun.? A lot of power was given in this experimental Small Team and many people served as active and unwavering advocates for their clients. That said, Paul McGrady did a good and fair job as Chair. He worked very hard to make sure all voices were heard, including ours. Best, Kathy ------------------------------------- Hi All [SubPro Small Team Plus], Please put away the knives and sheath the spears? We are coming in to support Kurt?s concerns and proposals: /?I think it is much better to take a conservative approach for this round and seek to avoid user confusion to the extent possible and eliminate exceptions at this point. I also believe we should deliver to ICANN an implementable policy that will avoid vagueness and litigation, i.e., creating policy that facilitates the implementation of a smooth running process. This is incredibly important for the reputation of the multi-stakeholder model.?Kurt, 4 Aug./ Efficiency, clarity, fairness. It?s not a perfect solution to consumer confusion since we know that .MOBIL can coexist and with .MOBILE and .MOBI and .NEW and .NEWS, but it is clear and understandable to everyone coming into the process.Yes, it favors incumbents, but it serves the overall goals of the SubPro Working Group: /?Specifically, the Working Group recommends prohibiting plurals and singulars of the same word within the same language/script in order to reduce the risk of consumer confusion.?/ In the current exceptions language, now added to our many Strawmen, we have strayed from any anchor point to the SubPro Small Team recommendation language.We are no longer evaluating new gTLDs against each other for meaning, or for confusion. We seem to have left these ideas completely behind. [1] /We cannot support rules that allow a trademark, from anywhere in the world, registered in the Trademark Clearinghouse and used for a .BRAND application, to get a complete ?pass? from all evaluation and examination of meaning ? that is a clear formula for consumer confusion./ Further, the current language and many prior Strawmen are premised on assumptions that are not fair or valid, including that the rest of the world will use ?generic words? for their new gTLDs. But that is not the case. Organizations, companies and individuals around the world will apply for the gTLD strings that are the most meaningful to them ? some will be fanciful, some will be arbitrary as applied to their activities, some will be descriptive, and some will be generic. There is no reason that trademarks should take priority over everyone else?s applications for new gTLD strings. /If we don?t evaluate the meaning of all gTLD strings identified in as Singulars or Plurals of other applications or existing gTLDs in a clear and transparent way, and if we don?t have fair and balanced exceptions that equally support legitimate noncommercial and commercial use,/ /then we must revert to Kurt?s language./ As long as the gTLDs are the same word, in the same language, in some legitimate dictionary, we should put them into a contention set. This is a clear and efficient way to avoid the risk of consumer confusion over the gTLDs. We are happy to explain further. _There is nothing magical about trademarks._ We oppose the exceptions language for five reasons and can certainly provide more: 1)It assumes a high standard of review for trademarks, and that is not true internationally. Trademarks in many countries are granted without ?use? requirements. The Trademark Clearinghouse (TMCH) must accept marks from every country, and although it requires a showing of use, the showing is de minimis. As long as the product or service appears somewhere on the website, even in a footer, the .BRAND requirements are satisfied. The Rights Protection Mechanisms PDP Working Group found a pattern of registration in the Trademark Clearinghouse that shows trademark owners in Switzerland actively using their TMCH registrations to ?game the system? to gain early access to valuable domain names in Sunrise. The stakes for gaming in the TMCH will be much higher when someone can get an automatic pass out of a contention set for a Singular/Plural gTLD. 2)It assumes that the trademark owners have better rights to new gTLDs than other applicants, and that is certainly not the case. *Every Applicant for a New gTLD, and especially those coming from the Global South, tribes and indigenous peoples, non-profits and civil society ? groups that ICANN will go to great lengths to recruit to the New gTLD program and to help through the application process ? should have the same right and opportunity to a new gTLD string.*Just because there is a trademark for the word ?rotary? does not mean that the .BRAND owner should prevail in a grouping of applications for .rotary and .rotaries by Rotary International and a group posting on the research of traffic circles (.rotaries) around the world. *New gTLDs are important and central to each and every applicant.* 3)It does not protect Sensitive Strings, and we need to. The GAC has told us that certain gTLDs are important to *Consumer Protection and Regulated Markets, *as /?These strings are likely to invoke a level of implied trust from consumers, and carry higher levels of risk associated with consumer harm.?/ *We respect this GAC Consensus Advice and urge a wall be built around the Sensitive String they identified for us.No Singular/Plurals of these words should be allowed: * /Children: .kid, .kids, .kinder, .game, .games, .juegos, .play, .school, .schule, .toys; Environmental: .earth, .eco, .green, .bio, .organic; Health and Fitness: .care, .diet, .fit, .fitness, .health, .healthcare, .heart, .hiv, .hospital,, .med, .medical, .organic, .pharmacy, .rehab, .surgery, .clinic, .healthy (IDN Chinese equivalent), .dental, .dentist .doctor, .dds, .physio; Financial:capital, . cash, .cashbackbonus, .broker, .brokers, .claims, .exchange, .finance, .financial, .fianancialaid, .forex, .fund, .investments, .lease, .loan, .loans, .market, . markets, .money, .pay, .payu, .retirement, .save, .trading, .autoinsurance, .bank, .banque, .carinsurance, .credit, .creditcard, .creditunion,.insurance, .insure, ira, .lifeinsurance, .mortgage, .mutualfunds, .mutuelle, .netbank, .reit, .tax, .travelersinsurance, .vermogensberater, .vermogensberatung and .vesicherung. Gambling: .bet, .bingo, .lotto, .poker, and .spreadbetting, .casino; Charity: .care, .gives, .giving, .charity; Education: degree, .mba, .university; Intellectual Property.audio, .book (and IDN equivalent), .broadway, .film, .game, .games, .juegos, .movie, .music, .software, .song, .tunes, .fashion (and IDN equivalent), .video, .app, .art, .author, .band, .beats, .cloud (and IDN equivalent), .data, .design, .digital, .download, .entertainment, .fan, .fans, .free, .gratis, .discount, .sale, .hiphop, .media, .news, .online, .pictures, .radio, .rip, .show, .theater, .theatre, .tour, .tours, .tvs, .video, .zip;Professional Services: .abogado, .accountant, .accountants, .architect, .associates, .attorney, .broker, .brokers, .cpa, .doctor, .dentist, .dds, .engineer, .lawyer, .legal, .realtor, .realty, .vet; Corporate Identifiers: .corp, .gmbh, .inc, .limited, .llc, .llp, .ltda, .ltd, .sarl, .srl, .sal; Generic Geographic Terms: .town, .city, .capital; .reise, .reisen; .weather; .engineering; .law; Inherently Governmental Functions .army, .navy, .airforce.Beijing Communique, ICANN46/ *Currently there is no protection for these strings and plural/singular gTLDs will be allowed, including .BRAND exceptions ? and lead to consumer confusion. * 4) It assumes that all .BRAND Registries will monitor their licensees closely, and that is not the case. There is no assurance that all .BRAND Registry Operators will closely oversee their affiliates and trademark licensees once they register domain names. The only requirement is that a user licensed by the .BRAND must also possess a trademark license, which can be incorporated into the .BRAND agreement. But, while trademark licenses in the US and some other countries require quality control, this type of oversight is not required in many parts of the world and not needed to maintain a trademark: ?The majority of countries (roughly 2/3) don?t require quality control in licenses. (Mary M. Squyres and Nanette Norton, Trademark Practice Throughout the World | September 2023 Update Appendix 23(G)). ??European trademark law does not require the licensor to exercise control over the use of the trademark in order to ensure the quality of the goods or services in question.??(Anne Lauber-R?nsberg, in The Commercial Exploitation Of Personality Features In Germany From The Personality Rights And Trademark Perspectives, 107 Trademark Rep. 803, 843 (2017)). ?In Germany and France, ?there is no concern for preserving the source function of trademarks by means of the provision and exercise of quality control.? (Neil Wilkof, in Trademark licensing: the once and future narrative, in Research Handbook on Intellectual Property Licensing 216 (2013)). ?The European Court of Justice held in 2017 that failure to monitor licensees doesn?t invalidate a registration, though the mark can be cancelled if its use was deceptive. (W.F. G?zze Frottierweberei Gmbh, Wolfgang G?zze GmbH v Verein Bremer Baumwollb?rse, case C-689/15, _https://perma.cc/554Z-8TYD_). If many countries do not require oversight of trademark licensees and such oversight can be lax or non-existent, then without more, we have no assurance of close oversight domain names by their affiliates and licensees around the world. 5) The remedies that our Small Team have discussed for termination of a .BRAND that receives a Singular/Plural exemption are not consistent with Specification 13. Jeff and Susan reasonably proposed the remedy of termination for a .BRAND receiving a Singular/Plurals exemption, and then ceasing to operate as a .BRAND: /?If at any time ICANN reasonably determines that the TLD no longer qualifies as a .Brand TLD, Registry Operator shall be considered in material breach of the Registry Agreement.? If the .Brand TLD is unable or unwilling to cure such breach, ICANN shall have the right to terminate the Registry Agreement.?/We do not disagree. *But Specification 13 dictates a different outcome. If a .BRAND cease to operate as a .BRAND then it becomes an open gTLD. //*/Spec 13: ?//If at any time ICANN determines, in its reasonable discretion, that the TLD no longer qualifies as a .Brand TLD, ? then (i) the TLD shall immediately cease to be a .Brand TLD, (ii) Registry Operator shall immediately comply with the provisions of the Agreement as no longer modified by this Specification 13 (other than Section 2 hereof) and (iii) the provisions of this Specification 13 (other than Section 2 hereof) shall thereafter no longer have any effect.?/ Truly such a change would immeasurably complicate consumer confusion issues, and be fundamentally unfair to all who did not receive their new gTLDs in the exemption process. _If we really wanted a fair and balanced exception, we would have had one by now._ In this incredibly talented group of Small Team members, if we had wanted a fair and balanced exception, we would have found it weeks ago. /Early on, we talked about the high standard we wanted for those receiving exceptions and that, consistent with the policies of ICANN, exceptions should be fair and balanced./ But that is not what has happened. *Non-profits and Civil Society organizations are at least as driven to monitor who receives their domain names as any .BRAND applicant.* The motivation for Non-profits and Civil Society diligence comes from their special status with their governments, their communities, their donors, and the people at the local, national and international level who benefit from their services. *Their reputations, and therefore their existences, are intricately bound to serving their missions.* *As a trademark owner can bind their affiliates and licensees who receive domain names, Non-profits and Civil Society clearly delineate their eligible registrants, based on specific, objective eligibility criteria and enforceable mechanisms in Registry Voluntary Commitments that are strong and binding. * ----------------------- */A parallel exception would have been very fair and easy for us to accept:/* Exception: 1. in the event that an entity applies for a string that is either the plural or singular of an existing string in any language, that entity?s application shall be allowed to proceed through the application process and be delegated provided that it meets the criteria for a Non-Profit and Civil Society Organization pursuant to the presented and signed Registry Voluntary Commitment. 2. If at any time ICANN reasonably determines that the TLD no longer operates pursuant to its commitments in the RVC, then Registry Operator shall be considered in material breach of the Registry Agreement.? If the Non-Profit or Civil Society TLD is unable or unwilling to cure such breach, ICANN shall have the right to terminate the Registry Agreement. _____________________ _Defining Non-profit and Civil Society gTLDs_ Non-profit and Civil Society gTLDs: 1.A non-profit or civil society gTLD meets the general definition of a civil society organization under the UN, namely: Non-State, not-for-profit, voluntary entities formed by people in the social sphere that are separate from the State and the market. Civil society groups are?community-based organizations as well as non-governmental organizations (NGOs).?) 2.Methods of verification, to be provided to ICANN, include: 1. Certification as a non-profit or civil society organization under the laws of the country in which the organization is registered; or 2. Confirmation of equivalence determination by a reputable group, e.g. TechSoup (making?a good-faith determination that a non-U.S. organization is equivalent to a U.S. public charity); or 3. Recognition by an international organization such as the United Nations. iii.The Applicant must document that it has been in continuous existence for over a year prior to the filing of its TLD registry application with ICANN. iv.The TLD string should be a key term or identifier that the organization associates with itself and its mission. v.It should be owned and used continuously by the Registry Operator or its Affiliates in connection with the Registry Operator?s or its Affiliates? offering of their non-profit/civil society services. Such services shall not include services related to the provision of TLD Registry Services. vi.only Registry Operator, its Affiliates or members in good standing are registrants of domain names in the TLD and control the DNS records associated with domain names at any level in the TLD; vii.the TLD is not a Generic String TLD (as defined in Specification 11). But our Small Team could not do that. _In closing, we note there is another new idea floating around the Small Team that ICANN cannot look at the meaning of the words in gTLDs, and that cannot be right or accurate._ NCSG was very involved in the call for ICANN to not allow content to be placed in Registry Voluntary Commitments, including the type of content that would require ICANN to monitor the text, videos and pictures placed on websites. *But that does not mean that ICANN can never again look at the meaning of the word or the purpose of a word in a gTLD. That would invalidate much of ICANN?s mission and purpose. * ICANN?s mission is and remains: /Section 1.1. MISSION/ /(a) The mission of the Internet Corporation for Assigned Names and Numbers ("ICANN") is to ensure the stable and secure operation of the Internet's unique identifier systems as described in this Section 1.1(a) (the "Mission"). Specifically, ICANN:/ /(i) Coordinates the allocation and assignment of names in the root zone of the Domain Name System ("DNS") and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains ("gTLDs"). In this role, ICANN's scope is to coordinate the development and implementation of policies:/ /For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and/ /That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet's unique names systems./ ---------- *The limits of Bylaws 1.1 sections (b) and (c), include not imposing rules on the content that domain names carry and provide, but does not stop ICANN from looking closely at top level and second level domain names. * *Saying otherwise would eliminate the URS and UDRP. * The basis of the UDRP and URS /is looking at the meaning of the second level domain name, who has registered it and how they are using it. /Although ICANN has delegated the authority for the review and decision, the URDP and URS decisions are enforced by ICANN under its Registry Agreements and Registrar Accreditation Agreements. This is ICANN?s responsibility. *Similarly at the top level, ICANN must examine the nature of the applicant, who they are, and how they intend to use the applied-for gTLD. ICANN will review comments from the Community on these same issues. This is part and parcel of the application process. * Three objection processes are based on these same substantive factors: String Confusion, Community and Legal Rights objections. All decided via delegated authority from ICANN and all enforced by ICANN. Even reviewing a .BRAND application to see, among other things, if it is a generic word involves ICANN looking closely at the Applicant, the New gTLD, and its meaning. It?s all consistent with a much wider range of exemptions, for Non-profits and Civil Society as well as .BRANDs, that we could have created had we chosen to do so. ----------------------------------- As shared above, we have come to support Kurt?s concerns and proposals: /?I think it is much better to take a conservative approach for this round and seek to avoid user confusion to the extent possible and eliminate exceptions at this point. I also believe we should deliver to ICANN an implementable policy that will avoid vagueness and litigation, i.e., creating policy that facilitates the implementation of a smooth running process. This is incredibly important for the reputation of the multi-stakeholder model.?Kurt, 4 Aug./ It?s not a perfect solution, but it is efficient, clear and fair. Kathy and Rebecca [1] https://docs.google.com/document/d/13VIPAxR5OYAzgTvSiaWCBTzYT0siLC2mpt-1Tm3JxTA/edit#heading=h.oc222usgafq2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathy at kathykleiman.com Wed Sep 4 03:09:12 2024 From: kathy at kathykleiman.com (Kathy Kleiman) Date: Tue, 3 Sep 2024 20:09:12 -0400 Subject: [NCSG-PC] Singular/Plurals - Email [2] in preparation for our NCSG PC meeting tomorrow In-Reply-To: <3085e2de-1134-4231-b338-bbf99e6824c4@KathyKleiman.com> References: <3085e2de-1134-4231-b338-bbf99e6824c4@KathyKleiman.com> Message-ID: <5e948fde-8f14-4973-8086-63af6f8c0166@kathykleiman.com> Hi All, In follow-up to my email earlier today, here is the near-final text of the Supplemental Recommendation, as approved by the Subpro Small Team Plus today (and headed back to you in Council soon). Staff is making final tweaks based on the conversation today, and this is 99.99% of the final text.? For our discussion tomorrow! Best, Kathy --------------------- New gTLD Subsequent Procedures Supplemental Recommendations Background On 10 September 2023, the ICANN Board resolved (see scorecard) to not adopt select recommendations from amongst five topics contained in the New gTLD Subsequent Procedures Final Report. On 26 October 2023, the ICANN Board resolved (see scorecard) to not adopt recommendations related to one additional topic. As indicated in the ICANN Bylaws, the Council, ?shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for the then-current recommendation.? The GNSO Council convened the Small Team Plus in April 2024 to draft Supplemental Recommendation(s) to address the Board?s concerns with the non-adopted New gTLD Subsequent Procedures (SubPro) PDP recommendation on Topic 24: String Similarity Evaluations.See the _motion _.In particular, ?[t[he Board remains concerned, as previously voiced as part of its comment on the Draft Final Report, over the wording in section (a) and (c) of this Recommendation as they stipulate ?intended use? of a gTLD, which implies that ICANN will have to enforce the ?intended use? post delegation, which could be challenged as acting outside its mission.? Herein contained are the GNSO Council?s conclusions related to recommendations not adopted by the ICANN Board. Supplemental Recommendations Topic 24: String Similarity Evaluations Supplemental Recommendation Supplemental Recommendation 24.3: The GNSO Council recommends prohibiting the delegation of singulars and plurals of the same word in the same language in order to reduce the risk of end user confusion. This prohibition applies in two distinct situations: 1) where an applied-for gTLD string is a singular or plural of an existing gTLD or those Blocked Names on Annex A[1] <#_msocom_1>and 2) where an applied-for gTLD[2] <#_msocom_2>string is a singular or plural of another applied-for gTLD string: 1)If ICANN org is informed[3] <#_msocom_3>, and verifies by reference to a dictionary[4] <#_msocom_4>, that an application for a string that is the singular or plural version of the same word in the same language during the same application window, of an existing gTLD or Blocked Name^^[1] <#_ftn1>has been submitted, such application will not be permitted to proceed. For the avoidance of doubt, this does not include names other than those on the list in Annex A.[5] <#_msocom_5>[6] <#_msocom_6>[7] <#_msocom_7>[8] <#_msocom_8>ICANN org will treat all other applications for the same strings in the same manner . 2)If ICANN org is informed, and verifies by reference to a dictionary, that there is an application for the singular version of a word and an application for a plural version of the same word in the same language during the same application window, the relevant applications will be placed in a contention set.ICANN org will treat all other applications for the same string[9] <#_msocom_9>s[10] <#_msocom_10>in the same manner. *Explanation for Recommendation* The GNSO Council sought to address the concerns of the ICANN Board by making the following amendments to the original recommendation. To assist in addressing the Board?s concerns, ICANN org developed a proposed text which provided a reporting mechanism for singulars and plurals of the same word in the same language but did not contain any exceptions. The Small Team Plus began with deliberation on this proposal and spent considerable time discussing various exception details, such as exceptions for trademark owners using Specification 13 for .brands and exceptions for non-profit and civil society organizations using registry voluntary commitments. After extensive deliberations, including suggesting that an evaluation for non-confusion could include an ?intended registrant? or "eligible registrant? instead of the problematic ?intended use?, the Small Team Plus agreed that it could not agree on the details of any exceptions process and instead chose to recommend to the GNSO Council that there should be no exceptions. The GNSO Council recommends to prohibit new delegations of gTLDs consisting of singulars and plurals of the same word in the same language without exceptions[11] <#_msocom_11>. Nothing in this Supplemental Recommendation is meant to have any effects upon the rights of pre-existing gTLDs. The Council notes that non-adoption by the Board of this recommendation risks potentially reverting the policy to 2012 practice where singulars and plurals are allowed to coexist and applicants may use the string confusion[12] <#_msocom_12>objection process if concerned about consumer confusion[13] <#_msocom_13>.** *Minority Statement: * *Two members *have significant reservations regarding the majority Supplemental Recommendation. The Recommendation is overly broad. Such a broad approach is not consistent with the principles of (1) Applicant Freedom of Expression as confirmed by the Sub Pro Final Report, (2) promotion of competition, or with (3)Recommendation 24.3 from Sub Pro which was intended to moderate the effect of the proposed prohibition. The Small Team Plus worked hard to develop a Supplemental Recommendation based on verification of objective criteria substantiating restricted registrant eligibility clearly enforceable by ICANN such as meeting Spec 12 or Spec 13 commitments or licensing or other professional qualifications. These restrictions were viewed as too narrow by some and perhaps too broad by others. Full consensus was not achieved. Accordingly, the minority favors non-adoption of the total ban on singulars and plurals. NCSG Plurality Statement:[14] <#_msocom_14>A different minority [15] <#_msocom_15>had openness to exceptions, but only if they could be fair and balanced. The proponents of a .BRAND exception, however, insisted that no noncommercial exception could be properly bounded to avoid abuse while also maintaining that the requirements for .BRANDS would not pose risks of abuse. This was unbalanced given the minimal restrictions on .BRANDS in practice. Thus, the majority Supplemental Recommendation is superior to special treatment for .BRANDS, although balanced exceptions would have been preferable. Annex A: [16] <#_msocom_16>LIMITED BLOCKED NAMES LIST Top-Level BlockedNames List AFRINICIANA-SERVERSNRO ALACICANNRFC-EDITOR APNICIESGRIPE ARINIETFROOT-SERVERS ASOINTERNICRSSAC CCNSOINVALIDSSAC EXAMPLE*IRTFTEST* GACISTFTLD GNSOLACNICWHOIS GTLD-SERVERSLOCALWWW IABLOCALHOST IANANIC *Note that in addition to the above strings, ICANN will reserve translations of the terms ?test? and ?example? in multiple languages. The remainder of the strings are reserved only in the form included above. In addition, the following names should also be included: ?Per SubPro Affirmation 21.3: ONION ?Per SubPro Recommendation 21.4: PTI ?Per SAC113: INTERNAL ------------------------------------------------------------------------ ^^[1] <#_ftnref1>A ?Blocked Name? (formerly the ?Top-Level Reserved Names List?) as defined in the then-current Applicant Guidebook. ------------------------------------------------------------------------ On 9/3/2024 11:49 AM, Kathy Kleiman wrote: > > To our NCSG Councilors, > > This has been a very difficult summer.? We fought for a fair and > balanced creation of exceptions for Singulars and Plurals, and yet > almost no one wanted to listen. The only exception everyone on the > team wanted to create was one for Brands, and the more Cara and later > Rebecca (as our Subject Matter alternates and experts) thought about > it, the more dangerous it became. > > In a few minutes, I'll be able to share the final text of the proposed > SubPro Recommendation on Singulars/Plurals. It's still being finalized > by Staff based on last wording changes in our final meeting that ended > half an hour ago. > > *But before then, I want to share with you the memo that Professor > Rebecca Tushnet (a world expert on international trademark laws and > free speech and expression laws and protections), about our utter > frustration that few in the Small Team cared about the real and > genuine problems of the proposed .BRAND Exceptions.? Almost no one > cared about the far higher integrity and credibility of Noncommercial > and Non-Profit organizations in their applications for new gTLDs. * > > History: We (NCSG and NCUC before NCSG existed) fought this battle at > second level and now at the top level.? Trademark owners /do not have > a better right to words than we do -- /in fact under traditional > trademark laws and balances, noncommercial uses of organization and > individuals are protection, for example, as our names (Wendy & > McDonald), for descriptions of our activities like baseball, art, and > poetry - and for our criticisms, concerns, and arguments.? Words like > liberty and freedom are also gas stations and blood glucose monitors! > > In preparation for our meeting tomorrow, I share our final memo to the > Small Team after weeks of seeking support for an equal and equivalent > exception for noncommercial and non-profit organizations.? We have to > share that we felt very beaten up in this process - it was not fun.? A > lot of power was given in this experimental Small Team and many people > served as active and unwavering advocates for their clients. > > That said, Paul McGrady did a good and fair job as Chair. He worked > very hard to make sure all voices were heard, including ours. > > Best, Kathy > > ------------------------------------- > > Hi All [SubPro Small Team Plus], > > Please put away the knives and sheath the spears? > > We are coming in to support Kurt?s concerns and proposals: /?I think > it is much better to take a conservative approach for this round and > seek to avoid user confusion to the extent possible and eliminate > exceptions at this point. I also believe we should deliver to ICANN an > implementable policy that will avoid vagueness and litigation, i.e., > creating policy that facilitates the implementation of a smooth > running process. This is incredibly important for the reputation of > the multi-stakeholder model.?Kurt, 4 Aug./ > > Efficiency, clarity, fairness. It?s not a perfect solution to consumer > confusion since we know that .MOBIL can coexist and with .MOBILE and > .MOBI and .NEW and .NEWS, but it is clear and understandable to > everyone coming into the process.Yes, it favors incumbents, but it > serves the overall goals of the SubPro Working Group: /?Specifically, > the Working Group recommends prohibiting plurals and singulars of the > same word within the same language/script in order to reduce the risk > of consumer confusion.?/ > > In the current exceptions language, now added to our many Strawmen, we > have strayed from any anchor point to the SubPro Small Team > recommendation language.We are no longer evaluating new gTLDs against > each other for meaning, or for confusion. We seem to have left these > ideas completely behind. [1] > > /We cannot support rules that allow a trademark, from anywhere in the > world, registered in the Trademark Clearinghouse and used for a .BRAND > application, to get a complete ?pass? from all evaluation and > examination of meaning ? that is a clear formula for consumer confusion./ > > Further, the current language and many prior Strawmen are premised on > assumptions that are not fair or valid, including that the rest of the > world will use ?generic words? for their new gTLDs. But that is not > the case. Organizations, companies and individuals around the world > will apply for the gTLD strings that are the most meaningful to them ? > some will be fanciful, some will be arbitrary as applied to their > activities, some will be descriptive, and some will be generic. There > is no reason that trademarks should take priority over everyone else?s > applications for new gTLD strings. > > /If we don?t evaluate the meaning of all gTLD strings identified in as > Singulars or Plurals of other applications or existing gTLDs in a > clear and transparent way, and if we don?t have fair and balanced > exceptions that equally support legitimate noncommercial and > commercial use,/ /then we must revert to Kurt?s language./ As long as > the gTLDs are the same word, in the same language, in some legitimate > dictionary, we should put them into a contention set. This is a clear > and efficient way to avoid the risk of consumer confusion over the gTLDs. > > We are happy to explain further. > > _There is nothing magical about trademarks._ > > We oppose the exceptions language for five reasons and can certainly > provide more: > > 1)It assumes a high standard of review for trademarks, and that is not > true internationally. Trademarks in many countries are granted without > ?use? requirements. The Trademark Clearinghouse (TMCH) must accept > marks from every country, and although it requires a showing of use, > the showing is de minimis. As long as the product or service appears > somewhere on the website, even in a footer, the .BRAND requirements > are satisfied. > > The Rights Protection Mechanisms PDP Working Group found a pattern of > registration in the Trademark Clearinghouse that shows trademark > owners in Switzerland actively using their TMCH registrations to ?game > the system? to gain early access to valuable domain names in Sunrise. > The stakes for gaming in the TMCH will be much higher when someone can > get an automatic pass out of a contention set for a Singular/Plural gTLD. > > 2)It assumes that the trademark owners have better rights to new gTLDs > than other applicants, and that is certainly not the case. *Every > Applicant for a New gTLD, and especially those coming from the Global > South, tribes and indigenous peoples, non-profits and civil society ? > groups that ICANN will go to great lengths to recruit to the New gTLD > program and to help through the application process ? should have the > same right and opportunity to a new gTLD string.*Just because there is > a trademark for the word ?rotary? does not mean that the .BRAND owner > should prevail in a grouping of applications for .rotary and .rotaries > by Rotary International and a group posting on the research of traffic > circles (.rotaries) around the world. *New gTLDs are important and > central to each and every applicant.* > > 3)It does not protect Sensitive Strings, and we need to. The GAC has > told us that certain gTLDs are important to *Consumer Protection and > Regulated Markets, *as /?These strings are likely to invoke a level of > implied trust from consumers, and carry higher levels of risk > associated with consumer harm.?/ > > *We respect this GAC Consensus Advice and urge a wall be built around > the Sensitive String they identified for us.No Singular/Plurals of > these words should be allowed: * > > /Children: .kid, .kids, .kinder, .game, .games, .juegos, .play, > .school, .schule, .toys; Environmental: .earth, .eco, .green, .bio, > .organic; Health and Fitness: .care, .diet, .fit, .fitness, .health, > .healthcare, .heart, .hiv, .hospital,, .med, .medical, .organic, > .pharmacy, .rehab, .surgery, .clinic, .healthy (IDN Chinese > equivalent), .dental, .dentist .doctor, .dds, .physio; > Financial:capital, . cash, .cashbackbonus, .broker, .brokers, .claims, > .exchange, .finance, .financial, .fianancialaid, .forex, .fund, > .investments, .lease, .loan, .loans, .market, . markets, .money, .pay, > .payu, .retirement, .save, .trading, .autoinsurance, .bank, .banque, > .carinsurance, .credit, .creditcard, .creditunion,.insurance, .insure, > ira, .lifeinsurance, .mortgage, .mutualfunds, .mutuelle, .netbank, > .reit, .tax, .travelersinsurance, .vermogensberater, > .vermogensberatung and .vesicherung. Gambling: .bet, .bingo, .lotto, > .poker, and .spreadbetting, .casino; Charity: .care, .gives, .giving, > .charity; Education: degree, .mba, .university; Intellectual > Property.audio, .book (and IDN equivalent), .broadway, .film, .game, > .games, .juegos, .movie, .music, .software, .song, .tunes, .fashion > (and IDN equivalent), .video, .app, .art, .author, .band, .beats, > .cloud (and IDN equivalent), .data, .design, .digital, .download, > .entertainment, .fan, .fans, .free, .gratis, .discount, .sale, > .hiphop, .media, .news, .online, .pictures, .radio, .rip, .show, > .theater, .theatre, .tour, .tours, .tvs, .video, .zip;Professional > Services: .abogado, .accountant, .accountants, .architect, > .associates, .attorney, .broker, .brokers, .cpa, .doctor, .dentist, > .dds, .engineer, .lawyer, .legal, .realtor, .realty, .vet; Corporate > Identifiers: .corp, .gmbh, .inc, .limited, .llc, .llp, .ltda, .ltd, > .sarl, .srl, .sal; Generic Geographic Terms: .town, .city, .capital; > .reise, .reisen; .weather; .engineering; .law; Inherently Governmental > Functions .army, .navy, .airforce.Beijing Communique, ICANN46/ > > *Currently there is no protection for these strings and > plural/singular gTLDs will be allowed, including .BRAND exceptions ? > and lead to consumer confusion. * > > 4) It assumes that all .BRAND Registries will monitor their licensees > closely, and that is not the case. There is no assurance that all > .BRAND Registry Operators will closely oversee their affiliates and > trademark licensees once they register domain names. The only > requirement is that a user licensed by the .BRAND must also possess a > trademark license, which can be incorporated into the .BRAND > agreement. But, while trademark licenses in the US and some other > countries require quality control, this type of oversight is not > required in many parts of the world and not needed to maintain a > trademark: > > ?The majority of countries (roughly 2/3) don?t require quality control > in licenses. (Mary M. Squyres and Nanette Norton, Trademark Practice > Throughout the World | September 2023 Update Appendix 23(G)). > > ??European trademark law does not require the licensor to exercise > control over the use of the trademark in order to ensure the quality > of the goods or services in question.??(Anne Lauber-R?nsberg, in The > Commercial Exploitation Of Personality Features In Germany From The > Personality Rights And Trademark Perspectives, 107 Trademark Rep. 803, > 843 (2017)). > > ?In Germany and France, ?there is no concern for preserving the source > function of trademarks by means of the provision and exercise of > quality control.? (Neil Wilkof, in Trademark licensing: the once and > future narrative, in Research Handbook on Intellectual Property > Licensing 216 (2013)). > > ?The European Court of Justice held in 2017 that failure to monitor > licensees doesn?t invalidate a registration, though the mark can be > cancelled if its use was deceptive. (W.F. G?zze Frottierweberei Gmbh, > Wolfgang G?zze GmbH v Verein Bremer Baumwollb?rse, case C-689/15, > _https://perma.cc/554Z-8TYD_). > > If many countries do not require oversight of trademark licensees and > such oversight can be lax or non-existent, then without more, we have > no assurance of close oversight domain names by their affiliates and > licensees around the world. > > 5) The remedies that our Small Team have discussed for termination of > a .BRAND that receives a Singular/Plural exemption are not consistent > with Specification 13. > > Jeff and Susan reasonably proposed the remedy of termination for a > .BRAND receiving a Singular/Plurals exemption, and then ceasing to > operate as a .BRAND: /?If at any time ICANN reasonably determines that > the TLD no longer qualifies as a .Brand TLD, Registry Operator shall > be considered in material breach of the Registry Agreement.? If the > .Brand TLD is unable or unwilling to cure such breach, ICANN shall > have the right to terminate the Registry Agreement.?/We do not disagree. > > *But Specification 13 dictates a different outcome. If a .BRAND cease > to operate as a .BRAND then it becomes an open gTLD. //*/Spec 13: > ?//If at any time ICANN determines, in its reasonable discretion, that > the TLD no longer qualifies as a .Brand TLD, ? then (i) the TLD shall > immediately cease to be a .Brand TLD, (ii) Registry Operator shall > immediately comply with the provisions of the Agreement as no longer > modified by this Specification 13 (other than Section 2 hereof) and > (iii) the provisions of this Specification 13 (other than Section 2 > hereof) shall thereafter no > longer have any effect.?/ > > Truly such a change would immeasurably complicate consumer confusion > issues, and be fundamentally unfair to all who did not receive their > new gTLDs in the exemption process. > > _If we really wanted a fair and balanced exception, we would have had > one by now._ > > In this incredibly talented group of Small Team members, if we had > wanted a fair and balanced exception, we would have found it weeks > ago. /Early on, we talked about the high standard we wanted for those > receiving exceptions and that, consistent with the policies of ICANN, > exceptions should be fair and balanced./ But that is not what has > happened. > > *Non-profits and Civil Society organizations are at least as driven to > monitor who receives their domain names as any .BRAND applicant.* The > motivation for Non-profits and Civil Society diligence comes from > their special status with their governments, their communities, their > donors, and the people at the local, national and international level > who benefit from their services. *Their reputations, and therefore > their existences, are intricately bound to serving their missions.* > *As a trademark owner can bind their affiliates and licensees who > receive domain names, Non-profits and Civil Society clearly delineate > their eligible registrants, based on specific, objective eligibility > criteria and enforceable mechanisms in Registry Voluntary Commitments > that are strong and binding. * > > ----------------------- > > */A parallel exception would have been very fair and easy for us to > accept:/* > > Exception: > > 1. in the event that an entity applies for a string that is either > the plural or singular of an existing string in any language, that > entity?s application shall be allowed to proceed through the > application process and be delegated provided that it meets the > criteria for a Non-Profit and Civil Society Organization pursuant > to the presented and signed Registry Voluntary Commitment. > 2. If at any time ICANN reasonably determines that the TLD no longer > operates pursuant to its commitments in the RVC, then Registry > Operator shall be considered in material breach of the Registry > Agreement.? If the Non-Profit or Civil Society TLD is unable or > unwilling to cure such breach, ICANN shall have the right to > terminate the Registry Agreement. > > _____________________ > > _Defining Non-profit and Civil Society gTLDs_ > > Non-profit and Civil Society gTLDs: > > 1.A non-profit or civil society gTLD meets the general definition of a > civil society organization under the UN, namely: Non-State, > not-for-profit, voluntary entities formed by people in the social > sphere that are separate from the State and the market. Civil society > groups are?community-based organizations as well as non-governmental > organizations (NGOs).?) > > 2.Methods of verification, to be provided to ICANN, include: > > 1. Certification as a non-profit or civil society organization > under the laws of the country in which the organization is > registered; or > 2. Confirmation of equivalence determination by a reputable > group, e.g. TechSoup (making?a good-faith determination that a > non-U.S. organization is equivalent to a U.S. public charity); or > 3. Recognition by an international organization such as the > United Nations. > > iii.The Applicant must document that it has been in continuous > existence for over a year prior to the filing of its TLD registry > application with ICANN. > > iv.The TLD string should be a key term or identifier that the > organization associates with itself and its mission. > > v.It should be owned and used continuously by the Registry Operator or > its Affiliates in connection with the Registry Operator?s or its > Affiliates? offering of their non-profit/civil society services. Such > services shall not include services related to the provision of TLD > Registry Services. > > vi.only Registry Operator, its Affiliates or members in good standing > are registrants of domain names in the TLD and control the DNS records > associated with domain names at any level in the TLD; > > vii.the TLD is not a Generic String TLD (as defined in Specification 11). > > But our Small Team could not do that. > > _In closing, we note there is another new idea floating around the > Small Team that ICANN cannot look at the meaning of the words in > gTLDs, and that cannot be right or accurate._ > > NCSG was very involved in the call for ICANN to not allow content to > be placed in Registry Voluntary Commitments, including the type of > content that would require ICANN to monitor the text, videos and > pictures placed on websites. > > *But that does not mean that ICANN can never again look at the meaning > of the word or the purpose of a word in a gTLD. That would invalidate > much of ICANN?s mission and purpose. * > > ICANN?s mission is and remains: > > /Section 1.1. MISSION/ > > /(a) The mission of the Internet Corporation for Assigned Names and > Numbers ("ICANN") is to ensure the stable and secure operation of the > Internet's unique identifier systems as described in this Section > 1.1(a) (the "Mission"). Specifically, ICANN:/ > > /(i) Coordinates the allocation and assignment of names in the root > zone of the Domain Name System ("DNS") and coordinates the development > and implementation of policies concerning the registration of > second-level domain names in generic top-level domains ("gTLDs"). In > this role, ICANN's scope is to coordinate the development and > implementation of policies:/ > > /For which uniform or coordinated resolution is reasonably necessary > to facilitate the openness, interoperability, resilience, security > and/or stability of the DNS including, with respect to gTLD registrars > and registries, policies in the areas described in Annex G-1 and Annex > G-2; and/ > > /That are developed through a bottom-up consensus-based > multistakeholder process and designed to ensure the stable and secure > operation of the Internet's unique names systems./ > > ---------- > > *The limits of Bylaws 1.1 sections (b) and (c), include not imposing > rules on the content that domain names carry and provide, but does not > stop ICANN from looking closely at top level and second level domain > names. * > > *Saying otherwise would eliminate the URS and UDRP. * > > The basis of the UDRP and URS /is looking at the meaning of the second > level domain name, who has registered it and how they are using it. > /Although ICANN has delegated the authority for the review and > decision, the URDP and URS decisions are enforced by ICANN under its > Registry Agreements and Registrar Accreditation Agreements. This is > ICANN?s responsibility. > > *Similarly at the top level, ICANN must examine the nature of the > applicant, who they are, and how they intend to use the applied-for > gTLD. ICANN will review comments from the Community on these same > issues. This is part and parcel of the application process. * > > Three objection processes are based on these same substantive factors: > String Confusion, Community and Legal Rights objections. All decided > via delegated authority from ICANN and all enforced by ICANN. Even > reviewing a .BRAND application to see, among other things, if it is a > generic word involves ICANN looking closely at the Applicant, the New > gTLD, and its meaning. It?s all consistent with a much wider range of > exemptions, for Non-profits and Civil Society as well as .BRANDs, that > we could have created had we chosen to do so. > > ----------------------------------- > > As shared above, we have come to support Kurt?s concerns and proposals: > > /?I think it is much better to take a conservative approach for this > round and seek to avoid user confusion to the extent possible and > eliminate exceptions at this point. I also believe we should deliver > to ICANN an implementable policy that will avoid vagueness and > litigation, i.e., creating policy that facilitates the implementation > of a smooth running process. This is incredibly important for the > reputation of the multi-stakeholder model.?Kurt, 4 Aug./ > > It?s not a perfect solution, but it is efficient, clear and fair. > > Kathy and Rebecca > > [1] > https://docs.google.com/document/d/13VIPAxR5OYAzgTvSiaWCBTzYT0siLC2mpt-1Tm3JxTA/edit#heading=h.oc222usgafq2 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Wed Sep 4 18:09:31 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 4 Sep 2024 17:09:31 +0200 Subject: [NCSG-PC] FW: Proposal: NCPH Day 0 Meeting ICANN81 In-Reply-To: References: Message-ID: <46763c50-ccfe-43a3-8ed5-a16184a39233@Julf.com> Here is the initial draft agenda for the day 0. I will have a call with Mason and Paul on Thursday - comments and suggestions welcome! Julf 1. Procedural/Process issues 1. Finalize procedures for appointment of candidate for Board Seat 14 2. Arrive at predictable procedures for the selection of GNSO Council leadership. 3. Schedule for intersessional NCPH Executive Committee meetings 4. Scheduled for intersessional NCPH member meetings (?) 2. Alignment on contributions to community work 1. Further contribute input to the work of the RDRS Standing Committee. 2. Collaborate in discussions regarding the impact of the European Union?s NIS2 Directive as it relates to the DNS. 3. Review current status of and contribute to community work on SubPro 3. Policy issues ? Align on where we have policy issues of mutual interest, potential topics might include: 1. IPC Recommendation 18 2. DNS Abuse 3. Holistic Review 4. Others? 4. ICANN Engagement 1. Develop strategy for developing messaging on the output and timing/location of presentation with relevant Board members. From mesumbeslin at gmail.com Thu Sep 12 00:00:17 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 12 Sep 2024 07:00:17 +1000 Subject: [NCSG-PC] Fwd: Draft Agenda | NCSG Policy Meeting | Monday, 16 September 2024 In-Reply-To: <1F714B0F-6C3C-40BD-B33D-F38CDF87275D@icann.org> References: <1F714B0F-6C3C-40BD-B33D-F38CDF87275D@icann.org> Message-ID: Hi team, Please see the draft agenda for our meeting next week. I don't have anything in particular to put on the agenda since most of what I could think of is already in the council meeting agenda that we will walk through. So, if you have anything that you'd like us to discuss, please add it to the agenda document. Warmly, Tomslin ---------- Forwarded message --------- From: Andrea Glandon Date: Wed, 4 Sept 2024 at 01:50 Subject: Draft Agenda | NCSG Policy Meeting | Monday, 16 September 2024 To: Tomslin Samme-Nlar Cc: Daniel Gluck , Andrea Glandon < andrea.glandon at icann.org> Hi Tomslin, Please find below a link to the draft agenda for the NCSG PC meeting on Monday, 16 September 2024. Please feel free to adjust as needed. https://docs.google.com/document/d/1R1pZoQcQnngCctO-YFgChUpJD1f2asaeMKC_fk6UFUU/edit?usp=sharing Thanks! *Andrea Glandon* Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) *Skype ID:* acglandon76 -------------- next part -------------- An HTML attachment was scrubbed... URL: From emmanuelvitus at gmail.com Thu Sep 12 13:57:58 2024 From: emmanuelvitus at gmail.com (Emmanuel Vitus) Date: Thu, 12 Sep 2024 10:57:58 +0000 Subject: [NCSG-PC] =?utf-8?q?IDNs_EPDP=3A_Review_of_proposed_language_cha?= =?utf-8?q?nges_for_Recommendations_14_and_15_=E2=80=93_Alignment_w?= =?utf-8?q?ith_NCSG=27s_public_comment?= Message-ID: Dear NCSG Members, I hope this message finds you well. As your representatives in the IDN EPDP, Peter and I would like to inform you about some recent developments concerning the proposed changes to Recommendation 14 and Recommendation 15, shared by the Chair of the IDN EPDP working group. These changes were presented as we continued to revise the public comment on the EPDP draft recommendations. Leadership has requested that we review these proposals and provide feedback. *Recommendation 14:* The revised language separates two key concepts: - Ensuring communication between registries and registrars to enforce the 'same entity' principle regarding variant domain names. - Providing a mechanism for end users to discover the allocated variant domain names for purposes like registering a domain or filing a complaint. Under the new language, responsibility is given to gTLD registry operators, who will work with ICANN-accredited registrars to provide necessary information about the allocated variant domain names, including the source and initial source domain names. *Recommendation 15:* The changes to Recommendation 15 address privacy concerns raised by ICANN Legal, indicating that disclosing allocated variant domain names could reveal details about the registrant that may unintentionally compromise privacy. Registrars are now expected to evaluate whether to disclose this information based on balancing the interests of the requestor and the data subject, in line with applicable privacy laws. *NCSG?s Position:* * These changes align well with the comments we raised in our public submission during the review process, particularly regarding the protection of personal data and ensuring that any handling of variant domain names respects applicable privacy laws. The revisions strike a careful balance between transparency and privacy, which is in line with the principles that NCSG has always advocated for.* *Recommendation:* Since these proposed changes reflect our earlier feedback and address concerns outlined in our public comment, Peter and I recommend that we accept the updated language for Recommendations 14 and 15. Please feel free to provide your thoughts or questions. Best regards, Emmanuel & Peter NCSG Representatives, IDN EPDP -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Thu Sep 12 20:49:24 2024 From: julf at Julf.com (Johan Helsingius) Date: Thu, 12 Sep 2024 19:49:24 +0200 Subject: [NCSG-PC] Fwd: Draft Agenda | NCSG Policy Meeting | Monday, 16 September 2024 In-Reply-To: References: <1F714B0F-6C3C-40BD-B33D-F38CDF87275D@icann.org> Message-ID: <8a67032b-0d30-4bdc-9981-e76028135c25@Julf.com> My apologies, but I am unfortunately travelling on Monday. Julf On 11/09/2024 23:00, Tomslin Samme-Nlar wrote: > Hi team, > > Please see the draft agenda for our meeting next week. I don't have > anything in particular to put on the agenda since most of what I could > think of is already in the council meeting agenda that we will walk > through. So, if you have anything that you'd like us to discuss, please > add it to the agenda document. > > Warmly, > Tomslin > > > > ---------- Forwarded message --------- > From: *Andrea Glandon* > > Date: Wed, 4 Sept 2024 at 01:50 > Subject: Draft Agenda | NCSG Policy Meeting | Monday, 16 September 2024 > To: Tomslin Samme-Nlar > > Cc: Daniel Gluck >, Andrea Glandon > > > > > Hi Tomslin, ____ > > __ __ > > Please find below a link to the draft agenda for the NCSG PC meeting on > Monday, 16 September 2024. Please feel free to adjust as needed.____ > > __ __ > > https://docs.google.com/document/d/1R1pZoQcQnngCctO-YFgChUpJD1f2asaeMKC_fk6UFUU/edit?usp=sharing ____ > > __ __ > > Thanks!____ > > *Andrea Glandon*____ > > Policy Operations Sr. Coordinator____ > > Internet Corporation for Assigned Names and Numbers (ICANN)____ > > *Skype ID:*acglandon76____ > > ____ > > ____ > > __ __ > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From julf at Julf.com Fri Sep 13 10:34:47 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 13 Sep 2024 09:34:47 +0200 Subject: [NCSG-PC] Fwd: NCPH Day 0 Meeting ICANN81 [ ref:!00D1a0Y7OU.!500Qk0CyRb7:ref ] In-Reply-To: References: Message-ID: <74d7d9f6-35f1-48c8-a24c-71607f32fb03@Julf.com> FYI -------- Forwarded Message -------- Subject: NCPH Day 0 Meeting ICANN81 [ ref:!00D1a0Y7OU.!500Qk0CyRb7:ref ] Date: Thu, 12 Sep 2024 20:07:53 +0000 (GMT) From: Correspondence To: mcole at perkinscoie.com , julf at julf.com CC: carlos.reyes at icann.org , sally.costerton at icann.org , mary.wong at icann.org , andrea.glandon at icann.org , cassia.oliveira at icann.org Dear Mason Cole and Julf Helsingius, Please find attached a letter from Sally Costerton, Sr. Advisor to President and SVP, Global Stakeholder Engagement & Interim President and CEO at ICANN regarding the proposed NCPH Day 0 Meeting ICANN81. This letter will be posted shortly to the ICANN Correspondence page (https://www.icann.org/resources/pages/correspondence ). Please submit any questions you may have about this message to correspondence at icann.org . Best Regards, Michael Kovach The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence at icann.org www.icann.org ref:!00D1a0Y7OU.!500Qk0CyRb7:ref -------------- next part -------------- A non-text attachment was scrubbed... Name: Costerton to Cole-Helsingius 10Sep24.pdf Type: application/pdf Size: 162949 bytes Desc: not available URL: From julf at Julf.com Fri Sep 13 19:48:07 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 13 Sep 2024 18:48:07 +0200 Subject: [NCSG-PC] Fwd: Status of your Application for the Pilot Holistic Review Team In-Reply-To: <9733462F-293E-455A-A5BC-FF831276B556@icann.org> References: <9733462F-293E-455A-A5BC-FF831276B556@icann.org> Message-ID: <15cb40d1-4a5f-47a3-a723-8fc47c2a8f1a@Julf.com> FYI -------- Forwarded Message -------- Subject: Status of your Application for the Pilot Holistic Review Team Date: Fri, 13 Sep 2024 16:39:32 +0000 From: RSA Coordinators CC: Larisa Gurnick , Theresa Swinehart Dear applicant, Thank you for applying to be a member of the Pilot Holistic Review Team. We regret to inform you that you were not selected to serve on the review team. The Supporting Organizations, Advisory Committees, and ICANN organization appreciate your experience and willingness to volunteer your time for this effort. We encourage you to follow the work of the Pilot Holistic Review via the pilot?s wiki page. If you are interested in becoming an Observer of the pilot, please visit the pilot?s Observers wiki page for more information. Thank you again for your application and interest. Best regards, Larisa Gurnick Vice President, Review Support and Accountability, Global Domains and Strategy From compsoftnet at gmail.com Sat Sep 14 18:33:48 2024 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Sat, 14 Sep 2024 11:33:48 -0400 Subject: [NCSG-PC] Fwd: Status of your Application for the Pilot Holistic Review Team In-Reply-To: <15cb40d1-4a5f-47a3-a723-8fc47c2a8f1a@Julf.com> References: <9733462F-293E-455A-A5BC-FF831276B556@icann.org> <15cb40d1-4a5f-47a3-a723-8fc47c2a8f1a@Julf.com> Message-ID: Hi Julf, Thanks for sharing this with the group. Unfortunately we don?t have rep on the pilot holistic review. Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ On Fri, Sep 13, 2024 at 12:48?PM Johan Helsingius via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > FYI > > > -------- Forwarded Message -------- > Subject: Status of your Application for the Pilot Holistic Review > Team > Date: Fri, 13 Sep 2024 16:39:32 +0000 > From: RSA Coordinators > CC: Larisa Gurnick , Theresa Swinehart > > > > > Dear applicant, > > Thank you for applying to be a member of the Pilot Holistic Review Team. > > We regret to inform you that you were not selected to serve on the > review team. > > The Supporting Organizations, Advisory Committees, and ICANN > organization appreciate your experience and willingness to volunteer > your time for this effort. > > We encourage you to follow the work of the Pilot Holistic Review via the > pilot?s wiki page. If you are > interested in becoming an Observer of the pilot, please visit the > pilot?s Observers wiki page for > more information. > > Thank you again for your application and interest. > > Best regards, > > Larisa Gurnick > > Vice President, Review Support and Accountability, Global Domains and > Strategy > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Mon Sep 16 14:55:51 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Mon, 16 Sep 2024 21:55:51 +1000 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: References: Message-ID: FYA team. Razoana Moslam would like to be nominated by our SG for the NextGen Mentorship Program. Let me know your thoughts. Warmly, Tomslin ---------- Forwarded message --------- From: Razoana Moslam Date: Wed, 4 Sept 2024, 19:43 Subject: nextgen Mentor nomination To: Tomslin Samme-Nlar Hi Tomsil, I hope you are well. I am interested to be nominated for the NextGen Mentorship via our constituency. Can you please help me? Please let me know if you need any information from me. Best Regards, Razoana Moslam -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Mon Sep 16 15:25:41 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Mon, 16 Sep 2024 12:25:41 +0000 Subject: [NCSG-PC] FW: [Ext] Nextgen mentor nomination In-Reply-To: References: Message-ID: <5F54FF99-62BD-4788-AB80-33F16B8B05A4@icann.org> Hello PC, Please see below. Kind Regards, Andrea From: Razoana Moslam Date: Monday, September 16, 2024 at 07:15 To: Andrea Glandon Subject: [Ext] Nextgen mentor nomination Hi Andrea, I hope you are well. I am interested to be nominated for the NextGen Mentor via our constituency. Can you please help me? Please let me know if you need any information from me. Best Regards, Razoana Moslam -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Mon Sep 16 15:26:40 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Mon, 16 Sep 2024 12:26:40 +0000 Subject: [NCSG-PC] FW: [Ext] Re: NEW: NIS2 Consultation and Next Steps In-Reply-To: References: <5592EDA5-F999-4243-A2EF-B5ECBC967BD4@icann.org> Message-ID: Hello! Another name for interest in the NextGen mentor. Thanks! Kind Regards, Andrea From: "Yao Amevi A. Sossou" Date: Monday, September 16, 2024 at 03:46 To: Andrea Glandon Subject: [Ext] Re: NEW: NIS2 Consultation and Next Steps Dear Andrea, Thank you fro the update. I would to know if I can be part of the NextGen at ICANN Program Selection Committee ? I state interest to be part of that committe. Kind regards ............................................................. Yao Amevi A. Sossou Researcher |IxD| IT Support | Project manager| Human centered Entrepreneurship| SDG Advocate | Internet Governance | Youth IGF Email: soyames at gmail.com Twitter: https://twitter.com/_amevY2 [twitter.com] LinkedIn: Yao Amevi A. sossou | LinkedIn [linkedin.com] ............................................................. To promote respect for the environment, thank you to only print this email only when necessary On Thu, Sep 12, 2024 at 5:04?PM Andrea Glandon > wrote: [Image removed by sender.] Thursday, 12 September 2024 ICANN Community Digest [Image removed by sender.] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Click Here to Learn More about the RDRS Pilot Program [danh45uab.cc.rs6.net] Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo at icann.org! Table of Contents ICANN81 ? Register Now for ICANN81 ? ICANN Reviews team available for engagement during ICANN81 ? ICANN81 Community Childcare Grants Program: Apply Now Information Sharing ? NEW: Reminder to Participate in ICANN?s Operational Design Phase (ODP) Community Consultation Survey ? NEW: ICANN Seeks Input on Additional Reference Label Generation Rules and Updates ? NEW: ICANN Seeks Input on Proposed Language for Next Round Applicant Guidebook ? NEW: NIS2 Consultation and Next Steps ? Africa Internet Summit 2024 Webinars ? Webinars Introduce ICANN?s New gTLD Program: Next Round RSP Evaluation Program ? Action Items ? ? NEXT WEEK: Draft ICANN FY26?30 Strategic Plan and Operating Plan Framework Open for Public Comment ? Participate in ICANN?s Operational Design Phase Community Consultation Survey ? DEADLINE EXTENDED: NextGen at ICANN82 Applications ? NextGen at ICANN Mentor Program Nominations ? NextGen at ICANN Program Selection Committee Nominations Public Comment ? NEW: Second Proceeding for Proposed Language for Draft Sections of the Next Round Applicant Guidebook ? NEW: Additional Reference Label Generation Rules and Related Updates ? CLOSES TODAY: gTLD IDN Tables Review Process When Reference LGR is not available ? CLOSES MONDAY: IRP-IOT ? Proposed updates to the IRP Supplementary Procedures ? CLOSES MONDAY: Proposed Fundamental Bylaws Amendments Related to Grant Program ? CLOSES TUESDAY: Draft ICANN Strategic Plan and Operating Plan Framework for FY26-30 ? Initial Report on the Transfer Policy Review ICANN81 Register Now for ICANN81 ICANN81 will be held 09 - 14 November 2024 at the Istanbul Congress Center. Register and Read more [danh45uab.cc.rs6.net] ICANN Reviews team available for engagement during ICANN81 The ICANN Reviews Program encompasses the management of Specific Reviews and Organizational Reviews, including any resulting implementation work that relates to improving the reviews process. The ICANN org Review Support and Accountability team is available to your group to engage on the status of several initiatives underway to improve ICANN Reviews, including: ? Launch of the Pilot Holistic Review ? Progress of the work led by the community to evolve Organizational Reviews into a Continuous Improvement Program ? Planning for the Fourth Accountability and Transparency Review Schedule an engagement with us by contacting rsa-coordinators at icann.org [danh45uab.cc.rs6.net]. ICANN Accountability page [danh45uab.cc.rs6.net] | ICANN.org Reviews page [danh45uab.cc.rs6.net] ICANN81 Community Childcare Grants Program: Apply Now The program facilitates in-person participation of community members with children who are 12 years old or younger at ICANN Public Meetings and eligible ICANN events. Deadline: Friday, 4 October 2024, at 23:59 UTC Read more. [danh45uab.cc.rs6.net] Information Sharing NEW: Reminder to Participate in ICANN?s Operational Design Phase (ODP) Community Consultation Survey More information regarding this request and the ODP Community Consultation can be found from the following ICANN announcement [danh45uab.cc.rs6.net]. NEW: ICANN Seeks Input on Additional Reference Label Generation Rules and Updates These Reference LGRs are reference Internationalized Domain Name tables in a machine-readable format and are developed in the context of either a language or a script with consultation from relevant language and script communities. Read more. [danh45uab.cc.rs6.net] NEW: ICANN Seeks Input on Proposed Language for Next Round Applicant Guidebook This is the second in a series of Public Comment proceedings that will gather input from the ICANN community on proposed language for selected sections of the Applicant Guidebook for the New gTLD Program: Next Round. Read more. [danh45uab.cc.rs6.net] NEW: NIS2 Consultation and Next Steps As we move closer to the October deadline, it remains important for all stakeholders to stay engaged and proactive, ensuring a uniform transposition of NIS2 which not only recognizes the uniqueness of national ecosystems but also aligns with international standards, safeguarding the integrity of the DNS and the broader internet ecosystem. Read more. [danh45uab.cc.rs6.net] Africa Internet Summit 2024 AIS?24 is a platform for the Internet community to gather to discuss, collaborate, learn, and disseminate information about these key areas of Africa?s Internet development. Date: Tuesday 10 September 2024 (07:00 UTC) - Saturday 14 September 2024 (07:00 UTC) Read more and Register. [danh45uab.cc.rs6.net] Webinars Webinars Introduce ICANN?s New gTLD Program: Next Round RSP Evaluation Program The webinars will provide an overview of the requirements for evaluation, a description of the testing that will be conducted, and an explanation of the overall evaluation process. Webinar 1: Tuesday, 1 October 2024 from 15:00?16:00 UTC | Register [danh45uab.cc.rs6.net] Webinar 2: Wednesday, 2 October 2024 from 00:00?1:00 UTC | Register [danh45uab.cc.rs6.net] Read more. [danh45uab.cc.rs6.net] Action Items NEXT WEEK: Draft ICANN FY26?30 Strategic Plan and Operating Plan Framework Open for Public Comment The Draft ICANN FY26?30 Strategic Plan and Operating Plan Framework is open for Public Comment through 17 September 2024. Read More and Participate [danh45uab.cc.rs6.net] The Board Strategic Planning Committee co-chairs hosted two community webinars on 30 and 31 July 2024 to provide an in-depth overview of the plans. The zoom Recordings are posted here [danh45uab.cc.rs6.net]. Participate in ICANN?s Operational Design Phase Community Consultation Survey Community input will help ICANN identify opportunities for continuous improvement regarding ODP objectives and related mechanisms in the policy lifecycle to fulfill the needs of the Board, community, and org. Deadline: 27 September 2024 Read more and access the survey here. [danh45uab.cc.rs6.net] DEADLINE EXTENDED: NextGen at ICANN82 Applications ICANN wants to hear from university students living and studying in the North America region who are interested in the future of the Internet and in participating in the ICANN82 Community Forum. ICANN82 is scheduled to be held in Seattle, Washington, from 8?13 March 2025. Deadline: 11 October 2024 Read more. [danh45uab.cc.rs6.net] NextGen at ICANN Mentor Program Nominations The NextGen at ICANN Program seeks nominations to fill three (3) slots for the 2025 Mentor Program. These appointments will serve for the ICANN82-84 meetings. Nominations must be submitted no later than Thursday, 31 October 2024. Interested community groups should select their respective volunteers and notify Fernanda Iunes at fernanda.iunes at icann.org. NextGen at ICANN Program Selection Committee Nominations NextGen at ICANN Program is seeking nominations to fill three (3) slots for selection committee members. Each SO/AC is asked to nominate candidates for these positions. Individual self-nominations will not be considered. Interested community groups should select their respective NextGen at ICANN Selection Committee volunteers by Thursday, 31 October 2024. Interested community groups should select their respective volunteers and notify Fernanda Iunes at fernanda.iunes at icann.org. Each selection committee member will serve for a period of two (2) years beginning with ICANN82. For program details please visit our page [danh45uab.cc.rs6.net]. Public Comment NEW: Second Proceeding for Proposed Language for Draft Sections of the Next Round Applicant Guidebook [danh45uab.cc.rs6.net] Open for Submissions: 10 September 2024 Closed for Submissions: 21 October 2024 NEW: Additional Reference Label Generation Rules and Related Updates [danh45uab.cc.rs6.net] Open for Submissions: 12 September 2024 Closed for Submissions: 24 October 2024 CLOSES TODAY: gTLD IDN Tables Review Process When Reference LGR is not available [danh45uab.cc.rs6.net] Open for Submissions: 01 August 2024 Closed for Submissions: 12 September 2024 CLOSES MONDAY: IRP-IOT ? Proposed updates to the IRP Supplementary Procedures [danh45uab.cc.rs6.net] Open for Submissions: 03 July 2024 Closed for Submissions:16 September 2024 CLOSES MONDAY: Proposed Fundamental Bylaws Amendments Related to Grant Program [danh45uab.cc.rs6.net] Submissions Opening Date: 7 August 2024 Submissions Closing Date:16 September 2024 CLOSES TUESDAY: Draft ICANN Strategic Plan and Operating Plan Framework for FY26-30 [danh45uab.cc.rs6.net] Open for Submissions: 23 July 2024 Closed for Submissions: 17 September 2024 Initial Report on the Transfer Policy Review [danh45uab.cc.rs6.net] Open for Submissions: 01 August 2024 Closed for Submissions: 30 September 2024 See upcoming proceedings [danh45uab.cc.rs6.net]. See other public consultations [danh45uab.cc.rs6.net]. Volume 6, Issue 69 | Archive [danh45uab.cc.rs6.net] | Next Issue: Monday, 16 September 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net] ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 US Unsubscribe [visitor.constantcontact.com] | Update Profile [visitor.constantcontact.com] | Constant Contact Data Notice [constantcontact.com] [Image removed by sender. Constant Contact][constantcontact.com] -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Wed Sep 18 17:50:52 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 18 Sep 2024 16:50:52 +0200 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: References: Message-ID: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> Just wondering if a nextgen mentor shouldn't be someone with council experience? Julf On 16/09/2024 13:55, Tomslin Samme-Nlar wrote: > FYA team. > Razoana Moslam would like to be nominated by our SG for the NextGen > Mentorship Program. > > Let me know your thoughts. > > Warmly, > Tomslin > > ---------- Forwarded message --------- > From: *Razoana Moslam* > > Date: Wed, 4 Sept 2024, 19:43 > Subject: nextgen Mentor nomination > To: Tomslin Samme-Nlar > > > > Hi Tomsil, > > I hope you are well. I am interested to be nominated for the NextGen > Mentorship via our constituency. > > Can you please help me? Please let me know if you need any information > from me. > > > Best Regards, > Razoana Moslam > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From mamattah.raymond at gmail.com Wed Sep 18 17:54:14 2024 From: mamattah.raymond at gmail.com (Raymond Mamattah) Date: Wed, 18 Sep 2024 14:54:14 +0000 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> Message-ID: Hi all, I thought the person should rather have been a NextGen before. That will allow the person to speak from experience on how the program is all about. I believe we will have a lot of people with this experience who might not have had the privilege of being a council member. By the way, what has been the norm in selecting such people? Regards, Raymond Mamattah [image: linkedin] [image: facebook] [image: twitter] Accra, Ghana On Wed, Sep 18, 2024 at 2:50?PM Johan Helsingius via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > Just wondering if a nextgen mentor shouldn't be someone with council > experience? > > Julf > > > On 16/09/2024 13:55, Tomslin Samme-Nlar wrote: > > FYA team. > > Razoana Moslam would like to be nominated by our SG for the NextGen > > Mentorship Program. > > > > Let me know your thoughts. > > > > Warmly, > > Tomslin > > > > ---------- Forwarded message --------- > > From: *Razoana Moslam* > > > > Date: Wed, 4 Sept 2024, 19:43 > > Subject: nextgen Mentor nomination > > To: Tomslin Samme-Nlar > > > > > > > > Hi Tomsil, > > > > I hope you are well. I am interested to be nominated for the NextGen > > Mentorship via our constituency. > > > > Can you please help me? Please let me know if you need any information > > from me. > > > > > > Best Regards, > > Razoana Moslam > > > > _______________________________________________ > > NCSG-PC mailing list > > NCSG-PC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Wed Sep 18 18:11:54 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 18 Sep 2024 17:11:54 +0200 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> Message-ID: <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. Julf From mamattah.raymond at gmail.com Wed Sep 18 18:22:15 2024 From: mamattah.raymond at gmail.com (Raymond Mamattah) Date: Wed, 18 Sep 2024 15:22:15 +0000 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> Message-ID: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program - https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree ? Regards, Raymond Mamattah [image: linkedin] [image: facebook] [image: twitter] Accra, Ghana On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > On 18/09/2024 16:54, Raymond Mamattah wrote: > > > I thought the person should rather have been a NextGen before. That will > > allow the person to speak from experience on how the program is all > about. > > That is a good point, but I guess it depends on what kind of support/ > experience/guidance the mentor is supposed to provide - support for > being on the nextgen program or support in actual policy work in ICANN. > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Wed Sep 18 18:30:38 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 18 Sep 2024 17:30:38 +0200 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> Message-ID: <8de6c953-b75d-4125-9944-8d0f768f8e9d@Julf.com> Raymond, I am specifically thinking of the role of the mentor as described: "Mentors should encourage NextGen to find ways to contribute to an SO/AC or working group(s) that interests them. The focus should be on assisting NextGen to integrate into the community and engaging them with ICANN processes. Newcomers should have the necessary support to find their place within ICANN?s multistakeholder processes." Whet we need is mentors who can help mentees get into ICANN processes. That doesn't necessarily mean it has to be someone with council experience, but the GNSO council is our main tool for policy work. Julf On 18/09/2024 17:22, Raymond Mamattah wrote: > Let us agree that among the responsibilities for being a mentor is > related to actual policy work. But are we trying to say it is only those > with council experience that have experience in the policy process? I > don't think so. > > Here is the document that gives more information on the mentoring > program - > https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf > > I suggest we open the opportunity to those who dont even have council > experience, especially when the NextGen programme introduces new people > to the ICANN family. Hope you agree?? > > Regards, > Raymond Mamattah > linkedin facebook > twitter > > Accra, Ghana > > > On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC > > wrote: > > On 18/09/2024 16:54, Raymond Mamattah wrote: > > > I thought the person should rather have been a NextGen before. > That will > > allow the person to speak from experience on how the program is > all about. > > That is a good point, but I guess it depends on what kind of support/ > experience/guidance the mentor is supposed to provide - support for > being on the nextgen program or support in actual policy work in ICANN. > > ? ? ? ? Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > From jumaropi at yahoo.com Wed Sep 18 19:24:35 2024 From: jumaropi at yahoo.com (Juan Manuel Rojas) Date: Wed, 18 Sep 2024 16:24:35 +0000 (UTC) Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> Message-ID: <490072686.4977608.1726676675586@mail.yahoo.com> Hi all,? Just a reminder that is a selection made by SO.. That's mean GNSO, in our case. There exists chance that any other constituency boost another candidate. And also remembering that any person who have been a Mentor could invite someone else for this role. I think we could use that last part as an asset. If I am not wrong we have people who had served as NextGen Mentor before.?Best Regards,? JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL ColombiaNPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com Cel. +57 301 743 56 00 Instagram: jmanurojas -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond Mamattah escribi?: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program -?https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree?? Regards,Raymond Mamattah ???Accra, Ghana? On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC wrote: On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. ? ? ? ? Julf _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu Sep 19 02:12:17 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 19 Sep 2024 09:12:17 +1000 Subject: [NCSG-PC] Council meeting absence Message-ID: Hi Julf, Despite best efforts, a time conflict has arisen at the time of the council meeting tomorrow. Could you please send in a proxy form me with Peter as my proxy? My apologies for this. Warmly, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Thu Sep 19 08:53:49 2024 From: julf at Julf.com (Johan Helsingius) Date: Thu, 19 Sep 2024 07:53:49 +0200 Subject: [NCSG-PC] Council meeting absence In-Reply-To: References: Message-ID: Sure! Done! Julf On 19/09/2024 01:12, Tomslin Samme-Nlar wrote: > Hi Julf, > > Despite best efforts, a time conflict has arisen at the time of the > council meeting tomorrow. Could you please send in a proxy form me with > Peter as my proxy? > > My apologies for this. > > Warmly, > Tomslin > From mesumbeslin at gmail.com Fri Sep 20 00:39:33 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 20 Sep 2024 07:39:33 +1000 Subject: [NCSG-PC] Open Public Comment: Second Proceeding for Proposed Language for Draft Sections of the Next Round Applicant Guidebook and others Message-ID: Dear members, ICANN org is seeking input on the two open public comment proceedings below. Let me know if you'd like to volunteer on any one of them. The open public comments are: 1. Second Proceeding for Proposed Language for Draft Sections of the Next Round Applicant Guidebook. - *Link*: https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-proposed-language-for-draft-sections-of-the-next-round-applicant-guidebook-10-09-2024 - *Deadline*: Closes on 21 October 2024. - *Draft document*: https://docs.google.com/document/d/1yl4g5N-BwW6zzr4aHkQgkBBwCmtC62xoOqC6d9aaPS0/edit?usp=sharing 2. Additional Reference Label Generation Rules and Related Updates - *Link*: https://www.icann.org/en/public-comment/proceeding/additional-reference-label-generation-rules-and-related-updates-12-09-2024 - *Deadline*: Closes on 24 October 2024 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Tue Sep 24 01:16:45 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Tue, 24 Sep 2024 08:16:45 +1000 Subject: [NCSG-PC] Fwd: nextgen Mentor nomination In-Reply-To: <490072686.4977608.1726676675586@mail.yahoo.com> References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> Message-ID: What @Juan Manuel Rojas said below, that's it. This is an SO role, so we usually just forward the announcement to our folks, which Andrea already did. I have never known a process where GNSO asks for formal recommendations. My understanding is that all interested candidates from GNSO throw in their ticket in a hat, and the SSC picks from the hat. Warmly, Tomslin On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > Hi all, > Just a reminder that is a selection made by SO.. That's mean GNSO, in our > case. There exists chance that any other constituency boost another > candidate. And also remembering that any person who have been a Mentor > could invite someone else for this role. > > I think we could use that last part as an asset. If I am not wrong we have > people who had served as NextGen Mentor before. > Best Regards, > > *JUAN MANUEL ROJAS, M.Sc.* > Director - MINKA DIGITAL Colombia > NPOC Chair - NCSG/GNSO > M.Sc. Information Technology > > Registered Linux User No.*533108.* > http://www.jmanurojas.com > > > *Cel. +57 301 743 56 00Instagram: jmanurojas* > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ > PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ > ------END GEEK CODE BLOCK------ > > > > > > > > > El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond > Mamattah escribi?: > > > Let us agree that among the responsibilities for being a mentor is related > to actual policy work. But are we trying to say it is only those with > council experience that have experience in the policy process? I don't > think so. > > Here is the document that gives more information on the mentoring program > - > https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf > > I suggest we open the opportunity to those who dont even have council > experience, especially when the NextGen programme introduces new people to > the ICANN family. Hope you agree ? > > Regards, > Raymond Mamattah > [image: linkedin] [image: > facebook] [image: twitter] > > Accra, Ghana > > > On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > > On 18/09/2024 16:54, Raymond Mamattah wrote: > > > I thought the person should rather have been a NextGen before. That will > > allow the person to speak from experience on how the program is all > about. > > That is a good point, but I guess it depends on what kind of support/ > experience/guidance the mentor is supposed to provide - support for > being on the nextgen program or support in actual policy work in ICANN. > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Sep 24 09:06:30 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 24 Sep 2024 08:06:30 +0200 Subject: [NCSG-PC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session In-Reply-To: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> References: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> Message-ID: <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session Date: Mon, 23 Sep 2024 22:30:17 +0000 From: Carlos Reyes via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Carlos Reyes To: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning Hello, all. There is a 90-minute plenary session scheduled for 10:30?12:00 local time in Istanbul, T?rkiye on Wednesday, 13 November 2024. The joint proposal from the ALAC and GAC is available here: https://community.icann.org/x/DQBhFQ The first step is to convene a planning team. *Please let me know by Monday, 30 September 2024, if you would like to be part of the planning team.*?The goal is to have a few planning calls in the coming weeks. Building on previous plenary session experiences, my colleagues and I will facilitate your planning efforts.We look forward to working with you. Best, Carlos and the ICANN81 plenary session planning support team Carlos Reyes Senior Policy Director Internet Corporation for Assigned Names and Numbers Washington, D.C. Engagement Center From andrea.glandon at icann.org Tue Sep 24 16:21:03 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Tue, 24 Sep 2024 13:21:03 +0000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> Message-ID: <6F988A42-56FD-4C3C-AE38-0EEA76CB92F4@icann.org> Hello all, I have reached out to the NextGen program to get more information about how this works and who they are receiving the appointment from. I looked at the SSC wiki page and I don?t see this position listed as one that they choose. The NextGen mentor is appointed by the SO (GNSO). Thanks! Kind Regards, Andrea From: NCSG-PC on behalf of Tomslin Samme-Nlar Date: Monday, September 23, 2024 at 17:17 To: Juan Manuel Rojas Cc: "ncsg-pc at lists.ncsg.is" Subject: [Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination What @Juan Manuel Rojas said below, that's it. This is an SO role, so we usually just forward the announcement to our folks, which Andrea already did. I have never known a process where GNSO asks for formal recommendations. My understanding is that all interested candidates from GNSO throw in their ticket in a hat, and the SSC picks from the hat. Warmly, Tomslin On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC > wrote: Hi all, Just a reminder that is a selection made by SO.. That's mean GNSO, in our case. There exists chance that any other constituency boost another candidate. And also remembering that any person who have been a Mentor could invite someone else for this role. I think we could use that last part as an asset. If I am not wrong we have people who had served as NextGen Mentor before. Best Regards, JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL Colombia NPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com [jmanurojas.com] Cel. +57 301 743 56 00 Instagram: jmanurojas -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond Mamattah > escribi?: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program - https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree ? Regards, Raymond Mamattah [Image removed by sender. linkedin][linkedin.com] [Image removed by sender. facebook] [facebook.com] [Image removed by sender. twitter] [twitter.com] Accra, Ghana On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC > wrote: On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. Julf _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Sep 24 16:32:57 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 24 Sep 2024 15:32:57 +0200 Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session In-Reply-To: References: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> Message-ID: <3e47993d-d461-44c1-a415-ede617855794@Julf.com> Dear Pedro, While the "fair share" (for those who aren't familiar with the discussion, the "fair" is telco newspeak, and pretty much the opposite of what most of the Internet would consider fair) discussion is a very important one, it is pretty well outside the scope for ICANN (and especially GNSO). The discussion is going on in communities such as ISOC and network operator groups and forums (and to some degree the RIRs). Julf On 24/09/2024 15:05, Pedro de Perdig?o Lana wrote: > Dear Julf, > > One thing that I see missing from that list, and which is becoming > increasingly important, is a debate about network fees/fair share > proposals. Maybe we can suggest it? If we need to be a part of the > planning team to suggest things, I would like to candidate myself to > help there (: > > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Coordination/Board/EC @ISOC BR ,NCUC > & NCSG > (ICANN), > YouthLACIGF ,IODA and > CC Brasil > This message is restricted to the sender and recipient(s). If received > by mistake, please reply informing it. > > > Em ter., 24 de set. de 2024 ?s 03:06, Johan Helsingius via NCSG-EC > > escreveu: > > > > > -------- Forwarded Message -------- > Subject:? ? ? ? [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary > Session > Date:? ?Mon, 23 Sep 2024 22:30:17 +0000 > From:? ?Carlos Reyes via SOAC-Leaders-ICANNMeeting-Planning > > > Reply-To:? ? ? ?Carlos Reyes > > To:? ? ?Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > > > > > > Hello, all. > > There is a 90-minute plenary session scheduled for 10:30?12:00 local > time in Istanbul, T?rkiye on Wednesday, 13 November 2024. The joint > proposal from the ALAC and GAC is available here: > https://community.icann.org/x/DQBhFQ > > > > > The first step is to convene a planning team. *Please let me know by > Monday, 30 September 2024, if you would like to be part of the planning > team.*?The goal is to have a few planning calls in the coming weeks. > > Building on previous plenary session experiences, my colleagues and I > will facilitate your planning efforts.We look forward to working > with you. > > Best, > Carlos and the ICANN81 plenary session planning support team > > Carlos Reyes > > Senior Policy Director > > Internet Corporation for Assigned Names and Numbers > > Washington, D.C. Engagement Center > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > From julf at Julf.com Tue Sep 24 17:58:22 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 24 Sep 2024 16:58:22 +0200 Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session In-Reply-To: References: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> <3e47993d-d461-44c1-a415-ede617855794@Julf.com> Message-ID: <40f907c9-7f8f-459a-8ab9-4c05a4472694@Julf.com> Your assumption was perfectly justified. It is definitely on the radar for ALAC and GAC. Anyway, I don't think there is a way to add topics any more. Julf On 24/09/2024 16:00, Pedro de Perdig?o Lana wrote: > Oops, forget what I said then. Since some regional ICANN-connect > entities were discussing the issue (such as LACNIC and RIPE), I thought > it was also a topic of interest within ICANN - the AI Act being listed > there also gave me the impression that the scope was a bit broader. > > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Coordination/Board/EC @ISOC BR ,NCUC > & NCSG > (ICANN), > YouthLACIGF ,IODA and > CC Brasil > This message is restricted to the sender and recipient(s). If received > by mistake, please reply informing it. > > > Em ter., 24 de set. de 2024 ?s 10:33, Johan Helsingius > escreveu: > > Dear Pedro, > > While the "fair share" (for those who aren't familiar with the > discussion, the "fair" is telco newspeak, and pretty much the > opposite of what most of the Internet would consider fair) > discussion is a very important one, it is pretty well outside > the scope for ICANN (and especially GNSO). The discussion > is going on in communities such as ISOC and network operator > groups and forums (and to some degree the RIRs). > > ? ? ? ? Julf > > > On 24/09/2024 15:05, Pedro de Perdig?o Lana wrote: > > Dear Julf, > > > > One thing that I see missing from that list, and which is becoming > > increasingly important, is a debate about network fees/fair share > > proposals. Maybe we can suggest it? If we need to be a part of the > > planning team to suggest things, I would like to candidate myself to > > help there (: > > > > Cordially, > > > > *Pedro de Perdig?o Lana* > > Lawyer >, GEDAI/UFPR > > > > Researcher > > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > > Coordination/Board/EC @ISOC BR >,NCUC > > > & NCSG > > >(ICANN), > > YouthLACIGF >,IODA > and > > CC Brasil > > > This message is restricted to the sender and recipient(s). If > received > > by mistake, please reply informing it. > > > > > > Em ter., 24 de set. de 2024 ?s 03:06, Johan Helsingius via NCSG-EC > > > >> escreveu: > > > > > > > > > >? ? ?-------- Forwarded Message -------- > >? ? ?Subject:? ? ? ? [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 > Plenary > >? ? ?Session > >? ? ?Date:? ?Mon, 23 Sep 2024 22:30:17 +0000 > >? ? ?From:? ?Carlos Reyes via SOAC-Leaders-ICANNMeeting-Planning > >? ? ? > >? ? ? >> > >? ? ?Reply-To:? ? ? ?Carlos Reyes > >? ? ?>> > >? ? ?To:? ? ?Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > >? ? ? > >? ? ? >> > > > > > > > >? ? ?Hello, all. > > > >? ? ?There is a 90-minute plenary session scheduled for > 10:30?12:00 local > >? ? ?time in Istanbul, T?rkiye on Wednesday, 13 November 2024. The > joint > >? ? ?proposal from the ALAC and GAC is available here: > > https://community.icann.org/x/DQBhFQ > > >? ? ? > > >? ? ? > >? ? ? >> > > > >? ? ?The first step is to convene a planning team. *Please let me > know by > >? ? ?Monday, 30 September 2024, if you would like to be part of > the planning > >? ? ?team.*?The goal is to have a few planning calls in the coming > weeks. > > > >? ? ?Building on previous plenary session experiences, my > colleagues and I > >? ? ?will facilitate your planning efforts.We look forward to working > >? ? ?with you. > > > >? ? ?Best, > >? ? ?Carlos and the ICANN81 plenary session planning support team > > > >? ? ?Carlos Reyes > > > >? ? ?Senior Policy Director > > > >? ? ?Internet Corporation for Assigned Names and Numbers > > > >? ? ?Washington, D.C. Engagement Center > > > >? ? ?_______________________________________________ > >? ? ?NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > >? ? ? > > > > From pedrodeperdigaolana at gmail.com Tue Sep 24 16:05:20 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Tue, 24 Sep 2024 10:05:20 -0300 Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session In-Reply-To: <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> References: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> Message-ID: Dear Julf, One thing that I see missing from that list, and which is becoming increasingly important, is a debate about network fees/fair share proposals. Maybe we can suggest it? If we need to be a part of the planning team to suggest things, I would like to candidate myself to help there (: Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Coordination/Board/EC @ ISOC BR , NCUC & NCSG (ICANN), YouthLACIGF , IODA and CC Brasil This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em ter., 24 de set. de 2024 ?s 03:06, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > > > > -------- Forwarded Message -------- > Subject: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary > Session > Date: Mon, 23 Sep 2024 22:30:17 +0000 > From: Carlos Reyes via SOAC-Leaders-ICANNMeeting-Planning > > Reply-To: Carlos Reyes > To: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > > > > > Hello, all. > > There is a 90-minute plenary session scheduled for 10:30?12:00 local > time in Istanbul, T?rkiye on Wednesday, 13 November 2024. The joint > proposal from the ALAC and GAC is available here: > https://community.icann.org/x/DQBhFQ > > > The first step is to convene a planning team. *Please let me know by > Monday, 30 September 2024, if you would like to be part of the planning > team.* The goal is to have a few planning calls in the coming weeks. > > Building on previous plenary session experiences, my colleagues and I > will facilitate your planning efforts.We look forward to working with you. > > Best, > Carlos and the ICANN81 plenary session planning support team > > Carlos Reyes > > Senior Policy Director > > Internet Corporation for Assigned Names and Numbers > > Washington, D.C. Engagement Center > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Tue Sep 24 17:00:08 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Tue, 24 Sep 2024 11:00:08 -0300 Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary Session In-Reply-To: <3e47993d-d461-44c1-a415-ede617855794@Julf.com> References: <2D8C97CE-4064-479A-BBFD-3427744F95E1@icann.org> <1b322dd1-5af0-48c3-8f0f-f2337eb4be01@Julf.com> <3e47993d-d461-44c1-a415-ede617855794@Julf.com> Message-ID: Oops, forget what I said then. Since some regional ICANN-connect entities were discussing the issue (such as LACNIC and RIPE), I thought it was also a topic of interest within ICANN - the AI Act being listed there also gave me the impression that the scope was a bit broader. Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Coordination/Board/EC @ ISOC BR , NCUC & NCSG (ICANN), YouthLACIGF , IODA and CC Brasil This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em ter., 24 de set. de 2024 ?s 10:33, Johan Helsingius escreveu: > Dear Pedro, > > While the "fair share" (for those who aren't familiar with the > discussion, the "fair" is telco newspeak, and pretty much the > opposite of what most of the Internet would consider fair) > discussion is a very important one, it is pretty well outside > the scope for ICANN (and especially GNSO). The discussion > is going on in communities such as ISOC and network operator > groups and forums (and to some degree the RIRs). > > Julf > > > On 24/09/2024 15:05, Pedro de Perdig?o Lana wrote: > > Dear Julf, > > > > One thing that I see missing from that list, and which is becoming > > increasingly important, is a debate about network fees/fair share > > proposals. Maybe we can suggest it? If we need to be a part of the > > planning team to suggest things, I would like to candidate myself to > > help there (: > > > > Cordially, > > > > *Pedro de Perdig?o Lana* > > Lawyer , GEDAI/UFPR > > Researcher > > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > > Coordination/Board/EC @ISOC BR ,NCUC > > & NCSG > > (ICANN), > > YouthLACIGF ,IODA and > > CC Brasil > > This message is restricted to the sender and recipient(s). If received > > by mistake, please reply informing it. > > > > > > Em ter., 24 de set. de 2024 ?s 03:06, Johan Helsingius via NCSG-EC > > > escreveu: > > > > > > > > > > -------- Forwarded Message -------- > > Subject: [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Plenary > > Session > > Date: Mon, 23 Sep 2024 22:30:17 +0000 > > From: Carlos Reyes via SOAC-Leaders-ICANNMeeting-Planning > > > > > > Reply-To: Carlos Reyes > > > > To: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > > > > > > > > > > > > Hello, all. > > > > There is a 90-minute plenary session scheduled for 10:30?12:00 local > > time in Istanbul, T?rkiye on Wednesday, 13 November 2024. The joint > > proposal from the ALAC and GAC is available here: > > https://community.icann.org/x/DQBhFQ > > > > > > > > > > The first step is to convene a planning team. *Please let me know by > > Monday, 30 September 2024, if you would like to be part of the > planning > > team.* The goal is to have a few planning calls in the coming weeks. > > > > Building on previous plenary session experiences, my colleagues and I > > will facilitate your planning efforts.We look forward to working > > with you. > > > > Best, > > Carlos and the ICANN81 plenary session planning support team > > > > Carlos Reyes > > > > Senior Policy Director > > > > Internet Corporation for Assigned Names and Numbers > > > > Washington, D.C. Engagement Center > > > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Tue Sep 24 22:09:44 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Wed, 25 Sep 2024 05:09:44 +1000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: <6F988A42-56FD-4C3C-AE38-0EEA76CB92F4@icann.org> References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> <6F988A42-56FD-4C3C-AE38-0EEA76CB92F4@icann.org> Message-ID: Thank you so much, Andrea. Would GNSO Secretariat know then? Warmly, Tomslin On Tue, 24 Sept 2024, 23:21 Andrea Glandon, wrote: > Hello all, > > > > I have reached out to the NextGen program to get more information about > how this works and who they are receiving the appointment from. I looked at > the SSC wiki page and I don?t see > this position listed as one that they choose. The NextGen mentor is > appointed by the SO (GNSO). > > > > Thanks! > > Kind Regards, > > Andrea > > > > > > *From: *NCSG-PC on behalf of Tomslin > Samme-Nlar > *Date: *Monday, September 23, 2024 at 17:17 > *To: *Juan Manuel Rojas > *Cc: *"ncsg-pc at lists.ncsg.is" > *Subject: *[Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination > > > > What @Juan Manuel Rojas said below, that's it. This > is an SO role, so we usually just forward the announcement to our folks, > which Andrea already did. I have never known a process where GNSO asks for > formal recommendations. My understanding is that all interested candidates > from GNSO throw in their ticket in a hat, and the SSC picks from the hat. > > > > Warmly, > > Tomslin > > > > > > > > On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > > Hi all, > Just a reminder that is a selection made by SO.. That's mean GNSO, in our > case. There exists chance that any other constituency boost another > candidate. And also remembering that any person who have been a Mentor > could invite someone else for this role. > > > > I think we could use that last part as an asset. If I am not wrong we have > people who had served as NextGen Mentor before. > > Best Regards, > > > > *JUAN MANUEL ROJAS, M.Sc.* > > Director - MINKA DIGITAL Colombia > > NPOC Chair - NCSG/GNSO > > M.Sc. Information Technology > > > > Registered Linux User No.*533108.* > > http://www.jmanurojas.com [jmanurojas.com] > > > > > > *Cel. +57 301 743 56 00 Instagram: jmanurojas* > > > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ > PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ > ------END GEEK CODE BLOCK------ > > > > > > > > > > > > > El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond > Mamattah escribi?: > > > > > > Let us agree that among the responsibilities for being a mentor is related > to actual policy work. But are we trying to say it is only those with > council experience that have experience in the policy process? I don't > think so. > > > > Here is the document that gives more information on the mentoring program > - > https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf > > > > I suggest we open the opportunity to those who dont even have council > experience, especially when the NextGen programme introduces new people to > the ICANN family. Hope you agree ? > > > > Regards, > > Raymond Mamattah > > [image: Image removed by sender. linkedin][linkedin.com] > > [image: Image removed by sender. facebook] [facebook.com] > > [image: Image removed by sender. twitter] [twitter.com] > > > > Accra, Ghana > > > > > > On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > > On 18/09/2024 16:54, Raymond Mamattah wrote: > > > I thought the person should rather have been a NextGen before. That will > > allow the person to speak from experience on how the program is all > about. > > That is a good point, but I guess it depends on what kind of support/ > experience/guidance the mentor is supposed to provide - support for > being on the nextgen program or support in actual policy work in ICANN. > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Sep 24 22:16:56 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 24 Sep 2024 21:16:56 +0200 Subject: [NCSG-PC] Fwd: Invitation for input: "Perspectives on Registration Data Accuracy" In-Reply-To: References: Message-ID: <465a6ec3-2f04-4f8e-8ae6-6abc19b9a99f@Julf.com> -------- Forwarded Message -------- Subject: Invitation for input: "Perspectives on Registration Data Accuracy" Date: Tue, 24 Sep 2024 18:08:05 +0000 From: aheineman at godaddy.com To: Johan Helsingius CC: Zoe Bonython , Sarah Wyld Hello Julf! The RrSG is planning our ICANN81 session ?/Perspectives on Registration Data Accuracy/?, a listening session focused on registration data accuracy with inputs from various Community viewpoints. This session will include breakout discussions in person and on the Zoom, taking?place at 16:30 ? 17:30 local time on Monday, 11 November 2024. We are asking for your input as a group representing the perspective of the registrant to help kick start the discussion by sharing your thoughts on *what accuracy means in the context of domain name registration data*. We are not looking for official vetted SG/SO/AC Positions, but rather for*key perspectives on the topic from those who are directly involved.* Our intent is to provide the perspective on screen and in the slide deck, identified by group type but not naming who contributed the text. Would you be able to assist us with getting *brief *input from the registrant perspective? We?re reaching out to you as NCSG chair but you are of course welcome to delegate this to someone else in the NCSG We don?t need the actual input right away, just a yes or no to whether your group will be able to provide input to the session; then we?d need the final text from you in the week of October 14th. Here are some questions to spark discussion (these may already be familiar to you): * What does it mean for registration data to be accurate? * What concrete effects have we seen from inaccurate data, how is it stopping legitimate things from happening? * What processes should be in place to ensure data is accurate? Do those processes pose risks of their own? We look forward to hearing back from you and please don?t hesitate to reach out if you have any questions about this request. Thank you, Ashley Heineman Chair, RrSG From andrea.glandon at icann.org Tue Sep 24 23:13:08 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Tue, 24 Sep 2024 20:13:08 +0000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> <6F988A42-56FD-4C3C-AE38-0EEA76CB92F4@icann.org> Message-ID: <17C772E9-03AB-4779-80A7-528E5EA47DE2@icann.org> You?re welcome! I am chatting with the GNSO Secretariat about this as well. Kind Regards, Andrea From: Tomslin Samme-Nlar Date: Tuesday, September 24, 2024 at 14:10 To: Andrea Glandon Cc: Juan Manuel Rojas , ncsg-pc Subject: Re: [Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination Thank you so much, Andrea. Would GNSO Secretariat know then? Warmly, Tomslin On Tue, 24 Sept 2024, 23:21 Andrea Glandon, > wrote: Hello all, I have reached out to the NextGen program to get more information about how this works and who they are receiving the appointment from. I looked at the SSC wiki page and I don?t see this position listed as one that they choose. The NextGen mentor is appointed by the SO (GNSO). Thanks! Kind Regards, Andrea From: NCSG-PC > on behalf of Tomslin Samme-Nlar > Date: Monday, September 23, 2024 at 17:17 To: Juan Manuel Rojas > Cc: "ncsg-pc at lists.ncsg.is" > Subject: [Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination What @Juan Manuel Rojas said below, that's it. This is an SO role, so we usually just forward the announcement to our folks, which Andrea already did. I have never known a process where GNSO asks for formal recommendations. My understanding is that all interested candidates from GNSO throw in their ticket in a hat, and the SSC picks from the hat. Warmly, Tomslin On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC > wrote: Hi all, Just a reminder that is a selection made by SO.. That's mean GNSO, in our case. There exists chance that any other constituency boost another candidate. And also remembering that any person who have been a Mentor could invite someone else for this role. I think we could use that last part as an asset. If I am not wrong we have people who had served as NextGen Mentor before. Best Regards, JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL Colombia NPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com [jmanurojas.com] Cel. +57 301 743 56 00 Instagram: jmanurojas -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond Mamattah > escribi?: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program - https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree ? Regards, Raymond Mamattah Error! Filename not specified.[linkedin.com] Error! Filename not specified. [facebook.com] Error! Filename not specified. [twitter.com] Accra, Ghana On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC > wrote: On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. Julf _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Thu Sep 26 17:15:38 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Thu, 26 Sep 2024 14:15:38 +0000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> Message-ID: Hello all, Is Razoana Moslam the official NCSG choice to be put in the hat for GNSO NextGen Mentor? Thanks! Kind Regards, Andrea From: NCSG-PC on behalf of Tomslin Samme-Nlar Date: Monday, September 23, 2024 at 17:17 To: Juan Manuel Rojas Cc: "ncsg-pc at lists.ncsg.is" Subject: [Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination What @Juan Manuel Rojas said below, that's it. This is an SO role, so we usually just forward the announcement to our folks, which Andrea already did. I have never known a process where GNSO asks for formal recommendations. My understanding is that all interested candidates from GNSO throw in their ticket in a hat, and the SSC picks from the hat. Warmly, Tomslin On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC > wrote: Hi all, Just a reminder that is a selection made by SO.. That's mean GNSO, in our case. There exists chance that any other constituency boost another candidate. And also remembering that any person who have been a Mentor could invite someone else for this role. I think we could use that last part as an asset. If I am not wrong we have people who had served as NextGen Mentor before. Best Regards, JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL Colombia NPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com [jmanurojas.com] Cel. +57 301 743 56 00 Instagram: jmanurojas -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond Mamattah > escribi?: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program - https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree ? Regards, Raymond Mamattah [Image removed by sender. linkedin][linkedin.com] [Image removed by sender. facebook] [facebook.com] [Image removed by sender. twitter] [twitter.com] Accra, Ghana On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC > wrote: On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. Julf _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu Sep 26 22:56:49 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 27 Sep 2024 05:56:49 +1000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> Message-ID: Hi Andrea, Thanks for the question. I don't think we have an official name yet nor have done anything further with it, since we weren't sure of the process. I have one other interested candidate contact me as well. If we are expected to put forward an officially supported candidate, then I have to make the call on the mailing list to give everyone a fair chance. Once you confirm, I will do that. Warmly, Tomslin On Fri, 27 Sept 2024 at 00:15, Andrea Glandon wrote: > Hello all, > > > > Is Razoana Moslam the official NCSG choice to be put in the hat for GNSO > NextGen Mentor? > > > > Thanks! > > Kind Regards, > > Andrea > > > > > > *From: *NCSG-PC on behalf of Tomslin > Samme-Nlar > *Date: *Monday, September 23, 2024 at 17:17 > *To: *Juan Manuel Rojas > *Cc: *"ncsg-pc at lists.ncsg.is" > *Subject: *[Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination > > > > What @Juan Manuel Rojas said below, that's it. This > is an SO role, so we usually just forward the announcement to our folks, > which Andrea already did. I have never known a process where GNSO asks for > formal recommendations. My understanding is that all interested candidates > from GNSO throw in their ticket in a hat, and the SSC picks from the hat. > > > > Warmly, > > Tomslin > > > > > > > > On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > > Hi all, > Just a reminder that is a selection made by SO.. That's mean GNSO, in our > case. There exists chance that any other constituency boost another > candidate. And also remembering that any person who have been a Mentor > could invite someone else for this role. > > > > I think we could use that last part as an asset. If I am not wrong we have > people who had served as NextGen Mentor before. > > Best Regards, > > > > *JUAN MANUEL ROJAS, M.Sc.* > > Director - MINKA DIGITAL Colombia > > NPOC Chair - NCSG/GNSO > > M.Sc. Information Technology > > > > Registered Linux User No.*533108.* > > http://www.jmanurojas.com [jmanurojas.com] > > > > > > *Cel. +57 301 743 56 00 Instagram: jmanurojas* > > > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ > PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ > ------END GEEK CODE BLOCK------ > > > > > > > > > > > > > El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond > Mamattah escribi?: > > > > > > Let us agree that among the responsibilities for being a mentor is related > to actual policy work. But are we trying to say it is only those with > council experience that have experience in the policy process? I don't > think so. > > > > Here is the document that gives more information on the mentoring program > - > https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf > > > > I suggest we open the opportunity to those who dont even have council > experience, especially when the NextGen programme introduces new people to > the ICANN family. Hope you agree ? > > > > Regards, > > Raymond Mamattah > > [image: Image removed by sender. linkedin][linkedin.com] > > [image: Image removed by sender. facebook] [facebook.com] > > [image: Image removed by sender. twitter] [twitter.com] > > > > Accra, Ghana > > > > > > On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > > On 18/09/2024 16:54, Raymond Mamattah wrote: > > > I thought the person should rather have been a NextGen before. That will > > allow the person to speak from experience on how the program is all > about. > > That is a good point, but I guess it depends on what kind of support/ > experience/guidance the mentor is supposed to provide - support for > being on the nextgen program or support in actual policy work in ICANN. > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Thu Sep 26 23:03:04 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Thu, 26 Sep 2024 20:03:04 +0000 Subject: [NCSG-PC] [Ext] Re: Fwd: nextgen Mentor nomination In-Reply-To: References: <397d5e34-e49b-4bf1-86b4-f38ea1c96322@Julf.com> <9488b29f-84f4-4620-b431-df5a9c587075@Julf.com> <490072686.4977608.1726676675586@mail.yahoo.com> , Message-ID: <06735B03-D491-42D8-B451-4A39499C1FEF@icann.org> Hi Tomslin, Yes, please issue a call. There does need to be an official candidate that will go into the hat for GNSO. I am hoping there will be some changes next year when this comes around again. I?m working with the new person in charge of this program. Thanks! Andrea On Sep 26, 2024, at 2:57?PM, Tomslin Samme-Nlar wrote: ? Hi Andrea, Thanks for the question. I don't think we have an official name yet nor have done anything further with it, since we weren't sure of the process. I have one other interested candidate contact me as well. If we are expected to put forward an officially supported candidate, then I have to make the call on the mailing list to give everyone a fair chance. Once you confirm, I will do that. Warmly, Tomslin On Fri, 27 Sept 2024 at 00:15, Andrea Glandon > wrote: Hello all, Is Razoana Moslam the official NCSG choice to be put in the hat for GNSO NextGen Mentor? Thanks! Kind Regards, Andrea From: NCSG-PC > on behalf of Tomslin Samme-Nlar > Date: Monday, September 23, 2024 at 17:17 To: Juan Manuel Rojas > Cc: "ncsg-pc at lists.ncsg.is" > Subject: [Ext] Re: [NCSG-PC] Fwd: nextgen Mentor nomination What @Juan Manuel Rojas said below, that's it. This is an SO role, so we usually just forward the announcement to our folks, which Andrea already did. I have never known a process where GNSO asks for formal recommendations. My understanding is that all interested candidates from GNSO throw in their ticket in a hat, and the SSC picks from the hat. Warmly, Tomslin On Thu, 19 Sept 2024 at 02:24, Juan Manuel Rojas via NCSG-PC > wrote: Hi all, Just a reminder that is a selection made by SO.. That's mean GNSO, in our case. There exists chance that any other constituency boost another candidate. And also remembering that any person who have been a Mentor could invite someone else for this role. I think we could use that last part as an asset. If I am not wrong we have people who had served as NextGen Mentor before. Best Regards, JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL Colombia NPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com [jmanurojas.com] Cel. +57 301 743 56 00 Instagram: jmanurojas -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ El mi?rcoles, 18 de septiembre de 2024, 10:22:35 a.m. GMT-5, Raymond Mamattah > escribi?: Let us agree that among the responsibilities for being a mentor is related to actual policy work. But are we trying to say it is only those with council experience that have experience in the policy process? I don't think so. Here is the document that gives more information on the mentoring program - https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13sep23-en.pdf I suggest we open the opportunity to those who dont even have council experience, especially when the NextGen programme introduces new people to the ICANN family. Hope you agree ? Regards, Raymond Mamattah [Image removed by sender. linkedin][linkedin.com] [Image removed by sender. facebook] [facebook.com] [Image removed by sender. twitter] [twitter.com] Accra, Ghana On Wed, Sep 18, 2024 at 3:12?PM Johan Helsingius via NCSG-PC > wrote: On 18/09/2024 16:54, Raymond Mamattah wrote: > I thought the person should rather have been a NextGen before. That will > allow the person to speak from experience on how the program is all about. That is a good point, but I guess it depends on what kind of support/ experience/guidance the mentor is supposed to provide - support for being on the nextgen program or support in actual policy work in ICANN. Julf _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is] -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Sep 27 09:13:23 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 27 Sep 2024 08:13:23 +0200 Subject: [NCSG-PC] Fwd: NOTICE: ICANN Leadership Program Postponed for FY25 In-Reply-To: References: Message-ID: <0eb486e2-0a09-457e-9743-8ca154db8742@Julf.com> FYI Julf -------- Forwarded Message -------- Subject: [ICANN Community Leaders] NOTICE: ICANN Leadership Program Postponed for FY25 Date: Thu, 26 Sep 2024 21:39:44 +0000 From: Mary Wong via SO-AC-SG-CLeaders Reply-To: Mary Wong To: soac-chairs at icann.org , so-ac-sg-cleaders at icann.org CC: Sally Costerton , Ergys Ramaj Dear community leaders, Around this time of year, we would typically have reached out to you for nominations to the ICANN Leadership Program . Due to current funding constraints, however, we wish to inform you that the program is being postponed and will not take place in FY25. We are planning to request funds for the program to take place in FY26 and will keep you updated on further developments. Thank you for your understanding and your long-standing support for the program. Best regards, Ergys & Mary