.hiphop: Difference between revisions

Line 67:

Despite the .hiphop domain originally being advertised as part of UNR's April auction, Dot Hip Hop LLC (DHH) separately negotiated the purchase of the TLD in an arms-length transaction.<ref name="annex">[https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-annex-1-14dec21-en.pdf Annex 1 to Dot Hip Hop LLC's Reconsideration Request 21-3], December 14, 2021</ref> UNR submitted the assignment request for .hiphop to ICANN in August 2021.<ref name="annex" /> The assignment was delayed for the same reasons as the other, auctioned TLDs.<ref name="annex" />

In December, DHH submitted a reconsideration request regarding ICANN's inaction on the assignment request for the .hiphop TLD.<ref name="record">[https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en Reconsideration Request 21-3: Dot Hip Hop, LLC], filed December 14, 2021</ref> In its request, DHH noted that it had spent considerable time explaining, and re-explaining, its position on the NFT associated with .hiphop, which was transferred as part of DHH's purchase agreement with UNR.<ref name="annex" />

In December, DHH submitted an urgent [[Reconsideration|reconsideration request]] regarding ICANN's inaction on the assignment request for the .hiphop TLD.<ref name="record">[https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en Reconsideration Request 21-3: Dot Hip Hop, LLC], filed December 14, 2021</ref> In its request, DHH noted that it had spent considerable time explaining, and re-explaining, its position on the NFT associated with .hiphop, which was transferred as part of DHH's purchase agreement with UNR.<ref name="annex" /> The Board Accountability Mechanisms Committee denied the request for urgent action, because only Board inaction could be subject to such a request.<ref>[https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf BAMC Determination re: Urgent Reconsideration], December 16, 2021</ref> ICANN posted a blog in January 2022 regarding the .hiphop situation and the Uniregistry assignments more broadly.<ref>[https://www.icann.org/en/blogs/details/relying-on-icann-community-developed-processes-for-a-safe-secure-internet-5-1-2022-en ICANN.org Blog - Relying on Community Developed Process for a Safe & Secure Internet]January 5, 2022</ref>

On January 13, DHH withdrew its reconsideration request, due in part to the additional delay that would be incurred if ICANN suspended consideration of the assignment request to evaluate the merits of the reconsideration request on the normal timeline for such proceedings.<ref name="DHHletter">[https://www.jjnsolutions.com/post/dot-hip-hop-withdraws-icann-reconsideration-request-and-corrects-the-record Jeff Neumann letter to ICANN], January 13, 2022</ref> The letter withdrawing the request again attempted to correct the record regarding DHH's expectation of "ownership" of the TLD and other concerns raised in ICANN's blog post.<ref name="DHHletter" />

==References==

@@ Line 67: / Line 67: @@
 Despite the .hiphop domain originally being advertised as part of UNR's April auction, Dot Hip Hop LLC (DHH) separately negotiated the purchase of the TLD in an arms-length transaction.<ref name="annex">[https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-annex-1-14dec21-en.pdf Annex 1 to Dot Hip Hop LLC's Reconsideration Request 21-3], December 14, 2021</ref> UNR submitted the assignment request for .hiphop to ICANN in August 2021.<ref name="annex" /> The assignment was delayed for the same reasons as the other, auctioned TLDs.<ref name="annex" />
-In December, DHH submitted a reconsideration request regarding ICANN's inaction on the assignment request for the .hiphop TLD.<ref name="record">[https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en Reconsideration Request 21-3: Dot Hip Hop, LLC], filed December 14, 2021</ref> In its request, DHH noted that it had spent considerable time explaining, and re-explaining, its position on the NFT associated with .hiphop, which was transferred as part of DHH's purchase agreement with UNR.<ref name="annex" />
+In December, DHH submitted an urgent [[Reconsideration|reconsideration request]] regarding ICANN's inaction on the assignment request for the .hiphop TLD.<ref name="record">[https://www.icann.org/resources/pages/reconsideration-21-3-dot-hip-hop-request-2021-12-16-en Reconsideration Request 21-3: Dot Hip Hop, LLC], filed December 14, 2021</ref> In its request, DHH noted that it had spent considerable time explaining, and re-explaining, its position on the NFT associated with .hiphop, which was transferred as part of DHH's purchase agreement with UNR.<ref name="annex" /> The Board Accountability Mechanisms Committee denied the request for urgent action, because only Board inaction could be subject to such a request.<ref>[https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf BAMC Determination re: Urgent Reconsideration], December 16, 2021</ref> ICANN posted a blog in January 2022 regarding the .hiphop situation and the Uniregistry assignments more broadly.<ref>[https://www.icann.org/en/blogs/details/relying-on-icann-community-developed-processes-for-a-safe-secure-internet-5-1-2022-en ICANN.org Blog - Relying on Community Developed Process for a Safe & Secure Internet]January 5, 2022</ref>
+On January 13, DHH withdrew its reconsideration request, due in part to the additional delay that would be incurred if ICANN suspended consideration of the assignment request to evaluate the merits of the reconsideration request on the normal timeline for such proceedings.<ref name="DHHletter">[https://www.jjnsolutions.com/post/dot-hip-hop-withdraws-icann-reconsideration-request-and-corrects-the-record Jeff Neumann letter to ICANN], January 13, 2022</ref> The letter withdrawing the request again attempted to correct the record regarding DHH's expectation of "ownership" of the TLD and other concerns raised in ICANN's blog post.<ref name="DHHletter" />
 ==References==