Dear All, Please find below the notes and action items from today’s RDS PDP WG meeting. Please take particular note of the following action items: Action item #1: if you have not completed the doodle poll, please do so as soon as possible: http://doodle.com/poll/zezbbghrmwavtdma Action item #2: Those not able to participate in the meeting are encouraged to review the explanation of the triage document provided during the meeting. Action item #3: WG to review D3Triage document with focus on ensuring that pre-requisites/dependencies and assigned phase are correct. Any other feedback on format, refinement of methodology, etc. are also welcome. Action #4: WG members to volunteer to develop use cases of their own interest to be presented during next week's meeting using the attached template (Note, any other EWG example use cases that volunteers want as input are available from staff). Best regards, Marika ================ Notes – RDS PDP WG Meeting 20 July 2016: These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/C4xlAw. 1. Roll call/SOI updates · Attendance will be taken from AC. · Reminder: please check and update your SOI as appropriately. 2. Brief updates on: · Completion of work task #11 - final clean v13 distributed with agenda. Task #11 is hereby considered completed. WG will now prepare for actual deliberations. · Doodle poll results/ICANN57 planning - 38 responses to date. At least 18 would participate, 6 if need be, 10 remote participants. Authoritative confirmation may not be possible at this stage, but this is just to get a sense of possible participation. The GNSO Council is expected to discuss ICANN57 schedule on its call on Thursday so hopefully there will be clarity shortly after that. Action item #1: if you have not completed the doodle poll, please do so as soon as possible: http://doodle.com/poll/zezbbghrmwavtdma · Update on problem statement: it looks like some further work has been done (some discussion and drafting). See https://etherpad.wikimedia.org/p/gnso-rds-pbstatement-0. Not one concise problem statement yet, three different ones that need to be combined / edited down. Anyone can add comments to the etherpad. Hope is that drafting team will complete its work shortly. 3. Review and discuss triage of possible requirements (see D3 Triage, below) · RDS PDP List of Possible Requirements D3 - TriageInProgress - 13 July.docx (previously distributed) · An Excel workbook version is also available for filtering on phase and group: PRSpreadsheets-D3Triage-13July.xlsx · Note that a word version was also distributed (on 13 July) · Purpose of excel sheet is to be able to filter on different phases and groups. · Not stopping with draft 3, draft 4 will be produced next which will include all the possible requirements that have been submitted since draft 3. · Triage is not intended to add, change any of the requirements, it is only a re-organisation of the possible requirements. It includes formatting to include a grid to be able to add columns. This version currently includes 5 columns - first three are the same as in the original document. Column 4 includes the proposed phase according to the charter (phase 1 - requirements, phase 2, policy, phase 3 - implementation / co-existence), column 5 includes a possible grouping - which is just a starting point to highlight possible interdependencies. Unique identifier number means it should always be possible to find back the possible requirement, no matter how the table is sorted. · Guidance from the charter which derives from the process approach determined currently proposed phase. In some cases, a possible requirement may fall into more than 1 stage - likely that these will get refined. · Objective of phase identification is to allow WG to first focus on deliberating phase 1 possible requirements. · Grouping aims to identify possible requirements that have some linkage and/or interdependency (duplicates, connection, sub-requirement of other requirement, etc.). Idea is that this would allow to identify the most foundational requirements that do not have any dependencies. · Group column includes letters - these are a key (see last page for description). Main focus of the possible requirements was determining factor for assigning a key, which was easy in some cases more difficult in others. This is not set in stone - as the WG deliberates and reviews the use cases, it will be able to update as needed. Groups are not intended to be exhaustive. In some cases, possible requirements fell into multiple groups. Categories came from possible requirements themselves, no separate kind of overall grouping approach was applied. May be better to think of them as key words / hashtags, not "group" as that may imply some kind of segregation that was not intended. Key words would allow to show at one glance all requirements linked to for example consent, or proxy. Noting is pulled out - grouping is just a keyword/tag to allow for filtering/sorting. · Best place to focus for WG is pre-requisites & depencies column as well as phase column, to make sure these are accurately. At this stage, there may not be too much value in refining / reviewing the groupings. Grouping is aimed at organising work, it is not a determining factor in how/when possible requirements are deliberated. · Excel sorting will allow WG to view certain parts of the possible requirements to facilitate deliberations. · Word document includes some introductory materials as well as cross-cutting questions identified in the charter that are not available in the excel version. · The triage is assisting us in quickly locating useful information amongst at least 800 items. The grouping doesnt assign any value or restrictions to the requirement. Action item #2: Those not able to participate in the meeting are encouraged to review the explanation of the triage document provided during the meeting. Action item #3: WG to review D3Triage document with focus on ensuring that pre-requisites/dependencies and assigned phase are correct. Any other feedback on format, refinement of methodology, etc. are also welcome. 4. Start work on purpose and use cases (see Example Use Cases attached) · See EWG Report - Example Use Case and Related Data Annexes.doc distributed together with the agenda · Draft example use cases listed on pages 1-2 as distributed with the agenda may be used as input by volunteers if they wish. · Domain name control use cases presented during the meeting by Michele (see attached). · Template for use cases will be sent to the WG list following meeting. Any updates / changes to the template are welcome - the idea behind the template is to facilitate a uniform format for presenting the use cases. · Volunteers requested to come forward to develop use cases for review and discussion during next week's meeting. · Purpose of use cases is to allow to look at particular real world scenarios involving RDS and identify and better understand WHOIS uses which following determination may be determined permissible or non-permissible and/or primary / secondary. As well as understand better the users of RDS and data elements. This should then provide context for deliberation on possible requirements. · Volunteers to provide a one-line summary of the case they are working on so that others know and may choose different use cases. Action #4: WG members to volunteer to develop use cases of their own interest to be presented during next week's meeting using the attached template. 5. Confirm Next Meeting - Tuesday 26 July at 16.00 UTC Marika Konings Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings@icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-e...>.