Dear Work Track members, Please see below the action items and notes from the meeting today. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording or transcript. See the chat transcript and recording at: https://community.icann.org/display/NGSPP/Work+Track+4+Meetings.   Slides are attached for reference and some chat room excerpts are included below. Kind regards, Julie Julie Hedlund, Policy Director ---------------------------------------------------------------------------------------- Notes and Action Items: New gTLD Subsequent Procedures PDP WG - Track 4 – 01 March 2018 1. Welcome, SOI updates: No updates. 2. WG Co-chairs guidance on Initial Report: -- Very aggressive timeline.  Want to hone in on possible recommendations where there is no contention, as well as questions for the community. -- There is an Initial Report format used by the GNSO. -- There are a number of documents from various Work Tracks that are being compiled into one very preliminary draft working document. -- A lot of the Initial Report will be presenting the different options on the table and where we don't have recommendations.  Propose questions for public comment the would include your perspective. -- Document will be the bulk and meat of the report, such as recommendations and questions; there are other pieces that we will include later, such as appendices etc., as they are informed by the substance. -- Will pick up the boilerplate contents later. -- Capture everyone's views in the Initial Report.  Need to have the positions document and get input on all of the different options. 3. Registry System Testing Slide 14: Convergence of Recommendations: -- Split RST between overall RSP matters and specific TLD testing. -- Remove a better part or all of self-certification assessments. -- Rely on SLA monitoring for most if not all overall RSP testing. -- Limiting IDN testing to specific TLD policy. -- RSP Pre-Approval Program Slide 15: Recommendations that are not convergent: -- IDN testing -- Additional operational tests -- 3rd-party certifications of ROs/RSPs infrastructure and key personnel -- Periodic RSP audits -- Stricter penalties for repeated SLA breaches -- Consideration of number of TLDs per RSP in RST Discussion: -- Idea of ISO certifications.  Makes barriers quite high.  It costs money and not all companies can do this. -- Certification that it is not directly tied to technical performance (not only price concern) -- Stricter SLA it was not shown why ICANN wants more strict SLA penalties.  Don't have an answer from ICANN why. -- To have an audit of an RSP you have to have a relationship with them.  To have another contract makes it more complicated.

From the chat:

Steve Chan: Taking a look again at the recommendation from technical services, it does mention the expected number of registrations, but it does not appear to cover the other element you mentioned, about activity in the TLD. Rubens Kuhl: Steve, they mentioned total registrations instead of registrations per time period. 3. Next meeting:  Face-to-Face meeting at ICANN61 -- 10 March 12:15-15:00 for SubPro -- Work Track 4 in the last 45 minutes unless this changes.