1. CREATING A DOMAIN NAME

1. The creation phase for a domain name, i.e. the phase preparing for the registration and attribution of a domain name, is carried out on behalf of the requesting body in collaboration with the AFNIC by the ISP, chosen from the list of available ISPs available on the AFNIC website.

2. All requests for the creation of a domain name are carried out in accordance with the present Naming Charter.

3. Requests for the creation of a domain name must never infringe the rights of third parties or threaten public order.

4. In this context, the AFNIC reserves the right to employ any measures in order to counteract any infringement of the rights of third parties, and the option of using any appropriate procedure against offenders, but is not obliged to do so.

5. If a domain name is created on the basis of provisional supporting documents (e.g. a provisional K Bis extract or one in the process of being modified), and if the AFNIC cannot verify the existence of the definitive documents in the databases within the allotted time, the AFNIC will suspend the domain name.

6. The domain name remains registered in the name of the requesting body in the database, but may no longer be used to access the corresponding services (website, email etc.). The domain name is suspended for a maximum of one month.

7. It is the requesting body's responsibility to resolve the situation by supplying the AFNIC, via its ISP, with the proofs. During this period the AFNIC will do its best to place the domain name back into service within 72 hours after having received the definitive documents.

8. If the situation is not resolved within the allotted time, the domain name is removed without notice or compensation. Once the domain name has been removed, it can be reassigned to any third party making a request within the terms of the present Charter.

9. In order to ensure the proper management of the naming zone, the AFNIC will not pre-register or reserve domain names prior to the full request for the creation of a domain name.

2. MODIFICATIONS TO DOMAIN NAMES OR TECHNICAL OR ADMINISTRATIVE ELEMENTS

10. The requesting body may, through its ISP, request that a domain name be modified in response to changes in the supporting documents (such as changes in the corporate name, trading name, shop name, association name or changes to a trademark etc.).

11. A modification request can only be undertaken by the AFNIC if the requesting body provides the corresponding supporting documents.

12. The modification of a domain name can involve an initial "migration period" of 1 (one) or 2 (two) months, at the requesting body's discretion, during which both the previous and the new names are active simultaneously.

13. The requesting body may ask for a further delay of no more than 1 (one) year starting from the date of the modification request submitted by the ISP to the AFNIC, on condition that the corresponding supporting documents are supplied and that the maximum number of domain names that can be allocated is not exceeded. The extra time granted by the AFNIC varies according to the age of the domain name initially registered.

14. The requesting body may, through its ISP, request changes in the administrative details held on it (such as the technical or administrative contact person, address etc.).

15. In the context of a "company transformation", i.e. a change in the legal status of a company during its existence (such as when a limited company becomes a public limited company), the requesting body must submit to the AFNIC, through its ISP, the supporting documents certifying the change.

3. TRANSMISSION OF A DOMAIN NAME

16. The "transmission" of a domain name may arise in the following cases: company merger or demerger, partial transfer of assets, agreement between parent and subsidiary companies, transfer of a trademark, collective procedures or as a result of a judicial decision.

17. For administrative and technical reasons, the transmission of a domain name in the abovementioned cases entails removing and then recreating the domain name. The two operations take place on the same day. The transmission procedure is designed to avoid the domain name being subsequently reassigned to any other unauthorised party.

18. Like all administrative operations, requests for the transmission of a domain name are addressed to the AFNIC by an ISP on behalf of the requesting body.

19. The requesting body on whose behalf the transmission is taking place must satisfy the requirements of the Charter, in particular in terms of supplying the necessary supporting documents.

20. The transmission of a domain name must not have effects that run contrary to the Naming Charter.

21. The contribution of the ISP must be strictly in accordance with the Procedural Guide.

22. In all cases, the AFNIC reserves the right to require any further supporting documents necessary in addition to those already identified in the present Naming Charter in order to carry out the necessary verification.

3.1. MERGERS

23. The term "merger" refers to the operation described in articles L 236-1 and L 236-3 of the Commercial Code ("fusion"), by which at least two companies come together to form one company. This operation may result from the transfer of property belonging to one or several companies, either to an existing company or to a new one made up of them.

24. When a request for the transmission of a domain name follows a merger, the governing body of the new company or the purchasing company must include the following with the request for each of the companies involved in the merger:

• A copy of the K Bis extract of the companies concerned;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.2 DEMERGER

25. The term "demerger" refers to the operation described in articles L 236-1 and L 236-3 of the Commercial Code ("scission"), by which a company (the "scindée" or "split" company) transfers its property to two or more existing or new companies.

26. When a request for the transmission of a domain name follows a demerger, the governing body of the beneficiary company must include with its request:

• A copy of the K Bis extract for each company involved mentioning the demerger;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.3 PARTIAL TRANSFER OF ASSETS

27. The term "partial transfer of assets" refers to the operation described in article L 236-22 of the Commercial Code ("apport partiel d'actifs"), by which a company transfers a part of its assets to another company (existing or new), in exchange for shares released by the company benefiting from the transfer, on the express condition that the partial transfer of assets applies to the assets and liabilities of a complete branch of activity.

28. When a request for the transmission of a domain name follows a partial transfer of assets under a demerger settlement, the governing body of the beneficiary company must include a statement from the company's auditor, if there is one, or a chartered accountant if not, certifying that:

• The partial transfer of assets agreement mentions the option for the demerger settlement;
• The domain name of the transferring company is indeed included in this transfer.

29. The requesting body must also include with the request:

• A copy of the K Bis extract for the companies involved mentioning the partial transfer of assets;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.4. AGREEMENTS BETWEEN PARENT AND SUBSIDIARY COMPANIES

30. The term "parent company" refers to a company owning more than half the capital of another company and "subsidiary company" refers to a company more than half of whose capital is owned by another company, in accordance with article L 233-1 of the Commercial Code ("société mère" and "filiale" respectively).

31. When a request for the transmission of a domain name is made in the context of an agreement between a parent company and its subsidiary, the governing body of the parent company or the subsidiary must include with the request:

• Any documents justifying the transmission,
• A statement from the auditor or, if there is no auditor, a chartered accountant, certifying that a link exists between the parent company and the subsidiary,
• The letter of acceptance based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.5. TRANSFER OF A TRADEMARK

32. In the case of the transfer of a properly registered trademark, the domain name with the ".tm.fr" extension is removed, without an express request from the transferring company and the concessionary who will benefit from a transmission procedure.

33. In this case, it is up to the party which is the first to take action to communicate to the AFNIC through the ISP:

• The up-to-date inscriptions in the Registre national des marques (national trademark register) mentioning the transfer of the trademark;
• The acceptance letter according to the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (in particular, the original ISP).

3.6. COLLECTIVE INSOLVENCY PROCEDURES

34. If the requesting body is subject to insolvency proceedings, the AFNIC will proceed with the transmission of the domain name as ordered by the competent judicial authorities.

3.7. JUDICIAL DECISIONS

35. The AFNIC will carry out any administrative operation ordered by a judicial decision in the terms of the decision, and under the following conditions:

• When all parties involved agree to carry out the judicial decision and inform AFNIC by registered letter with confirmation of receipt.
  
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of an immediately enforceable judicial decision, with good reason, in application of article 514 of the new Civil Procedure Code, with proof that the party has been informed of the decision.
  
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of an immediately enforceable judicial decision within the meaning of article 515 of the new Civil Procedure Code, with proof that the party has been informed of the decision, and on presentation of proof of any surety settlement ordered by the judge, in application of article 517 of the new Civil Procedure Code.
  
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of a judgement possessing the force of law within the meaning of article 500 of the new Civil Procedure Code, for which proof will be provided. Depending on the circumstances, this proof may, for example, consist of the submission of a certificate of no appeal or of notification of the appeal judgement.

36. Casein the event that a judicial decision is reversed, the AFNIC will proceed to implement the new administrative deeds ordered, under the same conditions.

37. The AFNIC may not undertake petitions that do not meet these conditions, and may not be bound, for example, by letters dispatched or by writs.

38. The AFNIC cannot be held responsible for any administrative operations undertaken in application of a judicial decision, and the requesting body will guarantee the AFNIC against any claim.

39. The requesting body must supply the AFNIC, through the ISP, with the supporting documents required by the Naming Charter within one month. If this is not done, the use of the domain name by the requesting body may be suspended until the situation is resolved.

40. The technical and administrative expenses incurred in the transmission are due from the requesting body, and it is up to the requesting body to seek reimbursement from one or other of the parties involved as need be.

4. GIVING UP A DOMAIN NAME

41. The operation of a domain name in the ".fr" zone depends on having the right to use it. As a result, no form of disposal of a domain name, either gratuitously or for a consideration, can be enforceable against the AFNIC.

42. Consequently, any removal/recreation operation on a domain name is carried out at the risk of the requesting body. It should be remembered that as soon as a domain name is removed it returns to the public domain, and can thus be reattributed at any time to any other requesting body respecting the present Naming Charter.

5. CHANGING THE ISP

43. As long as the necessary agreement has been made with the ISP, the requesting body may ask for a change of delegation, which consists of the technical transfer of the domain name from one ISP to another.

44. To make this change, it is the responsibility of:

• the requesting body to make the necessary arrangements with the ISPs so that they can proceed with the change of delegation;
  
  
• the ISPs involved to proceed with the change of delegation properly on behalf of the requesting body.

45. The ISP to whom the domain name is being delegated must ensure that the technical change does not affect the administration of the domain name.

6. REMOVAL OF A DOMAIN NAME

46. At any time, the requesting body through its ISP may ask that the domain name be removed. This request cannot be revoked and requires no justification.

47. In the interests of Requesting Bodies and in order to avoid errors and disputes, requests for the removal of a domain name from third parties are not accepted. However, if the domain name has already been subject to a transmission, the new owner can ask that the name be removed.

48. Any removed domain name can be recreated on behalf of a requesting body, in accordance with the present Charter.

49. In the event that the ISP ceases activity for any reason (collective proceedings, stopping the activity, cancellation of the membership agreement etc.), the AFNIC will write to the requesting body, one year after the last fee-paying operation on the domain name, to ask that they change ISP, if necessary, within a period of at most one month from receipt of the letter. If the change is not made within the allotted time, the AFNIC will proceed to remove the corresponding domain name, which can then be reallocated to another requesting body.

APPENDIX: PROCEDURAL GUIDE

1. GENERAL REMARKS

1. Administrative operations on domain names in the ".fr" naming zone are carried out on behalf of requesting bodies by ISPs who have signed a membership agreement with the AFNIC, in accordance with the rules of the Naming Charter and the technical provisions in the "Procedural Guide".

2. As soon as the complete membership file is received, the ISP receives an e-mail message confirming its ISP code, password and membership number, to be quoted in all correspondence with the AFNIC.

3. When these identifying elements have been received, the ISP may proceed with any request for an administrative operation on the domain names of its clients.

4. As a guideline, the average time taken to set up a domain name by the AFNIC is 24 hours from receipt of the request from the ISP and on condition that the submitted request for an administrative operation be in accordance with the requirements of the present Charter.

5. All requests for administrative operations that are submitted by an ISP to the AFNIC are kept for a maximum duration of three months. After this time, if no approach has been made to the AFNIC to finalise the procedure, an e-mail is sent to the ISP to request that the file be finalised. The ISP then has one month to finalise the file. If the ISP informs the AFNIC within the month that the request has been cancelled, the request is simply deleted; if the AFNIC receives no information within the month the request is archived and the ISP is invoiced a fixed sum set at the cost of creating a domain name under option 1.

6. The AFNIC may at any moment verify that the present Naming Charter is being adhered to, and in particular that:

• The requested name corresponds to the supporting documents supplied (see the Naming Charter)
• The technical delegation is valid (see technical rules).

7. When communicating with the AFNIC by e-mail ("nic@nic.fr"), correspondents are asked to respect current standards and to avoid sending documents in proprietary formats.

8. When communicating with the AFNIC's automated ticket system by e-mail ("auto-ticket@nic.fr"), the MIME/HTML format must not be used. Only the plain text format is allowed.

9. A FAQ is available: "http://www.nic.fr/faq/"

10. The list of checks given below may be amended according to new administrative and technical constraints imposed by developments in protocols or regulations.

2. GENERAL TECHNICAL RULES

11. In general, the AFNIC respects the currently applicable RFCs (for the DNS and SMTP protocols among others), as well as directives defined by the RIPE NCC. Please consult AFNIC support about DNS.

12. The ISP supplies IP addresses to its clients. The delegation of inverse addresses in the DNS is carried out by the ISP and/or its clients, in accordance with the procedures set up by the RIPE NCC; it is essential that these inverse addresses be correctly configured for IP services to work properly on the network.

13. The list of checks carried out when the zone is set up is given below, and corresponds to the various tests carried out by the ZoneCheck tool:

• Zone configuration:
  
  
  • the zone is installed in all the name servers (at least two) given in the installation request ticket sent to the auto-ticket@nic.fr address,
    
    
  • the primary server name in the SOA record corresponds to the first server given in the list of servers to install,
    
    
  • the zone contact (RNAME) is valid and must be contactable by e-mail,
    
    
  • the zone serial number is the same on each server,
    
    
  • the "refresh" time is at least one hour,
    
    
  • the "retry" time is at least one hour,
    
    
  • the "expire" time is at least a week, and much higher than the "refresh" time,
    
    
  • the "TTL" time in the SOA specifies the TTL for negative responses (NXDOMAIN) and must not exceed one day,
    
    
  • the "TTL" time is at least one hour for SOA and NS records,
    
    
  • the list of zone name servers returned by the server corresponds to the list of servers requested in the ticket,
    
    
  • there is one MX for the zone, using a message service relay with a legal name that must be (or must point to) an Internet address (A record); any alias (CNAME) will be refused in accordance with the RFCs,
    
    
  • the postmaster@domain-name.fr mailbox must be contactable,
    
    
  • the contents of the zone conform to the RFCs.
    
    
• Configuration of name servers:
  
  
  • the server must have international IP connectivity,
    
    
  • the server must be on-line 24 hours a day, 7 days a week,
    
    
  • the DNS service must be accessible on port 53 in UDP and TCP, and to ICMP echo packets, for packets sent from any machine on the Internet,
    
    
  • the server must have authority for the requested zone,
    
    
  • the server must obtain the correct list of name servers corresponding to each of the ".fr", ".in-addr.arpa" and "." zones, and must not have authority unless it is mentioned in this list. The addresses of the servers mentioned must be correct,
    
    
  • the server obtains the correct address for each of the other servers in the zone,
    
    
  • the server calculates checksums for UDP packets and generates its IP packets with a TTL of at least 64,
    
    
  • the server does not forward requests to AFNIC servers,
    
    
  • it must be possible to obtain the server names based on their IP addresses.
    
    
• Messaging:
  
  
  • the VRFY command is implemented in accordance with RFC1123,
    
    
  • the return code must be of type "2xx" in accordance with RFC1893,
    
    
  • the postmaster@domain-name.fr address can be delivered to on the first message service relay,
    
    
  • it must be possible to deliver to the zone contact address specified in the SOA record on the first message service relay.
    
    
• Network database (RIPE - RADB) :
  
  
  • For each server mentioned:
    • there is an "inetnum" record for the network to which it belongs,
    • there is a "route" record for the network to which it belongs,
      
      
  • For each zone registration request:
    • the first technical contact is located at the requesting ISP,
    • the identifier of the first technical contact is a NIC-HDL of a role object in the FRNIC database. For more information on NIC-HDLs and role objects, please consult this document and course material.

14. If any of the above points do not comply with the DNS configuration, the AFNIC reserves the right to withdraw the zone within 15 days following notification by e-mail.

3. PROCEDURE FOR ADMINISTRATIVE OPERATIONS ON A DOMAIN NAME

15. The on-line form enables you to carry out the following operations:

C: Create a domain
N: Modify the syntax of a domain name
M: Administrative or technical modification
A: Modify the administrative information for a domain (to be implemented in the future)
T: Modify the technical configuration of a domain
D: Change of ISP (transfer to another approved ISP)
S: Remove a domain
P: Transmit a domain

3.1 CREATING A DOMAIN - PROCEDURE "C"

16. The ISP must use the on-line form and tick the "C" box.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

17. The ISP receives a confirmation e-mail giving the order number assigned to the request.

18. Within 15 days, the ISP must send the following by fax to +33 1 39 30 83 83:

• the commitment letter¹, completed, dated and signed by the requesting body, with the order number,
• the required supporting documents: see the Naming Charter.

  IMPORTANT: beyond this time, the request record will be deleted.

19. As soon as the AFNIC receives the documents, the following are sent to the ISP:

• a "Customer Pending" ticket if the file is administratively correct,
• a "Problem" ticket if a error is detected,
• an e-mail message if the file contains an error making it impossible to issue a ticket.

20. To finalise the installation of the domain, the ISP must:

• prepare the technical delegation,
• "reply" to the ticket.

  Note: Once the ISP has received the "Customer Pending" ticket, it must proceed to the technical installation of the domain and test it using the ZoneCheck tool: if any error occurs, the domain cannot be installed. If there is no error, the ISP just sends a "reply" to the e-mail containing the ticket to request the installation. For more information, please consult the explanatory note about tickets.

21. The procedure is complete when the ISP receives a "Finished" ticket.

Note: any request for an administrative operation for which a ticket has been issued is kept for three months. After this time, the ISP must make a decision, otherwise the file will be archived and invoiced.

IMPORTANT: Unless specifically allowed within the Naming Charter or established within a particular procedure, such as pre-registration by the Centres de Formation des Entreprises (business training centres), it is not possible to reserve or pre-register a domain name before making the name creation request.

3.2 MODIFYING THE SYNTAX OF A DOMAIN NAME - PROCEDURE "N"

22. The ISP must use the on-line form and tick the "N" box.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

23. The ISP receives a confirmation e-mail giving the order number assigned to the request.

24. Within 15 days, the ISP must send the following by fax to +33 1 39 30 83 83:

• the commitment letter¹, completed, dated and signed by the requesting body, with the order number,
• the required supporting documents: see the Naming Charter.

  IMPORTANT: beyond this time, the request record will be deleted.

25. As soon as the AFNIC receives the documents, the following are sent to the ISP:

• a "Customer Pending" ticket if the file is administratively correct,
• a "Problem" ticket if a error is detected,
• an e-mail message if the file contains an error making it impossible to issue a ticket.

26. To finalise the installation of the domain, the ISP must:

• prepare the technical delegation,
• "reply" to the ticket.

  Note: Once the ISP has received the "Customer Pending" ticket, it must proceed to the technical installation of the domain and test it using the ZoneCheck tool: if any error occurs, the domain cannot be installed. If there is no error, the ISP just sends a "reply" to the e-mail containing the ticket to request the installation. For more information, please consult the explanatory note about tickets.

27. The procedure is complete when the ISP receives a "Finished" ticket.

Note: any request for an administrative operation for which a ticket has been issued is kept for three months. After this time, the ISP must make a decision, otherwise the file will be archived and invoiced.

IMPORTANT: The change to the domain name should not have any effect on the requesting body itself.

3.3 MODIFYING A DOMAIN'S ADMINISTRATIVE DETAILS (ADDRESS, CONTACTS, NIC-HDL ETC.) AND/OR TECHNICAL CONFIGURATION (NAMES OF DNS OR IP SERVERS) - PROCEDURES "M", "A" AND "T"

28. The ISP must use the on-line form and tick the "M", "A" or "T" box according to the desired operation.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

29. The ISP receives a reply by e-mail confirming receipt. The request is processed by hand as soon as possible during business hours (if there is an error in the requested modifications, the ISP must reformulate the request).

Note: this operation does not require files to be sent, except that in the case of a change to the corporate name, explanatory documents must be faxed to the Interface service which will approve or deny the request.

IMPORTANT: The change to the domain name should not have any effect on the requesting body itself. However, certain technical disturbances out of the AFNIC's control may be observed over several days following the operation.

3.4 CHANGE OF ISP (TRANSFER TO ANOTHER AGREED ISP) - PROCEDURE "D"

30. The ISP (to which the domain is to be transferred) must use the on-line form and tick the "D" box.

31. The ISP must make sure that its future client has requested the former ISP to close the domain by registered letter with confirmation of receipt.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

32. The ISP receives a confirmation e-mail giving the order number assigned to the request.

33. Within 15 days the ISP must fax the commitment letter¹, dated and signed by the final client, with the order number - no supporting documents are required.

IMPORTANT: beyond this time, the request record will be deleted.

34. As soon as the AFNIC receives this document, it sends an e-mail to the former ISP asking for its agreement for the change of delegation, and then sends the new ISP a "Removal Pending" ticket to inform it that the file has been undertaken.

35. A positive response from the former ISP is required before a "Customer Pending" ticket can be issued. In the absence of a response, or in the case of a negative response, the domain is maintained for 6 weeks. Beyond this period, the "Customer Pending" ticket is issued to the new ISP.

Note: for more information, please consult the explanatory note about tickets.

36. To finalise the installation of the domain, the ISP must:

• prepare the technical delegation,
• "reply" to the ticket.

37. The procedure is complete when the ISP receives a "Finished" ticket.

Note: any request for an administrative operation for which a ticket has been issued is kept for three months. After this time, the ISP must make a decision, otherwise the file will be archived and invoiced.

IMPORTANT: The change to the domain name should not have any effect on the requesting body itself. However, certain technical disturbances out of the AFNIC's control may be observed over several days following the operation.

3.5 REMOVING A DOMAIN - PROCEDURE "S"

38. The ISP must use the on-line form and tick the "S" box.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

39. The ISP receives a first e-mail message confirming receipt of the request.

40. When the domain is removed, the ISP receives an e-mail to say that the removal has been carried out.

Note: no supporting documents need be sent for this operation.

IMPORTANT: The removal request is definitive and its consequences are extremely important, given that the removed domain name re-enters the public domain and may be re-allocated at any time.

3.6 TRANSMISSION OF A DOMAIN - PROCEDURE "P"

41.The ISP must use the on-line form and tick the "P" box.

Note: the ISP may also use e-mail, sending the request to domain@nic.fr. However, the on-line form must first be filled in to obtain the acceptable e-mail template.

42. The ISP receives a confirmation e-mail giving the order number assigned to the request.

43. Within 15 days, the ISP must fax the corresponding supporting documents as specified within the Naming Charter.

IMPORTANT: beyond this time, the request record will be deleted.

44. As soon as the documents are received, the AFNIC will:

• check that the request is valid (the documents must be complete),
• check that the zone is technically correct (the new domain must be operational).

45. When the previous stage has been checked, the AFNIC proceeds to remove the domain:

• a "removal" ticket is sent to the ISP

46. The AFNIC recreates the domain name according to the new administrative and technical data entered.

47. The procedure is complete when the ISP receives a "Finished" ticket.

Note:

• the request must be entered automatically in "immediate installation",
• the ISP does not receive the "Customer Pending" ticket and does not request the technical installation with a reply,
• the operation takes place within one day to guarantee continuity of service as far as possible. However, certain technical disturbances out of the AFNIC's control may be observed over several days following the operation.

--------------
¹ Whether or not a commitment letter needs to be submitted depends on the option chosen by the ISP as part of their signed agreement with the AFNIC.