Date: Wednesday, 08 June 2022
Time: 07:00 - 08:00 UTC (for the time in various time zones click here)
How do I participate in this meeting?
English Conference ID = 1638
ZOOM REGISTRATION REQUIRED: https://icann.zoom.us/meeting/register/tJEpduqtqjgtG9JgSoVq9GOQgGI7yO0VjfdF
Zoom Recording: EN
Audio Recording: EN
Chat: EN
Transcript: EN
Participants: Olivier Crépin-Leblond, Holly Raiche, Amrita Chouhury, Aris Ignacio, Samik Kharel, Cheryl Langdon-Orr, Eranga Samararathna, Gopal Tadepalli, Hadia Elminiawi, Justine Chew, Laxmi Prasad Yadav, Isaac Apenteng, Lianna Galstyan, Liubomir Nikiforov, Maureen Hilyard, Nthabiseng Pule, Olévié Kouami, Priyatosh Jana, Puteri Ameena Hishammuddin, Raymond Mamattah, Riccardo Nanni, Satish Babu, Sivasubramanian Muthusamy, Suhaidi Hassan, Prateek Pathak, Cherie Lagakali, Frank Anati, Carine Malor, Ebenezer Obeng, Godsway Akakpo, Christopher Wilkinson
Apologies: None
Staff: Heidi Ullrich, Gisella Gruber, Baher Esmat, Mikhail Anisimov, Yeşim Sağlam
Call Management: Yeşim Sağlam
You are invited to participate the second APRALO Policy Forum Fireside Chat: "Let's Talk About Closed Generics" on Wednesday 08 June 2022 at 07:00 UTC for 60 minutes, where Olivier Crépin-Leblond, Co-Chair of the At-Large Consolidated Policy Working Group (CPWG) will be chatting with his guest, Holly Raiche, APRALO ALAC Member.
As a prelude to the At-Large session on Closed Generics at ICANN 74, we hope you will join Olivier and Holly in an informal conversation regarding new Generic Top-Level Domains (new gTLDs), and what a closed generic is. Pertinent to their conversation is how the issue of closed generics might impact Internet end-users, and in this respect, Holly will also discuss some factors in favour of versus against closed generics being made available for application in the next round of new gTLDs.
Don't forget to pre-register your participation! And if you have any, please let us have your questions on this topic by posting them as comments to this wiki page below; or if you prefer, submit them by emailing staff at staff@atlarge.icann.org
Agenda
1. Roll call - Staff (2 mins)
2. Welcome & Introduction - Olivier Crépin-Leblond (2 mins)
3. Let's chat! - Olivier Crépin-Leblond, Holly Raiche, participants (40 min)
4. Participant Feedback / Poll (10 mins)
5. Concluding Remarks - Holly Raiche and Olivier Crépin-Leblond (3 min)
6. Upcoming Fireside Chat - Justine Chew (1 min)
7. Close
Guest Speaker & Moderator Profiles
| Holly Raiche represents the Asian, Australian and Pacific Islands Regional At-Large Organization (APRALO) as a member of the At-Large Advisory Committee (ALAC). She is a Director and Chair of the Policy Committee of Internet Australia (the Australian Chapter of ISOC). She is also a Director on the Boards of the Australian Communications Consumer Action Network (ACCAN) and the Australian Privacy Foundation and a former Board member of auDA. She is an Adjunct Lecturer at the Law Faculty of UNSW and lectures at the Department of Media and Communications at Sydney University in Internet Cultures and Governance. Holly has an MA and an LLB, and is a non-practicing Solicitor in New South Wales, Australia. |
| Olivier Crépin-Leblond is the Co-Chair of the At-Large Consolidated Policy Working Group (CPWG), a former Chair of the ALAC and a former Chair of EURALO, among other ICANN leadership positions he has held in the past. Olivier is the recipient of the 2020 ICANN Community Excellence Award. |
Olivier and Holly having a good time |
|
|
Participants' Post-Event Comments
"The concept of the fireside chat was a great one. The informality of the session brings the natural and a more comfortable way of explaining and discussing relevant issues like closed generics which was one of the hottest topics currently. The session brought a clearer view on the what closed generics are and the impact it may bring moving forward. Honestly I do not have a broad idea about closed generics but because of this session, it gave a different perspective and new knowledge of the topic at hand. Holly was a great resource and the moderation of Olivier was superb! Their expertise brought light to a somewhat obscure subject matter. I hope that the fireside chat initiative continues as the simple dress down discussion negates the complexities of formal sessions which is easy to grasp even to the common attendees." ~ Aris Ignacio
"The event was very well organized, with experts who know much about the topic. One interesting part is it was very engaging and we the participants were very much involved as well. For instance, I asked a question and I was asked to share my thoughts on what I think about the question, which of course generated into great chats. In all, I think it will be good to do series of by-the-fire-side concept events. Well done to the organising team." ~ Raymond Mamattah
1 Comment
Gopal Tadepalli
Sub: "Generics" and Programmability
Thank you Olivier Crepin-Leblond for a nice conversation on the topic "Closed Generics".
This comment is after the presentation of Gregory Shatan for the CPWG on 20 July 2022.
If domain names that are frequently used on a company's internal network - such as .corp, .mail, and .exchange -- become accepted gTLDs then:
#1. organizations could inadvertently expose data and server access to the Internet.
#2. would-be attackers could easily pick up certificates for domains that are not yet assigned and cache them for use in man-in-the-middle attacks when the specific gTLD is deployed.
My first brush with the idea of "Generic" in programming was with Ada - a well documented language design. The generic unit can be used to create instances of the code that work with actual data types. The data type required is passed in as a parameter when the generic unit is instantiated.
It is (Gu)estimated that 25 percent of queries (or may be more) to the domain name system are for devices and computers that do not exist !!! This is an indicator of "information leaks" as well.
Syntax for "Generic Units" differs for different programming languages but the concept is that the name of the data type (closed generic can double up for this) triggers a code (please read a function). None knows until one runs into this on the run-time.
Question: Is ICANN attempting a rule - based / regulated prevention of abuse of closed generics ?