Jump to content

.music

From Wikipedia, the free encyclopedia
.music
TLDtypeCommunity
StatusICANN Registry Agreement for.music was signed on May 4, 2021
Intended usemusic
Registry websitemusic.us

.musicis a community-basedtop-level domain name(TLD) operated for the benefit of the global music community. It was one of the most highly contestednew gTLDs,with eight applicants in contention.

On April 17, 2019, the.MUSIC registry, theInternational Federation of the Phonographic Industry,Confédération Internationale des Sociétés d'Auteurs et Compositeurs,theInternational Federation of Musicians,the International Federation of Arts Councils and Culture Agencies, theRecording Industry Association of America,theNational Music Publishers' Association,The Recording Academy,theIndependent Music Companies Association,the Worldwide Independent Network, theAmerican Association of Independent Music,the NSAI, theNational Association of Music Merchants(NAMM), and the Independent Music Publishers International Forum (IMPF) announced that the global music community based application, that was supported by a global music coalition with members representing over 95% of global music consumed, was approved by theInternet Corporation for Assigned Names and Numbers(ICANN).[1]The.MUSIC registry agreement was signed on May 4, 2021.[2]

Applicants

[edit]
  1. .MUSIC[3]
  2. Google(Charleston Road Registry Inc.)
  3. Amazon
  4. Donuts (Victor Cross)
  5. Far Further
  6. Top Level Domain Holdings Ltd. (TLDH) and LHL TLD Investment Partners
  7. Radix
  8. Famous Four MediaGRS Domains

.MUSIC

[edit]

A community priority application was applied for by.MUSIC under the legal name of DotMusic.[4]MUSIC was headed byConstantine Roussos,who launched the.MUSIC Initiative in 2005 to gather support from the global music community for a petition to ICANN for the rights of.MUSIC. Associated organizations included the International Federation of Arts Councils and Culture Agencies (IFACCA), theAmerican Association of Independent Music(A2IM), and the National Association of Music Manufacturers (NAMM).[5]The initiative's objectives included:[6][7]

  • Music education
  • Fighting piracy
  • Promoting the arts and global music
  • Innovation in music and the internet space
  • Promoting competition

The team planned to operate the.music TLD using a multi-stakeholder approach. A portion of the revenue generated from registrations was marked for donation to selected non-profit music organizations. These registrations would be restricted to.MUSIC-accredited Community Member Organizations (MCMOs).[8]CentralNicwas selected as the back-end registry services provider.[9]

Far Further

[edit]

Far Further was founded by music professionals[10]with the objective of uniting the globalmusic industryby providing it with a secure domain space[11]to promote music, protect intellectual property rights and help advance music education. They submitted a community priority application using.music LLC, a subsidiary of Far Further LLC.

The company choseNeustarto provide back-end registry services. The domain was to be restricted to registrants qualified via association with a number of supporting organizations.[12][13]

TLDH and LHL

[edit]

On March 23, 2012, Top Level Domain Holdings Ltd. and LHL TLD Investment Partners signed a partnership agreement to apply for the.music TLD. Minds + Machines was to provide the back-end registry services.[14]

Amazon

[edit]

Amazon's application was issued aGACEarly Warning[15]from representative of Australia and GAC Chair Heather Dryden. It stated that the applicant was "seeking exclusive access to a common generic string [..] that relates to a broad market sector," which Dryden noted could have unintended consequences and a negative impact on competition.[16]

Radix

[edit]

Radix received a GAC Early Warning from the U.S. Government. The issue did not relate to their technical capabilities or the content of their applications, but rather the inclusion of an email address associated with the U.S. Federal Bureau of Investigation in a recommendation filed with Radix's application.[17]

Objections

[edit]

A Legal Rights Objection, as defined by the ICANN approved mediatorWIPO,is a third party "formal objection to an application on several grounds [..] When such an objection is filed, an independent panel (comprised of one or three experts) will determine whether the applicant’s potential use of the applied-for gTLD would be likely to infringe [..] the objector’s existing trademark, or IGO name or acronym."[18]

Official objection

[edit]

An official objection was filed by DotMusic Limited against.music applicants since DotMusic Limited had registered trademarks for ".music" and "dotmusic" in nearly thirty countries.[19]

Community objections

[edit]

The American Association of Independent Music (AAIM) and DotMusic filed community objections against Google, dot Music Limited, Dotmusic Inc., Top Level Domain Holdings Ltd., and Donuts on the basis that they applied as open registries without enhanced safeguards or sufficient eligibility restrictions to protect music-related intellectual property and prevent music piracy. The AAIM also filed a community objection against Amazon because of its application's exclusive-access registry policies and discriminatory registration eligibility criteria that restricted registrations solely to Amazon and its affiliates. For the same reason, the International Federation of Arts Councils and Culture Agencies and DotMusic filed a community objection against Far Further.[20]

The objections against Amazon and Far Further were based on the ICANN Registry Agreement which required that new gTLD registries be subject to the requirements of Specification 11, which mandates that a TLD Registry must provide non-discriminatory access to registry services to all ICANN accredited registrars that enter into and are in compliance with the registry-registrar agreement for the TLD.[21]In February 2014 ICANN passed resolutions for the new gTLD program which mandated specific enhanced safeguards[22]and prohibited applicants from operating a new gTLD as an exclusive-access registry for a TLD based on a generic term.[23]

References

[edit]
  1. ^"Global music community prevails in winning the rights to the.MUSIC domain extension".Archived fromthe originalon 2020-10-24.Retrieved2021-03-25.
  2. ^".music Registry Agreement".Retrieved2021-09-20.
  3. ^"What is the.MUSIC Domain?"..MUSIC(DotMusic).Archived fromthe originalon 2021-03-04.Retrieved24 June2021.The.MUSIC Initiative by DotMusic is a truly global.MUSIC community-led effort and the only initiative with enhanced music tailored policies that ensure that music artists, bands, industry professionals and organizations register a trusted, secure and verified.MUSIC domain — a safe, authenticated domain identity similar to that of a domain ending in.EDU or.GOV — and own their exclusive www.name.music web address.
  4. ^"Roussos Group".Archived fromthe originalon June 14, 2013.RetrievedMarch 3,2019.
  5. ^Application 1-1115-14110
  6. ^ Constantine Roussos Linkedin Profile
  7. ^"music.us".Archived fromthe originalon 2013-06-14.Retrieved2013-06-14.
  8. ^"About Us".Archived fromthe originalon 2013-05-29.Retrieved2013-06-14.
  9. ^.MUSIC (DotMusic) Applies for Generic Top Level Domain (gTLD) with ICANN
  10. ^"About US".Archived fromthe originalon 2015-05-18.Retrieved2018-11-27.
  11. ^"Far Further Mission".Archived fromthe originalon 2015-09-24.Retrieved2018-11-27.
  12. ^RIAA backs.music new gTLD bid
  13. ^"About Far Further".Archived fromthe originalon 2015-05-10.Retrieved2018-11-27.
  14. ^TLDH to apply for.music
  15. ^GAC Early Warning, NewgTLDS.ICANN.orgRetrieved 25 Nov 2012
  16. ^"Music AU, GACweb.ICANN.org"(PDF).Archived fromthe original(PDF)on 2013-01-21.Retrieved2018-11-27.
  17. ^RadixReg. GACweb.ICANN.orgArchived2013-01-21 at theWayback MachineRetrieved 27 Nov 2012
  18. ^LRO, WIPO.intRetrieved 25 March 2013
  19. ^LRO Cases, WIPO.int
  20. ^List of Pending Cases, ICCWBO.orgRetrieved 14 May 2013
  21. ^New gTLD Agreement, Section 2.9, ICANN.org
  22. ^ICANN Resolutions, ICANN.org
  23. ^ICANN Resolutions, ICANN.org