On 29 Jul 2015, at 19:10, Kal Feher wrote:

PDT_Whois_TC_Web:

WhoisWeb01 – There is no explicit or implied requirement for HTTPS for web based whois in the Registry Agreement or the clarifications announcement. The lack of HTTPS should not be cause for a warning. The previous PDT_Whois_TC_Web document (E) had HTTPS as optional and I’m not aware of any recent approved policy which overrides this. Perhaps the pdtwhois.xml file should include an element stating whether HTTPS is supported or not. If it is, then the criteria for PASS, WARN and FAIL can remain unchanged. If HTTPS is explicitly not supported, then HTTPS testing should be limited to confirming that it is in fact not available.


I think that if no support is claimed, then it should not be tested at all.

Luis Muñoz
Director, Registry Operations
____________________________

2161 San Joaquin Hills Road
Newport Beach, CA 92660

Office +1 949 706 2300 x 4242
lem@uniregistry.link