View source for Registry Registration Data Directory Services Consistent Labeling and Display Policy

The '''Registry Registration Data Directory Services Consistent Labeling and Display Policy''' sought to align how registries and registrars label and display registration data. This [[Consensus Policy]] treated the output specifications from the 2013 [[Registrar Accreditation Agreement]] as the standard. The policy details can be found [https://www.icann.org/rdds-labeling-display here]. 

==History==
On February 7, 2014, the ICANN Board adopted the GNSO's recommendations regarding “thick” Whois for all gTLD registries. The [[IRT| Implementation Reviewam (IRT)]] identified two key outcomes, one of which was the consistent labeling and display of Whois output for all gTLDs.<ref>[https://www.icann.org/rdds-labeling-display RDDS Labeling & Display, ICANN Resources]</ref> 

On 3 December 2015, ICANN opened a [[Public Comment]] proceeding for the Proposed Implementation of Consistent Labeling and Display of RDDS Output for All gTLDs for public comment and published the policy for implementation on July 26, 2016. On August 9, 2016, the [[RySG|Registry Stakeholder Group]] submitted a Request for Reconsideration, objecting to the inclusion of Registration Data Access Protocol (RDAP).

On October 21, 2016, ICANN released the revised version of the Registry Registration Data Directory Services Consistent Labeling and Display Policy, which  removed the requirement of registries to implement the RDAP. The protocol would be mandated through contractual agreement rather than through consensus policy.<ref>[https://www.icann.org/public-comments/rdds-labeling-display-2016-10-21-en RDDS Labeling, Public Comment]</ref>

Then, on February 27, 2019, the ICANN org issued a notification to gTLD registries and registrars of the requirement to implement an RDAP service by August 26, 2019.<ref>[https://www.icann.org/resources/pages/rdap-faqs-2018-08-31-en RDAP FAQs]</ref>

==References==