Back

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

gTLDFull Legal NameE-mail suffixDetail
.NGOPublic Interest Registrypir.orgView
PIR’s goal is to provide the NGO Community an exclusive and immediately recognized home on the Internet. To achieve this goal and ensure that .NGO domain names are allocated in a manner that serves the NGO Community, PIR has developed a set of .NGO registration restriction policies and corresponding compliance and enforcement mechanisms.

The policies are built to match the need of the NGO Community based on feedback from NGO Community members; based on experience from the .ORG gTLD management since 2003; and generally established to ensure a higher security level for .NGO domain names than what currently is considered standard global requirements for gTLDs today.

.NGO Registration Policies
The registration policies in support of the NGO Community goals are described in the following summary and are detailed later in this section.
• Registrant Eligibility Requirements – all registrants must demonstrate affiliation through NGO membership organizations or through evidence of NGO status. PIR will work with membership organization, the NGO Community Advisory Council, and other members of the NGO Community to validate their eligibility.
• Name Selection Policy – ensures that only NGO Community relevant domain names are registered.
• Reserved Name Policy – names⁄types of domain names will initially be reserved from registration under .NGO.
• Registry Name Policy – names⁄types of domain names will be held from general availability, these will be used in support of the registry.
• Content and Use Restriction Policy – ensures that usage of the .NGO domain name corresponds with NGO Community activities.
• Compliance Functions – ensures ongoing compliance of the Registrant Eligibility Requirements, and the Content and Use Restriction Policy listed below.

The following policies support of the NGO Community goals and are detailed in subsequent Evaluation Questions of the application dedicated to such policies, as noted below.
• Abuse Prevention and Mitigation – includes the Anti-Abuse Policy which addresses the identification and prompt action taken on malicious use of domain names, and the Restriction Dispute Resolution Policy (RDRP) which ensures that disputes concerning any of the .NGO Registration Policies can be solved in an appropriate manner. Detailed descriptions of both policies can be found in response to Evaluation Question #28.
• Rights Protection Mechanisms – protects intellectual property holders under the Trademark Clearinghouse, Uniform Dispute Resolution Policy (UDRP), Uniform Rapid Suspension (URS), Registry Restrictions Dispute Resolution Procedures (RRDRP),Post-Delegation Dispute Resolution Policy (PDDRP), in addition to the Sunrise services and policies that can be found in response to Evaluation Question #29.

PIR will review all policies and processes on an annual basis with involvement from the PIR’s NGO Community Advisory Council and present the results to the NGO Community, allowing them to provide feedback.

Specific Policy Details

Registrant Eligibility Requirements: The .NGO domain registrations are open to NGO Community members. All registrants must demonstrate affiliation through NGO membership organizations or through evidence of NGO status. PIR will work with NGO membership organizations, the NGO Community Advisory Council, and other members of the NGO Community to validate their eligibility.

In consultation with PIR’s NGO Community Advisory Council PIR is reviewing potential NGO membership organizations who can verify the NGO status of registrants. NGO membership organizations include the following, and will expand over time:
• Global organizations: International associations and⁄or classification-based associations.
• Regional organizations: Associations across broad geographic areas, potentially including multiple countries or jurisdictions.
• Local organizations: Associations or groups that provide support and memberships at a country or local level.

During the registration process, the registrant will be asked to verify their eligibility and to demonstrate affiliation with a NGO member organization. Once the initial certification in step 1 of the verification process is confirmed, the domain is successfully created. If the .NGO registrant fails to provide any additional required information through step 2 of the verification process, the domain will be deleted and released back into the pool of available domains.

Content and Use Restriction Policy: Abusive use of the .NGO domain names will not be tolerated by PIR. The following use and content limitations apply:
• Overall the NGO domain name must be for a bona fide NGO use, as defined in the Restrictions Dispute Resolution in response to Evaluation Question #28.
• Websites must be developed with the intent to promote the corresponding .NGO registrant’s existing mission and activities, and not solely for commercialized or for-profit marketing usage.
• Use of the registered domain name to engage in activities inconsistent with the mission of a NGO is not allowed.
• Any illegal or fraudulent usage of the .NGO domain name is not allowed, including but not limited to phishing and pharming attacks, distribution of malware, and distribution of adult content.
• Registration and use of a domain name in violation of Rights Protection Mechanisms is not allowed.

Violations of any of the .NGO Registration Policies may be grounds for loss of registration, pursuant to the enforcement mechanism discussed below (with an appeal procedure).

Compliance Functions: While disputes will be managed directly by resolution providers, PIR will conduct random compliance audits across all the .NGO Registration Policies. Periodically PIRʹs compliance staff will audit a sample of .NGO registrations to verify claims to membership in a listed organization, name policy adherence, and compliance with the name and use policy.

If a registrant is found to not be in compliance the registrant will be notified that the domain will be placed on registry lock and that if the compliance issue is not cured the domain will be terminated.

As part of the compliance function PIR will also utilize its existing expertise, obtained through its management of .ORG, to monitor and take action on any abusive behavior taken place with .NGO domain names.

Name Selection Policy: The .NGO registrant must fulfill certain name policy criteria. PIR will employ the following restrictions concerning the names that eligible .NGO registrants can register. As such a .NGO registrant cannot register any name they wish but is limited by the following restrictions. A .NGO registered domain name may be:
1) the name of (entire or portion of) the NGO, e.g. its “doing business as” name,
2) an acronym representing the NGO,
3) a name that recognizes or generally describes the NGO, or
4) a name related to the mission or activities of the NGO.

Reserved Name Policy: The following names⁄types of domain names will initially be reserved from registration:
• All single- and two-character second-level domain names;
• Domains of an inappropriate nature, e.g., adult-related terminology, pursuant to a list defined by PIR and its NGO Community Advisory Council;
• Names provided by ICANN as required reserved names;
• A list of generic names defined by PIR and its NGO Community Advisory Council based on the overall criteria that the names represent the NGO Community in a general manner. Such names will be released in a specific RFP process ensuring that the names will benefit the NGO Community.

Registry Name Policy: The following names⁄types of domain names will be held from general availability; they will be used in support of the registry.
• Names to support registry operations, e.g., directory.ngo;
• Names to support PIR’s NGO Community Advisory Council.

Compliance and Enforcement Mechanisms
PIR will take both proactive and reactive measures to enforce the policies of the gTLD. Proactive measures are taken at the time of registration by requiring .NGO registrants to meet the .NGO Registration Policies and to agree to all policies and procedures of the gTLD. Reactive measures are addressed via our audit process and through our defined dispute resolution processes.

A violation of the .NGO Registration Policies will be enforced on a case-by-case, fact specific basis under the processes set forth below:
1. Any allegation that a domain name is not used primarily for NGO purposes shall be enforced under the provisions of the Restrictions Dispute Resolution Policy (ʺRDRPʺ) as described in Evaluation Question #28. The RDRP will be included as an appendix to the Registry Agreement. An appeal procedure is included in the RDRP.
2. Any alleged violation of the Rights Protection Mechanisms shall be enforced under the provisions contained in each of them.

Disputes resulting from violations of the .NGO Registration Policies will be resolved through the Compliance Functions and the Rights Protection Mechanisms. The Rights Protection Mechanisms (as detailed in Evaluation Question #29) will be made applicable by the ICANN-Accredited Registrarsʹ registration agreements with registrants. Proceedings under the Rights Protection Mechanisms will be conducted in accordance with the policies and procedures that will be included in an appendix to the Registry Agreement. As set forth in the Compliance Functions, the registry operator will review on a random basis, monitor, and verify that any particular domain name is being used primarily for NGO purposes and that a domain is being used in compliance with the Rights Protection Mechanisms processes.

Resource Plans
PIR will devote 2 compliance officers to handle compliance and disputes as they arise, although currently for .ORG this need is rare. Most compliance checks on registration eligibility are expected to be handled in an automated process.
gTLDFull Legal NameE-mail suffixDetail
.MUSICDotMusic ⁄ CGR E-Commerce Ltdmusic.usView
DotMusic has incorporated enhanced policies to ensure only eligible members of the Music Community who comply with the values, purpose and mission of the TLD can participate; to ensure domains are used in a manner benefitting the Community; to protect intellectual property; and to safeguard domains from malicious conduct and copyright infringement.
The policies are built to match Music Community needs, based on years of feedback from Music Community members and on experience from the previous ICANN new gTLD introductions, as well as established to ensure a higher level of security for .MUSIC than what is considered standard for gTLDs.
Aside from the policies described below .MUSIC will be launched with standard gTLD lifecycle requirements per response to question #27. DotMusic will adhere to all ICANN mandated rights protection mechanisms and consensus policies.

RESERVATION PROTECTION:
DotMusic will reserve names at the second level per ICANN requirements. The Country and Territory Names are reserved per the response to question #22. Names to support registry operations, e.g. nic.MUSIC can only be registered by DotMusic.

INNOVATIVE PREMIUM NAMES RESERVATIONS:
DotMusic will reserve premium names that will be used in an innovative manner to benefit eligible members including the development of Premium Channels, such as genres (e.g Rock.MUSIC), that will define the locale web of music, promote Community members based on their classification⁄cateogry, and improve music discovery.

RIGHTS PROTECTION AND NOTIFICATIONS SYSTEM:
- Globally Protected Marks List (GPML) will ensure major music brands and established artists, such as RIAA-certified platinum-selling bands, are protected not cybersquatted. These are reserved at all times.
- Trademark Clearing House and its notification mechanisms will be implemented in accordance to ICANN specifications.
- Names Selection Policy – to ensure only music-related names are registered as domains under .MUSIC, with the following restrictions:
1) A name of (entire or portion of) the musician, band, company, organization, e.g. the registrants “doing business as” name
2) An acronym representing the registrant
3) A name that recognizes or generally describes the registrant, or
4) A name related to the mission or activities of the registrant

SUNRISE LAUNCH W⁄ TRADEMARK VALIDATION
This is the first phase of .MUSIC domain registration. It is a phase designed to protect trademarks in the roll-out of .MUSIC. The Sunrise is the time when regional, national and international trademark and service mark holders can apply for .MUSIC domains.
The eligibility requirements will be verified, and multiple registration applications for the same string will be auctioned, except for GPML entries that supersede any other sunrise registration applications.
The Sunrise Challenge Process solves disputes concerning domains registered under the Sunrise Policy.
Details of the Sunrise Policy and Challenge Process can be found in response to question #29.

MUSIC COMMUNITY MEMBER ORGANIZATION (MCMO) LANDRUSH LAUNCH
This is the second phase of.MUSIC domain registration. It is a limited-time period reserved for members of DotMusic-accredited music Community Member Organizations (mCMO). Unique registrations will be granted to the sole registrant and delegated at the close of the time period; multiple registration requests for the same string will go through an auction.

LANDRUSH LAUNCH
This is the third phase of .MUSIC domain registration; a limited- time period. Unique registrations will be granted to the registrant; multiple registration requests for the same domain will go through an auction.
Landrush is designed for members of the Music Community that want to secure premium .MUSIC domains giving members the chance to register their preferred .MUSIC domains; multiple registration requests for the same domain will go through an auction.

GENERAL AVAILABILITY
This is the fourth and final phase of registration of .MUSIC domains. .MUSIC registrations will now be available to Music Community members on a first come, first served basis.

USE POLICY
This policy is in place for .MUSIC registrants regardless of the applicable launch phase. It is developed with extensive participation of Music Community members; tailored to meet the specific needs of the Music Community; and solve issues currently existing in the Music Community related to intellectual property infringement and malicious conduct.

The policy is incorporated in the registration agreement for all .MUSIC registrants. DotMusic may modify or revise these use policies at any time. Registrants agree to be bound by such modifications or revisions. Registrants that do not accept and abide by the registration agreement are disqualified from domain registrations.

The following use requirements apply:
• Use only for music-related activities
• Comply with applicable laws and regulations and not participate in, facilitate, or further illegal activities
• Do not post or submit content that is illegal, threatening, abusive, harassing, defamatory, libelous, deceptive, fraudulent, invasive of anotherʹs privacy, or tortious
• Respect the intellectual property rights of others by posting or submitting only content that is owned, licensed, or otherwise have the right to post or submit
• Immediately notify us if there is a security breach, other member incompliance or illegal activity on .MUSIC sites
• Do not register a domain containing an established music brand’s name in bad faith that might be deemed confusing to Internet users and the Music Community
• Do not use any automated process to access or use the .MUSIC sites or any process, whether automated or manual, to capture data or content from any service for any reason
• Do not use any service or any process to damage, disable, impair, or otherwise attack .MUSIC sites or the networks connected to .MUSIC sites

ANTI-ABUSE POLICY
This policy is in place for all registrants under .MUSIC and addresses the identification and prompt action on malicious abuse of domains. Such activity can lead to security and stability issues for the registry, registrars, and registrants, and general users of the Internet which the policy is in place to prevent. The policy is incorporated in the .MUSIC registration agreement with all registrants and detailed in response to question #28.

REGISTRY DATA VALIDATION
While DotMusic will hold the thick WHOIS data provided through registrars, we will also validate elements of the received WHOIS data:
1. The registrant’s email address through validation links
2. The registrant’s phone number through validated PIN-codes
Upon successful completion of these two steps, DotMusic will provide the registrant their Music Community membership details; used to join⁄access the Premium Channels. All future .MUSIC domains associated with the registrant-verified email address will not be re-verified.
COMPLIANCE AND ENFORCEMENT
DotMusic will take proactive and reactive measures to enforce its TLD policies. Proactive measures are taken at the time of registration. Reactive measures are addressed via compliance and enforcement mechanisms and through dispute processes.
Any violation of the .MUSIC Policies will be enforced on a case-by-case, fact-specific basis:
1. Any allegation that a domain is not used for legitimate music purposes or otherwise infringes on the .MUSIC Policies shall be enforced under the provisions of the .MUSIC Policy & Copyright Infringement Dispute Resolution Process (ʺMPCIDRPʺ) as described in our response to question #28.
2. Any alleged violation of the UDRP shall be enforced under the provisions contained therein, as modified by the URS.

The MPCIDRP, UDRP, and URS are required in the registrarsʹ registration agreements with registrants. Proceedings under the MPCIDRP, UDRP, and URS must be brought by interested third parties in accordance with the associated policies and procedures.
DotMusic will conduct random compliance efforts across all the .MUSIC Policies. Periodically a sample of .MUSIC registrations will be verified for compliance with all established .MUSIC Policies.
If a Registrant is found out of compliance with any of the .MUSIC Policies the registrant will be notified that the domain will be placed on registry lock. The registrant will have a reasonable time period to fix the compliance matter or the domain will be terminated.
Repeat offenders will be placed on a special monitoring list that DotMusic staff will conduct additional compliance checks against. DotMusic holds the right to prohibit repeat offenders from registering .MUSIC domains for a period of time or indefinitely.
DotMusic will review all policies and processes on a regular basis with involvement from the .MUSIC Advisory Committee and will present them publicly to enable Music Community constituents to provide feedback. DotMusic will also conduct registrar and registrant surveys based on the level of registrant satisfaction concerning .MUSIC usability and how to improve value proposition.
DotMusic reserves the right to deny, cancel or transfer any registration that it deems necessary, in its discretion, to protect the integrity and stability of the registry, to comply with any applicable laws, government rules or requirements, requests of law enforcement, in compliance with any dispute resolution process, or to avoid any liability, civil or criminal, on the part of DotMusic, as well as its affiliates, subsidiaries, officers, directors and employees. DotMusic reserves the right to freeze a domain during resolution of a dispute. DotMusic reserves the right to terminate a domain for failure by the registrant to demonstrate it meets .MUSIC policies.