I guess 7.1.X is a matter of the interpretation of the word "transfer".

7.1.1. Domain Name > Already in place for technical reasons.
 7.1.2. Registrar URL -> out of band, registrar portal
 7.1.3. Registrar -> login
 7.1.4. Registrar IANA ID -> out of band, account accreditation
 7.1.5. Registrar Abuse Contact Email -> out of band, registrar portal
 7.1.6. Registrar Abuse Contact Phone -> out of band, registrar portal
 7.1.7. Domain Status(es) -> Already in place for technical reasons.

Makes me wonder if the above is really required for the policy.

Best,

Theo

Hi,

The policy states the following;

7. Transfer of Registration Data from Registrar to Registry Operator
7.1. Registrar MUST transfer the following data elements to Registry Operator: (See
Implementation Note B.1-2)
7.1.1. Domain Name
7.1.2. Registrar URL
7.1.3. Registrar
7.1.4. Registrar IANA ID
7.1.5. Registrar Abuse Contact Email
7.1.6. Registrar Abuse Contact Phone
7.1.7. Domain Status(es)

However this is not how it technically works.

When you send a domain create to the registry using EPP it contains the following information.

1 Domain name

2 Name servers (optional)

3 Period 1-10

That is it.

The same goes for the registrar WHOIS server, this is not something registrars send to the registry.

A note on the IANA ID, only Verisign uses that. Other gTLD's use a different ID in their database and as such in the RDAP/WHOIS output.

7.5.2. Reseller
This information is not send to a registry. Such information is available sometimes at an RDAP or WHOIS server.

Section 9.2.5 Proxy services. In order to make this work we need an new EPP extension to mark such registrations so the registry can identify such registrations.

From an implementation point of view. The changes at the registry and registrar level are massive. Let me boil this down to three phases of implementation.

Registry changes, backwards compatible

• admin/billing/tech optional
• registrant optional if no processing agreement
• thin contacts, (name, phone, email only for tech contacts)
• implement epp disclose mandatory
• accredited privacy epp extension

Registry changes + migration

• adjust systems
• disclose update
• delete admin/billing/tech
• EPP extension accredited privacy

Registry changes, final

• delete admin/billing data & support
• tech delete additional data?

The above is just high level, most likely I missed a few other things. However if there is an idea to implement all this within a one month time frame at a set date, that is going to be very risky and a real challenge and I advise not to go down that route.

Best,

Theo

Op 04/05/2023 om 16:08 schreef Dennis Chang via IRT.RegDataPolicy:

Dear IRT,

 

We’ve completed review of all public comments and made the updates to the policy language.

Prepared are the redline version and the clean version for your review.

• The Registration Data Policy with redlined changes resulting from Public Comment: Registration Data Policy - Redline Version Post Public Comment
• The clean version of the Registration Data Policy with changes resulting from Public Comment: Registration Data Policy - CLEAN Version Post Public Comment

Also prepared is the Public Comment Report Addendum that documents the analysis and responses for the comments.

• Public Comment Report - 20 January 2023
• Public Comment Report Addendum - Responses to Registration Data Public comment - 28 April 2023

You will find all these documents posted on the IRT wiki following our normal process. https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Resource+Documents

We’ll go over these in the IRT meeting on 10 May 2023.

-- 

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang

www.icann.org One World – One Internet

 

_______________________________________________
IRT.RegDataPolicy mailing list
IRT.RegDataPolicy@icann.org
https://mm.icann.org/mailman/listinfo/irt.regdatapolicy

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

_______________________________________________
IRT.RegDataPolicy mailing list
IRT.RegDataPolicy@icann.org
https://mm.icann.org/mailman/listinfo/irt.regdatapolicy

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.