<html 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=utf-8">
<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:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:19480071;
mso-list-template-ids:-1900351816;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:397632225;
mso-list-template-ids:1579424726;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:637802754;
mso-list-template-ids:1156587826;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3
{mso-list-id:806776049;
mso-list-template-ids:1586499708;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4
{mso-list-id:1497498678;
mso-list-template-ids:1761406668;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5
{mso-list-id:1594776518;
mso-list-template-ids:-429343078;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
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:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6
{mso-list-id:1667243331;
mso-list-type:hybrid;
mso-list-template-ids:-1752260934 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l7
{mso-list-id:1792556822;
mso-list-type:hybrid;
mso-list-template-ids:-317013982 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l7:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l7:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l7:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l8
{mso-list-id:1932742421;
mso-list-template-ids:1192894688;}
@list l8:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l8:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l8:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l8:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l9
{mso-list-id:2120642541;
mso-list-type:hybrid;
mso-list-template-ids:834976982 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l9:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l9:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l9:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l9:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l9:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l9:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l9:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l9:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l9:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l10
{mso-list-id:2146583835;
mso-list-template-ids:-1396407158;}
@list l10:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l10:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l10:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l10:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4 lfo12
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4 lfo13
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5 lfo13
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:o;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level4 lfo14
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5 lfo14
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:o;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level6 lfo14
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4 lfo15
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5 lfo15
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:o;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level6 lfo15
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Moin!<o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Please find below the notes and action items from the three EPDP IDNs sessions in Hamburg.<o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Here are the wiki space pages for all three sessions:<br>
Session 1: https://community.icann.org/x/KgGWDw<br>
Session 2:</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> <span style="color:black">
https://community.icann.org/x/LAGWDw<o:p></o:p></span></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Session 3: https://community.icann.org/x/LgGWDw<o:p></o:p></span></p>
<p style="margin:0in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Best Regards,<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p style="margin:0in;border:none;padding:0in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Ariel, Steve, and Dan <o:p></o:p></span></p>
<p style="margin:0in;border:none;padding:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 1 ACTION ITEMS<o:p></o:p></span></u></i></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l6 level1 lfo6">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Limited the text for the definition of Source Domain Name by linking to the recommendation, to avoid redundant or contradictory text.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l6 level1 lfo6">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Revise definition to ensure adherence of the same entity principle and make clear that the disposition value is a part of the definition.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p><span style="text-decoration:none"> </span></o:p></span></u></i></b></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 1 NOTES<o:p></o:p></span></u></i></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Roll Call and SOI Updates </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">None<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Welcome and Chair Updates </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l8 level1 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Started consensus call on Phase 1 recommendations and today is the deadline. Heard back from registrars and ALAC. No response is assumed to mean support. Expect to hear from the GAC as well. Once
midnight hits, it means we have hit an enormous milestone and will deliver the Final Report to the Council no later than 9 Nov.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l8 level1 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Goal for sessions at ICANN78 is to make progress on Phase 2 questions.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Continued Discussion of Source Domain: D4 </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 4: Refresher - Source Domain Name<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 5: Open questions remain. Question 1: Should there be one source domain name per gTLD?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Preliminary Agreement is that yes, there should be one source domain identified per gTLD.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 6: Example shows that the valid labels can differ between each gTLD, and a given variant.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Persian, Arabic, Urdu use the same script, but languages might not use the same character set. Otherwise, no objections to the preliminary agreement.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 7: Question 2: Must the source domain name be register?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Preliminary Agreement: The source domain name must be registered but may or may not be
<u>activated</u>. No objection to the preliminary agreement.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 8: Michael B proposal - It should be possible to delete or change a source domain name as long as its active variant domain names remain allocatable.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 9: Question 3: Can a source domain name be changed or deleted?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Preliminary Agreement: No need to prescribe policy recommendation in response to this question. <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Certain attributes of a domain name cannot be edited. The string in particular cannot be edited. It must be deleted and re-registered. If the source is deleted, the rest of the variants should also
conclude their lifecycle. Essentially, there should be no remnants from the variant set.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 10: Source Domain Name and Variant Domain Set are suggested items to be included in the Glossary. Definitions are suggested and were read out to the team during the meeting. <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion to add: “should be at the second-level (or levels for which the registry provides registration for)”. Some concern that the recommendations have been limited to the second level.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion that the recommendation should be limited to the second level since the contracts generally do not prescribe actions for the third level. Third level and beyond, if allowed, are generally
up to the registrant to manage.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Agreement with this comment and belief that this question is actually out of scope. IDN tables are actually not even required at the third level and beyond. <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Confirmation that the text related to the registrant and sponsoring registrar jointly identify the primary source domain is also captured as a recommendation.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l5 level2 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion to remove the last sentence since it’s also captured in the recommendation. Could also reference recommendation for clarity and consistency. <o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Concern/question: Are we creating rules beyond the extent of IDNs? There are generally not variants for non-IDNs.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion that the recommendations and definitions must be consistent. Agreement that this is indeed important.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Action Item:
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Limited the text for the definition of Source Domain Name by linking to the recommendation, to avoid redundant or contradictory text.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the Variant Domain Set definition, it is currently limited to the primary gTLD. Would it be extended to variant gTLDs? It would seem that this definition should be consistent with the preliminary
agreement [add reference to agreement]<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Might need another layer to connect variant domain sets across gTLD variants. This coherence is needed to help ensure the same entity principle is applied across the gTLD variants.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The definition is not clear whether or not the disposition values are a part of the set.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Clarified that the top-level definition does in fact include the disposition value, so there might be a benefit to be consistent.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question whether the disposition terminology is the same for top-level and second level. Confirmation that the terminology is consistent.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion that the definition should include domain names across all of the variant gTLDs, which would aid in the issue of ensuring same entity across the variant gTLDs.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Action Item:</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> Revise definition to ensure adherence of the same entity principle
and make clear that the disposition value is a part of the definition.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Identifying the Same Registrant: C3, C3a </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">CPH TechOps was requested to provide a presentation on this topic.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 12: Preliminary Recommendation 2: The “same entity” principle applies to the activation of future variant domain names. This means that all allocatable variant domain names from a variant domain
set must be activated or withheld for possible allocation only to the same registrant at the same sponsoring registrar.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 13: Context about charter questions C3 and C3a<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 14: Domain Name Registration flow and parties involved.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A person or entity wanting a certain domain name goes to a registrar, which communicates with the registry (via EPP). The EPP command is domain create, which includes the domain name and the required
registrant information. This command is a billable transaction.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l10 level2 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The result is either a confirmation or an error output. If successful, the entry gets added to the database and registration data server.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l10 level2 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For variant activation (not necessarily registration, since it might not require an EPP command), it could be a create command (which would be billable) or an update command (which would not be billable).<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l10 level1 lfo5;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Need to consider resellers, who might not be able to easily determine or enforce same entity rules who are in some ways, like a registrant in terms of information known. Registrar sees the reseller
contacts, not necessarily for the ultimate registrant.<o:p></o:p></span></li></ul>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="vertical-align:baseline;border:none;padding:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 2 ACTION ITEMS<o:p></o:p></span></u></i></b></p>
<ul style="margin-top:0in" type="disc">
<li style="margin-top:0in;margin-bottom:0in;margin-left:-.25in;mso-list:l9 level1 lfo10">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Develop a response to this charter question. There will not be a recommendation to prescribe a mechanism.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></li><li style="margin-top:0in;margin-bottom:0in;margin-left:-.25in;mso-list:l9 level1 lfo10">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Consider getting data about usage of ROID, for inclusion in rationale.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p><span style="text-decoration:none"> </span></o:p></span></u></i></b></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 2 NOTES<o:p></o:p></span></u></i></b></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For resellers, this question is likely relevant for the next part of our conversation.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">RAA already has provisions about responsibilities of registrars vis a vis their resellers. <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question about who is maintaining the RDDS information and how to enforce the same entity requirements.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There are two instances of the RDDS information - at the registry and registrar level, with potentially different levels of data.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">How to enforce same entity requirements when the registration data is that of the registering party, not necessarily the registrant. The true registrant information is masked.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For privacy proxy and for masked registration data, the responsibility resides with the registrar to enforce.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 15: Refresher on ROID, which C3 suggested as the mechanism to enforce same entity requirements. All registry contacts, including domain objects, have a ROID.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Under GDPR, using the same ROID helps associate domains to a single entity.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 16: Refresher on ROID cont., which includes benefits and drawbacks.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The point about a ROID being assigned after domain creation is not accurate. The ROID is assigned before.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 17: Where we left off.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question 1: Should ROID be used to identify a registrant as the same entity?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ROID may be a reasonable mechanism, but contracted parties cannot be forced to use it<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question 2: In, what would be a better mechanism?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A joint responsibility between the registry and the registrar to identify the same registrant; The registry enforces the same registrar, and the registrar enforces the same registrant; Registry may
have to reuse contact object IDs <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question 3: Any additional info needed for this discussion?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION: RySG and RrSG members to take solicit input from CPH TechOps group regarding verifying the same registrant, also taking into consideration implications of resellers<o:p></o:p></span></li></ul>
</li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide has summarized CPH TechOps well. Reinforced that ROID is sometimes not available, such as in thin registries. The logic for determining what are variants resides with the registry. The relationship
with the registrant resides with the registrar. The CPH TechOps has talked about developing an EPP command to help with managing these transactions.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The registry identifies the variants.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level2 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The registrar ensures that the same entity check has completed.<o:p></o:p></span></li></ul>
</li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ROID currently is not fit for purpose. Could an extended ROID make sense? How to extend same entity across gTLDs?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Would the registrars be told how to enforce same entity, or do they just need to comply with the requirement? The suggestion from CPH TechOps is yes, enforce the requirement as they see fit.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Clarification: ROID is often sufficient, but in some cases, it is not. Therefore, it is problematic as a hard requirement.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">EPP creates interoperability. But EPP Extensions can be different across registries.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Data does not, or cannot, be transferred across registries. ROID does not translate across registries. <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Could consider noting that the ROID is sensible, in the context of implementation guidance. Should consider the impact of data escrow, or how the relational nature of the set is captured in the registration
data.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Data is escrowed at the registry and the registrar level, separately. All of the registration data will be escrowed.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Model 3 could have split responsibilities but define the allowable method(s).<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question about whether the use of ROID is directly linked to thick versus thin registration data.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question about how many registries do not use ROID? Which parties would not be able to meet a requirement to use ROID?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Even if all registries use ROID, registrars are not required to reuse ROID.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">COM, NET, JOBS are thin registries. The registration data policy will transfer the discussion to the minimum data set. ROID is not currently included in that minimum data set.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Could the recommendation be about the registries and registrars agreeing to develop a mechanism be a way to go? Currently, there are already two ways to establish variant domain names. The CPH desire
is to stay at the level of what is to be accomplished, but not prescribe the how.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There are a lot of moving parts, which makes it hard to recommend a singular way to enforce the same entity requirement. <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Noted that from a contractual point of view, there is no shared responsibilities. The registries and the registrars are independently responsible for their respective requirements. Registry would
enforce same registrar and the registrar would enforce same registrant.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If we end up with various mechanisms to enforce same entity, will it create consistency issues across the industry (e.g., EPP, data escrow). Within the single gTLD, there will only be a single model. <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Support to concentrate on just the goal of what is desired to be accomplished and leave details to implementation.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Concern that the same registrar requirement forces a registrant to use the same registrar for any variant domain names. If a registrant is displeased with a registrar, they are free to move to another
registrar.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">It does not seem that models 1 or 2 are the answers. However, the agreement is that the policy recommendation will be about the same registrar and same entity.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">During pre-delegation testing, this may create a more challenging testing environment for evaluation of the RO/RSP. This seems to be out of scope for the IDNs EPDP.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l4 level1 lfo7;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The question could be different for an RO versus RSP. RO would be asked how and the RSP would be asked to confirm that they can do it.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Action Item: Develop a response to this charter question. There will not be a recommendation to prescribe a mechanism.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Action Item: Consider getting data about usage of ROID, for inclusion in rationale.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Variant Domain Transaction Fees: D5 </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 21: Review of charter question. Similar to Phase 1 charter question.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Slide 22: Discussion Question: Once a source domain name is registered by a registrant, its allocatable variant domains may be calculated for potential activation. If the registrant decides to activate
one or more of its variant domains, should ICANN charge the $0.18 mandatory annual fee for each year of registration, renewal, or transfer of each activated variant domain?<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Noted that registries also pay a fee for <50k, as well as an incremental cost per additional DUMs.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The answer may be that it depends. There are two models to activate a variant, either use EPP create or EPP update command. The first would incur a fee, the latter would not. <o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Belief that the source and variants should all be treated as registrations, upon activation.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The variants will not always have the same lifecycle as the primary. How would that affect the billing cycle? This scenario would come from EPP create and would result in separate charges. The two
models exist now for registries.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggestion that the registrant usage should potentially dictate the fee structure. Concern about going into these aspects for our discussions.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There seems to be agreement that the source domain must be first. Currently, some registries choose to treat as create versus others that treat as updates. To dictate a single model now would change
the approach for existing registrants.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However, the existing registrations could be grandfathered if the EPDP wants to recommend a single approach.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Question about whether the Phase 1 recommendation would be inconsistent if the EPDP elects to keep the status quo (i.e., allow for variable treatment of create or update). The Phase 1 recommendation
seems to assume that each variant should be treated as an independent registration.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level2 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">It seems that create would be counted, but update would not. So, no inconsistency is created<o:p></o:p></span></li></ul>
</li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The intent could be inferred. If the usage is similar/interlinked, maybe it’s update? And if the usage is independent, maybe it’s created? Noted that the status quo is not documented, it is just
what is done. This EPDP could therefore enshrine the current practices.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We need to be careful to not infringe on current implementation models since registry models are built upon what is counted as a billable transaction.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l1 level1 lfo8;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Should our recommendation be at the high level, of what the goal is for the recommendation?<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 3 ACTION ITEMS</span></u></i></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Leadership will review the notes and transcript to best determine how to address Charter Question D5</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SESSION 3 NOTES<o:p></o:p></span></u></i></b></p>
<ul style="margin-top:0in" type="disc">
<li style="color:#172B4D;margin-top:8.0pt;margin-bottom:0in;mso-list:l0 level1 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Roll Call and SOI Updates <o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level1 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Welcome and Chair Updates <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The Chair welcomed everyone to the meeting and handed the mic over to GNSO Chair Sebastian Ducos for some remarks<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The GNSO Chair congratulated the EPDP team on achieving full consensus for the Phase 1 Final Report<o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The EPDP Chair thanked the GNSO chair and congratulated the team as well<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level1 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Continued Discussion of Source Domain: D4 <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff then introduced the topics for the day, including the continued discussion regarding the source domain.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff asked if there was any comment or question from the team, but there was no objection for the rationale updates for Preliminary Rec 5<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level1 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Identifying the Same Registrant: C3, C3a <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff described the updates to developing responses to the charter questions C3 and C3a. <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This received approval in chat from multiple team members<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level1 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Variant Domain Transaction Fees: D5 <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff described the preliminary recommendation to capture the agreement about mandatory annual fees for registration, renewal, or transfer for each REGISTERED variant domain name. Activated variant
domain names would not be charged the annual fee.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo11;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One team member commented that this might not be necessary. If a variant is not registered, then it doesn't get charged. They are not sure why it would have to be <o:p></o:p></span></li></ul>
</li></ul>
</li></ul>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo12;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair replied that they would like to view the language in the registrar and registry agreements regarding this as it might not matter if it is in or not in a variant domain set. “A domain name
is a domain name is a domain name”<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member commented in chat with the following excerpt from the registry agreement “The registry-level transaction fee will be equal to the number of annual increments of an initial or renewal
domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25”<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level6 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Taken from Article 6, 6.1 Registry-Level Fees: https://itp.cdn.icann.org/en/files/registry-agreements/nrw/nrw-agmt-html-21nov13-en.htm<o:p></o:p></span></li></ul>
</li></ul>
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another team member commented “situation where some registries are to pay for each variant in the set and some not - is going to be a huge issue” <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">They spoke about the possibility of angering regulators and tax agencies about this.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level6 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair mentioned they would like to get to an understanding where it doesn't matter if the registered domain is being used as part of a variant set or not. It should be treated equally<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A different team member questioned legal distinction between registration and activation<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair replied that registration is a specific process and that garners a fee being charged.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level6 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There is a need to clear up language regarding this<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The vice chair discussed the meaning of registration.<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">“If the domain name is used, will it trigger fees”<o:p></o:p></span></li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The vice chair continued, what are the use cases of activating but not registering?<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One team member discussed the process of reserved domain names <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level6 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If you change the property of a reserved variant, it should not incur a fee, they suggested.<o:p></o:p></span></li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo13;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The GNSO Chair discussed that Reserved Names are set aside for future registrations. If the name applied for is on this list of set asides, then the application fails.<o:p></o:p></span></li></ul>
</li></ul>
</ul>
</ul>
</ul>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:3.5in;text-indent:-.25in;mso-list:l0 level6 lfo14;background:white;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:#172B4D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#172B4D">They are not sure how this applies to this question.<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo14;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member posted: “if the result of activation is indistinguishable from the results of the activation - there is an issue in courts around the globe. it sounds pretty much like an allocation
without the registration. I think registered domains without NS records are still used , at least as a proof in UDRP or courts. fees are not applicable to reserved names. reserved might be different from allocation or can mean the same depends on the implementation.
fees are for registered domains”<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo14;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">They continued by talking about the process including escrow and accounting. For the reasons of potentially <o:p></o:p></span></li></ul>
</li></ul>
</ul>
</ul>
</ul>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level6 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another team member described the two labels that can be applied for registrars regarding this process in EPP: Escrow and Not a Domain Name (NADN)<o:p></o:p></span></li></ul>
</ul>
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair mentioned that this depends on the registry policy<o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member from the RySG mentioned that if the registry policy says that a variant domain name is the same as a regular domain name, then it goes through the regular reporting and billing process.<o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If variant domain names are qualified in a different way, then they won't trigger the billing process. <o:p></o:p></span></li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The same entity principal enforcement is also going to be key, per a different team member. <o:p></o:p></span></li></ul>
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair mentioned that there is a fee associated with each domain name. Leadership will research appropriate language that will future proof for variant domains at the second level. It should not
be convoluted and can probably be thought of as being straight forward. <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership will review the notes and transcript to best determine how to address Charter Question D5. <o:p></o:p></span></li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member asked whether or not ICANN receives a fee for every registered domain name. If yes, they believe there should be a fee. Whether or not a registry charges for variants, they should have
to pay for them. If they want to make it free, then it is a marketing expense.<o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A member of staff asked if there are different ways for domains to come into the DNS and serve content, but some can be billable and some cannot. <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="disc">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One way to instantiate a domain is to put an EPP create command in, which creates a billable transaction <o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level4 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another method is to activate a domain, it serves content, but it is not billable. <o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level5 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There is not alignment on this, but this seems to be the general understanding<o:p></o:p></span></li></ul>
</li></ul>
</li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair is not concerned with updating processes and lower-level information; they are concerned at the high level. <o:p></o:p></span></li><li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level3 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The GNSO chair delineated transaction vs domain names. ICANN will match the amount of domain names to what the registrars report. <o:p></o:p></span></li></ul>
</ul>
<li style="color:#172B4D;margin-top:0in;margin-bottom:0in;mso-list:l0 level1 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">AOB</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span>
<ul style="margin-top:0in;padding-inline-start:48px" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair thanked Dennis Tan for his fantastic work and efforts for this group subject matter.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff provided an update on the final reporting process, pursuant to the final deadline of 7 November for delivery to the GNSO council.<o:p></o:p></span></li><li style="color:black;margin-top:0in;margin-bottom:0in;mso-list:l0 level2 lfo15;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair announced they would like to finish all charter questions by the time they leave the Kuala Lumpur Face-to-Face meeting.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p><span style="text-decoration:none"> </span></o:p></span></u></i></b></p>
</div>
</body>
</html>