<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>I support Sanas position on this. Stated more eloquently than I can.</div>
<div><br>
</div>
<div>-James</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of Sana Ali <<a href="mailto:sana.ali2030@gmail.com">sana.ali2030@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday 15 June 2016 at 20:50<br>
<span style="font-weight:bold">To: </span>"Gomes, Chuck" <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [gnso-rds-pdp-wg] Possible approach to consensus in deliberation of possible requirements for RDS PDP WG<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
My comments on Proposal 2-
<div class=""><br class="">
<div class="">I believe we should go ahead and limit the initial report to three fundamental questions (privacy, data, users/purposes), and add a new second initial report on remaining fundamental questions (accuracy and gated access). </div>
<div class=""><br class="">
</div>
<div class="">The cons for doing so seem largely speculative. Ordering our work is not going to "impede attempts to balance privacy, access, and accuracy issues as requested by board and charter”. It simply allows us to chew off the amount of work we can handle
at any one given time. Please keep in mind that different parts of the process will naturally weigh differently on the different stakeholders involved in this working group. To allow us to proceed incrementally lets us decide how much work we are going to
be able to do well, at any one given time. It also gives us all the opportunity to play a stronger and more thorough oversight role at each step. So, ultimately, no-one should be disadvantaged by proceeding in this manner.</div>
<div class="">2 is not so much less than 3 public comment periods, especially if it makes our work a little bit easier to handle, and allows us to look at the issues in a more thorough fashion. Quality over quantity should be the obvious choice here. And dividing
the work this way, will allow us to do a better job at looking at each of the fundamental questions set by the WG charter. We are not asking to ignore some of the task, we are simply choosing to go about it in an intuitive order.</div>
<div class=""><br class="">
</div>
<div class="">I support the proposal.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Warm wishes,</div>
<div class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Sana</div>
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 15, 2016, at 3:21 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com" class="">cgomes@verisign.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Per Action Item #3 from yesterday’s WG call, attached is a slighted revised 'possible approach for consensus in deliberation of possible requirements for RDS PDP WG'. This version was revised from the one presented in the WG call; edits were made and comments
inserted in an effort to reflect the WG discussion that occurred in the meeting. Given on-going list discussion, all WG members are encouraged to review and comment with an aim to 'finalise' the approach during next week's meeting. To aid in discussion, below
is a recap of two proposals made during yesterday’s WG call with some pros & cons.<br class="">
<br class="">
<b class="">Proposal 1: When indicating level of support for possible requirements within initial report(s), identify whether there is support or lack of support by each SG/C.<br class="">
<br class="">
</b>Pros: Communicate any formal statement(s) of support in context with draft recommendations.<br class="">
Cons: SG/C positions likely to be formalized after initial report, during public comment.<o:p class=""></o:p></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Personal comment from Chuck: The attached approach does not specifically address this so I believe that we could deal with this once we get to that point; if I am correct, we do not need to resolve this now.<br class="">
<br class="">
<b class="">Proposal 2: Limit initial report to three fundamental questions (privacy, data, users/purposes), adding a new second initial report on remaining fundamental questions (accuracy and gated access) prior to the required initial report at conclusion
of Phase 1 to address (at minimum) all 11 charter questions.<br class="">
<br class="">
</b>Pros:<o:p class=""></o:p></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>Allows
WG to make incremental progress by focusing on fewer questions and possible requirements<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>There
are only so many issues we can work on at once, and to stick with the big 3 provides a focus and direction.<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>Allows
additional/earlier opportunity for public comment<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>It
may be premature to consider accuracy and gated access when we have not yet established if there is a basis for collecting registration data in the first place.<b class=""><o:p class=""></o:p></b></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Cons:<o:p class=""></o:p></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>Delays
deliberation on inter-dependent questions<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>May
impede attempts to balance privacy, access, and accuracy issues as requested by board and charter<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>Adds
overhead for WG and community (additional workload associated with running two vs. three public comment periods (both from a staff as well as WG perspective as well as impact on the overall timeline)<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span>There
is a risk of public comment fatigue so the WG will need to give consideration to whether there are any downsides to having three public comment periods on the same topic vs. two.<b class=""><o:p class=""></o:p></b></p>
<p class="MsoListParagraph" style="margin: 0in 0in 10pt 0.5in; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in;">
<span style="" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 10pt; line-height: 15.333332061767578px; font-family: Arial, sans-serif;" class="">There’s
a reason the charter was written as is and to change it unwinds the charter without the benefit of the thoughtful work and deliberations that went into it.</span><br class="">
<br class="">
<b class=""><o:p class=""></o:p></b></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Personal note from Chuck: I tried to include the pros and cons from various people both in yesterday’s meeting and<span class="Apple-converted-space"> </span><b class="">on the</b><span class="Apple-converted-space"> </span>list since then. If I missed some,
please communicate them. Also, I encourage others to suggest additional pros and cons on the list.<o:p class=""></o:p></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Thanks to those who have begun to share their views on these proposals and expand upon possible pros/cons. You are all encouraged to continue exchanging views to reach agreement on a possible approach for deliberation that can lead this WG to consensus agreement
on all of the questions we must answer during Phase 1.<b class=""><o:p class=""></o:p></b></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt; line-height: 16.866666793823242px; font-size: 11pt; font-family: Calibri, sans-serif;">
Chuck<o:p class=""></o:p></p>
</div>
<span id="cid:1C17BBF6-44A7-4581-97A7-8959FDD8AF0E@hitronhub.home"><Possible approach to consensus in deliberation of possible requirements 13-Jun 16 v5.docx></span><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">gnso-rds-pdp-wg
mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">gnso-rds-pdp-wg@icann.org</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</span>
</body>
</html>