The call for the IDNs EPDP team will take place on Thursday, 25 July 2024 at 12:00 UTC for 2 hours.
For other places see: https://tinyurl.com/mryww4t
PROPOSED AGENDA
- Roll Call and SOI Updates (2 min)
- Welcome and Chair Updates (5 min)
- Continue Reviewing Phase 2 Initial Report Public Comments: (110mins)
- Revisit comments for PR14-IG15
- Continue Discussions from “Other” (General, Charter Questions without the Team’s Responses)
- AOB (3mins)
BACKGROUND DOCUMENTS
PARTICIPATION
RECORDINGS
Zoom Recording (including audio, visual, rough transcript and chat)
GNSO transcripts are located on the GNSO Calendar
Notes/ Action Items
ACTION ITEMS
- The Team should review IG7 language and provide thoughts on the email list before the next meeting.
- ICANN org will check what can be provided on if a domain set is assigned to a specific registrant. Not who that registrant is, but if a selected domain is in a set (IG 15)
- On the ALAC comment regarding C6, Leadership and Staff will discuss on how to incorporate the comment into the recommendations or rationale.
NOTES
- Roll Call and SOI Updates (2 min)
- Welcome and Chair Updates (5 min)
- Updates were provided by the chair regarding the use of the term “grandfathered” - ETA on a reply from ICANN org is 15 August- and the request from ICANN org to stabilize PR6.
- There was also revised language on IG7 provided to the team by staff.
- ACTION ITEM: The Team should review IG7 language and provide thoughts on the email list before the next meeting.
- Michael Karakesh, ICANN org, announced that the IRT subtract on IDNs will start on 8 August at 18:00 UTC. In order to be a part of this, participants have to sign up for the entire next-round IRT. To sign up please email nextround_policyimplementation@icann.org
- Continue Reviewing Phase 2 Initial Report Public Comments: (110mins)
- Revisit comments for PR14-IG15
- Starting with PR14, the ICANN org comment seeking clarity from the RySG was discussed. This included the public nature of the data requested. The team discussed that having a minimum level of publicly available information should be in place, but the whole data set does not need to be public.
- There was also a second discussion about the RySG comment about the requirement for the public service. Language was revised to ensure that registries are not going to be mandated to perform a task. It was discussed that ICANN org may be able to fulfill the task instead of the registries.
- On IG15, discussion continued on the status of the item.
- ACTION ITEM: ICANN org will check what can be provided on if a domain set is assigned to a specific registrant. Not who that registrant is, but if a selected domain is in a set.
- Continue Discussions from “Other” (General, Charter Questions without the Team’s Responses)
- On “ROID”, the ALAC comment has been accepted.
- There was agreement on the need for a uniform response and for the solution to be interoperable between
- Also relating to the ALAC comment, the potential linkage between C3, C3a and PR6 was discussed. The team will discuss this further.
- The Business Constituency comment was discussed
- There are no outputs and it will stay as is.
- The ALAC discussed consistency among pricing for variant TLDs
- There was some push back as there is not consistency among current domain sales. Pricing is set by the registry and registrar, based on the markets.
- ACTION ITEM: On the ALAC comment regarding C6, Leadership and Staff will discuss on how to incorporate the comment into the recommendations or rationale.
- AOB (3mins)
- The chair provided an update on the path forward for reviewing the revised language
- PR6 will be discussed in the first hour next week as a member of the RySG will only be available for the first half of the call.