Logo
ICANN
ICANN
Filtered Search

Are you sure you want to sign out from https://www.icann.org?

If you want to sign out from both https://www.icann.org and ICANN Account, click here.

Public Comment

Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.

هذا المحتوى متوفر فقط باللغة (أو اللغات)

  • English

Name: Katrin Ohlmer
Date: 7 Feb 2025
Affiliation: Dotzon GmbH
Email: [email protected]
Original Public Comment: Third Proceeding for Proposed Language for Draft Sections of Next Round AGB
1) Is the proposed Next Round Applicant Guidebook language for Application Comments (Topic 28: Role of Application Comment) consistent with the relevant SubPro Final Report recommendations?
Yes
2) Is the proposed Next Round Applicant Guidebook language for GAC Member Early Warnings (Topic 30: GAC Consensus Advice and GAC Early Warning) consistent with the relevant SubPro Final Report recommendations?
Yes
3) Is the proposed Next Round Applicant Guidebook language for GAC Advice (Topic 30: GAC Consensus Advice and GAC Early Warning) consistent with the relevant SubPro Final Report recommendations?
Yes
4) Is the proposed Next Round Applicant Guidebook language for Singular/Plural Notification (Topic 24: String Similarity Evaluations) consistent with the relevant SubPro Final Report recommendations?
Yes
5) Is the proposed Next Round Applicant Guidebook language for Objections (Topic 31: Objections and Topic 32: Limited Challenge/Appeal Mechanism) consistent with the relevant SubPro Final Report and IDN EPDP Phase 1 Final Report recommendations?
Yes
6) Is the proposed Next Round Applicant Guidebook language for ICANN Dispute Resolution Procedure (Topic 31: Objections and Topic 32: Limited Challenge/Appeal Mechanism) consistent with the relevant SubPro Final Report and IDN EPDP Phase 1 Final Report recommendations?
Yes
7) Is the proposed Next Round Applicant Guidebook language for ICANN Objection Appeals Procedure (Topic 31: Objections and Topic 32: Limited Challenge/Appeal Mechanism) consistent with the relevant SubPro Final Report and IDN EPDP Phase 1 Final Report recommendations?
Yes
8) Is the proposed Next Round Applicant Guidebook language for New gTLD Program: Next Round Privacy Policy consistent with the relevant SubPro Final Report recommendations?
Yes
9) Is the proposed Next Round Applicant Guidebook language for Post-Contracting consistent with the relevant SubPro Final Report recommendations
Yes
10) Is the proposed Next Round Applicant Guidebook language for DNS Stability consistent with the relevant SubPro Final Report recommendations?
Yes
11) Is the proposed Next Round Applicant Guidebook language for Security and Stability (Topic 26: Security and Stability) consistent with the relevant SubPro Final Report recommendations?
Yes
12) Is the proposed Next Round Applicant Guidebook language for Different TLD Types (Topic 4: Different TLD Types) consistent with the relevant SubPro Final Report recommendations and IDN EPDP Phase 1 Final Report recommendations?
Yes

If no, please explain

The language is consistent with the relevant recommendation, however we would like to offer two amendments which will support applicants and the ICANN community with greater clarity, and streamline the wording of different TLD types. OLD: 1.2.2.1 An applicant that elects to designate its applied-for gTLD string as community-based (hereinafter, a “community gTLD string”) propose to operate the community gTLD string for the benefit of a clearly delineated community [see CPE]. NEW - Delete: "propose to" 1.2.2.1 An applicant that elects to designate its applied-for gTLD string as community-based (hereinafter, a “community gTLD string”) must operate the community gTLD string for the benefit of a clearly delineated community [see CPE]. OLD 1.2.2.4.1. .BRAND TLD is a string that is identical to the textual elements (e.g., a name, word, or phrase) of a registered trademark valid under applicable law, and which the applicant intends to operate as a .BRAND TLD. NEW - Delete: "intends to" 1.2.2.4.1. .BRAND TLD is a string that is identical to the textual elements (e.g., a name, word, or phrase) of a registered trademark valid under applicable law, and which the applicant must operate as a .BRAND TLD.

13) Is the proposed Next Round Applicant Guidebook language for Legal Compliance Check consistent with the relevant SubPro Final Report recommendations and IDN EPDP Phase 1 Final Report recommendations?
Yes