Took a look, some comments: 1.3.2 - I agree that RDAP providers have to offer https, but I don't see why they can't also offer plain http if they want. 1.4.1 - it says servers must support A-labels or U-labels, but I expect you mean they have to accept both. Do they have to accept names with a mixture of the two? 1.4.4 and 1.4.5 - this currently says that all of the JSON has to be returned as one giant line with no line breaks, which doesn't match the examples in RFC 7483 and doesn't make much sense. It it supposed to say there's no leading or trailing spaces or line breaks inside of JSON string values? 2.8.2 - says that if a service moves, the old service only needs to stay up until the IANA bootstrap http expiration. That's a week, which seems too short. Once the set of TLDs stabilizes, I expect people will refresh their bootstrap on the order of once a month. 2.8.3 - I don't understand it. Is it supposed to mean don't publish a bootstrap until the server is available on both ipv4 and ipv6? If so that seems redundant with 1.3.6. 3.1.2 - if you query a registrar for a name, it belongs to someone else, and the registrar happens to know whose it is (an affiliate with a separate RDAP server, perhaps) what's the harm in allowing a 301 to redirect there? R's, John