Candidatures / .avocat / ODAC2678T-T94227 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08
§ 1 — Sens de la chaîne Q118·Q120
attorney
a.vɔ.kɑ
§ 2 — Mission et objet Q133
See attachment 133 Mission and purpose of the applied-for gTLD
§ 3 — Engagements et sauvegardes Q164–Q188
| Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169 | Oui à : confiance accrue (Q164), risque pour le consommateur en cas d'abus (Q165), licence ou accréditation (Q166), déclarations à l'État (Q167) |
|---|---|
| PIC de sauvegarde volontaires Q170·Q171 | Aucun · 90 candidatures de la ronde en proposent |
| Registry Voluntary Commitments Q172·Q173 | Aucun · 5 en proposent |
| TLD communautaire Q131·Q132 | |
| Exemption du Code de conduite demandée Q185·Q188 | Non |
§ 4 — Toutes les autres réponses publiées
Toutes les autres réponses que l'ICANN a publiées pour cette candidature, dans l'ordre du formulaire. Les coordonnées (Q17–Q24) sont laissées à la fiche ICANN.
Q212Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q121As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
true
Q134How would you categorize your community?
How would you categorize your community?
See attachment 134 categorize your community
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q135What is the applying entity's connection to the community?
What is the applying entity's connection to the community?
See attachment135 connection with community
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q136How is the community organized? Are there one or multiple organizations ("organizing body") that represent or administer the community?
How is the community organized? Are there one or multiple organizations ("organizing body") that represent or administer the community?
See attachment 136 How is the community organized
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q137Does the community have defined membership requirements, such as registration, licensing, or use of specific communication? Or, do community members self-identify as part of the community?
Does the community have defined membership requirements, such as registration, licensing, or use of specific communication? Or, do community members self-identify as part of the community?
See attachment 137 membership requirements
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q138Where is the community located?
Where is the community located?
The Communauté professionnelle des Avocats is present throughout French territory. Its members are registered on the Tableaux of the 164 Barreaux established within the jurisdiction of the French judicial courts.
Q139What is the estimated size of the community? This should take into account any regions listed in Question 138.
What is the estimated size of the community? This should take into account any regions listed in Question 138.
The Communauté professionnelle des Avocats comprises approximately 78,000 Avocats as a natural person in France and about 30,000 entities through which the Profession d’avocat is practised, distributed among the 164 Barreaux.
Q140What portion of the community do any organizing bodies represent or administer to?
What portion of the community do any organizing bodies represent or administer to?
Each Ordre des Avocats represent Avocats registered in the Barreau they administer. The CNB, represents all the Avocats registered in France. Finally, the Conférence des Bâtonniers represents approximately 45,000 Avocats.
Q141Do the organizing bodies demonstrate active and consistent efforts to engage and connect with the identified community and its members?
Do the organizing bodies demonstrate active and consistent efforts to engage and connect with the identified community and its members?
See attachment 141 efforts to engage with the community
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q142What is the role of the applying entity in the engagement efforts listed in Question 141?
What is the role of the applying entity in the engagement efforts listed in Question 141?
See attachment142 role of the applying entity in the engagement efforts
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q143Are community members aware of the identified community and each other?
Are community members aware of the identified community and each other?
See attachment 143 community awareness
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q144Are community members aware of the applying entity and its intention to apply for a community gTLD?
Are community members aware of the applying entity and its intention to apply for a community gTLD?
See attachment 144 gTLD application awareness
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q145Was there an established presence of the identified community prior to the opening of the application submission period?
Was there an established presence of the identified community prior to the opening of the application submission period?
Yes
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q146Are individuals and groups outside of the identified community aware of the existence of the identified community?
Are individuals and groups outside of the identified community aware of the existence of the identified community?
See attachment 146 outside awareness
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q147Are the pursuits of the identified community enduring and sustainable?
Are the pursuits of the identified community enduring and sustainable?
See attachment 147 enduring and sustainability
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q148Does the string match the name of the identified community?
Does the string match the name of the identified community?
See attachment 148 string match community
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q149Will the general public instinctively think of the community when thinking of the applied-for string?
Will the general public instinctively think of the community when thinking of the applied-for string?
See attachment 149 general public awareness
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q150Are you proposing to include one or more Community Registration Policies in the Registry Agreement (RA) that are unique to the applying entity's applied-for community gTLD?
Are you proposing to include one or more Community Registration Policies in the Registry Agreement (RA) that are unique to the applying entity's applied-for community gTLD?
Yes
Q151.1Please state a specific Community Registration Policy with respect to registration eligibility for community members.
Please state a specific Community Registration Policy with respect to registration eligibility for community members.
Community Registration Policy - Eligibility of Registrants
The Registry Operator must reserve the registration of domain names in the “.AVOCAT” TLD exclusively for natural persons and legal entities belonging to the Communauté professionnelle des Avocats, as defined in the eligibility rules published by the Registry Operator.
The Registry Operator must define and publish the categories of holders eligible to register a “.AVOCAT” domain name, comprising:
• The Avocats;
• The Ordres;
• The Conseil National des Barreaux (CNB);
• The Conférence des Bâtonniers;
• The Centres Régionaux de Formation Professionnelle des Avocats (CRFPA);
• The Caisses Autonomes des Règlements Pécuniaires des Avocats (CARPA);
• The Conseils de discipline;
• The Syndicats and Associations d’avocats;
• The ad hoc structures mandated by the Institutions de la Profession d’avocat;
• The social and/or technical bodies mandated by the Institutions de la Profession d’avocat.
Before registering a “.AVOCAT” domain name, the Registry Operator must verify that the applicant satisfies the eligibility criteria applicable to the relevant holder category, including the applicant's identity, membership of the Communauté professionnelle des Avocats and, where applicable, effective registration on the Tableau of a Barreau.
The Registry Operator must ensure that the holder's eligibility is validated before any “.AVOCAT” domain name is created in the registry database.
The Registry Operator must not permit the automatic registration of a “.AVOCAT” domain name solely on the basis of an application submitted by a Registrar without prior validation of the holder's eligibility in accordance with the eligibility rules published by the Registry Operator.
Q151.2If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
Obligations Applicable to Registrars
The Registry Operator will include the following provisions in its Registry-Registrar Agreement: the Registrar must collect from the applicant the information and supporting documents necessary to verify the applicant's eligibility and transmit them to the Registry Operator in accordance with the procedures established by the Registry Operator.
The Registry Operator will include the following provisions in its Registry-Registrar Agreement: the Registrar must not register a “.AVOCAT” domain name without first obtaining validation of the holder's eligibility from the Registry Operator.
The Registry Operator will include the following provisions in its Registry-Registrar Agreement: the Registrar must retain the necessary information relating to the registration application and cooperate with the Registry Operator in connection with any review concerning a holder's eligibility.
Q151.3If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
Obligations Relating to Registration Agreements
The Registry Operator will include a provision requiring Registrars to include in their Registration Agreements a provision requiring the holder to maintain eligibility to register a “.AVOCAT” domain name throughout the term of the domain name registration.
The Registry Operator will include a provision requiring Registrars to include in their Registration Agreements a provision requiring the holder to notify any change that may affect eligibility for the “.AVOCAT” TLD.
The Registry Operator will include a provision requiring Registrars to include in their Registration Agreements a provision prohibiting the holder from providing inaccurate, incomplete or misleading information concerning eligibility for the “.AVOCAT” TLD.
Q151.4If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
Retention of Evidence and Compliance Monitoring
The Registry Operator must retain the information and supporting documents demonstrating the eligibility of registered holders throughout the term of the domain name registration.
The Registry Operator must implement a monitoring mechanism to verify that holders of “.AVOCAT” domain names continue to satisfy the applicable eligibility criteria throughout the term of the domain name registration.
The Registry Operator must establish a procedure applicable where a holder no longer satisfies the eligibility requirements of the “.AVOCAT” TLD, including loss of Avocat status, removal from the Tableau, dissolution of an entity through which Avocats practise or cessation of membership of the Communauté professionnelle des Avocats.
Q151.5If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
Publication and Review of the Policy
The Registry Operator must develop, implement and publish on its website a registration eligibility policy defining the categories of holders authorised to register a “.AVOCAT” domain name no later than the date on which the “.AVOCAT” TLD is delegated in the DNS.
The Registry Operator must review the registration eligibility policy annually and publish the results of that review, including any amendment to the policy, within thirty (30) days after each anniversary of the effective date of the Registry Agreement.
Q151.6If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
If there is an additional proposed policy, please state the specific Community Registration Policy with respect to registration eligibility for community members.
Limitation of the Policy
This Community Registration Policy applies throughout the entire period of operation of the “.AVOCAT” TLD.
The eligibility restrictions set out in this policy apply to all registrations, renewals and transfers of “.AVOCAT” domain names throughout the entire period of operation of the TLD.
Q152.1State a specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
State a specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
1. General principles applicable to name selection
The Registry Operator must reserve the registration of second-level domain names under the “.AVOCAT” TLD for names that comply with the selection criteria set out in the naming policy published by the Registry Operator.
The Registry Operator must ensure that every “.AVOCAT” domain name registered by a member of the Communauté professionnelle des Avocats constitutes an authenticatable digital identifier having a direct, verifiable and objective connection with the identity, official name or institutional capacity of the registrant.
The Registry Operator must verify that the requested domain name corresponds to:
• The name of the registrant who is an individual Avocat, as registered on the Tableau;
• The full or abbreviated name of the registrant entity through which Avocats practise, as registered on the Tableau;
• The official name, recognised acronym or validated institutional identity, where the registrant is an institutional member of the Communauté professionnelle des Avocats.
The Registry Operator must not authorise the registration of a “.AVOCAT” domain name that has no identifiable connection with the applicant’s name, as registered on the Tableau; full or abbreviated name, as registered on
the Tableau; official name; recognised acronym; or institutional capacity.
The Registry Operator must not authorise the registration of a “.AVOCAT” domain name that generically evokes the title of Avocat or a potentially misleading title, a field of law or an activity falling within those of an Avocat, unless expressly approved in accordance with the rules published by the Registry Operator.
Q152.2If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
2. Criteria applicable to individual Avocats
The Registry Operator must permit an individual Avocat to register only domain names corresponding to their name as registered on the Tableau and as evidenced by the information validated during the eligibility review.
The Registry Operator must permit the following formats by default:
• surname.avocat;
• first-name-surname.avocat.
Examples:
• dupont.avocat;
• jean-dupont.avocat.
The Registry Operator must reserve and block the registration of the format consisting solely of the concatenation of the first name and surname without a separator where that format is liable to cause confusion as to identity.
Example:
• jeandupont.avocat.
Q152.3If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
3. Management of identical-name situations involving individual Avocats
The Registry Operator must implement an objective and published procedure for resolving identical-name situations involving individual Avocats who satisfy the eligibility requirements.
Where the name of an Avocat as registered on the Tableau cannot be allocated because another registrant has a prior right to that name, the Registry Operator must permit the following alternative formats:
• Addition of a parent’s surname (i);
• Addition of the spouse’s surname where it constitutes a legally recognised customary name (ii);
• Replacement of the full first name with its initial (iii).
Examples:
• jean-dupont-martin.avocat (i);
• jean-dupont-durand.avocat (ii);
• j-dupont.avocat (iii);
• jdupont.avocat (iii).
The Registry Operator must apply an order of priority among the alternative solutions based on transparent and published criteria, taking into account the supporting documents provided by the applicant.
Q152.4If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
4. Criteria applicable to entities through which Avocats practise
The Registry Operator must permit the registration of a “.AVOCAT” domain name by an entity through which Avocats practise only where the requested name corresponds to its full or abbreviated name as registered on the Tableau.
The Registry Operator must permit variants with or without a hyphen where they correspond to the same full or abbreviated name as registered on the Tableau.
Examples:
• cabinet-dupont.avocat;
• cabinetdupont.avocat.
The Registry Operator must apply a normalisation rule removing the generic terms “avocat” and “avocats” where they appear in the official name of an entity through which Avocats practise, in order to avoid duplication with the “.AVOCAT” extension.
Example:
Cabinet Dupont Avocats
Becomes:
cabinetdupont.avocat.
The Registry Operator must not authorise the registration of a domain name based exclusively on:
• A trademark;
• A trade name;
• An initialism;
• An acronym;
• A diminutive;
• An abbreviated form.
Where those elements do not correspond to the full or abbreviated name as registered on the Tableau, unless approved in accordance with the Registry’s published rules.
Q152.5If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
5. Criteria applicable to institutional members of the Communauté professionnelle des Avocats
The Registry Operator must permit institutional members of the Communauté professionnelle des Avocats to register domain names corresponding to their official name, recognised acronym or institutional identity validated by the Registry Operator.
This provision applies in particular to:
• Ordres;
• Conseil National des Barreaux;
• Conférence des Bâtonniers;
• Centres Régionaux de Formation Professionnelle des Avocats;
• Caisses Autonomes des Règlements Pécuniaires des Avocats;
• Conseils de discipline;
• Syndicats and Associations d’avocats;
• Structures mandated by the Institutions de la Profession d’avocat.
Q152.6If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
6. Trademarks and distinctive signs
The Registry Operator must provide that the existence of a prior right in a trademark, trade name or any other distinctive sign does not, by itself, confer an automatic right to register a “.AVOCAT” domain name.
The Registry Operator must not authorise the registration of a “.AVOCAT” domain name by an applicant that does not satisfy the criteria for membership of the Communauté professionnelle des Avocats and the name selection rules applicable to the “.AVOCAT” TLD.
Q152.7If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
7. Reserved and blocked names
The Registry Operator must establish, maintain and publish a list of reserved or blocked names in order to preserve public trust, the general interest of the Communauté professionnelle des Avocats and the security of the “.AVOCAT” TLD.
The Registry Operator must not authorise the registration of those names unless their use is expressly approved in accordance with the rules published by the Registry Operator.
Reserved or blocked names include in particular:
• Names corresponding to French municipalities;
• Names generically evoking the title of avocat or a potentially misleading title;
• Names evoking a field of law or an activity falling within those of an avocat;
• Terms contrary to public policy or accepted principles of morality;
• Any term having institutional, professional-ethics or security significance for the TLD.
Q152.8If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
8. Technical selection and normalisation rules
The Registry Operator must define and publish the rules applicable to:
• Permitted characters;
• Separators;
• Spelling variants;
• Normalisation rules;
• Any linguistic variants applicable to “.AVOCAT” domain names.
The Registry Operator must apply those rules uniformly to all registration applications.
Q152.9If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
9. Transfer and continued compliance of the registered name
The Registry Operator must not authorise the transfer of a “.AVOCAT” domain name where the new registrant does not satisfy the name selection criteria and eligibility requirements applicable to the “.AVOCAT” TLD.
The Registry Operator must apply the name selection criteria to registrations, renewals and transfers of “.AVOCAT” domain names.
Q152.10If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
If there is an additional proposed policy, state the specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.
10. Objective compliance measures
The Registry Operator must develop, implement and publish on its website a name selection policy applicable to second-level domain names under “.AVOCAT” no later than the date on which the “.AVOCAT” TLD is delegated in the DNS.
The Registry Operator must retain the records demonstrating that registered names comply with the applicable selection criteria throughout the registration period of the relevant domain names.
The Registry Operator must review the name selection policy annually and publish the results of that review, including any amendments, within thirty (30) days following each anniversary of the effective date of the Registry Agreement.
Q153.1State a specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
State a specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
Community Registration Policy – Continued Eligibility and Professional Status Monitoring of Registrants
Registry Operator must implement a continued-eligibility policy for registrants of “.AVOCAT” domain names to ensure that registrants remain members of the Communauté professionnelle des Avocats throughout the registration term of their domain names.
Registry Operator must verify that registrants of “.AVOCAT” domain names continue to satisfy the membership requirements of the Communauté professionnelle des Avocats applicable to their registrant category throughout the registration term of the domain name.
Registry Operator must implement cooperation procedures with the Institutions de la Profession d’avocat in order to receive the information necessary to verify registrants’ continued eligibility for “.AVOCAT” domain names.
Registry Operator must establish a procedure applicable when a registrant of a “.AVOCAT” domain name ceases to satisfy the membership requirements of the Communauté professionnelle des Avocats, including removal from the Tableau of a Barreau, cessation of professional activity, dissolution of an entity through which Avocats practise, or loss of the status that permitted registration of the domain name.
Registry Operator must define in its continued-eligibility policy the conditions governing temporary suspension and permanent deletion of a “.AVOCAT” domain name where a registrant no longer satisfies the applicable eligibility criteria.
Registry Operator must address any identified loss of eligibility in accordance with the published policy applicable to the “.AVOCAT” TLD and apply the measures provided for in that policy concerning the maintenance, temporary suspension, or permanent deletion of the relevant domain name.
Registry Operator must establish a procedure for giving prior notice to the registrant before any suspension or deletion of a “.AVOCAT” domain name resulting from a loss of eligibility, except where such action is necessary to prevent an immediate risk to the security or integrity of the TLD or to public trust.
Q153.2If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
Obligations Applicable to Registrars
Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar must cooperate with Registry Operator in verification procedures relating to the continued eligibility of registrants of “.AVOCAT” domain names.
Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar must not maintain a “.AVOCAT” domain name where Registry Operator has notified it of a suspension or deletion decision based on the registrant’s loss of eligibility in accordance with the applicable policies of the “.AVOCAT” TLD.
Q153.3If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
Obligations Relating to Registration Agreements
Registry Operator will include a provision requiring registrars to include in their Registration Agreements a provision requiring the registrant to notify the registrar of any change that may affect the registrant’s membership of the Communauté professionnelle des Avocats.
Registry Operator will include a provision requiring registrars to include in their Registration Agreements a provision prohibiting the registrant from retaining a “.AVOCAT” domain name where the registrant no longer satisfies the eligibility requirements applicable to the “.AVOCAT” TLD.
Registry Operator will include a provision requiring registrars to include in their Registration Agreements a provision requiring the registrant to satisfy the applicable eligibility requirements upon any transfer of a “.AVOCAT” domain name to a new registrant.
Q153.4If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
Record Retention and Traceability
Registry Operator must retain the records necessary to demonstrate implementation of this policy throughout the registration term of the relevant domain names.
Registry Operator must retain the records supporting any decision to suspend or delete a “.AVOCAT” domain name on the basis of a loss of eligibility.
Q153.5If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
If there is an additional policy, state the specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.
Publication and Compliance Monitoring
Registry Operator must develop, implement, and publish on its website a continued-eligibility policy for registrants of “.AVOCAT” domain names no later than the date on which the “.AVOCAT” TLD is delegated in the DNS.
Registry Operator must review the registrant continued-eligibility policy annually and publish the results of that review, including any amendment to the policy, within thirty (30) days following each anniversary of the Effective Date of the Registry Agreement.
Q154Explain the rationale for any limitations to the Community Registration Policy proposed by the applying entity in Questions 151-153.
Explain the rationale for any limitations to the Community Registration Policy proposed by the applying entity in Questions 151-153.
Not applicable
Q155Explain how the proposed Community Registration Policies of the applying entity meets the Registry Commitments Evaluation criteria 4 and 5?
Explain how the proposed Community Registration Policies of the applying entity meets the Registry Commitments Evaluation criteria 4 and 5?
See attachment 155 Registry Commitments Evaluation criteria compliance
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q156From where does the applying entity have the support to run the applied-for string on behalf of the identified community?
From where does the applying entity have the support to run the applied-for string on behalf of the identified community?
See attachment 156 Community Endorsement + 14 support letters
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q157Is there any opposition to the applying entity, application, or applied-for string that the applying entity is aware of? If yes, please explain.
Is there any opposition to the applying entity, application, or applied-for string that the applying entity is aware of? If yes, please explain.
See attachment 157 absence of community opposition
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q222If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q223By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true
Q224By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true