Logo
ICANN
ICANN

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.

Contenido disponible solo en los siguientes idiomas

  • English

Name: Ali Issa Ali
Date: 3 Dec 2022
Email: aliissaelimi@gmail.com
Original Public Comment: Registration Data Consensus Policy for gTLDs
Please provide your feedback:
Section 1 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 2 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 3 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 4 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 5 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 6 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 7 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 8 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 9 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 10 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 11 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Section 12 accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Addendum I accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Addendum II accurately reflects the policy recommendations with no issues.
Please provide your feedback:
Implementation Notes accurately reflect the policy recommendations with no issues.
Please provide your feedback:
Background Section accurately reflects the policy recommendations with no issues.
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the AWIP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the ERRP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Protection of IGO and INGO Identifiers in all gTLDs Policy correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the CL&D Policy correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the RNAP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Thick Whois Transition Policy correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Transfer FOA Confirmation correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Transfer FOA Initial Authorization correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the TDRP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Transfer Policy correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the UDRP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the UDRP Rules correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the URS Procedure correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the URS Rules correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the URS Requirements correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the WDRP correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Whois Marketing Restriction Policy correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, is the proposed Advisory Clarifications to the Registry and Registrar Requirements for Whois Data Directory Services correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, is the proposed the RDAP Technical Implementation Guide correct?
Yes
Based on the requirements outlined in the Registration Data Consensus Policy, is the proposed RDAP Response Profile correct?
Yes
Attachment

ALI ISSA PASSEPORT.pdf (323.29 KB)

Summary of Submission

Madame, Monsieur , je soumet mon offre de service et vous prie de trouver cette offre ci-joint.

Je peux vous assurer que je peux mettre en œuvre ce projet dans le délai susmentionné et dans les limites du budget prévisionnel.

Nous vous prions d’agréer, Madame, Monsieur, l’assurance de nos salutations distinguées