<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div><span>Hi there,</span></div><div><span><br></span></div><div id="yui_3_16_0_ym19_1_1467283460469_105922"><span>I was just watching the Adobe Connect videos and am happy to put a face on so many names. You all look great! :)</span></div><div></div><div id="yui_3_16_0_ym19_1_1467283460469_105927"> </div><div class="signature" id="yui_3_16_0_ym19_1_1467283460469_105924">Nathalie </div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> On Thursday, June 30, 2016 11:02 AM, "Gomes, Chuck" <cgomes@verisign.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv0034955033"><style>#yiv0034955033 #yiv0034955033 --
_filtered #yiv0034955033 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;}
_filtered #yiv0034955033 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;}
_filtered #yiv0034955033 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered #yiv0034955033 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
_filtered #yiv0034955033 {}
#yiv0034955033
#yiv0034955033 p.yiv0034955033MsoNormal, #yiv0034955033 li.yiv0034955033MsoNormal, #yiv0034955033 div.yiv0034955033MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 a:link, #yiv0034955033 span.yiv0034955033MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv0034955033 a:visited, #yiv0034955033 span.yiv0034955033MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv0034955033 p.yiv0034955033MsoNoSpacing, #yiv0034955033 li.yiv0034955033MsoNoSpacing, #yiv0034955033 div.yiv0034955033MsoNoSpacing
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 p.yiv0034955033MsoListParagraph, #yiv0034955033 li.yiv0034955033MsoListParagraph, #yiv0034955033 div.yiv0034955033MsoListParagraph
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 p.yiv0034955033MsoListParagraphCxSpFirst, #yiv0034955033 li.yiv0034955033MsoListParagraphCxSpFirst, #yiv0034955033 div.yiv0034955033MsoListParagraphCxSpFirst
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 p.yiv0034955033MsoListParagraphCxSpMiddle, #yiv0034955033 li.yiv0034955033MsoListParagraphCxSpMiddle, #yiv0034955033 div.yiv0034955033MsoListParagraphCxSpMiddle
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 p.yiv0034955033MsoListParagraphCxSpLast, #yiv0034955033 li.yiv0034955033MsoListParagraphCxSpLast, #yiv0034955033 div.yiv0034955033MsoListParagraphCxSpLast
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv0034955033 span.yiv0034955033EmailStyle19
{color:windowtext;}
#yiv0034955033 span.yiv0034955033EmailStyle20
{color:#1F497D;}
#yiv0034955033 .yiv0034955033MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv0034955033 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv0034955033 div.yiv0034955033WordSection1
{}
#yiv0034955033
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {margin-left:1.25in;}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
_filtered #yiv0034955033 {font-family:Symbol;}
_filtered #yiv0034955033 {}
_filtered #yiv0034955033 {font-family:Wingdings;}
#yiv0034955033 ol
{margin-bottom:0in;}
#yiv0034955033 ul
{margin-bottom:0in;}
#yiv0034955033 </style><div>
<div class="yiv0034955033WordSection1">
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;color:#1F497D;">For those who were not able to participate in the meeting (whether in-person or remotely), please note
</span><b><span style="font-size:11.0pt;">Action Item #5:</span></b><span style="font-size:11.0pt;">
<i>All WG members are asked to review F2F meeting recordings Part 2 and/or transcript Part 3 to ensure that all WG members are up to date with the discussions that took place in Helsinki. Please do this as soon as possible.</i></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><i><span style="font-size:11.0pt;"> </span></i></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><i><span style="font-size:11.0pt;">Several other actions will apply when the applicable updated documents are distributed and a few actions have already been done by staff.</span></i></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><i><span style="font-size:11.0pt;"> </span></i></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><i><span style="font-size:11.0pt;">Chuck</span></i></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal"><span style="font-size:11.0pt;color:#1F497D;"> </span></div>
<div class="yiv0034955033yqt1297441308" id="yiv0034955033yqt37427"><div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;">
<div class="yiv0034955033MsoNormal"><b><span style="font-size:10.0pt;">From:</span></b><span style="font-size:10.0pt;"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Lisa Phifer<br clear="none">
<b>Sent:</b> Thursday, June 30, 2016 9:24 AM<br clear="none">
<b>To:</b> gnso-rds-pdp-wg@icann.org<br clear="none">
<b>Subject:</b> [gnso-rds-pdp-wg] Notes and Action Items - RDS PDP WG F2F Meeting - 28 June 2016</span></div>
</div>
</div>
<div class="yiv0034955033MsoNormal"> </div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">Dear all,</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">The following notes summarize key points of discussion, agreements, and action items from the RDS PDP WG F2F meeting on 28 June at ICANN56. All WG members – especially
those who were unable to attend the meeting - are asked, prior to providing their input, to review the official transcript and recordings of the meeting:</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span class="yiv0034955033MsoHyperlink"><span style="font-family:Symbol;text-decoration:none;"><span style="">·<span style="font:7.0pt;">
</span></span></span></span><span class="yiv0034955033MsoHyperlink"><span style="font-size:11.0pt;"><a rel="nofollow" shape="rect" target="_blank" href="http://schd.ws/hosted_files/icann562016/f0/Transcript%20RDS%201%2028%20June%20Helsinki.pdf">Transcript GNSO RDS Part 1 28 June Helsinki</a></span></span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span class="yiv0034955033MsoHyperlink"><span style="font-size:11.0pt;font-family:Symbol;text-decoration:none;"><span style="">·<span style="font:7.0pt;">
</span></span></span></span><span class="yiv0034955033MsoHyperlink"><span style="font-size:11.0pt;"><a rel="nofollow" shape="rect" target="_blank" href="http://schd.ws/hosted_files/icann562016/29/Transcript%20GNSO%20RDS2%2028%20June%20Helsinki%20%5B1%5D.pdf">Transcript GNSO RDS Part 2 28
June Helsinki </a></span></span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span style="font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span class="yiv0034955033MsoHyperlink"><span style="font-size:11.0pt;"><a rel="nofollow" shape="rect" target="_blank" href="http://schd.ws/hosted_files/icann562016/cd/Transcript%20GNSO%20RDS3%2028%20June%20Helsinki.pdf">Transcript GNSO RDS Part 3 28 June Helsinki</a></span></span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span style="font-size:11.0pt;font-family:Symbol;color:#333333;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;color:#333333;">Adobe Connect Recording </span><span class="yiv0034955033MsoHyperlink"><span style="font-size:11.0pt;"><a rel="nofollow" shape="rect" target="_blank" href="https://icann.adobeconnect.com/p3qr9nmm42k/">Multimedia Session Recording</a>
Part 1</span></span><span style="font-size:11.0pt;color:#333333;"></span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span style="font-size:11.0pt;font-family:Symbol;color:#333333;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;color:#333333;">Adobe Connect Recording
</span><a rel="nofollow" shape="rect" target="_blank" href="https://icann.adobeconnect.com/p3ty476eer8/"><span style="font-size:11.0pt;">Multimedia Session Recording Part 2</span></a><span style="font-size:11.0pt;color:#333333;">
</span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span style="font-size:11.0pt;font-family:Symbol;color:#333333;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;color:#333333;">English Audio </span><a rel="nofollow" shape="rect" target="_blank" href="http://audio.icann.org/meetings/hel56/hel56-OPEN-2016-06-28-T0425-hallb-IC3By7pjcu7tl0hdSj9fNZR36HW1oLO7-en.m3u"><span style="font-size:11.0pt;">Session
Recording Part </span><span style="font-size:11.0pt;color:#0960AB;border:none windowtext 1.0pt;padding:0in;text-decoration:none;">1</span></a><span style="font-size:11.0pt;color:#333333;"></span></div>
<div class="yiv0034955033MsoNoSpacing" style="margin-left:.5in;">
<span style="font-size:11.0pt;font-family:Symbol;color:#333333;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;color:#333333;">English Audio </span><a rel="nofollow" shape="rect" target="_blank" onclick="return theMainWindow.showLinkWarning(this)" href="http://stream.icann.org:8000/hel56-hallb-en.m3u"><span style="font-size:11.0pt;">Session Recording Part 2</span></a><span style="font-size:11.0pt;color:#333333;">
</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">In particular, refer to Transcript Part 3 (Adobe Connect Session Recording Part 2) for significant discussion of how the WG will begin deliberation to reach
consensus. After brief initial deliberation on a few possible requirements, participants agreed to revamp the proposed approach by starting with a statement of purpose and use cases to establish a foundation for deliberation on specific possible requirements.
This proposed approach will be circulated to the full WG for comment by 7 July.</span></b></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">1. Introductions</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">WG members in attendance introduced themselves.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">No SOI updates were noted.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">2. PDP Work Plan: Accomplishments and Status</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Current Work Plan: <a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/x/oIxlAw">
https://community.icann.org/x/oIxlAw</a></span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Reviewed WG progress on recent tasks</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Task 7e: Outreach #1 – Review & Analyze inputs using Comment Review Tool (16 June) – Task completed at this meeting (see agenda item 3 below)
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Task 9c: Outreach #2 – Request additional Possible Requirements (11-27 June) – Additions received from RySG, response with no further inputs at this time received from NCSG, GAC expects to respond
by end of July. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Task 11: Decide how and when the WG will try to reach consensus – Task continued in this meet (see agenda item 3 below)</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Approved Work Plan was relayed to GNSO Council by liaison Stephanie Perrin to inform them of this WG’s initial plans.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Timeline for completing phase 1? Task 11 will determine approach to reaching consensus during phase 1; this will help us get a better handle on timeline, but phase 1 will take a while.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">If an SO/AC/SG/C doesn’t have any input at this point, it would still be helpful if they indicate this now to facilitate planning of WG activities.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">3. PDP Work Plan: Next Steps and Working Session</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><u><span style="font-size:11.0pt;">Task 7f: Outreach #1 – Finalize Comment Review Tool</span></u></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">The WG reviewed the draft Comment Review Tool:<br clear="none">
</span><a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/download/attachments/59641480/Outreach%20%231%20-%20Public%20Comment%20Review%20Tool%20-%2025%20June%202016%20.docx?version=1&modificationDate=1467016057000&api=v2"><span style="font-size:10.5pt;">Outreach
#1 - Public Comment Review Tool - 25 June 2016 .docx</span></a><span style="font-size:11.0pt;"></span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Q2-RySG – Add text under Action Items: WG members should be tasked with extracting possible requirements from the RySG comments provided here</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Responses that refer to deliberating upon possible requirements should note that the WG is currently developing a phase 1 process for deliberating on all possible requirements</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">How will the GAC be engaged in this PDP so that concerns are not raised at the end of the process?
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">It is important to address any differences between PDP advice and GAC advice throughout the PDP process, so that there is no need for board to consider over-riding policy recommendations.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Steps have already been taken to facilitate this – for example, the GAC has provided input through outreach #1 – and it is important that input is taken into consideration by the WG. We have an active
liaison to the GAC PSWG (Greg Mounier) to facilitate on-going interaction. There may still be situations where the GAC does not agree with GNSO consensus policy but hopefully there will be fewer with early/on-going engagement.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">To answer the question of is a new RDS needed we need to take into consideration the outcome of parallel WHOIS improvements – it is part of this WG’s charter to do so. If improvements haven’t yet
been implemented, may need to reflect any assumptions in the WG’s initial report.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Q2-GAC – Vicky Scheckler volunteered to extract possible requirements from the GAC’s suggested inputs. Adjust action item text to reflect this.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Noted that some EWG member statements and blogs still need volunteers to extract possible requirements. Ayden Ferdeline and Stacie Walsh volunteered to do so.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Q4-SSAC response – Revise to indicate that the WG is in the process of gathering possible requirements to help define the problem.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Q4 SSAC response – A Problem Statement drafting team was formed to help develop a very concise and tight problem statement, drawing from the Issue Report and Charter. This should be a conceptual
problem statement; it should not redefine the issue or charter or go into details and/or solutions. This drafting will be done in parallel to ongoing work.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Volunteers for this drafting team are:
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Stephanie Perrin</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">James Gannon.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Alex Deacon </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Nick Shore </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Shane Kerr </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Ayden Federline
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Susan Kawaguchi (leadership liaison)
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Mark Svancarek
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Daniel Nanghanki
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">•<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Marina A. Lewis
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">With respect to RDAP, this WG may recommend that RDAP be used to implement policy, but any policy needs requiring RDAP extension will need to be relayed to the IETF for consideration.</span></div>
<div class="yiv0034955033MsoNormal" style="margin-left:.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action Item #1:</span></b><span style="font-size:11.0pt;"> The sign-up sheet will be updated to reflect the following volunteers will review these documents
to extract possible requirements:</span></div>
<div class="yiv0034955033MsoNormal" style="margin-left:.25in;line-height:16.0pt;">
<span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Additional GAC-suggested documents – Vicky Sheckler</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Dissenting Report from Stephanie Perrin – Ayden Ferdeline</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Where Do Old Protocols Go To Die? by Scott Hollenbeck – Stacie Walsh</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Building a Better WHOIS for the Individual Registrant – Stacie Walsh</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action Item #2:
</span></b><span style="font-size:11.0pt;">Staff to update draft Comment Tool to reflect noted change and circulate to WG for final approval within two weeks.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action Item #3:
</span></b><span style="font-size:11.0pt;">Staff to create a mailing list for the Problem Statement drafting team. Concise Problem Statement to be drafted by team for WG consideration.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><u><span style="font-size:11.0pt;">Task 9e: Outreach #2 - Incorporate additional Possible Requirements</span></u></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Possible requirements from Cross-Community RDS session were posted to mailing list, see:<br clear="none">
</span><a rel="nofollow" shape="rect" target="_blank" href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2016-June/000933.html"><span style="font-size:11.0pt;">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2016-June/000933.html</span></a><span style="font-size:11.0pt;"></span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">All additions suggested during Cross-Community RDS session to be added to the next draft of the WG’s ongoing Possible Requirements List after confirming with transcript</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Also expect to incorporate any additional Possible Requirements gathered during Outreach #2, as well as those to be extracted by WG members from documents identified during Outreach #1 (see above)
and suggested during this F2F meeting</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Additional possible requirements that are not already on the list will be added to Draft 4</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Draft 4 will be produced after Draft 3 triage effort has been completed</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">For a description of triage goals, see Task 11 approach</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><u><span style="font-size:11.0pt;">Finalize Task 11: Decide how and when the WG will try to reach consensus
</span></u></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">The proposed approach to reach consensus (v12) was reviewed by the WG, see:<br clear="none">
</span><a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/download/attachments/59648535/Possible%20approach%20to%20consensus%2024%20Jun%2016%20WG%20v12%20clean.docx?version=1&modificationDate=1466823237000&api=v2"><span style="font-size:11.0pt;">Possible approach to consensus
24 Jun 16 WG v12 clean.docx</span></a><span style="font-size:11.0pt;"> (24 Jun 2016)</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">There were no additional questions or concerns raised on items 1 & 2</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Questions were raised on item 3 (where to start deliberation) on Chuck’s proposal to start by identifying a subset of possible requirements “that would apply to the RDS in all circumstances“</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Chuck explained that the aim of item 3 was to commence discussions today on any possible requirements that may apply in all circumstances, regardless of users, jurisdiction, etc.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Should the WG consider sending regular questions to the GAC via the PSWG on some of the constitutional or data protection requirements that may apply in the different countries? Could help with the
research on this topic. This should not hold up deliberations of the WG. Is that information needed now, if we design a system that respects the laws of each land, that would need to be dealt with in the implementation phase. The possible requirements could
say something like 'the system would allow for respecting the laws of each country’ which would translate in the implementation phase to a system that would accommodate this and where this information will be needed. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Should be cognizant of possible legal requirements when developing possible requirements, but recognize that these may be dealt with in the implementation phase. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Are there certain requirements that would apply in all circumstances and which the WG would agree with? Meeting participants brainstormed this question with the following suggestions:</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to comply with international standards and legislation - for example UN Law on corporate social responsibility which includes a whole chapter on human rights, International convention for
data protection & privacy which has been signed by all Council of Europe countries and Turkey and Uruguay. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Registration data collection needs to reflect necessity, proportionality, & be purpose bound - 108 countries that currently have data protection / privacy legislation which are expressed as principles.
This may not be a universal requirement as it is not necessarily subscribed to by all countries. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.5in;line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Wingdings;"><span style="">§<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Discussion: Does this apply in all circumstances? At high level yes, but would need more definition on what it means in practice.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Must prevent leaks of RDS information
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.5in;line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Wingdings;"><span style="">§<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Discussion: If all information were publicly available then would no leaks be possible? No, there is some information related to the system itself which you do not want to see public, for example,
ID and password or information enabling corruption of the database. Change to: Ensure system security and secure administration. May need to provide examples to broader community. May need to differentiate between system and user security?</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to be a properly-designed secure, stable, and resilient system</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Registration data elements must include domain name and its status</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to be resilient against single point of failure (e.g., Backup of information)</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS must provide the name of the registrant, and a physical address and email address for the registrant that should be accurate and contactable</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to collect registrar name</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to be accessible for purposes identified</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.5in;line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Wingdings;"><span style="">§<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Discussion: Elements of security and administration would need to be in place to accomplish this (see also earlier requirements).
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to include name server information</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.5in;line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Wingdings;"><span style="">§<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Discussion: Does this need to be in the RDS? The information is already available in the DNS and you do not need a name server to registrar a domain name.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to include standard information that is required for registrars to meet contractual obligations such as domain name registration transfers</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to support IDNs</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs to avoid out of sync information between different systems that may interact or contain the same information (e.g. DNS and RDS)
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="margin-left:1.0in;line-height:16.0pt;">
<span style="font-size:11.0pt;"><span style="">o<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">RDS needs informed consent - Individual consent concerning information that is collected as well as options for redress</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">After the WG discussed the above possible requirements, the question was asked:<br clear="none">
<i>Should the WG first deal with the policy and then system requirements? If so, how?</i></span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">It was suggested that the WG start by examining use cases - talk about users, their purposes, the data involved, and privacy impacts at a principle level, separate out the principles from the actual
data to be collected and the system requirements. Continue to refine each use case until enough use cases have been considered to understand the purpose of registration data. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Expert WG took a similar approach, by starting with use cases. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">The WHOIS 2007 Task Force also examined use cases, should consider those as well.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Attendees agreed that there was a need to find an approach that is efficient for deliberating on possible requirements and discussed whether the use case approach would facilitate this.
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">How to ensure that a sufficient set of use cases are identified? Does the approach presuppose that information currently collected will continue to be collected? Would the use case approach prevent
starting from a clean slate? </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Note that use cases examined could include those that shouldn’t be a valid use case under a next generation RDS. Need to be careful on how use cases are defined - shouldn’t be about specific business
models. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Consider splitting use cases to examine both user and technical requirements – but need to be careful not to start designing the system. Need use cases to focus on policy requirements, which may
include some high level technical requirements. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Need to consider possible constraints on the use of the data - in some jurisdictions data can also be used for previously agreed upon cases</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Use cases are not a one-to-one relationship to a solution that is then implemented. Broad concepts will come forward from use cases such as cases that could be supported by gated or non-gated access.
The same solutions may apply to other uses cases, even those that may not have been identified yet. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Do we need to come to rough consensus on “purpose” before looking at use cases?
</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Starting with “purpose” is key to making progress.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action Item #4:</span></b><span style="font-size:11.0pt;"> Circulate EWG statement on purpose that was originally drafted by Stephanie as an example and possible
starting point for this WG to answer the question of “What is the purpose of collecting, maintaining, and providing access to registration data?”</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Avoids repeating work that has already been done - that doesn’t mean that work is accepted as is, but at least it provides a starting point. </span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Identifying use cases does not mean endorsing that case - it may actually do the opposite (e.g. not a use that the system should facilitate). A spectrum of use cases (from permissible to illegal)
were also identified as part of the EWG’s analysis of use cases.</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">There was no disagreement among meeting participants to approach deliberations by beginning with a statement of Purpose.
</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action Item #5:</span></b><span style="font-size:11.0pt;">
<i>All WG members are asked to review F2F meeting recordings Part 2 and/or transcript Part 3 to ensure that all WG members are up to date with the discussions that took place in Helsinki.</i></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action item #6</span></b><span style="font-size:11.0pt;">: Leadership team to update Task 11 item 3 to reflect direction given in this meeting to circulate
the EWG report’s Purpose statement as an example and pursue use case methodology as a possible starting point prior to deliberating upon individual possible requirements.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><b><span style="font-size:11.0pt;">Action item #7:</span></b><span style="font-size:11.0pt;"> After listening to recording or reviewing transcript of F2F discussion of Task 11, WG members are
asked to review/comment on updated Task 11 approach by 7 July, in preparation for further discussion and finalization during the 12 July WG call.</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">4. Confirm Action Items, Next Steps, Next Meeting</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoListParagraphCxSpFirst" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">No WG meeting week of 3 July</span></div>
<div class="yiv0034955033MsoListParagraphCxSpMiddle" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Next WG meeting will be 12 July 16.00 UTC</span></div>
<div class="yiv0034955033MsoListParagraphCxSpLast" style="line-height:16.0pt;">
<span style="font-size:11.0pt;font-family:Symbol;"><span style="">·<span style="font:7.0pt;">
</span></span></span><span style="font-size:11.0pt;">Next steps and call agenda to be circulated to WG mailing list</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><u><span style="font-size:11.0pt;">Meeting Materials:</span></u></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">RDS PDP WG Wiki:
<a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/x/rjJ-Ag">https://community.icann.org/x/rjJ-Ag</a></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">WG Email Archive:
<a rel="nofollow" shape="rect" target="_blank" href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg">http://mm.icann.org/pipermail/gnso-rds-pdp-wg</a></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">Work Plan:
<a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/x/oIxlAw">https://community.icann.org/x/oIxlAw</a></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">SO/AC/SG/C Outreach and Inputs:
<a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/x/pYxlAw">https://community.icann.org/x/pYxlAw</a></span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">Phase 1 Documents:
<a rel="nofollow" shape="rect" target="_blank" href="https://community.icann.org/x/p4xlAw">https://community.icann.org/x/p4xlAw</a>, including</span></div>
<div class="yiv0034955033MsoNormal" style="line-height:16.0pt;"><span style="font-size:11.0pt;">Initial List of Possible Requirements (10 June 2016)</span></div></div>
<div class="yiv0034955033MsoNormal"><span style="font-size:11.0pt;"> </span></div>
<div class="yiv0034955033MsoNormal"><span style="font-size:11.0pt;"> </span></div>
</div>
</div></div><br><div class="yqt1297441308" id="yqt85213">_______________________________________________<br clear="none">gnso-rds-pdp-wg mailing list<br clear="none"><a shape="rect" ymailto="mailto:gnso-rds-pdp-wg@icann.org" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br clear="none"><a shape="rect" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></div><br><br></div> </div> </div> </div></div></body></html>