Thanks for sharing your thoughts.
Like I said on today’s call, our task is important but in essence rather simple.
We are here to offer a medium for the community to provide feedback on how the IANA performance has been according to the SLA. It increases the transparency towards the community and it gives the stakeholders an opportunity to raise concerns if the performance of IANA It will most likely never be an exciting report, but that doesn’t mean it still serves a good purpose. There have been some suggestions in the past to make the report more detailed, but we have tried to find the right balance, and keep it fairly short and simple.
One of the pieces of feedback when I presented this in the RIPE community was “Great work. Boring is good!”, which I think sums up the somewhat simple (boring) but important task we have. :)
We have made a conscious effort in the past years to produce a fairly standardised report, can be easily reproduced every year and that is not overly cumbersome for the IANA RC members to produce in a short space of time, but that still has all the right information included. We also wanted to make sure we could work collaboratively in a tool that is accessible to all RC members. We have made it accessible on the web as well as in a downloadable PDF format.
I don’t think we can or should reduce this report to a one pager, but that doesn’t mean that we can’t improve it of course! We have asked the RIRs to get help from their comms teams to “prettify” the RIR Matrix as that is the element that the RIRs are responsible for. So I encourage everyone to provide feedback to the suggested format that John circulated on the list yesterday.
If you want to send a draft report to the list with the suggested changes to next year’s report outside of the Matrix, we can make some room at our January meeting to consider them.
Thanks again.
Kind regards,
Nurani
[ clip ]
I’d like to see us consider adding an agenda item on how to boil this report down. There is a lot of good information, but my reading made me feel like I was reading the report all over. If this is an analysis, perhaps we can figure out how to get it to a one pager that is digestable by “anyone”?
Indeed, the report has more background information than actual analysis and conclusion. I believe that this approach was initially adopted so that the report can stand on their own.
I would agree, though, that it is worth revisiting to produce a more digestible report. Much of the background and supporting information can be moved to the appendix or linked to the web content.
Do you have a report format in mind? I would love to see us mimic a report that is concise, useful, and compelling.
Louie, Condensing the report into an infographic summary for the first is a great idea.
I do see some room for improvements.
Here's one example:
"The RC notes that one comment was received in the public comment period supporting the conclusions that the SLAs for the IANA numbering service have been met 100%. The full comment is included in Appendix 2".
We might consider condensing this to:
"One comment was received during the public comment period. See Appendix A". 36 words to 12. Feels like there are a lot of candidates for such a reduction.
I'm happy to help propose a version if useful and helpful.
_______________________________________________
Rc mailing list
Rc@nro.nethttps://www.nro.net/mailman/listinfo/rc