Minutes and Open Actions IANA RC Teleconference Wednesday 27 November 2019
Dear RC I'm attaching minutes of this week teleconference for your review and feedback Open Actions: • New Action Item 191127-1: EM to coordinate with the RIR staff representatives and circulate a first draft of the matrix before the January teleconference (date TBD). • New Action Item 191127-2: LL to circulate the first draft of the IANA RC report before the January teleconference (date TBD). • New Action Item 191127-3: NN and GV to send call for nominations and voting information for the IANA RC Chair Election before the first IANA RC teleconference in January 2020. • New Action Item 191127-4: GV to send out a Doodle poll to find a date for the January IANA RC teleconference. Regards German
Dear German et al, I have reviewed the minutes from the IANA RC November meeting. I find them accurate and propose that we approve them in our January 2020 teleconference. Kind regards, Nurani IANA RC Chair
On 29 Nov 2019, at 00:32, German Valdez <german@apnic.net> wrote:
Dear RC
I'm attaching minutes of this week teleconference for your review and feedback
Open Actions:
• New Action Item 191127-1: EM to coordinate with the RIR staff representatives and circulate a first draft of the matrix before the January teleconference (date TBD). • New Action Item 191127-2: LL to circulate the first draft of the IANA RC report before the January teleconference (date TBD). • New Action Item 191127-3: NN and GV to send call for nominations and voting information for the IANA RC Chair Election before the first IANA RC teleconference in January 2020. • New Action Item 191127-4: GV to send out a Doodle poll to find a date for the January IANA RC teleconference.
Regards
German
<191127_IANA Review Committee Meeting Minutes_Draft 1.0.pdf>_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> . Louie
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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
-- Juan Alejo Peirano
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@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@louie.net <mailto:louie@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@louie.net <mailto:louie@louie.net>> wrote: On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@apnic.net <mailto:german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing>.
Louie
_______________________________________________ Rc mailing list Rc@nro.net <mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc <https://www.nro.net/mailman/listinfo/rc>
-- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
-- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
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@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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
-- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
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@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@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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
-- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
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 <https://www.nro.net/wp-content/uploads/2018-Number-Resource-Perfomance-Report.pdf> 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@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@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@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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
-- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
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@nro.net> on behalf of Louie Lee <louie@louie.net> Date: Wednesday, January 22, 2020 at 8:48 AM To: IANA Numbering Services Review Committee <rc@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<https://www.nro.net/wp-content/uploads/2018-Number-Resource-Perfomance-Report.pdf> 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@louie.net<mailto:louie@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@louie.net<mailto:louie@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@louie.net<mailto:louie@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@nimblebits.net<mailto:nurani@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@gmail.com<mailto:juan.alejo.peirano@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@louie.net<mailto:louie@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@louie.net<mailto:louie@louie.net>> wrote: On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@apnic.net<mailto:german@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<https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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<https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing>. Louie _______________________________________________ Rc mailing list Rc@nro.net<mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc -- Juan Alejo Peirano _______________________________________________ Rc mailing list Rc@nro.net<mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc
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@nro.net> on behalf of Louie Lee <louie@louie.net> *Date: *Wednesday, January 22, 2020 at 8:48 AM *To: *IANA Numbering Services Review Committee <rc@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 <https://www.nro.net/wp-content/uploads/2018-Number-Resource-Perfomance-Report.pdf> 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@louie.net <mailto:louie@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@louie.net <mailto:louie@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@louie.net <mailto:louie@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@nimblebits.net <mailto:nurani@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@gmail.com <mailto:juan.alejo.peirano@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@louie.net <mailto:louie@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@louie.net <mailto:louie@louie.net>> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@apnic.net <mailto:german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing>.
Louie
_______________________________________________ Rc mailing list Rc@nro.net <mailto:Rc@nro.net> https://www.nro.net/mailman/listinfo/rc
--
Juan Alejo Peirano
_______________________________________________ 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
Feedback: When creating defined terms, quotation is preferred over parenthesis since some terms may otherwise be mistaken for parenthetical text. Especially across regions.We also define terms e.g. Review Committee (RC) but then go on to say Review Committee instead of RC. I like consistency and I know we all do to. Very minor nits. Good work overall! Cheers, -M< On Tue, Jan 28, 2020 at 4:00 PM John Sweeting <jsweeting@arin.net> wrote:
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@nro.net> on behalf of Louie Lee <louie@louie.net> *Date: *Wednesday, January 22, 2020 at 8:48 AM *To: *IANA Numbering Services Review Committee <rc@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 <https://www.nro.net/wp-content/uploads/2018-Number-Resource-Perfomance-Report.pdf> 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@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@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@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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
--
Juan Alejo Peirano
_______________________________________________ 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
Thank you, Martin! I had not paid attention that particular usage before, but I'm always happy to learn and adopt best practices to make improvements over time. Ernesto's question is a good one. My feeling is that while we would not have to include the special allocation in the RC report if the allocation was made outside of the SLA, it would still be useful to call it out without weighing in on the administrative activity and its timeline so that the report appears to not conflict with available information in the matrix or otherwise. But first, we do need to understand if the interaction was done under the SLA. Louie On Wed, Jan 29, 2020 at 8:53 AM Martin Hannigan <hannigan@gmail.com> wrote:
Feedback:
When creating defined terms, quotation is preferred over parenthesis since some terms may otherwise be mistaken for parenthetical text. Especially across regions.We also define terms e.g. Review Committee (RC) but then go on to say Review Committee instead of RC. I like consistency and I know we all do to.
Very minor nits. Good work overall!
Cheers,
-M<
On Tue, Jan 28, 2020 at 4:00 PM John Sweeting <jsweeting@arin.net> wrote:
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@nro.net> on behalf of Louie Lee <louie@louie.net> *Date: *Wednesday, January 22, 2020 at 8:48 AM *To: *IANA Numbering Services Review Committee <rc@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 <https://www.nro.net/wp-content/uploads/2018-Number-Resource-Perfomance-Report.pdf> 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@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@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@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@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@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@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@louie.net> wrote:
On Thu, Nov 28, 2019 at 3:32 PM German Valdez <german@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 <https://www.nro.net/wp-content/uploads/2018-IANA-Numbering-Services-Review-Committee-Report.pdf> 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 <https://docs.google.com/document/d/18WRPPQBxlqvuCBoZ19vtVRZEvxKPsZ2R-sTtWwjJVtY/edit?usp=sharing> .
Louie
_______________________________________________ Rc mailing list Rc@nro.net https://www.nro.net/mailman/listinfo/rc
--
Juan Alejo Peirano
_______________________________________________ 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
participants (7)
-
Ernesto Majó -
German Valdez -
John Sweeting -
Juan Alejo Peirano -
Louie Lee -
Martin Hannigan -
Nurani Nimpuno