Implementation Review Team: Difference between revisions

(12 intermediate revisions by 2 users not shown)

Line 1:

An '''Implementation Review Team''' is a voluntary [[ICANN]] team that ~~reviews proposed~~ implementation ~~plans as drafted by [[ICANN Organization]]~~, ~~checking for consistency with~~ [~~[ICANN Board]]~~-~~approved GNSO recommendations~~. ~~The team also answers questions and gathers clarifications from~~ ICANN ~~org as needed. It provides advice~~ on ~~technical~~ and ~~operational details concerning the recommendations in question~~.<ref>[https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf Implementation Review Team (IRT) Principles & Guidelines]</ref>

An '''Implementation Review Team''' is a voluntary [[ICANN]] team which is convened to assist staff in

developing the implementation details for a given policy to ensure that the implementation conforms to this police recommendations. Thus, each IRT is different depending on the issues addressed.<ref name="cpif">[https://gnso.icann.org/sites/default/files/policy/2025/correspondence/psr-to-gnso-council-07feb25-en.pdf ICANN GNSO: Policy Status Report on the Policy and Implementation Recommendations]</ref> The IRT is not a forum for opening or revising policy discussions, unless new information became available.<ref name="guide">[https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf ICANN GNSO: Implementation Review Team (IRT) Principles & Guidelines]</ref>

==~~History~~==

== Guidelines ==

The GNSO Council approved and assembled a pre-IRT in April 2019 just before the ICANN Board considered the EPDP Team's Final Report to guide the implementation of the Interim Registration Data Policy. All pre-IRT members transitioned to the IRT, for which [[ICANN]] called volunteers on 20 May 2019. The IRT helps with the implementation of the Expedited Policy Development Process ([[EPDP]]) Team's Phase 1 policy recommendations. ICANN expressed special interest in the assistance EPDP Phase 1 Team members and registry and registrar representatives could offer.<ref>[https://www.icann.org/en/announcements/details/call-for-volunteers-implementation-review-team-for-registration-data-policy-implementation-20-5-2019-en Call for IRT on RegDataPolicy Volunteers, ICANN Announcements]</ref>

==~~Active~~ IRTs==

In August 2016, the [https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf IRT Principles and Guidelines] was published as part of the GNSO Policy & Implementation Working Group Final Recommendations Report. Since the adoption and the implementation of the Recommendations Report, IRTs have been formed and operated under those principles and guidelines.<ref name="cpif"></ref>

* Registration Data Policy ~~for All gTLDs~~ (~~EPDP Phase 1 Implementation~~)

=== CPIF ===

The [[Consensus Policy Implementation Framework]] (CPIF), a document by ICANN org, provides a holistic framework for an implementation process involving several distinct parties. However, its ICANN org-specific focus means that it exists alongside, and in some cases, duplicates alternative implementation guidance produced by the GNSO, notably the IRT Principles and Guidelines. This may lead to confusion regarding the convening of the IRT and its responsibilities.<ref name="cpif"></ref>

== Formation and Recruitment ==

According to IRT Principles and Guidelines, an IRT must be lauched after a PDP Working Group adopts Consensus Policy recommendations.

The IRT volunteer recruitment process must take into account what areas of expertise are expected to be needed for each team.

Also, the call for IRT volunteers should at a minimum be sent to all members of the PDP working group that was responsible for developing the policy recommendations. IRTs should include at least one participant from the original PDP WG who can provide insight into the original reasoning behind consensus policy recommendations.

The call for volunteers may need to reach beyond the working group members to ensure broad participation by parties directly impacted by the implementation and parties with specialized expertise needed. In some cases, additional outreach at the start or at a later stage of the IRT may be necessary to ensure that appropriate expertise is available and that directly affected parties are involved. IRTs are open to all interested parties.

The GNSO Council is expected to designate a GNSO Council liaison to each IRT to ensure a direct link to the GNSO if needed. <ref name="guide"></ref>

== IRT Before the Guidelines ==

Before the publication of the Guidelines, each team created its own scope, mailing list, and meeting cadence.

The first documented IRT was the PEDNR Implementation Review Team, as described in the Approved Board Resolutions on October 28, 2011: "The GNSO Council shall convene a PEDNR Implementation Review Team to assist ICANN Staff in developing the implementation details for the new policy should it be approved by the ICANN Board. The Implementation Review Team will be tasked with evaluating the proposed implementation of the policy recommendations as approved by the Board and is expected to work with ICANN Staff to ensure that the resultant implementation meets the letter and intent of the approved policy."<ref>[https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-dakar-28-10-2011-en ICANN: Approved Board Resolutions | Regular Meeting of the ICANN Board | Dakar 28 October 2011]</ref>

== Implementation Review Teams ==

* [[Inter-Registrar Transfer Policy (IRTP) Series IRT]]

* [[Post-Expiration Domain-Name Recovery (PEDNR) IRT]]

* [[UDRP-Lock IRT]]

* [[IGO-INGO Identifiers Protection IRT]]

* [[Thick WHOIS IRT]]

* [[T/T Contact-Info IRT]]

* [[Registration Data Policy IRT]]

* [[Subsequent Procedures IRT]]

* [[IGO-INGO Curative Rights IRT]]

* [[Across-Field Address Validation IRT]]

* [[Privacy & Proxy Services Accreditation (PPSAI) IRT]]

* [[Registrar Naming Services Portal (RNSP) IRT]]

==References==

[[Category:Communities of Practice]]

[[Category:ICANN]]

@@ Line 1: / Line 1: @@
-An '''Implementation Review Team''' is a voluntary [[ICANN]] team that reviews proposed implementation plans as drafted by [[ICANN Organization]], checking for consistency with [[ICANN Board]]-approved GNSO recommendations. The team also answers questions and gathers clarifications from ICANN org as needed. It provides advice on technical and operational details concerning the recommendations in question.<ref>[https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf Implementation Review Team (IRT) Principles & Guidelines]</ref>
+An '''Implementation Review Team''' is a voluntary [[ICANN]] team which is convened to assist staff in
+developing the implementation details for a given policy to ensure that the implementation conforms to this police recommendations. Thus, each IRT is different depending on the issues addressed.<ref name="cpif">[https://gnso.icann.org/sites/default/files/policy/2025/correspondence/psr-to-gnso-council-07feb25-en.pdf ICANN GNSO: Policy Status Report on the Policy and Implementation Recommendations]</ref> The IRT is not a forum for opening or revising policy discussions, unless new information became available.<ref name="guide">[https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf ICANN GNSO: Implementation Review Team (IRT) Principles & Guidelines]</ref>
-==History==
+== Guidelines ==
-The GNSO Council approved and assembled a pre-IRT in April 2019 just before the ICANN Board considered the EPDP Team's Final Report to guide the implementation of the Interim Registration Data Policy. All pre-IRT members transitioned to the IRT, for which [[ICANN]] called volunteers on 20 May 2019. The IRT helps with the implementation of the Expedited Policy Development Process ([[EPDP]]) Team's Phase 1 policy recommendations. ICANN expressed special interest in the assistance EPDP Phase 1 Team members and registry and registrar representatives could offer.<ref>[https://www.icann.org/en/announcements/details/call-for-volunteers-implementation-review-team-for-registration-data-policy-implementation-20-5-2019-en Call for IRT on RegDataPolicy Volunteers, ICANN Announcements]</ref>
-==Active IRTs==
+In August 2016, the [https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/irt-principles-guidelines-23aug16-en.pdf IRT Principles and Guidelines] was published as part of the GNSO Policy & Implementation Working Group Final Recommendations Report. Since the adoption and the implementation of the Recommendations Report, IRTs have been formed and operated under those principles and guidelines.<ref name="cpif"></ref>
-* Registration Data Policy for All gTLDs (EPDP Phase 1 Implementation)
+=== CPIF ===
+The [[Consensus Policy Implementation Framework]] (CPIF), a document by ICANN org, provides a holistic framework for an implementation process involving several distinct parties. However, its ICANN org-specific focus means that it exists alongside, and in some cases, duplicates alternative implementation guidance produced by the GNSO, notably the IRT Principles and Guidelines. This may lead to confusion regarding the convening of the IRT and its responsibilities.<ref name="cpif"></ref>
+== Formation and Recruitment ==
+According to IRT Principles and Guidelines, an IRT must be lauched after a PDP Working Group adopts Consensus Policy recommendations.
+The IRT volunteer recruitment process must take into account what areas of expertise are expected to be needed for each team.
+Also, the call for IRT volunteers should at a minimum be sent to all members of the PDP working group that was responsible for developing the policy recommendations. IRTs should include at least one participant from the original PDP WG who can provide insight into the original reasoning behind consensus policy recommendations.
+The call for volunteers may need to reach beyond the working group members to ensure broad participation by parties directly impacted by the implementation and parties with specialized expertise needed. In some cases, additional outreach at the start or at a later stage of the IRT may be necessary to ensure that appropriate expertise is available and that directly affected parties are involved. IRTs are open to all interested parties.
+The GNSO Council is expected to designate a GNSO Council liaison to each IRT to ensure a direct link to the GNSO if needed. <ref name="guide"></ref>
+== IRT Before the Guidelines ==
+Before the publication of the Guidelines, each team created its own scope, mailing list, and meeting cadence.
+The first documented IRT was the PEDNR Implementation Review Team, as described in the Approved Board Resolutions on October 28, 2011: "The GNSO Council shall convene a PEDNR Implementation Review Team to assist ICANN Staff in developing the implementation details for the new policy should it be approved by the ICANN Board. The Implementation Review Team will be tasked with evaluating the proposed implementation of the policy recommendations as approved by the Board and is expected to work with ICANN Staff to ensure that the resultant implementation meets the letter and intent of the approved policy."<ref>[https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-dakar-28-10-2011-en ICANN: Approved Board Resolutions | Regular Meeting of the ICANN Board | Dakar 28 October 2011]</ref>
+== Implementation Review Teams ==
+* [[Inter-Registrar Transfer Policy (IRTP) Series IRT]]
+* [[Post-Expiration Domain-Name Recovery (PEDNR) IRT]]
+* [[UDRP-Lock IRT]]
+* [[IGO-INGO Identifiers Protection IRT]]
+* [[Thick WHOIS IRT]]
+* [[T/T Contact-Info IRT]]
+* [[Registration Data Policy IRT]]
+* [[Subsequent Procedures IRT]]
+* [[IGO-INGO Curative Rights IRT]]
+* [[Across-Field Address Validation IRT]]
+* [[Privacy & Proxy Services Accreditation (PPSAI) IRT]]
+* [[Registrar Naming Services Portal (RNSP) IRT]]
 ==References==
+{{reflist}}
 [[Category:Communities of Practice]]
+[[Category:ICANN]]