Patrick Mevzek<p>The "joy" of <a href="https://framapiaf.org/tags/RDAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDAP</span></a> and especially its "notice" elements is to allow a registry to publish basically that they do NOT guarantee any accuracy and want to not be liable to any problems related to that, yet ICANN contract with registry at <a href="https://itp.cdn.icann.org/en/files/registry-agreements/base-registry-agreement-21-01-2024-en.html#specification10.4" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">itp.cdn.icann.org/en/files/reg</span><span class="invisible">istry-agreements/base-registry-agreement-21-01-2024-en.html#specification10.4</span></a> clearly defines an <a href="https://framapiaf.org/tags/RDAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDAP</span></a> update time (between <a href="https://framapiaf.org/tags/EPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPP</span></a> command and RDAP visibility) of "≤ 60 min, for at least 95% of the probes". So eventually consistent…</p>