<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:x="urn:schemas-microsoft-com:office:excel" 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:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:12.0pt;
font-family:"Cambria",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:37052442;
mso-list-type:hybrid;
mso-list-template-ids:985672856 1173919078 397723342 1755625796 526690308 976274014 39729320 382609984 649257734 -510352350;}
@list l0:level1
{mso-level-number-format:roman-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:roman-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level4
{mso-level-number-format:roman-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:roman-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level7
{mso-level-number-format:roman-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:roman-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l1
{mso-list-id:480120669;
mso-list-type:hybrid;
mso-list-template-ids:949279078 -1642331400 1445122942 585418988 -1626453098 923155746 -1665217924 -2016126126 -522534176 -1869436834;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l2
{mso-list-id:493034282;
mso-list-type:hybrid;
mso-list-template-ids:-956248852 -202621362 -1251714314 549117818 -423330798 781237730 746617774 1125133556 -726656572 -1272544498;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3
{mso-list-id:710962332;
mso-list-type:hybrid;
mso-list-template-ids:-1196761702 544876698 279613870 1104549922 928555664 -267764376 947292070 1298429186 1163437142 412367672;}
@list l4
{mso-list-id:839392361;
mso-list-type:hybrid;
mso-list-template-ids:1017512294 46278326 -1721350686 1755867708 140158420 1062998842 16284728 -298053204 1054517656 -1407056288;}
@list l4:level1
{mso-level-number-format:roman-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:roman-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level4
{mso-level-number-format:roman-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level5
{mso-level-number-format:roman-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level7
{mso-level-number-format:roman-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level8
{mso-level-number-format:roman-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:right;
text-indent:-.25in;}
@list l5
{mso-list-id:857626051;
mso-list-template-ids:-1011820754;}
@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:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@list l6
{mso-list-id:1134297588;
mso-list-type:hybrid;
mso-list-template-ids:1556223742 1785769846 -494873462 1702367368 1899790962 -415085296 -746322530 -571564822 1475888898 -1949521458;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l7
{mso-list-id:1192260181;
mso-list-template-ids:157983916;}
@list l7: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 l7:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l7: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:Symbol;}
@list l8
{mso-list-id:1769154392;
mso-list-type:hybrid;
mso-list-template-ids:706764992 487759258 -1434427948 -420547008 -2087127198 354462766 -486777820 960684138 -543266838 -79505564;}
@list l8:level1
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l8:level2
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@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;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l9
{mso-list-id:2002732006;
mso-list-type:hybrid;
mso-list-template-ids:-559921822 590361838 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l9:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l9: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 l9: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 l9: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 l9: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 l9: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 l9: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 l9: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 l9: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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear TPR WG members,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please find below the brief notes and action items from today’s meeting. <b><i><o:p></o:p></i></b></span></p>
<p class="MsoPlainText"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></i></b></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The next meeting will be on Tuesday, 16 May at 1600 UTC.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Emily, Julie, Berry, and Caitlin<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEMS/HOMEWORK: None captured.<o:p></o:p></span></b></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Notes:<o:p></o:p></span></b></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Transfer Policy Review - Meeting #90</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposed Agenda</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">09 May 2023</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1. Roll Call & SOI updates<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2. Welcome and Chair Updates<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yesterday was the deadline of policy proposals for requirements related to informal resolution. There do not appear to be any new proposals
in the document. Therefore we are going to focus back on the questions in the charter, beginning with TEAC.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Steinar: CPWG/ALAC discussed the proposal for informal resolution and agreed it should be policy, but offered no specific language.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We are trying something different this week -- a more structured approach, including a chair proposal for the path forward based on inputs
to date. Perhaps we can take a few mins at the end of the call to collect feedback on the approach and whether folks are comfortable continuing this way for TEAC/TDPR questions.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Project Work Plan:
<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There were no new policy proposals for requirements related to informal resolution, so we will focus back on the questions in the charter,
beginning with TEAC.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Note that there are new meetings on the calendar for June and July. We will send a poll to gauge availability for August.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3. New proposals for policy requirements - non-emergency informal resolution (if any are received) (link to <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1vP9Q-EyhroHIrurlqrMWOl13_6yAQX2_y7vzteOV3fQ/edit?usp=sharing__;!!PtGJab4!5aOOi61IZ_IHzmUrvAHTPiVmJAQOz-qYYtlRRUmNgNUY0KTcoDe8DPC6xYYeqMG31UC0Q5hO7FPUKgN_aBAnE3yhoPdX8dVl7A$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1vP9Q-EyhroHIrurlqrMWOl13_6yAQX2_y7vzteOV3fQ/edit?usp=sharing__;!!PtGJab4!5aOOi61IZ_IHzmUrvAHTPiVmJAQOz-qYYtlRRUmNgNUY0KTcoDe8DPC6xYYeqMG31UC0Q5hO7FPUKgN_aBAnE3yhoPdX8dVl7A$">working
document [docs.google.com]</a>)<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No new proposals to discuss.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4. Status and next steps on Charter Questions F1-F7 (see <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1ejqMnKrN5Pnqyne6G4jHj-DPTfFLVidmeSDpyPM06eA/edit?usp=sharing__;!!PtGJab4!5aOOi61IZ_IHzmUrvAHTPiVmJAQOz-qYYtlRRUmNgNUY0KTcoDe8DPC6xYYeqMG31UC0Q5hO7FPUKgN_aBAnE3yhoPcrilDBQg$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1ejqMnKrN5Pnqyne6G4jHj-DPTfFLVidmeSDpyPM06eA/edit?usp=sharing__;!!PtGJab4!5aOOi61IZ_IHzmUrvAHTPiVmJAQOz-qYYtlRRUmNgNUY0KTcoDe8DPC6xYYeqMG31UC0Q5hO7FPUKgN_aBAnE3yhoPcrilDBQg$">TEAC
working document [docs.google.com]</a> and <b>attached slides</b>)<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question F1:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<i>f1) Is additional data needed to support evaluation of the effectiveness of the TEAC mechanism? If so, what data is needed?</i><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Status:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In written input RySG, NCSG, and BC have stated that it would be helpful to have additional metrics from registrars to support policymaking. In WG discussion, some support
was expressed for requiring registrars to track and report on TEAC activity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1061" style="width:795.75pt;border-collapse:collapse">
<tbody>
<tr style="height:19.35pt">
<td width="107" valign="top" style="width:80.25pt;border:solid #37761C 1.5pt;background:#6AA84F;padding:6.15pt .75pt 0in .75pt;height:19.35pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="954" valign="top" style="width:715.5pt;border:solid #37761C 1.5pt;border-left:none;background:#FDFDFD;padding:3.65pt .75pt 0in .75pt;height:19.35pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Recommendation to require registrars to track and report on specific data points related to the TEAC going forward, leveraging lists from RySG, NCSG, and BC.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:19.3pt">
<td width="107" valign="top" style="width:80.25pt;border:solid #37761C 1.5pt;border-top:none;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:19.3pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="954" valign="top" style="width:715.5pt;border-top:none;border-left:none;border-bottom:solid #37761C 1.5pt;border-right:solid #37761C 1.5pt;background:#FDFDFD;padding:3.65pt .75pt 0in .75pt;height:19.3pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Metrics will support understanding of how well the TEAC functions and any pain points, which will support future data-driven policy making.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:14.8pt">
<td width="107" valign="top" style="width:80.25pt;border:solid #37761C 1.5pt;border-top:none;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:14.8pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">To Discuss</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="954" valign="top" style="width:715.5pt;border-top:none;border-left:none;border-bottom:solid #37761C 1.5pt;border-right:solid #37761C 1.5pt;background:#FDFDFD;padding:6.2pt .75pt 0in .75pt;height:14.8pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Specific metrics that would be required.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Think the WG agrees that we need additional data and tracking, but need specifics. Confirmed that this is a good idea.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Talk about the things that would be most helpful to track at a high level.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We may be creating pieces of these metrics as we go.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Any thoughts from the WG on specific metrics to collect? Not a lot of discussion about this yet.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Questions F2/F3:
<o:p></o:p></span></b></p>
<p class="MsoPlainText"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">f2)
<b>The time frame (4 hours) for registrars to respond to communications via the TEAC channel
</b>has been raised as a concern by the Transfer Policy Review Scoping Team and in survey responses. Some have expressed that registries must, in practice, have 24x7 coverage by staff members with the appropriate competency to meet this requirement and the
language skills to respond to communications from around the world. <b>Is there merit to concerns
</b>that the requirement disproportionately impacts certain registrars, namely:</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="i">
<li class="MsoPlainText" style="mso-list:l0 level1 lfo5"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrars located in regions outside of the Americas and Europe, because of significant time zone differences?</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo5"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Small and medium-sized registrars, which may not have a sufficiently large team to have 24x7 staff coverage with the necessary competency?</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo5"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrars in countries where English is not the primary language, who may, in practice, need to have English-speaking TEAC contacts
to respond to requests in English?</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
<p class="MsoPlainText"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">f3)
<b>To what extent should the 4-hour time frame be revisited </b>in light of these concerns? Are there alternative means to address the underlying concerns other than adjusting the time frame?</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Status:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In initial deliberations, some support was expressed for extending the timeframe for initial contact from 4 hours to 24 hours. Early written input does not seem to contradict this path
forward:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l8 level1 lfo6"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“. . . as a practical matter, the 4-hour timeframe and the telephone-driven nature of the TEAC mechanism can lead to suboptimal outcomes. . . Research of prior RySG comments on the
IRTP Part B (March 2011) indicates (at that time) most voicing an opinion within the RySG supported a timeframe of
<b>24 hours</b>.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l8 level1 lfo6"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RrSG:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“While 4 hours may be too short, there should be a minimum response deadline (<b>perhaps 48 hours</b>) to ensure that emergency transfer disputes are addressed in a timely manner.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l8 level1 lfo6"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“The 4-hour time frame should be revisited to,
<b>at least, 24 hours</b>.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l8 level1 lfo6"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BC:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">depending on the frequency and effectiveness of use, the
<b>four-hour time frame seems generally appropriate </b>for emergency situations, though it can
<b>perhaps be expanded somewhat to 12 or 24 hours</b>.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1013" style="width:759.75pt;border-collapse:collapse">
<tbody>
<tr style="height:20.2pt">
<td width="135" valign="top" style="width:101.1pt;border:solid #37761C 1.5pt;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:20.2pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="878" valign="top" style="width:658.65pt;border:solid #37761C 1.5pt;border-left:none;background:#FDFDFD;padding:6.2pt .75pt 0in .75pt;height:20.2pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Recommendation to extend the TEAC deadline to 24 hours.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:50.35pt">
<td width="135" valign="top" style="width:101.1pt;border:solid #37761C 1.5pt;border-top:none;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:50.35pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="878" valign="top" style="width:658.65pt;border-top:none;border-left:none;border-bottom:solid #37761C 1.5pt;border-right:solid #37761C 1.5pt;background:#FDFDFD;padding:3.65pt .75pt 0in .75pt;height:50.35pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Reduce risk of gaming, reduce burden on registrars (especially smaller companies and those in time zones outside of Europe and the Americas), while still providing
a reasonable response timeframe. Currently RAA has a 24 hour SLA for Rrs to provide a non-automated initial response to reports of illegal activity. This may be considered an analogous situation.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Heard a lot of support for the 24-hour window.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question F4</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
<i>f4) Section I.A.4.6.2 of the Transfer Policy states that “Communications to a TEAC must be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized loss of a domain.” The Transfer Policy Review Scoping Team noted
that this timeframe should be more clearly defined. Is additional guidance needed to define a “reasonable period of time” after which registrars should be expected to use a standard dispute resolution process?</i><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Note:<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The working group has considered
<b>two items related to this charter question</b>:<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoPlainText" style="mso-list:l3 level1 lfo7"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The timeframe for initial contact to the TEAC following the alleged unauthorized loss of a domain.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l3 level1 lfo7"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The timeframe for final resolution of an issue raised through the TEAC channel.<o:p></o:p></span></li></ol>
<p class="MsoPlainText"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></i></p>
<p class="MsoPlainText"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">f4, Item 1</span></i></b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The timeframe for initial contact to the TEAC following the alleged unauthorized loss of a domain.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Status:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Comments from the RySG, RrSG, NCSG, and BC support providing
<b>more guidance around “a reasonable period of time.” </b>While some working group members have favored providing a precise deadline, others have noted that there may be circumstances that require more flexibility. RrSG suggested that the timeframe should
be aligned with when the registrar is made aware of the unauthorized transfer. BC suggested the period could be 5 days from the alleged unauthorized loss of a domain.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1049" style="width:786.75pt;border-collapse:collapse">
<tbody>
<tr style="height:43.15pt">
<td width="184" valign="top" style="width:138.0pt;border:solid #37761C 1.5pt;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:43.15pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="865" valign="top" style="width:648.75pt;border:solid #37761C 1.5pt;border-left:none;background:#FDFDFD;padding:3.65pt .75pt 0in .75pt;height:43.15pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Initial contact to a TEAC should generally occur no more than [x days] following the alleged unauthorized loss of a domain. If the initial contact to the TEAC
channel occurs more that [x days] following the alleged unauthorized loss of a domain, the registrar must provide a detailed explanation of why this is an emergency situation that must be addressed through the TEAC channel, including why earlier contact
to the TEAC was not possible.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:14.8pt">
<td width="184" valign="top" style="width:138.0pt;border:solid #37761C 1.5pt;border-top:none;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:14.8pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="865" valign="top" style="width:648.75pt;border-top:none;border-left:none;border-bottom:solid #37761C 1.5pt;border-right:solid #37761C 1.5pt;background:#FDFDFD;padding:3.65pt .75pt 0in .75pt;height:14.8pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The suggested approach puts additional definition around “a reasonable period of time,” while allowing flexibility for exceptional circumstances that may still
constitute an emergency.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:5.35pt">
<td width="184" valign="top" style="width:138.0pt;border:solid #37761C 1.5pt;border-top:none;background:#6AA84F;padding:6.2pt .75pt 0in .75pt;height:5.35pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">To Discuss</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
<td width="865" valign="top" style="width:648.75pt;border-top:none;border-left:none;border-bottom:solid #37761C 1.5pt;border-right:solid #37761C 1.5pt;background:#FDFDFD;padding:6.2pt .75pt 0in .75pt;height:5.35pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Would 30 days be an appropriate time frame, corresponding to the post-transfer lock period?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We had discussions around data occurrence versus data reporting – when is it a TEAC/emergency situation?<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not sure how the above would be validated. Better to look at an objective number. 30 days seems more reasonable. Shouldn’t be gauging
awareness.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">f4, Item 2</span></i></b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The timeframe for final resolution of an issue raised through the TEAC channel<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Status:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some working group members noted that it would be
<b>helpful to have defined timeframes</b>, but others raised that <b>each case is different
</b>and some cases may take longer to resolve than others. Absent data about the types of cases and resolutions handled through the TEAC channel, it is
<b>difficult to define requirements</b>.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If an issue is raised through the TEAC channel, the registrar receiving the communication must provide updates about the status of the resolution to the party who initiated
the TEAC contact no less than every [x period of time], including specific actions taken to work towards resolution.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;border-top:none;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Introduces additional transparency and accountability without providing strict deadlines that may not be appropriate or feasible to meet, depending on circumstances.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;border-top:none;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">To Discuss</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Time period for periodic updates.<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is a complicated thing to write policy around. Not sure how regular these updates need to be.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Timeframe might vary.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Goal is to keep the two parties engaged and working towards resolution. Two or three days seems reasonable.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question F5:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<i>f5) According to section I.A.4.6.2 of the Transfer Policy, the TEAC may be designated as a telephone number, and therefore some TEAC communications may take place by phone. The Transfer Policy Review Scoping Team flagged this provision as a potential item
for further consideration. Do telephone communications provide a sufficient “paper trail” for registrars who may later wish to request a transfer “undo” based on failure by a TEAC to respond? Such a request would require the registrar to provide evidence
that a phone call was made and not answered, or a call back was not received within 4 hours.
<b>Noting this requirement, should the option to communicate by phone be eliminated? Is an authoritative “system of record” for TEAC communications warranted?
</b>If so, what are the requirements for such a system?</i><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Status:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are different views on this question:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l1 level1 lfo8"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">supports “<b>exploring integrating a TEAC-like function into the ICANN nSP”</b>, but is “not prepared to recommend that the option for phone communication be eliminated without understanding
the proposed option(s) for replacement.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l1 level1 lfo8"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RrSG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">does not have a unified position and suggests that It “may be ideal to
<b>allow each registrar to choose which form of contact </b>they would prefer.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l1 level1 lfo8"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suggests that the use of telephone communication for TEAC may “raise concerns about the ability to provide a sufficient "paper trail"” and suggests that
<b>email may be a suitable system of record</b>.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l1 level1 lfo8"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BC
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">notes that “the
<b>telephone contact appears to remain an effective means </b>of communications for the initial contact, however there should perhaps be an
<b>additional logging mechanism </b>via a written report to ICANN, for example, or even via email correspondence which would have a paper trail.”<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Require that registrars provide an email address for TEAC. First attempt to contact the TEAC must be by email, but can be followed by other forms of communication (for
example, phone). The TEAC must respond to that initial email within 24 hours.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;border-top:none;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Ensures that there is a paper trail associated with each initial TEAC contact without creating complex new requirements for an system of record that may be seldom used.<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hard to build requirements when we have very little data at this point.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Don’t think the Registries role to gather evidence.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The 24-hour might stretch this out a little.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Being used so little, does it make sense to create a system of record?<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could add in that ICANN could be pushing the TEACs when then send out contacts – if ICANN knows when contact updates go out it would be
helpful if they could send them to the Registries.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Good to keep the phone contact, but the email would be initiating it and moving it forward. Solves a paper-trail/evidence issue.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems to be support for the possible path.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Questions F6/7:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<i>f6/f7) The Transfer Policy Review Scoping Team indicated that there are several factors that make a Registry Operator’s obligation to “undo” a transfer under Section 6.4 of the Transfer Policy challenging:</i><o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="i">
<li class="MsoPlainText" style="mso-list:l4 level1 lfo9"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registry Operators do not have access to the designated TEACs for each Registrar, making validation of an undo request nearly impossible.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l4 level1 lfo9"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is no way for Registry Operators to independently verify that a Registrar did not respond within the required time frame or at
all since Registry Operators are not a party to, or copied on, communications between the Registrar TEACs.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l4 level1 lfo9"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Transfer “undo” requests associated with the failure of a TEAC to respond are unilateral so there is no validation required prior to
a Registry Operator taking action. This has, on occasion, led to a “he said”, “she said” scenario.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l4 level1 lfo9"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Follow on to f6 iii., if the policy were to be updated to allow for some level of validation by the Registry Operator prior to taking
action, the requirement to “undo” a transfer within 5 calendar days of receiving an TEAC undo request leaves little to no time to attempt to validate the request prior to taking the action.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
<p class="MsoPlainText"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">To what extent are changes to the policy needed to address these concerns? Are there other pain points for Registry Operators that need to be considered in the review
of the policy in this regard?</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Issue i Status:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l2 level1 lfo10"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suggests “that ICANN Org include the Rr TEAC in the list of Rr contacts that it regularly supplies to the ROs.”<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" width="1049" style="width:787.1pt;border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Possible Path</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Recommendation that ICANN Org include the registrar TEAC in the list of registrar contacts that it regularly supplies to the ROs.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="312" valign="top" style="width:233.75pt;border:solid windowtext 1.0pt;border-top:none;background:#70AD47;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Rationale</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
</td>
<td width="738" valign="top" style="width:553.35pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Helps to ensure that registries are aware of updates to TEAC information.<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What is the issue behind the RySG suggestion:<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrars are required to keep their TEAC updated in the NsP and also the portal with the RO.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN doesn’t include the TEAC when they send updates to the RO.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Ask that ICANN includes the TEAC update along with the primary Registrar contacts.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Questions: Do registries have access to the NsP? Answer: The primary way we access the TEAC is in our own systems – pretty sure we don’t
have access to the registrar’s TEAC in the portal.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question: It seems like a logistics and operational – rather than policy – issue. Could registries go directly to GDS? Answer: Yes, we
have tried to do this but it was decided that because of GDPR this information could no longer be distributed.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Issue ii, iii, iv Status:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l6 level1 lfo11"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">early input reiterated concerns stated in the charter question. In working group discussion, RySG members have held that the process should work in such a way that the RO doesn’t need
to make a decision or conduct any verification. Registries should also not be liable in cases where they undo a transfer because a TEAC did not respond in time.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l6 level1 lfo11"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RrSG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">early input noted that “some Registrars suggest that the
<b>registry should be required to contact both registrars </b>before taking action that could impact the domain in determining whether there is noncompliance.” Further, “Transfer undoes should only occur for TEAC noncompliance when a
<b>registry can conclude that the TEAC obligations of the gaining registrar were noncompliant,
</b>not in a scenario where evidence from the two registrars is conflicting. The group may benefit from considering requiring the creation of a
<b>communication path to pass these TEAC requests back and forth </b>and ensure that the registry and ICANN also have visibility into them.”<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l6 level1 lfo11"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suggested that “one possible solution could be to require Registrar TEACs to copy Registry Operators on all TEAC communications” and noted that an authoritative system is an alternative.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l6 level1 lfo11"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BC
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">notes that in the “. . . absence of much data concerning dissatisfaction with a very infrequently used procedure, would seem to mitigate in favour little change to the current approach.”<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for Input: According to Transfer Policy Section I.A.6.4,
<i>“The Registry Operator shall undo a transfer if, after a transfer has occurred, the Registry Operator receives one of the notices as set forth below. . .6.4.4 Documentation provided by the Registrar of Record prior to transfer that the Gaining Registrar
has not responded to a message via the TEAC within the timeframe specified in Section I.A.4.6.”
</i>Would a requirement that first contact occurs by email sufficiently mitigate registry concerns about “he said, she said” scenarios?<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussion:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No suggested path forward as there are diverging positions.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Good step to go from phone to email, and having RO cc’d on TEAC email – also could be helpful if there was a suggested template for the
email to ensure it contains key information. Think about it going to a specific inbox (i.e.,
<a href="mailto:teac@godaddy.com">teac@godaddy.com</a>).<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The specific inbox probably can’t be policy, but could be guidance.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question: What evidence would the RO need to do a rollback? Answer: It is very situationally dependent. Registries have concerns about liability
– really look hard before doing a rollback.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Looking at current practices there is a lot of concern about liability.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Extending the timeframe from 4 to 24 hours will help a lot, and having an email paper trail. Could mitigate the issues.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Next Steps:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is this approach useful?
<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems like there is general support for this approach.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l9 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question: Can staff start drafting answers to charter questions? Answer: Yes, and drafting some preliminary recommendations.<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">5. AOB<o:p></o:p></span></p>
</div>
</body>
</html>