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

Re: [IANA-RC] [AC-COORD] Work Rooms
by Jason Schiller 14 Mar '17

14 Mar '17

Kevin, I look forward to taking advantage of workshop time, to get some stuff accomplished while we are in person. I will be there and help out. I'm thinking about what to do if there is time left over. It might be useful to discuss thoughts about the ASO AC / NRO EC gap, and put some notes down on paper in order to short cut having this discussion over email. We may consider getting the RC together Wednesday evening for putting pen to paper on finalizing procedures if that is needed. ___Jason On Mon, Mar 13, 2017 at 3:47 AM, Kevin Blumberg <kevinb(a)thewire.ca> wrote: > Good Morning everyone, > > > > Carlos was able to secure 2 spots for the ASO to work during the next 2 > days. > > > > I plan to use Tuesday to work on 2016-121214 and would appreciate any ASO > member who is able to contribute to stop by. > > > > I’m sure there will be time for anything other people would like to work > on as a group. > > > > Tuesday, 14 March > > 15:00-17:00 > > MR 5 > > > > Wednesday, 15 March > > 15:00-17:00 > > B4.6 > > > > If you have any work, such as a brainstorming or procedural development > please respond and let everyone know. > > > > Thanks, > > > Kevin Blumberg > > > > > > > > > > _______________________________________________ > AC-coord mailing list > AC-coord(a)aso.icann.org > https://aso.icann.org/mailman/listinfo/ac-coord > -- _______________________________________________________ Jason Schiller|NetOps|jschiller(a)google.com|571-266-0006 <(571)%20266-0006>

3 2

Webex Details IANA RC 2nd Meeting
by German Valdez 13 Mar '17

13 Mar '17

Dear Committee Below you have the webex details for the 2nd IANA RC meeting. This information will be used in the announcement of this meeting in the different RIRs regards German 2nd IANA Review Committee Meeting Wednesday, 15 March 2017 11:00 am | Europe Time (Copenhagen, GMT+01:00) | 1 hr 45 mins Join WebEx meeting https://apnic.webex.com/apnic/j.php?MTID=m38f13c81ebf643af63bd961e341e054f Meeting number: 578 906 568 Meeting password: ianarc Join by phone: Australia toll 61 2 8518 1927 Australia toll free 1800-049-813 China - North toll free 10-800-714-1686 China - South toll free 10-800-140-1717 Hong Kong toll 852 5808 1924 Hong Kong toll free 800-96-3828 India - Landline toll free 000800 100 8151 India - Mobile toll free 000800 100 8152 Indonesia toll free 0018-0301-93594 Japan toll 81 345808165 Japan toll free 00531161210 Malaysia toll free 1-800-815777 Netherlands toll 31 207 94 7999 Netherlands toll free 0800-022-3587 New Zealand toll 64 99291753 New Zealand toll free 0800-45-9102 Singapore toll 65 31581417 Singapore toll free 800-101-2599 South Korea toll free 00798-14-203-5535 Taiwan toll free 00801-12-7313 Thailand Toll Free 0018-00156206-3126 US/ Canada toll 1-650-429-3300 US/ Canada toll free 1-866-469-3239 All/ other call-in numbers https://apnic.webex.com/apnic/globalcallin.php

1 1

Fwd: [NRO-IANAXFER] Announcement IANA Review Committee 2nd Teleconference - 15 March 2017 at 10:00 AM UTC
by German Valdez 09 Mar '17

09 Mar '17

Hi FYI, IANA RC meeting announcement is out now. RIR comms staff received the request for further regional dissemination. I have published this in the NRO media channels Cheers German > Begin forwarded message: > > From: German Valdez <german(a)nro.net> > Subject: [NRO-IANAXFER] Announcement IANA Review Committee 2nd Teleconference - 15 March 2017 at 10:00 AM UTC > Date: 9 March 2017 at 12:20:02 am AEST > To: <ianaxfer(a)nro.net> > > > Dear Colleagues > > This is an invitation to participate as observers of the next IANA Review Committee (IANA RC) teleconference to be held on Wednesday March 15th 2017 at 10:00 AM UTC. Webex information below > > More Information about the IANA RC can be found at > > https://www.nro.net/iana-numbering-services-review-committee/ > > Regards > > German Valdez > NRO > > === > > Draft Agenda > > 0. Welcome > 1. Roll Call > 2. Review Open Actions > 3. Agreement on Review Committee Scope > 4. Internal Operational Procedures > 5. IANA Performance Report > 5.1 performance matrix presented by RC RIR staff members > 5.2 Gap review of performance matrix > 5.3 Discussion of metrics and measurement > 5.4 Discussion of current IANA measurements > 5.4 Gap review of current IANA performance measures > 5.5 Contents of IANA performance review document > 6. Review process > 6.1 Review process internal to the RC > 6.2 Process for community feed back for performance review report > 6.3 Discussion of operating procedures changes for section 5 updates (if any) > 7. Any other community engagement > 8. Next Meeting > 9. AOB > 10. Adjourn > > 2nd IANA Review Committee Meeting > Wednesday, 15 March 2017 > 10:00 am | UTC | 1 hr 45 mins > > Join WebEx meeting > https://apnic.webex.com/apnic/j.php?MTID=m38f13c81ebf643af63bd961e341e054f > Meeting number: 578 906 568 > Meeting password: ianarc > > Join by phone: > > https://apnic.webex.com/apnic/globalcallin.php > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Minutes 1st IANA RC Teleconference
by German Valdez 09 Mar '17

09 Mar '17

Dear Review Committee I’m attaching minutes of the 1st IANA RC teleconference for your perusal. Regards German

4 7

Draft Review Process
by Nurani Nimpuno 08 Mar '17

08 Mar '17

Dear all, In an attempt to move forward on defining scope and processes for this group, I have drafted a proposed Review Process below. I believe this reflects the intention of the CRISP proposal. Given that there are only ~3 requests per year in total for all RIRs, and that we have a history of 20+ years of stable services that the RIRs have been satisfied with, I believe it does not have to be more complicated than this. Happy to discuss any details of this. (The timing, such as September every year, and 30 days comment period, are merely suggestions. Feel free to suggest adjustments to these as you see fit.) Kind regards, Nurani Nimpuno ----------------------- Review Process The RIRs will publish an IANA numbering services review matrix in September every year, summarising the RIR’s review of the performance of the IANA numbering services in the last year. This review matrix gets submitted to the Review Committee who passes it on to the five respective RIR communities for a public comment period of 30 days. The Review Committee gathers input and comments from the five RIR communities, which it reviews and summarises. The Review Committee compiles a final report on the review matrix, with the summarised input appended, which it publishes and submits to the NRO EC as advice. -----------------------

7 7

Participation List IANA RC f2f Meeting in ICANN 58
by German Valdez 08 Mar '17

08 Mar '17

Hi As requested in the last teleconference this is the information of IANA RC members participating remotely or on site in the coming meeting during ICANN 58 AFRINIC Omo Oaiya - ON SITE Douglas Onyango - ON SITE Madhvi Gokool - PON SITE APNIC Tomohiro Fujisaki - ON SITE Brajesh Jain - ON SITE George Kuo - remotely ARIN Louie Lee - ON SITE Jason Schiller - ON SITE Nate Davis - ON SITE LACNIC Nicolas Antoniello - remotely Edmundo Cazarez - remotely Ernesto Majo - ON SITE RIPE NCC Filiz Yilmaz - ON SITE Nurani Nimpuno - ON SITE Andrew de la Haye - ON SITE Regards German Valdez

1 1

Webex Details IANA RC 1st Teleconference - Wednesday February 15th 2017 at 12:00 PM UTC
by German Valdez 07 Mar '17

07 Mar '17

Dear Colleagues Thank you for completing the poll to set the 1st IANA Review Committee Teleconference. Based on your feedback the teleconference would take place at Wednesday February 15th 2017 at 12:00 PM UTC IANA Review Committee 1st Teleconference Wednesday, 15 February 2017 12:00 pm | UTC | 2 hrs Join WebEx meeting https://apnic.webex.com/apnic/j.php?MTID=mcc7249a609a5ff8083d1f75d1e59209e Meeting number: 572 054 243 Meeting password: ianarc https://apnic.webex.com/apnic/globalcallin.php Regards German

3 5

test
by Razvan C. Oprea 07 Mar '17

07 Mar '17

test

1 0

RC meeting in ICANN 58
by German Valdez 06 Mar '17

06 Mar '17

Hi We are aiming to have a f2f meeting during ICANN 58 meeting on Wednesday March 15th from 11:00 - 12:45 Denmark time (GMT +1) As established in the IANA RC chapter we’ll provide remote participation tools. Please could you confirm your availability at this date and time Thanks German

15 15

Re: [IANA-RC] [AC-COORD] A Note for need of Second f2f meeting of ASOAC/RC
by Jason Schiller 03 Mar '17

03 Mar '17

reposing because with the whole thread my mail is too big for the list: Filiz, Rather than a point by point thread which seems difficult to follow, let my try to plainly (and bluntly) restate my previous email. Yes we need to boot strap things. No, that has not been progressing well over teleconference / email Yes, we need to figure out our general process - I hoped this would be done prior to Copenhagen The SLAs are clearly defined and agreed to - https://www.nro.net/wp-content/uploads/SLA-Executed-ICANN-RIRS.pdf Yes, we need to figure out or process for compiling the report - I believe this will be clear and simple - Nate is taking the first stab - There is lots of prior work - Pre-existing SLAs - https://www.ntia.doc.gov/other-publication/2012/icann-proposal - specifically section 1.2.8.1.vi in: https://www.ntia.doc.gov/files/ntia/publications/icann_volume_i_elecsub_par… - Pre-existing ICANN performance reporting: - https://www.iana.org/performance/metrics/20160930#c293 - Between all of this I hope that we will easily agree what needs reporting and our process to compile and review the performance will be self evident, and quickly resolved as we review the preliminary report. Yes, we need to figure out or process for reviewing the report - I believe this will be clear and simple - given everything involved in compiling the preliminary report (see above) I hope that review will be self evident, and quickly resolved. This leaves the general discussion of the role of the RC, and the subsequent discussion of procedures wrt community engagement The scope here is potentially very wide, with a lot of room for contention. It is unclear how quickly we can resolve the contention, and how wide the scope will be which directly impacts how much procedure is needed. ----- Optimistically if preliminary report is good and has everything people are looking for, and we feel there is appropriate detail about how the data is collected and processed, then we can likely close out our procedures for creating and reviewing the report in about an hour. Optimistically if we quickly agree that our scope is narrow, and the only community engagement needed is to ask for feed back on the draft, then we can conclude this discussion, as quickly as we can get agreement and simply lift text from the charter. ----- I am personally optimistic on the first, and see more room for contention on the scope and have concerns that the wider the scope, the more complicate the community engagement procedures. I reasonably hope we can get consensus on scope in 1.5 hours and spend 30 mins making notes on process. I am willing to spend a day putting pen to paper with some feed back here and there from those that are willing and available, and then have another meeting for 1 hour where we tweak and agree to the final procedures. ------ I am concerned as time is currently structured, we will only get resolution, if everything is non-contentions and our scope narrow. If that is not the case, it will likely drag out over phone / email, and ultimately be justification for more f2f meetings. I don't think it makes sense to set up 4 face to face meetings over the next two years. Things should be driven by the amount of work pending. I think we should keep having face to face meetings until we have resolution on the scope question, agreement about the report contents and how we judge compliance, and our process documentation hammered out. I would like to invest a maximum of time in Copenhagen in order to ensure we complete all this work and not need another face to face meeting. I think it will become evident how easy this work is by how the scope discussion goes and if we leave that discussion with good process notes. ------ Once we have all the process, I expect the review process to be very light weight. I also expect the community engagement process to also be very light weight while there are no community concerns with IANA operator's performance, which has been the case. If fact there are only three issues I am aware of and the IANA operators reached out to the communities and/or ASO AC seeking clarification on how to implement global policy. And those both took only a few days discussing and consulting with the community.\ (In the case of the first the answer was new global policy which took a long time to get ratification) 1. What should IANA do once it gives are RIR its last /8, and then later finds it is holding IPv4 addresses from returns? 2. Can IANA give more 4-byte ASNs to an RIR the has a glut of two byte ASNs? 3. When should we open the reclaimed IPv4 pool, as soon as APNIC runs out, or at the 6 month mark that is just a month or so off? ___Jason

3 3