<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<meta name="Generator" content="Microsoft Word 15 (filtered medium)">

<style><!--

/* Font Definitions */

@font-face

        {font-family:"Cambria Math";

        panose-1:2 4 5 3 5 4 6 3 2 4;}

@font-face

        {font-family:DengXian;

        panose-1:2 1 6 0 3 1 1 1 1 1;}

@font-face

        {font-family:Aptos;

        panose-1:2 11 0 4 2 2 2 2 2 4;}

@font-face

        {font-family:"\@DengXian";

        panose-1:2 1 6 0 3 1 1 1 1 1;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

        {margin:0in;

        font-size:12.0pt;

        font-family:"Aptos",sans-serif;

        mso-ligatures:standardcontextual;}

span.EmailStyle17

        {mso-style-type:personal-compose;

        font-family:"Aptos",sans-serif;

        color:windowtext;}

.MsoChpDefault

        {mso-style-type:export-only;}

@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:300041273;

        mso-list-template-ids:547508828;}

@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:;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@list l1

        {mso-list-id:375932143;

        mso-list-template-ids:-1446452224;}

@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:;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@list l2

        {mso-list-id:448083557;

        mso-list-template-ids:-484832650;}

@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:;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@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:Symbol;}

@list l3

        {mso-list-id:1133447561;

        mso-list-template-ids:-311149564;}

@list l3:level1

        {mso-level-start-at:3;

        mso-level-tab-stop:.5in;

        mso-level-number-position:left;

        text-indent:-.25in;}

@list l4

        {mso-list-id:1951425882;

        mso-list-template-ids:-437589082;}

@list l4:level1

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level2

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level3

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:1.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level4

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:2.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level5

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:2.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level6

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:3.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level7

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:3.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level8

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:4.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l4:level9

        {mso-level-number-format:bullet;

        mso-level-text:;

        mso-level-tab-stop:4.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l5

        {mso-list-id:1972400170;

        mso-list-template-ids:-1557526986;}

@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:2074816567;

        mso-list-template-ids:-530799384;}

@list l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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;}

ol

        {margin-bottom:0in;}

ul

        {margin-bottom:0in;}

--></style>

</head>

<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">

<div class="WordSection1">

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Dear ARIN Colleagues, </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:13.5pt;color:black;mso-ligatures:none"> <o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">We appreciate the opportunity to provide feedback on the “Governance Document for the Recognition, Maintenance, and Derecognition of RIRs” (Version

 2 (DRAFT)). After speaking with many members of the global Internet community, this e-mail captures the collective feedback discussed. We sincerely appreciate the NRO Number Council (NRO NC) and all community members who have dedicated significant time and

 effort to producing this second draft of the RIR Governance Document. This is a critical and complex undertaking, and we value the progress made.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">We share the goals articulated in the draft's preamble: to "Ensure Accountability," "Support System Stability and Continuity," and "Preserve the

 Bottom-Up, Multistakeholder Model". We offer our feedback in a constructive spirit to ensure this draft <i>achieves</i> those goals in a legally sound and operationally robust manner. The community has a critical need to address these issues in an open and

 transparent means for the betterment of the Internet. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">TL;DR – Executive Summary & Key Takeaways (for those with limited time)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">We support evolving ICP-2 into a binding governance framework.</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> This

 timely and necessary evolution requires the NRO NC to provide the foundation for essential conversations between all RIRs and ICANN—the only entities that can resolve issues of enforceability, transparency, and operational robustness within this draft framework.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Immediate transparency is required.</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Each

 RIR and ICANN must publicly identify any objections to this framework or obstacles to adoption. This must be done promptly, with feedback shared openly and transparently with the entire Internet community, including all stakeholders.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Governance and Global Policy must remain separate.</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Existing

 avenues serve each; discussions must focus on their respective domains without co-mingling. We must immediately establish and transparently communicate clear next steps and timelines. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The community deserves meaningful inclusion.</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Beyond

 representation through the NRO NC or RIR representatives, the community deserves access to open and transparent meetings, including working sessions where any community member can attend and witness proceedings.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Critical issues require immediate attention.</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Next

 steps must address continuity, data security, and rapidly finalize NRO NC efforts to ensure the security and stability of the Internet. We have an obligation to protect the RIRs, and the community must be included in this process.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Continuity first: </span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#434343;mso-ligatures:none">Adopt

 a domain-style <b>Emergency Back-End Registry Operator (EBERO)</b> model with clearly defined, proactive continuity triggers.</span><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l2 level1 lfo1;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Include <b>escrow of registry and operational data</b>.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo1;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Define <b>approved operators</b> under contract with ICANN and/or RIRs.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l2 level1 lfo1;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Avoid peer-triggered failover; replace with <b>technical + legal thresholds</b> for real-time action.</span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Detail obligations:</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l6 level1 lfo2;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Define “<b>financially stable and independent</b>” using public, measurable criteria.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l6 level1 lfo2;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Require <b>annual financial audits</b> and <b>triennial governance audits</b>.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l6 level1 lfo2;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Establish <b>formal rehabilitation pathways</b> for non-compliant RIRs, with deadlines and enforcement.</span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Legal backbone: </span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#434343;mso-ligatures:none">Convert

 this draft into <b>bilateral, binding Recognition Agreements</b> between each RIR and a Trusted Neutral 3rd Party (currently ICANN via PTI post IANA Transition).</span><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l4 level1 lfo3;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">This gives legal force to global obligations (audits, compliance, continuity, and recognition/derecognition).</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo3;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Supersede the ineffective Section 4.1(i) “local law” carve-out—<b>no global policy can be optional</b>.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo3;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Mandate structural alignment (e.g. bylaws, MoUs) with this governance framework.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l4 level1 lfo3;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">This framework can support the current legal relationship with ICANN. </span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Decision-making Fixes:</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l0 level1 lfo4;vertical-align:baseline">

<b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Replace unanimity</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none"> with super-majority or arbitration to prevent stalemates.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">

<b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Lower derecognition thresholds</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none"> the current numbers are an incumbent shield. Understand

 that 5% is too low and opens risk for organizational capture. </span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Give ICANN an <b>emergency escalation trigger</b> when RIRs cannot act with clearly articulated rules for usage. </span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l0 level1 lfo4;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Empower an <b>independent</b> <b>Ombudsman</b>. </span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Structural gaps:</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l1 level1 lfo5;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Acknowledge and resolve the NRO’s <b>non-legal status</b> and its dual role as ASO.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo5;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Mandate a <b>transparent public charter</b> defining ASO/NRO/RIR relationships, funding, and obligations.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l1 level1 lfo5;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Avoid “peer-led takeovers”—<b>fiduciary risk is too high</b>. Legal continuity must rely on contractual mechanisms, not political votes.</span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:4.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Honor the spirit and keep IANA transition promises:</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<ul style="margin-top:0in" type="disc">

<li class="MsoNormal" style="color:black;margin-top:12.0pt;mso-list:l5 level1 lfo6;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Preserve <b>bottom-up multistakeholder authority</b>.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo6;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Require <b>open, transparent processes</b> for all implementation procedures.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo6;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Ensure <b>community-driven oversight</b>, not just RIR/ICANN negotiations behind closed doors.</span><span style="mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;margin-bottom:12.0pt;mso-list:l5 level1 lfo6;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Provide <b>achievable continuity</b> of services for all RIRs<b>.</b></span><span style="mso-ligatures:none"><o:p></o:p></span></li></ul>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This e-mail formally analyzes the draft. We find that while it introduces necessary concepts,

 it contains fundamental structural and legal ambiguities that threaten an effective governance framework. We will identify these ambiguities, explain their legal and operational consequences, and propose specific, actionable next steps to resolve them.<br>

<br>

This feedback focuses on building upon the draft’s revision – offering draft-specific feedback on clarity, requirements, and provisions – while attempting to determine future plans for implementation details. Our comments center on whether the new draft addresses

 identified issues, whether the ongoing obligations and remediation processes are sufficiently defined, and the community's next steps to ensure continuity and accountability. We also highlight certain structural concerns and suggest improvements, all in the

 spirit of constructively refining the draft. Finally, we conclude with our general support for this important process.

<br>

<br>

The remainder of this e-mail addresses detailed structural, legal, and governance recommendations and should be reviewed in full.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.25pt"><b><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Key Structural Deficiencies and a Proposed Path Forward</span></b><b><span style="font-size:18.0pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This draft represents an attempt by the numbering community to self-regulate. However, it fails to resolve the central legal conflict of the RIR

 system: the supremacy of RIRs' local legal incorporation over the "global policy" and community consensus this draft purports to enforce. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Summary of Core Deficiencies</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 "Local Law" Supremacy Clause (Sec. 4.1(i)):</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The draft grants RIRs an explicit "carve-out" to ignore any global policy or draft provision if it conflicts

 with "any applicable law" [Sec 4.1(i)]. This single clause invalidates the entire framework, rendering it advisory rather than binding, and explicitly permits the very capture and fragmentation it was meant to prevent.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 "Implementation Procedures" Black Box (Sec. 1.3):</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The draft defers critical, substantive details of governance, compliance, and continuity to "Implementation

 Procedures". These procedures are to be developed <i>later</i>, solely by "the RIRs and ICANN", with no explicit guarantee of the "open, transparent, bottom-up" community process mandated for other policies [Sec 4.1(h)]. This is an unacceptable risk, creating

 a vector for capture and dilution of intent for this draft.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Ineffective

 Accountability Triggers (Sec. 2.4, 4.2):</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The member-initiated triggers for audits and derecognition—set at "25% of the RIR's total Members or 2,000 Members,

 whichever is lesser" [Sec 2.3(b)(i)(B), Sec 2.4(b)]—are prohibitively high. They are a defense for incumbents, not a tool for the stated goal of "member-driven oversight". Equally 5% or 100 members is too low and opens the door for organizational capture.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">4.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">A

 Weak and Reactive Continuity Model (Art. 5):</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The "Emergency Continuity" plan is dangerously underdeveloped. It is <i>reactive</i>, requiring unanimous agreement

 from all other RIRs and ICANN <i>after</i> a failure has already occurred [Sec 5.1(a)], rather than a proactive, funded, and tested system. This lags significantly behind the contractual, secure models used in the domain name community. We already have clear

 examples where ICANN failed to act in response to the AFRINIC crisis. Continuity is paramount and all industry participants must have a clear understanding of their role in continuity. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Proposed Path Forward</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The NRO NC, having now received substantive community feedback, has completed its analysis. The next essential step is to move from drafting to

 adjudication. <b>We formally request the NRO NC to conclude their drafting and engage the leadership of ICANN and each of the five RIR Executive Boards, asking them to clearly and publicly articulate to the community any objections they may have to this draft

 as written.</b> This will bring any private objections (e.g., to removing the "local law" carve-out) into the open and create a transparent, documented basis for resolving these final, critical issues.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.25pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Foundational Legal Basis and Structural Flaws: A Legal Analysis</span></b><b><span style="font-size:18.0pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This section serves as our legal brief on the draft standing and core flaws.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Draft’s Legal Standing: A Multilateral Agreement, Not an enforceable "Law" </span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The draft’s preamble, which states it is an "initiative led by the NRO Number Council (NRO NC), also serving as the ASO Address Council (ASO AC)"

 highlights a foundational legal ambiguity.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Number Resource Organization (NRO) is an unincorporated "coordinating body for the five RIRs". It is, in effect, a trade association. It has

 no independent legal personality or authority to create binding "policy” or “laws" for its members (the RIRs) or for ICANN. It has no accountability to any community as it cannot enter into any legal contracts. Any substantial obligation the NRO undertakes

 requires the explicit agreement and signatures of all five RIRs. This structure still has substantial anti-trust and competition concerns. <br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Address Supporting Organization (ASO) is an official Supporting Organization <i>within the ICANN structure</i>. Its role and relationship with

 ICANN are defined by the ASO Memorandum of Understanding (MoU).</span><sup><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>

<br>

</span></sup><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The relationship between these bodies is the source of profound conflicts of interest and transparency failures. The RIRs <i>created</i> the NRO,

 which then, via the 2004 (and 2019) ASO MoU, <i>fulfills</i> the role of the ASO. This "dual-hatting" means the RIRs' coordination body is also the body meant to provide independent policy advice to ICANN specifically about numbering and RIR governance–This

 is a textbook unmitigated conflict of interest. <br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Therefore, this draft <i>cannot</i> be a "law." Its <i>only</i> path to legal force is, as defined in its own Article 7.1, "the unanimous agreement

 of ICANN and the RIRs". This draft must be treated as a proposed binding, multilateral agreement—a <i>contract</i>—between ICANN and the five RIR legal entities. This framing is essential for understanding <i>why</i> the loopholes and carve-outs it contains

 are so dangerous. It is not a policy; it is the <i>charter</i> for the system's operation.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:13.5pt;color:black;mso-ligatures:none"> <o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Currently, ICANN is a vendor to the RIRs via a contract the RIRs have with PTI which is part of ICANN. As we would consider trusted neutral 3rd

 parties to support audits, continuity, and recognition we might envision an expansion of this relationship to provide the many services such as the emergency backup or even a party to manage RIR recognition and conduct de-recognition processes if ever needed.

 This all must be contractual to be enforceable. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Fatal Flaw: Section 4.1(i) and the "Local Law" Carve-Out</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The core of the community's concern is correctly identified as Section 4.1(i). The clause states an RIR must comply with policies "so long as those

 Number Resource Policies do not obligate the RIR to violate any applicable law" [Sec 4.1(i)]. This subordinates the entire global framework to the local judiciary of any RIR's headquarters.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This concern is often raised regarding RIPE NCC, which is incorporated as a membership association under Dutch law. The concern that RIPE NCC's

 structure prevents accountability is correct in principle, the problem is the RIPE NCC's <i>obligation</i> to comply with Dutch law <i>over</i> global policy. Research confirms that RIPE NCC, as a Dutch association, is subject to Dutch court orders and has

 been compelled by them in the past.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Under Section 4.1(i) as written, a single Dutch court order could force RIPE NCC to violate a global policy, <i>and this draft would explicitly

 permit it</i>. This nullifies the concept of "global" policy and accountability, creating five different legal regimes (USA, Netherlands, Mauritius, Brazil, Australia) instead of one.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Recommendation:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> This carve-out must

 be removed. The draft’s "Rectification" clause (Sec. 7.2) must be inverted. It should not be a "grace period" for RIRs <i>to comply</i>; it must be a <b>mandatory "cure period"</b> during which an RIR must effect any <b>structural or legal changes necessary</b> (e.g.,

 changes to its articles of association or corporate form) <b>to <i>achieve</i> compliance</b> with the global draft. This is the only way to establish the supremacy of the global multistakeholder consensus over local legal structures. Note the domain name

 industry has already accomplished this with their structure with ICANN. The RIRs need for autonomy has opened the existing structure to anti-trust, jurisdictional, competitive, capture, and other vulnerabilities. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Separation of Governance and Policy</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">A foundational principle of good governance is the separation of the rules of the system (governance) from the outputs of the system (policy).

 This draft fails to maintain that separation.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This draft is a <i>governance</i> document. It establishes the entities, their obligations, and the accountability mechanisms. "Global Policies"

 are <i>policy</i> outputs related to number resources, developed via the Policy Development Process (PDP) [Sec 1.1, Sec 4.1(h)].<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">By including the Section 4.1(i) "carve-out" for <i>policies</i>, the draft co-mingles these two distinct layers. It allows a local legal challenge

 to a <i>policy</i> to invalidate the <i>governance</i> commitment.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Recommendation:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> This draft must be finalized

 as the <i>Master Governance Agreement</i> for the RIR System. Its sole purpose should be to define the rules, recognition, and accountability of the <i>RIRs themselves</i>. It should simply state that RIRs <i>must comply</i> with Global Policies developed

 through the ICANN/ASO process with <i>no</i> legal carve-outs. This separates the <i>charter of the system</i> from the <i>policies that run on it</i>.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.25pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Analysis of Community Protections: Accountability, Transparency, and Continuity</span></b><b><span style="font-size:18.0pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Proposals for robust anti-capture, continuity, and transparency measures were not meaningfully integrated into this draft.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Accountability and Anti-Capture (Failure)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The triggers for an ad-hoc audit (Sec. 2.4) or a derecognition proposal (Sec. 2.3) based on member action are "at least 25% of the RIR's total

 Members or 2,000 Members, whichever is lesser" [Sec 2.3(b)(i)(B), Sec 2.4(b)].<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">These thresholds are not an accountability tool; they are an impenetrable shield for RIR management and boards. The language supporting an ICANN

 triggered audit lacks clear direction and undermines ICANNs ability to trigger an audit requiring RIR approvals. There should be pre-determined rules that are open an transparent to direct the audit triggers.  </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">RIPE

 NCC has approximately 20,000 members. 25% would be 5,000. The trigger is therefore 2,000 members.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ARIN

 has approximately 7,000 voting members. 25% is 1,750.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Organizing

 2,000 (or 1,750) distinct corporate entities to sign a formal petition is a massive, expensive, and politically fraught undertaking.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">4.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Equally

 5% or 100 members is far too low and opens organizational capture. <br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This threshold makes the draft’s stated goal of "member-driven oversight" a fiction.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Recommendation:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> These triggers are a

 clear sign of incumbent capture. They must be dramatically lowered to a realistic level and supplemented by an <b>independent, system-wide Ombudsman</b> with the power to initiate an audit. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Transparency (Failure)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Greater transparency into the relationship between the NRO, the ICANN ASO, and the RIRs is a core community demand. There must be clear and delineated

 lines of responsibility for each entity without overlap. This draft <i>worsens</i> this problem by accepting the conflated "NRO NC, also serving as the ASO AC" without question or definition. The ASO MoU is the <i>only</i> thing giving the NRO this power,

 yet this draft fails to clarify the lines of authority, funding, and legal liability between the RIRs (who <i>fund</i> everything), the NRO (their unincorporated <i>agent</i>), and the ASO (their <i>ICANN mask</i>).<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Furthermore, the community requires that "any meetings should be open," especially "working sessions."</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Problem:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Section

 1.3 states the RIRs and ICANN will <i>jointly develop</i> the "Implementation Procedures". It does <i>not</i> state this development is subject to the "open, transparent, bottom-up" PDP mandated in Section 4.1(h). Or that this will include any community involvement,

 oversight, or participation. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Risk:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> This

 allows the RIRs and ICANN to create the <i>real</i> rules of the system in closed-door negotiations, bypassing the community. This is a primary vector for capture, manipulations, and deception.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Recommendation:</span></b><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This

 draft must mandate a formal, public charter clarifying the NRO-ASO relationship, its funding by the RIRs, and its legal status.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Section

 1.3 must be amended</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> to state explicitly that all "Implementation Procedures" are subject to a full community consultation and consensus process before they

 can be adopted by the RIRs and ICANN.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 ASO, NRO, RIRs, etc must be separate entities each conducting their specific purpose. Only through this separation can we remove conflicts and anti-competitive issues. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Continuity and Data Security (Failure)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The community requires confirmation of "Continuity, database security and protection against capture while protecting against monopoly."<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Article 5 ("Emergency Continuity") and Section 4.1(m) (Continuity) are the draft’s response, and they are wholly inadequate.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Section

 4.1(m) requires RIRs to "share such records, data... with an Emergency Operator" [Sec 4.1(m)]. This is a vague promise, not a secure, audited, and tested data escrow program. Properly funded, regularly submitted escrow property, and on-going tests to verify

 data integrity and ability to recover from this escrow data. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Article

 5 requires a <i>unanimous</i> vote of all <i>other</i> RIRs and ICANN to initiate an emergency continuity event [Sec 5.1(a)]. This is slow, political, and unworkable in a real crisis (e.g., a board capture, catastrophic financial failure, or government seizure). <br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This is not a continuity plan; it is a political "last resort" trigger. It provides <i>no</i> real-time security for the registry database, which

 is a critical global resource. As drafted this does not maintain the security and stability of the Internet. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.25pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The "Hasty" IANA Transition and the Domain Community Standard</span></b><b><span style="font-size:18.0pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The numbering community's governance model, as reflected in this draft, is demonstrably weaker, less secure, and provides fewer protections against

 capture and failure than the domain community's model. This reflects a "hasty" approach during the IANA transition that prioritized RIR autonomy over global community accountability.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Domain Community Model (ICANN Contractual Compliance)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Accountability:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> gTLD

 registries and registrars operate under direct, legally-binding contracts (the Registry Agreement and Registrar Accreditation Agreement) with ICANN. ICANN has a dedicated Contractual Compliance department to enforce these terms.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Continuity

(EBERO):<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The domain community has the Emergency Back-End Registry Operator (EBERO) program. This is a proactive, funded, and testedsystem.

 ICANN has contracts with third-party operators to take over "Critical Functions" (DNS resolution, Shared Registration System, Registration Data Directory Services, Data Escrow) in the event of a registry failure. This system has been activated to protect registrants. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The Numbering Community Model (This Draft)</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Accountability:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> A

 "collegial" model based on "good faith" </span><sup><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1</span></sup><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> and

 unanimous consent of <i>peers</i> (the other RIRs) to initiate an audit or derecognition [Sec 2.3(b)(v), Sec 2.4(a)]. This is peer protection, not public accountability.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Continuity:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> A <i>reactive</i> model

 (Article 5) that requires a unanimous political vote <i>during</i> an emergency.</span><sup><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>

<br>

</span></sup><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Conclusion & Recommendation:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> The numbering

 community's governance must be brought up to the standard set by the domain community. <b>We recommend that Article 5 and Section 4.1(m) be removed and replaced with a mandate for the RIRs and ICANN to jointly develop and fund a formal, EBERO-equivalent program

 for the Internet Numbers Registry System.</b><br>

<br>

This program must ensure proactive, secure data escrow, defined technical triggers for activation (not requiring RIR peer-unanimity), and a funded, contracted, independent operator ready to ensure service continuity.This can be under the legal framework that

 exists with ICANN, PTI, and the RIRs today. But should be re-evaluated in the future to evolve this to the benefit of number resource registrants. </span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.25pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Conclusion and Formal Next Steps</span></b><b><span style="font-size:18.0pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">We thank the NRO NC for its work in stewarding this draft. The community has now provided exhaustive feedback identifying critical, structural

 flaws. Further drafting by the same group will not solve these high-level political and legal impasses.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The time for community drafting is over; the time for leadership commitment has begun. We formally request that the NRO NC, as the convenor of

 this process, now execute the following transparent, "top-down" finalization process:</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Engage

 Leadership:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Formally transmit this draft (and a summary of community objections) to the ICANN Board and the Executive Boards of all five RIRs.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Request

 Public Comment:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"> Request that each of these six bodies provide a <b>formal, public, on-the-record response</b> to the community, articulating:</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:60.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:"Courier New";color:black;mso-ligatures:none">o</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Their

 official position on the draft.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:60.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:"Courier New";color:black;mso-ligatures:none">o</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Any

 specific objections they have to the draft as written, <i>especially</i> regarding:</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 removal of the "local law" carve-out (Sec. 4.1(i)).</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 mandate for community oversight of "Implementation Procedures" (Sec. 1.3).</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 strengthening of accountability triggers (Sec. 2.4, 4.2).</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:10.0pt;font-family:Symbol;color:black;mso-ligatures:none">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">         </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 mandate to create a formal EBERO-equivalent continuity program (Art. 5).<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<ol style="margin-top:0in" start="3" type="1">

<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo7;vertical-align:baseline">

<b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none">Document and Resolve:</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;mso-ligatures:none"> Publicly document all objections and establish a final, open,

 and transparent process (with open working sessions, as requested by the community) to adjudicate and resolve these specific, documented objections.<br>

<br>

</span><span style="mso-ligatures:none"><o:p></o:p></span></li></ol>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">This is the only path to a final, binding document that the community can trust. We must not defer these fundamental conflicts to "Implementation

 Procedures" to be solved in secret, at a later date. The risk of capture is too high, and the security and stability of the Internet Numbers Registry System is too important.<br>

<br>

</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">We look forward to participating in this next, critical phase of the process.<br>

<br>

Sincerely,</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>

William Sylvester</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">William has been a member of the global Internet community for nearly 30 years. He has actively

 contributed to RIR policy development, chaired working groups, support committees, and served as Chair of the RIPE Community Accountability Task Force after the IANA Stewardship Transition. William began his career at the InterNIC, helped launch ARIN in 1997,

 assisted in establishing the DNS Registry System in 1998, and was a member of the Whitehouse sponsored President’s Committee on Internet and Security in the early 2000s.</span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:13.5pt;color:black;mso-ligatures:none"> <o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.75pt"><b><span style="font-size:13.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Recommended Further Reading and Supporting Documents</span></b><b><span style="font-size:13.5pt;color:black;mso-ligatures:none"><o:p></o:p></span></b></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 current v2 DRAFT RIR-Governance-Document-v2-FINAL.pdf, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.nro.net/wp-content/uploads/RIR-Governance-Document-v2-FINAL.pdf" title="https://www.nro.net/wp-content/uploads/RIR-Governance-Document-v2-FINAL.pdf"><span style="font-size:12.0pt;color:#1155CC">https://www.nro.net/wp-content/uploads/RIR-Governance-Document-v2-FINAL.pdf</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Emergency

 Back-end Registry Operator - icann, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator" title="https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator"><span style="font-size:12.0pt;color:#0000EE">https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Safe

 and Secure New gTLDs: ICANN Seeks Back-up Registry Operators | (Emergency Back-End Registry Operators or "EBEROs"), accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.icann.org/en/announcements/details/safe-and-secure-new-gtlds-icann-seeks-back-up-registry-operators--emergency-back-end-registry-operators-or-eberos-14-9-2011-en" title="https://www.icann.org/en/announcements/details/safe-and-secure-new-gtlds-icann-seeks-back-up-registry-operators--emergency-back-end-registry-operators-or-eberos-14-9-2011-en"><span style="font-size:12.0pt;color:#0000EE">https://www.icann.org/en/announcements/details/safe-and-secure-new-gtlds-icann-seeks-back-up-registry-operators--emergency-back-end-registry-operators-or-eberos-14-9-2011-en</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">4.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Registry

 Transition Processes - icann, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.icann.org/registry-transition-processes-en" title="https://www.icann.org/registry-transition-processes-en"><span style="font-size:12.0pt;color:#0000EE">https://www.icann.org/registry-transition-processes-en</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">5.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">What

 is the relationship between the ASO and the NRO | The Address Supporting ... - icann, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://aso.icann.org/faq/what-is-the-relationship-between-the-aso-and-the-nro/" title="https://aso.icann.org/faq/what-is-the-relationship-between-the-aso-and-the-nro/"><span style="font-size:12.0pt;color:#0000EE">https://aso.icann.org/faq/what-is-the-relationship-between-the-aso-and-the-nro/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">6.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ASO

 & NRO | The Address Supporting Organization (ASO ICANN), accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://aso.icann.org/about/aso-and-nro/" title="https://aso.icann.org/about/aso-and-nro/"><span style="font-size:12.0pt;color:#0000EE">https://aso.icann.org/about/aso-and-nro/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">7.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">The

 Address Supporting Organization (ASO ICANN), accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://aso.icann.org/about/aso-icann/" title="https://aso.icann.org/about/aso-icann/"><span style="font-size:12.0pt;color:#0000EE">https://aso.icann.org/about/aso-icann/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">8.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ICANN

 ASO MoU 2019 | The Number Resource Organization, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.nro.net/icann-aso-mou-2019/" title="https://www.nro.net/icann-aso-mou-2019/"><span style="font-size:12.0pt;color:#0000EE">https://www.nro.net/icann-aso-mou-2019/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">9.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">    </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ICANN

 – ASO MoU (2019) | The Address Supporting Organization (ASO ICANN), accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://aso.icann.org/documents/memorandums-of-understanding/icann-address-supporting-organization-mou-november-2019/" title="https://aso.icann.org/documents/memorandums-of-understanding/icann-address-supporting-organization-mou-november-2019/"><span style="font-size:12.0pt;color:#0000EE">https://aso.icann.org/documents/memorandums-of-understanding/icann-address-supporting-organization-mou-november-2019/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">10.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ASO

 Memorandum of Understanding | The Address Supporting Organization (ASO ICANN), accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://aso.icann.org/documents/memorandums-of-understanding/aso-memorandum-of-understanding/" title="https://aso.icann.org/documents/memorandums-of-understanding/aso-memorandum-of-understanding/"><span style="font-size:12.0pt;color:#0000EE">https://aso.icann.org/documents/memorandums-of-understanding/aso-memorandum-of-understanding/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">11.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">NRO

 Number Council - American Registry for Internet Numbers - ARIN, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.arin.net/about/welcome/nronc/" title="https://www.arin.net/about/welcome/nronc/"><span style="font-size:12.0pt;color:#0000EE">https://www.arin.net/about/welcome/nronc/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">12.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">RIPE

 NCC Website and Publicly Available RIPE NCC Services Terms of Service, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.ripe.net/about-us/legal/terms-of-service/" title="https://www.ripe.net/about-us/legal/terms-of-service/"><span style="font-size:12.0pt;color:#0000EE">https://www.ripe.net/about-us/legal/terms-of-service/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">13.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">RIPE

 NCC Standard Service Agreement, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.ripe.net/publications/docs/ripe-812/" title="https://www.ripe.net/publications/docs/ripe-812/"><span style="font-size:12.0pt;color:#0000EE">https://www.ripe.net/publications/docs/ripe-812/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">14.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">RIPE

 NCC Conflict Arbitration Procedure — RIPE Network ..., accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.ripe.net/publications/docs/ripe-844/" title="https://www.ripe.net/publications/docs/ripe-844/"><span style="font-size:12.0pt;color:#0000EE">https://www.ripe.net/publications/docs/ripe-844/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">15.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Update

 on Court Proceedings Between RIPE NCC and State of the Netherlands, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.ripe.net/about-us/news/update-on-court-proceedings-between-ripe-ncc-and-state-of-the-netherlands/" title="https://www.ripe.net/about-us/news/update-on-court-proceedings-between-ripe-ncc-and-state-of-the-netherlands/"><span style="font-size:12.0pt;color:#0000EE">https://www.ripe.net/about-us/news/update-on-court-proceedings-between-ripe-ncc-and-state-of-the-netherlands/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">16.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">A

 First for the RIPE NCC: Seizure of the “Right to Registration of IPv4 Addresses” for the Recovery of Money, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://labs.ripe.net/author/ciaran_byrne/a-first-for-the-ripe-ncc-seizure-of-the-right-to-registration-of-ipv4-addresses-for-the-recovery-of-money/" title="https://labs.ripe.net/author/ciaran_byrne/a-first-for-the-ripe-ncc-seizure-of-the-right-to-registration-of-ipv4-addresses-for-the-recovery-of-money/"><span style="font-size:12.0pt;color:#0000EE">https://labs.ripe.net/author/ciaran_byrne/a-first-for-the-ripe-ncc-seizure-of-the-right-to-registration-of-ipv4-addresses-for-the-recovery-of-money/</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">17.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Seizing

 IP addresses in the Netherlands as a security for your damages claims in international litigation - Taylor Wessing, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.taylorwessing.com/en/insights-and-events/insights/2023/07/seizing-ip-addresses-in-the-netherlands" title="https://www.taylorwessing.com/en/insights-and-events/insights/2023/07/seizing-ip-addresses-in-the-netherlands"><span style="font-size:12.0pt;color:#0000EE">https://www.taylorwessing.com/en/insights-and-events/insights/2023/07/seizing-ip-addresses-in-the-netherlands</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">18.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">About

 Registrars - ICANN, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.icann.org/resources/pages/what-2013-05-03-en" title="https://www.icann.org/resources/pages/what-2013-05-03-en"><span style="font-size:12.0pt;color:#0000EE">https://www.icann.org/resources/pages/what-2013-05-03-en</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">19.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none">  </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">gTLD

 Registry Continuity - icann, accessed November 6, 2025, </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator/gtld-registry-continuity" title="https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator/gtld-registry-continuity"><span style="font-size:12.0pt;color:#0000EE">https://www.icann.org/en/contracted-parties/registry-operators/resources/emergency-back-end-registry-operator/gtld-registry-continuity</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">20.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none"> </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">ICANN

 to Move Four gTLDs Into the Emergency Back-End Registry Operator Program, accessed November 6, 2025, <a href="https://www.icann.org/en/announcements/details/icann-to-move-four-gtlds-into-the-emergency-back-end-registry-operator-program-12-07-2024-en" title="https://www.icann.org/en/announcements/details/icann-to-move-four-gtlds-into-the-emergency-back-end-registry-operator-program-12-07-2024-en"><span style="color:#0000EE">https://www.icann.org/en/announcements/details/icann-to-move-four-gtlds-into-the-emergency-back-end-registry-operator-program-12-07-2024-en</span></a></span><u><span style="font-family:"Arial",sans-serif;color:#0000EE;mso-ligatures:none"> </span></u><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">21.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none"> </span><span style="font-family:"Arial",sans-serif;color:#1B1B1B;mso-ligatures:none">Fact

 Sheet: The IANA Stewardship Transition Explained, </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://www.ntia.gov/other-publication/fact-sheet-iana-stewardship-transition-explained" title="https://www.ntia.gov/other-publication/fact-sheet-iana-stewardship-transition-explained"><span style="color:#1155CC">https://www.ntia.gov/other-publication/fact-sheet-iana-stewardship-transition-explained</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:30.0pt;text-indent:-.25in;vertical-align:baseline">

<span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">22.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black;mso-ligatures:none"> </span><span style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Proposal

 to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions, <a href="https://www.ianacg.org/icg-files/documents/IANA-transition-proposal-final.pdf" title="https://www.ianacg.org/icg-files/documents/IANA-transition-proposal-final.pdf"><span style="color:#1155CC">https://www.ianacg.org/icg-files/documents/IANA-transition-proposal-final.pdf</span></a></span><span style="color:black;mso-ligatures:none"><o:p></o:p></span></p>

<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:13.5pt;color:black;mso-ligatures:none"><br>

<br>

<br>

<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:13.5pt;color:black;mso-ligatures:none"> <o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size:13.5pt;color:black;mso-ligatures:none"> <o:p></o:p></span></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

</div>

</body>

</html>