The call for the IDNs EPDP team will take place on Thursday, 27 June 2024 at 12:00 UTC for 2 hours.

For other places see: https://tinyurl.com/44usjh3c

PROPOSED AGENDA

  1. Roll Call and SOI Updates (2 min)
  2. Welcome and Chair Updates (5 min)
  3. Continue Reviewing Phase 2 Initial Report Public Comments [docs.google.com]; (110 min)
    1. Finish Discussions for PR6, IG7
    2. Start Discussions from IG2 (Going no further than IG15, sequentially)
  4. AOB (3 min)

 

BACKGROUND DOCUMENTS


PARTICIPATION

Apologies: Anil Jain 

Attendance

RECORDINGS

Audio Recording

Zoom Recording (including audio, visual, rough transcript and chat)

GNSO transcripts are located on the GNSO Calendar

Notes/ Action Items

Action Items

  • Staff and Leadership will work on revised language for the ICANN org comment on PR6 
  • Leadership and staff will review the text and discuss the other stakeholders clause in PR6
  • Leadership and staff will review and update the language for IG2 and its Rationale
  • Leadership and Staff will review the text for PR 8 and 9
  • The RySG small team will review their comment (with relation to PR10) and revert back to the team
  • Staff will discuss with Transfer Policy WG if there are any policies that interact with each other and cause a red flag to be raised.
    • This is similar to how the EPDP team interfaced with ccPDP4


Notes

  • Roll Call and SOI Updates (2 min)
  • Welcome and Chair Updates (5 min)
    • The chair welcomed everyone from the call and congratulated everyone on a successful ICANN80. Using ICANN81 as a benchmark to get everything completed for the P2 Final Report. 
  • Continue Reviewing Phase 2 Initial Report Public Comments [docs.google.com]; (80 min)
    • Finish Discussions for PR6, IG7
      • A proposed team action for the ICANN org comment on PR 6 was presented with approval from the team.
        • ACTION ITEM: Staff and Leadership will work on revised language for the ICANN org comment on PR6
      • On the first ALAC comment, ICANN org asked if it was acceptable to keep “variant sets” as an example of harmonization to ensure clarity.
        • A member of the ALAC requested language to be cleaned up 
        • A different team member mentioned that “i.e.” should be replaced by something like “such as”
      • On the second ALAC comment, there was discussion as to the ccNSO’s role in the relevant stakeholders listed in the recommendation. Registry team members noted that they would accept other stakeholders to observe the process but not for input / votes.
        • ACTION ITEM: Leadership and staff will review the text and discuss the other stakeholders clause in PR6. 
    • Start Discussions from IG2 (Going no further than IG15, sequentially)
      • For IG2, there was a hearty discussion on the specificity of chinese characters related to the ICANN org comment
        • ACTION ITEM: Leadership and staff will review and update the language for IG2 and its Rationale
      • For the RySG IG2 Significant Change required comment, 
      • Moving to PR9 and the RySG Comment, the team has requested additional clarification for the term lifecycle, to be added to the glossary and rationale. 
        • ACTION ITEM: Leadership and Staff will review the text for PR 8 and 9
      • Next, the RySG comment touching on PR 10, 11 and IG 12 was discussed. The input of someone from the Transfer Policy PDP was taken into account by those who drafted the comment. An Impact assessment of the work / policy recommendations 
        • ACTION ITEM: The RySG will review their comment (with relation to PR10) and revert back to the team
        • ACTION ITEM: Staff will discuss with Transfer Policy WG if there are any policies that interact with each other and cause a red flag to be raised. 
          • This is similar to how the EPDP interfaced with ccPDP4
  • AOB (3 min)
    • There will be no meeting on 4 July (US Holiday)
    • There will be a few absences on 11 July (APIGA and other events)
  • No labels