- Rc - nro-apps-2.ripe.net

Fwd: [NRO-EC] IANA Numbering Services Report for February 2020
by Susannah Gray 14 Mar '20

14 Mar '20

FYI -------- Forwarded Message -------- Subject: [NRO-EC] IANA Numbering Services Report for February 2020 Date: Fri, 13 Mar 2020 18:26:33 +0000 From: Naela Sarras <naela.sarras(a)iana.org><mailto:naela.sarras@iana.org> Reply-To: NRO Executive Council <ec(a)nro.net><mailto:ec@nro.net> To: ec(a)nro.net<mailto:ec@nro.net> <ec(a)nro.net><mailto:ec@nro.net> CC: Marilia Hirano <marilia.hirano(a)iana.org><mailto:marilia.hirano@iana.org>, Amy Creamer <amy.creamer(a)icann.org><mailto:amy.creamer@icann.org>, Kim Davies <kim.davies(a)iana.org><mailto:kim.davies@iana.org>, Naela Sarras <naela.sarras(a)iana.org><mailto:naela.sarras@iana.org>, Selina Harrington <selina.harrington(a)iana.org><mailto:selina.harrington@iana.org> Dear NRO-EC, As per the Service Level Agreement for the IANA Numbering Services, we are notifying the NRO-EC that the IANA Numbering Services performance report for February 2020 is published. You will find the January monthly performance report posted at the following link: https://www.iana.org/performance/numbers/202002 Best regards, Naela Sarras Director, IANA Operations ICANN Office: +1 310 301 5819 Mobile: +1 310 463 9669

2 1

Meeting Invitation IANA RC Post Mortem Report Teleconference Tuesday 31 March 2020 at 12:00 PM UTC
by German Valdez 03 Mar '20

03 Mar '20

Dear RC As agreed in the last teleconference here are the zoom details for the post mortem report teleconference to be held on Tuesday 31 March 2020 at 12:00 PM UTC Regards German Valdez === Topic: IANA RC Post Mortem Report Teleconference Time: Mar 31, 2020 12:00 PM GMT Join Zoom Meeting https://apnic.zoom.us/j/603506145 Meeting ID: 603 506 145 One tap mobile +61280156011,,603506145# Australia +61370182005,,603506145# Australia Dial by your location +61 2 8015 6011 Australia +61 3 7018 2005 Australia +61 8 7150 1149 Australia 1800 893 423 Australia Toll-free Meeting ID: 603 506 145

1 0

Reminder: IANA RC 2nd 2020 Teleconference: Tuesday 3 March 2020 at 12:00 PM UTC
by German Valdez 03 Mar '20

03 Mar '20

Dear RC This is just a friendly reminder for the next IANA Review Committee Teleconference to be held next week on Tuesday 3 March 2020 at 12:00 PM UTC. Regards German Valdez === Topic: IANA RC 2nd 2020 Teleconference Time: Mar 3, 2020 12:00 PM GMT Join Zoom Meeting https://apnic.zoom.us/j/587329635 Meeting ID: 587 329 635 Find your local number: https://apnic.zoom.us/u/abv6v2k00E

9 13

public comments for 2019 matrix
by Louie Lee 03 Mar '20

03 Mar '20

Hi, I'd just like to confirm that, to date, we have received only a single comment (from Liman) on the 2019 IANA Performance Matrix Summary Report. Is that correct? I didn't see any others come through, but I may have missed them. Thanks, Louie

3 2

Evento cancelado: IANA RC 2nd Teleconference: Tuesday 3 March 202... mar 3 de mar de 2020 12:00 - 13:00 (GMT) (rc@nro.net)
by juan.alejo.peirano＠gmail.com 25 Feb '20

25 Feb '20

Este evento se ha cancelado. Título: [IANA-RC] IANA RC 2nd Teleconference: Tuesday 3 March 2020 at 12:00 PM UTC Dear RC Based in your input in the last polls please schedule the following days. - 2nd IANA RC 2020 Teleconference: Tuesday 3 March 2020 12:00 PM UTC. (zoom information below) - Place Holder Meeting: Tuesday 24 March 2020 12:00 PM UTC - Post Mortem Report Meeting: Tuesday 31 March 2020 12:00 PM UTC Kind regards Germán Valdez ==== German Valdez is inviting you to a scheduled Zoom meeting. Topic: IANA RC 2nd 2020 Teleconference Time: Mar 3, 2020 12:00 PM GMT Join Zoom Meeting https://apnic.zoom.us/j/587329635 Meeting ID: 587 329 635 Find your local number: https://apnic.zoom.us/u/abv6v2k00E _______________________________________________ Rc mailing list Rc(a)nro.net https://www.nro.net/mailman/listinfo/rc Cuándo: mar 3 de mar de 2020 12:00 – 13:00 Hora de Reino Unido Calendario: rc(a)nro.net Quién: * juan.alejo.peirano(a)gmail.com- organizador Invitación de Google Calendar: https://www.google.com/calendar/ Recibes este mensaje de cortesía en la dirección rc(a)nro.net de la cuenta porque eres uno de los participantes de este evento. Si ya no quieres recibir más avisos sobre este evento, recházalo. Si lo prefieres, solicita una cuenta de Google en https://www.google.com/calendar/ y controla la configuración de las notificaciones de todo tu calendario. Si reenvías esta invitación, los destinatarios podrían enviar una respuesta al organizador para que los añada a la lista de invitados, o invitar a otras personas independientemente del estado de su propia invitación, o cambiar tu respuesta de confirmación de asistencia. Más información en https://support.google.com/calendar/answer/37135#forwarding

2 1

Invitación: IANA RC 2nd Teleconference: Tuesday 3 March 202... mar 3 de mar de 2020 12:00 - 13:00 (GMT) (rc@nro.net)
by juan.alejo.peirano＠gmail.com 25 Feb '20

25 Feb '20

Tienes una invitación para el siguiente evento. Título: [IANA-RC] IANA RC 2nd Teleconference: Tuesday 3 March 2020 at 12:00 PM UTC Dear RC Based in your input in the last polls please schedule the following days. - 2nd IANA RC 2020 Teleconference: Tuesday 3 March 2020 12:00 PM UTC. (zoom information below) - Place Holder Meeting: Tuesday 24 March 2020 12:00 PM UTC - Post Mortem Report Meeting: Tuesday 31 March 2020 12:00 PM UTC Kind regards Germán Valdez ==== German Valdez is inviting you to a scheduled Zoom meeting. Topic: IANA RC 2nd 2020 Teleconference Time: Mar 3, 2020 12:00 PM GMT Join Zoom Meeting https://apnic.zoom.us/j/587329635 Meeting ID: 587 329 635 Find your local number: https://apnic.zoom.us/u/abv6v2k00E _______________________________________________ Rc mailing list Rc(a)nro.net https://www.nro.net/mailman/listinfo/rc Cuándo: mar 3 de mar de 2020 12:00 – 13:00 Hora de Reino Unido Calendario: rc(a)nro.net Quién: * juan.alejo.peirano(a)gmail.com- organizador * nathalia.sautchuk(a)gmail.com * german(a)apnic.net * rc(a)nro.net Detalles del evento: https://www.google.com/calendar/event?action=VIEW&eid=NDRlZTJ2bDVlZTlrb2Y1c… Invitación de Google Calendar: https://www.google.com/calendar/ Recibes este mensaje de cortesía en la dirección rc(a)nro.net de la cuenta porque eres uno de los participantes de este evento. Si ya no quieres recibir más avisos sobre este evento, recházalo. Si lo prefieres, solicita una cuenta de Google en https://www.google.com/calendar/ y controla la configuración de las notificaciones de todo tu calendario. Si reenvías esta invitación, los destinatarios podrían enviar una respuesta al organizador para que los añada a la lista de invitados, o invitar a otras personas independientemente del estado de su propia invitación, o cambiar tu respuesta de confirmación de asistencia. Más información en https://support.google.com/calendar/answer/37135#forwarding

1 0

IANA RC 2nd Teleconference: Tuesday 3 March 2020 at 12:00 PM UTC
by German Valdez 18 Feb '20

18 Feb '20

Dear RC Based in your input in the last polls please schedule the following days. - 2nd IANA RC 2020 Teleconference: Tuesday 3 March 2020 12:00 PM UTC. (zoom information below) - Place Holder Meeting: Tuesday 24 March 2020 12:00 PM UTC - Post Mortem Report Meeting: Tuesday 31 March 2020 12:00 PM UTC Kind regards Germán Valdez ==== German Valdez is inviting you to a scheduled Zoom meeting. Topic: IANA RC 2nd 2020 Teleconference Time: Mar 3, 2020 12:00 PM GMT Join Zoom Meeting https://apnic.zoom.us/j/587329635 Meeting ID: 587 329 635 Find your local number: https://apnic.zoom.us/u/abv6v2k00E

2 1

FW: [NRO-EC] IANA Numbering Services Report for January 2020
by German Valdez 14 Feb '20

14 Feb '20

FYI From: <ec-bounces(a)nro.net> on behalf of Naela Sarras <naela.sarras(a)iana.org> Reply to: NRO Executive Council <ec(a)nro.net> Date: Thursday, 13 February 2020 at 4:05 am To: "ec(a)nro.net" <ec(a)nro.net> Cc: Marilia Hirano <marilia.hirano(a)iana.org>, Amy Creamer <amy.creamer(a)icann.org>, Kim Davies <kim.davies(a)iana.org>, Naela Sarras <naela.sarras(a)iana.org>, Selina Harrington <selina.harrington(a)iana.org> Subject: [NRO-EC] IANA Numbering Services Report for January 2020 Dear NRO-EC, As per the Service Level Agreement for the IANA Numbering Services, we are notifying the NRO-EC that the IANA Numbering Services performance report for January 2020 is published. You will find the January monthly performance report posted at the following link: https://www.iana.org/performance/numbers/202001 Best regards, Naela Sarras Director, IANA Operations ICANN Office: +1 310 301 5819 Mobile: +1 310 463 9669

2 1

Re: [IANA-RC] Call for Public Comments on the 2019 IANA Performance Matrix Summary Report
by Nurani Nimpuno 10 Feb '20

10 Feb '20

Dear Liman, Thank you so much for your review and your very constructive comments. They are well noted and appreciated. Your comments will be reflected in the final report. Kind regards, Nurani, IANA RC Chair > On 5 Feb 2020, at 10:00, Lars-Johan Liman <liman(a)netnod.se> wrote: > > Nurani, (others), > > I took a look at the report with a certain premonition of what it would > look like. And it did. Meeting the SLAs to 100 % all over. > > This matches very well the levels we see in the similar monthly reports > to the ICANN Customer Standing Committee (CSC) - a committee with a > corresponding auditing function for IANA's performance on the domain > name side. More often than not they meet the SLAs to 100 % and when they > don't, it's a few nagging decimals below, and the explanation is nearly > alway a specific SLA which is surprisingly ill-design (we're slowly > fixing that) and where action times outside the control of the IANA are > taken into account, which is unfair. > > The IANA is probably the most well-run service on the entire Internet, > and I suggest that you let the people that operate the IANA services > know that they're doing a stellar job, and that what they do is very > much appreciated by the community. That is certainly how I feel, and the > message I try to convey from our (the CSC's) side. > > Best regards, > /Lars-Johan Liman > CSC Chair, Netnod LIR > #---------------------------------------------------------------------- > # Lars-Johan Liman, M.Sc. ! E-mail: liman(a)netnod.se > # Senior Systems Specialist ! Tel: +46 8 - 562 860 12 > # Netnod Internet Exchange, Stockholm ! http://www.netnod.se/ > #---------------------------------------------------------------------- > > nurani(a)nimblebits.net 2020-02-04 23:14 [+0100]: >> Dear colleagues, > >> As you may be aware, as a result of the successful IANA Stewardship >> transition in 2016, the IANA Numbering Services are today being managed >> through an SLA between ICANN and the five RIRs. > >> As part of the result of the IANA Stewardship transition, the IANA >> Numbering Services Review Committee (IANA RC) was established in 2016. >> The IANA RC is composed of representatives from each RIR region, and >> advises and assists the RIRs in the review of the IANA Numbering >> Services. > >> The IANA services are today provided by Public Technical Identifiers >> (PTI), which publishes monthly performance reports on the IANA Numbering >> Services (https://www.iana.org/performance/numbers) > >> Based on these monthly performance reports, the five RIRs have produced >> the 2019 IANA Performance Matrix Summary Report: > >> https://www.nro.net/wp-content/uploads/2019-RIR-IANA-summary-report.pdf > > >> The IANA RC IANA 2019 performance report >> ----------------------------------- > >> The IANA RC is now launching a public comment period of 30 days, seeking >> comments and input from the community on the IANA numbering services >> performance and the 2019 IANA Performance Matrix Summary Report. > >> The IANA RC encourages all members of the Internet number community to >> review the public IANA Performance Matrix Summary Report. > >> Comments on the IANA service performance should be sent to: > >> iana-performance(a)nro.net > >> The IANA RC will publish an annual report in March 2020, as advice to >> the NRO EC with its evaluation of the IANA Numbering services. The >> report will be based on the IANA Performance Matrix Summary Report, as >> well as any input gathered on the performance from the global number >> community. > >> The public comment period ends on Friday, 4 March 2020 at 23:59 UTC. > >> All public comments will be published on the IANA RC website, and will >> be considered as input to the final report by IANA. At the end of the >> 30-day public comment period, the IANA RC will meet and evaluate all >> input to the final report. > >> The IANA RC report will be published on the IANA RC website: > >> https://www.nro.net/iana-numbering-services-review-committee > >> Kind regards, > >> Nurani Nimpuno >> Chair, IANA Numbering Services Review Committee > > > > >> References: >> ----------- > >> IANA Numbering Services Review Committee >> https://www.nro.net/iana-numbering-services-review-committee/ > >> Public Technical Identifiers (PTI) >> https://pti.icann.org > >> IANA Stewardship Transition Archive >> https://www.nro.net/internet-governance/iana/iana-stewardship-transition/ > >> The SLA for the IANA Numbering Services >> https://www.nro.net/sla > >> Number Community Proposal >> https://www.nro.net/crisp-final-proposal

1 0

Re: [IANA-RC] DRAFT: 2019 IANA Numbering Services Review Committee Report
by Nurani Nimpuno 08 Feb '20

08 Feb '20

Hi, Thank you for this Ernesto. This is indeed a correct assessment and it does reflect our mandate in this committee. Any services outside of the SLA between IANA/PTI and the RIRs are also outside the scope for this group. If this was an allocation by IANA to the RIPE NCC, I would assume it would be part of that SLA. I am not familiar with the particular allocation. Is there a reason it is not in the IANA report? Could I ask the RIPE NCC representatives Nikolas (and Felipe) staff to clarify this and to determine whether or not it should be included in the RIR Matrix (and consequently therefore also included in the IANA RC report)? Thank you. Kind regards, Nurani > >> On 29 Jan 2020, at 17:32, Ernesto Majó <ernesto(a)lacnic.net> wrote: > > Is this interaction part of the SLA or not? I think this is the key point to agree. > > If this interaction is covered by the SLA, then we must include it in the RC report (even though IANA didn´t include in its reports). > > If not, then we do not have to include it. > > > El 28/1/20 a las 17:59, John Sweeting escribió: >> I think this is fine but am wondering if we are going to mention the fact of the IPv6 /22 allocation made to RIPE on 3/12/2019? >> >> >> >> From: <rc-bounces(a)nro.net> on behalf of Louie Lee <louie(a)louie.net> >> Date: Wednesday, January 22, 2020 at 8:48 AM >> To: IANA Numbering Services Review Committee <rc(a)nro.net> >> Subject: Re: [IANA-RC] DRAFT: 2019 IANA Numbering Services Review Committee Report >> >> Friends, >> >> Due to a number of changes that were made today, attached is draft version 0.3 for your review. >> >> In this draft, I've added links to the "More info" buttons on the 2018 matrix to point to the IANA pages where the graphics were taken from. (Recall that the matrix as originally posted does not contain these links.) We can add links this way in the future if needed. >> >> Louie >> >> On Wed, Jan 22, 2020 at 5:03 AM Louie Lee <louie(a)louie.net> wrote: >> And after fixing the grammatical errors: >> >> The Regional Internet Registry (RIR) staff have reviewed the IANA performance reports for 2019 and confirm that the Service Level Agreements (SLA) were met 100% of the time in all cases. It is noted that the IPv4 unicast request in March was an automatic allocation made to the RIRs in accordance with the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. This allocation was executed as expected with no issues to note. The two IPv6 unicast requests and the one AS number request submitted during the months of May, June, and November fully met the expectations of the RIRs and were executed within the agreed to terms of our SLA with no issues to note. The RIRs recognize the flawless execution of IANA services in 2019. >> >> On Wed, Jan 22, 2020 at 4:54 AM Louie Lee <louie(a)louie.net> wrote: >> And to make this suggested paragraph read just a little better, I added "one" before "AS number request": >> >> The Regional Internet Registry (RIR) staff have reviewed the IANA performance reports for 2019 and confirm that the Service Level Agreements (SLA) were met 100% of the time in all cases. It is noted that the IPv4 unicast request in March was automatic allocations made to the RIRs in accordance with the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. These allocation was executed as expected with no issues to note. The two IPv6 unicast requests and the one AS number request submitted during the months of May, June, and November fully met the expectations of the RIRs and were executed within the agreed to terms of our SLA with no issues to note. The RIRs recognize the flawless execution of IANA services in 2019. >> >> On Wed, Jan 22, 2020 at 4:28 AM Louie Lee <louie(a)louie.net> wrote: >> Thanks for catching that, Juan, and the update to the date, Nurani. >> >> I've updated the suggested RIR summarising statement paragraph with the details of the 2019 number requests: >> >> The Regional Internet Registry (RIR) staff have reviewed the IANA performance reports for 2019 and confirm that the Service Level Agreements (SLA) were met 100% of the time in all cases. It is noted that the IPv4 unicast request in March was automatic allocations made to the RIRs in accordance with the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. These allocation was executed as expected with no issues to note. The two IPv6 unicast requests and the AS number request submitted during the months of May, June, and November fully met the expectations of the RIRs and were executed within the agreed to terms of our SLA with no issues to note. The RIRs recognize the flawless execution of IANA services in 2019. >> >> On Wed, Jan 22, 2020 at 2:42 AM Nurani Nimpuno <nurani(a)nimblebits.net> wrote: >> Hi Juan, >> >> Indeed. I will correct this in Louie’s draft. >> >> Thanks, >> Nurani >> >> >> On 22 Jan 2020, at 10:07, Juan Alejo Peirano <juan.alejo.peirano(a)gmail.com> wrote: >> >> Hi all, >> >> Quick question for clarification: Section 3.3 (datasets, matrix, etc) are from 2018, but conclusions are from 2019. Is that correct? >> >> Thanks! >> >> Juan >> >> El mié., 22 ene. 2020 a las 7:40, Louie Lee (<louie(a)louie.net>) escribió: >> I already found an error that I had made: >> Two IPv6 allocations were made – one during May to RIPE NCC and one during November to ARIN. >> >> Updated PDF attached. >> >> Louie >> >> On Tue, Jan 21, 2020 at 11:26 PM Louie Lee <louie(a)louie.net> wrote: >> On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german(a)apnic.net> wrote: >> • New Action Item 191127-2: LL to circulate the first draft of the IANA RC report before the January teleconference (date TBD). >> >> Dear members of the Review Committee, >> >> Please review the attached the DRAFT 2019 IANA Numbering Services Review Committee Report. Of course, it will be updated again when the RIR review matrix is published and announced on the various mailing lists. >> >> Along with updating the references from 2018 to 2019, these are the more substantial updates I've made since the last report: >> >> Section 2.4 Current members of the Review Committee >> >> Section 4. Conclusion >> >> The Review Committee evaluated the Data sets in Section 3 and observed that: >> One IPv4 automatic allocations were made to all RIRs – during March – in accordance with the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. >> Two IPv6 allocations were made – one during March to RIPE NCC and one during November to ARIN. >> One ASN allocation was made – during June to RIPE NCC. >> And in order to streamline the report, I've moved the links to the RIR announcements for the 30 day comment period on the matrix from section 3.2 to appendix 2. (If interested, the 2018 report can be reviewed for comparison.) >> >> And if anyone would like to suggest changes or comment directly to the draft, you may do so on the Google docs version. >> >> Louie >> >> _______________________________________________ >> Rc mailing list >> Rc(a)nro.net >> https://www.nro.net/mailman/listinfo/rc >> >> >> -- >> Juan Alejo Peirano >> _______________________________________________ >> Rc mailing list >> Rc(a)nro.net >> https://www.nro.net/mailman/listinfo/rc >> >> >> >> _______________________________________________ >> Rc mailing list >> Rc(a)nro.net >> https://www.nro.net/mailman/listinfo/rc > _______________________________________________ > Rc mailing list > Rc(a)nro.net > https://www.nro.net/mailman/listinfo/rc

3 3