On Tue, 19 Sep 2017 at 18:36, Bernhard Reutner-Fischer <rep.dot....@gmail.com> wrote: > > On 13 September 2017 at 01:17, Francisco Arias > <francisco.ar...@icann.org> wrote: > > Thank you for the suggestion, Bernhard. We'll take it into consider if the > > document is revived, as you said. > > > > -- > > Francisco > > > > On 9/12/17, 2:00 AM, "Bernhard Reutner-Fischer" <rep.dot....@gmail.com> > > wrote: > > > The "RDAP Operational Profile for gTLD Registries and Registrars" > > version 1.0 Document erroneously talks about "publicIDs" (as opposed > > to "publicIds" specified in RFC 7483). > > Please fix if the operational profile ever gets revived. > > In general the profile could need a touch-up, IMHO. > > Further notes i took. > > 1.4.10. An RDAP response MUST contain a remarks member with a > description containing the string "This response conforms to the RDAP > Operational Profile for gTLD Registries and Registrars version 1.0". > > Since remarks are only allowed in objects classes and /help is not an > object this requirement should mention "object response" somewhere as > otherwise it would be in violation with the RFC. > > 1.5.20. A domain name RDAP response MUST contain a remarks member with > a title "Whois Inaccuracy Complaint Form", a description containing > the string "URL of the ICANN Whois Inaccuracy Complaint Form: > https://www.icann.org/wicf"; and a links member with the > https://www.icann.org/wicf URL. > > Drop the "www." part of the URL to be consistent with 1.5.18 (the > "https://icann.org/epp"; URL)
The proposed rdap-profile-31aug18 still uses the superlong wicf URL. Please double check the 31aug18 profile against my comments above. thanks, _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
