ICANN 75: Difference between revisions
| Line 37: | Line 37: | ||
* The Transfer Policy Review PDP Working Group discussed the Public Comment report concerning the Phase 1A Initial Report | * The Transfer Policy Review PDP Working Group discussed the Public Comment report concerning the Phase 1A Initial Report | ||
==IDNs=== | ===IDNs=== | ||
* The working group for the [[EPDP-IDNs|Expedited Policy Development Process for Internationalized Domain Names]] discussed its progress, namely that it will break the process into "chunks." The WG will publish the Initial Report in two parts. Part 1 will cover charter questions and recommendations about TLD variant management and part 2 will concern charter questions and recommendations about second-level variant management.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref> | * The working group for the [[EPDP-IDNs|Expedited Policy Development Process for Internationalized Domain Names]] discussed its progress, namely that it will break the process into "chunks." The WG will publish the Initial Report in two parts. Part 1 will cover charter questions and recommendations about TLD variant management and part 2 will concern charter questions and recommendations about second-level variant management.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref> | ||
* [[James Caulfield]] of ICANN Org's [[Risk Management]] discussed issues around introducing TLD variant labels and the need for a common understanding and an agreed mechanism to quantify the risks, in terms of likelihood (occurrence) and severity (seriousness of the consequences). He recommended considering the String Similarity Review as a way to understand the proportionality of the proposed Hybrid Model in addressing the risks associated with failure modes. Issues could include denial of service if a user attempts to visit http://example.X, reading it as being the same as http://example.Y, and after typing the address (http://example.X), the connection does not work as http://example.X is not registered. There could be a misconnection if a user attempts to visit http://example.X, reading it as being the same as http://example.Y. After clicking on http://example.Y, the user arrives at a site controlled by a registrant different from http://example.X, or a misconnection due to variants blocked to avoid string similarity.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref> | * [[James Caulfield]] of ICANN Org's [[Risk Management]] discussed issues around introducing TLD variant labels and the need for a common understanding and an agreed mechanism to quantify the risks, in terms of likelihood (occurrence) and severity (seriousness of the consequences). He recommended considering the String Similarity Review as a way to understand the proportionality of the proposed Hybrid Model in addressing the risks associated with failure modes. Issues could include denial of service if a user attempts to visit http://example.X, reading it as being the same as http://example.Y, and after typing the address (http://example.X), the connection does not work as http://example.X is not registered. There could be a misconnection if a user attempts to visit http://example.X, reading it as being the same as http://example.Y. After clicking on http://example.Y, the user arrives at a site controlled by a registrant different from http://example.X, or a misconnection due to variants blocked to avoid string similarity.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref> | ||
Revision as of 17:56, 5 October 2022
 | |
| Dates: | 17-22 September 2022
Annual General Meeting |
| Location: | Kuala Lumpur, Malaysia (Malaysia Time / UTC+8) |
| Venue: | Kuala Lumpur Convention Centre |
| Website: | https://75.schedule.icann.org/ |
ICANN 75 is the first hybrid Annual General Meeting and the second ICANN meeting to be held in Kuala Lumpur, Malaysia. It takes place from September 17 through 22, 2022.
Prep Week[edit | edit source]
The ICANN 75 Prep Week is running from September 6 through 8, 2022.[1]
Presentations[edit | edit source]
- Contractual Compliance spoke about
- its 2022 Registry Agreement audit
- TempSpec-related registration data complaints
- UDRP-related complaints
- DNS Abuse-related complaints of which there were nearly 3500 from June 2021 through May 2022 and the number one hurdle in helping complainants is that they aren’t sending reports to registrars before contacting ICANN.[2]
- its outreach efforts
- The GNSO Policy Update entailed
- PDP improvement tracker
- Policy Development Process to Review the Transfer Policy, namely that the team is currently working on Phase 1b concerning the change of registrant and Phase 1a, whose report was published. It had 34 submissions in response and lots of useful feedback. Six recommendations need to be updated, six others may need review.
- The EPDP on Internationalized Domain Names has made significant headway. Its aims and methods seem to align with ccPDP4. The team has more than 40 questions to address in the charter, but the focus is currently on IDN string similarity and the String Confusion Objection process as well as breaking the EPDP into chunks. The idea is that the first part will concern TLDs and the second part will concern post-delegation and operational issues on the second level; the team is seeking risk assessment expertise from ICANN Organization.[3]
- The Registration accuracy scoping team is a pre-PDP effort and is currently planning a survey for registrars
- The SSAD ODA small team said that ICANN would share its report on the SSAD Light proof of concept the week before ICANN 75.
- The DNS abuse small team is working on "Issue Buckets" to determine which approach works best for each type of abuse issue. It could be structuring voluntary agreements, engaging in ICANN Community outreach, or taking the PDP route.
- The Closed Generics Facilitation arrangement is underway and signifies a new type of process for ICANN.
Topics discussed in KL[edit | edit source]
Whois Disclosure System[edit | edit source]
- ICANN Organization presented its ideas for a WHOIS Disclosure System
Transfer Policy Review PDP[edit | edit source]
- The Transfer Policy Review PDP Working Group discussed the Public Comment report concerning the Phase 1A Initial Report
IDNs[edit | edit source]
- The working group for the Expedited Policy Development Process for Internationalized Domain Names discussed its progress, namely that it will break the process into "chunks." The WG will publish the Initial Report in two parts. Part 1 will cover charter questions and recommendations about TLD variant management and part 2 will concern charter questions and recommendations about second-level variant management.[4]
- James Caulfield of ICANN Org's Risk Management discussed issues around introducing TLD variant labels and the need for a common understanding and an agreed mechanism to quantify the risks, in terms of likelihood (occurrence) and severity (seriousness of the consequences). He recommended considering the String Similarity Review as a way to understand the proportionality of the proposed Hybrid Model in addressing the risks associated with failure modes. Issues could include denial of service if a user attempts to visit http://example.X, reading it as being the same as http://example.Y, and after typing the address (http://example.X), the connection does not work as http://example.X is not registered. There could be a misconnection if a user attempts to visit http://example.X, reading it as being the same as http://example.Y. After clicking on http://example.Y, the user arrives at a site controlled by a registrant different from http://example.X, or a misconnection due to variants blocked to avoid string similarity.[5]
Registration Data Accuracy[edit | edit source]
- The gTLD Registration Data Accuracy Scoping Team discussed options for implementing two recommendations
DNS Abuse[edit | edit source]
- The DNS Abuse Small Team discussed its outputs with the GNSO Council
- The CPH gave a presentation on DNS Abuse Outreach
- The ccNSO's standing committee on DNS Abuse met
- The IPC held a closed working session on DNS Abuse
Universal Acceptance[edit | edit source]
- ALAC held a session for At-Large members and the ICANN community to review results and discuss the next steps from a survey the ALAC conducted with funding from an Additional Budget Request (ABR) in Fiscal Year 2022. ALAC engaged a professional survey organization to conduct a survey on a topic of interest to Internet end users and it decided to focus on IDNs and Universal Acceptance among Indian end users in the Hindi language.[6]
- UASG met with the GNSO Council to figure out how to make UA readiness take hold more quickly around the world
- There was a cross-community session focused on how to drive local change toward UA adoption
- ccNSO held a UA session
- There was a session dedicated to planning for UA day
Internet Fragmentation[edit | edit source]
- There was a plenary on Internet Fragmentation that paid special attention to the impact of legislative developments