<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0//EN" "http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><!--This file was converted to xhtml by LibreOffice - see http://cgit.freedesktop.org/libreoffice/core/tree/filter/source/xslt for the code.--><head profile="http://dublincore.org/documents/dcmi-terms/"><meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/><title xml:lang="en-US">CRISP Team Draft Proposal</title><meta name="DCTERMS.title" content="CRISP Team Draft Proposal" xml:lang="en-US"/><meta name="DCTERMS.language" content="en-US" scheme="DCTERMS.RFC4646"/><meta name="DCTERMS.source" content="http://xml.openoffice.org/odf2xhtml"/><meta name="DCTERMS.issued" content="2015-01-08T15:44:00" scheme="DCTERMS.W3CDTF"/><meta name="DCTERMS.contributor" content="Alan Barrett"/><meta name="DCTERMS.modified" content="2015-01-12T15:27:14.943040928" scheme="DCTERMS.W3CDTF"/><meta name="DCTERMS.provenance" content="" xml:lang="en-US"/><meta name="DCTERMS.subject" content="," xml:lang="en-US"/><link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" hreflang="en"/><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" hreflang="en"/><link rel="schema.DCTYPE" href="http://purl.org/dc/dcmitype/" hreflang="en"/><link rel="schema.DCAM" href="http://purl.org/dc/dcam/" hreflang="en"/><style type="text/css">
        @page {  }
        table { border-collapse:collapse; border-spacing:0; empty-cells:show }
        td, th { vertical-align:top; font-size:12pt;}
        h1, h2, h3, h4, h5, h6 { clear:both }
        ol, ul { margin:0; padding:0;}
        li { list-style: none; margin:0; padding:0;}
        <!-- "li span.odfLiEnd" - IE 7 issue-->
        li span. { clear: both; line-height:0; width:0; height:0; margin:0; padding:0; }
        span.footnodeNumber { padding-right:1em; }
        span.annotation_style_by_filter { font-size:95%; font-family:Arial; background-color:#fff000;  margin:0; border:0; padding:0;  }
        * { margin:0;}
        .No_20_Spacing { color:#00000a; font-size:11pt; line-height:100%; font-family:Calibri; writing-mode:lr-tb; text-align:left ! important; }
        .P1 { color:#000000; font-size:11pt; line-height:100%; text-align:center ! important; font-family:Arial; writing-mode:lr-tb; }
        .P10 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P11 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; font-style:italic; }
        .P12 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P13 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.139in; }
        .P14 { color:#000000; font-size:14pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.139in; font-weight:bold; }
        .P15 { color:#000000; font-size:11pt; line-height:115%; text-align:center ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.139in; }
        .P16 { color:#000000; font-size:12pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.139in; font-style:italic; font-weight:bold; }
        .P17 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.139in; }
        .P18 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0in; text-indent:0.5in; }
        .P19 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.5in; margin-right:0in; text-indent:-0.2492in; }
        .P2 { color:#00000a; font-size:10.5pt; line-height:0.1528in; margin-left:0in; margin-right:0in; text-align:left ! important; text-indent:0in; font-family:Arial; writing-mode:lr-tb; }
        .P20 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.5in; margin-right:0in; text-indent:0in; }
        .P21 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.6252in; margin-right:0in; text-indent:-0.3752in; }
        .P22 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0in; margin-top:0in; margin-bottom:0.139in; text-indent:0.25in; }
        .P23 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0in; text-indent:0.25in; }
        .P24 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0in; text-indent:0.25in; font-weight:bold; }
        .P25 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0in; text-indent:0.2508in; }
        .P26 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.1945in; margin-right:0in; text-indent:0in; }
        .P27 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.25in; margin-right:0in; text-indent:0in; }
        .P28 { color:#000000; font-size:11pt; line-height:115%; margin-bottom:0in; margin-left:0.25in; margin-right:0in; margin-top:0in; text-align:left ! important; text-indent:0in; font-family:Arial; writing-mode:lr-tb; }
        .P3 { color:#00000a; font-size:10.5pt; line-height:120%; margin-left:0in; margin-right:0.0783in; text-align:left ! important; text-indent:0in; font-family:Arial; writing-mode:lr-tb; margin-top:0.0319in; margin-bottom:0in; }
        .P30 { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P31 { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P32 { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Calibri; writing-mode:lr-tb; margin-left:0.25in; margin-right:0in; text-indent:0in; }
        .P33 { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.25in; margin-right:0in; text-indent:0in; }
        .P34 { color:#00000a; font-size:12pt; line-height:100%; text-align:left ! important; font-family:Cambria; writing-mode:lr-tb; }
        .P35 { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P36 { color:#00000a; font-size:11pt; line-height:100%; text-align:justify ! important; font-family:Arial; writing-mode:lr-tb; }
        .P37 { color:#000000; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P38 { color:#000000; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P39 { color:#000000; font-size:11pt; line-height:100%; text-align:justify ! important; font-family:Arial; writing-mode:lr-tb; }
        .P4 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P40 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P41 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P42 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P43 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0.122in; text-indent:0in; }
        .P44 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0.122in; text-indent:0in; }
        .P45 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.0693in; margin-right:0.122in; text-indent:0in; }
        .P46 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0.0693in; margin-right:0.2075in; text-indent:0in; }
        .P47 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0.0752in; text-indent:0in; }
        .P48 { color:#000000; font-size:11pt; line-height:120%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0.1508in; text-indent:0in; }
        .P49 { color:#000000; font-size:11pt; line-height:100%; text-align:justify ! important; font-family:Arial; writing-mode:lr-tb; margin-left:0in; margin-right:0.148in; margin-top:0in; margin-bottom:0.148in; text-indent:0in; }
        .P5 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; font-weight:bold; }
        .P50 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; margin-top:0in; margin-bottom:0.1665in; }
        .P6 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P7 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P8 { color:#000000; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .P9 { color:#00000a; font-size:11pt; line-height:115%; text-align:left ! important; font-family:Arial; writing-mode:lr-tb; }
        .Plain_20_Text { color:#00000a; font-size:11pt; line-height:100%; text-align:left ! important; font-family:Calibri; writing-mode:lr-tb; }
        .Standard { color:#000000; font-size:11pt; line-height:115%; font-family:Arial; writing-mode:lr-tb; text-align:left ! important; }
        .normal { color:#000000; font-size:11pt; line-height:115%; font-family:Arial; writing-mode:lr-tb; text-align:left ! important; }
        .Table1 { width:6.6507in; margin-left:-0.0785in; margin-top:0in; margin-bottom:0in; margin-right:auto;writing-mode:lr-tb; }
        .Table2 { width:5.0729in; margin-left:-0.075in; margin-top:0in; margin-bottom:0in; margin-right:auto;writing-mode:lr-tb; }
        .Table1_A1 { padding-left:0.0785in; padding-right:0.075in; padding-top:0in; padding-bottom:0in; border-width:0.0176cm; border-style:solid; border-color:#00000a; }
        .Table2_A1 { padding:0.0139in; border-style:none; }
        .Table1_A { width:1.5292in; }
        .Table1_B { width:0.8097in; }
        .Table1_C { width:2.8535in; }
        .Table1_D { width:1.4576in; }
        .Table2_A { width:0.9681in; }
        .Table2_B { width:2.9264in; }
        .Table2_C { width:1.1785in; }
        .Internet_20_link { color:#0000ff; text-decoration:underline; }
        .ListLabel_20_1 { text-decoration:none ! important; }
        .T1 { font-family:Times New Roman; }
        .T10 { font-size:12pt; font-weight:bold; }
        .T11 { font-size:12pt; font-style:italic; font-weight:bold; }
        .T12 { font-weight:bold; }
        .T13 { font-weight:bold; }
        .T16 { font-family:Tahoma; }
        .T17 { color:#1155cc; text-decoration:underline; }
        .T18 { color:#1155cc; text-decoration:underline; }
        .T19 { color:#0000ff; }
        .T2 { font-size:14pt; font-weight:bold; }
        .T21 { color:#0000ff; text-decoration:underline; }
        .T22 { font-size:11pt; }
        .T23 { font-size:11pt; letter-spacing:0.0138in; }
        .T24 { font-size:11pt; letter-spacing:0.0126in; }
        .T25 { font-size:11pt; letter-spacing:0.0146in; }
        .T26 { font-size:11pt; letter-spacing:0.0134in; }
        .T27 { font-size:11pt; letter-spacing:0.0154in; }
        .T28 { font-size:11pt; letter-spacing:0.0181in; }
        .T29 { font-size:11pt; letter-spacing:0.0173in; }
        .T3 { font-style:italic; }
        .T30 { font-size:11pt; letter-spacing:0.0165in; }
        .T31 { font-size:11pt; letter-spacing:0.0402in; }
        .T32 { font-size:11pt; letter-spacing:0.0161in; }
        .T33 { letter-spacing:0.0146in; }
        .T34 { letter-spacing:0.0154in; }
        .T35 { letter-spacing:0.0138in; }
        .T36 { letter-spacing:0.0161in; }
        .T37 { letter-spacing:0.0402in; }
        .T38 { letter-spacing:0.0165in; }
        .T39 { letter-spacing:0.0134in; }
        .T4 { font-style:italic; }
        .T40 { letter-spacing:0.0319in; }
        .T41 { letter-spacing:0.0209in; }
        .T42 { letter-spacing:0.0201in; }
        .T43 { letter-spacing:0.0193in; }
        .T44 { letter-spacing:0.0217in; }
        .T45 { letter-spacing:0.0457in; }
        .T46 { letter-spacing:0.0283in; }
        .T47 { letter-spacing:0.0362in; }
        .T48 { letter-spacing:0.0181in; }
        .T49 { letter-spacing:0.0374in; }
        .T5 { font-style:italic; font-weight:bold; }
        .T50 { letter-spacing:0.0445in; }
        .T51 { letter-spacing:0.0339in; }
        .T53 { font-family:Arial; }
        .T54 { font-family:Arial; font-style:italic; font-weight:bold; }
        .T55 { font-family:Arial; font-style:italic; }
        .T56 { color:#0000e9; text-decoration:underline; }
        .T58 { color:#1a1a1a; }
        .T59 { color:#103cc0; text-decoration:underline; }
        .T6 { color:#00000a; font-family:Cambria; font-size:12pt; font-style:italic; }
        .T7 { color:#00000a; }
        .T8 { color:#00000a; vertical-align:super; font-size:58%;}
        .T9 { color:#00000a; text-decoration:underline; }
        <!-- ODF styles with no properties representable as CSS -->
        .Table1.1 .Table2.1 .T14 .T15 .T52 .T57  { }
        </style></head><body dir="ltr" style="max-width:8.5in;margin-top:1in; margin-bottom:0.5in; margin-left:1in; margin-right:1in; background-color:#ffffff; "><p class="P17"><span class="T2">Version Control</span></p><table border="0" cellspacing="0" cellpadding="0" class="Table1"><colgroup><col width="170"/><col width="90"/><col width="317"/><col width="162"/></colgroup><tr class="Table11"><td style="text-align:left;width:1.5292in; " class="Table1_A1"><p class="P34"><span class="T3">DATE</span></p></td><td style="text-align:left;width:0.8097in; " class="Table1_A1"><p class="P34"><span class="T3">DRAFT VERSION</span></p></td><td style="text-align:left;width:2.8535in; " class="Table1_A1"><p class="P34"><span class="T3">DESCRIPTION</span></p></td><td style="text-align:left;width:1.4576in; " class="Table1_A1"><p class="P34"><span class="T3">URL</span></p></td></tr><tr class="Table11"><td style="text-align:left;width:1.5292in; " class="Table1_A1"><p class="P34"><span class="T3">2015/01/08</span></p></td><td style="text-align:left;width:0.8097in; " class="Table1_A1"><p class="P34"><span class="T3">2</span></p></td><td style="text-align:left;width:2.8535in; " class="Table1_A1"><p class="P34"><span class="T3"> - Additional description on contract details, review committee and intellectual property rights</span></p><p class="P34"><span class="T3"> - Description revised on Section V. NITA Requirements and VI. Community Process for more clarity</span></p><p class="P34"><span class="T3"> - No changes are made to key elements of the proposal. </span></p></td><td style="text-align:left;width:1.4576in; " class="Table1_A1"><p class="P37"><a href="https://www.nro.net/crisp-proposal-second-draft" class="Internet_20_link"><span class="T6">https://www.nro.net/crisp-proposal-second-draft</span></a></p></td></tr><tr class="Table11"><td style="text-align:left;width:1.5292in; " class="Table1_A1"><p class="P34"><span class="T3">2014/12/24</span></p></td><td style="text-align:left;width:0.8097in; " class="Table1_A1"><p class="P34"><span class="T3">1.1</span></p></td><td style="text-align:left;width:2.8535in; " class="Table1_A1"><p class="P34"><span class="T3">Editorial Changes</span></p></td><td style="text-align:left;width:1.4576in; " class="Table1_A1"><p class="P37"><a href="https://www.nro.net/crisp-proposal-first-draft-1-1" class="Internet_20_link"><span class="T6">https://www.nro.net/crisp-proposal-first-draft-1-1</span></a></p></td></tr><tr class="Table11"><td style="text-align:left;width:1.5292in; " class="Table1_A1"><p class="P34"><span class="T3">2014/12/19</span></p></td><td style="text-align:left;width:0.8097in; " class="Table1_A1"><p class="P34"><span class="T3">1.0</span></p></td><td style="text-align:left;width:2.8535in; " class="Table1_A1"><p class="P34"><span class="T3">First draft for comments</span></p></td><td style="text-align:left;width:1.4576in; " class="Table1_A1"><p class="P37"><a name="_GoBack"/><a href="https://www.nro.net/crisp-proposal-first-draft" class="Internet_20_link"><span class="T6">https://www.nro.net/crisp-proposal-first-draft</span></a></p></td></tr></table><p class="P14"> </p><p class="P15"><span class="T2">Draft Response to the Internet Coordination Group Request for Proposals on IANA from the RIR community</span></p><p class="P13"><span class="T10">1.              Proposal type</span></p><p class="normal">Identify which category of the IANA functions this submission proposes to address:</p><p class="P18"> [  ] Names                           <span> [ ✔] Numbers                   </span><span> [  ] Protocol Parameters</span></p><p class="normal"> </p><p class="P13"><span class="T10">I.               Description of Community’s Use of IANA</span></p><p class="normal"><span class="T3">This section should list the specific, distinct IANA services or activities your community relies on. For each IANA service or activity on which your community relies, please provide the following:</span></p><p class="normal"><span class="T3"> </span></p><p class="P19">·       <span class="T3">A description of the service or activity.</span></p><p class="P19">·       <span class="T3">A description of the customer(s) of the service or activity.</span></p><p class="P19">·       <span class="T3">What registries are involved in providing the service or activity.</span></p><p class="P19">·       <span class="T3">A description of any overlaps or interdependencies between your IANA requirements and the functions required by other customer communities</span></p><p class="P20"> </p><p class="P19"><span class="T12">I.A.</span>  <span class="T3">A description of the service or activity.</span></p><p class="normal"> </p><p class="normal">The IANA activities relevant to the number resource communities are the maintenance of the global Internet number resource registries, including the allocation of IPv4 addresses, IPv6 addresses, and Autonomous System Numbers (“ASNs”) to the Regional Internet Registries (“RIRs”) as well as the delegation of subdomains below the “IN-ADDR.ARPA” and “IP6.ARPA” domains in accordance with the allocation of IPv4 and IPv6 addresses.</p><p class="normal"> </p><p class="P19"><span class="T12">I.B.</span>  <span class="T3">A description of the customer(s) of the service or activity.</span></p><p class="normal"> </p><p class="normal">The RIRs manage the registration and distribution of Internet number resources (IPv4 and IPv6 addresses and ASNs) to members within their service regions. The five RIRs in operation at this point in time are:</p><p class="normal"> </p><table border="0" cellspacing="0" cellpadding="0" class="Table2"><colgroup><col width="107"/><col width="325"/><col width="131"/></colgroup><tr class="Table21"><td style="text-align:left;width:0.9681in; " class="Table2_A1"><p class="P4">AFRINIC</p></td><td style="text-align:left;width:2.9264in; " class="Table2_A1"><p class="P4">Serving Africa</p></td><td style="text-align:left;width:1.1785in; " class="Table2_A1"><p class="P4">Founded in 2005</p></td></tr><tr class="Table21"><td style="text-align:left;width:0.9681in; " class="Table2_A1"><p class="P4">APNIC</p></td><td style="text-align:left;width:2.9264in; " class="Table2_A1"><p class="P4">Serving the Asia Pacific region</p></td><td style="text-align:left;width:1.1785in; " class="Table2_A1"><p class="P4">Founded in 1993</p></td></tr><tr class="Table21"><td style="text-align:left;width:0.9681in; " class="Table2_A1"><p class="P4">ARIN</p></td><td style="text-align:left;width:2.9264in; " class="Table2_A1"><p class="P4">Serving North America</p></td><td style="text-align:left;width:1.1785in; " class="Table2_A1"><p class="P4">Founded in 1997</p></td></tr><tr class="Table21"><td style="text-align:left;width:0.9681in; " class="Table2_A1"><p class="P4">LACNIC</p></td><td style="text-align:left;width:2.9264in; " class="Table2_A1"><p class="P4">Serving South America and the Caribbean</p></td><td style="text-align:left;width:1.1785in; " class="Table2_A1"><p class="P4">Founded in 2001</p></td></tr><tr class="Table21"><td style="text-align:left;width:0.9681in; " class="Table2_A1"><p class="P4">RIPE NCC</p></td><td style="text-align:left;width:2.9264in; " class="Table2_A1"><p class="P4">Serving Europe, Central Asia and the Middle East</p></td><td style="text-align:left;width:1.1785in; " class="Table2_A1"><p class="P4">Founded in 1992</p></td></tr></table><p class="normal"> </p><p class="normal">The five RIRs manage the distribution and registration of Internet number resources at the regional level, having received blocks of unused resources from the global pools managed by the IANA operator.  The RIRs also facilitate the policy development processes of their respective communities, providing secretariat roles.</p><p class="normal"> </p><p class="normal">The five RIRs have a long-standing and straightforward operational relationship with IANA. IANA maintains the global pools of Internet number resources from which the RIRs receive allocations to distribute to their communities. The RIRs also coordinate with IANA to correctly register any resources that are returned to the global pools. Collectively, the system for administering Internet number resources is referred to as the "Internet Number Registry System" and is described in detail in RFC 7020.</p><p class="normal"> </p><p class="P19"><span class="T12">I.C.</span>  <span class="T3">What registries are involved in providing the service or activity.</span></p><p class="normal"> </p><p class="normal">The most relevant IANA registries are the IPv4 address registry, the IPv6 address registry, and the ASN registry.  Provision of reverse DNS services in “IN-ADDR.ARPA” and “IP6.ARPA” domains may also require interaction with the .ARPA zone registry.</p><p class="normal"> </p><p class="P21"><span class="T12">I.D.</span>  <span class="T3">A description of any overlaps or interdependencies between your IANA requirements and the functions required by other customer communities.</span></p><p class="normal"> </p><p class="normal">The Internet Engineering Task Force (“IETF”) is responsible for policy relating to the entire IP address space and AS number space.  Through the IANA protocol parameters registries, the IETF delegates unicast IP address ("IANA IPv4 Address Space Registry" and "IPv6 Global Unicast Allocations Registry") and AS number space (“ASN Registry) to the RIR system [RFC7020]. These registries are generally accessed via references based on the iana.org domain name.  Note that within each IANA registry, there are also reserved values or ranges, and special-purpose registries, which are outside the Internet Numbers Registry System and instead administered under the direction of the IETF. The delineation of the specific ranges delegated to the Internet Number Registry system is provided in RFC 7249.  It is expected that the boundary between IETF-managed and Internet Number Registry-managed parts of the number spaces may change from time to time, with agreement between the IETF and the RIRs.  Potential reasons for changes include the possibility that the IETF may release some previously reserved space for general use, or may reserve some previously unused space for a special purpose.</p><p class="normal">The global Internet community also depends upon the IANA operator for administration of the special-purpose “IN-ADDR.ARPA” and “IP6.ARPA” DNS zones which are associated with IPv4 and IPv6 number resources respectively. These zones are delegated to IANA by the Internet Architecture Board (“IAB”) and “[s]ub-delegations within this hierarchy are undertaken in accordance with the IANA’s address allocation practices” (RFC3172). The IANA operator administers these zones as “agreed technical work items” per the IETF- Internet Corporation for Assigned Names and Numbers (“ICANN”) IANA MoU.  It is important to note that this work is outside the scope of the National Telecommunications and Information Administration (“NTIA”) contract.</p><p class="normal"> </p><p class="normal">The RIR communities also make use of the term “IANA” in the description of their processes, policies and public database records.</p><p class="normal"> </p><p class="normal"><span class="T12">Relevant links:</span></p><p class="normal">IETF-ICANN MoU Concerning the Technical Work of the Internet Assigned Numbers Authority: https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-en</p><p class="normal">“The Internet Numbers Registry System”, RFC 7020: https://tools.ietf.org/html/rfc7020</p><p class="normal">“Internet Numbers Registries”, RFC 7249: https://tools.ietf.org/html/rfc7249 </p><p class="normal"> </p><p class="P13"><span class="T11">II.              Existing, Pre-Transition Arrangements</span></p><p class="P13"><span class="T3">This section should describe how existing IANA-related arrangements work, prior to the transition.</span></p><p class="P22"><span class="T5">II.A.                 Policy Sources</span></p><p class="P13"><span class="T3">This section should identify the specific source(s) of policy which must be followed by the IANA functions operator in its conduct of the services or activities described above.  If there are distinct sources of policy or policy development for different IANA activities, then please describe these separately. For each source of policy or policy development, please provide the following:</span></p><p class="P19">·       <span class="T3">Which IANA service or activity (identified in Section I) is affected.</span></p><p class="P19">·       <span class="T3">A description of how policy is developed and established and who is involved in policy development and establishment.</span></p><p class="P19">·       <span class="T3">A description of how disputes about policy are resolved.</span></p><p class="P19">·       <span class="T3">References to documentation of policy development and dispute resolution processes.</span></p><p class="normal"> </p><p class="P25"><span class="T12">II.A.1.</span>  <span class="T3">Which IANA service or activity (identified in Section I) is affected.</span></p><p class="normal"> </p><p class="normal">The Internet number resource registries.</p><p class="normal"> </p><p class="normal">It is important to note that allocations of Internet number resources from IANA to the RIRs and its registrations in IANA registries, as well as delegations of “IN-ADDR.ARPA” and “IP6.ARPA” domains, described in Section I, are conducted between IANA and the RIRs without involvement by the NTIA.</p><p class="normal"> </p><p class="P23"><span class="T12">II.A.2.</span>  <span class="T3">A description of how policy is developed and established and who is involved in policy development and establishment.</span></p><p class="normal"> </p><p class="P43"><span class="T14">The policies under which the IANA operator manages the global pools of Internet number resources (excluding those address ranges reserved by the IETF for specific technical purposes) are developed and agreed by the five RIR communities via open, transparent and bottom-up policy development processes. Each RIR community engages in its own regional policy development process</span><span class="T16">;</span><span class="T14"> these processes are open to all stakeholders regardless of specific background or interest. Links to each of the five regional Policy Development Processes (“PDPs”) are included under in the RIR Governance Matrix published on the Number Resource Organization (“NRO”) website [</span><a href="http://www.nro.net/about-the-nro/rir-governance-matrix" class="Internet_20_link"><span class="T17">www.nro.net/about-the-nro/rir-governance-matrix</span></a><span class="T14">].</span></p><p class="P45"> </p><p class="P43"><span class="T14">Any individual may submit a global proposal. Each RIR community must ratify an identical version of the proposed policy. The NRO Executive Council (“NRO EC”) then refers the coordinated proposal to the Address Supporting Organization (“ASO”) Address Council (“ASO AC”), which reviews the process by which the proposal was developed and, under the terms of the ASO Memorandum of Understanding (“ASO MoU”), passes it to the ICANN Board of Directors for ratification as a global policy.</span></p><p class="P44"> </p><p class="P43"><span class="T14">There are currently three global policies relating to management of the global pools of IPv4 addresses, IPv6 addresses and AS Numbers [</span><span class="T19">https://</span><a href="http://www.nro.net/policies" class="Internet_20_link"><span class="T19">www.nro.net/policies</span></a><span class="T14">]:</span></p><p class="P44"> </p><p class="P43"><span class="T14">(a) IANA Policy for Allocation of IPv6 Blocks to Regional Internet Registries;</span></p><p class="P43"><span class="T14">(b) IANA Policy for Allocation of ASN Blocks to Regional Internet</span></p><p class="P43"><span class="T14">Registries; and</span></p><p class="P43"><span class="T14">(c) Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA.</span></p><p class="P45"> </p><p class="P43"><span class="T14">There is a fourth global policy agreed by the RIR communities, ICP-2,</span></p><p class="P43"><span class="T14">"Criteria for Establishment of New Regional Internet Registries".</span></p><p class="P45"> </p><p class="P43"><span class="T14">The global Policy Development Process (“gPDP”) described in </span><span class="T16">“</span><span class="T14">Global Policy</span></p><p class="P43"><span class="T14">Development Process Document</span><span class="T16">” </span><span class="T14">[</span><span class="T19">https://www.nro.net/documents/global-policy-development-process</span><span class="T14">] is used for all of the number-related IANA activities described in Section I, but the policy that </span><span class="T16">“</span><span class="T14">IN-ADDR.ARPA</span><span class="T16">”</span><span class="T14"> and </span><span class="T16">“</span><span class="T14">IP6.ARPA</span><span class="T16">”</span><span class="T14"> domains must be delegated following IPv4 and IPv6 address allocations is specified by the IETF (most recently in RFC 3172).</span></p><p class="normal"> </p><p class="P19"><span class="T12">II.A.3.</span>  <span class="T3">A description of how disputes about policy are resolved.</span></p><p class="normal"> </p><p class="normal">The gPDP is formally described in "Attachment A" of the ASO MoU<span class="T12">, </span>signed by ICANN and the RIRs in 2004 (and signed by AFRINIC when it was established as the fifth RIR in 2005). This MoU includes provisions for resolving disputes between ICANN and the RIRs or their communities. It is important to note that while the gPDP allows for the ICANN Board to dispute the outcome of a consensus community decision (escalating to mediation between ICANN and the RIRs), it does not include any role for the IANA contract holder (currently the NTIA). The ASO MoU is an agreement between the RIR communities and ICANN; NTIA has no oversight role in policy-making as regards management of the global Internet number resource pools, and its transition out of its current role would have minimal effect on the policy-making framework.</p><p class="normal"> </p><p class="normal">A separate MoU, the NRO MoU, establishes the NRO as "a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs", and includes provisions for dispute resolutions between RIRs on issues relating to global policy development or implementation.</p><p class="normal"> </p><p class="normal">It is the responsibility of the NRO Number Council (“NRO NC”), a group comprising three community members selected by each of the five RIR communities, to confirm that the documented RIR PDPs have been followed in the development and approval of a new policy or policy change.  Further, this group reviews the policy followed by each of the RIR communities to assure itself that the significant viewpoints of interested parties were adequately considered, and only after this confirmation does it then consider forwarding global policy proposals to the ICANN Board for ratification.</p><p class="normal"> </p><p class="normal">The NRO NC also acts in the role of the ICANN ASO AC, and as such, presents the agreed global policy proposal to the ICANN Board for ratification and operational implementation.</p><p class="normal"> </p><p class="normal">The ICANN Board reviews the received global number resource policy proposals and may ask questions and otherwise consult with the ASO Address Council and/or the individual RIRs acting collectively through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate. If the ICANN Board rejects the proposed policy, it delivers to the ASO ACa statement of its concerns with the proposed policy, including in particular an explanation of the significant viewpoints that were not adequately considered during the regular RIR processes. By agreement of all RIRs, the ASO AC may forward a new proposed policy (either reaffirming the previous proposal or a modified proposal) to the ICANN Board. If the resubmitted proposed policy is rejected for a second time by ICANN, then the RIRs or ICANN shall refer the matter to mediation.</p><p class="normal"/><p class="normal">In case of disputes where mediation has failed to resolve the dispute, the ICANN ASO MoU agreement provides for arbitration via International Chamber of Commerce (ICC) Rules of Arbitration in the jurisdiction of Bermuda or such other location as is agreed between the RIRs and ICANN. It is also worth noting that the RIRs have been participating (as the ASO) in the periodic independent review processes for Accountability and Transparency (ATRT) that is called for per ICANN’s Bylaws.</p><p class="normal"> </p><p class="P23"><span class="T12">II.A.4.</span>  <span class="T3">References to documentation of policy development and dispute resolution processes.</span> </p><p class="P5"> </p><p class="normal"><span class="T12">Relevant links:</span></p><p class="normal">ICANN ASO MoU:<a href="https://www.nro.net/documents/icann-address-supporting-organization-aso-mou" class="Internet_20_link"> </a><a href="https://www.nro.net/documents/icann-address-supporting-organization-aso-mou" class="Internet_20_link"><span class="T18">https://www.nro.net/documents/icann-address-supporting-organization-aso-mou</span></a></p><p class="normal">NRO MoU:<a href="https://www.nro.net/documents/nro-memorandum-of-understanding" class="Internet_20_link"> </a><a href="https://www.nro.net/documents/nro-memorandum-of-understanding" class="Internet_20_link"><span class="T18">https://www.nro.net/documents/nro-memorandum-of-understanding</span></a></p><p class="normal">About the NRO Number Council:<a href="https://www.nro.net/about-the-nro/the-nro-number-council" class="Internet_20_link"> </a><a href="https://www.nro.net/about-the-nro/the-nro-number-council" class="Internet_20_link"><span class="T18">https://www.nro.net/about-the-nro/the-nro-number-council</span></a></p><p class="normal">RIR Governance Matrix:<a href="https://www.nro.net/about-the-nro/rir-governance-matrix" class="Internet_20_link"> </a><a href="https://www.nro.net/about-the-nro/rir-governance-matrix" class="Internet_20_link"><span class="T18">https://www.nro.net/about-the-nro/rir-governance-matrix</span></a></p><p class="normal"><span class="T18">Global Policies: </span><a href="https://www.nro.net/policies" class="Internet_20_link">https://www.nro.net/policies</a></p><p class="P20"> </p><p class="P20"> </p><p class="P20"> </p><p class="P20"> </p><p class="P20"><span class="T5">II.B.                  Oversight and Accountability</span></p><p class="normal"><span class="T3"> </span></p><p class="normal"><span class="T3">This section should describe all the ways in which oversight is conducted over IANA’s provision of the services and activities listed in Section I and all the ways in which IANA is currently held accountable for the provision of those services. For each oversight or accountability mechanism, please provide as many of the following as are applicable:</span></p><p class="normal"><span class="T3"> </span></p><p class="P19">·       <span class="T3">Which IANA service or activity (identified in Section I) is affected.</span></p><p class="P19">·       <span class="T3">If the policy sources identified in Section II.A are affected, identify which ones are affected and explain in what way.</span></p><p class="P19">·       <span class="T3">A description of the entity or entities that provide oversight or perform accountability functions, including how individuals are selected or removed from participation in those entities.</span></p><p class="P19">·       <span class="T3">A description of the mechanism (e.g., contract, reporting scheme, auditing scheme, etc.). This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is transparent and the terms under which the mechanism may change.</span></p><p class="P19">·       <span class="T3">Jurisdiction(s) in which the mechanism applies and the legal basis on which the mechanism rests.</span>  </p><p class="normal"> </p><p class="P19"><span class="T12">II.B.1.</span>  <span class="T3">Which IANA service or activity (identified in Section I) is affected.</span></p><p class="normal"/><p class="normal">The Internet number resource registries.</p><p class="normal"> </p><p class="P23"><span class="T12">II.B.2.</span>  <span class="T3">If the policy sources identified in Section II.A are affected, identify which ones are affected and explain in what way.</span></p><p class="normal"> </p><p class="P2"><span class="T22">A</span><span class="T23"> </span><span class="T22">decision</span><span class="T23"> </span><span class="T22">by</span><span class="T24"> </span><span class="T22">the</span><span class="T23"> </span><span class="T22">NTIA</span><span class="T23"> </span><span class="T22">to</span><span class="T23"> </span><span class="T22">discontinue</span><span class="T25"> </span><span class="T22">its</span><span class="T24"> </span><span class="T22">stewardship</span><span class="T23"> </span><span class="T22">of</span><span class="T26"> </span><span class="T22">the</span><span class="T23"> </span><span class="T22">IANA</span><span class="T23"> </span><span class="T22">functions,</span><span class="T26"> </span><span class="T22">and</span><span class="T23"> </span><span class="T22">therefore</span><span class="T23"> </span><span class="T22">its</span></p><p class="P3"><span class="T22">contractual</span><span class="T27"> </span><span class="T22">relationship</span><span class="T28"> </span><span class="T22">with</span><span class="T29"> </span><span class="T22">the</span><span class="T29"> </span><span class="T22">IANA</span><span class="T28"> </span><span class="T22">functions</span><span class="T30"> </span><span class="T22">operator,</span><span class="T30"> </span><span class="T22">would</span><span class="T29"> </span><span class="T22">not</span><span class="T30"> </span><span class="T22">have</span><span class="T28"> </span><span class="T22">any</span><span class="T30"> </span><span class="T22">significant</span><span class="T30"> </span><span class="T22">impact</span><span class="T31"> </span><span class="T22">on</span><span class="T27"> </span><span class="T22">the</span><span class="T27"> </span><span class="T22">continuity</span><span class="T32"> </span><span class="T22">of</span><span class="T25"> </span><span class="T22">Internet</span><span class="T25"> </span><span class="T22">number-related</span><span class="T27"> </span><span class="T22">IANA</span><span class="T30"> </span><span class="T22">services</span><span class="T27"> </span><span class="T22">currently</span><span class="T32"> </span><span class="T22">provided</span><span class="T27"> </span><span class="T22">by</span><span class="T27"> </span><span class="T22">ICANN.</span><span class="T29"> </span><span class="T22">However, it</span><span class="T25"> </span><span class="T22">would</span><span class="T25"> </span><span class="T22">remove</span><span class="T25"> </span><span class="T22">a</span><span class="T25"> </span><span class="T22">significant</span><span class="T26"> </span><span class="T22">element</span><span class="T23"> </span><span class="T22">of</span><span class="T23"> </span><span class="T22">oversight</span><span class="T23"> </span><span class="T22">from</span><span class="T32"> </span><span class="T22">the</span><span class="T25"> </span><span class="T22">current</span><span class="T23"> </span><span class="T22">system.</span></p><p class="P46"> </p><p class="P47"><span class="T14">There</span><span class="T33"> </span><span class="T14">is</span><span class="T34"> </span><span class="T14">no</span><span class="T34"> </span><span class="T14">contractual</span><span class="T35"> </span><span class="T14">obligation</span><span class="T36"> </span><span class="T14">directly</span><span class="T36"> </span><span class="T14">to</span><span class="T36"> </span><span class="T14">the</span><span class="T36"> </span><span class="T14">Internet</span><span class="T34"> </span><span class="T14">number</span><span class="T34"> </span><span class="T14">resource</span><span class="T36"> </span><span class="T14">community</span><span class="T36"> </span><span class="T14">for</span><span class="T33"> </span><span class="T14">the</span><span class="T37"> </span><span class="T14">IANA</span><span class="T36"> </span><span class="T14">operator</span><span class="T36"> </span><span class="T14">to</span><span class="T38"> </span><span class="T14">provide</span><span class="T38"> </span><span class="T14">IANA</span><span class="T36"> </span><span class="T14">registry</span><span class="T36"> </span><span class="T14">services</span><span class="T34"> </span><span class="T14">for</span><span class="T36"> </span><span class="T14">the</span><span class="T34"> </span><span class="T14">Internet</span><span class="T34"> </span><span class="T14">number</span><span class="T34"> </span><span class="T14">registries.  ICANN has historically provided</span><span class="T33"> </span><span class="T14">IANA</span><span class="T15"> </span><span class="T14">services</span><span class="T39"> </span><span class="T14">for</span><span class="T35"> </span><span class="T14">the</span><span class="T33"> </span><span class="T14">Internet</span><span class="T35"> </span><span class="T14">number</span><span class="T39"> </span><span class="T14">registries</span><span class="T35"> </span><span class="T14">under the terms</span><span class="T40"> </span><span class="T14">of</span><span class="T39"> </span><span class="T14">the</span><span class="T36"> </span><span class="T14">NTIA</span><span class="T34"> </span><span class="T14">IANA</span><span class="T36"> </span><span class="T14">Functions</span><span class="T33"> </span><span class="T14">contract</span><span class="T35"> </span><span class="T14">and</span><span class="T34"> </span><span class="T14">therefore</span><span class="T36"> </span><span class="T14">IANA</span><span class="T34"> </span><span class="T14">services</span><span class="T34"> </span><span class="T14">for</span><span class="T33"> </span><span class="T14">the</span><span class="T34"> </span><span class="T14">Internet</span><span class="T35"> </span><span class="T14">number</span><span class="T33"> </span><span class="T14">registries</span><span class="T40"> </span><span class="T14">are</span><span class="T34"> </span><span class="T14">presently</span><span class="T36"> </span><span class="T14">subject</span><span class="T33"> </span><span class="T14">to</span><span class="T36"> </span><span class="T14">change</span><span class="T38"> </span><span class="T14">per</span><span class="T34"> </span><span class="T14">that</span><span class="T34"> </span><span class="T14">agreement.</span></p><p class="normal"> </p><p class="P19"><span class="T12">II.B.3.</span>  <span class="T3">A description of the entity or entities that provide oversight or perform accountability </span></p><p class="normal"><span class="T3">functions, including how individuals are selected or removed from participation in those entities.</span></p><p class="normal"> </p><p class="normal">All institutional actors with a role in management of Internet number resources are accountable to the open communities that make and agree on the policies under which those resources are distributed and registered. The mechanisms used to ensure and enforce this accountability differ for each of these actors.</p><p class="normal"> </p><p class="P23"><span class="T12">II.B.3.i. NTIA</span></p><p class="normal"> </p><p class="normal">ICANN, as the current operator of the IANA functions, is obligated by the NTIA agreement to carry out management of the global IP address and AS Number pools according to policies developed by the communities. </p><p class="normal"> </p><p class="normal">While the IANA operator escalation and reporting mechanisms are public in nature, the Internet number community is primarily represented in oversight of the IANA operator performance by the RIRs, which are member-based based organizations with elected governance boards. Currently, the NTIA does not have an oversight role in this regard.</p><p class="normal"> </p><p class="normal">The ultimate consequence of failing to meet the performance standards or reporting requirements is understood to be a decision by the contracting party (the NTIA) to terminate or not renew the IANA functions agreement with the current contractor (ICANN).  </p><p class="normal"> </p><p class="P23"><span class="T12">II.B.3.ii. The Regional Internet Registries</span></p><p class="normal"> </p><p class="P48"><span class="T14">Administration by the IANA operator</span><span class="T41"> </span><span class="T14">consists</span><span class="T42"> </span><span class="T14">predominantly</span><span class="T42"> </span><span class="T14">of</span><span class="T43"> </span><span class="T14">processing</span><span class="T44"> </span><span class="T14">of</span><span class="T43"> </span><span class="T14">requests</span><span class="T45"> </span><span class="T14">from</span><span class="T38"> </span><span class="T14">the</span><span class="T36"> </span><span class="T14">RIRs</span><span class="T34"> </span><span class="T14">for</span><span class="T34"> </span><span class="T14">issuance</span><span class="T36"> </span><span class="T14">of</span><span class="T35"> </span><span class="T14">additional</span><span class="T35"> </span><span class="T14">number</span><span class="T34"> </span><span class="T14">resources. </span><span class="T46"> </span><span class="T14">The</span><span class="T36"> </span><span class="T14">five</span><span class="T47"> </span><span class="T14">RIRs</span><span class="T48"> </span><span class="T14">are</span><span class="T48"> </span><span class="T14">intimately</span><span class="T48"> </span><span class="T14">familiar</span><span class="T48"> </span><span class="T14">with</span><span class="T48"> </span><span class="T14">global</span><span class="T38"> </span><span class="T14">number</span><span class="T48"> </span><span class="T14">resource</span><span class="T48"> </span><span class="T14">policies</span><span class="T48"> </span><span class="T14">under</span><span class="T49"> </span><span class="T14">which</span><span class="T34"> </span><span class="T14">the</span><span class="T36"> </span><span class="T14">requests</span><span class="T34"> </span><span class="T14">are</span><span class="T36"> </span><span class="T14">made</span><span class="T36"> </span><span class="T14">and</span><span class="T34"> </span><span class="T14">maintain</span><span class="T36"> </span><span class="T14">communications</span><span class="T34"> </span><span class="T14">with</span><span class="T36"> </span><span class="T14">the</span><span class="T36"> </span><span class="T14">IANA</span><span class="T36"> </span><span class="T14">operations</span><span class="T36"> </span><span class="T14">team</span><span class="T50"> </span><span class="T14">throughout</span><span class="T39"> </span><span class="T14">the</span><span class="T34"> </span><span class="T14">request</span><span class="T39"> </span><span class="T14">process. </span><span class="T51"> </span></p><p class="normal"> </p><p class="normal">The RIRs are not-for-profit membership associations, and as such are accountable to their members by law. The specific governance processes for each RIR differ depending on where they have been established and the decisions made by their membership, but in all RIRs, members have the right to vote individuals onto the governing Board and to vote on matters related to the respective RIR.</p><p class="normal"> </p><p class="normal">At the same time, an RIR's registration and allocation practices are directed by policies developed by its community. Each RIR community's PDP defines how these policies are developed, agreed and accepted for operational implementation.</p><p class="normal"> </p><p class="normal">The corporate governance documents and PDPs of each RIR and its community are accessible via the RIR Governance Matrix, published on the NRO website.</p><p class="normal"> </p><p class="P23"><span class="T12">II.B.4.</span>  <span class="T3">A description of the mechanism (e.g., contract, reporting scheme, auditing scheme, etc.). This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is transparent and the terms under which the mechanism may change.</span> </p><p class="normal"> </p><p class="normal">The NTIA IANA Agreement currently defines obligations of the IANA operator for Internet number resources. </p><p class="normal"> </p><p class="normal">This obligation is specifically noted in section C.2.9.3 of the NTIA agreement:</p><p class="normal"> </p><p class="P26"><span class="T3">C.2.9.3 Allocate Internet Numbering Resources --The Contractor shall have responsibility for allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space </span><span class="T5">based on established guidelines and policies as developed by interested and affected parties as enumerated in Section C.1.3.</span></p><p class="normal"> </p><p class="normal">The NTIA agreement also lays out specific deliverables for the IANA operator (ICANN) to produce as a condition of the agreement (see "Section F – Deliveries and Performance"), including performance standards developed in cooperation with the affected parties (in the case of the Internet number resource pools, the affected parties include the RIRs and their communities), customer complaint procedures and regular performance reporting.</p><p class="normal"> </p><p class="normal">These deliverables are met by ICANN via monthly reporting on their performance in processing requests for the allocation of Internet number resources; these reports include IANA operator performance against key metrics of accuracy, timeliness, and transparency, as well as the performance metrics for individual requests. The IANA operations team also provides escalation procedures for use in resolving any issues with requests, as per the "IANA Customer Service Complaint Resolution Process".</p><p class="normal"> </p><p class="P23"><span class="T12">II.B.5.</span>  <span class="T3">Jurisdiction(s) in which the mechanism applies and the legal basis on which the mechanism rests.</span>  </p><p class="normal"> </p><p class="normal">Jurisdiction for this current mechanism is the United States of America under applicable Federal government contracting laws and regulations.</p><p class="normal"> </p><p class="normal"><span class="T12">Relevant links:</span></p><p class="normal">NTIA IANA Agreement:<a href="http://www.ntia.doc.gov/page/iana-functions-purchase-order" class="Internet_20_link"> </a><a href="http://www.ntia.doc.gov/page/iana-functions-purchase-order" class="Internet_20_link"><span class="T18">http://www.ntia.doc.gov/page/iana-functions-purchase-order</span></a></p><p class="normal">ICANN ASO MoU:<a href="https://www.nro.net/documents/icann-address-supporting-organization-aso-mou" class="Internet_20_link"> </a><a href="https://www.nro.net/documents/icann-address-supporting-organization-aso-mou" class="Internet_20_link"><span class="T18">https://www.nro.net/documents/icann-address-supporting-organization-aso-mou</span></a></p><p class="normal">NRO MoU:<a href="https://www.nro.net/documents/nro-memorandum-of-understanding" class="Internet_20_link"> </a><a href="https://www.nro.net/documents/nro-memorandum-of-understanding" class="Internet_20_link"><span class="T18">https://www.nro.net/documents/nro-memorandum-of-understanding</span></a></p><p class="normal">IANA Customer Service Complaint Resolution Process: <a href="http://www.iana.org/help/escalation-procedure" class="Internet_20_link"><span class="T18">http://www.iana.org/help/escalation-procedure</span></a></p><p class="normal">IANA Performance Standards Metrics Report:</p><p class="normal"><a href="http://www.iana.org/performance/metrics" class="Internet_20_link"><span class="T18">http://www.iana.org/performance/metrics</span></a></p><p class="normal">RIR Governance Matrix:<a href="https://www.nro.net/about-the-nro/rir-governance-matrix" class="Internet_20_link"> </a><a href="https://www.nro.net/about-the-nro/rir-governance-matrix" class="Internet_20_link"><span class="T18">https://www.nro.net/about-the-nro/rir-governance-matrix</span></a></p><p class="normal"> </p><p class="P16"> </p><p class="P16"> </p><p class="P13"><span class="T11">III.            Proposed Post-Transition Oversight and Accountability Arrangements</span></p><p class="P13"><span class="T3">This section should describe what changes your community is proposing to the arrangements listed in Section II.B in light of the transition. If your community is proposing to replace one or more existing arrangements with new arrangements, that replacement should be explained and all of the elements listed in Section II.B should be described for the new arrangements. Your community should provide its rationale and justification for the new arrangements.</span></p><p class="P13"><span class="T3">If your community’s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described here.</span></p><p class="P13"><span class="T3">If your community is not proposing changes to arrangements listed in Section II.B, the rationale and justification for that choice should be provided here.</span></p><p class="P23"><span class="T12">III.A.</span> The elements of this proposal are as follows:</p><p class="normal"> </p><ol><li><p class="P6" style="margin-left:0cm;"><span style="display:block;float:left;min-width:1.27cm;">(1)</span>ICANN to continue as the IANA functions operator on number resources;<span class="odfLiEnd"/> </p></li><li><p class="P6" style="margin-left:0cm;"><span style="display:block;float:left;min-width:1.27cm;">(2)</span>Intellectual property rights (IPR) related to the provision of the IANA services stay with the community;<span class="odfLiEnd"/> </p></li><li><p class="P6" style="margin-left:0cm;"><span style="display:block;float:left;min-width:1.27cm;">(3)</span>Service level agreement with the IANA functions operator on number resources; and<span class="odfLiEnd"/> </p></li><li><p class="P6" style="margin-left:0cm;"><span style="display:block;float:left;min-width:1.27cm;">(4)</span>Establishment of a Review Committee, with representatives from each RIR, to advise the NRO EC on the review of the IANA functions operator’s performance and meeting of identified service levels. <span class="odfLiEnd"/> </p></li></ol><p class="normal"> </p><p class="P23"><span class="T12">III.A.1.  ICANN to continue as the IANA functions operator on number resources</span></p><p class="normal"> </p><p class="normal">To maintain stability and continuity in operations of the Internet number-related IANA services, very minimal changes to the arrangements listed in Section II.B are proposed, including the identification of the proposed initial IANA functions operator.  As noted in numerous NRO communications over the past decade, the RIRs have been very satisfied with the performance of ICANN in the role of IANA functions operator. Taking this into account, and considering the strong desires expressed in the five RIR communities' IANA stewardship discussions for stability and a minimum of operational change, the Internet numbering community believes that ICANN should remain in the role of IANA functions operator for at least the initial term of the new contract.</p><p class="normal"> </p><p class="normal">A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system.</p><p class="normal"> </p><p class="normal">While there are no concrete needs or plans at this point, the NRO EC may in the future determine that the IANA functions related to number resources should be transferred to a different contractor.  In such a case, selection of a new contractor shall be conducted in a fair, open and transparent process, in line with applicable industry best practices and standards.  </p><p class="normal"> </p><p class="P23"><span class="T12">III.A.2.  IPR related to the provision of the IANA services stay with the community</span></p><p class="normal"> </p><p class="normal">There are several intellectual properties related to the provision of the IANA services whose status should be clarified as part of the transition. Namely, the "IANA" trademark, the "IANA.ORG" domain name, and public databases related to the performance of the IANA function.</p><p class="normal"> </p><p class="normal">It is important that through the stewardship transition the IPR status of the registries is clear and ensures free unlimited access to the public registry data. It is the expectation of the RIR communities that the public number resource registries are in the public domain.  </p><p class="normal"> </p><p class="normal">It is also the expectation of the RIR communities that non-public information related to the IANA number resource registries and corresponding services, including the provision of reverse DNS delegation in IN-ADDR.ARPA and IP6.ARPA, is managed by the IANA operator and will be transferred to its successor(s) along with relevant rights.  </p><p class="normal"> </p><p class="normal">It is the preference of the RIR communities that all relevant parties acknowledge that fact as part of the transition.</p><p class="normal"/><p class="normal">With regards to the IANA trademark and the iana.org domain it is the expectation of the RIR communities that both are associated with the IANA function and not with a particular IANA functions operator. Identifying an organisation, not associated with an IANA operator, that holds these assets permanently will facilitate a smooth transition should another operator (or operators) be selected at some point in the future. It is the preference of the RIR communities that the IANA trademark and the IANA.ORG domain name be transferred to an entity independent of the IANA functions operator that will ensure these assets are used purposefully in a non-discriminatory manner for the benefit of all operational communities. From the RIR communities' perspective, the IETF Trust would be an acceptable candidate for this role.</p><p class="normal"> </p><p class="normal">The transfer of the IANA trademark and iana.org domain to the IETF Trust will require additional coordination with the other affected communities of the IANA functions, namely protocol parameters and names.</p><p class="normal"> </p><p class="P23"><span class="T12">III.A.3. Service level agreement with the IANA functions operator on number resources</span></p><p class="normal"> </p><p class="normal">This proposal assumes that specific IANA customers (i.e. the numbers community, the protocol parameters community and the names community) will have independent arrangements with the IANA operator relating to maintenance of the specific registries for which they are responsible. At the same time, the Internet numbers community wishes to emphasize the importance of communication and coordination between these communities to ensure the stability of IANA functions operation. Such communication and coordination would be especially vital should the three communities reach different decisions regarding the identity of the IANA functions operator going forward. Efforts to facilitate this communication and coordination should be undertaken by the affected communities via processes separate to this stewardship transition process.   </p><p class="normal"> </p><p class="normal">The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA functions operator's accountability to the open, bottom-up numbers community.  The proposal attempts to ensure the continuity of processes and mechanisms that have proved successful and with which the community is satisfied.  </p><p class="normal"> </p><ul><li><p class="P7" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The services provided by the IANA functions operator in relation to the Internet number-related functions remain unchanged<span class="odfLiEnd"/> </p></li><li><p class="P7" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span><span class="odfLiEnd"/> </p></li></ul><p class="normal">The oversight and accountability mechanisms detailed in Section II.B remain unchanged</p><ul><li><p class="P7" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The policy sources identified in Section II.A are unaffected<span class="odfLiEnd"/> </p></li><li><p class="P7" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The entities that provide oversight or perform accountability functions (the RIRs) remain the same<span class="odfLiEnd"/> </p></li><li><p class="P7" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The consequence for failure to meet performance standards remains termination or decision not to renew the IANA functions agreement with the then-current contractor<span class="odfLiEnd"/> </p></li></ul><p class="normal"> </p><p class="normal">The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five RIRs. The contract, essentially an <span class="T12">IANA Service Level Agreement</span>, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services.</p><p class="normal"> </p><p class="normal">It is expected that RIR staff will draft the specific language of this agreement, and that the drafting process will be guided by the principles listed below. References to relevant sections of the current NTIA agreement are also noted, as it is expected the new agreement will share many of the same contractual goals and mechanisms. </p><p class="normal"> </p><p class="normal"> </p><p class="normal"> </p><p class="normal"> </p><p class="normal"> </p><p class="normal"> </p><p class="normal"><span class="T3">IANA Agreement Principles</span></p><p class="normal">i. <span class="T12">Applicability of ASO MoU - Separation of Policy Development and</span> <span class="T13">Operational Roles </span></p><p class="Standard"><span class="T13"> </span></p><p class="Standard"><span class="T4">Principle: </span></p><p class="Standard"><span class="T52">The IANA Operator will merely execute the global policies adopted according to the global Policy Development Process defined in the ASO MoU.</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52"> C.2.4, C.2.5</span></p><p class="P40"> </p><p class="P37"><span class="T13">ii. Description of Serviced Provided by the IANA Operator to RIRs </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">The IANA Operator will maintain the global Internet number resource registries.  The IANA Operator will distribute Internet number Resources to the RIRs in accordance with the specific processes and timelines described in this section of the agreement.  The IANA Operator will delegate subdomains below the IN-ADDR.ARPA and IP6.ARPA domains in accordance with the allocation of IPv4 and IPv6 addresses.</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">C.2.9.3</span></p><p class="P40"/><p class="P37"><span class="T13">iii. Obligation to Issue Reports on Transparency and Accountability </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">The IANA Operator will commit to certain obligations so as to perform the function as expected by the community and will be obliged to periodically issue reports illustrating its compliance with the community’s expectations. </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">C.2.6, C.2.7, C.2.8</span></p><p class="P40"> </p><p class="P37"><span class="T13">iv. Security Requirements – Performance Metric Requirements – Audit Requirements </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">The IANA Operator will commit to specific security standards, metric requirements and audit requirements and will be obliged to periodically issue reports illustrating its compliance with them. </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">C.3, C.4, C.5</span></p><p class="P40"> </p><p class="P40"> </p><p class="P40"> </p><p class="P40"> </p><p class="P37"><span class="T13">v. Review of the IANA Operations  </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">The RIRs will perform reviews to assess whether the IANA Operator complies with all requirements described in the agreement whenever they deem appropriate. The IANA Operator will be obliged to facilitate this review. </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">N/A</span></p><p class="P28"> </p><p class="P37"><span class="T13">vi. Failure to Perform </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">If the IANA Operator fails to perform as agreed in this agreement, there will be specific consequences. One of these consequences may be termination of the contract. </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">E.2, I.67</span></p><p class="P40"> </p><p class="P37"><span class="T13">vii. Term and Termination</span><span class="T52"> </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">RIRs will be able to periodically review the agreement and evaluate whether they want to renew the agreement. </span></p><p class="P40"> </p><p class="Standard"><span class="T52">Either party may terminate the agreement with reasonable prior notice.</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">Page 2 of Award/Contract, I.51, I.52, I.53</span></p><p class="P40"> </p><p class="P37"><span class="T13">viii. Continuity of Operations</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">If, at the end of the contract term, the RIRs decide to sign an agreement for operation of the number-related IANA functions with a different party, the previous IANA Operator will be obliged to ensure an orderly transition of the function while maintaining continuity and security of operations.</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">C.7.3 and I.61 </span></p><p class="P40"> </p><p class="P40"> </p><p class="P40"> </p><p class="P40"> </p><p class="P40"> </p><p class="P37"><span class="T13">ix. Intellectual Property Rights and Rights Over Data </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">Both parties acknowledge that the data of the public number resource registries remain in the public domain. The RIRs will have unlimited rights in all other data delivered under this agreement and in all other data first produced in the performance of this agreement. </span></p><p class="P40"> </p><p class="Standard"><span class="T52">If the IANA operator becomes the owner of intellectual property rights through the performance of this agreement, these rights will be transferred to the public domain or to the RIRs. In case the legislation does not allow such transfer, the IANA operator must grant appropriate licenses for ongoing use of the relevant intellectual property.</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">H.4, H.5</span></p><p class="P40"> </p><p class="Standard"><span class="T13">x. Resolution of Disputes</span></p><p class="P40"> </p><p class="Standard"><span class="T4">Principle:</span></p><p class="Standard"><span class="T52">Disputes between the parties related to the SLA will be resolved through arbitration. </span></p><p class="P40"> </p><p class="Standard"><span class="T4">Relevant section(s) in the NTIA contract:</span></p><p class="Standard"><span class="T52">N/A</span></p><p class="normal"> </p><p class="P23"><span class="T12">III.A.4.  Establishment of a Review Committee</span></p><p class="normal"> </p><p class="normal">To ensure the service level defined in the proposed contract is maintained and provided by the IANA functions operator, the NRO EC will conduct periodic reviews of the service level of the IANA number resource functions that serves each RIR and their respective communities.  </p><p class="normal"> </p><p class="normal">The NRO EC shall establish a Review Committee that will advise and assist the NRO EC in its periodic review.  The Review Committee will, as needed, undertake a review of the level of service received from the IANA functions operator and report to the NRO EC any concerns regarding the performance of the IANA functions operator, including especially any observed failure or near-failure by the IANA functions operator to meet its contractual obligations under the proposed contract.  Any such Review Committee will advise the NRO EC in its capacity solely to oversee the performance of the IANA number resource functions and the Review Committee’s advice and comment will be limited to the processes followed in the IANA functions operator’s performance under the proposed contract.  Activities of the Review Committee shall be conducted in an open and transparent manner.  Reports from the Review Committee shall be published.</p><p class="normal"> </p><p class="normal">The Review Committee should be a team composed of suitably qualified representatives from each RIR region.</p><p class="P22"><span class="T5">III.B.</span><span class="T3">  If your community’s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described here.</span></p><p class="normal">This proposal carries no implication for the interface between IANA functions and existing policy arrangements described in Section II.A.  The text in "Attachment A" of the ICANN ASO MoU meets the current and anticipated requirements for a community-driven global policy development process. </p><p class="normal"> </p><p class="normal">As an additional measure of security and stability, the RIRs have documented their individual accountability and governance mechanisms, and asked the community-based Number Resource Organization Number Council (NRO NC) to undertake a review of these mechanisms and make recommendations for improvements that may be warranted given the nature of the stewardship transition for Internet number resources.</p><p class="normal"> </p><p class="P13"><span class="T11">IV.            Transition Implications</span></p><p class="P13"><span class="T3">This section should describe what your community views as the implications of the changes it proposed in Section III. These implications may include some or all of the following, or other implications specific to your community:</span></p><p class="P19">·       <span class="T3">Description of operational requirements to achieve continuity of service and possible new service integration throughout the transition.</span></p><p class="P19">·       <span class="T3">Risks to operational continuity and how they will be addressed.</span></p><p class="P19">·       <span class="T3">Description of any legal framework requirements in the absence of the NTIA contract.</span></p><p class="P19">·       <span class="T3">Description of how you have tested or evaluated the workability of any new technical or operational methods proposed in this document and how they compare to established arrangements.</span></p><p class="P19"> </p><p class="P19"><span class="T12">IV.A.</span>  <span class="T3">Description of operational requirements to achieve continuity of service and possible new service integration throughout the transition.</span></p><p class="P19">·       <span class="T3">Risks to operational continuity and how they will be addressed.</span></p><p class="normal"> </p><p class="normal">The intent of the proposal described above is to:</p><p class="normal"> </p><p class="P19">1. <span> Minimize risks to operational continuity of the management of the Internet number-related IANA functions, and;</span></p><p class="P19">2. <span> Retain the existing framework for making those policies that describe the management of the global Internet number resource pools, as this framework is already structured to ensure open, bottom-up development of such policies.</span></p><p class="normal"> </p><p class="normal">Under current arrangements, the NTIA is responsible for extending or renewing the IANA functions agreement, and setting the terms of that contract. A new contract with the five RIRs and the IANA functions operator as signatories would shift the responsibility for renewing, setting terms or terminating the contract to the RIRs, who would coordinate their decisions via the NRO EC (made up of the RIR Directors and Chief Executives). Decisions made regarding the contract would be based on operational circumstances, past performance and input from open, regional communities.</p><p class="normal"> </p><p class="normal">The shift from the existing contractual arrangement to another contractual arrangement (perhaps relying on a set of distinct contracts) covering the IANA functions operator’s ongoing management of all the IANA functions should result in no operational change for management of the global Internet number resource pools. This will help minimize any operational or continuity risks associated with stewardship transition.</p><p class="normal">By building on the existing Internet registry system (which is open to participation from all interested parties) and its structures, the proposal reduces the risk associated with creating new organizations whose accountability is unproven.</p><p class="normal"> </p><p class="normal">The necessary agreement proposed for IANA operation services for the Internet number registries can be established well before the NTIA target date for transition (September 2015), as there are no changes to existing service levels or reporting that are being proposed, only a change in contracting party to align with the delegated policy authority.</p><p class="normal"> </p><p class="P19"><span class="T12">IV.B.</span>  <span class="T3">Description of any legal framework requirements in the absence of the NTIA contract.</span></p><p class="normal"> </p><p class="normal">The necessary legal framework in the absence of the NTIA contract will be fulfilled by the proposed agreement between the IANA functions operator and the five RIRs.  As stated in Section III above, the contract, essentially an <span class="T12">IANA Service Level Agreement</span>, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services.  The contract would also provide for jurisdiction and governing law regarding the new arrangement.</p><p class="normal"> </p><p class="P19"><span class="T12">IV.C.</span>  <span class="T3">Description of how you have tested or evaluated the workability of any new technical or operational methods proposed in this document and how they compare to established arrangements.</span></p><p class="P19">·       <span class="T3">Risks to operational continuity and how they will be addressed.</span></p><p class="normal"> </p><p class="normal">This proposal does not propose any new technical or operational methods.  There is inclusion of a proposed Review Committee to be established by the five RIRs acting cooperatively and coordinating through the NRO EC; however, this does not carry any new operational method as the IANA functions operator would remain accountable to the party with whom it is contracting, in this case, the five RIRs in place of the NTIA.  The proposed Review Committee is a tool for the five RIRs to, together with their respective communities collectively, evaluate and review performance of the IANA functions provided.</p><p class="normal"> </p><p class="P13"><span class="T11">V.             NTIA Requirements</span></p><p class="normal"><span class="T3">Additionally, NTIA has established that the transition proposal must meet the following five requirements:</span></p><p class="normal"><span class="T3"> </span></p><p class="P19">·       <span class="T3">Support and enhance the multistakeholder model;</span></p><p class="P19">·       <span class="T3">Maintain the security, stability, and resiliency of the Internet DNS;</span></p><p class="P19">·       <span class="T3">Meet the needs and expectation of the global customers and partners of the IANA services;</span></p><p class="P19">·       <span class="T3">Maintain the openness of the Internet.</span></p><p class="P19">·       <span class="T3">The proposal must not replace the NTIA role with a government-led or an inter-governmental organization solution.</span></p><p class="P20"><span class="T3"> </span></p><p class="normal"><span class="T3">This section should explain how your community’s proposal meets these requirements and how it responds to the global interest in the IANA functions.</span></p><p class="P27"> This proposal addresses each of the NTIA's requirements: <br/><br/><span class="T5">V.A.</span><span class="T3"> Support and enhance the multi-stakeholder model;</span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">The RIRs are not-for-profit membership organisations accountable to their membership and communities. The processes developed by these communities over time are open, bottom-up and inclusive of all stakeholders, ensuring the opportunity for anyone with an interest in management of Internet number resources to participate in policy-making. </span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">Shifting stewardship of the IANA functions to the RIRs and their communities is an important step in acknowledging the maturity and stability of the multi-stakeholder governance model, and in recognizing the success and de facto authority of that model under the current arrangement.</span></p><p class="P32"><span class="T53"><br/></span><span class="T54">V.B.</span><span class="T55">  Maintain the security, stability, and resiliency of the Internet DNS;</span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">No changes are proposed in this document that affect the security, stability, and resiliency of the DNS.</span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">This proposal is chiefly concerned with Internet number resources, which also need security, stability, and resiliency.  The existing operational and policy-making structures relating to management of the global Internet number resource pools have served the Internet community well over time, and the RIR communities have strongly expressed a desire for stability and operational continuity of this critical element of the Internet infrastructure. Accordingly, this proposal suggests minimal changes to existing processes.</span></p><p class="P33"> </p><p class="P33"> </p><p class="P33"> </p><p class="P32"><span class="T53"><br/></span><span class="T54">V.C.</span><span class="T55">  Meet the needs and expectation of the global customers and partners of the IANA services;</span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">The RIRs and their communities are the primary global customers for the Internet number resource-related IANA functions. As such, they have on numerous occasions expressed their satisfaction with the current management of the IANA functions, which has ensured the effective implementation of policies developed by the community and the efficient distribution of number resources to the RIRs. This proposal has been developed by the RIR communities, as customers of the IANA number-related functions, and meets their need for continuity and stability in the operation of the number-related IANA functions. It does this by solidifying the IANA functions operator's accountability to the RIRs and their communities in relation to the number-related IANA functions. </span></p><p class="P32"><span class="T53"><br/></span><span class="T54">V.D.</span><span class="T55">  Maintain the openness of the Internet. </span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">An "open" Internet relies on the effective implementation of policies developed via open, inclusive, bottom-up processes, ensuring the transparent and coordinated distribution and registration of Internet number resources. The Internet numbers community has a longstanding history of bottom-up, inclusive, open and transparent policy-making and operational processes (including the transparent publication of all registration information). By building on the structures developed by the Internet numbers community, this proposal ensures that in this regard, the openness of the Internet is maintained. </span></p><p class="P31"> </p><p class="No_20_Spacing"><span class="T53">In addition, the proposed community Review Committee will ensure bottom-up community involvement in the open and transparent evaluation of the IANA functions operation.</span></p><p class="P32"><span class="T53"><br/></span><span class="T54">V.E.</span><span class="T55">  The proposal must not replace the NTIA role with a government-led or an inter-governmental organization solution. </span></p><p class="P30"> </p><p class="Plain_20_Text"><span class="T53">This proposal does not replace the NTIA role with a government-led or an inter-governmental organization solution.  This proposal will place the RIRs in the role currently occupied by the NTIA. The RIRs are not-for-profit organisations, accountable to their memberships and their communities. Those communities are open to anyone that wishes to contribute and they include participants from all Internet stakeholder groups, including operators, civil society, business, the technical community and governments. Open, community-driven and consensus-based policy development processes mean that no single stakeholder group has a dominant role in policy-making. </span></p><p class="normal"> </p><p class="normal"><span class="T11">VI.            Community Process</span></p><p class="normal"><span class="T3"> </span></p><p class="P13"><span class="T3">This section should describe the process your community used for developing this proposal, including:</span></p><p class="P19">·       <span class="T3">The steps that were taken to develop the proposal and to determine consensus.</span></p><p class="P19">·       <span class="T3">Links to announcements, agendas, mailing lists, consultations and meeting proceedings.</span></p><p class="P19">·       <span class="T3">An assessment of the level of consensus behind your community’s proposal, including a description of areas of contention or disagreement.</span></p><p class="normal"> </p><p class="normal">The Internet numbers community process is "bottom-up", transparent and inclusive, with the initial discussions and proposal elements agreed on a regional basis in each RIR region community. The consensus output of these five community discussions has been consolidated in a single global proposal by representatives from each RIR region, however the ensuring feedback to and from regional discussion forums has been a priority for all of those representatives. </p><p class="normal"> </p><p class="normal">This process was deliberately modeled on the longstanding community processes that the RIR communities have successfully employed for policy-making at the regional and global levels. It reflects the strong commitment emerging from all community discussions to employing proven structures and mechanisms in this process. </p><p class="normal"> </p><p class="P13">The proposal development can therefore be seen as two distinct phases, first at the RIR community level and then at the global level. It is important to emphasize that neither of these phases occurred in isolation – throughout the first phase, there was communication between the five communities, and during the second phase, regional communities were kept informed of progress and provided feedback on successive iterations of the global proposal.</p><p class="P23"><span class="T12">VI.A.</span>  Regional Processes</p><p class="normal"> </p><p class="normal">The number resources communities based their process for developing an IANA stewardship proposal primarily on the regional RIR community structures, which are the existing forums for number resources stakeholders to discuss policies and other issues relevant to the numbers resources. The RIR communities have for many years fostered the active, bottom-up participation of a broad range of stakeholders. Existing mechanisms and communication channels could therefore be used for the IANA stewardship transition discussions, eliminating the need for the creation of distinct new processes, communication channels or bodies. All RIRs have worked actively over the years to engage the full range of stakeholders via outreach activities within their regions as part of their commitment to openness, inclusiveness and transparency. Building on these outreach activities, the RIRs and the CRISP team have ensured that this proposal has been the product of input and feedback from the full range of stakeholders with an interest in Internet number resources. </p><p class="normal"> </p><p class="normal">Each of the RIR communities operates according to open, bottom-up, transparent and consensus based processes, allowing anyone with an interest to contribute to the discussions. Grounding the IANA stewardship discussion in these communities has ensured broad participation across the global communities and facilitated examination of the issues raised in the context of local and regional circumstances. The very active engagement by the community, particularly in their regional discussions, shows not only the positive commitment of the numbering community to this process, but is evidence of the RIR community’s mature and well-functioning decision-making processes.</p><p class="normal"> </p><p class="normal">Each of the five RIR communities discussed the IANA stewardship issues via mailing lists, at their RIR public meetings and in other community forums(many of which included facilities for remote participation). While the discussions have been uniformly open and transparent, with all discussions archived on mailing lists and meeting records, each community has adopted a specific process suitable to their particular local needs and culture to reach an agreed community output.</p><p class="normal"> </p><p class="normal">Links to specific output documents and archives of all the RIR community discussions are available at: </p><p class="normal"><a href="https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs-engagement-in-iana-stewardship-transition-process" class="Internet_20_link">https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs-engagement-in-iana-stewardship-transition-process</a></p><p class="normal"> </p><p class="P23"><span class="T12">VI. B.</span>  AFRINIC regional process<span class="T12">:</span></p><p class="P35"> </p><p class="P38"><span class="T7">The AFRINIC community held a consultative meeting on 25 May to 6 June 2014 during the Africa Internet Summit (AIS'2014) in Djibouti in the "IANA oversight transition" workshop. As a follow up to the meeting, AFRINIC set up a mailing list to provide a platform for the African Internet community to discuss the IANA Oversight Transition process. The mailing list was announced on July 4, 2014 to develop a community position. The list and its archives can be found at: </span><a href="https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight" class="Internet_20_link"><span class="T56">https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight</span></a><span class="T7">  </span></p><p class="P35"> </p><p class="P38"><span class="T7">A dedicated web portal was setup for sharing information on the IANA stewardship transition with the AFRINIC community and is also available at </span><a href="http://afrinic.net/en/community/iana-oversight-transition" class="Internet_20_link"><span class="T56">http://afrinic.net/en/community/iana-oversight-transition</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">AFRINIC also conducted a survey seeking community input on the IANA Stewardship </span><span class="T7">Transition. The results of the survey are published at: </span><a href="http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%20stewardship%20transition.pdf" class="Internet_20_link"><span class="T56">http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%20stewardship%20transition.pdf</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">The last face-to-face meeting at which IANA oversight transition consultations were held with the community was during the AFRINIC-21 meeting in Mauritius, 22-28 November 2014. The recordings of the session are available at </span><a href="http://meeting.afrinic.net/afrinic-21/en/vod" class="Internet_20_link"><span class="T56">http://meeting.afrinic.net/afrinic-21/en/vod</span></a><span class="T7">  </span></p><p class="P35"> </p><p class="normal"><span class="T7">Discussions continued on the </span><a href="mailto:ianaoversight@afrinic.net" class="Internet_20_link"><span class="T56">ianaoversight@afrinic.net</span></a><span class="T7"> mailing list, until the closure of the comments from the number resources communities set by the Consolidated RIR IANA Stewardship Proposal (CRISP) Team on 12th Jan 2015.</span></p><p class="P8"> </p><p class="P38"><span class="T7">The AFRINIC region CRISP team was selected/appointed by the AFRINIC Board of Directors. Key highlights/milestones of the selection/appointment process follow below:</span></p><p class="P35"> </p><p class="P38"><span class="T7">27 Oct 2014: Public Call for nominations - The call was sent by the AFRINIC CEO to major community mailing lists, indicating intent of the Board to make appointments by 12 Nov 2014.</span></p><p class="P35"> </p><p class="P38"><span class="T7">URL: </span><a href="https://lists.afrinic.net/pipermail/announce/2014/001326.html" class="Internet_20_link"><span class="T56">https://lists.afrinic.net/pipermail/announce/2014/001326.html</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">8 Nov 2014: The AFRINIC CEO announced the 5 nominated candidates:</span></p><p class="P38"><a href="https://lists.afrinic.net/pipermail/ianaoversight/2014-November/000099.html" class="Internet_20_link"><span class="T56">https://lists.afrinic.net/pipermail/ianaoversight/2014-November/000099.html</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">13 Nov 2014: The AFRINIC Board Chair announced the three CRISP team members selected to the community.</span></p><p class="P35"> </p><p class="P38"><span class="T7">URL: </span><a href="https://lists.afrinic.net/pipermail/rpd/2014/004381.html" class="Internet_20_link"><span class="T56">https://lists.afrinic.net/pipermail/rpd/2014/004381.html</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">The AFRINIC IANA oversight transition info page can be found at:</span></p><p class="P38"><a href="http://www.afrinic.net/en/community/iana-oversight-transition" class="Internet_20_link"><span class="T56">http://www.afrinic.net/en/community/iana-oversight-transition</span></a><span class="T52"> </span></p><p class="normal"> </p><p class="P23"><span class="T12">VI.C.</span>  APNIC regional process<span class="T12">:</span></p><p class="P35"> </p><p class="P38"><span class="T7">APNIC, as the secretariat for the APNIC community, set up a public mailing list (announced on 1 Apr 2014) to develop a community position, and have discussions about the proposal from the region on IANA stewardship transition: </span><a href="http://mailman.apnic.net/mailman/listinfo/IANAxfer" class="Internet_20_link"><span class="T56">http://mailman.apnic.net/mailman/listinfo/IANAxfer</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">A website, dedicated to sharing up-to-date information on the IANA stewardship transition was set up for the APNIC community members and wider community members interested in this issue: </span><a href="http://www.apnic.net/community/iana-transition" class="Internet_20_link"><span class="T56">http://www.apnic.net/community/iana-transition</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">A draft proposal was discussed at the dedicated session at the APNIC 38 Meeting in September 2014, which saw the general community consensus. The meeting provided remote participation tools to enable wider participation from communities across Asia Pacific and beyond, with live webcasts as well as Adobe Connect virtual conference room.</span></p><p class="P35"> </p><p class="P38"><a href="https://conference.apnic.net/38/program#iana" class="Internet_20_link"><span class="T56">https://conference.apnic.net/38/program#iana</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">The discussions continued on the "</span><a href="mailto:ianaxfer@apnic.net" class="Internet_20_link"><span class="T56">ianaxfer@apnic.net</span></a><span class="T7">." mailing list, until the closure of the comments from the number resources communities</span></p><p class="normal"><span class="T7">set by the CRISP Team as 12th Jan 2015.</span></p><p class="P9"/><p class="P38"><span class="T7">On 23 October 2014, through a post to the APNIC IANAxfer mailing list, APNIC sought volunteers from the Asia Pacific community to nominate to join the CRISP team. The nominees were asked to provide information about their qualifications and interest to the APNIC Executive Council for its consideration. The nomination period was open for two weeks. On 12 November 2014, the APNIC Executive Council appointed Izumi Okutani and Dr Govind as its CRISP community members, and Craig Ng as its non-voting staff member to the CRISP team.</span></p><p class="P35"> </p><p class="P38"><span class="T7">The information was also posted on APNIC's IANA oversight transition website:</span></p><p class="P35"> </p><p class="P38"><span class="T7">APNIC EC announces CRISP Team appointees</span></p><p class="P38"><span class="T7">APNIC EC seeks nominations for CRISP Team</span></p><p class="normal"><a href="http://www.apnic.net/community/iana-transition" class="Internet_20_link"><span class="T56">http://www.apnic.net/community/iana-transition</span></a></p><p class="normal"> </p><p class="P23"><span class="T12">VI.D.</span>  ARIN regional process:</p><p class="normal"> </p><p class="P41"><span class="T57">ARIN held a community consultation during the period 10/1 – 10/10/14. On 10/9/14 the ARIN community held a </span><a href="https://www.youtube.com/watch?v=PosSKAJfDP4&amp;feature=youtu.be&amp;t=2h59m12s" class="Internet_20_link"><span class="T57">consultative meeting</span></a><span class="T57"> at ARIN 34 in Baltimore, MD. </span></p><p class="P42"> </p><p class="P41"><span class="T57">On 10/13/14 ARIN established a mailing list, </span><a href="http://lists.arin.net/mailman/listinfo/iana-transition" class="Internet_20_link"><span class="T57">iana-transition@arin.net</span></a><span class="T57"> to facilitate the open community discussion in the region regarding the IANA Stewardship Transition planning process. This mailing list will remain open for comments and updates throughout the transition planning process. The </span><a href="http://lists.arin.net/pipermail/iana-transition" class="Internet_20_link"><span class="T57">archives</span></a><span class="T57"> are open and available for all Internet community members to view.</span></p><p class="P42"> </p><p class="P41"><span class="T57">A community survey was conducted following ARIN 34 from October 13, 2014 –October 20, 2014. There were a total of 64 participants and the Community Survey Summary Report can be viewed at </span><a href="https://www.arin.net/participate/governance/iana_survey.pdf" class="Internet_20_link"><span class="T57">https://www.arin.net/participate/governance/iana_survey.pdf</span></a><span class="T57"> </span></p><p class="P42"> </p><p class="P41"><span class="T57">On October 25, 2014, ARIN put a call out for volunteers to serve on the CRISP team as community representatives of the ARIN region.  The call for volunteers ended on October 31, 2014.  The ARIN Board of Trustees considered all the names that were submitted in response to the call for volunteers.  On November 8, 2014, the ARIN Board of Trustees announced the appointment of its three ARIN region CRISP team members.</span></p><p class="P42"> </p><p class="P41"><span class="T57">On November 21, 2014 the first ARIN </span><a href="http://teamarin.net/wp-content/uploads/2014/03/ARIN_draft_proposal.pdf" class="Internet_20_link"><span class="T57">draft proposal</span></a><span class="T57"> was shared on </span><a href="http://lists.arin.net/mailman/listinfo/iana-transition" class="Internet_20_link"><span class="T57">iana-transition@arin.net</span></a><span class="T57"> and discussion followed. </span></p><p class="P41"><span class="T57">http://teamarin.net/wp-content/uploads/2014/03/ARIN_draft_proposal.pdf</span></p><p class="P42"> </p><p class="P41"><span class="T57">ARIN has a dedicated </span><a href="http://teamarin.net/education/internet-governance/iana-transition" class="Internet_20_link"><span class="T57">web portal</span></a><span class="T57"> set up for sharing information and keeping the ARIN region updated on the IANA Stewardship Transition planning process.  http://teamarin.net/education/internet-governance/iana-transition/</span></p><p class="normal"> </p><p class="P23"><span class="T12">VI.E.</span>  LACNIC regional process:</p><p class="normal"> </p><p class="P39"><span class="T7">The LACNIC community developed a consultative process launched on August 15</span><span class="T8">th</span><span class="T7"> 2014, with a </span><span class="T7">public teleconference. In that opportunity LACNIC’s CEO explained the methodology, the expected timeline and the consultation scope. </span><span class="T58">The public consultation process had as a primary goal to obtain the regional community's input</span><span class="T7"> </span><span class="T58">with a view to shaping the multi-stakeholder debate on the transition of stewardship of the IANA functions in Latin America and the Caribbean, taking into account regional points of view, concerns, suggestions and/or recommendations regarding this transition,</span><span class="T7"> </span><span class="T58">specifically as it concerns IP address assignment.</span></p><p class="P36"> </p><p class="P38"><span class="T7">From that starting point, three representatives from the community guided the regional debate: </span><a href="http://www.lacnic.net/en/web/transicion/representantes" class="Internet_20_link"><span class="T59">http://www.lacnic.net/en/web/transicion/representantes</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">Contributions were received on the </span><a href="mailto:internet-gov@lacnic.net" class="Internet_20_link"><span class="T21">internet-gov@lacnic.net</span></a><span class="T7"> mailing list.   </span></p><p class="P35"> </p><p class="P38"><span class="T9">Timeline for discussion:</span></p><p class="P35"> </p><p class="P49"><span class="T58">During the thirty (30) day period (August 15 to September 15), open discussion was held. Seven (7) days later, moderators prepared a first draft, a preliminary Transition Document summarizing all contributions and discussions.</span></p><p class="P49"><span class="T58">The first Transition Document was presented on September 23. Another thirty (30) day period started for the community to comment, ending on October 24th.</span></p><p class="P49"><span class="T58">Within the framework of the LACNIC22 meeting held on 27-31 October in the city of Santiago, Chile, two (2) sessions were scheduled for discussing the first preliminary version of the Transition Document. After these two (2) sessions, a second version of the Transition Document was drafted.</span></p><p class="P39"><span class="T7">The consultative process included two panel sessions during the LACNIC 22 meeting in Santiago the Chile (October 28</span><span class="T8">th</span><span class="T7"> 2014). The first panel session was to share information about the global IANA’s oversight transition process and the work done by communities involved (names, numbers, and protocols) and the second was to discuss the main proposals on the mailing list, in order to draft a LACNIC community proposal. During the panels, with strong participation of the community, the LACNIC community proposal was shaped.  </span></p><p class="P35"> </p><p class="P39"><span class="T7">After these panels, there was a seven (7) day period that lasted until November 15</span><span class="T8">th</span><span class="T7"> 2014 for the community to present additional comments. Once this step was accomplished the proposal was filed to LACNIC’s Board of Directors and after its approval, it was submitted to the CRISP Team.</span></p><p class="P36"> </p><p class="P39"><span class="T7">Announcement of the appointment of the LACNIC region members of the CRISP team can be found at </span><a href="http://www.lacnic.net/en/web/anuncios/2014-crisp-team" class="Internet_20_link"><span class="T56">http://www.lacnic.net/en/web/anuncios/2014-crisp-team</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">After the board appointed the CRISP Team members, there was continued dialogue between the Community Leaders and the LACNIC CRISP team representatives through email and teleconferences.</span></p><p class="P35"> </p><p class="P38"><span class="T7">The final result of the Consultation at LACNIC Community: </span><a href="http://www.lacnic.net/en/web/transicion/resultado-consulta-publica" class="Internet_20_link"><span class="T59">http://www.lacnic.net/en/web/transicion/resultado-consulta-publica</span></a></p><p class="P35"> </p><p class="P38"><span class="T7">The list </span><a href="mailto:internet-gov@lacnic.net" class="Internet_20_link"><span class="T21">internet-gov@lacnic.net</span></a><span class="T7"> is still open for regional discussions until the closure of the comments set by the CRISP Team on 12th Jan 2015.</span></p><p class="normal"> </p><p class="P23"><span class="T12">VI.F.</span>  RIPE regional process:</p><p class="normal"> </p><p class="normal">The RIPE community agreed at the RIPE 68 Meeting in May 2014 that the development of a community position on IANA stewardship should take place in the existing RIPE Cooperation Working Group, and via that working group's public mailing list:<a href="https://www.ripe.net/ripe/mail/wg-lists/cooperation" class="Internet_20_link"> </a><a href="https://www.ripe.net/ripe/mail/wg-lists/cooperation" class="Internet_20_link"><span class="T18">https://www.ripe.net/ripe/mail/wg-lists/cooperation</span></a></p><p class="normal"> </p><p class="normal">The RIPE NCC, as secretariat for the RIPE community, also facilitated discussions on the IANA stewardship in national and regional forums across the RIPE NCC service region from the period of May to November 2014. Some of these forums also included remote participation facilities.  Summaries of all discussions were posted to the RIPE Cooperation Working Group mailing list and on the RIPE website:</p><p class="normal"><a href="https://www.ripe.net/iana-discussions" class="Internet_20_link"><span class="T18">https://www.ripe.net/iana-discussions</span></a></p><p class="normal"> </p><p class="normal">While there were very active, and at times passionate, discussions in the community throughout the consultation period, there was clearly strong agreement on the needs of the numbering community and the general principles that should underpin the transition of the IANA stewardship. Between September and November 2014, RIPE community discussion converged around developing a set of principles reflecting the community’s primary concerns and needs in the development of an IANA stewardship transition proposal. </p><p class="normal"> </p><p class="normal">These discussions are reflected in the discussions on the mailing list from that time:<a href="http://www.ripe.net/ripe/mail/archives/cooperation-wg/" class="Internet_20_link"> </a><a href="http://www.ripe.net/ripe/mail/archives/cooperation-wg/" class="Internet_20_link"><span class="T18">http://www.ripe.net/ripe/mail/archives/cooperation-wg/</span></a></p><p class="normal"> </p><p class="normal">Discussions at the RIPE 69 Meeting in November 2014 saw the RIPE community discuss a range of issues in relation to the IANA stewardship transition and reach consensus on the principles discussed on the mailing list.  During the RIPE 69 Meeting, a general invitation for community volunteers to the CRISP team was distributed via various RIPE NCC membership and RIPE community mailing lists: <span class="T21">http://www.ripe.net/ripe/mail/archives/ripe-list/2014-November/000877.html</span><span class="T52">  </span></p><p class="P8"> </p><p class="normal"><span class="T52">This announcement also noted the procedure whereby the RIPE Chair, in consultation with the RIPE NCC Executive Board, would select two community representatives (with the staff representative agreed by the Executive Board).  </span>At the conclusion of RIPE 69, the community expressed its support for the three RIPE representatives selected to join the CRISP)team.</p><p class="normal"> </p><p class="normal">RIPE Cooperation Working Group Session:<a href="https://ripe69.ripe.net/programme/meeting-plan/coop-wg/#session1" class="Internet_20_link"> </a><a href="https://ripe69.ripe.net/programme/meeting-plan/coop-wg/#session1" class="Internet_20_link"><span class="T18">https://ripe69.ripe.net/programme/meeting-plan/coop-wg/#session1</span></a></p><p class="normal">RIPE 69 Closing Plenary Session:<a href="https://ripe69.ripe.net/archives/video/10112/" class="Internet_20_link"> </a><a href="https://ripe69.ripe.net/archives/video/10112/" class="Internet_20_link"><span class="T18">https://ripe69.ripe.net/archives/video/10112/</span></a> </p><p class="normal"> </p><p class="P23"><span class="T12">VI.G.</span>  Global Internet Numbers Community Process (CRISP Team)</p><p class="normal"> </p><p class="normal">Following the broad consultations and active discussion in the respective five RIR communities, a mechanism was established to develop a single proposal from the Internet numbers community, based on the positions and issues noted in the five communities. </p><p class="normal"> </p><p class="normal">On 16 October 2014, the NRO EC proposed the formation of theCRISP team to develop a single Internet numbering community proposal to the IANA Stewardship Coordination Group (ICG). Established around a model similar to the community-based NRO Number Council, the CRISP team comprises three community members from each of the RIR regions (two community members and one RIR staff). The selection of the CRISP team members from each region was facilitated via transparent but distinct processes in each RIR community. Details of these selection processes are included in the RIR community process descriptions above. </p><p class="normal"> </p><p class="normal">The CRISP team members are: </p><p class="normal">AFRINIC Region</p><p class="normal"> </p><p class="normal"><span> Alan P. Barrett – Independent Consultant</span></p><p class="normal"><span> Mwendwa Kivuva – Network Infrastructure Services, University of Nairobi</span></p><p class="normal"><span> Ernest Byaruhanga (Appointed RIR staff)</span></p><p class="normal"> </p><p class="normal"> </p><p class="normal">ARIN Region</p><p class="normal"> </p><p class="normal"><span> Bill Woodcock – President and Research Director of Packet Clearing House</span></p><p class="normal"><span> John Sweeting – Sr. Director, Network Architecture &amp; Engineering at Time Warner Cable</span></p><p class="normal"><span> Michael Abejuela (Appointed RIR staff)</span></p><p class="normal"> </p><p class="normal">APNIC Region</p><p class="normal"> </p><p class="normal"><span> Dr Govind – CEO NIXI</span></p><p class="normal"><span> Izumi Okutani – Policy Liaison JPNIC</span></p><p class="normal"><span> Craig Ng (Appointed RIR staff)</span></p><p class="normal"> </p><p class="normal">LACNIC Region</p><p class="normal"> </p><p class="normal"><span> Nico Scheper - Curacao IX</span></p><p class="normal"><span> Esteban Lescano - Cabase Argentina</span></p><p class="normal"><span> Andrés Piazza (Appointed RIR staff)</span></p><p class="normal"> </p><p class="normal">RIPE NCC Region</p><p class="normal"> </p><p class="normal"><span> Nurani Nimpuno – Head of Outreach &amp; Communications at Netnod</span></p><p class="normal"><span> Andrei Robachevsky – Technology Programme Manager at the Internet Society</span></p><p class="normal"><span> Paul Rendek (Appointed RIR staff)</span></p><p class="normal"> </p><p class="P23"><span class="T12">VI.H.</span>  <span class="T12">CRISP Team Working Methods</span></p><p class="normal"> </p><p class="normal">The charter of the CRISP team describes its working methods, which are established to ensure maximum transparency and openness of the process for anyone with an interest. The charter is available on the NRO website: </p><p class="normal"><a href="https://www.nro.net/crisp-team" class="Internet_20_link">https://www.nro.net/crisp-team</a></p><p class="normal"> </p><p class="normal">From that charter: </p><p class="normal"> </p><ul><li><p class="P10" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The CRISP team shall meet entirely via teleconference for its activities; these teleconferences will be open to the public who wish to listen to the CRISP Team discussions, and will be facilitated by the Regional Internet Registries. <span class="odfLiEnd"/> </p></li><li><p class="P10" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The CRISP team shall also work through a public mailing list and the archive of such mailing list will be publicly available. The name of the mailing list will be &lt;<a href="https://www.nro.net/mailman/listinfo/ianaxfer" class="Internet_20_link">ianaxfer@nro.net</a>&gt;. <span class="odfLiEnd"/> </p></li><li><p class="P10" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>The results of each CRISP team meeting shall be published on the &lt;ianaxfer@nro.net&gt; mailing list and additionally by each RIR to its respective community. The CRISP team members from the region shall monitor and participate in the community discussion in their region regarding CRISP Team outputs.<span class="odfLiEnd"/> </p></li></ul><p class="normal"> </p><p class="normal">The CRISP team held its first teleconference on 9 December 2014. At that meeting, Izumi Okutani (APNIC region) and Alan Barrett (AFRINIC region) were selected as the Chair and Vice-Chair respectively. A timeline for the process was defined, published and announced. All CRISP teleconferences have been announced on the relevant regional mailing lists as well as the global <a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a> list. As stipulated in the charter, all CRISP teleconferences have been open to observers. Archives of the audio, video and minutes of all CRISP teleconferences, as well as several iterations of the proposal draft and a spreadsheet of issues raised by community members and their current status, have been made available online at:</p><p class="normal"><a href="https://nro.net/crisp-team" class="Internet_20_link">https://www.nro.net/crisp-team</a></p><p class="normal"> </p><p class="normal">Additionally, the CRISP team decided that in the interests of efficiency, an "internal" CRISP mailing list would be established – only members of the CRISP team would be able to send mails to this list or receive mail sent to the list, but the list content would be archived publicly on the NRO website. This archive is available at: </p><p class="normal"><a href="https://www.nro.net/pipermail/crisp/" class="Internet_20_link">https://www.nro.net/pipermail/crisp/</a></p><p class="normal"> </p><p class="normal">Throughout the CRISP team process, CRISP team members have engaged with their regional communities, ensuring that the communities are informed and sharing information with other CRISP team members on key events and discussions in their regional forums. They have also consulted the discussion archives of their regional communities as necessary throughout the process to ensure the fair and accurate representation of their community’s views. CRISP team members have been active in encouraging feedback from their regions, whether on the global <a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a> mailing list or in the regional discussion forums.</p><p class="P24"> </p><p class="P23"><span class="T12">VI.I.</span>  <span class="T3">An assessment of the level of consensus behind your community’s proposal, including a description of areas of contention or disagreement.</span></p><p class="P11"> </p><p class="normal">Throughout CRISP team deliberations, consensus was determined when, following discussions within the team, no further comments, concerns or objections were observed. A 24-hour window was set for decisions made during CRISP team teleconferences and shared on the CRISP team mailing list to allow those who were not at the call to provide input.</p><p class="normal"> </p><p class="normal">A similar approach was taken for the &lt;<a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a>&gt; list. Consensus was determined following discussions on the list around an issue raised or a new suggestion when no further comments, concerns, objections were observed. </p><p class="normal"> </p><p class="normal">Prior to submitting this proposal to the ICG, two drafts were published, along with calls for feedback from the global community. These two comment periods were important in ensuring that the community had a chance to actively contribute to resolving issues identified during the process.</p><p class="normal"> </p><p class="normal">In addition, the CRISP team has called for community feedback on this current draft of the proposal. ICG members and other interested parties can observe the level of support for the proposal in the archives of  &lt;<a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a>&gt; mailing list.</p><p class="normal"> </p><p class="normal">In comparing output coming from each RIR region, many commonalities were identified early in the process, and there was a clear consensus across the five RIR communities on the basic principles for this proposal. The RIR community tradition of openness, transparency and bottom-up processes defined the discussions in all regions, and a solid trust in the RIR system was consistently expressed throughout the process. While all five regional inputs differed, there were no major conflicts or irreconcilable points of contention identified.<br/><br/>Notable points of difference included the views on the format of the agreement to be established between IANA operator and the RIRs, and on the need for an oversight body to periodically review the agreement. The current proposal reflects the consensus agreement reached on these issues through discussion within the CRISP team and in public forums, especially the &lt;<a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a>&gt; mailing list.</p><p class="normal"> </p><p class="normal">In the global discussions at &lt;<a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a>&gt;, several issues received close attention and provoked significant discussion. These issues included:</p><p class="normal"> </p><ul><li><p class="P12" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>Composition of Review Committee<span class="odfLiEnd"/> </p></li><li><p class="P12" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>Details of the agreement, including its term and termination conditions<span class="odfLiEnd"/> </p></li><li><p class="P12" style="margin-left:0cm;"><span style="display:block;float:left;min-width:0.635cm;"></span>Intellectual property rights of the data and trademarks associated with the IANA function<span class="odfLiEnd"/> </p></li></ul><p class="normal"> </p><p class="normal">Comments mainly focused on clarification of details of these issues.  Support was expressed by several people on the <a href="mailto:ianaxfer@nro.net" class="Internet_20_link">ianaxfer@nro.net</a> mailing list on the final, agreed elements of the proposal listed in Section III.</p><p class="normal"/><p class="normal">There was clear agreement from the global community on positions regarding each of these issues, as reflected in the content of the current proposal.  The CRISP team believes therefore that the current proposal fully reflects the consensus of the global numbering community.</p><p class="P50"> </p><p class="normal"> </p><p class="normal"> </p><p class="P13"> </p><p class="normal"> </p></body></html>