Meeting of the ARIN Advisory Council - 16 May 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)
  • 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
  • Alyssa Arceneaux, Exec. Coord./Scribe
  • John Curran, President & CEO
  • Eddie Diego, Policy Analyst
  • Jenny Fulmer, Staff Attorney
  • Richard Jimmerson, Chief Operating Officer
  • Lisa Liedel, Dir., Reg. Svcs.

Regrets:

  • Brian Jones

1. Welcome.

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

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 CW, and seconded by DC, that:

“The ARIN Advisory Council approves the 17 April 2024 Minutes, as written.”

The Chair called for comments. There were no comments.

4. Draft Policy ARIN-2022-12: Direct Assignment Language Update.

DC stated that he and LS reviewed all feedback received from ARIN 53, along with prior feedback received. The only notable comment was that some of the subsections had assignments listed and that it was fine to craft a separate proposal to follow up.

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

“The ARIN Advisory Council moves ‘Draft Policy ARIN-2022-12: Direct Assignment Language Update’ to Recommended Draft Policy status.”

The Chair called for discussion. There were no comments.

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

Retire 4.2.1.4 Slow Start. KP noted the very positive feedback at ARIN 53 and that the policy has now completed the last call period. She stated the policy is ready to move forward.

It was moved by KP, and seconded by AT, that:

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2023-1: Retire 4.2.1.4 Slow Start’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for discussion. There were no comments.

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

AW stated this policy was moved to Last Call, which ends on 22 May. Next week, this policy will be complete.

AT stated that this policy had a successful last call period, which expired, and there were no additional comments on the Public Policy Mailing List (PPML).

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

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2023-6: ARIN Waitlist Qualification’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for discussion. There were no comments.

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

CW stated that this policy is currently in a holding state. The policy shepherds are waiting to see how 2022-12 has progressed, and will then consider other revisions that were made at ARIN 53.

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

GG stated that there was good discussion at ARIN 53, and he is now seeing a general direction in the comments. He noted that there was some concern about what to do with those on the current waitlist if the policy changed. He asked if language should be added regarding the waitlist, or would it need to be posted to the PPML.

The Chair suggested that the language could be added, and that GG has the pen to make the changes, especially if the community is in favor. She stated GG could reach out to the PPML if he desired, but he can make these changes because they do not change the policy statement.

GG asked that since there is no specific policy on the impact of policies within ARIN, would this create an issue with this one folded in? The Chair noted that it was brought up in the last meeting and language could be drafted in the direction he wants to go with those on the waitlist. She noted she is not in favor of this approach because they have to be pulled out later, but understood the approach with this policy. The President commented that the most important aspect to consider is if the policy is changed, make sure it is clear how those currently on the waitlist will be handled. He further noted the problem last time the policy was changed, and it was not clear about the current waitlist.

MW asked about introducing temporary language - could the language be explained in the comments section of Number Resource Policy Manual (NRPM), not the document itself, so as to make it more temporary? The President replied that the NRPM document is all temporary, for arguments sake, just note the circumstance in which the policy changes, and we will then change the language again stating that this policy is no longer valid (or remove it with an editorial change).

CW asked what this would look like in the policy text - would there be a reference to specific language? The President stated that there would be a reference. Going forward, he advised to post the statement as new text, and add a new section stating that prior to the adoption of this policy, parties on the waitlist will transition this way. That way, when it gets substantiated, it will go with the draft policy’s number and be adopted.

GG stated that he plans to comment on the PPML regarding the language surrounding the existing waitlist to garner guidance from the community.

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

GR stated that after ARIN 53, the policy went to staff and legal for review and the review came back clean.

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

“The ARIN Advisory Council moves ‘Draft Policy ARIN-2024-1: Definition of Organization ID/Org ID’ to Recommended Draft Policy status.”

The Chair called for discussion. There were no comments.

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

11. Draft Policy ARIN 2024-2: WHOIS Data Requirements Policy for Non-Personal Information.

LS stated that supportive feedback from ARIN 53 was received, and the policy shepherds are now addressing some of the text’s issues (postal and address information). There are also some questions on Section 2 and Section 3 definitions, but they are continuing to move forward.

12. ARIN-edit-2024-3: Edit 6.5.8.3 Section 2.

KK stated that there were no issues from the community on this edit.

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

“The ARIN Advisory Council, having completed a successful policy development process for ‘ARIN-edit-2024-3: Edit 6.5.8.3 Section 2’, recommends it to the ARIN Board of Trustees for adoption.”

The Chair called for discussion. There were no comments.

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

13. ARIN-prop-331: Addition of Definitions for General and Special Purpose IP Addresses.

KP stated that the Policy Analyst and the ARIN communications team had an editorial change to the problem statement about not using acronyms, and the author has accepted this change. KP noted a concern about the problem statement and whether is it clear enough. Regarding the special purpose and general purpose IPv4 address definition, and special purpose and general purpose IPv6 definitions, she asked would special purpose be confusing with those words already in use?

The President explained that special purpose comes from the Internet Engineering Task Force (IETF), and is used in many different ways. He believed it was fine to have multiple special purposes for all different types of addresses.

MW stated that the special purpose term appears twice in the NRPM – once with regard to the Internet Assigned Numbers Authority (IANA), and once in Sections 4.4 and 4.10. He agreed with the President’s comments.

GG asked that once those IP addresses are issued, would there be any differentiation on how they are used or routed? Is the special purpose referencing the allocation instead of the address itself? The President advised to think about how it is used presently in Sections 4.4 and 4.10, where it has typical constraints, and where the definition currently overlaps in both sections.

The COO noted that some of these policies are notable enough to have a running page of tracking, and he wanted to make sure it was mentioned during this discussion. KP stated that she has an established line of communication, and will reach out about defining all of the purposes, instead of listing all of the purposes.

14. ARIN-prop-332: Internet Exchange Point Definition.

MG stated that the communications team had a few edits on this proposal, such as spelling out the acronym. The policy shepherds worked with the author to resubmit the proposal with corrections, and it is now ready to move forward.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-332: Internet Exchange Point Definition’ as a Draft Policy.”

The Chair called for discussion. CW stated he would recommend one specific change regarding the use of the word ‘ethernet’ so as not to tie the text to one specific technology. The Chair stated that MG could make that change and still move the proposal forward as he would then have the pen. MW agreed.

KK asked, do we need to include the word ‘three’? MG noted the use of ‘minimum of three’ because it differentiates between private parties. MW also noted that Section 4.4 also relates to that term. DS noted ‘three’ is also listed in prop-333, and he will make sure that both policies use the same language/definition.

GG asked about changing the word ‘ethernet’ to mention interconnection or connection with Layer 2 interface and would that still be potentially limiting? CW stated that in practical terms he believes that most must be Layer 2, physically or virtually. EG stated that ‘broadcast domain’ would be the broader term that could be used. CW agreed.

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

15. ARIN-prop-333: Rewrite of NRPM Section 4.4 Micro-Allocation.

DS stated that there are many different sections in this proposal including router and TLD, but it is within scope.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-333: Rewrite of NRPM Section 4.4 Micro-Allocation’ as a Draft Policy.”

The Chair called for discussion. MW stated he believed it is worth clarifying areas that are not well-sparsed, and it is a good proposal to accept onto the docket.

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

16. ARIN-prop-334: 6.5.1a Definition Update.

KK stated that he will make a motion to move this proposal to draft policy status, but he will canvas the community as it may be more editorial in nature.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-334: 6.5.1a Definition Update’ as a Draft Policy.”

The Chair called for discussion. The Chair agreed with KK, but it could make some people feel like it is less restrictive in a legal sense, however, it should be fairly simple through the PDP. MW agreed. He advised to err on the side of accommodating feedback regarding an editorial update.

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

17. ARIN AC Working Group.

  • Policy Experience Report (PER) Working Group Update. AW stated that ARIN 53 was a very effective meeting and some easy editorial proposals resulted. She noted that AT will have a proposal coming out next month, but is continuing to work with staff on clarifying some others.

18. Any Other Business.

The Chair called for any other business.

  • Changes in Employment and Affiliation. No changes were reported.

19. Adjournment.

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

Related