ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

Thick Whois/RDAP Implementation Comment Submission by Web.com

  • To: "comments-rdds-output-03dec15@xxxxxxxxx" <comments-rdds-output-03dec15@xxxxxxxxx>, "comments-rdap-profile-03dec15@xxxxxxxxx" <comments-rdap-profile-03dec15@xxxxxxxxx>
  • Subject: Thick Whois/RDAP Implementation Comment Submission by Web.com
  • From: Jennifer Gore Standiford <JStandiford@xxxxxxx>
  • Date: Thu, 17 Mar 2016 20:48:27 +0000

Web.com Group Inc. supports the alternative framework proposed by Google Inc. 
in its comments on Thick Whois/RDAP 

We agree that a consistent format outlined in the Thick Whois Policy 
requirements will result in optimal implementation based on the following 

     *   Reseller Field will remain optional for both registries and registrars;
     *   Registries will display only one (1) expiration date  that reflects 
the registry expiration date; and
     *   Registrar Abuse Contact Email and Phone Number shall be included 
within the Registry Whois output
The proposed alternative would drastically reduce the timeline for the 
remaining 'Thin Registries' to complete the transition to 'Thick Registries', 
by populating the applicable fields that are solely required in the current 
Registrar Whois and extend the publication within the Registry Whois. 
Registrars should not be required to comply, but rather obtain the option to 
implement RDAP on a volunteer basis.  Registries and participating Registrars 
shall also have the option to develop RDAP-related operational practices that 
will enable participates' willingness to share their key learnings and 
experiences that could be leveraged for future policy development initiatives.


Jennifer Gore
Policy Director
12808 Gran Bay Parkway, West  |  Jacksonville, FL 32258
Office: 904. 680-6919| Cell: 904. 401-4347

PNG image

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy