<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
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:197011273;
mso-list-template-ids:-1437956392;}
@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:1377387329;
mso-list-template-ids:-893096074;}
@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:1395741758;
mso-list-template-ids:752938240;}
@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:1868523418;
mso-list-template-ids:-1212796790;}
@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;}
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="color:black">Dear all, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please find below the notes from the IDNs EPDP Working Session (2 of 2) at ICANN74. Please note that as this meeting was primarily background/foundational information oriented, the recording should be consulted
for details.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Ariel, Emily, and Steve<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <b> </b> <o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:black">Notes – IDNs EPDP Call – 15 June 2022</span></u></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black"> <o:p></o:p></span></b></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="color:black">Welcome and Opening Remarks</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
Helpful to provide level-set before we talk about 2nd level implications, since it will not be the same as the top-level.<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Foundational Presentation: IDN Tables at Second-Level</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 2 - Terminology<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 3 - Rules for ASCII Domain Name Labels<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 4 - Domain Name Mnemonics in ASCII<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 5 - Domain Name Mnemonics in ASCII - top-level<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 6 - Internationalized Domain Name (IDN) Labels<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 7 - Objective of IDN Tables<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 8 - What Does the IDN Table Do?<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 9 - What is an IDN Table?<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Confirmation that IDN tables at the second-level are more discretionary than in nature versus the top-level, which is fixed against the RZ-LGR.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Two registries that serve the same language and/or script, may have different tables.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
As tables are established by the registry, how are they managed? Responsibility of the registry. This will be covered when the registries/registrars talk about their practical experiences.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
In reality, the tables generally have a lot of commonalities.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 10 - Evolution of IDN Table Formats<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 11 - Example of IDN Table in RFC3743 Format<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 12 - Example of IDN Table in RFC4290 Format<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 13 - Example of IDN Table in RFC7940 Format<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 14 - Why the XML Format?<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Question - must the old format tables be deleted with the new formats? Answer - it is a business decision. All three are supported by ICANN.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
For RZ-LGR, is the XML schema consistent? Consistent with relevant RFC.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 15 - Who Develops the IDN Tables?<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
How are security and stability problems mitigated? ICANN Org reviews and resolves with registry operator. Once mutually agreed to, it is captured in Exhibit A. <o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
“Any” security and stability problems, without context, is perhaps an unrealistically high bar. Iterative process between ICANN Org and RO tries to mitigate as best as possible.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 16 - Example: Mini Latin Script IDN Table<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 17 - Example: Mini Latin Script IDN Table, cont.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 18 - Activating Variant Labels at the Second Level<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 19 - Harmonizing Multiple IDN Tables Under TLDs<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 20 - Harmonizing Multiple IDN Tables under TLDs<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 21 - Example: The Need of Harmonization for IDN Tables<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 22 - Example: The Need of Harmonization for IDN Tables, cont.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 23 - Example: The Need of Harmonization for IDN Tables, cont.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 23 - Example: The Need of Harmonization for IDN Tables, cont.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 24 - Example: The Need of Harmonization for IDN Tables, cont.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 25 - Reference Label Generation Rules (LGRs)<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Question - Practically, is it possible to combine the tables, or do you just have common ruleset? Answer - there are actually three tables (e.g., Latin, Cyrillic, and combined).<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 26 - Background of IDN Table Review<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2;vertical-align:baseline">
Slide 27 - IDN Table Review Tool<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Share Practice with regard to IDN Management at Second-Level & IDN Table Implementation</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Given the presentation, what are the practical experiences for registries and registrars? For instance, are there implications for different IDN tables.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Dennis Tan (Verisign) - There are more than 100+ IDN tables. Different languages and scripts will require different rules (e.g., simplified and traditional Chinese).<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Policy for variants, for many years, is to simply block the variants.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Question - as there isn’t a high level of variability between IDN tables across different ROs, does that represent coordination? Answer - Generally, there are more commonalities than differences. Deviations generally just limited to a handful of characters/letters
and rules.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Suggestion, maybe some data can be gathered from IANA repository.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Question - is there direct interaction with language communities? Answer - the consultation did take place, but many years ago. Context is that the tables were leveraging existing work, not starting from the ground up.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Question - what’s the discussion like for the ICANN Org and RO security and stability review? Answer - can generally be limited b/c tables are consistent. However, ongoing discussions on how make the process more consistent and transparent. <o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
Security and stability is a dynamic property. What was previously secure and stable may not hold forever.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
For registrars, what is the applicability for the IDN tables? <o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
At least in one experience, the registrar does not implement the IDN table. The registrar will send the check to the RO, who is able to provide the authoritative answer. In essence, the registrar can rely on the registry’s validation (e.g., sending via EPP,
a domain check command).<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo3;vertical-align:baseline">
As a back-end RSP, will need to work with RO to determine which IDN tables the client wants to deploy. In some cases, will leverage existing IDN tables.<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">AOB</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo4;vertical-align:baseline">
None<o:p></o:p></li></ul>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Steven Chan</span></b><b><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span></b><b><span style="font-size:11.0pt"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Senior Director, Policy Development Support & GNSO Relations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Internet Corporation for Assigned Names and Numbers (ICANN) </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">12025 Waterfront Drive, Suite 300<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Los Angeles, CA 90094-2536</span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Email: <a href="mailto:steve.chan@icann.org">
<span style="color:#0563C1">steve.chan@icann.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Skype: steve.chan55<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Mobile: +1.310.339.4410<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Find out more about the GNSO by visiting: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4Mxf"><span style="color:#0563C1">https://learn.icann.org/</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Follow @GNSO on Twitter: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjE"><span style="color:#0563C1">https://twitter.com/ICANN_GNSO</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Transcripts and recordings of GNSO Working Group and Council events are located on the <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e="><span style="color:#0563C1">GNSO
Master Calendar</span><span style="color:#954F72"> </span></a></span><o:p></o:p></p>
</div>
</body>
</html>