.rsvp: Difference between revisions
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Delegated | ||
|manager = | |manager = | ||
|country = | |country = | ||
| Line 16: | Line 16: | ||
}} | }} | ||
'''.rsvp''' is a | '''.rsvp''' is a [GTLD]] that was proposed in [[ICANN]]'s [[New gTLD Program]]. The successful applicant is [[Google]] ([[Charleston Road Registry Inc.]])<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> rsvp was delegated to the [[Root Zone]] of the [[DNS]] on the 30th August, 2014, completing the successful application for the string.<ref>[http://newgtlds.icann.org/en/program-status/delegated-strings ICANN delegated strings] Retrieved 5th December 2014.</ref> | ||
==Application Details== | ==Application Details== | ||
The following is excerpted from the applicant's response to question #18: | The following is excerpted from the applicant's response to question #18: | ||
| Line 29: | Line 30: | ||
Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/501 Application Download, gTLDresult.ICANN.org] Retrieved 28 Feb 2013</ref> | Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/501 Application Download, gTLDresult.ICANN.org] Retrieved 28 Feb 2013</ref> | ||
==Contract Signed== | |||
On the 8th May 2014, [[Google]] received a [[Registry Agreement]] signed by [[ICANN]] for .rsvp after passing the [[Initial Evaluation]].<ref>[http://www.icann.org/en/about/agreements/registries Registry Agreements, ICANN.org] Retrieved 05 December 2014</ref> | |||
==Delegation== | |||
.rsvp was delegated to the [[Root Zone]] of the [[DNS]] on the 30th August, 2014, completing the successful application for the string.<ref>[http://newgtlds.icann.org/en/program-status/delegated-strings ICANN delegated strings] Retrieved 5th December 2014.</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Latest revision as of 21:30, 5 December 2014
| Status: | Delegated |
| Registry Provider: | |
| Type: | Generic |
| Category: | Lifestyle |
| Priority #: | 1340 - Google (Charleston Road Registry Inc.) |
More information: 
| |
.rsvp is a [GTLD]] that was proposed in ICANN's New gTLD Program. The successful applicant is Google (Charleston Road Registry Inc.)[1] rsvp was delegated to the Root Zone of the DNS on the 30th August, 2014, completing the successful application for the string.[2]
Application Details
The following is excerpted from the applicant's response to question #18:
"The proposed gTLD will provide the marketplace with direct association to the term, ʺrsvp,ʺ which is an acronym of the French phrase ʺrépondez sʹil vous plaît,ʺ which translates to English as ʺplease reply.ʺ ʺRSVPʺ is commonly used as a verb to denote response to an invitation. The mission of the proposed gTLD, .rsvp, is to provide a dedicated domain space in which registrants can enact second-level domains that relate to physical or online events where a response is sought. This mission will enhance consumer choice by providing new availability in the second-level domain space, creating new layers of organization on the Internet, and signaling the kind of content available in the domain. Charleston Road Registry believes that registrants will find value in associating with this gTLD, as supported by the prevalence of events, birthdays, weddings, and other celebrations occurring around the world each day. Evite, one of the primary U.S. providers of online invitations, reports 219 million invitations are created by users annually, further substantiating the demand potential in the proposed gTLD [Source: http:⁄⁄new.evite.com⁄content⁄about_us].
..
Charleston Road Registry believes that given its wide variety of uses, the .rsvp gTLD will best add value to the gTLD space by remaining purely open and unencumbered by registrant restrictions. There will, therefore, be no restrictions on second-level domain name registrations in the proposed gTLD, .rsvp.
Charleston Road Registry will make access to Registry Services, including the shared registration system, available to all ICANN-accredited registrars. Domain names within the proposed gTLD will be available to the general public for registration and use.
Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."[3]
Contract Signed
On the 8th May 2014, Google received a Registry Agreement signed by ICANN for .rsvp after passing the Initial Evaluation.[4]
Delegation
.rsvp was delegated to the Root Zone of the DNS on the 30th August, 2014, completing the successful application for the string.[5]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ ICANN delegated strings Retrieved 5th December 2014.
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 28 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 05 December 2014
- ↑ ICANN delegated strings Retrieved 5th December 2014.