Dennis and IPT / IRT members,

For this task, the change from “full” to “available” in registry requirement #9 makes sense and I support the change.

While reviewing that change, I noticed that Registrar requirement #6 in section 5 Registrar Requirements is NOT bolded (all the others are in bold). That’s a minor formatting item that should be addressed before the final version is published.

Best,

Marc

From: IRT.RegDataPolicy <irt.regdatapolicy-bounces@icann.org> On Behalf Of Dennis Chang via IRT.RegDataPolicy
Sent: Thursday, May 4, 2023 10:09 AM
To: Anderson, Marc via IRT.RegDataPolicy <irt.regdatapolicy@icann.org>
Subject: [EXTERNAL] [IRT.RegDataPolicy] IRT Task 237 Review URS High Level Technical Requirements - updated due 20230517

Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dear IRT,

There is a minor update to URS High Level Technical Requirements: Registry Requirement 9.

Basically, the change was from ~~full~~ Registration Data to available Registration Data

Here are the links to the redline and clean versions

(Updated) Redlined_URS High Level Technical Requirements for Registries and Registrars

(Updated) Clean_URS High Level Technical Requirements for Registries and Registrars

Both documents as well as the prior documents used for public comment are available in IRT wiki:

https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Resource+Documents

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang