I like Filiz's proposal of the full year summary approach starting early in the new year!

I think in the mean time, it would still be good to generate a report prior to January

so that we can have everything settled and for the process starting in January to run smoothly.

I suggest that after we close all the gaps identified in the review of the matrix produced

by Nate, and any gaps identified in current IANA performance reporting, we take at least

30 days of data, complete a review, and generate a report.

We may choose to keep the report internal as a "draft" or publish it (I have no preference).

I am not sure if we are required to publish a report in 2017.

from our charter:

"The Review Committee must submit such a report to the NRO EC at least once every

calendar year, by the date specified by the NRO EC from time to time."

___Jason

On Tue, Mar 7, 2017 at 8:30 AM, Madhvi Gokool <madhvi@afrinic.net> wrote:

hello

I agree with Filiz's proposal. Workable for AFRINIC.

Regards

Madhvi
On 07/03/2017 4:26 PM, Nate Davis wrote:
Yes – this is workable for ARIN.

Thanks!

From: <rc-bounces@nro.net> on behalf of Nurani Nimpuno <nurani@nimblebits.net>
Date: Tuesday, March 7, 2017 at 3:04 AM
To: Filiz Yilmaz <koalafil@gmail.com>
Cc: "rc@nro.net" <rc@nro.net>
Subject: Re: [IANA-RC] Draft Review Process

Hi Filiz,

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.

I support this change.

RIR staff - does this seem workable to you too?

Kind regards,

Nurani

On 6 Mar 2017, at 11:15, Filiz Yilmaz <koalafil@gmail.com> wrote:

Hi Nurani,

Thanks for putting this together. I like it, concise, to the point and easy to read.

I just have one comment and suggestion for a change:

Instead of September I propose:

"The RIRs will publish an IANA numbering services review matrix in January of every calendar year, summarising the RIR’s review of the performance of the IANA numbering services in the previous calendar year..."

This way RIRs can report on a full calendar year and then we can review that in say February.

So first report will come to us from RIRs in 2018 January, covering practices and performance of IANA in the entire 2017.

Then we review it in Feb and publish our review.

Then in 2019 Jan, RIRs send their report to us in Jan about the practices seen in 2018, etc etc...

This will make things much easier in my opinion, both managing deadlines, doing the work and then reporting what is done publicly too.

Cheers

Filiz

On Fri, Mar 3, 2017 at 4:01 AM, Nurani Nimpuno <nurani@nimblebits.net> wrote:

Dear all,

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.

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.

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.)

Kind regards,

Nurani Nimpuno

-----------------------

Review Process
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.

-----------------------

_______________________________________________
Rc mailing list
Rc@nro.net
https://nro.net/mailman/listinfo/rc
_______________________________________________
Rc mailing list
Rc@nro.net
https://nro.net/mailman/listinfo/rc
_______________________________________________
Rc mailing list
Rc@nro.net
https://nro.net/mailman/listinfo/rc

_______________________________________________________

Jason Schiller|NetOps|jschiller@google.com|571-266-0006