<div dir="ltr">I like Filiz&#39;s proposal of the full year summary approach starting early in the new year!<div><br></div><div>I think in the mean time, it would still be good to generate a report prior to January</div><div>so that we can have everything settled and for the process starting in January to run smoothly.</div><div><br></div><div>I suggest that after we close all the gaps identified in the review of the matrix produced</div><div>by Nate, and any gaps identified in current IANA performance reporting, we take at least</div><div>30 days of data, complete a review, and generate a report.  </div><div><br></div><div>We may choose to keep the report internal as a &quot;draft&quot; or publish it (I have no preference).</div><div><br></div><div>I am not sure if we are required to publish a report in 2017.</div><div>from our charter:</div><div><br></div><div>&quot;The<span style="white-space:pre"> </span>Review<span style="white-space:pre"> </span>Committee<span style="white-space:pre"> </span>must<span style="white-space:pre"> </span>submit<span style="white-space:pre"> </span>such<span style="white-space:pre"> </span>a<span style="white-space:pre"> </span>report<span style="white-space:pre"> </span>to<span style="white-space:pre"> </span>the<span style="white-space:pre"> </span>NRO<span style="white-space:pre"> </span>EC<span style="white-space:pre"> </span>at<span style="white-space:pre"> </span>least<span style="white-space:pre"> </span>once<span style="white-space:pre"> </span>every<span style="white-space:pre"> </span></div><div>calendar<span style="white-space:pre"> </span>year,<span style="white-space:pre"> </span>by<span style="white-space:pre"> </span>the<span style="white-space:pre"> </span>date<span style="white-space:pre"> </span>specified<span style="white-space:pre"> </span>by the<span style="white-space:pre"> </span>NRO<span style="white-space:pre"> </span>EC<span style="white-space:pre"> </span>from<span style="white-space:pre"> </span>time<span style="white-space:pre"> </span>to<span style="white-space:pre"> </span>time.&quot;</div><div><br></div><div>___Jason</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 7, 2017 at 8:30 AM, Madhvi Gokool <span dir="ltr">&lt;<a href="mailto:madhvi@afrinic.net" target="_blank">madhvi@afrinic.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <p>hello</p>
    <p>I agree with Filiz&#39;s proposal. Workable for AFRINIC.</p>
    <p>Regards</p><span class="HOEnZb"><font color="#888888">
    <p>Madhvi<br>
    </p></font></span><div><div class="h5">
    <br>
    <div class="m_-7046479960422839048moz-cite-prefix">On 07/03/2017 4:26 PM, Nate Davis
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div>Yes – this is workable for ARIN.</div>
      <div><br>
      </div>
      <div>Thanks!</div>
      <div><br>
      </div>
      <span id="m_-7046479960422839048OLK_SRC_BODY_SECTION">
        <div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
          <span style="font-weight:bold">From: </span>&lt;<a href="mailto:rc-bounces@nro.net" target="_blank">rc-bounces@nro.net</a>&gt;
          on behalf of Nurani Nimpuno &lt;<a href="mailto:nurani@nimblebits.net" target="_blank">nurani@nimblebits.net</a>&gt;<br>
          <span style="font-weight:bold">Date: </span>Tuesday, March 7,
          2017 at 3:04 AM<br>
          <span style="font-weight:bold">To: </span>Filiz Yilmaz &lt;<a href="mailto:koalafil@gmail.com" target="_blank">koalafil@gmail.com</a>&gt;<br>
          <span style="font-weight:bold">Cc: </span>&quot;<a href="mailto:rc@nro.net" target="_blank">rc@nro.net</a>&quot;
          &lt;<a href="mailto:rc@nro.net" target="_blank">rc@nro.net</a>&gt;<br>
          <span style="font-weight:bold">Subject: </span>Re: [IANA-RC]
          Draft Review Process<br>
        </div>
        <div><br>
        </div>
        <div>
          <div style="word-wrap:break-word">
            Hi Filiz,
            <div><br>
            </div>
            <div>Hm, that is a very good, practical point. Full
              calendar years makes much more sense of course. It should
              be rather easy for the RIRs to summarise the year in
              January and then for the community and us to review it in
              February. </div>
            <div><br>
            </div>
            <div>I support this change.</div>
            <div><br>
            </div>
            <div>RIR staff - does this seem workable to you
              too?</div>
            <div><br>
            </div>
            <div>Kind regards,</div>
            <div>Nurani</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
              <div>
                <blockquote type="cite">
                  <div>On 6 Mar 2017, at 11:15, Filiz Yilmaz
                    &lt;<a href="mailto:koalafil@gmail.com" target="_blank">koalafil@gmail.com</a>&gt;
                    wrote:</div>
                  <br class="m_-7046479960422839048Apple-interchange-newline">
                  <div>
                    <div dir="ltr">Hi Nurani,
                      <div><br>
                      </div>
                      <div>Thanks for putting this together. I
                        like it, concise, to the point and easy to
                        read. </div>
                      <div><br>
                      </div>
                      <div>I just have one comment and
                        suggestion for a change:</div>
                      <div><br>
                      </div>
                      <div>Instead of September I propose: </div>
                      <div><br>
                      </div>
                      <div>&quot;The RIRs will publish an IANA
                        numbering services review matrix in <b>
                          January</b> of <b>every calendar
                          year</b>, summarising the RIR’s review of the
                        performance of the IANA numbering services<b> in the previous calendar year...&quot;</b></div>
                      <div><b><br>
                        </b></div>
                      <div>This way RIRs can report on a full
                        calendar year and then we can review that in say
                        February. </div>
                      <div>So first report will come to us from
                        RIRs in 2018 January, covering practices and
                        performance of IANA in the entire 2017. </div>
                      <div>Then we review it in Feb and publish
                        our review. </div>
                      <div>Then in 2019 Jan, RIRs send their
                        report to us in Jan about the practices seen in
                        2018, etc etc...</div>
                      <div> </div>
                      <div>This will make things much easier in
                        my opinion, both managing deadlines, doing the
                        work and then reporting what is done publicly
                        too.  </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div>Cheers</div>
                      <div>Filiz</div>
                      <div><br>
                      </div>
                      <div><b><br>
                        </b></div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">On Fri, Mar 3, 2017 at
                        4:01 AM, Nurani Nimpuno <span dir="ltr">
                          &lt;<a href="mailto:nurani@nimblebits.net" target="_blank">nurani@nimblebits.net</a>&gt;</span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                          <div style="word-wrap:break-word">
                            <div>Dear all,</div>
                            <div><br>
                            </div>
                            <div>In an attempt to move forward
                              on defining scope and processes for this
                              group, I have drafted a proposed Review
                              Process below. I believe this reflects the
                              intention of the CRISP proposal.</div>
                            <div><br>
                            </div>
                            <div>Given that there are only ~3
                              requests per year in total for all RIRs,
                              and that we have a history of 20+ years of
                              stable services that the RIRs have been
                              satisfied with, I believe it does not have
                              to be more complicated than this. </div>
                            <div><br>
                            </div>
                            <div>Happy to discuss any details
                              of this. (The timing, such as September
                              every year, and 30 days comment period,
                              are merely suggestions. Feel free to
                              suggest adjustments to these as you see
                              fit.)</div>
                            <div><br>
                            </div>
                            <div>Kind regards,</div>
                            <div><br>
                            </div>
                            <div>Nurani Nimpuno</div>
                            <div><br>
                            </div>
                            <div><br>
                            </div>
                            <div>-----------------------</div>
                            <div><font size="4">Review
                                Process<br>
                              </font><font size="2">The RIRs
                                will publish an IANA numbering services
                                review matrix in September every year,
                                summarising the RIR’s review of the
                                performance of the IANA numbering
                                services in the last year. This review
                                matrix gets submitted to the Review
                                Committee who passes it on to the five
                                respective RIR communities for
                                a public comment period of 30 days. The
                                Review Committee gathers input and
                                comments from the five RIR communities,
                                which it reviews and summarises. The
                                Review Committee compiles a final report
                                on the review matrix, with the
                                summarised input appended, which it
                                publishes and submits to the NRO EC as
                                advice.</font></div>
                            <div>-----------------------</div>
                            <div><br>
                            </div>
                          </div>
                          <br>
                          ______________________________<wbr>_________________<br>
                          Rc mailing list<br>
                          <a href="mailto:Rc@nro.net" target="_blank">Rc@nro.net</a><br>
                          <a href="https://nro.net/mailman/listinfo/rc" rel="noreferrer" target="_blank">https://nro.net/mailman/listin<wbr>fo/rc</a><br>
                          <br>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </span>
      <br>
      <fieldset class="m_-7046479960422839048mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
Rc mailing list
<a class="m_-7046479960422839048moz-txt-link-abbreviated" href="mailto:Rc@nro.net" target="_blank">Rc@nro.net</a>
<a class="m_-7046479960422839048moz-txt-link-freetext" href="https://nro.net/mailman/listinfo/rc" target="_blank">https://nro.net/mailman/<wbr>listinfo/rc</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>______________________________<wbr>_________________<br>
Rc mailing list<br>
<a href="mailto:Rc@nro.net">Rc@nro.net</a><br>
<a href="https://nro.net/mailman/listinfo/rc" rel="noreferrer" target="_blank">https://nro.net/mailman/<wbr>listinfo/rc</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="&#39;courier new&#39;, monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="&#39;courier new&#39;, monospace">_______________________________________________________<br></font><div><font face="&#39;courier new&#39;, monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="&#39;courier new&#39;, monospace"><br></font></div></span></div></font></div>
</div>