09:52:14 From Yeşim Saglam - ICANN Org To Everyone:
Hello, my name is Yeşim Sağlam and I will be monitoring this chat room. In this role, I am the voice for the remote participants. Please note that I will read aloud comments/questions submitted in English within the time set by the Chair of this session.
When submitting a question or comment that you want me to read out loud on the mic, please start with a <QUESTION> and end with a “</QUESTION>” or <COMMENT> </COMMENT>. Text outside these quotes will be considered as part of “chat” and will not be read out loud on the microphone.
To listen to the interpretation, please click on the interpretation icon in the Zoom toolbar and select the language you will listen to and/or speak during this session.
09:52:26 From Yeşim Saglam - ICANN Org To Everyone:
This session also includes automated real time transcription. By clicking on the “closed caption” button in the Zoom toolbar you can view the real time transcription. This transcript is not official or authoritative.
As requested verbally, please rename your sign-in name with your full name. If you do not use your full name (e.g. First Name + Last Name/Surname), you may be removed from this session.
Please note that chat sessions are being archived and are governed by the ICANN Expected Standards of Behavior: http://www.icann.org/en/news/in-focus/accountability/expected-standards.
10:04:19 From Dave Kissoondoyal - ICANN ALAC To Everyone:
Hello everyone, both onsite and online
10:04:53 From Michel TCHONANG CMR To Everyone:
Greetings from Cameroon
10:05:31 From Godsway Kwaku Kubi To Everyone:
Greetings to everyone, I am Godsway Kwaku Kubi connecting from Ghana. It is a great time to connect with you all here for a common goal and networking. I am ever ready to learn, Contribute and network with as many as possible. Connect with me via LinkedIn: https://www.linkedin.com/in/godsway-kubi-3bb5aa191
10:16:18 From Dave Kissoondoyal - ICANN ALAC To Everyone:
It would be good to know about WEB3 and decentralised web
10:16:39 From Godsway Kwaku Kubi To Everyone:
Reacted to "It would be good to ..." with
10:18:43 From Lutz Donnerhacke To Everyone:
Blockchain and Web3 are mostly scam.
10:20:13 From Lutz Donnerhacke To Everyone:
Think About running a copy of Archive.org onto a locally available WORM (Write Once, Read Many) data store. Anywhere, anytime.
10:21:02 From Lutz Donnerhacke To Everyone:
The purpose of such a technology is very narrow and the usage is limited.
10:21:14 From Abdeldjalil Bachar Bong To Everyone:
Reacted to "It would be good to …" with
10:22:01 From Jonathan Zuck To Everyone:
Where do we find the paper on machine learning and DNS Abuse?
10:22:44 From Godsway Kwaku Kubi To Everyone:
Replying to "It would be good to ..."
Web3 is the future
10:23:24 From Shutruk-Nakhunte To Everyone:
I’ve heard CleanDNS and Freename have published a paper about Abuses in Web3 - anyone has a link to it ?
10:27:09 From Lutz Donnerhacke To Everyone:
If blockchain is used for DNS, the Primary Question is: Is ICANN willing to Hand over the Control over the root Zone to the Player with the most computing power?
10:28:26 From Lutz Donnerhacke To Everyone:
If a central decision making process is required, blockchain is out of the play.
10:30:16 From Dave Kissoondoyal - ICANN ALAC To Everyone:
Is it not a R&D at ICANN level warranted for emerging technologies?
10:30:16 From Maud Ashong Elliot ICANN Fellow To Everyone:
Reacted to "It would be good to …" with
10:34:42 From Hadia Elminiawi To Everyone:
Due to the time limitation, please put your questions in the Q&A box and we will get back to you if we are not able to give you an answer during the session
10:36:23 From Harold Arcos To Everyone:
<Q> One of the challenges is the possible collision for name resolution. You consider that ICANN would move towards the search for creating a Third instance that helps Query-Resolve the name query or would move towards an adoption-evolution of the new technology?<Q>
10:37:35 From Sivasubramanian M To Everyone:
@John and @Steve #With icann's strengths of its ability to bring together ry/rs/rirs/givernments/standard bodies, ICANN could 'educate' at strategic levels and forge ahead on what needs to be done on AI / blockchain, not only on identifiers but to make this and other emerging technologies work in a streamlined fashion, with a minimal degree of coordination. All this ICANN alone do.
10:37:40 From Sivasubramanian M To Everyone:
#
10:37:53 From Seun S. Ojedeji To Everyone:
So @John Crain, ICANN is not actively looking into any technilogical breakthrough or solution using blockchain...is that correct?
10:40:00 From Shah Rahman To Everyone:
Q apart from implementing/using emerging technologies application in icann within the remit of ICANN, did ICANN thought parallelly process that might to need aware internet user's and or operator's those providing DNS serivice ?
10:42:05 From Olivier MJ Crepin-Leblond To Everyone:
Here is my question - also copied to the Q&A box: ICANN At-Large was one of the first communities in ICANN to actively promote IPv6. We were also one of the first communities to actively use the WIKI spaces when they got rolled out in ICANN. We held Webinars about DNSSEC, DOI, DOA, alternative naming systems, Satellite Internet etc. etc. Some other parts of the community have repeatedly said, like a broken record, that all of this "stuff" is outside the ICANN Remit - and the bylaws specifically mention that ICANN should focus on topics that are strictly in its remit - thus domain names as they currently exist and IP addresses - even though the distribution of IP addresses isn't strictly in ICANN's mandate. If that is the case, why are you looking at all of these other technologies, many of which are outside ICANN's remit? And what is your mandate to roll out any future technologies? Where is the picket fence for your remit? How do you decide what is in OCTO's remit and what is not? ...and...
10:42:38 From Dave Kissoondoyal - ICANN ALAC To Everyone:
Reacted to "Here is my question ..." with
10:42:47 From Olivier MJ Crepin-Leblond To Everyone:
...Should it be down to ICANN's communities, SOs and ACs to decide on what is in ICANN's remit as far as new technologies are concerned?
10:44:52 From Dave Kissoondoyal - ICANN ALAC To Everyone:
The distinction should be made what ICANN should use as a corporation for its day to day use and technologies for the community. For example a Document Management System will be useful to ICANN for its internal use
10:45:22 From Godsway Kwaku Kubi To Everyone:
Great session
10:46:06 From Michel TCHONANG CMR To Everyone:
Good
10:50:28 From Angle Dimension To Everyone:
A Question to John, is there a team within ICANN tech that is constantly looking and experimenting on these emerging technologies like AI.
I am asking because when you mentioned about use cases, I expected the use case of the SLAM being of the major ones ICANN would be looking into. Training models that will streamline the SLAM tool.
10:52:53 From Dave Kissoondoyal - ICANN ALAC To Everyone:
This is the reason I am asking for a R&D at the level of ICANN independent of the IETF
10:53:03 From Abdeldjalil Bachar Bong To Everyone:
What Sebastian mentioned about interactive translation in Zoom , ISOC are doing until now we can get experience of Them ;
With that option we don’t need a dial out all things is incorporated in Zoom Salon , easy way to
10:57:45 From Bram Fudzulani To Everyone:
I agree with you Dave, going via IETF may not be as agile as John and ICANN team desire it to be
10:58:54 From Dave Kissoondoyal - ICANN ALAC To Everyone:
Perhaps new technologies, opportunities and risks should be included in the agenda of ICANN at a higher level
10:59:32 From Sivasubramanian M To Everyone:
# Without taking a restrained view on scope or mission, in matters related to metering technologies, there is work to do, not only identifiers, not only security / coordination, but also the overall DIRECTIONS that these technologies ought to take. For e.g, AI in the field could either get the earth rid of waste, or, it could put people out of work andl consequently render them homeless, starving and cold. What could ICANN do within and outside DNS? Who all can it bring to the table? #
11:00:09 From Chokri Ben Romdhane To Everyone:
Yes Evolve ICANN Policy and start the regulation of those new trends is a key point
11:00:21 From Chokri Ben Romdhane To Everyone:
+1 Jhon
11:01:40 From Bram Fudzulani To Everyone:
Replying to "+1 Jhon"
Regulations of the new tech trends?
11:01:53 From Chokri Ben Romdhane To Everyone:
I mean new for ICANN OCTO!
11:02:15 From Chokri Ben Romdhane To Everyone:
Reacted to "I mean new for ICANN..." with
11:02:38 From Chokri Ben Romdhane To Everyone:
Removed a reaction from "I mean new for ICANN..."
11:02:52 From Bill Jouris To Everyone:
Any attempt to do summarization will, Ithink, require software that can exercise something resembling judgement. Which seems like several long steps beyond what AI can manage at the moment
11:03:18 From Yeşim Saglam - ICANN Org To Everyone:
Thank you all for your participation. This meeting is now adjourned.
AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
1 Comment
Gopal Tadepalli
Thank you for a very nice session.
DNS is an Application-layer protocol. The Application layer is the top-most layer on the TCP/IP Model as well as the ISO - OSI Reference Model. Every one line out of 7 lines of code in every application is defective. Even if it is 1 in 10 lines, for every 10,00,000 Lines of Code (not a very complex system for the current day contexts) there will be 1,00,000 Lines of Code that is defenctive. Only 33% of the code can be tested.
So, the DNS ought to bank on the Transport Layer that builds on Data encapsulation. Both the ISO-OSI Model and TCP/IP are peer-to-peer at the Transport Layer. The "port" is a unique number assigned to different applications. A port or port number identifies a connection endpoint to direct data to a specific service. It is always associated with a network address such as an IP address
Data encapsulation is a fundamental principle that helps in designing and implementing complex systems. These evolving complex systems maximize resilience at the Trasnport Layer. The IP address is below the transport layer. In a way a double protection is accorded to every machine (in whatever form it is). Also, the "Network Interface Card" is the hardware implementation for Network Layer + Layers below this.
In the ISO - OSI Reference Model : Both Application and Transport Layer have five commonly used protocols. Presentation, Network and Data-Link Layer have four commonly used protocols. Session layer functions on Sockets. Physical layer is all about the connectivity.
Application Layer is "Where a Communication Originates". Transport Layer affixes the header for sending the communication and removes it while receiving. The layers below the transport layer also have respective headers / trailers. The data is thus fully packed and hidden.
Data Encapsulation at: https://drive.google.com/file/d/1WUkkvmDQDBMd7DQOpitmfseFsXER2Uoo/view?usp=sharing
Data Decapsulation at: https://drive.google.com/file/d/1r5aaEdUbG-e0l6jo80UXVmRZCRwkvlYe/view?usp=sharing
The impact of the application layer for sending and receiving data over the internet is minimal and this task is always over standard protocols.
I wish ICANN points this out with every policy made about the DNS. Three possible mechanisms for implementation of the policy at the transport layer can specify the boundary conditions within which the application designer can make any innovation over DNS.