Meeting of the ARIN Advisory Council - 21 November 2024

Teleconference

Draft Minutes

These minutes are DRAFT. They have been reviewed by the ARIN Advisory Council prior to posting. These minutes will remain draft until they are reviewed and approved by the ARIN Advisory Council at their next regularly scheduled meeting.

ARIN AC Attendees:

  • Kat Hunter, Chair (KH)
  • Matthew Wilder, Vice Chair (MW)
  • Doug Camin (DC)
  • Matthew Gamble (MG)
  • Gerry George (GG)
  • Elizabeth Goodson (EG)
  • Brian Jones (BJ)
  • Kendrick Knowles (KK)
  • Kaitlyn Pellak (KP)
  • Gus Reese (GR)
  • Leif Sawyer (LS)
  • Daniel Schatte (DS)
  • Alicia Trotman (AT)
  • Alison Wood (AW)
  • Chris Woodfield (CW)

ARIN Staff:

  • Michael Abejuela, General Counsel
  • John Curran, President & CEO
  • Eddie Diego, Policy Analyst
  • Richard Jimmerson, COO
  • Lisa Liedel, Director, Registration Services
  • Therese Simcox, Sr. Exec. Assist./Scribe
  • John Sweeting, CXO

Observers:

  • Lily Botsyoe, 2025-elect ARIN AC member
  • William Herrin, 2025-elect ARIN AC member

1. Welcome.

The Chair called the meeting to order at 4:02 p.m. ET. The presence of a quorum was noted. She noted MG would be delayed.

2. Agenda Review.

The Chair reviewed the agenda with the Council and called for any comments. There were no comments.

3. Approval of the Minutes.

(Exhibit A)

It was moved by DS, and seconded by DC, that:

“The ARIN Advisory Council approves the 25 October 2024 Minutes, as written.”

The Chair called for comments. There were no comments.

The motion carried with no objections.

DC stated that the last call period ended last week with no additional feedback received on the Public Policy Mailing List (PPML).

It was moved by DC, and seconded by GR, that:

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2022-12: Direct Assignment Language Update’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for comments. There were no comments.

The motion carried with all in favor, via roll call vote.

CW stated that this policy is currently in the last call period. No further comments have been received and he will address next steps at the next AC meeting in December.

6. Draft Policy ARIN-2023-8: Reduce 4.1.8 Maximum Allocation.

GG stated that nothing new has occurred; however, he is crafting a summary of the presentation with key points and opinions received at ARIN 54. He will post it to the PPML for feedback. He expects that the community will weigh-in on the policy’s direction by the AC’s next meeting in December.

7. Draft Policy ARIN-2024-1: Definition of Organization ID/Org ID.

GR stated that he received comments from the Chair earlier, and he will reach out to the author and then post the text to the PPML for feedback. The Chair noted she pointed GR to the ARIN website where there is a section on Organization ID definition and suggested he apply it.

LS stated that only positive feedback has been received from the ARIN 54 and no further feedback otherwise.

It was moved by LS, and seconded by BJ, that:

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2024-2: WHOIS Data Requirements Policy for Non- Personal Information’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for comments. There were no comments.

The motion carried with all in favor, via roll call vote.

9. Draft Policy ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation.

DS stated that the Policy Analyst contacted him and advised changing instances of ‘assignment’ to ‘allocation’. This has been done and DS will send the text to the Policy Analyst for publishing to the PPML. He also noted that language from abandoned policy 2024-4 policy will be incorporated into the policy.

10. Draft Policy ARIN-2024-7: Addition of Definitions for General and Special Purpose IP Addresses.

KP stated that feedback was received at ARIN 54, and she has reached out to the author with proposed changes. He was in agreement that ‘special purpose’ and ‘general purpose’ are confusing and KP suggested replacing the terms with ‘reserve pool’. The author pointed out that he hesitated on using ‘reserve pool’ because he believed that not all dedicated special purpose addresses are pulled from a reserve pool per the Number Resource Policy Manual (NRPM). The author suggested the term ‘special justification’ instead.

The CXO and Director of RSD confirmed that ‘reserve pool’ covers NRPM Sections 4.4, 4.10 and 6.10. There is no reserve pool for experimental allocations. KP stated she would relay that to the author. KP stated that the author wanted to also include the actual section numbers in the NRPM, and she could work on that.

MW stated there is also an experimental purpose for IP space from Section 11. He did not believe there was much value to try to define it distinctly as it is bordering on redundant and does not clarify anything. KP explained that it was the definition as a whole for ‘reserve’ versus ‘special purpose’. It was noted that the IETF also has definitions of special purpose space that can confuse the matter.

The President and CEO noted that ARIN deals with ‘general purpose’ IP addresses and even if we reserve them for a specific use, they remain ‘general purpose’ in the IETF’s view. We should not borrow the term ‘special purpose’, as there is a state of the art already for that term, including a ‘special purpose’ IP address registry.

MW stated that abandoning the term ‘special purpose’ is necessary, but ‘reserved purpose’ for some other use calls to question any value. The use of the term ‘special purpose’ is a non-starter, and he believes it best to move forward with new terminology and see what the community says.

The CXO noted that if one requested an IPv4 allocation for experimental purpose it would have to be from the waitlist, and a temporary assignment for IPv6 would come from the normal IPv6 free pool.

KP stated there is some value in trying to rework the definition for community input. She will reach out to the author relaying this discussion and formulate a better definition.

(MG joined at this time.)

AW stated that there is community support and that the last call period has ended. There was no negative feedback.

It was moved by AW, and seconded by LS, that:

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2024-9: Remove Outdated Carveout for Community Networks’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for comments. There were no comments.

The motion carried unanimously, via roll call vote.

12. Draft Policy ARIN-2024-10: Registration Requirements and Timing of Requirements with Retirement of Section 4.2.3.7.2.

AT stated that she updated the language based on feedback from the staff and legal review. The update was published today to solicit comments. The Chair stated the update looked good and thanked her for doing so.

13. Draft Policy ARIN-2024-11: IPv4 Transition Efficiency Reallocation Policy (ITERP).

BJ stated that some feedback has been received, but he is still soliciting feedback on the PPML. He noted there has been discussion on what problem is trying to be solved.

KP noted someone mentioned that there are some instances in which ISP reassignment of a /29, per Section 4.10, is allowable. She asked if this is the case. The CXO stated that ARIN cannot stop it from happening; however, it would not support a request for more space.

MW stated that the language for transitions is murky in Section 4.10, and noted that there are many ways to do it for IPv6 space. He suggested that the section might be due for another review — not for this policy — to tighten up the text with some parameters. The CXO agreed. He noted that dual stack is only allowed for DNS servers or critical infrastructure — not for customers. He stated that staff was going to address it in the next PER, and staff and MW can discuss it in January.

14. ARIN AC Working Group.

  • Policy Experience Report (PER) Working Group Update. AW stated that she has read the transcripts for the PER from ARIN 54. She stated she is looking forward to discussing her notes at the WG’s next meeting in December.

15. Any Other Business.

  • Changes in Employment and Affiliation. None reported.
  • ARIN 54 Expense Reports. The Chair reminded the Council to please submit these expenses by 30 November.
  • January 2025 Flights for AC F2F. The Chair stated that an email was sent from Melissa Montgomery, Travel Coordinator on 8 November. Please make arrangements asap if you have not done so already.
  • Trip Report Expectations — Confluence. The Chair stated she and the Vice Chair worked on the trip report template for when AC members travel to other RIR meetings. She asked the Council to review it on Confluence.
  • Mentorship 2025. The Chair asked the Council to please consider being a mentor at ARIN 55 in April next year.
  • January AC Face to Face Meeting.
    • The Chair stated that the AC will vote for an AC Chair in January. She also pointed out that there are two trips that come up in February quickly: NANOG and APNIC in Malaysia. She asked the Council to please keep these in mind if they would like to attend.

    • The COO stated that ARIN staff looks forward to seeing the AC in January and hotel arrangements have been made. He further stated that new AC member Orientation is being scheduled in early December. The Chair and Vice Chair will be open to invite the new members as observers to the AC’s December teleconference after the orientation.

    • General Counsel stated that he too was looking forward to seeing the AC in January and announced a change in personnel in the legal department. He stated that he will be the primary legal support to the AC, with the Deputy General Counsel supporting the group as well.

  • NANOG 93 February 2025. The CXO noted that ARIN will have a complimentary registration code for NANOG’s February meeting. Please check with staff before paying for that meeting registration.
  • 2025 RIR Meetings. MW stated the AC Wiki page has a link to the 2025 RIR meetings for the AC’s reference.

16. Adjournment.

The Chair entertained a motion to adjourn at 4:40 p.m. ET. LS moved to adjourn, seconded by DS. The meeting adjourned with no objections.