Source: http://tierra-aoi.net/415.html
Timestamp: 2019-04-22 00:19:48+00:00

Document:
Etisalat is a statutory corporation established by Federal Law #1 of 1991 (see attachment). Etisalat was established by decree and therefore does not have a registered name⁄number⁄address as would normally be found on a central registry.
The string ʺ.etisalatʺ consists of eight ASCII characters, each one of which currently occurs as part of existing and operational gTLD strings. We are not aware of any possible rendering problems concerning the string ʺ.etisalatʺ.
We are aware of the issue of universal acceptability and accept that some incorrectly configured third-party software may consider ʺ.etisalatʺ to be an invalid string, in the same way that other TLDs such as ʺ.INFOʺ and “.MUSEUMʺ are also at times considered ʺinvalid.ʺ Etisalat will work to raise awareness of the issue of universal acceptance of .etisalat and other new gTLDs. CentralNic has previously contributed to these efforts, such as by publication of TLD Verification code for the PHP programming language.
We are aware that a significant fraction of queries sent to the DNS root servers are for invalid TLDs such as ʺ.LOCALʺ or ʺ.LANʺ, and that the delegation of these TLDs could cause previously undiscovered configuration errors to result in operational problems for other operators. We have reviewed the research in this area, including the SAC 045 report from ICANNʹs Security and Stability Advisory Committee, data from the Day In The Life of the Internet project, and other sources, and are not aware of any significant volume of invalid root server queries related to .etisalat. Therefore we feel confident that the delegation of this string will not result in any operation problems for Internet users.
Etisalat’s award-winning Mobile Baby initiative delivers affordable healthcare for all powered by mobile connectivity with significant results: Mobile Baby programme is a complete suite of services that enables birth attendants and midwives to ensure safer pregnancies and deliveries by enabling them to identify, communicate, and act on obstetric emergencies quickly and accurately. In Tanzania, where Etisalat first launched the service, there has been a substantial drop in baseline maternal mortality rates and a 30 percent increase in the in-medical facility delivery rate.  During 2012 the Etisalat Mobile Baby service will be rolled out across its operations in Africa and Asia.
i. The TLD has been specifically designed to meet Etisalat’s requirements and facilitate its corporate mission. Mirroring ICANNʹs own goals of promoting consumer protection, security, stability, innovation, and rights protection, Etisalatʹs application for and desire to operate the TLD affirms its commitment to these areas and will ensure their execution. The domain will allow authorized parties to register the shortest, most intuitive, and most descriptive domain names possible. Various business units under the Etisalat corporate aegis will have access to the most efficient web and email addresses and be united under the Etisalat brand umbrella. Consumers will be aware that corporate communications and websites are authorized by Etisalat - promoting their confidence in the brand and their protection from potentially harmful third parties.
ii. The .etisalat TLD will be the first TLD specifically designed to serve the needs of Etisalatʹs brand, business, and consumers - allowing all to grow and prosper unhindered in the digital landscape. It will provide unprecedented levels of technical service and serve as a platform for the expansion of Etisalat’s services and product offerings.
- protecting Etisalat as a rights holder, creating a dedicated zone wherein complete brand protection and control is  Its use may include but is not limited to websites, emails, online applications, online transactions, social media, directories and any new usages of domain names.
iii. The .etisalat TLD will allow web users to easily identify the Etisalat brand worldwide – unimpeded by artificial boundaries (such as generic or ccTLD endings) and secure in the knowledge that the communications and information uncompromisingly originate directly from Etisalat. The TLD will assist with the dissemination of information about Etisalat product offerings, allowing internet users to become more familiar with the services offered and the various business units within the Etisalat brand universe. It will be a trusted zone functioning at the highest standards of technical and operational utility and security.
iv. The .etisalat TLD is open to registrations by authorized parties within the Etisalat universe. A global, top-down outreach initiative will ensure that authorized registrants and internet users alike are aware of the TLD. Although individual business units within the Etisalat organization may wish to adopt their own informative strategies corresponding specifically with their unique team or market preferences, the common denominator will remain uniting the Etisalat universe under one TLD.
i. Etisalat has taken great care to develop the most fair registration policy possible. We will offer a phased launch consistent with ICANN requirements to ensure the protection of Trademark holders and the satisfaction of potential registrants. Phase 1 will be the ICANN-mandated Sunrise period open to TM holders eligible for registering domains in the TLD. The Sunrise rules and regulations are described in full in section 29.
CentralNic has operated its EPP system since 2005, and it currently operates at significant load in terms of registrars, sessions and transaction volumes.
1.	domain names must comply with the Preferred name syntax described in RFC 1035 §2.3.1. Additionally, the first label of the name must be between 3 and 63 characters in length.
2.	domain names must have a registrant attribute which is associated with a contact object in the registry database.
3.	domain names must have an administrative contact attribute which is associated with a contact object in the registry database.
4.	domain names must have a technical contact which attribute is associated with a contact object in the registry database.
5.	domain names may have an billing contact attribute which is associated with a contact object in the registry database.
6.	domain names may have between 0 (zero) and thirteen (13) DNS servers. A domain with no name servers will not resolve and no records will be published in the DNS. CentralNicʹs EPP system uses the host object model for domain names, rather than the host attribute model (see RFC 5731, §1.1).
7.	domain names may have a number of status codes. These codes are described in RFC 5731, § 2.3. The presence of certain status codes indicates the domain nameʹs position in the lifecycle, which is described further in §27.
8.	where TLD policy requires, the server will response to a “domain:create” command with an ʺObject Pendingʺ (1001) response. When this occurs, the domain is placed onto the pendingCreate status while an out-of-band validation process takes place.
9.	when registered, the expiry date of a domain may be set up to ten years from the initial date of registration. Registrars can specify registration periods in one-year increments from one to ten.
10.	when renewed, the expiry date of a domain may be set up to ten years from the current expiry date. Registrars can specify renewal periods in one-year increments from one to ten. Domain names which auto-renew are renewed for one year at a time.
11.	domain names must have an authInfo code which is used to authenticate inter-registrar transfer requests. This authInfo code may contain up to 48 bytes of UTF-8 character data.
12.	domain names may have one or more DS records associated with them. DS records are managed via the secDNS EPP extension, as specified in RFC 5910.
13.	only the sponsoring registrar of the domain may submit “update”, “renew” or “delete” commands for the domain.
4.	sponsorship of host objects is determined as follows: if an object is in-bailwick (ie subordinate to a domain in the registry database, and therefore also subordinate to a TLD in the system), then the sponsor is the sponsor of the superordinate domain name. If the object is out-of-bailiwick, the sponsor is the registrar which created the contact.
6.	registrars are not permitted to create host objects that are subordinate to a non-existent in-bailiwick domain, or to change the name of a host object so that it us subordinate to a non-existent in-bailiwick domain.
7.	a host object cannot be deleted if one or more domain names are delegated to it (the registry may delete host objects to remove orphan glue, see §28).
8.	inter-registrar transfers of hosts are not permitted.
5.	contact objects must have an authInfo code which is used to authenticate inter-registrar transfer requests. This authInfo code may contain up to 48 bytes of UTF-8 character data.
6.	a contact object cannot be deleted if one or more domain names are associated with it.
7.	only the sponsoring registrar of the domain may submit “update” or “delete” commands for the object.
8.	the “contact:disclose” element may be used to cause a contact object to be opted-out of display in the Whois (see §26 and the discussion of the Contact Type extension below. Note that this feature is redundant and will be disabled for TLDs which forbid registration by natural persons).
The .etisalat  Acceptable Use Policy will be incorporated into the Registry-Registrar agreements and Registrars will be required to pass through the requirements to comply with the policy to the registrants.
Firstly, the Shared Registry System will reject any request to create host object that is the child of a non-existent domain name. That is, if EXAMPLE .etisalat does not exist, then NS0.EXAMPLE .etisalat cannot be created. If the parent domain name does exist, then only the sponsoring registrar of that domain is permitted to create child host objects.
In addition to the standard measures described above, the .etisalat WHOIS system will feature extra levels of reliability with regards to Whois information.
CentralNicʹs resourcing model assumes that the ʺdedicatedʺ resourcing required for the TLD (ie, that required to deal with issues related specifically to the TLD and not to general issues with the system as a whole) will be equal to the proportion of the overall registry system that the TLD will use. After three years of operation, the optimistic projection for the TLD states that there will be1000 domains in the zone. CentralNic has calculated that, if all its TLD clients are successful in their applications, and all meet their optimistic projections after three years, its registry system will be required to support up to 4.5 million domain names. Therefore the TLD will require less than 0.1% of the total resources available for this area of the registry system.
Registry TLD: ETISALAT Top Level Domain.

References: §2
 §1
 § 2
 §27
 §28
 §26