Please Wait...

Toll Free
888.398.4703

International
++1.760.736.3700

Application Preview

Application number: 1-879-42119 for Dot Auto LLC

Generated on 11 06 2012

Applicant Information

1. Full legal name

Dot Auto LLC

2. Address of the principal place of business

6600 College BLVD
Suite 125
Overland Park Kansas 66211
US

3. Phone number

9136084088

4. Fax number

8169947333

5. If applicable, website or URL

Primary Contact

6(a). Name

Ms. Tess Pattison-Wade

6(b). Title

Executive Director

6(c). Address

6(d). Phone Number

8168986598

6(e). Fax Number

6(f). Email Address

tess@cedarhillmusic.com

Secondary Contact

7(a). Name

Mr. Shaul Jolles

7(b). Title

Chief Executive Officer

7(c). Address

7(d). Phone Number

8162007080

7(e). Fax Number

7(f). Email Address

sjolles@gmail.com

Proof of Legal Establishment

8(a). Legal form of the Applicant

Limited Liability Company

8(b). State the specific national or other jursidiction that defines the type of entity identified in 8(a).

Kansas

8(c). Attach evidence of the applicant's establishment.

Not Available

9(a). If applying company is publicly traded, provide the exchange and symbol.

9(b). If the applying entity is a subsidiary, provide the parent company.

9(c). If the applying entity is a joint venture, list all joint venture partners.

Applicant Background

11(a). Name(s) and position(s) of all directors

Christopher Michael Parrott Director of Finance
Paul Eugene Spurgeon COO
Scott Adam Shachtman Director of Legal & Policy
Shaul Jolles CEO

11(b). Name(s) and position(s) of all officers and partners

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

Automotix LLC Not Applicable

11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility

Applied-for gTLD string

13. Provide the applied-for gTLD string. If an IDN, provide the U-label.

auto

14(a). If an IDN, provide the A-label (beginning with "xn--").

14(b). If an IDN, provide the meaning or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.

14(c). If an IDN, provide the language of the label (in English).

14(c). If an IDN, provide the language of the label (as referenced by ISO-639-1).

14(d). If an IDN, provide the script of the label (in English).

14(d). If an IDN, provide the script of the label (as referenced by ISO 15924).

14(e). If an IDN, list all code points contained in the U-label according to Unicode form.

15(a). If an IDN, Attach IDN Tables for the proposed registry.

Not Available

15(b). Describe the process used for development of the IDN tables submitted, including consultations and sources used.

15(c). List any variant strings to the applied-for gTLD string according to the relevant IDN tables.

16. Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.

There are no known operational or rendering issues associated with our applied for string. We are relying on the proven capabilities of Neustar to troubleshoot and quickly eliminate these should they arise.

17. (OPTIONAL) Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

Mission/Purpose

18(a). Describe the mission/purpose of your proposed gTLD.

“.AUTO” was born from our parent company, Automotix’s devotion to the success of the online automotive industry and a great desire to assist in creating a steady, solid and comprehensive way to reduce the struggle of automotive sellers, consumers, and retail agents in finding up to date, relevant information online. 

The purpose of “.AUTO” is to provide a commerce environment and information exchange network for the auto industry allowing businesses to create user friendly access to products, services and information instantaneously through accurate search engine classifications. 

It is our mission that businesses bearing the “.AUTO” gTLD string would become leaders in their market and be instantly differentiated online as automotive producers, providers, or service professionals.

18(b). How proposed gTLD will benefit registrants, Internet users, and others

The first steam-powered vehicle was built in 1672. At only 65 cm-long it was unable to hold a passenger or a driver. Now, more then three hundred years later, thousands of vehicles are available worldwide and the auto industry is seen as one of the most important economic sectors in the world. According to the US Bureau of Transit Statistics, over 254 million Americans own registered vehicles, and the United States is one of the top four producers for both vehicles and automotive parts.

The International Association of Vehicle Manufacturers reported that, in 2011, global production of cars and commercial vehicles was up by 26%, with over 77 million vehicles produced in 40 different countries. The automotive industry, which includes industries associated with the production, wholesaling, retailing and maintenance of motor vehicles, employs an average of 250,000 people per country and additionally impacts over 100 million workers who depend on automotive plants and labs for their own jobs. The Automotive industry provides a variety of employment options such as: parts suppliers, car dealerships, mechanics, road crews, and public service departments.

When we consider the rate at which domain registration has increased in the last ten years, resulting in overcrowding and a general lack of naming availability, we begin to see the need for industry classifications online such as “.AUTO”. “.AUTO” will not only open the door for increased online naming abilities, it will also allow consumers to easily locate specific products and services through increased search engine classifications. Further, by developing specific industry classifications such as “.AUTO” , advertisers will have increased confidence that they are reaching their target markets, thus increasing advertising revenue across the board for online retailers. 

With these thoughts in mind, we at DOT Auto believe that it is essential for the automotive industry to become a leader in this transition. On average, there are over 500 million searches a month for the words “CAR” and “AUTO” online, which result in a monthly volume of page views totaling well over 10 billion clicks. The opportunity to enhance the consumer experience while driving competition in our market is paramount and we are excited to be apart of this evolution.

In 2004, our parent company Automotix was formed to offer innovative solutions and technologies to the automotive industry, including: mobile application, patent pending peer-to-peer technology, and the ability to connect buyers and sellers around the world. Today, Automotix has more then 4 million online users a month, which contributes to our ever-growing market of online retailers, resource providers, and parts distributers.

Automotix is proudly responsible for the creation of an information exchange network that has provided for the sale of over 40 million recycled auto parts, 900,000 pre-owned⁄ new cars and trucks, and over 1 million salvaged vehicles. Automotix also provides hard to find part locating services, extensive auto repair service tips, safety recall information, nationwide auto classifieds, automotive news, and repair requests.

 “.AUTO” was born from Automotix’s devotion to the success of the online automotive industry and a great desire to assist in creating a steady, solid and comprehensive way to reduce the struggle of automotive sellers, consumers, and retail agents in finding up-to-date, relevant information online. The Automotix team combines extensive experience in the automotive arena and has been working to build strong relationships with car dealers, classic car traders, car brokers, rebuilders, auto pools, auction houses, insurance and fleet companies, trucking companies, auto parts suppliers, aftermarket car part distributers, salvage yards, car repair shops, mechanics, do-it yourselfers and catalog providers in order to further enhance the success and reach of the “.AUTO” gLTD. 

The demand for automotive services and products is constantly increasing online. “.AUTO” would provide a commerce environment for the auto industry allowing businesses to provide access to products and services instantaneously through accurate search engine classifications. Businesses bearing the “.AUTO” string would become leaders in their market and be instantly differentiated online as automotive producers, providers, or service professionals. 

In order to achieve our goals and build name recognition, DOT Auto will be implementing a robust marketing initiative, focused on enhancing the value of the “.AUTO” gTLD, while positioning “.AUTO” to become an industry “must –have” in assisting businesses to gain market share and exposure. 

Within six years of the “.AUTO” launch, it is our goal to register 70%+ of all auto industry-related companies with a minimum of one “.AUTO” gTLD. This achievement would solidify our mission statement and serve to differentiate the Internet in a much needed and effective way.

To do so, the following marketing strategies will be put in place:

1) Build strong relationships with Registrar services in order to capture new domain registrations.
2) Create a prominent and consistent image, representative of our mission and expressed clearly through branding, advertisements, and corporate relationships.
3) Secure “key” Registrants through our Founders program (described further in question 29 of this application) that will act as innovative leaders to assist us in appropriately exposing our target audience to the existence of “.AUTO”.
4) Cultivate relationships with both domestic and global automotive organizations. Partnerships with these organizations and others like them would increase DOT Auto’s knowledge base in regards to efficiently meeting the needs of auto industry consumers and business owners.
5) Partner with global marketing firms to ensure a wide reaching and effective marketing campaign. This process would allow DOT Auto, LLC to efficiently structure our marketing process to reach the desired Registrants. It is additionally important that Internet users become aware of the ʺ.AUTOʺ gTLD and the industry classification it represents. DOT Auto, LLC plans to utilize an outsourced marketing firm to intiate a consumer marketing initiative to educate consumers on the implementation of ʺ.AUTOʺ and itʹs impact on search classifications ⁄ consumer benefits.
6) Increase exposure for “.AUTO” by creating a strong international presence through attendance at conferences appropriate to our visibility in the market.
7) Create a consistent presence in all auto-related trade publications and sponsorship of well- attended auto-related events.
8) Utilize the Automotix team’s combined extensive experience in the automotive arena, allowing us to link consumers to the most efficient and applicable service provider via the “.AUTO” gTLD
9) Enhance our current relationships with the following:

A: Auto Clubs
B: Auto Detailing Shops
C: Auto Financing Providers
D: Auto Parts Retailers and suppliers
E: Auto Pools and auction houses
F: Auto Racing companies and race teams
G: Auto Repair and service shops
H: Auto Restoration and street rod builders
I: Automotive apparel and uniforms companies
J: Automotive Associations
K: Automotive data providers
L: Automotive media and marketing companies
M: Automotive news sources
N: Car Dealers
O: Car makers
P: Catalog Providers
Q: Classic⁄Antique Collectors
R: Do-It- yourselfers and auto enthusiasts
S: Insurance and fleet companies
T: Internet and technology providers
U: Mechanics and auto technicians
V: OEM⁄Aftermarket parts manufacturers
W: Rebuilders and Restylers
X: Roadside assistance companies
Y: Salvage yards and auto dismantlers
Z: Trucking Companies


We intend to implement a highly focused⁄ targeted marketing blitz to the industry sub-divisions listed above, their advertising agencies, and public relations personnel in order to assist them in implementing and utilizing the “.AUTO” gTLD.

It is our goal to provide an efficient and secure registration process by minimizing the input required by the Registrant and creating a streamlined application process. In order to do so and uphold the integrity of our mission to provide instant access to members of the automotive industry, DOT Auto, LLC will implement the following registration guidelines and naming conventions:

1) .AUTO registrations will be restricted to individuals, businesses, and organizations that are active members of the automotive industry. “Active” can be defined in this context as any individual, business or organization wishing to provide automotive industry information, services, or products online.

2) Registrants will be asked to submit, at minimum their contact information and agree to a statement indicating that it is their intention to utilize their “.AUTO” domain for the promotion, distribution, or exchange of information, products or services directly connected to the Automotive Industry.
3) Content on all awarded “.AUTO” sites are expected to primarily represent the Registrant’s connection to the automotive industry. Sites will be randomly selected for review to ensure compliance with this guideline. Should Registrant’s be found in violation of this guideline, they will be notified in writing of the violation and given a 30 - day probationary period in order to correct the content deficiencies of their site. If Registrants are unable to comply with this guideline within the 30 - day probationary period, DOT Auto, LLC will revoke the Registrant’s domain name and it will be returned to general availability. Should a Registrant’s domain name be revoked due to their content deficiencies, all funds paid by the Registrant to date will be considered non-refundable. Dot Auto or it’s designated agent will perform all tasks related to content monitoring in order to not further burden their registrar partners.

4) Should DOT Auto, LLC discover at any point that a Registrant has falsely represented themselves as an individual, business, or organization related to the automotive industry, their awarded domain will be immediately revoked and returned to general availability. Should a Registrant’s domain be revoked due their false representation of their industry relationship, all funds paid by the Registrant to date will be considered non-refundable. 

5) Registrant’s should understand that name availability is not guaranteed and that names will be issued on a first – come, first - served basis. Should a Registrant’s requested name be unavailable, the Registrant will be offered the option of re-wording, changing, or adapting their initial naming request until a suitable solution is found.

6) Registrants will not be allowed to register names that infringe on the legal rights of other individuals or companies, allude to criminal activities, or contain in any part racially offensive language. 

7) DOT Auto, LLC reserves the right to deny, cancel, or transfer any registration or transaction (as more fully described in our Abuse Policies in question 28 below), or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary ; (1) to protect the integrity and stability of the registry; (2) to comply with applicable laws, government rules or requirements, or court orders; (3) to avoid any liability, civil or criminal, on the part of DOT Auto, LLC, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) to correct mistakes made by the DOT Auto, LLC, registry services provider, or any Registrar in connection with a domain name registration; (5) during resolution of any dispute regarding the domain; and (6) if a Registrant’s pre-authorization or payment fails; or (7) to prevent the bad faith use of a domain name that is identical to a registered trademark and being utilized to confuse users.

8) DOT Auto’s registry services operator will provide thick WHOIS services that are fully compliant with RFC 3912 and with Specifications 4 and 10 of the Registry Agreement. Additionally, DOT Auto will provide a Web-based WHOIS application, which will be located at www.whois.auto. The WHOIS Web application will be an intuitive and easy to use application. A complete description of these services can be found in Question 26 below.
9) All Registrants awarded a “.AUTO” domain will agree to a one year minimum contract, which will need to be renewed on an annual basis. Renewal is the sole responsibility of the Registrant. Registrant’s failing to renew their awarded domains by their expiration dates will be given a 60-day renewal grace period prior to their domain being revoked and returned to general availability.

10) DOT Auto, LLC is not liable or responsible in any way for any errors, omissions or any other actions by any third party (including any Registrar service) arising out of, or related to a given Registrant’s application for, registration of, renewal of, or failure to register or renew a particular domain name.

11) Through the registration process, all Registrants will be expected to designate an administrative contact for their application, which would possess all the rights granted by DOT Auto, LLC or its designated agents to act in respect to the given domain including, but not limited to, managing the domain name or any services associated thereto. 

12) DOT Auto will implement a reserved names policy consisting of both names DOT Auto wishes to reserve for our own purposes as the registry operator and names protected by ICANN. DOT Auto will respect all ICANN reserved names including, but not limited to, two letter country codes and existing TLD’s. Additionally, DOT Auto will seek ICANN approval on any additional names we plan to reserve in order to appropriately secure them prior to the opening of general availability.


DOT Auto, LLC will additionally implement a series of Rights Protection Mechanisms (RPM) included, but not limited to: Support for and interaction with the Trademark Clearinghouse (“Clearinghouse”), use of the Trademark Claims Service, segmented Sunrise Periods allowing for the owners of trademarks listed in the Clearinghouse to register domain names that consist of an identical match of their listed trademarks, subsequent Sunrise Periods to give trademark owners or Registrants that own the rights to a particular name the ability to block the use of such name, stringent take-down services and Uniform Dispute Resolution Policies.

18(c). Describe operating rules to eliminate or minimize social costs or financial resource costs, various types of consumer vulnerabilities.

DOT Auto, LLC will collect personal information from it’s Registrants via any of our approved Registrars. In order to maintain the integrity of the “.AUTO” gTLD and minimize the negative consequences to consumers and business owners, the following policies will be adhered to:

a) No information collected from our Registrants will be used for marketing purposes.
b) Data collected will not be traded or sold.
c) All data collected on any Registrant will be available to the Registrant free of charge.
d) Registrants will be allowed to address and correct data inaccuracies as needed.
e) All data will be kept secure.

DOT Auto, LLC will strictly uphold the rules set forth in their registration guidelines in order to accurately service our Registrants and mitigate any negative consequences to consumers or Internet users.

DOT Auto, LLC does not plan to offer registrations to Registrants directly. Therefore, our pricing commitments will be made within our Registry–Registrar Agreements. It is our intention that these commitments will percolate down to Registrants directly and that the contractual commitments contained within our Registry-Registrar agreements will be reflected in the retail sale process of our gTLD, thus minimizing the negative consequences that might be imposed on Registrants via the retail process.

DOT Auto, LLC plans to offer bulk registration benefits to Registrars during the first 6 months of operation. Registrars wishing to purchase bulk registrations of 1,000 names or more would be offered a 5% discount at the time of purchase. Additionally, DOT Auto, LLC , through our founders program will provide a 25% discount to founders participants as a participation incentive. It is possible that DOT Auto, LLC would offer additional pricing benefits from time to time as relative to the market. All future pricing discounts not detailed in this application will be submitted through the appropriate ICANN channels for approval prior to introduction to the market.

Community-based Designation

19. Is the application for a community-based TLD?

No

20(a). Provide the name and full description of the community that the applicant is committing to serve.

20(b). Explain the applicant's relationship to the community identified in 20(a).

20(c). Provide a description of the community-based purpose of the applied-for gTLD.

20(d). Explain the relationship between the applied-for gTLD string and the community identified in 20(a).

20(e). Provide a description of the applicant's intended registration policies in support of the community-based purpose of the applied-for gTLD.

20(f). Attach any written endorsements from institutions/groups representative of the community identified in 20(a).

Not Available

Geographic Names

21(a). Is the application for a geographic name?

No

Protection of Geographic Names

22. Describe proposed measures for protection of geographic names at the second and other levels in the applied-for gTLD.

DOT Auto, LLC has thoroughly reviewed ISO 3166-1 and ISO 3166-2, relevant UN documents on the standardization of geographic names, GAC correspondence relating to the reservation of geographic names in the .INFO TLD, and understands its obligations under Specification 5 of the draft Registry Agreement. DOT Auto, LLC shall implement measures similar to those used to protect geographic names in the .INFO TLD by reserving and registering to itself all the geographic place names found in ISO-3166 and official country names as specified by the UN. DOT Auto, LLC has already discussed this proposed measure of protecting geographic names with its registry services provider, Neustar, and has arranged for such reservation to occur as soon after delegation as is technically possible.

As with the .INFO TLD, only if a potential second-level domain Registrant makes a proper showing of governmental support for country or territorial names will DOT Auto, LLC then relay this request to ICANN. At this point, DOT Auto, LLC would wait for the approval of the GAC and of ICANN before proceeding to delegate the domain at issue.

Registry Services

23. Provide name and full description of all the Registry Services to be provided.

23.1 Introduction

DOT Auto, LLC has elected to partner with NeuStar, Inc (Neustar) to provide back-end services for the ʺ.AUTOʺ registry. In making this decision, DOT Auto, LLC recognized that Neustar already possesses a production-proven registry system that can be quickly deployed and smoothly operated over its robust, flexible, and scalable world-class infrastructure. The existing registry services will be leveraged for the ʺ.AUTOʺ registry. The following section describes the registry services to be provided.

23.2 Standard Technical and Business Components

Neustar will provide the highest level of service while delivering a secure, stable and comprehensive registry platform. DOT Auto, LLC will use Neustarʹs Registry Services platform to deploy the ʺ.AUTOʺ registry, by providing the following Registry Services (none of these services are offered in a manner that is unique to ʺ.AUTOʺ):

-Registry-Registrar Shared Registration Service (SRS)

-Extensible Provisioning Protocol (EPP)

-Domain Name System (DNS)

-WHOIS

-DNSSEC

-Data Escrow

-Dissemination of Zone Files using Dynamic Updates

-Access to Bulk Zone Files

-Dynamic WHOIS Updates

-IPv6 Support

-Rights Protection Mechanisms

-Internationalized Domain Names (IDN). [Optional should be deleted if not being offered].

The following is a description of each of the services.

23.2.1 SRS

Neustarʹs secure and stable SRS is a production-proven, standards-based, highly reliable, and high-performance domain name registration and management system. The SRS includes an EPP interface for receiving data from registrars for the purpose of provisioning and managing domain names and name servers. The response to Question 24 provides specific SRS information.

23.2.2 EPP

The ʺ.AUTOʺ registry will use the Extensible Provisioning Protocol (EPP) for the provisioning of domain names. The EPP implementation will be fully compliant with all RFCs. Registrars are provided with access via an EPP API and an EPP based Web GUI. With more than 10 gTLD, ccTLD, and private TLDs implementations, Neustar has extensive experience building EPP-based registries. Additional discussion on the EPP approach is presented in the response to Question 25.

23.2.3 DNS

DOT Auto, LLC will leverage Neustarʹs world-class DNS network of geographically distributed nameserver sites to provide the highest level of DNS service. The service utilizes Anycast routing technology, and supports both IPv4 and IPv6. The DNS network is highly proven, and currently provides service to over 20 TLDs and thousands of enterprise companies. Additional information on the DNS solution is presented in the response to Questions 35.

23.2.4 WHOIS

Neustarʹs existing standard WHOIS solution will be used for the ʺ.AUTOʺ. The service provides supports for near real-time dynamic updates. The design and construction is agnostic with regard to data display policy is flexible enough to accommodate any data model. In addition, a searchable WHOIS service that complies with all ICANN requirements will be provided. The following WHOIS options will be provided:

Standard WHOIS (Port 43)

Standard WHOIS (Web)

Searchable WHOIS (Web)

23.2.5 DNSSEC

An RFC compliant DNSSEC implementation will be provided using existing DNSSEC capabilities. Neustar is an experienced provider of DNSSEC services, and currently manages signed zones for three large top level domains: .biz, .us, and .co. Registrars are provided with the ability to submit and manage DS records using EPP, or through a web GUI. Additional information on DNSSEC, including the management of security extensions is found in the response to Question 43.

23.2.6 Data Escrow

Data escrow will be performed in compliance with all ICANN requirements in conjunction with an approved data escrow provider. The data escrow service will:

-Protect against data loss

-Follow industry best practices

-Ensure easy, accurate, and timely retrieval and restore capability in the event of a hardware failure

-Minimizes the impact of software or business failure.

Additional information on the Data Escrow service is provided in the response to Question 38.

23.2.7 Dissemination of Zone Files using Dynamic Updates

Dissemination of zone files will be provided through a dynamic, near real-time process. Updates will be performed within the specified performance levels. The proven technology ensures that updates pushed to all nodes within a few minutes of the changes being received by the SRS. Additional information on the DNS updates may be found in the response to Question 35.

23.2.8 Access to Bulk Zone Files

DOT Auto, LLC will provide third party access to the bulk zone file in accordance with specification 4, Section 2 of the Registry Agreement. Credentialing and dissemination of the zone files will be facilitated through the Central Zone Data Access Provider.

23.2.9 Dynamic WHOIS Updates

Updates to records in the WHOIS database will be provided via dynamic, near real-time updates. Guaranteed delivery message oriented middleware is used to ensure each individual WHOIS server is refreshed with dynamic updates. This component ensures that all WHOIS servers are kept current as changes occur in the SRS, while also decoupling WHOIS from the SRS. Additional information on WHOIS updates is presented in response to Question 26.

23.2.10 IPv6 Support

The ʺ.AUTOʺ registry will provide IPv6 support in the following registry services: SRS, WHOIS, and DNS⁄DNSSEC. In addition, the registry supports the provisioning of IPv6 AAAA records. A detailed description on IPv6 is presented in the response to Question 36.

23.2.11 Required Rights Protection Mechanisms

DOT Auto, LLC, will provide all ICANN required Rights Mechanisms, including:

-Trademark Claims Service

-Trademark Post-Delegation Dispute Resolution Procedure (PDDRP)

-Registration Restriction Dispute Resolution Procedure (RRDRP)

-UDRP

-URS

-Sunrise service.

More information is presented in the response to Question 29.

23.2.12 Internationalized Domain Names (IDN)

IDN registrations are provided in full compliance with the IDNA protocol. Neustar possesses extensive experience offering IDN registrations in numerous TLDs, and its IDN implementation uses advanced technology to accommodate the unique bundling needs of certain languages. Character mappings are easily constructed to block out characters that may be deemed as confusing to users. A detailed description of the IDN implementation is presented in response to Question 44.

23.3 Unique Services

DOT Auto, LLC will not be offering services that are unique to ʺ.AUTOʺ.

23.4 Security or Stability Concerns

All services offered are standard registry services that have no known security or stability concerns. Neustar has demonstrated a strong track record of security and stability within the industry.

Demonstration of Technical & Operational Capability

24. Shared Registration System (SRS) Performance

24.1 Introduction

DOT Auto, LLC has partnered with NeuStar, Inc (ʺNeustarʺ), an experienced TLD registry operator, for the operation of the ʺ.AUTOʺ Registry. The applicant is confident that the plan in place for the operation of a robust and reliable Shared Registration System (SRS) as currently provided by Neustar will satisfy the criterion established by ICANN.

Neustar built its SRS from the ground up as an EPP based platform and has been operating it reliably and at scale since 2001. The software currently provides registry services to five TLDs (.BIZ, .US, TEL, .CO and .TRAVEL) and is used to provide gateway services to the .CN and .TW registries. Neustarʹs state of the art registry has a proven track record of being secure, stable, and robust. It manages more than 6 million domains, and has over 300 registrars connected today.

The following describes a detailed plan for a robust and reliable SRS that meets all ICANN requirements including compliance with Specifications 6 and 10.

24.2 The Plan for Operation of a Robust and Reliable SRS

24.2.1 High-level SRS System Description

The SRS to be used for ʺ.AUTOʺ will leverage a production-proven, standards-based, highly reliable and high-performance domain name registration and management system that fully meets or exceeds the requirements as identified in the new gTLD Application Guidebook.

The SRS is the central component of any registry implementation and its quality, reliability and capabilities are essential to the overall stability of the TLD. Neustar has a documented history of deploying SRS implementations with proven and verifiable performance, reliability and availability. The SRS adheres to all industry standards and protocols. By leveraging an existing SRS platform, DOT Auto, LLC is mitigating the significant risks and costs associated with the development of a new system. Highlights of the SRS include:

-State-of-the-art, production proven multi-layer design

-Ability to rapidly and easily scale from low to high volume as a TLD grows

-Fully redundant architecture at two sites

-Support for IDN registrations in compliance with all standards

-Use by over 300 Registrars

-EPP connectivity over IPv6

-Performance being measured using 100% of all production transactions (not sampling).

24.2.2 SRS Systems, Software, Hardware, and Interoperability

The systems and software that the registry operates on are a critical element to providing a high quality of service. If the systems are of poor quality, if they are difficult to maintain and operate, or if the registry personnel are unfamiliar with them, the registry will be prone to outages. Neustar has a decade of experience operating registry infrastructure to extremely high service level requirements. The infrastructure is designed using best of breed systems and software. Much of the application software that performs registry-specific operations was developed by the current engineering team and a result the team is intimately familiar with its operations.

The architecture is highly scalable and provides the same high level of availability and performance as volumes increase. It combines load balancing technology with scalable server technology to provide a cost effective and efficient method for scaling.

The Registry is able to limit the ability of any one registrar from adversely impacting other registrars by consuming too many resources due to excessive EPP transactions. The system uses network layer 2 level packet shaping to limit the number of simultaneous connections registrars can open to the protocol layer.

All interaction with the Registry is recorded in log files. Log files are generated at each layer of the system. These log files record at a minimum:

-The IP address of the client

-Timestamp

-Transaction Details

-Processing Time.

In addition to logging of each and every transaction with the SRS Neustar maintains audit records, in the database, of all transformational transactions. These audit records allow the Registry, in support of the applicant, to produce a complete history of changes for any domain name.

24.2.3 SRS Design

The SRS incorporates a multi-layer architecture that is designed to mitigate risks and easily scale as volumes increase. The three layers of the SRS are:

-Protocol Layer

-Business Policy Layer

-Database.

Each of the layers is described below.

24.2.4 Protocol Layer

The first layer is the protocol layer, which includes the EPP interface to registrars. It consists of a high availability farm of load-balanced EPP servers. The servers are designed to be fast processors of transactions. The servers perform basic validations and then feed information to the business policy engines as described below. The protocol layer is horizontally scalable as dictated by volume.

The EPP servers authenticate against a series of security controls before granting service, as follows:

-The registrarʹs host exchanges keys to initiates a TLS handshake session with the EPP server.

-The registrarʹs host must provide credentials to determine proper access levels.

-The registrarʹs IP address must be preregistered in the network firewalls and traffic-shapers.

24.2.5 Business Policy Layer

The Business Policy Layer is the brain of the registry system. Within this layer, the policy engine servers perform rules-based processing as defined through configurable attributes. This process takes individual transactions, applies various validation and policy rules, persists data and dispatches notification through the central database in order to publish to various external systems. External systems fed by the Business Policy Layer include backend processes such as dynamic update of DNS, WHOIS and Billing.

Similar to the EPP protocol farm, the SRS consists of a farm of application servers within this layer. This design ensures that there is sufficient capacity to process every transaction in a manner that meets or exceeds all service level requirements. Some registries couple the business logic layer directly in the protocol layer or within the database. This architecture limits the ability to scale the registry. Using a decoupled architecture enables the load to be distributed among farms of inexpensive servers that can be scaled up or down as demand changes.

The SRS today processes over 30 million EPP transactions daily.

24.2.6 Database

The database is the third core components of the SRS. The primary function of the SRS database is to provide highly reliable, persistent storage for all registry information required for domain registration services. The database is highly secure, with access limited to transactions from authenticated registrars, trusted application-server processes, and highly restricted access by the registry database administrators. A full description of the database can be found in response to Question 33.

Figure 24-1 attached depicts the overall SRS architecture including network components.

24.2.7 Number of Servers

As depicted in the SRS architecture diagram above Neustar operates a high availability architecture where at each level of the stack there are no single points of failures. Each of the network level devices run with dual pairs as do the databases. For the ʺ.AUTOʺ registry, the SRS will operate with 8 protocol servers and 6 policy engine servers. These expand horizontally as volume increases due to additional TLDs, increased load, and through organic growth. In addition to the SRS servers described above, there are multiple backend servers for services such as DNS and WHOIS. These are discussed in detail within those respective response sections.

24.2.8 Description of Interconnectivity with Other Registry Systems

The core SRS service interfaces with other external systems via Neustarʹs external systems layer. The services that the SRS interfaces with include:

-WHOIS

-DNS

-Billing

-Data Warehouse (Reporting and Data Escrow).

Other external interfaces may be deployed to meet the unique needs of a TLD. At this time there are no additional interfaces planned for ʺ.AUTOʺ.

The SRS includes an external notifier concept in its business policy engine as a message dispatcher. This design allows time-consuming backend processing to be decoupled from critical online registrar transactions. Using an external notifier solution, the registry can utilize control levers that allow it to tune or to disable processes to ensure optimal performance at all times. For example, during the early minutes of a TLD launch, when unusually high volumes of transactions are expected, the registry can elect to suspend processing of one or more back end systems in order to ensure that greater processing power is available to handle the increased load requirements. This proven architecture has been used with numerous TLD launches, some of which have involved the processing of over tens of millions of transactions in the opening hours. The following are the standard three external notifiers used the SRS:

24.2.9 WHOIS External Notifier

The WHOIS external notifier dispatches a work item for any EPP transaction that may potentially have an impact on WHOIS. It is important to note that, while the WHOIS external notifier feeds the WHOIS system, it intentionally does not have visibility into the actual contents of the WHOIS system. The WHOIS external notifier serves just as a tool to send a signal to the WHOIS system that a change is ready to occur. The WHOIS system possesses the intelligence and data visibility to know exactly what needs to change in WHOIS. See response to Question 26 for greater detail.

24.2.10 DNS External Notifier

The DNS external notifier dispatches a work item for any EPP transaction that may potentially have an impact on DNS. Like the WHOIS external notifier, the DNS external notifier does not have visibility into the actual contents of the DNS zones. The work items that are generated by the notifier indicate to the dynamic DNS update sub-system that a change occurred that may impact DNS. That DNS system has the ability to decide what actual changes must be propagated out to the DNS constellation. See response to Question 35 for greater detail.

24.2.11 Billing External Notifier

The billing external notifier is responsible for sending all billable transactions to the downstream financial systems for billing and collection. This external notifier contains the necessary logic to determine what types of transactions are billable. The financial systems use this information to apply appropriate debits and credits based on registrar.

24.2.12 Data Warehouse

The data warehouse is responsible for managing reporting services, including registrar reports, business intelligence dashboards, and the processing of data escrow files. The Reporting Database is used to create both internal and external reports, primarily to support registrar billing and contractual reporting requirement. The data warehouse databases are updated on a daily basis with full copies of the production SRS data.

24.2.13 Frequency of Synchronization between Servers

The external notifiers discussed above perform updates in near real-time, well within the prescribed service level requirements. As transactions from registrars update the core SRS, update notifications are pushed to the external systems such as DNS and WHOIS. These updates are typically live in the external system within 2-3 minutes.

24.2.14 Synchronization Scheme (e.g., hot standby, cold standby)

Neustar operates two hot databases within the data center that is operating in primary mode. These two databases are kept in sync via synchronous replication. Additionally, there are two databases in the secondary data center. These databases are updated real time through asynchronous replication. This model allows for high performance while also ensuring protection of data. See response to Question 33 for greater detail.

24.2.15 Compliance with Specification 6 Section 1.2

The SRS implementation for ʺ.AUTOʺ is fully compliant with Specification 6, including section 1.2. EPP Standards are described and embodied in a number of IETF RFCs, ICANN contracts and practices, and registry-registrar agreements. Extensible Provisioning Protocol or EPP is defined by a core set of RFCs that standardize the interface that make up the registry-registrar model. The SRS interface supports EPP 1.0 as defined in the following RFCs shown in Table 24-1 attached.

Additional information on the EPP implementation and compliance with RFCs can be found in the response to Question 25.

24.2.16 Compliance with Specification 10

Specification 10 of the New TLD Agreement defines the performance specifications of the TLD, including service level requirements related to DNS, RDDS (WHOIS), and EPP. The requirements include both availability and transaction response time measurements. As an experienced registry operator, Neustar has a long and verifiable track record of providing registry services that consistently exceed the performance specifications stipulated in ICANN agreements. This same high level of service will be provided for the ʺ.AUTOʺ Registry. The following section describes Neustarʹs experience and its capabilities to meet the requirements in the new agreement.

To properly measure the technical performance and progress of TLDs, Neustar collects data on key essential operating metrics. These measurements are key indicators of the performance and health of the registry. Neustarʹs current .biz SLA commitments are among the most stringent in the industry today, and exceed the requirements for new TLDs. Table 24-2 compares the current SRS performance levels compared to the requirements for new TLDs, and clearly demonstrates the ability of the SRS to exceed those requirements.

Their ability to commit and meet such high performance standards is a direct result of their philosophy towards operational excellence. See response to Question 31 for a full description of their philosophy for building and managing for performance.

24.3 Resourcing Plans

The development, customization, and on-going support of the SRS are the responsibility of a combination of technical and operational teams, including:

-Development⁄Engineering

-Database Administration

-Systems Administration

-Network Engineering.

Additionally, if customization or modifications are required, the Product Management and Quality Assurance teams will be involved in the design and testing. Finally, the Network Operations and Information Security play an important role in ensuring the systems involved are operating securely and reliably.

The necessary resources will be pulled from the pool of operational resources described in detail in the response to Question 31. Neustarʹs SRS implementation is very mature, and has been in production for over 10 years. As such, very little new development related to the SRS will be required for the implementation of the ʺ.AUTOʺ registry. The following resources are available from those teams:

-Development⁄Engineering 19 employees

-Database Administration- 10 employees

-Systems Administration 24 employees

-Network Engineering 5 employees

The resources are more than adequate to support the SRS needs of all the TLDs operated by Neustar, including the ʺ.AUTOʺ registry.

25. Extensible Provisioning Protocol (EPP)

25.1 Introduction

DOT Auto, LLCʹs back-end registry operator, Neustar, has over 10 years of experience operating EPP based registries. They deployed one of the first EPP registries in 2001 with the launch of .biz. In 2004, they were the first gTLD to implement EPP 1.0. Over the last ten years Neustar has implemented numerous extensions to meet various unique TLD requirements. Neustar will leverage its extensive experience to ensure DOT Auto, LLC is provided with an unparalleled EPP based registry. The following discussion explains the EPP interface which will be used for the ʺ.AUTOʺ registry. This interface exists within the protocol farm layer as described in Question 24 and is depicted in Figure 25-1 attached.

25.2 EPP Interface

Registrars are provided with two different interfaces for interacting with the registry. Both are EPP based, and both contain all the functionality necessary to provision and manage domain names. The primary mechanism is an EPP interface to connect directly with the registry. This is the interface registrars will use for most of their interactions with the registry.

However, an alternative web GUI (Registry Administration Tool) that can also be used to perform EPP transactions will be provided. The primary use of the Registry Administration Tool is for performing administrative or customer support tasks.

The main features of the EPP implementation are:

-Standards Compliance: The EPP XML interface is compliant to the EPP RFCs. As future EPP RFCs are published or existing RFCs are updated, Neustar makes changes to the implementation keeping in mind of any backward compatibility issues.

-Scalability: The system is deployed keeping in mind that it may be required to grow and shrink the footprint of the Registry system for a particular TLD.

-Fault-tolerance: The EPP servers are deployed in two geographically separate data centers to provide for quick failover capability in case of a major outage in a particular data center. The EPP servers adhere to strict availability requirements defined in the SLAs.

-Configurability: The EPP extensions are built in a way that they can be easily configured to turn on or off for a particular TLD.

-Extensibility: The software is built ground up using object oriented design. This allows for easy extensibility of the software without risking the possibility of the change rippling through the whole application.

-Auditable: The system stores detailed information about EPP transactions from provisioning to DNS and WHOIS publishing. In case of a dispute regarding a name registration, the Registry can provide comprehensive audit information on EPP transactions.

-Security: The system provides IP address based access control, client credential-based authorization test, digital certificate exchange, and connection limiting to the protocol layer.

25.3 Compliance with RFCs and Specifications

The registry-registrar model is described and embodied in a number of IETF RFCs, ICANN contracts and practices, and registry-registrar agreements. As shown in Table 25-1 attached, EPP is defined by the core set of RFCs that standardize the interface that registrars use to provision domains with the SRS. As a core component of the SRS architecture, the implementation is fully compliant with all EPP RFCs.

Neustar ensures compliance with all RFCs through a variety of processes and procedures. Members from the engineering and standards teams actively monitor and participate in the development of RFCs that impact the registry services, including those related to EPP. When new RFCs are introduced or existing ones are updated, the team performs a full compliance review of each system impacted by the change. Furthermore, all code releases include a full regression test that includes specific test cases to verify RFC compliance.

Neustar has a long history of providing exceptional service that exceeds all performance specifications. The SRS and EPP interface have been designed to exceed the EPP specifications defined in Specification 10 of the Registry Agreement and profiled in Table 25-2 attached. Evidence of Neustarʹs ability to perform at these levels can be found in the .biz monthly progress reports found on the ICANN website.

25.3.1 EPP Toolkits

Toolkits, under open source licensing, are freely provided to registrars for interfacing with the SRS. Both Java and C++ toolkits will be provided, along with the accompanying documentation. The Registrar Tool Kit (RTK) is a software development kit (SDK) that supports the development of a registrar software system for registering domain names in the registry using EPP. The SDK consists of software and documentation as described below.

The software consists of working Java and C++ EPP common APIs and samples that implement the EPP core functions and EPP extensions used to communicate between the registry and registrar. The RTK illustrates how XML requests (registration events) can be assembled and forwarded to the registry for processing. The software provides the registrar with the basis for a reference implementation that conforms to the EPP registry-registrar protocol. The software component of the SDK also includes XML schema definition files for all Registry EPP objects and EPP object extensions. The RTK also includes a dummy server to aid in the testing of EPP clients.

The accompanying documentation describes the EPP software package hierarchy, the object data model, and the defined objects and methods (including calling parameter lists and expected response behavior). New versions of the RTK are made available from time to time to provide support for additional features as they become available and support for other platforms and languages.

25.4 Proprietary EPP Extensions

[Default Response]

The ʺ.AUTOʺ registry will not include proprietary EPP extensions. Neustar has implemented various EPP extensions for both internal and external use in other TLD registries. These extensions use the standard EPP extension framework described in RFC 5730. Table 25-3 attached provides a list of extensions developed for other TLDs. Should the ʺ.AUTOʺ registry require an EPP extension at some point in the future, the extension will be implemented in compliance with all RFC specifications including RFC 3735.

The full EPP schema to be used in the ʺ.AUTOʺ registry is attached in the document titled EPP Schema Files.

25.5 Resourcing Plans

The development and support of EPP is largely the responsibility of the Development⁄Engineering and Quality Assurance teams. As an experience registry operator with a fully developed EPP solution, on-going support is largely limited to periodic updates to the standard and the implementation of TLD specific extensions.

The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams:

-Development⁄Engineering 19 employees

-Quality Assurance - 7 employees.

These resources are more than adequate to support any EPP modification needs of the ʺ.AUTOʺ registry.

26. Whois

DOT Auto, LLC recognizes the importance of an accurate, reliable, and up-to-date WHOIS database to governments, law enforcement, intellectual property holders, and the public as a whole, and is firmly committed to complying with all of the applicable WHOIS specifications for data objects, bulk access, and lookups as defined in Specifications 4 and 10 to the Registry Agreement and relevant RFCs.

DOT Auto, LLC’s back-end registry services provider, Neustar, has extensive experience providing ICANN and RFC-compliant WHOIS services for each of the TLDs that it operates both as a Registry Operator for gTLDs, ccTLDs, and back-end registry services provider. As one of the first “thick” registry operators in the gTLD space, the WHOIS service provided by DOT Auto, LLC’s registry services operator has been designed from the ground up to display as much information as required by ICANN and respond to a very stringent availability and performance requirement.

Some of the key features of DOT Auto, LLC’s WHOIS services will include: 

• Fully compliant with all relevant RFCs including 3912;
• Production proven, highly flexible, and scalable (DOT Auto, LLC’s back-end registry services provider has a track record of 100% availability over the past 10 years);
• Exceeds current and proposed performance specifications;
• Supports dynamic updates with the capability of doing bulk updates;
• Geographically distributed sites to provide greater stability and performance; and
• Search capabilities (e.g., IDN, registrant data) that mitigate potential forms of abuse as discussed below.
DOT Auto, LLC’s registry services operator will provide thick WHOIS services that are fully compliant with RFC 3912 and with Specifications 4 and 10 of the Registry Agreement. 

DOT Auto, LLC’s WHOIS service will support port 43 queries, and will be optimized for speed using an in-memory database and a master-slave architecture between SRS and WHOIS slaves. RFC 3912 is a simple text based protocol over TCP that describes the interaction between the server and client on port 43. DOT Auto, LLC’s registry services operator currently processes millions of WHOIS queries per day.

In addition to the WHOIS Service on port 43, DOT Auto, LLC will provide a Web-based WHOIS application, which will be located at www.whois.auto. This WHOIS Web application will be an intuitive and easy to use application for the general public to use. The WHOIS Web application provides all of the features available in the port 43 WHOIS. This includes full and partial search on:
• Domain names
• Nameservers
• Registrant, Technical and Administrative Contacts
• Registrars
The WHOIS web application will also provide features not available on the port 43 service. These include:
• Extensive support for international domain names (IDN)
• Ability to perform WHOIS lookups on the actual Unicode IDN
• Display of the actual Unicode IDN in addition to the ACE-encoded name
• A Unicode to Punycode and Punycode to Unicode translator
• An extensive FAQ
• A list of upcoming domain deletions
DOT Auto, LLC will also provide a searchable web-based WHOIS service in accordance with Specification 4 Section 1.8 The application will enable users to search the WHOIS directory to find exact or partial matches using any one or more of the following fields: 
• Domain name
• Contacts and registrant’s name
• Contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.)
• Registrar ID
• Name server name and IP address
• Internet Protocol addresses
• The system will also allow search using non-Latin character sets which are compliant with IDNA specification
The WHOIS user will be able to choose one or more search criteria, combine them by Boolean operators (AND, OR, NOT) and provide partial or exact match regular expressions for each of the criterion name-value pairs. The domain names matching the search criteria and their WHOIS information will quickly be returned to the user.
In order to reduce abuse for this feature, only authorized users will have access to the Whois search features after providing a username and password. DOT Auto, LLC will provide third party access to the bulk zone file in accordance with Specification 4, Section 2 of the Registry Agreement. Credentialing and dissemination of the zone files will be facilitated through the Central Zone Data Access Provider, which will make access to the zone files in bulk via FTP to any person or organization that signs and abides by a Zone File Access (ZFA) Agreement with the registry. Contracted gTLD registries will provide this access daily and at no charge. 
DOT Auto, LLC will also provide ICANN and any emergency operators with up-to-date Registration Data on a weekly basis (the day to be designated by ICANN). Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN. The file(s) will be made available for download by SFTP, unless ICANN requests other means in the future.
DOT Auto, LLC’s Legal Team consisting of 3 dedicated employees, will regularly monitor the registry service provider to ensure that they are providing the services as described above. This will entail random monthly testing of the WHOIS port 43 and Web-based services to ensure that they meet the ICANN Specifications and RFCs as outlined above, if not, to follow up with the registry services provider to ensure that they do. As the relevant WHOIS will only contain DOT Auto, LLC’s information, DOT Auto, LLC’s WHOIS services will necessarily be in compliance with any applicable privacy laws or policies.

27. Registration Life Cycle

25.1 Introduction

25.2 EPP Interface

The main features of the EPP implementation are:

-Scalability: The system is deployed keeping in mind that it may be required to grow and shrink the footprint of the Registry system for a particular TLD.

-Configurability: The EPP extensions are built in a way that they can be easily configured to turn on or off for a particular TLD.

-Security: The system provides IP address based access control, client credential-based authorization test, digital certificate exchange, and connection limiting to the protocol layer.

25.3 Compliance with RFCs and Specifications

25.3.1 EPP Toolkits

25.4 Proprietary EPP Extensions

[Default Response]

The full EPP schema to be used in the ʺ.AUTOʺ registry is attached in the document titled EPP Schema Files.

25.5 Resourcing Plans

The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams:

-Development⁄Engineering 19 employees

-Quality Assurance - 7 employees.

These resources are more than adequate to support any EPP modification needs of the ʺ.AUTOʺ registry.

28. Abuse Prevention and Mitigation

 General Statement of Policy

Abuse within the registry will not be tolerated. DOT Auto, LLC will implement very strict policies and procedures to minimize abusive registrations and other activities that have a negative impact on Internet users. DOT Auto, LLC’s homepages will provide clear contact information for its Abuse Team, and in accordance with ICANN policy DOT Auto, LLC shall host NIC.AUTO providing access to .AUTO’s WhoIs services, the Abuse Policy, and contact information for the Abuse Team.

Anti-Abuse Policy

DOT Auto, LLC will implement in its internal policies and its Registry-Registrar Agreements (RRAs) that all registered domain names in the TLD will be subject to a Domain Name Anti-Abuse Policy (“Abuse Policy”).

The Abuse Policy will provide DOT Auto, LLC with broad power to suspend, cancel, or transfer domain names that violate the Abuse Policy. DOT Auto, LLC will publish the Abuse Policy on its home website at NIC.AUTO and clearly provide DOT Auto, LLC’s Point of Contact (“Abuse Contact”) and its contact information. This information shall consist of, at a minimum, a valid e-mail address dedicated solely to the handling of abuse complaints, and a telephone number and mailing address for the primary contact. DOT Auto, LLC will ensure that this information will be kept accurate and up to date and will be provided to ICANN if and when changes are made. 

In addition, with respect to inquiries from ICANN-Accredited Registrars, the Abuse Contact shall handle requests related to abusive domain name practices.

Inquiries addressed to the Abuse Contact will be routed to DOT Auto, LLC’s Legal Team who will review and if applicable remedy any Complaint regarding an alleged violation of the Abuse Policy as described in more detail below. DOT Auto, LLC will catalog all abuse communications in its CRM software using a ticketing system that maintains records of all abuse complaints indefinitely. Moreover, DOT Auto, LLC shall only provide access to these records to third parties under limited circumstances, such as in response to a subpoena or other such court order or demonstrated official need by law enforcement.

The Abuse Policy will state, at a minimum, that DOT Auto, LLC reserves the right to deny, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary to ; (1) to protect the integrity and stability of the registry; (2) to comply with applicable laws, government rules or requirements, or court orders; (3) to avoid any liability, civil or criminal, on the part of DOT Auto, LLC, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) to correct mistakes made by the DOT Auto, LLC, registry services provider, or any Registrar in connection with a domain name registration; (5) during resolution of any dispute regarding the domain; and (6) if a Registrant’s pre-authorization or payment fails; or (7) to prevent the bad faith use of a domain name that is identical to a registered trademark and being used to confuse users.

The Abuse Policy will define the abusive use of domain names to include, but not be limited to, the following activities:

• Illegal or fraudulent actions: use of the DOT Auto, LLC’s or Registrarʹs services to violate the laws or regulations of any country, state, or infringe upon the laws of any other jurisdiction, or in a manner that adversely affects the legal rights of any other person;
• Spam: use of electronic messaging systems from email addresses from domains in the TLD to send unsolicited bulk messages. The term applies to e-mail spam and similar abuses such as instant messaging spam, mobile messaging spam, and the spamming of Web sites and Internet forums;
• Trademark and Copyright Infringement: DOT Auto, LLC will take great care to ensure that trademark and copyright infringement does not occur within the .AUTO TLD. DOT Auto, LLC will employ notice and takedown procedures based on the provisions of the Digital Millennium Copyright Act (DMCA) ;
• Phishing: use of counterfeit Web pages within the TLD that are designed to trick recipients into divulging sensitive data such as usernames, passwords, or financial data;
• Pharming: redirecting of unknowing users to fraudulent Web sites or services, typically through DNS hijacking or poisoning;
• Willful distribution of malware: dissemination of software designed to infiltrate or damage a computer system without the ownerʹs informed consent. Examples include, without limitation, computer viruses, worms, keyloggers, and trojan horses.
• Fast flux hosting: use of fast-flux techniques to disguise the location of Web sites or other Internet services, or to avoid detection and mitigation efforts, or to host illegal activities. Fast-flux techniques use DNS to frequently change the location on the Internet to which the domain name of an Internet host or name server resolves. Fast flux hosting may be used only with prior permission of DOT Auto, LLC;
• Botnet command and control: services run on a domain name that are used to control a collection of compromised computers or ʺzombies,ʺ or to direct denial-of-service attacks (DDoS attacks);
• Distribution of pornography;
• Illegal Access to Other Computers or Networks: illegally accessing computers, accounts, or networks belonging to another party, or attempting to penetrate security measures of another individualʹs system (often known as ʺhackingʺ). Also, any activity that might be used as a precursor to an attempted system penetration (e.g., port scan, stealth scan, or other information gathering activity);
• Domain Kiting⁄Tasting: registration of domain names to test their commercial viability before returning them during a Grace Period;
• High Volume Registrations⁄Surveying: registration of multiple domain names in order to warehouse them for sale or pay-per-click websites in a way that can impede DOT Auto, LLC from offering them to legitimate users or timely services to other subscribers;
• Geographic Name: registering a domain name that is identical to a Geographic Name, as defined by Specification 5 of the Registry Agreement;
• Inadequate Security: registering and using a domain name to host a website that collects third-party information but does not employ adequate security measures to protect third-party information in accordance with that geographic area’s data and financial privacy laws;
• Front Running: Registrars mining their own web and WhoIs traffic to obtain insider information with regard to high-value second-level domains, which the Registrar will then register to itself or an affiliated third party for sale or to generate advertising revenue;
• WhoIs Accuracy: Intentionally inserting false or misleading Registrant information into the TLD’s WhoIs database in connection with the bad faith registration and use of the domain in question;
• WhoIs Misuse: abusing access to the WhoIs database by using Registrant information for data mining purposes or other malicious purposes;
• Fake Renewal Notices; misusing WhoIs Registrant information to send bogus renewal notices to Registrants on file with the aim of causing the Registrant to spend unnecessary money or steal or redirect the domain at issue.

Domain Anti-Abuse Procedure

DOT Auto, LLC will provide a domain name anti-abuse procedure modeled after the DMCA’s notice-and-takedown procedure.

At all times, DOT Auto, LLC will publish on its home website at NIC.AUTO the Abuse Policy and the contact information for the Abuse Contact. Inquiries addressed to the Point of Contact will be addressed to and received by DOT Auto, LLC’s Legal Team who will review and if applicable remedy any Complaint regarding an alleged violation of the Abuse Policy. DOT Auto, LLC will catalog all abuse communications and provide them to third parties only under limited circumstances, such as in response to a subpoena or other such court order or demonstrated official need by law enforcement.

Any correspondence (“Complaint”) from a complaining party (“Complainant”) to the Abuse Contact will be ticketed in DOT Auto, LLC’s CRM software and relayed to DOT Auto, LLC’s Abuse Team. A member of DOT Auto, LLC’s Abuse Team will then send an email to the Complainant within forty-eight (48) hours of receiving the Complaint confirming receipt of the email and that DOT Auto, LLC will notify the Complainant of the results of the Complaint within ten (10) days of receiving the Complaint.

DOT Auto, LLC’s Abuse Team will review the Complaint and give it a “quick look” to see if the Complaint reasonably falls within an abusive use as defined by the Abuse Policy. If not, the Contact will write an email to the Complainant within thirty-six (36) hours of sending the confirmation email that the subject of the complaint clearly does not fall within one of the delineated abusive uses as defined by the Abuse Policy and that DOT Auto, LLC considers the matter closed.

If the quick look does not resolve the matter, DOT Auto, LLC’s Abuse Team will give the Complaint a full review. Any Registrant that has been determined to be in violation of DOT Auto, LLC policies shall be notified of the violation of such policy and their options to cure the violation. 
Such notification shall state:
1) the nature of the violation;
2) the proposed remedy to the violation;
3) the time frame to cure the violation; and
4) the Registry’s options to take subsequent action if the Registrant does not cure the violation.
If an abusive use is determined DOT Auto, LLC’s Abuse Team will alert it’s Registry services team to immediately cancel the resolution of the domain name. DOT Auto, LLC’s Abuse Team will immediately notify the Registrant of the suspension of the domain name, the nature of the complaint, and provide the Registrant with the option to respond within ten (10) days or the domain will be canceled.
If the Registrant responds within ten (10) business days, it’s response will be reviewed by the DOT Auto, LLC’s Abuse Team for further review. If DOT Auto, LLC’s Abuse Team is satisfied by the Registrant’s response that the use is not abusive, DOT Auto, LLC’s Abuse Team will submit a request by the registry services provider to reactivate the domain name. DOT Auto, LLC’s Abuse Team will then notify the Complainant that its complaint was ultimately denied and provide the reasons for the denial. If the Registrant does not respond within ten (10) business days, DOT Auto, LLC will notify the registry services team to cancel the abusive domain name.

This Anti-Abuse Procedure will not prejudice either party’s election to pursue another dispute mechanism, such as URS or UDRP.

With the resources of DOT Auto, LLC’s registry services personnel, DOT Auto, LLC can meet its obligations under Section 2.8 of the Registry Agreement where required to take reasonable steps to investigate and respond to reports from law enforcement and governmental and quasi-governmental agencies of illegal conduct in connection with the use of its TLD. The Registry will respond to legitimate law enforcement inquiries within one (1) business day from receiving the request. Such response shall include, at a minimum, an acknowledgement of receipt of the request, questions, or comments concerning the request, and an outline of the next steps to be taken by Application for rapid resolution of the request. 

In the event such request involves any of the activities which can be validated by DOT Auto, LLC and involves the type of activity set forth in the Abuse Policy, the sponsoring Registrar is then given forty-eight (48) hours to investigate the activity further and either take down the domain name by placing the domain name on hold or by deleting the domain name in its entirety or providing a compelling argument to the registry to keep the name in the zone. If the Registrar has not taken the requested action after the 48-hour period (i.e., is unresponsive to the request or refuses to take action), DOT Auto, LLC will place the domain on “serverHold”.

Maintenance of Registration Criteria

1) All Registrants awarded a “.AUTO” domain will agree to a one year minimum contract, which will need to be renewed on an annual basis. Renewal is the sole responsibility of the Registrant. Registrant’s failing to renew their awarded domains by their expiration dates will be given a 60 day renewal grace period prior to their domain being revoked and returned to general availability.

2) DOT Auto, LLC is not liable or responsible in any way for any errors, omissions or any other actions by any third party (including any Registrar service) arising out of or related to a given Registrant’s application for, registration of, renewal of, or failure to register or renew a particular domain name.

3) Through the registration process all Registrants will be expected to designate an administrative contact for their application, which would possess all the rights granted by DOT Auto, LLC or its designated agents to act in respect to the given domain including but not limited to managing the domain name or any services associated thereto. It is the Registrant’s responsibility to update and maintain accurate contact information for their registrations.


Orphan Glue Removal

As the Security and Stability Advisory Committee of ICANN (SSAC) rightly acknowledges, although orphaned glue records may be used for abusive or malicious purposes, the “dominant use of orphaned glue supports the correct and ordinary operation of the DNS.” See http:⁄⁄www.icann.org⁄en⁄committees⁄security⁄sac048.pdf. 

While orphan glue often supports correct and ordinary operation of the DNS, we understand that such glue records can be used maliciously to point to name servers that host domains used in illegal phishing, bot-nets, malware, and other abusive behaviors. Problems occur when the parent domain of the glue record is deleted but its children glue records still remain in the DNS. Therefore, when DOT Auto, LLC has written evidence of actual abuse of orphaned glue, DOT Auto, LLC will take action to remove those records from the zone to mitigate such malicious conduct. 

DOT Auto, LLC’s registry service operator will run a daily audit of entries in its DNS systems and compare those with its provisioning system. This serves as an umbrella protection to make sure that items in the DNS zone are valid. Any DNS record that shows up in the DNS zone but not in the provisioning system will be flagged for investigation and removed if necessary. This daily DNS audit serves to not only prevent orphaned hosts but also other records that should not be in the zone. 

In addition, if either DOT Auto, LLC or its registry services operator becomes aware of actual abuse on orphaned glue after receiving written notification by a third party through its Abuse Contact or through its customer support, such glue records will be removed from the zone.

WhoIs Accuracy

DOT Auto, LLC will provide WhoIs accessibility in a reliable, consistent, and predictable fashion in order to promote Whois accuracy. The Registry will adhere to port 43 WhoIs Service Level Agreements (SLAs), which require that port 43 WHOIS service be highly accessible and fast. 

DOT Auto, LLC will offer thick WhoIs services, in which all authoritative WhoIs data—including contact data—is maintained at the registry. DOT Auto, LLC will maintain timely, unrestricted, and public access to accurate and complete WhoIs information, including all data objects as specified in Specification 4. Moreover, prior to the release of any domain names, DOT Auto, LLC’s Registrar will provide DOT Auto, LLC with an authorization code to verify eligible Registrants provide accurate Registrant contact information. 

In order to further promote WhoIs accuracy, DOT Auto, LLC will offer a mechanism whereby third parties can submit complaints directly to the DOT Auto, LLC (as opposed to ICANN or the sponsoring Registrar) about inaccurate or incomplete WhoIs data. Such information shall be forwarded to the Registrar, who shall be required to address those complaints with their Registrants. Thirty days after forwarding the complaint to the Registrar, DOT Auto, LLC will examine the current WhoIs data for names that were alleged to be inaccurate to determine if the information was corrected, the domain name was deleted, or there was some other disposition. If the Registrar has failed to take any action, or it is clear that the Registrant was either unwilling or unable to correct the inaccuracies, DOT Auto, LLC reserves the right to cancel or suspend the applicable domain name(s) should DOT Auto, LLC determine that the domains are being used in a manner contrary to DOT Auto, LLC’s abuse policy. 

DOT Auto, LLC shall also require authentication and verification of all Registrant data. DOT Auto, LLC shall verify, contact information, e-mail address, and, to the best of its abilities, determine whether address information supplied is accurate. Second-level domains in the TLD shall not be operational unless two (2) out of three (3) of the above authentication methods have been satisfied. 

DOT Auto, LLC will also maintain historical databases of Registrants and associated information which have provided inaccurate WhoIs information. DOT Auto, LLC will endeavor to use this database to uncover patterns of suspicious registrations which DOT Auto, LLC shall then flag for further authentication or for review of the Registrant’s use of the domain in question to ensure Registrant’s use is consonant with DOT Auto, LLC’s abuse policy.

In addition, DOT Auto, LLC’s Abuse Team shall on its own initiative, no less than twice per year, perform a manual review of a random sampling of domain names within the applied-for TLD to test the accuracy of the WhoIs information. Although this will not include verifying the actual information in the WHOIS record, DOT Auto, LLC will be examining the WHOIS data for prima facie evidence of inaccuracies. In the event that such evidence exists, it shall be forwarded to the Registrar, who shall be required to address those complaints with their Registrants. Thirty days after forwarding the complaint to the Registrar, the DOT Auto, LLC will examine the current WhoIs data for names that were alleged to be inaccurate to determine if the information was corrected, the domain name was deleted, or there was some other disposition. If the Registrar has failed to take any action, or it is clear that the Registrant was either unwilling or unable to correct the inaccuracies, DOT Auto, LLC reserves the right to suspend the applicable domain name(s) should DOT Auto, LLC determine that the Registrant is using the domain in question in a manner contrary to DOT Auto, LLC’s abuse policy. DOT Auto, LLC shall also reserve the right to report such recalcitrant Registrar activities directly to ICANN.

Abuse Prevention and Mitigation – Domain Name Access

All domain name Registrants will have adequate controls to ensure proper access to domain functions.

In addition to the above, all domain name Registrants in the applied-for TLD will be required to name at least two (2) unique points of contact who are authorized to request and⁄or approve update, transfer, and deletion requests. The points of contact must establish strong passwords with the Registrar that must be authenticated before a point of contact will be allowed to process updates, transfer, and deletion requests. Once a process update, transfer, or deletion request is entered, the points of contact will automatically be notified when a domain has been updated, transferred, or deleted through an automated system run by DOT Auto, LLC’s Registrar. Authentication of modified Registrant information shall be accomplished within 72 hours of receipt.

29. Rights Protection Mechanisms

DOT Auto, LLC is committed to implementing strong and integrated Rights Protection Mechanisms (RPM). Use of domain names that infringe upon the legal rights of others in the TLD will not be tolerated. The nature of such uses creates security and stability issues for the registry, Registrars, and Registrants, as well as for users of the Internet in general. DOT Auto, LLC will protect the legal rights of others by implementing RPMs and anti-abuse policies backed by robust responsiveness to complaints and requirements of DOT Auto, LLC’s Registrars.

Trademark Clearinghouse

Each new gTLD Registry will be required to implement support for, and interaction with, the Trademark Clearinghouse (“Clearinghouse”). The Clearinghouse is intended to serve as a central repository for information to be authenticated, stored, and disseminated pertaining to the rights of trademark holders. The data maintained in the Clearinghouse will support and facilitate other RPMs, including the mandatory Sunrise Period and Trademark Claims service.

Utilizing the Clearinghouse, all operators of new gTLDs must offer: (i) a Sunrise registration service for at least 30 days during the pre-launch phase giving eligible trademark owners an early opportunity to register second-level domains in new gTLDs; and (ii) a Trademark Claims Service for at least the first 60 days that second-level registrations are open. The Trademark Claims Service is intended to provide clear notice to a potential Registrant of the rights of a trademark owner whose trademark is registered in the Clearinghouse.

Sunrise A Period

DOT Auto, LLC will offer segmented Sunrise Periods. The initial Sunrise Period will last [minimum 30 days] for owners of trademarks listed in the Clearinghouse to register domain names that consist of an identical match of their listed trademarks. All domain names registered during the Sunrise Period will be subject to DOT Auto, LLC’s domain name registration policies. DOT Auto, LLC will assign its RPM Team to receive and authenticate all Sunrise Registrations. DOT Auto, LLCʹs rights protection team will be headed by our Director of Legal and Policy and will have two full time dedicated employees in order to successfully handle all incoming RPM issues.

DOT Auto, LLC’s Registrar will ensure that all Sunrise Registrants meet sunrise eligibility requirements (SERs), which will be verified by Clearinghouse data. The proposed SERs include: (i) ownership of a mark that is (a) nationally or regionally registered and for which proof of use, such as a declaration and a single specimen of current use – was submitted to, and validated by, the Trademark Clearinghouse; or (b) that have been court-validated; or (c) that are specifically protected by a statute or treaty currently in effect and that was in effect on or before 26 June 2008, (ii) optional registry elected requirements concerning international classes of goods or services covered by registration; (iii) representation that all provided information is true and correct; and (iv) provision of data sufficient to document rights in the trademark.

Upon receipt of the Sunrise application, DOT Auto, LLC will issue a unique tracking number to the Registrar, which will correspond to that particular application. All applications will receive tracking numbers regardless of whether they are complete. Applications received during the Sunrise period will be accepted on a first-come, first-serve basis. Upon submission of all of the required information and documentation, Registrar will forward the information to DOT Auto, LLC’s RPM Team for authentication. DOT Auto, LLC’s RPM Team will review the information and documentation, verify the trademark information, and notify the potential Registrant of any deficiencies. If a Registrant does not cure any trademark-related deficiencies and⁄or respond by the means listed within one (1) week, DOT Auto, LLC will notify its Registrar and the domain name will be released for registration.

DOT Auto, LLC will incorporate a Sunrise Dispute Resolution Policy (SDRP). The SRDP will allow challenges to Sunrise Registrations by third parties for a ten-day period after acceptance of the registration based on the following four grounds: (i) at time the challenged domain name was registered, the Registrant did not hold a trademark registration of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty; (ii) the domain name is not identical to the mark on which the Registrant based its Sunrise registration; (iii) the trademark registration on which the Registrant based its Sunrise registration is not of national or regional effect or the trademark had not been court-validated or protected by statute or treaty; or (iv) the trademark registration on which the domain name Registrant based its Sunrise registration did not issue on or before the effective date of the Registry Agreement and was not applied for on or before ICANN announced the applications received.

After receiving a Sunrise Complaint, DOT Auto, LLC’s RPM Team will review the Complaint to see if the Complaint reasonably asserts a legitimate challenge as defined by the SDRP. If not, DOT Auto, LLC’s RPM Team will send an email to the Complainant within thirty-six (36) hours of sending the confirmation email that the subject of the complaint clearly does not fall within one of the delineated grounds as defined by the SDRP and that DOT Auto, LLC considers the matter closed.

If the domain name is not found to have adequately met the SERs, DOT Auto, LLC RPM Team will alert the Registrar and registry services provider to immediately suspend the resolution of the domain name. Thereafter, DOT Auto, LLC’s RPM Team will immediately notify the Sunrise Registrant of the suspension of the domain name, the nature of the complaint, and provide the Registrant with the option to respond within ten (10) days to cure the SER deficiencies or the domain name will be canceled.

If the Registrant responds within ten (10) business days, its response will be reviewed by DOT Auto, LLC’s RPM Team to determine if the SERs are met. If DOT Auto, LLC’s RPM Team is satisfied by the Registrant’s response, DOT Auto, LLC’s RPM Team will submit a request to the Registrar and the registry services provider to un-suspend the domain name. DOT Auto, LLC’s RPM Team will then notify the Complainant that its complaint was ultimately denied and provide the reasons for the denial.

Names secured as described through the Sunrise AT⁄AD processes will result in the registration of resolving domain names at the registry. Names reserved through the Sunrise B process will not result in resolving domain name at DOT Auto, LLC. Rather, these names will be reserved and blocked from live use. The applied for string will resolve to an informational page informing visitors that the name is unavailable for registration and reserved from use.

Applications that fit the following criteria will be considered during the Sunrise A⁄D period: Applicant owns and operates an existing domain name in another gTLD or ccTLD, in connection with eligible commerce and satisfies the registration requirements described in Section 1.

Sunrise B
Applications that fit the following criteria will be considered during the Sunrise B period:
a) Applicant holds valid trademark registrations or owns rights to a particular name and wishes to block the use of such name.
b) The Applicant must seek to block a name that corresponds to the entire text of its trademark or the complete textual component of a graphical or compound trademark. Certain variances are permitted for trademarks containing spaces or special characters that are not available for domain names.

Founder’s Program
Applications for the Founder’s Program will be accepted after the close of the Sunrise Periods. Potential Registrants should understand that certain expectations, as described herein will accompany the issuance of a domain name under the Founder’s Program and all registrations resulting from this program will be required to follow the below listed guidelines, which will be further described in their Program Agreement:
a) Registrants awarded a domain through the Founder’s Program must use their best efforts to launch a “.AUTO” website within 30 days of signing the Program Agreement.
b) In addition, each Registrant will be required to issue a press release announcing the launch of their “.AUTO” Founder Website, concurrent with the launch of their “.AUTO” Founder Website, said press release must be approved by DOT Auto, LLC;
c) Founders are expected to proactively market and promote “.AUTO” gTLD in a manner that is likely to produce widespread awareness of the unique advantages gained through the “.AUTO” string.
d) Founders will allow DOT Auto, LLC to use in good faith Founder’s name, likeness, trademarks, logos, and Application contents (other than Confidential Information,) as well as other Founder information and content as may be mutually agreed, in DOT Auto, LLC’s marketing, promotional and communications materials.

DOT Auto, LLC will randomly verify compliance of the above listed expectations and have the right to revoke any Founder’s site, should they be deemed non-compliant. Additionally, DOT Auto, LLC may suspend or delete a Founder’s site without prior notice to the Registrar or Registrant if the Founder’s site is deemed in violation of any of DOT Auto, LLCʹs registration guidelines or policies.
Registrants participating in the Founders program will receive 25% off their initial registration fees, additional discounts may be offered to founders at the time of renewal, should DOT Auto, LLC choose to offer additional discounts to founders or term extensions (not to exceed 5 years) DOT Auto, LLC will seek advance approval from ICANN via the specified channels.

Landrush
Landrush is a limited time opportunity for companies that want to secure a high value “.AUTO” name for a small fee (above the basic registration cost). The landrush period will last 30 days. Applications will be accepted and evaluated to determine if they meet the requirements for registration. At the end of the Landrush period domain names with only one application will be awarded directly to the Applicant. Domain names with two or more applications will proceed to a closed mini auction, between the respective Applicants, where the highest bidder wins.

General Availability Period
Applicant must meet all registration requirements.
Names will be awarded on a first-come, first serve basis which is determined as of the time of the initial request, not when authentication occurs.

Domain Name Contentions
Name contentions will arise when both a Sunrise A and Sunrise B application are submitted for the same name, the following actions will be taken to resolve the contention.
a) Both Applicants will be notified of the contention and the Sunrise A Applicant will be given first right to either register their requested domain or withdraw their application. A domain applied for under Sunrise A will, all else being equal, receive priority over the identical domain applied for under Sunrise B. Sunrise A names get priority over Sunrise B names.
b) If the Sunrise Applicant chooses to register their name regardless of the contention, then the Sunrise B Applicant may choose to pursue further action independently of DOT Auto, LLC to contest the name. These processes may include UDRP or Civil Court and are not connected to DOT Auto’s sunrise policies.
c) If two Sunrise A Applicants apply for the same domain name (i.e., Delta Airlines and Delta Faucet both seek to be awarded the use of DELTA.auto) then DOT Auto, LLC will notify both Applicants of the contention and proceed to an auction process as described in Section 9.
d) If two Sunrise B Applicants apply for the same domain name (i.e., Delta Airlines and Delta Faucet, both seek to block the use of DELTA. auto), then DOT Auto, LLC will accept both applications as valid and block the use of the indicated domain.

Appeal of Rejected Sunrise Applications
An Applicant can file a request for reconsideration within 10 days of the notification of DOT Auto, LLC’s rejection. Reconsideration can be requested by completing a reconsideration form and filing a reconsideration fee with DOT Auto, LLC. Forms, fee information, and process documentation will be available on the DOT Auto, LLC website. Upon receipt of the reconsideration form and the corresponding fee, DOT Auto, LLC or its Agents will re-examine the application, and notify the Registrant of all findings or additional information needed. The Request for Reconsideration must be submitted through the Registrant’s Registrar, and a reconsideration fee must be paid to DOT Auto, LLC.

Auctions
Sunrise A names found to be in contention as described above will result in Auction. DOT Auto, LLC plans to have a qualified third party conduct our auction processes, therefore the rules contained in this document are subject to change based on the selection of an auctioneer:
a) All auction participants are expected to keep their account information current, throughout the auction process.
b) Auction participants will receive up to date communication from the auctioneer as the auction progresses, bidding status changes, or issues arise.

Bidding
a) Auctions will follow a standard process flow: scheduled (upcoming), open and closed.
b) You will receive an “Auction Scheduled” notice at least ten (10) days prior to the scheduled auction start date. You will receive an “Auction Start” notice on the auction start date, which will indicate that you may begin placing bids through the interface. Once closed, the auction is complete and if you are the winning bidder, you will proceed to the payment process.
c) If you choose to bid for a particular domain and you are the highest bidder at the end of an auction, you are obligated to complete the transaction and pay the Auctioneer the amount of your winning bid. Carefully consider your bids prior to placing them - bids are not retractable under any circumstances.
d) If no bids are placed on a particular domain, the Registry will register the domain on behalf of the first customer (in the respective phase) to submit an application through a Registrar.

Extensions
a) A normal auction period is anticipated to last a minimum of 7 (seven) days. However, in the event of significant auction activity, an auction close may extend during the last twenty-four (24) hours of scheduled operation to better need the volume of the auction.
b) Auction extensions are meant to provide a mechanism that is fair for bidders in all time zones to respond to being outbid.
c) An auction extension will occur whenever the auction lead changes in the last twenty- four (24) hours of the schedule of an auction. The close will be revised to reflect a new closing time set at twenty- four (24) hours after the change in auction lead occurred. Essentially, this means that a winning maximum bid has to remain unchallenged for a period of twenty- four (24) hours before the auction will close.
d) It is important to note that extensions are not simply based on the auction value changing since this could occur as a result of proxy bidding where the same bidder retains their lead. In this case, the maximum bid has not changed, the leader has not changed and therefore no extension will occur.

Payment Default
In the event that you as the winning bidder decide not to honor your payment obligations (or in the event of a reversal of payment or a charge back by a credit card company or other payment provider) on any outstanding balance, the Registry has the right to cancel any⁄all of your winning registrations for any .auto domain name, regardless of whether they have been paid for or not. You do not have the right to “pick and choose” the names you wish to keep or not keep. Winning an auction creates an obligation to remit payment. Failure to remit payment is a breach of your agreement. You will lose any previously won domains and will no longer be allowed to bid on any current or future auctions sponsored by DOT Auto, LLC. Participants are encouraged therefore to consider carefully each bid submitted as any bid could be a winning bid.
Trademark Claims Service

DOT Auto, LLC will offer a Trademark Claims Service to provide maximum protection and value to rights holders. The Trademark Claims Service will be monitored and operated by DOT Auto, LLC’s RPM Team that will receive all communications regarding the Trademark Claims Service and catalog them. DOT Auto, LLC’s Registrar will review all domain name requests to determine if they are an identical match of a trademark filed with the Trademark Clearinghouse. A domain name will be considered an identical match when the domain name consists of the complete and identical textual elements of the mark, and includes domain names where (a) spaces contained within a mark that are either replaced by hyphens (and vice versa) or omitted; (b) certain special characters contained within a trademark are spelled out with appropriate words describing it (e.g., @ and &); and (c) punctuation or special characters contained within a mark that are unable to be used in a second-level domain name are either (i) omitted or (ii) replaced by spaces, hyphens or underscores. Domain names that are plural forms of a mark, or that merely contain a mark, will not qualify as an identical match.

If the Registrar determines that a prospective domain name registration is identical to a mark registered in the Trademark Clearinghouse, the Registrar will be required to email a “Trademark Claims Notice” (Notice) in English to the protective Registrant of the domain name and copy DOT Auto, LLC’s RPM Team. The Notice will provide the prospective Registrant information regarding the trademark referenced in the Trademark Claims Notice to enhance understanding of the Trademark rights being claimed by the trademark holder. The Notice will be provided in real time without cost to the prospective Registrant.

After receiving the notice, the Registrar will provide the prospective Registrant five (5) days to reply to the Trademark Claims Service with a signed document that specifically warrants that: (i) the prospective Registrant has received notification that the mark is included in the Clearinghouse; (ii) the prospective Registrant has received and understood the notice; and (iii) to the best of the prospective Registrant’s knowledge the registration and use of the requested domain name will not infringe on the rights that are the subject of the notice. If the warranty document satisfies these requirements, the Registrar will effectuate the registration and notify DOT Auto, LLC’s RPM Team.

After the effectuation of a registration that is identical to a mark listed in the Trademark Clearinghouse, the Registrar will provide clear notice to the trademark owner consisting of the domain name that has been registered and copy DOT Auto, LLC’s RPM Team. The trademark owner then has the option of filing a Complaint under the Uniform Domain Name Dispute Resolution Policy (UDRP) or the Uniform Rapid Suspension System (URS).

Uniform Rapid Suspension System (URS)

DOT Auto, LLC will specify in the Registry Agreement, all RRAs, and all Registration Agreements used in connection with the TLD that it and its Registrars will abide by all decisions made by panels in accordance with the Uniform Rapid Suspension System (URS). DOT Auto, LLC’s RPM Team will receive all URS Complaints and decisions, and will notify its Registrar to suspend all registrations determined by a URS panel to be infringing within a commercially reasonable time of receiving the decision. DOT Auto, LLC’s RPM Team will catalog all abuse communications, but only provide them to third-parties under limited circumstances, such as in response to a subpoena or other such court order or demonstrated official need by law enforcement.

Uniform Domain Name Dispute Resolution Policy (UDRP)

DOT Auto, LLC will specify in the Registry Agreement, all Registry-Registrar Agreements, and Registration Agreements used in connection with the TLD that it will promptly abide by all decisions made by panels in accordance with the Uniform Domain Name Dispute Resolution Policy (UDRP). DOT Auto, LLC’s RPM Team will receive all UDRP Complaints and decisions, and will notify its Registrar to cancel or transfer all registrations determined to by a UDRP panel to be infringing within ten (10) business days of receiving the decision. DOT Auto, LLC’s RPM Team will catalog all abuse communications, but only provide them to third-parties under limited circumstances, such as in response to a subpoena or other such court order or demonstrated official need by law enforcement.

Proven Registrars

In order to reduce abusive registrations and other activities that affect the legal rights of others, DOT Auto, LLC will only contract with ICANN-accredited Registrars. The Registrar, according to the RRA, will not be able to register any domain names, thus eliminating the possibility of front-running.

Pre-Authorization and Authentication

Registrant authentication shall occur in accordance with the registration eligibility criteria and the Anti-Abuse Policy for “.AUTO” as set forth in Question 28.

The verification process is designed to prevent a prospective Registrant from providing inaccurate or incomplete data, such that, if necessary, the Registrant can be readily contacted regarding an infringing use of its site; indeed, the process (including verification of a Registrant’s certificate of incorporation) is designed to ensure that only qualified members of the community are permitted to register in the TLD.

Thick WhoIs

DOT Auto, LLC will include a thick WhoIs database as required in Specification 4 of the Registry agreement. A thick WhoIs provides numerous advantages including a centralized location of Registrant information, the ability to more easily manage and control the accuracy of data, and a consistent user experience.

Takedown Procedure

DOT Auto, LLC will provide a Takedown Procedure modeled after the Digital Millennium Copyright Act’s notice-and-takedown procedure.

At all times, DOT Auto, LLC will publish on its home website at NIC.AUTO contact information for receiving rights protection complaints (Complaint) from rights holders, including but not limited to trademark and copyright Complaints. Complaints will be addressed to and received by DOT Auto, LLCs RPM Team who will catalogue and ticket in DOT Auto, LLC’s CRM software and review as outlined herein. DOT Auto, LLC will catalog all rights protection communications and only provide them to third parties under limited circumstances, such as in response to a subpoena or other such court order or demonstrated official need by law enforcement.

Any Complaint from a rights holder will be relayed to DOT Auto, LLC’s RPM Team. A member of DOT Auto, LLC’s RPM Team will then send an email to the Complainant within forty-eight (48) hours of receiving the Complaint confirming receipt of the email, and that DOT Auto, LLC will notify the Complainant of the results of the Complaint within (10) days of receiving the Complaint.

After sending the confirmation email, DOT Auto, LLC’s RPM Team will review the Complaint. If DOT Auto, LLC or its Registrar determines that the registration was in bad faith, DOT Auto, LLC or its Registrar may cancel or suspend the resolution of the domain name. Bad faith registration includes, but is not limited to, the registration of a domain identical to a registered trademark where the Registrant has proceeded with registration after receipt of a Clearinghouse notice, as described above.

If the Registrant responds within ten (10) business days, its response will be reviewed by the DOT Auto, LLC’s RPM Team. If DOT Auto, LLC’s RPM Team is satisfied by the Registrant’s response that the content has been taken down or is not infringing, DOT Auto, LLC’s RPM Team will un-suspend the domain name. DOT Auto, LLC’s RPM Team will then notify the Complainant that its complaint was ultimately denied and provide the reasons for the denial. If the Registrant does not respond within ten (10) business days, DOT Auto, LLC or its Registrar may cancel or suspend the resolution of the domain name.

This Takedown Procedure will not prejudice any party’s election to pursue another dispute mechanism, such as URS or UDRP, as set forth in DOT Auto, LLC’s response to Question 28.

30(a). Security Policy: Summary of the security policy for the proposed registry

30.(a).1 Security Policies

DOT Auto, LLC and our back-end operator, Neustar recognize the vital need to secure the systems and the integrity of the data in commercial solutions. The ʺ.AUTOʺ registry solution will leverage industry-best security practices including the consideration of physical, network, server, and application elements.

Neustarʹs approach to information security starts with comprehensive information security policies. These are based on the industry best practices for security including SANS (SysAdmin, Audit, Network, Security) Institute, NIST (National Institute of Standards and Technology), and CIS (Center for Internet Security). Policies are reviewed annually by Neustarʹs information security team.

The following is a summary of the security policies that will be used in the ʺ.AUTOʺ registry, including:

1. Summary of the security policies used in the registry operations

2. Description of independent security assessments

3. Description of security features that are appropriate for ʺ.AUTOʺ

4. List of commitments made to registrants regarding security levels

All of the security policies and levels described in this section are appropriate for the ʺ.AUTOʺ registry.

30.(a).2 Summary of Security Policies

Neustar has developed a comprehensive Information Security Program in order to create effective administrative, technical, and physical safeguards for the protection of its information assets, and to comply with Neustarʹs obligations under applicable law, regulations, and contracts. This Program establishes Neustarʹs policies for accessing, collecting, storing, using, transmitting, and protecting electronic, paper, and other records containing sensitive information.

-The policies for internal users and our clients to ensure the safe, organized and fair use of information resources.

-The rights that can be expected with that use.

-The standards that must be met to effectively comply with policy.

-The responsibilities of the owners, maintainers, and users of Neustarʹs information resources.

-Rules and principles used at Neustar to approach information security issues

The following policies are included in the Program:

1. Acceptable Use Policy

The Acceptable Use Policy provides the rules of behavior covering all Neustar Associates for using Neustar resources or accessing sensitive information.

2. Information Risk Management Policy

The Information Risk Management Policy describes the requirements for the on-going information security risk management program, including defining roles and responsibilities for conducting and evaluating risk assessments, assessments of technologies used to provide information security and monitoring procedures used to measure policy compliance.

3. Data Protection Policy

The Data Protection Policy provides the requirements for creating, storing, transmitting, disclosing, and disposing of sensitive information, including data classification and labeling requirements, the requirements for data retention. Encryption and related technologies such as digital certificates are also covered under this policy.

4. Third Party Policy

The Third Party Policy provides the requirements for handling service provider contracts, including specifically the vetting process, required contract reviews, and on-going monitoring of service providers for policy compliance.

5. Security Awareness and Training Policy

The Security Awareness and Training Policy provide the requirements for managing the on-going awareness and training program at Neustar. This includes awareness and training activities provided to all Neustar Associates.

6. Incident Response Policy

The Incident Response Policy provides the requirements for reacting to reports of potential security policy violations. This policy defines the necessary steps for identifying and reporting security incidents, remediation of problems, and conducting lessons learned post-mortem reviews in order to provide feedback on the effectiveness of this Program. Additionally, this policy contains the requirement for reporting data security breaches to the appropriate authorities and to the public, as required by law, contractual requirements, or regulatory bodies.

7. Physical and Environmental Controls Policy

The Physical and Environment Controls Policy provides the requirements for securely storing sensitive information and the supporting information technology equipment and infrastructure. This policy includes details on the storage of paper records as well as access to computer systems and equipment locations by authorized personnel and visitors.

8. Privacy Policy

Neustar supports the right to privacy, including the rights of individuals to control the dissemination and use of personal data that describes them, their personal choices, or life experiences. Neustar supports domestic and international laws and regulations that seek to protect the privacy rights of such individuals.

9. Identity and Access Management Policy

The Identity and Access Management Policy covers user accounts (login ID naming convention, assignment, authoritative source) as well as ID lifecycle (request, approval, creation, use, suspension, deletion, review), including provisions for system⁄application accounts, shared⁄group accounts, guest⁄public accounts, temporary⁄emergency accounts, administrative access, and remote access. This policy also includes the user password policy requirements.

10. Network Security Policy

The Network Security Policy covers aspects of Neustar network infrastructure and the technical controls in place to prevent and detect security policy violations.

11. Platform Security Policy

The Platform Security Policy covers the requirements for configuration management of servers, shared systems, applications, databases, middle-ware, and desktops and laptops owned or operated by Neustar Associates.

12. Mobile Device Security Policy

The Mobile Device Policy covers the requirements specific to mobile devices with information storage or processing capabilities. This policy includes laptop standards, as well as requirements for PDAs, mobile phones, digital cameras and music players, and any other removable device capable of transmitting, processing or storing information.

13. Vulnerability and Threat Management Policy

The Vulnerability and Threat Management Policy provides the requirements for patch management, vulnerability scanning, penetration testing, threat management (modeling and monitoring) and the appropriate ties to the Risk Management Policy.

14. Monitoring and Audit Policy

The Monitoring and Audit Policy covers the details regarding which types of computer events to record, how to maintain the logs, and the roles and responsibilities for how to review, monitor, and respond to log information. This policy also includes the requirements for backup, archival, reporting, forensics use, and retention of audit logs.

15. Project and System Development and Maintenance Policy

The System Development and Maintenance Policy covers the minimum security requirements for all software, application, and system development performed by or on behalf of Neustar and the minimum security requirements for maintaining information systems.

30.(a).3 Independent Assessment Reports

Neustar IT Operations is subject to yearly Sarbanes-Oxley (SOX), Statement on Auditing Standards #70 (SAS70) and ISO audits. Testing of controls implemented by Neustar management in the areas of access to programs and data, change management and IT Operations are subject to testing by both internal and external SOX and SAS70 audit groups. Audit Findings are communicated to process owners, Quality Management Group and Executive Management. Actions are taken to make process adjustments where required and remediation of issues is monitored by internal audit and QM groups.

External Penetration Test is conducted by a third party on a yearly basis. As authorized by Neustar, the third party performs an external Penetration Test to review potential security weaknesses of network devices and hosts and demonstrate the impact to the environment. The assessment is conducted remotely from the Internet with testing divided into four phases:

-A network survey is performed in order to gain a better knowledge of the network that was being tested

-Vulnerability scanning is initiated with all the hosts that are discovered in the previous phase

-Identification of key systems for further exploitation is conducted

-Exploitation of the identified systems is attempted.

Each phase of the audit is supported by detailed documentation of audit procedures and results. Identified vulnerabilities are classified as high, medium and low risk to facilitate managementʹs prioritization of remediation efforts. Tactical and strategic recommendations are provided to management supported by reference to industry best practices.

30.(a).4 Augmented Security Levels and Capabilities

There are no increased security levels specific for ʺ.AUTOʺ. However, Neustar will provide the same high level of security provided across all of the registries it manages.

A key to Neustarʹs Operational success is Neustarʹs highly structured operations practices. The standards and governance of these processes:

-Include annual independent review of information security practices

-Include annual external penetration tests by a third party

-Conform to the ISO 9001 standard (Part of Neustarʹs ISO-based Quality Management System)

-Are aligned to Information Technology Infrastructure Library (ITIL) and CoBIT best practices

-Are aligned with all aspects of ISO IEC 17799

-Are in compliance with Sarbanes-Oxley (SOX) requirements (audited annually)

-Are focused on continuous process improvement (metrics driven with product scorecards reviewed monthly).

A summary view to Neustarʹs security policy in alignment with ISO 17799 can be found in section 30.(a).5 below.

30.(a).5 Commitments and Security Levels

The ʺ.AUTOʺ registry commits to high security levels that are consistent with the needs of the TLD. These commitments include:

Compliance with High Security Standards

-Security procedures and practices that are in alignment with ISO 17799

-Annual SOC 2 Audits on all critical registry systems

-Annual 3rd Party Penetration Tests

-Annual Sarbanes Oxley Audits

Highly Developed and Document Security Policies

-Compliance with all provisions described in section 30.(b) and in the attached security policy document.

-Resources necessary for providing information security

-Fully documented security policies

-Annual security training for all operations personnel

High Levels of Registry Security

-Multiple redundant data centers

-High Availability Design

-Architecture that includes multiple layers of security

-Diversified firewall and networking hardware vendors

-Multi-factor authentication for accessing registry systems

-Physical security access controls

-A 24x7 manned Network Operations Center that monitors all systems and applications

-A 24x7 manned Security Operations Center that monitors and mitigates DDoS attacks

-DDoS mitigation using traffic scrubbing technologies

Welcome,

Account Manager Log Out

Information

Home

About

Contact

Legal

Payment Methods

Site Map

Log In

Log Out
Ecommerce Solutions

SearchFit eCommerce Platforms

Power Search
Search Engine Marketing

Traffic Master

LinkFit

Pay Per Click

Search Engine Optimization
Domains & Hosting

Generic Domains (gTLD Domains)

Country Domains (ccTLD Domains)

New Generic Domains (New gTLD)

Prices

Hosting

Tools & Security
Design Studio

Website Design

Single Page Design

Banner Ad Design

Logo Design

Business Card Design

Identity Package

Brochure Design

Flyer Design

Christopher Michael Parrott	Director of Finance
Paul Eugene Spurgeon	COO
Scott Adam Shachtman	Director of Legal & Policy
Shaul Jolles	CEO

Application number: 1-879-42119 for Dot Auto LLC

Generated on 11 06 2012

Applicant Information

1. Full legal name

2. Address of the principal place of business

3. Phone number

4. Fax number

5. If applicable, website or URL

Primary Contact

6(a). Name

6(b). Title

6(c). Address

6(d). Phone Number

6(e). Fax Number

6(f). Email Address

Secondary Contact

7(a). Name

7(b). Title

7(c). Address

7(d). Phone Number

7(e). Fax Number

7(f). Email Address

Proof of Legal Establishment

8(a). Legal form of the Applicant

8(b). State the specific national or other jursidiction that defines the type of entity identified in 8(a).

8(c). Attach evidence of the applicant's establishment.

9(a). If applying company is publicly traded, provide the exchange and symbol.

9(b). If the applying entity is a subsidiary, provide the parent company.

9(c). If the applying entity is a joint venture, list all joint venture partners.

Applicant Background

11(a). Name(s) and position(s) of all directors

11(b). Name(s) and position(s) of all officers and partners

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility

Applied-for gTLD string

13. Provide the applied-for gTLD string. If an IDN, provide the U-label.

14(a). If an IDN, provide the A-label (beginning with "xn--").

14(b). If an IDN, provide the meaning or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.

14(c). If an IDN, provide the language of the label (in English).

14(c). If an IDN, provide the language of the label (as referenced by ISO-639-1).

14(d). If an IDN, provide the script of the label (in English).

14(d). If an IDN, provide the script of the label (as referenced by ISO 15924).

14(e). If an IDN, list all code points contained in the U-label according to Unicode form.

15(a). If an IDN, Attach IDN Tables for the proposed registry.

15(b). Describe the process used for development of the IDN tables submitted, including consultations and sources used.

15(c). List any variant strings to the applied-for gTLD string according to the relevant IDN tables.

16. Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.

17. (OPTIONAL) Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

Mission/Purpose

18(a). Describe the mission/purpose of your proposed gTLD.

18(b). How proposed gTLD will benefit registrants, Internet users, and others

18(c). Describe operating rules to eliminate or minimize social costs or financial resource costs, various types of consumer vulnerabilities.

Community-based Designation

19. Is the application for a community-based TLD?

20(a). Provide the name and full description of the community that the applicant is committing to serve.

20(b). Explain the applicant's relationship to the community identified in 20(a).

20(c). Provide a description of the community-based purpose of the applied-for gTLD.

20(d). Explain the relationship between the applied-for gTLD string and the community identified in 20(a).

20(e). Provide a description of the applicant's intended registration policies in support of the community-based purpose of the applied-for gTLD.

20(f). Attach any written endorsements from institutions/groups representative of the community identified in 20(a).

Geographic Names

21(a). Is the application for a geographic name?

Protection of Geographic Names

22. Describe proposed measures for protection of geographic names at the second and other levels in the applied-for gTLD.

Registry Services

23. Provide name and full description of all the Registry Services to be provided.

Demonstration of Technical & Operational Capability

24. Shared Registration System (SRS) Performance

25. Extensible Provisioning Protocol (EPP)

26. Whois

27. Registration Life Cycle

28. Abuse Prevention and Mitigation

29. Rights Protection Mechanisms

30(a). Security Policy: Summary of the security policy for the proposed registry

© 2012 Internet Corporation For Assigned Names and Numbers.

Manage Your Account

Internet & Marketing Solutions

Domain Registration

ccTLD International Domains

New gTLD Public Domains