Page History

Notes/ Action Items

ACTION ITEMS:

• Staff will circulate the new language in PR6 and IG7 and The EPDP Team will review and report back.
• Staff will incorporate the RPM PDP WG into the Glossary.
• Staff will update the ROID entry in the glossary.

NOTES

• Roll Call and SOI Updates (2 min)
• Welcome and Chair Updates (5 min)
  • A brief discussion on the Noncommercial Stakeholder Group’s comment to IG 15

• • • There was suggestion that rationale language could be added to ensure no PII is collected in the additional RDDS fields, which the NCSG said would be acceptable. If not possible, the NCSG would recommend dropping IG 15 entirely

• Discuss ICANN org Request: Stabilize Outputs PR6 and IG7 (30 mins)
• ICANN org has requested that the EPDP stabilize the outputs for PR6 and IG7 as they may be considered a dependency for future work on the RSP program.

• • • Does ICANN org want this data so the program can start early or do they need this data so it begins on scheduled time?

• ICANN org provided an update to the work that will be completed and the use case for stabilizing the outputs above. It would be nice to have, but it would not necessarily hold up work
• From a team member in chat: “We should not short-circuit the EPDP processes. Recs/IGs do not become "stable" until the entire process is completed.”
• Updated language that was circulated to the team was discussed and was generally received well by the team.
• There was further discussion on who needs to reach consensus as opposed to which parties are part of the process. In general, everyone should be consulted, but consensus needs to be reached between gTLD Registries and ICANN org.
• ACTION ITEM: Staff will circulate this language in PR6 and IG7 and The EPDP Team will review and report back.
• Continue Reviewing Phase 2 Initial Report Public Comments (80 mins)
• Start Discussions from PR17

• • • On PR18, there was discussion on the subject of the Board and if a committee should be mentioned.

• There was a push to drop the Board WG and just have the subject as the Board.
• There was support to leaving in the reference to the ccNSO council, but the RySG is still uncomfortable with this
• As this recommendation is referring to the process on IDN implementation guidelines and not the actual implementation, there was some push back from the Chair.
• There is not full consensus on this recommendation, as the RySG is opposed to the ccNSO being involved in the policy process, but there is consensus and this will be noted.

• • • • It was suggested that reference to the ccNSO could be moved to the rationale.

• • • For PR20, the RySG believes that if PR18 is updated, PR20 is not necessary.

• Additional context was provided. PR18 is about formalizing and documenting the process for IDN Implementation Guidelines. PR20 is about how future versions of the IDN Implementation Guidelines are approved. The Chair supports keeping this recommendation.
• Discussions on “Other” (Glossary, General, Charter Questions without the Team’s Responses)

• • • The team agreed that the RPM PDP WG will be explicitly mentioned in the glossary

• ACTION ITEM: Staff will incorporate the RPM PDP WG into the Glossary.

• • • The NCSG comment on reading level was determined by the chair to be out of scope. This topic is highly technical and difficult to understand and it will not be easy to remove complexity from the document
    • An “easy fix” was suggested for the ALAC Comment and agreed upon by the team.

• ACTION ITEM: Staff will update the ROID entry in the glossary.
• AOB (3 min)