Dear TPR WG members,
Please find below the brief notes and action items from yesterday’s meeting.
The next meeting will take place on Tuesday 4 June
2024 at 16:00 UTC.
Kind regards,
Christian, Caitlin, Berry, Julie and Feodora
2024-05-21
Transfer Policy Review PDP WG Call
Action Item:
WG to review initial impact assessment rating in
Initial Report Recommendations Google Doc and propose changes if needed answers to charter questions.
Action Item:
WG will have two weeks to identify any CANNOT LIVE WITH items (focus on Group 1b and Group 2 recs)
Deadline: 3rd of June
i. At this stage it seems, like all of the recommendations, are ready for inclusion in the comprehensive initial report which will include
all of the groups, charter questions, deliberations, and policy recommendations.
ii. Staff explained currently, WG will probably have a couple of additional annexes to include in the report that will need to be updated.
iii. Current draft of initial report is at 121 pages.
iv. Staff opened the discussion on “how to make the report digestible” for public comment.
v. Staff introduced the
Initial Report Recommendations Google Doc and explained the doc is “missing” the deliberation, rationale and impact assessment of each recommendation.
vi. Each recommendation would have an anchor link to an annex in the report that would go over that more detailed deliberation of the working
group for those that are interested.
vii. Staff has gone in and put in a draft policy impact rating as well as a short sentence on why, the policy impact might be low versus high
versus medium.
viii. Legend Options [LOW MEDIUM HIGH]: An example of a LOW impact would be a definitional change, e.g., “Change of Registrant” to “Change of
Registrant Data.” An example of a MEDIUM impact would be a change to an existing requirement or a new requirement. An example of a HIGH impact would be removing a previous requirement, such as the removal of the Post Change of Registrant 60-day transfer restriction.
Criteria to consider when gauging impact: Degree of change from existing requirement? [No change or confirm existing; Modification to existing req.; or New req.] Security enhancement or detraction Level of technical change (impact to CPs) ICANN Contractual
Compliance enforcement capability RNH impacts (such as increased or reduced protections; level of confusion)
ix. A high impact doesn't necessarily mean that it's bad. And a low impact doesn't necessarily mean it's good. It's just to serve as an indication
to the reader that this is a big change from the status quo.
Action Item:
WG to review initial impact assessment rating in
Initial Report Recommendations Google Doc and propose changes if needed.
a shorter explanation of the recommendations and rationals, and then the Annex will include all of those detailed answers to charter questions.
readable and logical.
Action Item:
WG will have two weeks to identify any CANNOT LIVE WITH items (focus on Group 1b and Group 2 recs)
Feodora Hamza
Policy
Development Support Manager (GNSO)
Internet Corporation for Assigned Names and Numbers (ICANN)
Mobile: +32
496 30 24 15
Email: feodora.hamza@icann.org
Website: www.icann.org