Logo

Tech Day - Shared screen with speaker view
Raymond Mamattah (ICANN70 Fellow)
59:55
Good afternoon from Accra, Ghana
Leonid Todorov- APTLD
01:01:09
Dr. Pepper Harley :))))
Leonid Todorov- APTLD
01:01:48
Kudos to the transcript guys!
Barry Leiba
01:02:01
Breaks are important. Both.
Wes Hardaker
01:11:49
Here's the link to dnsanon: https://ant.isi.edu/software/dnsanon/index.html
Kathy Schnitt
01:12:06
Welcome to Tech Day part 1 of 3. Please use the Q&A Pod to comment and ask questions.We will not be monitoring the chat pod for questions or comments.ICANN’s Expected Standards of Behavior. https://www.icann.org/resources/pages/expected-standards-2016-06-28-en
Claudia Ruiz (ICANN Org)
01:13:38
Welcome to Tech Day part 1 of 3. Please use the Q&A Pod to comment and ask questions.We will not be monitoring the chat pod for questions or comments.ICANN’s Expected Standards of Behavior. https://www.icann.org/resources/pages/expected-standards-2016-06-28-en
Claudia Ruiz (ICANN Org)
01:13:51
Here's the link to dnsanon: https://ant.isi.edu/software/dnsanon/index.html
Kathy Schnitt - ICANN Org.
01:13:53
Here's the link to dnsanon: https://ant.isi.edu/software/dnsanon/index.html
Rubens Kuhl
01:16:46
AS 4134 is China Telecom. So the latency could the Great Firewall.
Rubens Kuhl
01:17:35
"Congestion"
Kathy Schnitt - ICANN Org.
01:25:09
Reminder: Please use the Q&A Pod to comment and ask questions.We will not be monitoring the chat pod for questions or comments.
Herb Waye
01:26:01
Hello everyone. The ICANN Ombuds team will be available at our drop-in virtual Zoom office during meeting hours (9 AM to 5:30 PM daily). You can visit using the following Zoom link: https://icann.zoom.us/j/97816079697 Passcode: Y^63mHe0NTYou will be placed in a waiting room to ensure confidentiality for anyone who may be visiting the office when you join. If you are not allowed entry within a few minutes please send us an email at ombudsman@icann.org
Kimberly Carlson - ICANN Org
01:26:10
Link from slides: https://github.com/SIDN/anteater
Frank Michlick
01:28:48
Thank you for the presentation.
Kathy Schnitt - ICANN Org.
01:29:17
Please use the Q&A Pod to comment and ask questions.We will not be monitoring the chat pod for questions or comments.
Samaneh Tajalizadehkhoob
01:30:36
Well done Giovane!
Kimberly Carlson - ICANN Org
01:31:43
Block 1 presentations can be found here: https://70.schedule.icann.org/meetings/XHTZ2poTeXSDxvPuH#
Kimberly Carlson - ICANN Org
01:35:35
As a reminder, this session includes automated real time transcription. Please note this transcript is not official or authoritative. To view the real time transcription, click on the “Closed Caption” button in the Zoom toolbar.”
Frank Michlick
01:39:00
This is great data too and research.
Kimberly Carlson - ICANN Org
01:39:15
We have a question in the Q&A pod
Eberhard Lisse (.NA)
01:39:54
after the end of the presentation
Kimberly Carlson - ICANN Org
01:41:18
REMINDER: Please use the drop down menu in the chat pod and select "respond to all panelists and attendees." This will allow everyone to view your comment.
Kimberly Carlson - ICANN Org
01:44:46
168 was the max number of total attendees so far
Eberhard Lisse (.NA)
01:54:33
Jaromir, please take note for your closing remarks
Eberhard Lisse (.NA)
01:56:07
If anyone from Greg Aaron’s group is attending and wishes to remark, please make yourself known
Kathy Schnitt - ICANN Org.
01:58:59
Please use the Q&A Pod to comment and ask questions.We will not be monitoring the chat pod for questions or comments.
Jaromír Talíř
01:59:13
Hi Eberhard, confirming making notes.
Rod Rasmussen
02:00:43
A domain name itself can be “compromised” as well as a website. For example, one can use compromised credentials at a registrar to add malicious subdomains to a legitimate domain.
Rod Rasmussen
02:07:17
In the case where a domain itself is compromised (as per my example) and Maciej is correctly calling domain shadowing, you have a different response than a compromised website. Registrar needs to help registrant re-establish control of domain and an external 3rd party may want to block the domain until it is “fixed”. Would be interesting to see things tuned for this type of attack.
Peter Koch
02:07:58
@Rod: thanks for adding this interesting and important scenario (think registrant identification), but given the complexity it might still be useful to not name this a ‘compromised domain’, but emphasize that this aims at the technical control over the name space itself;
Kimberly Carlson - ICANN Org
02:08:05
You can see the asked questions if you click the Answered ta
Rubens Kuhl
02:08:32
Blocking an entire shadowed domain is definitely an overreaction. Minimum collateral damage can be achieved by allowing the non-compromised hosts of the domain.
Kimberly Carlson - ICANN Org
02:09:11
We will return from the break at 15:30 UTC, a quick poll will be conducted. We will use the same URL for part 2, so its not necessary to disconnect
Rod Rasmussen
02:09:14
Great work by the team who put this together - very important to see all of these things in open source!
Peter Koch
02:09:15
@Rod (cntd) not splitting hairs, but in your scenario, detection and mitigation are “different”, also it brings into play the registrar (or reseller) as the “DNS operator” or, more precisely, “DNS zone maintainer”
Kimberly Carlson - ICANN Org
02:09:49
We will return from the break at 15:30 UTC, a quick poll will be conducted. We will use the same URL for part 2, so its not necessary to disconnect