ICANN 75: Difference between revisions
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
*The [[GNSO]] [[PDP|Policy]] Update entailed | *The [[GNSO]] [[PDP|Policy]] Update entailed | ||
** [[PDP]] improvement tracker | ** [[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 | ** [[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. | ||
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 be aligning with [[CcNSO Policy Development Process - IDN Strings|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 [[TLD]]s 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]].<ref>[https://75.schedule.icann.org/prep-week Prep Week, ICANN 75 website]</ref> | * The [[EPDP on Internationalized Domain Names]] has made significant headway. Its aims and methods seem to be aligning with [[CcNSO Policy Development Process - IDN Strings|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 [[TLD]]s 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]].<ref>[https://75.schedule.icann.org/prep-week Prep Week, ICANN 75 website]</ref> | ||
*The Registration [[accuracy]] scoping team is a pre-PDP effort and is currently planning a survey for registrars | *The Registration [[accuracy]] scoping team is a pre-PDP effort and is currently planning a survey for registrars | ||
Revision as of 17:49, 7 September 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 be aligning 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 will 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.