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:
On 12 October 2016 at 02:46, Francisco Arias <francisco.ar...@icann.org>
wrote:
> FYI,
>
>
>
> There is an updated proposal to handle the RySG proposed revision to the
> CL&D policy to remove the requirement to implement RDAP. We are planning
to
> put a draft updated CL&D policy for public comment before the end of the
> month.
>
>
>
> We are also planning to issue the request to implement RDAP (on
contractual
> basis as opposed to policy) in parallel but separate from the request to
> implement the revised CL&D policy. Both requests, to implement CL&D and
> RDAP, are expected to happen by the end of January 2017 (after the public
> comment period) with effective date of implementation by 1 August 2017.
[]
> 1. ICANN to issue a revised CL&D Policy to all registry operators,
removing
> provision 12. For your reference, provision 12 states: “The implementation
> of an RDAP service in accordance with the "RDAP Operational Profile for
gTLD
> Registries and Registrars" is required for all gTLD registries in order to
> achieve consistent labeling and display.” Additionally, I have attached
the
> proposed revised CL&D Policy.
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.
Thanks,
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
