.
Community Plenary
.
21 May 2021
.
10:30 (UTC + 2)
MIRJAM KUHNE: Good morning, good afternoon, good night everyone, wherever you are. I assume you can hear me.
.
This is the Community Plenary. Hello. I am Mirjam Kuhne, I am the RIPE Chair, and Niall O'Reilly is also here, the Vice‑Chair.
.
We have quite a full agenda, so, I think I just want to start right away on time.
.
It's quite a full agenda so note to myself, allow for more time during Community Plenary again, and next time, we always thinking we're not going to fill this slot and then, in the end, we're running out of time.
.
So, I'll give you a quick update of what the RIPE Chair team has been up to over the last six months or so since the last meeting. And then we'll have two reports from the RIPE task forces, and report by Nuani Nimpuno of the Numbering Services Review Committee.
.
I'll start with our update, we are actually publishing a regular update on RIPE Labs, kind of roughly every month or so, and so you can follow our developments and our activities there, so I only want to give you a quick summary here. Let me know if you have any questions at the end.
.
We have got a load of documentation and writing and cleaning up things also to document our processes and traditions, so including ‑‑ some support for Working Group Chairs, for instance we have now guidelines for Working Group Chairs, we have guidelines to moderate the mailing lists for Working Group Chairs. Also, some short documents on how to operate and ask for interim meetings, like the DNS Working Group has done over the last, I would say a year or so now, and other Working Groups also had some interim meetings, and so that's definitely a possibility if you are interested in that.
.
And we also updated some web pages for the Working Groups.
.
We have also supported the task forces, of course, but I would really like to stress that the heavy lifting is done by the task force members, so, I want to ‑‑ you will hear more from them later on on the agenda, as you saw, but I want to just show you the volunteers here of the RIPE Code of Conduct Task Force, including the RIPE NCC staff, and also the RIPE Database Requirements Task Force, and I can assure you that all of them have put a lot of time and effort into this and are still continuing to do this for the benefit of the community. You will hear more from them later on. We are doing a bit of work in the background to make sure they are okay but they are doing all the work, of course.
.
Coming back to documentation. We have published two RIPE documents, one was a review of the appeals process, as it's currently described in the policy development process document, RIPE‑710, and another quite detailed documentation of the evolution of the whole RIPE Policy Development Process that Niall has mostly worked on, and I think will come in handy for future reference and when we are going to change PDP in the future.
.
I shared some recommended changes with you on the RIPE list, and we will go back and draft a new document and share it with the list soon, sometime after the meeting, and then we can discuss that on the list.
.
The nominating ‑‑ the RIPE Nominating Committee has published a report in March on the RIPE list and there is also a blog where you can still find all the documentation and all the communication that they have put out. I would really like to thank the Chair of the Nominating Committee, Daniel Karrenberg, and all the members of the Nominating Committee for all the effort that they have put into, and that wasn't easy at times. So they are now finished their work and they published this report, including a number of recommendations, both for a future Nominating Committee Chair and also a recommendations for the community.
.
One recommendation is in there for the community that Niall and I already got when we started and we want to come back, and basically it asks the community to come up with consensus on the relationship between the RIPE and the RIPE NCC and specifically the way the RIPE NCC staff can participate in the RIPE community. And we already started working on this on and off, and now with the NomCom report out, we actually want to go back to that and focus on that. In my last update on RIPE Labs in April, I already shared sharing principles what we were thinking of, like RIPE NCC staff are also part of this community, and their input is valued by the community and they have specific expertise on certain topics. And other principles are that the RIPE community roles must benefit the community as a whole, and therefore people filling these roles must be able to act independently. And we will continue to work on these, together with Hans Petter, to describe ‑‑ it will probably be two sets of documents maybe, one description of RIPE NCC staff and the RIPE community and then possibly another document describing the relationship and the services the RIPE NCC provides to the community overall.
.
So watch this space. This is a work in progress.
.
A lot of ‑‑ a big part of our tasks is listening to the community, as we have also done here during this week, but, of course, also, you know, outside the meetings, we have attended a number of industry events online, obviously, and we are also reaching out to the the regional communities like SEE, ENOG, MENOG; I will be presenting at ENOG next month, and we are also promoting the deployment of the RIPE Code of Conduct in the original regions and so we'll be discussing that as well with the other communities.
.
I have also been involved a bit in the community wellbeing activity that you have seen the result of earlier this week, where Erik Bais was presenting in the Plenary the resilience of the human network, and I was really pleased to see so much positive feedback during and after Erik's presentation. I think that's an important topic for us, as a community.
.
So what's next? There is a lot of ongoing work, a lot of continuation work. We continue to work with the Code of Conduct Task Force to finalise the first part of the Charter, and then we are also continuing to work with the RIPE Database Requirements Task Force to review all the recommendations and then see how we can reach consensus on each of them or how we further, as a community, respond to each of these recommendations.
.
As I said, we'll update ‑‑ we'll work on an update of the PDP documentation and the documentation between the RIPE and the RIPE NCC.
.
Also kind in the back of our heads the whole time is the RIPE vision and purpose overall, and we keep reviewing the first RIPE documents just to see if they are still valid, if there is anything we might want to change as a community. So we might come back to that also to you at some point.
.
I have to say, it's amazing that actually I think that most of the stuff that's been written down in the late eighties, early nineties, I think is still very valid and really applies to what we are still doing here as a community. So, cheers to the early RIPE.participants.
.
Another topic that's also kind of close to my heart, of course, is to be open and attractive to newcomers and welcoming so that the whole set of activities like reviewing documentation on the website, creating maybe new documentation for how to engage in the RIPE community, make it a bit more easy and welcoming and attractive to enter this community and to become more active and related to that also, continue to document our traditions.
.
How can you reach us? This is our e‑mail address. You can reach us as a team or also individually. And I think that's about it.
.
And, so, I'll stop sharing around. I'll hand over to Shane Kerr who I believe will be giving you an update on the RIPE Database Requirements Task Force.
SHANE KERR: Thank you, Mirjam.
.
Hello everyone, I am Shane Kerr and I am giving a brief report of the background and activity of the RIPE Database Requirements Task Force.
.
So, the task force has a number of different people, that you can see here. We have Bijal running the effort, James and myself helping her as additional Chaire, and then Nick and Peter. We had one of the members of the task force leave the task force, Sara, recently, which is a bit of a pity, because we feel like we are very close to the end of the work, but she was unable to continue. We have also had excellent support from the RIPE NCC, of course, Maria and Edward.
.
So what is this whole task force about?
.
This comes out of a work ‑‑ out of a discussion that happened in the RIPE community, there was this big‑picture BoF and one of the suggestions was that we never actually had written down what the purpose of the RIPE database was and this is such a big part of RIPE activities, so the idea was to create a task force to handle this. And the main output of the task force is a document which, like we said, we had never written down the requirements, let's write them down, so that's the goal, to make a document which has all the requirements, as well as some reasoning behind them. It's not just a document which says do this, but also to do this, and why.
.
And the idea of this document is that it will then be used to guide further efforts in the community, any changes that are needed in the database or not.
.
So, what have we done so far to achieve this goal?
.
We have been meeting regularly, and we publish all the meetings and the agenda and the minutes from the meetings are all published. We have done a couple of surveys. The idea is that we have a pretty broad set of people in terms of the members of the task force. There is thousands or tens of thousands of members of the RIPE community, so we have done a couple of surveys to get feedback. We have done a number of efforts to engage the RIPE community through existing mechanisms, like using the e‑mail list, we have had a few BoFs, both personal and online, and we have also done smaller meetings with the Chairs of the database Working Group, because it's so critical to their Working Group and their work there, we wanted to make sure that they understood where we were at and we could get any feedback from them that was important. We have given a couple of updates about how are our progress has been. This is the third one.
.
And we have also done other efforts to collect data such as scanning the contents of the database and looking at the way people use it based on logs and things like that.
.
We have published a draft, and then there was also, earlier this week, a presentation about one ‑‑ one of our specific suggestions at the Address Policy Working Group.
.
So, in spite of all that work, we still have a number of specific open issues that we are continuing to work on. One is the document structure itself. It's pretty logically weighed out now, but we got some feedback that we need to improve that so we're going to work on that.
.
We have an open issue about legal address. This was basically a request from the law enforcement community to make it easier to pursue problems with the ‑‑ by including the legal address of companies that had received resources. Not natural persons, but legal entities. So it shouldn't run afoul of privacy concerns. But we have both support for and against this effort so we're not exactly sure where we're going to go with that. We may also want to come up with some sort of compromise solution which doesn't publish this address for everyone but publishes in a way that's more useful to law enforcement than it is today.
.
And to be clear, it's not just law enforcement. There are other people who are interested in this information.
.
We also have an open issue about whether or not it makes sense to have PERSON objects in the database at all. There is a suggestion to move from PERSON objects to ROLE objects. There is, of course, a concern that then we just have the same objects but just call them ROLE objects instead of PERSON objects, so we're not sure how that will work. But being more explicit about it may improves the privacy situation and get unneeded and unwanted data out of the database.
.
And, of course, there is a lot of historical data in the database. Basically, since it was converted from the Version 2, something like that, in 2000, or so, or 2001, something like, that there was historical data for all of that. We need to figure out what the actual requirements are there.
.
Anyway, those are the open issues. We have ‑‑ we had a BoF before the RIPE meeting and there is minutes and feedback from there, from that meeting, from that BoF online.
.
What are our next steps?
.
Well, of course, we have to tackle those open issues. We are integrating the feedback that we received at the BoF, and the way we're doing that is by basically the way we have done it from the beginning and breaking up the work to the people in the task force who are most interested and most qualified to handle it.
.
And we hope to get all of that written and edited and updated in June and then publish a new and hopefully final draft in the third quarter of 2021.
.
So, hopefully it's been apparent throughout this presentation that we are not trying to do this in isolation. We want feedback. You can go to these links. You can follow the work that we have done. We are trying to be open and transparent. And because we're very interested ‑‑ we think it's very important for the requirements that we generate to actually represent what the RIPE community wants and needs.
.
That is it. I am looking at the Q&A, I don't see any questions. I am not looking at the chat. Anything you want to add, Mirjam?
MIRJAM KUHNE: No. I was watching time. We have some time for questions and answers. I was ‑‑ I kind of ignored questions after my presentation, but there weren't any in the Q&A also. We might have some time at the end if people want to think about questions for the entire ‑‑ for all the agenda items. So... let's just move on then. Thanks, Shane.
.
Next we'll have Leo as the Chair of the ‑‑
NIALL O'REILLY: Before ‑‑ somebody was in the microphone queue. He has rejoined the microphone queue, I am giving the microphone for a moment to Elvis.
.
ELVIS VELEA: I was interested to talk a bit more about your last slide, the one regarding historic data and what you want to do with it. And I was wondering whether you guys have seen the requests also ‑‑ you probably have ‑‑ from Denis regarding NW‑2, with publishing more historic data. And I was wondering if you have an opinion on that as a task force yet or is this just something that you want to continue collecting feedback and discuss?
SHANE KERR: I think it's safe to say we ‑‑ sorry, go ahead.
ELVIS VELEA: I personally think it's a good idea to provide for historic data. So, provide access to all that historic data, except it should be cleaned up, personal info.
SHANE KERR: Sure, I think it's safe to say that we do not have a consensus or any kind of preferred recommendation as far as historical data now. So, hearing that it's useful to you is good feedback. We are ‑‑ we're a bit nervous about it because there is no explicit warnings now when you use the database that will tell you, hey if you delete something that doesn't actually mean delete it, it could still be there. So it's ‑‑ I think ‑‑ we have to be careful about the expectation of the users, and that's basically the main concern and the tricky bit with historical data.
.
ELVIS VELEA: So we collect a lot of data about IP addresses that we broker, so we take WHOIS history and stuff like that from all the registries if we can. ARIN and APNIC have an option which provides all the historic information about an IP address, and I think we shouldn't worry too much about whether an object has been deleted or not, whether that ‑‑ well, the history still being available, I still believe that's a good thing, at least that's what my customers have appreciated when we have provided this information. It helps a lot of people to see the history of how the IP addresses have been used, and make a decision on which IP addresses they would like to use for purchase and use as their own.
SHANE KERR: Just to be clear, this is kind of like when you are buying a used car, if you found out that it's owned by a 20‑year‑old who likes to travel all around the country for his business, versus being owned by a quiet grandmother who only goes out for Sunday driving.
ELVIS VELEA: Something like that.
SHANE KERR: I definitely see the use case for it, we have to balance it against the people who the information is about.
.
MIRJAM KUHNE: Niall, do you see any more questions somewhere?
NIALL O'REILLY: No. There is nothing in the queue, either the written queue or the microphone queue, so I would say let's go ahead.
MIRJAM KUHNE: Thanks again, Shane.
.
Next up is Leo Vegoda with an update of the Code of Conduct Task Force.
LEO VEGODA: Thank you very much. I am just going to give an update on the Code of Conduct Task Force and specifically talk a little bit about the BoF that we held earlier this week.
.
Just to recap and bring everyone up to speed on where we are.
.
The Code of Conduct Task Force was formed as a result of the outcomes from the Diversity Task Force, and the Diversity Task Force produced version 3 of the Code of Conduct. The Code of Conduct Task Force was proposed at RIPE 80, chartered in mid‑September last year, and we have three work items to deliver:
.
A Code of Conduct, a document describing the way to select the Code of Conduct team, and reporting on operational procedures for the Code of Conduct team. And we have been working on the first one, and we'll talk a little bit about looking forward to the future.
.
Before we do that, I am just going to refresh you on the members of the task force. Mirjam has already introduced us. I would like to pay thanks to Athina and Antony, who have been absolutely brilliant in supporting us as a task force. We couldn't have delivered what we have done so far without their help.
.
This is what we have delivered so far: We delivered a draft Code of Conduct and published it for review and feedback. There were more than 50 messages discussing the draft. They were mostly supportive. They came from about 18 people.
.
We now need to go and work through the feedback that we have already got, and we want to deliver an updated draft before July. So, that is helpfully going to be a completion for work item 1 on our set of 3.
.
And then this week, we started looking forward to the next two work items, and we held a Birds of a Feather, A BoF, so the goal of this was that we could start listening to people about what they see as the requirements for the next two work items. We were very happy to have the BoF chaired by Olaf Kolkman. Because Olaf was able to chair this for us, it meant that the members of the task force were able to spend more time listening than essentially running the BoF, and just doing the logistics of managing the speaker queue and running the time and all that kind of stuff.
.
And we could focus on hearing what the community wanted regarding the kind of team that is needed to implement the Code of Conduct, the balance between the speed of responding to reports and requirements for process, and the kind of process that will be needed to update the Code of Conduct and the Code of Conduct team's processes just, you know, continuous improvement that you would want for any kind of operational activity.
.
So we were, you know, very happy to see that between 150 and 200 people joined us for the hour of the BoF, and we're really, you know, very grateful that we had that many people join us because we recognise that it scheduled a time when, for many people, there are family commitments, and so this won't be the only opportunity for people to give us feedback.
.
The things that we heard were that because the Code of Conduct now expands the scope from just meetings to all participation in RIPE, we need to have more than three people on the Code of Conduct team so that we can have a decent amount of diversity and resilience in that Code of Conduct team.
.
We also heard that we should not essentially suffer from 'not invented here' syndrome. We should be looking to learn from the best implementations of Code of Conducts that have been implemented in other communities, and so that's something that we will be looking at.
.
And we also saw that there was support for some structured continuous improvements with a distinction between the improvement delivered by the Code of Conduct team itself and the Code of Conduct separately from that, and so those are things that we're going to be looking at as we get to work on what will be documents 2 and 3.
.
So obviously we have, I hope, a little bit of time for questions now, and I see that there is something in the queue, but I also wanted to let people know that they can contact us. You can contact us coc‑tf [at] ripe [dot] net. That is our mailing list for contacting the team. The archive of that list is public but that's a great list to go to us and say, hey, I saw a great implementation of a Code of Conduct at this community and this is where you can find the documentation. If you are looking to engage in discussion, please use the RIPE discussion list which is I have the address for there below.
.
At this point I think I have done speaking. I see that there is something in the questions queue. Do I have time for that, Mirjam and Niall?
NIALL O'REILLY: What's in the questions queue is simply a suggestion from Daniel Karrenberg that we have the discussion now rather than waiting until after the final report from Nurani, and that will ‑‑ I will protect the time slot for Nurani and we can discuss things now and I'll archive's Daniel's question because it's ‑‑
MIRJAM KUHNE: I think really given time and sort of if there are any questions to any of the task forces or also to my update, I think we'll have some time now to discuss before we go to Nurani. That's a good suggestion, thanks.
NIALL O'REILLY: The microphone queue is empty. Not any more. Randy Bush.
RANDY BUSH: I don't want to put it negatively, but what serious issues are there in the actual code in deciding about the code, not about the processes and the processes? Tell us something interesting about the Code of Conduct.
LEO VEGODA: Are you asking, Randy, for a discussion about what's going to be in the updated version based on the feedback that we already received?
RANDY BUSH: What have you actually learned in all this process about the Code of Conduct? What kind of things need to change? Anything about the code, not the process.
LEO VEGODA: I would say that what we learned about the code itself was that it's useful to have examples of the behaviours that people should exhibit and the behaviours that are considered unacceptable, but these need to be rooted in principles and the key thing is that people should be thinking about ‑‑ if I was a recipient of these behaviours, how would I feel? And we don't want the code to be seen as essentially some kind of software and, if it's not in the code, then it's acceptable. And so, we want this to be guidance but we want people to use their intelligence in implementing it, and when I say implementing it, it's implementing it as a participant in the RIPE community, moderating one's own behaviour to make sure that we are sensitive to the feelings of others, as well as when there is a Code of Conduct team, they will need to use their emotional and intellectual intelligence in implementing the code when they evaluate reports. And those reports could indeed come from the person that exhibited a behaviour.
.
One of the things that was really important that was brought up in the discussion on the mailing list was that essentially everyone has suffered from foot and mouth syndrome and walked away from a conversation and felt, oh, I think I just said something that was unacceptable and I don't know how to rectify the situation. And one of the things that the Code of Conduct team in the future ‑‑ and the trusted contacts now ‑‑ can do is help to go and say, you know, yes, you did put your foot in your mouth, but we can help mediate so that you can resolve that situation and bring things back to the place that they ought to be.
.
So this is not intended as something that is investigative and judicial. This is definitely intended as something that is meant to be a support to the RIPE community, to help it function more effectively by helping people essentially manage their relationships where they experience some sort of cultural miscommunication because, you know, people participate in the RIPE community from everywhere in the world, and, you know, it's unfortunately occasionally possible to miscommunicate and ‑‑ so the Code of Conduct is there to help people understand what they should be doing and what they shouldn't be doing, but it's not intended to be some sort of punitive judicial code.
.
I hope that was helpful.
MIRJAM KUHNE: I see some confirming comments in the chat and I don't see any more questions, Niall. Is there anything else going on in any of the channels?
NIALL O'REILLY: Not that I see.
MIRJAM KUHNE: Are there any questions to any other topics at this point?
NIALL O'REILLY: One quick remark from myself. I see in the chat Denesh thanking Leo for being extremely coherent at his time. It's 2 a.m. in Randy's time too and he is pretty coherent too, so congratulations to both of them.
LEO VEGODA: Well, my appreciation to the people who make the tea.
NIALL O'REILLY: Now, there is a comment from Vesna? Let me give Vesna the microphone ‑‑ she is not asking ‑‑ she now has asked for it.
VESNA MANOJLIVIC: Good morning. I'll just repeat what I said. The other reason to have a Code of Conduct at all is to make people feel safe in the knowledge that if there is ever a behaviour that hurts them, that is considered unacceptable by the community and it will not be tolerated. So this is really important if we want to get people from unrepresented groups come to the RIPE community and enrich our community with their presence and their contribution and their needs and their points of view, because they do not want to take part in the community that does not have both a Code of Conduct and a very clear procedure of how to report if they think the Code of Conduct has been not followed.
.
Thank you.
NIALL O'REILLY: Thanks, Vesna, and applause in the chat.
MIRJAM KUHNE: I see one more comment or question ‑‑
NIALL O'REILLY: The question is: "The slides for the Database Task Force said each task force member was assigned a topic. Did the Code of Conduct Task Force similarly condense feedback into a list of topics?
MIRJAM KUHNE: From Sandra Murphy.
LEO VEGODA: We didn't condense a feedback in the same way. What I did was, I worked with the rest of the team and we created a little table that said this is the person, this is whether we think the person has been supportive of the draft or not, and this is the feedback that we heard from that person, and we sent that back to the RIPE discussion list. And the goal of that was to let people know that this is what we heard from you. If you think that we have misunderstood what you have told us, please let us know, because this is the information that we are using to drive the work forward.
.
So we did the same kind of active listening technique that the database task force has been using, but we did it in a slightly different way.
DANIEL KARRENBERG: Morning /evening, whatever. I just wanted to really, really support the way that the Code of Conduct Task Force did this. Leo actual put some work in to condense all the feedback into different topics and then republished it, said this is what we heard, and I think this is only to be commended and should be an example on how we do stuff. Thank you.
LEO VEGODA: Thank you very much, Daniel.
MIRJAM KUHNE: Are there any other questions /comments to Leo or Shane or myself?
NIALL O'REILLY: Silence.
MIRJAM KUHNE: I don't see any. All right. Well then we will move on to Nurani's update of the IANA numbering Review Committee. The floor is yours.
NURANI NIMPUNO: Thank you. So, I will be giving a brief and hopefully simple and non‑controversial presentation on a Friday morning. I'll trying to share my screen but I have been told that I don't have permission. Permission is denied. Is someone able to help me with that or to load the pre‑loaded slides.
.
So good morning, everyone, I hope you can see this.
.
So, I am here to give you a brief update from the IANA Numbering Services Review Committee, the IANA RC for short.
.
I added a nice natural theme to give you a nice presentation the morning after the RIPE dinner.
.
So, just a very brief background on what the IANA RC is.
.
As you say or a may not know, there was a transition called the IANA stewardship transition that happened in 2016 which resulted in an SLA being arranged between ICANN and the five RIRs for the services that IANA provides. So it's a resource allocation to the RIRs.
.
And part of that proposal also called for the establishment of the very lightweight IANA Review Committee to look at the services provided by IANA to the RIRs, and make sure that it met the SLA and that it meets the need of the community.
.
So, this was the arrangement before with a contractual arrangement between NTIA and ICANN and that has now been replaced by a contract between the RIRs and ICANN, and the Review Committee is just there to provide a channel, a voice for the community to provide some accountability to the RIRs when it comes to the services.
.
And the IANA Review Committee is just there to really assist and advise the NRO EC when reviewing the services they get.
.
The other idea behind the IANA RC was also to make sure that the number community kept control over the review of the services that they get from IANA because, as, you know, there are other services that the IANA provide, protocols and names, and the name services are a little bit more frequent and complicated than the numbering services, so we wanted to make sure that we stayed out of that review and that we had a known lightweight review mechanism.
.
So the naming services, they have ‑‑ or the naming community had something called the Customer Standing Committee, which has a Charter, and it's a rather involved ‑ well, we wanted to keep our part quite lightweight.
.
So, the numbering ‑‑ the IANA Numbering Services Review Committee consists of 15 members from each RIR region, so that means two community members from each region and one staff member from the RIRs.
.
And the different regions do it in different ways, but in the RIPE region, we have simply kept is ‑‑ we have tried to keep it simple so that whoever is representative on the AOC is also on the IANA RC.
.
So, the IANA publishes ‑‑ the IANA RC is meant to publish an an actual report that we put out to the public and this is really based on the matrix of all reports that IANA publishes, and this is something that the RIRs look at. So, basically, IANA, they publish these monthly reports on their performances that anyone can go in and look at. The RIRs, the staff members and the IANA RC, they put together a nice little matrix, and we put that out to the community to comment on.
.
And it's really the ‑‑ just to give the opportunity to the community to catch anything or if there are any issues for the community to voice their opinions around this. I think anyone who has been involved with the RIRs for any amount of time knows that, since the beginning of time, we have never detected any issues with the services provided by IANA to the RIRs before or after the transition. So, this is really just a way of ensuring that the community knows what's going on, and that things are still fine. And if they are not fine, then it gives the opportunity to the community to say something.
.
This matrix is then put in the report and we publish this.
.
And so, as you probably also know if you have been involved with the RIRs for any amount of time, the services the IANA provide to the RIRs itself, they very simple. Now, also with at least near‑depletion of v4, we have not seen much activity in the v4 space at all, which should come as no surprise to anyone.
.
So over the last year we had 5 requests for AS numbered blocks, one from each RIR, so March, April, May, and then one in October and November. So as you can imagine, these were very simple transactions, they were all responded to within less than a day and implemented in less than a day.
.
So for all of these we established that they meet the SLA ‑‑ they've been acknowledge and implemented and implemented accurately. And that's really what's specified in the SLA.
.
So fortunately, or unfortunately, depending on how you see it, it's been a very straightforward process; all requests were fulfilled accurately and on time. We don't see any indication of failure or near failure. We don't see any interesting patterns, or anything like that, and no concerns were raised by the community.
.
So we conclude that the IANA numbering services operations are within the SLA and that they meet the need of the numbering community.
.
So, we have said it before; In fact, it was Lideman, one of the community members, who said boring is good, and we think that that is the case and we hope that you agree. As mentioned, there are very few IANA requests. We don't foresee that that will change in the future. Things are stable. The IANA services have been stable for many, many years so we don't expect much excitement, and that's not why we are here. We think that's a good thing.
.
We have made some improvement over time to make the report a little bit clearer. If you have other feedback on it, then please let us know. You can do that in the open comment period, but you can also just get in touch with any one of us and have comments on the amount of outreach we do or what font we use for the report, on any other type of feedback.
.
So, that was it. Here are some references for you if you want to know more about the process. Feel free to get in touch with me or any other members.
.
And thank you very much.
MIRJAM KUHNE: Thank you very much, Nurani. I really like your nature theme in this presentation. It's very uplifting, especially it's terrible weather here in Amsterdam today. But thanks for the update. It's an important tasks and I am glad somebody is taking care of this. So thanks for that, you and the rest of the RC.
.
There was a chat conversation about all the acronyms we have been using in this community, especially in the ICANN community.
.
Are there any questions for Nurani? I don't see any. There are nothing in the ‑‑
NIALL O'REILLY: I don't see anything either.
MIRJAM KUHNE: Well, that's it then. Thanks, Nurani. We have still some time. Is there anything else you want to say? I mean, the Community Plenary is, of course, also meant for open mic and open discussions, so is there anything else burning you want to say right now? Then now is the time. Maybe we don't need longer time next time if we don't even fill this one. But, it's Friday morning, I guess we're all tired. If there are no more questions, going once, going twice, then we'll have a quick break before we start the Closing Plenary, in about ten minutes, at 11:30, which will be right here in the same Meetecho room. So grab a coffee or something else, and see you here soon for the last session of the RIPE 82 meeting.
.
(Coffee break)
