<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-2"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML-ként formázott Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Buborékszöveg Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;
color:black;}
span.HTML-kntformzottChar
{mso-style-name:"HTML-ként formázott Char";
mso-style-priority:99;
mso-style-link:"HTML-ként formázott";
font-family:Consolas;
color:black;}
span.BuborkszvegChar
{mso-style-name:"Buborékszöveg Char";
mso-style-priority:99;
mso-style-link:Buborékszöveg;
font-family:"Segoe UI",sans-serif;
color:black;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.E-mailStlus23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.E-mailStlus24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
p.BalloonText, li.BalloonText, div.BalloonText
{mso-style-name:"Balloon Text";
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;
color:black;}
span.E-mailStlus27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.E-mailStlus28
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:255676101;
mso-list-template-ids:1462153522;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:908658877;
mso-list-template-ids:-500643434;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:1660033697;
mso-list-template-ids:-1802590532;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3
{mso-list-id:1754886355;
mso-list-template-ids:1454380492;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4
{mso-list-id:1764455766;
mso-list-template-ids:1993920488;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5
{mso-list-id:1993563484;
mso-list-template-ids:-967943514;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6
{mso-list-id:2000108209;
mso-list-template-ids:-1161376282;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=HU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Sorry for not being able to attend the call, but I am continuously in meetings…However I just wanted to support the idea of talking first on the purpose of the WHOIS. I share the views stating that it’s hard to speak about any data, set of data without setting the purpose of the whole data processing (ie. WHOIS here). Even if we started with defining the data requested we will surely bump into the question: For what purpose?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Peter<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] <b>On Behalf Of </b>Stephanie Perrin<br><b>Sent:</b> Friday, February 26, 2016 6:55 AM<br><b>To:</b> gnso-rds-pdp-wg@icann.org<br><b>Subject:</b> Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>As I said somewhat facetiously during the chat, you should have seen the dissents I refrained from emitting....the EWG did not start from a de novo position. Given the repeated failure to even define the purpose of WHOIS (see the SAC Blind men and the elephant report) we do need to take a de novo approach. The EWG report provided good analysis on some issues, and some new approaches. It certainly did not solve all the problems or deal with all the issues. Brace yourself for me repeatedly pointing these lacunae out, as I know a lot more about all the issues than I did when I started with the EWG....<br>Stephanie Perrin<o:p></o:p></p><div><p class=MsoNormal>On 2016-02-25 20:27, Gomes, Chuck wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Please see my responses below Kathy.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Chuck</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'> Kathy Kleiman [<a href="mailto:kathy@kathykleiman.com">mailto:kathy@kathykleiman.com</a>] <br><b>Sent:</b> Thursday, February 25, 2016 5:18 PM<br><b>To:</b> Gomes, Chuck; <a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b> Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Hi Chuck, <br>I'm sorry, but I don't understand the starting point of the draft work plan. It says that the "Bulk of Work in phase 1 relates to recommending requirements for Registration Directory Services." After review of the EWG, it states that we will "Develop a comprehensive list of possible requirement [sic] (without a debate) as a first step." <o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] That statement is an assumption based on the WG charter. Do you not think that the WG’s main task, which will consume most of our time, will involve most of our time? If not, please show me what I am missing in the charter.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>It seems to me that the first step should be evaluating the data collected by the registrars for registration purposes. The next step should be evaluating the purposes for which that data is collected. The third step should be seeking out additionally purposes for which folks not registrars would like to use the data. The fourth step should be to determine whether the information could legally be made available for those additional purposes, and whether those additional purposes are even desirable or useful (or are there dangers and concerns?)<o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] The EWG already spent countless hours evaluating the data collected and had multiple opportunities for public comment on their work. Are you suggesting that we should repeat that work? The first of the eleven questions deals with users and purposes so your suggested first two steps seem to be covered by the WG deliberations on the first charter question. In other words, it seems to me that the proposed approach covers your first two steps at the beginning like you are suggesting. The only difference is that the approach suggests identifying possible requirements first.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>Jumping straight into "Develop a comprehensive list of possible requirements (without debate)" skips the whole analysis (above) that I understand is necessary under EU nations' laws (and the many other countries with data protection laws) and jumps straight into -- "who wants this data?! Get your data here!"<o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] The analysis will not be skipped. It will happen when we do our deliberation.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>For the draft work plan, section 3 below ("Review and discuss draft work plan"), I would start with these opening bullet points:<br>- what domain name registration data is collected and for what purpose? <b><i><span style='color:#1F497D'>[Chuck Gomes] </span></i></b><span style='color:#1F497D'> First area of deliberation.</span><br>- what specific laws and restrictions limit the re-use or secondary use of this domain name registration data? (data gathering, legal analysis section)<b><i><span style='color:#1F497D'>[Chuck Gomes] </span></i></b><span style='color:#1F497D'> This will happen in our deliberation on each possible requirement.</span><br>- what additional uses would people like to use the domain name registration data and why?<b><i><span style='color:#1F497D'>[Chuck Gomes] </span></i></b><span style='color:#1F497D'> First area of deliberation.</span><br>- Outreach to the Supporting Organizations, Advisory Committees and outreach to the greater Internet Community<b><i><span style='color:#1F497D'>[Chuck Gomes] </span></i></b><span style='color:#1F497D'> We will do this multiple times during our work.</span><br>- Deliberations as to whether these additional uses are legal, possible, optional -- and what the costs and benefits are of providing this data for the secondary purposes that people are seeking it. <br><br>On a related note, I used to program large-scale databases on Wall Street and respectfully submit that the term "requirements" in the first 3 bullet points of section 3 is being used incorrectly (or confusingly) as a technical matter. Until we do the detailed analysis of the key issues of what data collected, its primary purpose, sought secondary use, proportionality, etc, we can't possibly know or lay out the "requirements" we are seeking for the new Registration Directory Services. "Requirements" is best used as the term for the features we intend to build into our new RDS system. We are nowhere near the "requirements" stage yet -- we are at the preliminary data gathering, use and user analysis, legal review, and other preliminaries. Shaping, scoping, defining and describing the "requirements" of the new system will come later. What other term can we use? <o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] We are using the term from the charter. I agree that it may fit better in some cases than others but I suggest we don’t get too hung up on terminology. If we can improve it, fine, but let’s not spend too much time debating terminology until it becomes critical, i.e., when we actually get into our deliberation.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br><i>To the other question of the WG, what "rough categories of expertise" are needed:<br></i>I would add groups that specialize in free speech, freedom of expression, human rights, domestic violence, international journalist organizations, and groups that specialize in political oppression. It is these groups that know intimately who is being harassed, stalked and even killed based on Whois data -- and many of them participated in the last public comment held by the Proxy/Privacy Accreditation Working Group. They are definitely reachable and in tune with our issues. <o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] We are way past the 24-hour deadline on this. If the membership review team has not finalized the categories yet, they of course can take your input into consideration but it is possible they have already completed the list. </span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>I deeply apologize for missing the meeting this week. We had a death of a family friend and given daytime commitments, I could not participate in the late-night call.<o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] Please accept my condolences.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>Tx for your review. <br>Best,<br>Kathy (Kleiman)<br><br><br>On 2/25/2016 9:57 AM, Gomes, Chuck wrote:<br><br><br><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks for the feedback Kathy. I will let those who were on the EWG respond to what happened after London but I did insert some personal responses below.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Chuck</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'> <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] <b>On Behalf Of </b>Kathy Kleiman<br><b>Sent:</b> Thursday, February 25, 2016 9:04 AM<br><b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b> Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Hi Chuck,<br>Tx you for the reminder for the last call of comments. I would like to raise concerns about some of the items in the work plan. My objections have to do with the focus of the<i> </i>"Outline of Approach for Phase 1" extensively on input from the EWG Final Report. The work plan, as circulated (particularly under its "Assumptions") implies an understanding and acceptance of the EWG Final Report that never existed. Let me explain<b> </b>(and invite my EWG friends and all present at that time) to supplement this record:<o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] Please tell me why you think there is an acceptance of the EWG Final Report? No such assumption was made by the Leadership Team. As you share below, the intent is for it to be a starting point.</span></i></b><o:p></o:p></p><p class=MsoNormal><b><br><br>Background: </b>the EWG Final Report was greatly changed from the interim to the final draft. Not a little bit, but significantly, substantively, clearly changed. Dozens of new pages were added; entirely new analysis and recommendations. The final Report was difficult, even impossible, to understand. Long public sessions were held at the ICANN meeting in London where speaker after speaker raised issues, concerns and questions, questions, questions. There were so much ambiguity in the text, so many sections that were unclear, so many cross-references that were not complete that even those of us who have been in this field for many years found it impossible to understand specifically what was being recommended and why. Further, there were major questions raised about the large amount of data being collected and retained, indications of nearly unlimited access for certain types of users, and many more concerns. <i>There were so many questions that commenters at the microphone agreed we/they could not even start a full and substantive critique of the Final Report because it is unclear even what was being recommended on certain key and substantive points. The essence of drafting rules and technical policy is, of course, clarity and we agreed in these public session in London that it was lacking in this Final Report.** Answers were promised; answers never came. The EWG Final Report remains an ambiguous, unclear document. <br><br></i><b>No Final Public Comment: </b>Unfortunately, despite major and extensive changes between the interim and final drafts, and ICANN precedent itself, the EWG Final Report never went to public written comment. (In all my time in ICANN, which is a lot, I have never seen a final report which did not go to public comment - particularly a final report as complex, difficult, convoluted and significantly-changed as this one.) There was no final comment period for this report -- just a promise that no group would ever accept the Final Report as an absolute starting point; and that all future groups working with the EWG Final Report would know that it never received a final review, never received consensus, and was never even understood by those critiquing it in the public sessions.<b> <br><br>Dissent: </b>Further, the EWG Final Report received a strong dissent from the only member of the EWG with a data protection background - the person who was a key drafter of the Canadian Data Protection Report. Her <o:p></o:p></p><p class=MsoNormal>issues and concerns have, of course, never been addressed because the EWG Final Report never went out for that final round of public comment and final round of revisions. <o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] I fully expect and encourage the dissenter (Stephanie) to add possible requirements that address her concerns.</span></i></b><br><b><br>Accordingly: </b>calls for acceptance and reliance on the EWG Final Report should be much more carefully worded and limited in the Work Plan than they are now. I know the Board wants us to refer it as a reference point and touch point, but not the only or exclusive starting point<b>. </b>The work plan has references to other sources other than the EWG Final Report, but what are they, where are they and who will find and summarize them? Given the speed we want to work, it is incumbent on the WG, at this early point in development, in this Work Plan, to determine what these other sources might be and how we can access them quickly, efficiently and effectively. I would like to request that the Work Plan include provisions for subteams to form and Staff to help find, use and summarize these other sources so that they will be available as quickly as the EWG Report (and noting that it may be difficult for members of the community to drop other work and write short White Papers.) But it is clear that we need to fairly and fully pull in the widest range of information and input at this critical point of Phase 1 -- the RDS Working Group richly deserves it! <o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>[Chuck Gomes] If you think the wording asks for acceptance and reliance on the EWG Final Report, please suggest alternative wording. Regarding other sources, many of them are identified in the EWG Report, in the Issues Report and I encourage WG members to identify other sources. Stephanie’s minority statement is one source already mentioned, although I consider it part of the EWG Report.</span></i></b><o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></i></b><o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>In my view, I see no need for writing white papers. What we will need though in the early parts of our work is for everyone to identify possible requirements so that we create as comprehensive a list as possible. That list will then be deliberated on by the WG to determine which ones we agree should be recommended.</span></i></b><o:p></o:p></p><p class=MsoNormal><br><br>Best, <br>Kathy (Kleiman)<br>p.s. In summary, I would like to ask Assumptions be modified to reflect the huge questions and concerns raised about the EWG Final Report in London, and the complete lack of any final comment period on a hugely and substantively-changed final report. I would also like to request that Outline of Approach to Phase 1 be modified to reflect a concerted effort of the WG, Leadership Team subteam(s) and Staff to identify, define and summarize the "sources other than the EWG Final Report" that will be used and what resources will be devoted by Staff to collecting and summarizing them for ease of use by the WG. <br><br>Best regards,<br>Kathy<br><br>On 2/24/2016 1:34 AM, Marika Konings wrote: <br><br><br><br><o:p></o:p></p><div><div><p class=MsoNormal>Dear All,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Please find below the notes and action items of today’s meeting. I would like to draw special attention to the following action items and deadlines associated with these:<o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo1'><b>Action item #1</b>: All to review categories identified by small team and provide feedback within 24 hours (see attached)<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo1'><b>Action item #4</b>: All to review work plan approach as has been circulated with the agenda and provide any comments / questions on the mailing list within 48 hours. (see attached)<o:p></o:p></li></ul><div><p class=MsoNormal>Please share any input or questions you may have with the mailing list.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Best regards,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Marika<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><b>Notes/Action items 24 February 2016 - Next–Generation RDS PDP WG Meeting</b><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><i>1. Roll call/ SOI</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo2'>Note, observers have read-only access to the mailing list and do not receive the call details. If you want to change your status, you can inform the GNSO Secretariat accordingly.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo2'>Members are required to provide a Statement of Interest in order to participate in the Working Group.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo2'>Updates to SOIs are requested at the start of every meeting.<o:p></o:p></li></ul><div><p class=MsoNormal>A<b>ction item #1</b>: Please complete / update your Statement of Interest if you have not done so yet. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><i>2. Review of WG membership & expertise update</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Small team has been discussing how to identify current level of expertise<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Identified a number of rough categories of expertise that is expected to be needed for this effort: Legal (IP, criminal, civil), Technical (Protocol development, Security, Audit), Data Protection, Operational (Registrar, Registries), Commercial/e-business, Non commercial/not for profit, government advisory, law enforcement (police, investigators, courts), individual internet user.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Proposal to put these categories into a zoomerang poll to allow for WG members to self-identify their expertise<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Small team would like to receive input on the categories identified and possible sub-categories<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Consider removing investigators as it can be considered part of 'police'. There are also other agencies that are involved in investigations, maybe that is why it has been identified as a separate category. Should investigators (non-government) be a separate category? This would include organisations like consumer organisations.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Security may not only be technical expertise, there may also be non-technical aspects to it. Consider having a security category that is not under the technical heading.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>DNS technical specialists should also be considered as a category<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Categories are intended to get a general sense of expertise available<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Consider updating law enforcement to public safety to capture a broader category of investigators?<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Should public defenders be added to the legal category? Might already be covered by legal/criminal?<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Consider a category for cybersecurity. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Experts can be invited to just join when a particular topic is discussed - not only looking at filling gaps in membership, but also identify specific support that may be needed in an expert capacity. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3'>Consider adding a category for WHOIS software / service developer<o:p></o:p></li></ul><div><p class=MsoNormal><b>Action item #1</b>: All to review categories identified and provide feedback within 24 hours<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><b>Action item #2</b>: staff to develop survey on the basis of the categories identified and request WG members to participate<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><b>Action item #3</b>: small team to review feedback received to the survey and identify whether additional outreach is needed based on the survey results. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><i>3. Review and discuss draft work plan approach</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Bulk of work in phase 1 relates to recommending requirements for Registration Directory Services<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Use EWG Final Report as starting point, as instructed by the ICANN Board. Substantial public input was provided and incorporated by this effort. Not restricted to the EWG Final Report, but an important starting point. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Develop a comprehensive list of possible requirement (without a debate) as a first step. Deliberations on each possible requirement will be the next step after developing this comprehensive list, including reaching consensus on whether requirements should be included or not.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Outreach to SO/ACs is expected during various stages of the PDP, periodically as needed. This outreach may take various forms, formal, informal. There is a requirement for formal input at the early phase of the process. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Interdependency of all eleven questions in the charter will main that the WG may need to go back and forth between questions. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>First five questions are critical as they are essential to responding to the foundational question of whether a new RDS is needed. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>No comment period held on the Final EWG Report. EWG Report expected to be starting point - not stopping there, just a first list of possible requirements that the WG is expected to add to.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Should purpose be defined before discussion uses? Purposes and uses are part of the charter which are expected to result in possible requirements (see question 1).<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Leadership team has started developing a first list of possible requirements - draft as a starting point for the full WG to review and add to. SO/AC/SG/Cs can also be asked to add to the list of possible requirements. Objective to have comprehensive list of requirements. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Once this comprehensive list is 'complete' (WG is of the view that all possible requirements have been added), systematic review of the requirements by the WG. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Deliberation of some requirements could be deferred to later phases, if deemed appropriate. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Following this work, the WG is expected to deliberate on foundational question: is a new RDS needed or can the existing WHOIS system be modified to satisfy the recommended requirements for questions 1-5. Answer to this question will determine subsequent steps. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Who will come up with costing based on the requirements identified? Is it possible to estimate costs until you get to phase 2 and 3? Might be possible to get a high level idea in phase 1, but you cannot do it thorougly until you get to phase 2 when the policies are identified. Phase 1 could identify what costs need to be measured while phase 2 may ballpark those. Cost impact expected across the whole eco-system. Impact assessment will be important question.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Outreach to SO/ACs may involve those groups to consult with their respective constituencies that may take more than 35 days. Smaller requests more frequently may facilitate feedback. All should be communicating regularly with their respective groups - bring feedback to the WG on an ongoing basis. If any request for input would be associated with a minimum 35 day timeline it would have a significant impact on the overall timeline.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Leadership team will work on the detail of the work plan based on the approach outlined and comments received.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Those on the call were supportive of the approach outlined. Provide opportunity for those not on the call to provide feedback on the approach. <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo4'>Leadership team would like to be able to send out a first cut of a work plan by the end of this week so it can be further discussed and reviewed during next week's meeting.<o:p></o:p></li></ul><div><p class=MsoNormal><b>Action item #4</b>: All to review work plan approach as has been circulated with the agenda and provide any comments / questions on the mailing list within 48 hours. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><b>Action item #5</b>: Leadership team to send out first draft of work plan by the end of this week.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><i>4. Discuss proposed outreach to SO/AC/SG/Cs to solicit early input</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo5'>Required to formally request input at early stage, minimum of 35 days response time. Considering asking for general input.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo5'>Request formal input shortly after ICANN meeting in Marrakech. <o:p></o:p></li></ul><div><p class=MsoNormal><b>Action item #6:</b> Leadership team to develop draft outreach message for WG review.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><i>5. ICANN meeting in Marrakech F2F meeting</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo6'>See <a href="http://doodle.com/poll/7f9h9spwwmys26c5">http://doodle.com/poll/7f9h9spwwmys26c5</a>. To date 46 expected to participate in person, 20 are planning to participate remotely and 5 are not able to attend.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo6'>See <a href="https://meetings.icann.org/en/marrakech55/schedule/wed-rds">https://meetings.icann.org/en/marrakech55/schedule/wed-rds</a> for further details.<o:p></o:p></li></ul><div><p class=MsoNormal><i>6. Confirm next steps and next meeting</i><o:p></o:p></p></div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo7'>Next meeting will be scheduled for Tuesday 1 March at 16.00 UTC <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo7'>Chuck will not be available for the next meeting - Susan Kawaguchi has volunteered to chair the meeting on 1 March.<o:p></o:p></li></ul></div><p class=MsoNormal><br><br><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre><pre><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre><pre><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre></blockquote><p class=MsoNormal><o:p> </o:p></p></div></body></html>