<<<
Chronological Index
>>> <<<
Thread Index
>>>
FW: [RrSG-Members] Fwd: ACTION REQUESTED: Thick Whois/RDAP Implementation
- To: both <comments-rdds-output-03dec15@xxxxxxxxx>, "comments-rdap-profile-03dec15@xxxxxxxxx" <comments-rdap-profile-03dec15@xxxxxxxxx>
- Subject: FW: [RrSG-Members] Fwd: ACTION REQUESTED: Thick Whois/RDAP Implementation
- From: Wayne Diamond <wayne@xxxxxxxxxxxxx>
- Date: Fri, 18 Mar 2016 06:15:30 +0000
DiaMatrix CC (IANA # 1645) supports the alternative framework proposed by
Google Inc. in its comments on Thick Whois/RDAP
Implementation<http://forum.icann.org/lists/comments-rdap-profile-03dec15/pdfXEuYViKmu4.pdf>.
We agree that the consistent display requirements in the Thick Whois Policy
could be better implemented as follows:
* Having registries include the Registrar Abuse Contact Email and Phone
Number in their Whois Outputs;
* Keeping the Reseller Field Optional for both registries and
registrars; and
* Having Registries continue to display only one expiration date (the
registry expiration date).
Considering that this proposed alternative would condense the timeline for the
remaining thin registries to transition to thick and show fields that are
currently only required in the registrar output within the registry output,
registrars should not be required to implement RDAP. Pending policy development
work that is applicable to RDAP, registries (and registrars that optionally
implement RDAP) should be free to develop their own operational practices for
RDAP and be encouraged to share their findings and experiences to inform future
policy development work.
Regards,
Wayne Diamond
----------------------------------------------------------------------------------------------------
Telephone: 011 640 9700 / 0861 100 698
Fax # 086-686-2445
www.domains.co.za<http://www.domains.co.za/>
-----------------------------------------------------------------------------------------------------
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|