Changes

Jump to navigation Jump to search
no edit summary
Line 21: Line 21:  
<div style="clear:both;"></div>
 
<div style="clear:both;"></div>
 
<div style="width:49.5%;float:left;">
 
<div style="width:49.5%;float:left;">
<div style="background:#61A376; font-family:sans-serif;font-size:100%;font-weight:bold;text-align:left;color:#F2EFEA;height: 1.5em;margin:.2em 0 .1em 0; padding:.5em .25em .5em .75em;border-radius:5px;">Featured Article, January 26, 2022</div>
+
<div style="background:#61A376; font-family:sans-serif;font-size:100%;font-weight:bold;text-align:left;color:#F2EFEA;height: 1.5em;margin:.2em 0 .1em 0; padding:.5em .25em .5em .75em;border-radius:5px;">Featured Article, January 27, 2022</div>
 
<div style="padding:.5em 0 0 0;width:95.5%;">   
 
<div style="padding:.5em 0 0 0;width:95.5%;">   
[[File: Dot Horse Logo.png|150px|right]]'''[[.horse]]''' is a delegated [[Community gTLD]] from ICANN's 2012 [[New gTLD Program]] for the horse industry. The proposed application succeeded and was delegated to the Root Zone on March 31, 2014. The intended use of .horse is for equine industry professionals, including trainers, instructors, breeders, facility managers, bloggers, and horse enthusiasts.
+
A '''[[Registry]]''' is the database of all domain names registered under a certain [[TLD]]. A '''Registry Operator''', also known as a '''Network Information Center (NIC)''', refers to person(s) or entity(ies) responsible for providing registry services. These services include customer database administration, zone file publication, [[DNS]] and [[DNSSEC]] operation, marketing and policy determination. A Registry may outsource some, all, or none of these services. Different registries exist for different [[TLD]]s.
 +
 
 +
See our list of [[:Category:Registries|registry companies]]
 
</div>
 
</div>
 
</div>
 
</div>
Line 31: Line 33:  
* On January 18, [[Karen Lentz]] posted a [https://www.icann.org/en/blogs/details/icann-subsequent-procedures-odp-introducing-the-work-tracks-18-1-2022-en blog] updating the community on the [[SUBPRO]] Operation Design Phase and identifying nine work tracks for the ODP.
 
* On January 18, [[Karen Lentz]] posted a [https://www.icann.org/en/blogs/details/icann-subsequent-procedures-odp-introducing-the-work-tracks-18-1-2022-en blog] updating the community on the [[SUBPRO]] Operation Design Phase and identifying nine work tracks for the ODP.
 
* On January 19, [[ICANN]] appointed [[John Crain]] [https://www.icann.org/en/announcements/details/john-crain-appointed-icann-senior-vice-president-and-chief-technology-officer-19-1-2022-en Senior Vice President and Chief Technology Officer.]
 
* On January 19, [[ICANN]] appointed [[John Crain]] [https://www.icann.org/en/announcements/details/john-crain-appointed-icann-senior-vice-president-and-chief-technology-officer-19-1-2022-en Senior Vice President and Chief Technology Officer.]
* [https://www.icann.org/en/announcements/details/icann-delivers-operational-design-assessment-of-ssad-recommendations-25-1-2022-en On January 25], [[ICANN Organization]] released the hotly anticipated [[ODP|ODA]] for the [[SSAD]] project, which the [[GNSO Council]] and [[ICANN Board]] will discuss on [https://icann.zoom.us/webinar/register/WN_XJ4k_qM0TfOdTsTkMbqOwQ January 27]. In essence, ICANN expects to spend $20 to 27 million and take three to four years to ''develop'' the SSAD and $14 to 107 million to ''run'' it.
+
* On January 25, [[Google]] Domains launched early access registrations for [[.day]].
 +
* [https://icann.zoom.us/webinar/register/WN_XJ4k_qM0TfOdTsTkMbqOwQ Today] the [[GNSO Council]] and [[ICANN Board]] will discuss the [[ODA]] for the [[SSAD]].  
 +
 
 
</div>
 
</div>
 
</div>
 
</div>
Bureaucrats, Check users, lookupuser, Administrators, translator
14,927

edits

Navigation menu