Verification of the ROID in PDT and upcoming Advisory
Dear Colleagues, As a follow up to the draft updated PDT specifications (http://newgtlds.icann.org/en/announcements-and-media/announcement-2-22jul1 5-en) and the gTLD Registries Operational Workshop held in Buenos Aires, I would like to let you know that ICANN is planning to release a verification of the ROID format as part of Pre-Delegation Testing (PDT). The ROID check would be done as part of both the EPP and Whois tests cases. The verification would check two things: 1) that the ROID is properly formatted as described in RFC 5730, per Specification 6 of the registry agreement; and 2) that the repository identifier used is already registered with IANA (https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids.xht ml). This update will be implemented at the same time as the updates regarding the RDDS (Whois) Advisory. We will implement warnings (no failures) in case of deviations starting on 2 November 2015, and strict enforcement will start on 31 January 2016. Finally, ICANN is planning to release in the next few weeks an advisory at https://www.icann.org/resources/pages/advisories-2012-02-25-en describing the considerations that registries should have when migrating ROIDs. I have attached a draft of the advisory and would appreciate any input you may have by 17 August. Please let me know if you have any questions or comments. Regards, -- Francisco Arias Director, Technical Services Domain Name Services & Industry Engagement Global Domains Division ICANN
Finally, ICANN is planning to release in the next few weeks an advisory at https://www.icann.org/resources/pages/advisories-2012-02-25-en <https://www.icann.org/resources/pages/advisories-2012-02-25-en> describing the considerations that registries should have when migrating ROIDs. I have attached a draft of the advisory and would appreciate any input you may have by 17 August.
Francisco, In the plan requirement, number 4 says: "4) The Registry MUST provide the affected registrars and ICANN (through a GDD portal case), the mapping of the new to the old ROIDs." Does this need to be a one-to-one mapping listed all contacts, or for registries that can say a general rule can it be just the rule ? For instance, something like "all ROIDs previously known as something-something will now be something_something-UniqueID". Tks, Rubens
Hi Rubens, Please see below. On 8/6/15, 5:22 PM, "Rubens Kuhl" <rubensk@nic.br<mailto:rubensk@nic.br>> wrote: In the plan requirement, number 4 says: "4) The Registry MUST provide the affected registrars and ICANN (through a GDD portal case), the mapping of the new to the old ROIDs." Does this need to be a one-to-one mapping listed all contacts, or for registries that can say a general rule can it be just the rule ? For instance, something like "all ROIDs previously known as something-something will now be something_something-UniqueID". Either would work. A description of the algorithm would be preferred, but if not possible or for simplicity (e.g., there are only a handful of names registered when the ROID change is done) the registry provides a table mapping one to one, that would work too. Regards, -- Francisco.
Dear Colleagues, Thank you for your input. We intend to publish the final advisory next Tuesday including the clarification requested by Rubens. I’ll update you when the publication is done. Regards, -- Francisco. On 8/6/15, 4:59 PM, "Francisco Arias" <francisco.arias@icann.org> wrote:
Dear Colleagues,
As a follow up to the draft updated PDT specifications (http://newgtlds.icann.org/en/announcements-and-media/announcement-2-22jul 1 5-en) and the gTLD Registries Operational Workshop held in Buenos Aires, I would like to let you know that ICANN is planning to release a verification of the ROID format as part of Pre-Delegation Testing (PDT).
The ROID check would be done as part of both the EPP and Whois tests cases. The verification would check two things: 1) that the ROID is properly formatted as described in RFC 5730, per Specification 6 of the registry agreement; and 2) that the repository identifier used is already registered with IANA (https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids.xh t ml).
This update will be implemented at the same time as the updates regarding the RDDS (Whois) Advisory. We will implement warnings (no failures) in case of deviations starting on 2 November 2015, and strict enforcement will start on 31 January 2016.
Finally, ICANN is planning to release in the next few weeks an advisory at https://www.icann.org/resources/pages/advisories-2012-02-25-en describing the considerations that registries should have when migrating ROIDs. I have attached a draft of the advisory and would appreciate any input you may have by 17 August.
Please let me know if you have any questions or comments.
Regards,
-- Francisco Arias Director, Technical Services Domain Name Services & Industry Engagement Global Domains Division ICANN
The Advisory has been published at https://www.icann.org/resources/pages/advisories-2012-02-25-en Regards, -- Francisco. On 8/20/15, 11:57 AM, "Francisco Arias" <francisco.arias@icann.org> wrote:
Dear Colleagues,
Thank you for your input. We intend to publish the final advisory next Tuesday including the clarification requested by Rubens.
I’ll update you when the publication is done.
Regards,
-- Francisco.
On 8/6/15, 4:59 PM, "Francisco Arias" <francisco.arias@icann.org> wrote:
Dear Colleagues,
As a follow up to the draft updated PDT specifications (http://newgtlds.icann.org/en/announcements-and-media/announcement-2-22ju l 1 5-en) and the gTLD Registries Operational Workshop held in Buenos Aires, I would like to let you know that ICANN is planning to release a verification of the ROID format as part of Pre-Delegation Testing (PDT).
The ROID check would be done as part of both the EPP and Whois tests cases. The verification would check two things: 1) that the ROID is properly formatted as described in RFC 5730, per Specification 6 of the registry agreement; and 2) that the repository identifier used is already registered with IANA (https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids.x h t ml).
This update will be implemented at the same time as the updates regarding the RDDS (Whois) Advisory. We will implement warnings (no failures) in case of deviations starting on 2 November 2015, and strict enforcement will start on 31 January 2016.
Finally, ICANN is planning to release in the next few weeks an advisory at https://www.icann.org/resources/pages/advisories-2012-02-25-en describing the considerations that registries should have when migrating ROIDs. I have attached a draft of the advisory and would appreciate any input you may have by 17 August.
Please let me know if you have any questions or comments.
Regards,
-- Francisco Arias Director, Technical Services Domain Name Services & Industry Engagement Global Domains Division ICANN
Dear Colleagues, My coworkers at IANA asked me to remind you that: To add your EPP Repository IDs to the IANA registry, please send the following information to iana@iana.org. For formatting examples, see http://www.iana.org/assignments/epp-repository-ids. Required Fields: EPP Repository ID (using the format “FOO, #x0046 #x004F #x004F”): Change Controller ID: Change Controller Name: Change Controller Email: Reference/Contact ID: Reference/Contact Name: Reference/Contact Email The Change Controller ID and Reference/Contact ID fields can be filled in with a short string or a long name, as desired. Names and IDs can be identical. Regards, -- Francisco. On 8/26/15, 6:06 PM, "Francisco Arias" <francisco.arias@icann.org> wrote:
The Advisory has been published at https://www.icann.org/resources/pages/advisories-2012-02-25-en
Regards,
-- Francisco.
On 8/20/15, 11:57 AM, "Francisco Arias" <francisco.arias@icann.org> wrote:
Dear Colleagues,
Thank you for your input. We intend to publish the final advisory next Tuesday including the clarification requested by Rubens.
I’ll update you when the publication is done.
Regards,
-- Francisco.
On 8/6/15, 4:59 PM, "Francisco Arias" <francisco.arias@icann.org> wrote:
Dear Colleagues,
As a follow up to the draft updated PDT specifications (http://newgtlds.icann.org/en/announcements-and-media/announcement-2-22j u l 1 5-en) and the gTLD Registries Operational Workshop held in Buenos Aires, I would like to let you know that ICANN is planning to release a verification of the ROID format as part of Pre-Delegation Testing (PDT).
The ROID check would be done as part of both the EPP and Whois tests cases. The verification would check two things: 1) that the ROID is properly formatted as described in RFC 5730, per Specification 6 of the registry agreement; and 2) that the repository identifier used is already registered with IANA (https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids. x h t ml).
This update will be implemented at the same time as the updates regarding the RDDS (Whois) Advisory. We will implement warnings (no failures) in case of deviations starting on 2 November 2015, and strict enforcement will start on 31 January 2016.
Finally, ICANN is planning to release in the next few weeks an advisory at https://www.icann.org/resources/pages/advisories-2012-02-25-en describing the considerations that registries should have when migrating ROIDs. I have attached a draft of the advisory and would appreciate any input you may have by 17 August.
Please let me know if you have any questions or comments.
Regards,
-- Francisco Arias Director, Technical Services Domain Name Services & Industry Engagement Global Domains Division ICANN
participants (2)
-
Francisco Arias -
Rubens Kuhl