On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
5. Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
5. Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg...
Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
So our meeting schedule for the coming year looks like this:
1. RC Meeting #1: Early Feb 2. RC Meeting #2: early March Finalising report at the end of the 30 day comment period 3. RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report 4. RC Meeting #4: April Brief check-in, debrief 5. RC Meeting #5: End Nov Begin preparation work for upcoming report
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process - Chair election timing - RC Operating procedure - Agreement on Section 5. Review Process - Any other changes needed
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller jschiller@google.com wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg... https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1SwguvQ/edit?usp=sharing
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Thanks Nurani,
comments in line. Regards Ernesto
El 7/2/18 a las 08:07, Nurani Nimpuno escribió:
Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
It makes sense to me. We need to be focused on the report during the next weeks.
So our meeting schedule for the coming year looks like this:
- RC Meeting #1: Early Feb
- RC Meeting #2: early March
Finalising report at the end of the 30 day comment period 3. RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report 4. RC Meeting #4: April Brief check-in, debrief 5. RC Meeting #5: End Nov Begin preparation work for upcoming report
The schedule looks good.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process
- Chair election timing
- RC Operating procedure
- Agreement on Section 5. Review Process - Any other changes needed
Having produced the first report we can deal with other important topics such as those you has listed.
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller <jschiller@google.com mailto:jschiller@google.com> wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg...
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
I concur fully with Ernesto’s comments.
From: rc-bounces@nro.net on behalf of Ernesto Majo ernesto@lacnic.net Date: Wednesday, February 7, 2018 at 7:33 AM To: "rc@nro.net" rc@nro.net Subject: Re: [IANA-RC] Procedure change
Thanks Nurani, comments in line. Regards Ernesto El 7/2/18 a las 08:07, Nurani Nimpuno escribió: Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
It makes sense to me. We need to be focused on the report during the next weeks.
So our meeting schedule for the coming year looks like this:
1. RC Meeting #1: Early Feb 2. RC Meeting #2: early March Finalising report at the end of the 30 day comment period 3. RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report 4. RC Meeting #4: April Brief check-in, debrief 5. RC Meeting #5: End Nov Begin preparation work for upcoming report
The schedule looks good.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process - Chair election timing - RC Operating procedure - Agreement on Section 5. Review Process - Any other changes needed Having produced the first report we can deal with other important topics such as those you has listed.
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller <jschiller@google.commailto:jschiller@google.com> wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
5. Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
5. Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg...
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.commailto:jschiller@google.com|571-266-0006
_______________________________________________ Rc mailing list Rc@nro.netmailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc
_______________________________________________
Rc mailing list
Rc@nro.netmailto:Rc@nro.net
While the new procedures clarify things a bit, I think the essentials are there, and I, personally, am comfortable moving forward.
I think there are a few differences between our current and proposed procedures that are relevant and we should clarify.
1. Will the final report will include the matrix?
2. Will the report include a statement about: non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends?
3. Should the 30 day comment be on the matrix, or the draft report with the matrix?
4. Will we include just a summary of the community concerns, or attach all the concerns in addition to our summary?
Below is my analysis of the differences which may be helpful we we do address changing the procedures.
Looking critically at the changes...
The current procedures do say we will: 1. publish the matrix 2. have a 30 day comment period 3. Do some outreach about the comment period 4. Collect, review, and summarize community comments 5. The summary is part of the final report
What is missing is: 1. That the report will normally be 01/01 - 31/12 2. That the full community comments will be included in the report, in addition to the summary 3. That the review matrix is part of the report (not just the subject) 4. The report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. 5. That the 30 day community comment period is on the draft report and the matrix (not the matrix alone). 6. The committee can complete the process out of cycle when asked 7. When appropriate, community comments can be passed to the NRO EC as advice. 8. Some general advice on community engangement A. During term engaged with local community B. Inform the community about developments C. Collect feedback about IANA Numbering Services Operatins
___Jason
On Wed, Feb 7, 2018 at 9:01 AM, Nate Davis ndavis@arin.net wrote:
I concur fully with Ernesto’s comments.
*From: *rc-bounces@nro.net on behalf of Ernesto Majo <ernesto@lacnic.net
*Date: *Wednesday, February 7, 2018 at 7:33 AM *To: *"rc@nro.net" rc@nro.net *Subject: *Re: [IANA-RC] Procedure change
Thanks Nurani,
comments in line. Regards Ernesto
El 7/2/18 a las 08:07, Nurani Nimpuno escribió:
Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
It makes sense to me. We need to be focused on the report during the next weeks.
So our meeting schedule for the coming year looks like this:
RC Meeting #1: Early Feb
RC Meeting #2: early March
Finalising report at the end of the 30 day comment period
RC Meeting #3: Mid-late Mar
Close any unresolved issues before publishing final report
RC Meeting #4: April
Brief check-in, debrief
RC Meeting #5: End Nov
Begin preparation work for upcoming report
The schedule looks good.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
If so, we add the following to the agenda for Meeting #4:
Debrief of report process
Chair election timing
RC Operating procedure
Agreement on Section 5. Review Process
Any other changes needed
Having produced the first report we can deal with other important topics such as those you has listed.
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller jschiller@google.com wrote:
On our call today we agreed to publish the "section 0" text on our website,
noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one
labeled working draft. The working draft had the newly added section zero,
But that text had not been circulated long enough for it to be adopted in our
May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and
was not reflected in the changes of our previous draft.
(apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with
a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSp gQbeBLe1SwguvQ/edit?usp=sharing
--
Jason Schiller|NetOps|jschiller@google.com|571-266-0006 <(571)%20266-0006>
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Rc mailing list
Rc@nro.net
https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Thanks all.
Support from me as well.
George
On 8/2/18 12:01 am, Nate Davis wrote:
I concur fully with Ernesto’s comments.
*From: *rc-bounces@nro.net on behalf of Ernesto Majo ernesto@lacnic.net *Date: *Wednesday, February 7, 2018 at 7:33 AM *To: *"rc@nro.net" rc@nro.net *Subject: *Re: [IANA-RC] Procedure change
Thanks Nurani,
comments in line. Regards Ernesto
El 7/2/18 a las 08:07, Nurani Nimpuno escribió:
Thanks for catching this Jason. This is rather unfortunate. We do indeed need to resolve this. As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.It makes sense to me. We need to be focused on the report during the next weeks.
So our meeting schedule for the coming year looks like this: 1. RC Meeting #1: Early Feb 2. RC Meeting #2: early March Finalising report at the end of the 30 day comment period 3. RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report 4. RC Meeting #4: April Brief check-in, debrief 5. RC Meeting #5: End Nov Begin preparation work for upcoming reportThe schedule looks good.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report. And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well. If so, we add the following to the agenda for Meeting #4: - Debrief of report process - Chair election timing - RC Operating procedure - Agreement on Section 5. Review Process - Any other changes neededHaving produced the first report we can deal with other important topics such as those you has listed.
All, please let me know your thoughts on this. Kind regards, Nurani On 6 Feb 2018, at 15:54, Jason Schiller <jschiller@google.com<mailto:jschiller@google.com>> wrote: On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action. Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions. It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0) I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures. New section 5: 5. Review Process The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site. 5.1. Expedited Performance Report In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement. 5.2. Community Feedback Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report. In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review. Current section 5: 5. Review Process At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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. I have made a google doc wshowing the edits here: https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1SwguvQ/edit?usp=sharing -- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com<mailto:jschiller@google.com>|571-266-0006 _______________________________________________ Rc mailing list Rc@nro.net<mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc _______________________________________________ Rc mailing list Rc@nro.net<mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Hello Folks
I support focusing on the report for now.
The meeting schedule is ok and I am open to any minor adjustments that may happen.
Regards
Madhvi
On 07/02/2018 4:32 PM, Ernesto Majo wrote:
Thanks Nurani,
comments in line. Regards Ernesto
El 7/2/18 a las 08:07, Nurani Nimpuno escribió:
Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
It makes sense to me. We need to be focused on the report during the next weeks.
So our meeting schedule for the coming year looks like this:
- RC Meeting #1: Early Feb
- RC Meeting #2: early March Finalising report at the end of the 30 day comment period
- RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report
- RC Meeting #4: April Brief check-in, debrief
- RC Meeting #5: End Nov Begin preparation work for upcoming report
The schedule looks good.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process
- Chair election timing
- RC Operating procedure
- Agreement on Section 5. Review Process
- Any other changes needed
Having produced the first report we can deal with other important topics such as those you has listed.
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller <jschiller@google.com mailto:jschiller@google.com> wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg...
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Hi Nurani and all,
My comments:
El El mié, 7 de feb. de 2018 a las 03:07, Nurani Nimpuno < nurani@nimblebits.net> escribió:
Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
Fully agree.
So our meeting schedule for the coming year looks like this:
- RC Meeting #1: Early Feb
- RC Meeting #2: early March Finalising report at the end of the 30 day comment period
- RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report
- RC Meeting #4: April Brief check-in, debrief
- RC Meeting #5: End Nov Begin preparation work for upcoming report
The “early march” meeting will be after the 10th (because of the 30 days for public comments) so that leave us almost in the middle of march. Why not having a meeting (#2) let's say about the 15th and the other (#3) about the first week of April. And #4 in May or late April if needed.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
If we have a discussion and Chair and Vice Chair proposals by email (let’s say during the 30 day period) we may have the “election” on the next meeting #2. Right? Then we may discuss timing on meeting #4 or even #3 if we have time.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
Sounds good to me.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process
- Chair election timing
- RC Operating procedure
- Agreement on Section 5. Review Process
- Any other changes needed
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller jschiller@google.com wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg...
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
Hello Nicolas, Hello everyone
You're a time saver to me ! you've said everything I wanted to say. I don't have anything else to add.
Cordialement, ___________________________________________ Bertrand Cherrier Administration Systèmes - R&D Micro Logic Systems b.cherrier@micrologic.nc mailto:b.cherrier@micrologic.nc https://www.mls.nc https://www.mls.nc/ Tél : +687 24 99 24 VoIP : 65 24 99 24 SAV : +687 36 67 76 (58F/min)
Le 8 févr. 2018 à 03:30, Nicolas Antoniello nantoniello@gmail.com a écrit :
Hi Nurani and all,
My comments:
El El mié, 7 de feb. de 2018 a las 03:07, Nurani Nimpuno <nurani@nimblebits.net mailto:nurani@nimblebits.net> escribió: Thanks for catching this Jason.
This is rather unfortunate. We do indeed need to resolve this.
As it is not an urgent matter, unless the group feels differently, I suggest that we park this for now to allow us to focus on the report, but that we bring it to the agenda of our first meeting (#4) after the publication of the report.
Fully agree.
So our meeting schedule for the coming year looks like this:
- RC Meeting #1: Early Feb
- RC Meeting #2: early March Finalising report at the end of the 30 day comment period
- RC Meeting #3: Mid-late Mar Close any unresolved issues before publishing final report
- RC Meeting #4: April Brief check-in, debrief
- RC Meeting #5: End Nov Begin preparation work for upcoming report
The “early march” meeting will be after the 10th (because of the 30 days for public comments) so that leave us almost in the middle of march. Why not having a meeting (#2) let's say about the 15th and the other (#3) about the first week of April. And #4 in May or late April if needed.
There is also the issue (raised by me) of the timing of the chair election, which we agreed to discuss at our first meeting (#4) after the publication of our report.
If we have a discussion and Chair and Vice Chair proposals by email (let’s say during the 30 day period) we may have the “election” on the next meeting #2. Right? Then we may discuss timing on meeting #4 or even #3 if we have time.
And as noted in the meeting, there may be a need to assess (and possibly document) the process after we have completed the report, as this is the first report this group produces. Meeting #4 could be a good opportunity to do so as well.
Sounds good to me.
If so, we add the following to the agenda for Meeting #4:
- Debrief of report process
- Chair election timing
- RC Operating procedure
- Agreement on Section 5. Review Process
- Any other changes needed
All, please let me know your thoughts on this.
Kind regards,
Nurani
On 6 Feb 2018, at 15:54, Jason Schiller <jschiller@google.com mailto:jschiller@google.com> wrote:
On our call today we agreed to publish the "section 0" text on our website, noting is it not really prescriptive of our procedures. I support that action.
Back in May, we had two draft procedures, one labeled draft and one labeled working draft. The working draft had the newly added section zero, But that text had not been circulated long enough for it to be adopted in our May meeting, hence the need to maintain two versions.
It seems there is another section of our procedures which got updated and was not reflected in the changes of our previous draft. (apologies from me, as I believed these two were in sync except for section 0)
I propose we review the new section 5 and update our operating procedures with a vote of 80% support per our procedures.
New section 5:
- Review Process
The RIRs will publish an IANA Numbering Services Operations Review Matrix in January every year, summarizing the RIRs’ review of the performance of the IANA Numbering Services Operations in the last calendar year. The Review Committee will compile a draft IANA Numbering Services Operations Performance Report that summarizes the the review matrix, and community comments, with the performance matrix and community input appended. The draft report will also highlight non-compliance, near non-compliance, anomalies, concerns, and/or interesting trends. The draft report will be provided to the five respective RIR communities for a comment period of 30 days. Community comments will be incorporated into the draft which will be finalized and submitted to the NRO EC as advice, and published on the IANA Numbering Services Review Committee web site.
5.1. Expedited Performance Report
In the event there is a requirement to complete an expedited review, the NRO EC chair will advise the Review Committee chairs of the requirement.
5.2. Community Feedback
Review Committee members are expected to be engaged with their respective RIR communities during their term. They should communicate relevant developments relating to the Committee to their respective community, and collect feedback relevant to the IANA Numbering Services Operations from their respective community. This input will be provided to the RIRs as advice when appropriate. These comments will be reviewed and summarized by the Review Committee and included in the IANA Numbering Services Operations Performance Report.
In extraordinary circumstances community input can be passed to the NRO EC separate from the IANA Numbering Services Performance Review to aid them in their consideration to request an expedited review.
Current section 5:
- Review Process
At a time of the NRO EC’s choosing, the RIRs will publish an IANA Numbering Services Review Matrix in January every year, summarizing the RIRs’ 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 RIR communities for a comment period of 30 days. The Review Committee members are responsible to make sure their respective communities are informed about the comment period, using their region’s relevant communication and announcement channels. Following the closure of the public comment, 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.
I have made a google doc wshowing the edits here:
https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1Swg... https://docs.google.com/document/d/1lT4mjDyw83qy1WL8l4Zuye9HjgYSpgQbeBLe1SwguvQ/edit?usp=sharing
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc https://www.nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc https://www.nro.net/mailman/listinfo/rc _______________________________________________ Rc mailing list Rc@nro.net mailto:Rc@nro.net https://www.nro.net/mailman/listinfo/rc https://www.nro.net/mailman/listinfo/rc
participants (9)
-
Bertrand Cherrier -
Ernesto Majo -
George Kuo -
Jason Schiller -
Jason Schiller -
Madhvi Gokool -
Nate Davis -
Nicolas Antoniello -
Nurani Nimpuno