[council] Thick WHOIS Registration Data Directory Services Requirements to Take Effect

[Steve Chan]

Dear Councilors,

 

FYI, the Thick WHOIS registration data directory services requirements were published on 1 February 2017. Please see the announcement below.

 

Best,

Steve

 

 

From: ICANN News Alert <no-reply at external.icann.org>
Reply-To: "no-reply at external.icann.org" <no-reply at external.icann.org>
Date: Thursday, February 2, 2017 at 1:28 PM
To: Steve Chan <steve.chan at icann.org>
Subject: [Ext] ICANN News Alert -- Thick WHOIS Registration Data Directory Services Requirements to Take Effect

 

[icann.org] 
News Alert
https://www.icann.org/news/announcement-2-2017-02-01-en[icann.org]

Thick WHOIS Registration Data Directory Services Requirements to Take Effect
1 February 2017

LOS ANGELES – 1 February 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today announced that all ICANN gTLD contracted parties must update their registration data directory services to comply with the Thick Whois Transition Policy for .COM, .NET and .JOBS[icann.org] and Registry Registration Data Directory Services Consistent Labeling and Display Policy[icann.org].

The policies require all gTLD registrations to be Thick with a consistent labeling and display of WHOIS output. gTLD registry operators currently providing Thin WHOIS services – .COM, .NET and .JOBS – must submit all new domain name registrations as Thick WHOIS by 1 May 2018. These registries must also migrate all data required for Thick WHOIS services for existing domain names by 1 February 2019. These changes are required by the Thick Whois Transition Policy for .COM, .NET and .JOBS. In addition, registries and registrars are required to implement the data specifications defined in the Registry Registration Data Directory Services Consistent Labeling and Display Policy by 1 August 2017. ICANN has notified contracted parties of their new responsibilities.

Background:

ICANN's agreements[icann.org] with accredited registrars and with gTLD registry operators require compliance with various specifically stated procedures and "consensus policies." Consensus policies are developed through a bottom-up, multistakeholder policy development process in accordance with ICANN Bylaws. The ICANN Board adopted GNSO consensus policy recommendations[icann.org] regarding the use of Thick WHOIS by all gTLD registries on 7 February 2014. The recommendations state that, "The provision of Thick Whois services, with a consistent labeling and display as per the model outlined in specification 3 of the 2013 [Registrar Accreditation Agreement], should become a requirement for all gTLD registries, both existing and future."

Learn more:
GNSO Thick Whois Policy Development Process[gnso.icann.org] 
Policy Implementation at ICANN[icann.org] 
About ICANN
ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org[icann.org].

 

This message was sent to steve.chan at icann.org from:ICANN News Alert | no-reply at external.icann.org | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536Email Marketing by [icontact.com]
Manage Your Subscription [app.icontact.com] 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20170203/9c1004dc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2018 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/council/attachments/20170203/9c1004dc/smime.p7s>