<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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        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:27687455;
        mso-list-type:hybrid;
        mso-list-template-ids:-531567422 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l1
        {mso-list-id:1118792433;
        mso-list-template-ids:-923098948;}
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 meeting on Thursday, 26 May 2022 at 13:30 UTC.<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>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"> <b>  </b><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:black">Notes – IDNs EPDP Call – 02 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" style="vertical-align:baseline"><b><span style="color:black">Roll Call & SOI<o:p></o:p></span></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
None<o:p></o:p></li></ul>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black">Welcome & Chair Updates<o:p></o:p></span></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Reviewing calendar, cancelled meeting #39 and #40. Takes into account ICANN74, which includes two sessions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">During ICANN74 session – to receive an update from liaison on ccPDP4, update from small team, working session on charter questions. The sessions will be open to the public.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Reminder that room capacities are limited.<o:p></o:p></span></li></ul>
<p class="MsoListParagraph" style="vertical-align:baseline"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black">Discuss charter question E7, parking lot item – evaluating variants of restricted gTLD (e.g., .brand, geographic names, etc.)<o:p></o:p></span></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">This parking lot item came from discussing the evaluation of variants of restricted gTLDs.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Connection to B5, which was about the principle for treatment of non-standard TLDs. Preliminary agreement there is that at a principle level, the variants should be considered different versions of the same string, and be bound
 by the same restrictions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Only considered the topic from the perspective of new gTLDs, not existing gTLDs. Also did not discuss at the evaluation process, which is why it was added to the parking lot.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Slide 7 – Community-based TLDs<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Slide 8 – Geographic Names<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Slide 9 – Brand TLDs<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Slide 10 – TLDs Subject to Category 1 Safeguards<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Slide 11 – Questions for Discussion<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">1. Bound by same eval process 2) must meet same criteria and 3) if not possible to meet criteria, how should variants be treated?<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Complicated topic, so this may be a challenging conversation.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Noted that the group has agreed that the primary and variants should be considered a single application. Therefore, it may make sense that the evaluation requirements should be applied against the variants.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Some agreement from members. And further, that if a variant does not meet the requirements, it should not pass evaluation.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For a community application in particular, it may not always be possible for a community applicant to meet the stringent requirements for Community Priority Evaluation. Therefore, may be better to consider the strings as a set,
 not individually require each to pass CPE.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Noting the principles this group has agreed to (e.g., RZ-LGR, same-entity, atomicity, conservativeness), they should serve as a lens to look at this topic through.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">The primary string may potentially be subject to the heaviest, full requirements, and perhaps variants can be subject to a lighter weight evaluation process/requirements.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Noted the expectation of updating the process flow to include preliminary recommendations, which may help understand requirements.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For geographic names, the process should take into account the different levels (1, 2, 3) for comparison purposes. As in, should the letter of support be required for level 1, 2, or 3.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Some suggestions that the letter of support should also apply to allocatable variants (requested variants).<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For .brand, a TM is required. In some cases, the variants may not have TMs. We may need additional expertise for some of these questions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">There are entry conditions, evaluation conditions, and in some cases, contractual requirements. Maybe helpful to look at each. And perhaps there are general treatment for all.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Three questions to shape discussion:<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Should each requested variant label be subject to the same evaluation process as the primary string?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Should the variant labels meet the same criteria as the primary string in order to pass evaluation?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">In the event where it is not possible for the variant labels to meet the same criteria as the primary string, how should such variant labels be treated?<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Geographic Names – the variant may not strictly meet the requirements of a geographic name as defined in the AGB. Is this possible?<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For a city name in Arabic, the variant may be in Urdu, Pashto, etc.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Requiring letters of support for variants potentially protects relevant governmental entity.
<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Question about multiple applications for the same term, with different spellings. Or even same spelling, with multiple applicants (with adequate support).<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For a city in China, it may be politically sensitive to request the traditional Chinese as a variant and say it supports/non-objects. Or vice versa, asking other regions to endorse a simplified string may be problematic where
 they typically use traditional Chinese. As such, this is an argument to emphasize the primary string.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">There are implications here, where the variants may still be subject to objection processes.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Noted that the example above, where a government is not in a position to endorse (even if it may not actually object.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">For Brands, it is similar to Geos, where the variants may not have a TM.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Suggestion to block (or disallow from application) variants that are not trademarks. No standing to treat as a brand name if it doesn’t have TM backing.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Community-based TLDs, would be relative to CPE. If not in contention, the claim to support a community is accepted as a matter of faith.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Concern about scoring system for CPE. Explanation of applicability of scoring (i.e., to award priority over others).<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Question for this group is relevance of variants to CPE scoring.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">What makes these conversation more difficult is that it requires a deep understanding of the process to understand implications.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Question about whether the 2012 round experienced challenging situations as it relates to variants. Clarification that variants were not allowed in 2012.<o:p></o:p></span></li></ul>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="color:black">AOB<o:p></o:p></span></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">None<o:p></o:p></span></li></ul>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-size:11.0pt;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>