Meeting of the ARIN Advisory Council - 21 July 2022 [Archived]

Teleconference

Attendees:

• Leif Sawyer, Chair (LS)
• Kat Hunter, Vice Chair (KH)
• Andrew Dul (AD)
• Amy Potter (AP)
• Joe Provo (JP)
• Alyssa Quinn (AQ)
• Kerrie Richards (KR)
• Chris Tacit (CT)
• Alicia Trotman (AT)
• Matthew Wilder (MW)
• Alison Wood (AW)
• Chris Woodfield (CW)

ARIN Staff:

• Michael Abejuela, (MA) General Counsel
• John Curran, (JC) President and CEO
• Jenny Fulmer, (JF) Staff Attorney
• Sean Hopkins, (SH) Senior Policy Analyst
• Richard Jimmerson, (RJ) COO
• Lisa Liedel, (LL) Director, Registration Services
• Therese Simcox, Scribe, Senior Executive Assistant
• John Sweeting, (CCO) Chief Customer Officer

Regrets

• Brian Jones
• Anita Nikolich
• Rob Seastrom

1. Welcome

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

2. Agenda Review

The Chair reviewed the agenda with the Council and called for comments.

There were no comments.

3. Approval of the Minutes

(Exhibit A)

It was moved by CT, and seconded by JP, that:

“The ARIN Advisory Council approves the Minutes of 16 June 2022, as written.”

The Chair called for comments. There were no comments.

The motion carried unanimously.

4. Recommended Draft Policy ARIN-2020-6: Allowance for IPv4 Allocation “Swap” Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers.

AP stated that this draft policy is ready to present to the Community at the next ARIN meeting. In the meantime, the policy shepherds can foster further discussion on the Public Policy Mailing List (PPML) to glean any further feedback.

5. Draft Policy ARIN-2021-6: Permit IPv4 Leased Addresses for Purposes of Determining Utilization for Future Allocations

AD stated that problem statement ideas were posted to the PPML to gather support. He requested discussion on the AC’s list as well.

6. Draft Policy ARIN 2021-7: Make Abuse Contact Useful.

AP stated that conflicting responses have been received from the PPML. Some folks do not like having a mandatory email field, and some want the field. She was unclear if it is a problem needing to be solved and stated that she will bring it up at the next Public Policy Consultation (PPC).

7. Draft Policy ARIN 2021-8: Deprecation of the ‘Autonomous System Originations’ Field.

AT stated that the policy shepherds are discussing abandoning this policy, however, there has been some support shown. Discussions are on-going and there is no action to be made at this time.

8. Recommended Draft Policy ARIN-2022-1: MDN Clarification for Qualification

CW stated that this policy has been on hold waiting to be presented at ARIN 50. If there is sufficient support at that time, he intends to move it to last call after the meeting.

9. Draft Policy ARIN 2022-2: Remove Barrier to BGP Uptake in ASN Policy.

KR stated that a staff and legal review was completed this month. There was a suggestion to refine the language in the problem statement, and the shepherds are working on it with the author. They will make sure it is completed by the deadlines to be able to present it at ARIN 50. KR stated she intends to move the policy to recommended draft at the AC’s next meeting.

10. Draft Policy ARIN 2022-3: Remove Officer Attestation Requirement for 8.5.5.

MW stated that feedback was received from the PPML, and obstacles were raised regarding fraud and removing officer attestations - would removing them undermine ARIN’s procedures? MW stated he intends to present the question for the staff and legal review to see if it is a necessary vehicle or not. The Chair asked if he was requesting a review at this time. MW stated he would do so at a later time.

11. ARIN-prop-308: Leasing not intended.

JP stated that he is working with authors on the initial statement as it was problematic. Late yesterday an update was received and circulated to the AC. JP acknowledged that while there is still work to be done, the shepherds can take the pen since the problem statement is clear.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-308: Leasing not intended’ as a Draft Policy.”

The Chair called for comments. AP had concerns regarding the scope, noting that language in the Number Resource Policy Manual (NRPM) regarding IPv6 addresses were not in scope at the time. Further, she was not certain that the guideline principals in the Registration Services Agreement (RSA) are in scope. AD agreed about the scope and stated that he received a new draft only minutes before this meeting. He was not in favor of the motion.

CW asked AD if he was stating that we should expect an updated draft, so it is premature at this time to accept it onto docket? AD responded that since the draft was posted this morning, he had not had a chance to fully understand it compared to the old language, in addition to putting property statements into the NRPM. He believed the AC should consider these items at the next meeting to give the Council a chance to review the updated language.

JP understood the lag time needed in assessing the problem statement. He noted that the shepherds worked extensively with the authors to streamline the text and believed they have succeeded. He acknowledged that it is unfortunate the update did not arrive sooner. He noted that the AC formally remanded it at their last meeting. Regarding property rights, given that it is in the NRPM, what is out of scope are the fees and how policies are implemented. He stated that the problem statement appears in scope from that perspective. JP stated that many months of discussion took place to get the text to this stage, it has support, and the problem statement is clear – but the language needs to be edited. He believed it has the criteria to move forward.

The motion failed with 7 in favor, 4 against (AD, AP, CT, CW) and 1 abstention (AT), via roll call vote. AT explained that she abstained as she did not have the opportunity to review the text.

12. ARIN-prop-310: Clean-up of NRPM Sections 2.1 and 2.2.

AW stated that minimal feedback has been received from the PPML. Community feedback revealed that they request the term ‘Internet number resources’ vs ‘Internet numbering resources’ as it is confusing.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-310: Clean-up of NRPM Sections 2.1 and 2.2’ as a Draft Policy.”

The Chair called for comments. CT asked if the AC is to move it as a draft policy with an editorial change? AW answered yes, using ‘Internet number resources’. She stated that she agreed that ‘Internet number resources’ makes sense, but if the authors dispute it, she is happy to discuss it.

The motion carried with 11 favor and 1 against (AD), via roll call vote.

13. ARIN-prop-311: Editorial Clean-up of NRPM Sections 2.4 and 2.5.

KH stated that this is an editorial clean up from the NRPM Working Group. She reviewed the changes with the Council.

It was moved by KH and seconded by CT, that:

“The ARIN Advisory Council accepts ‘ARIN-prop-311: Editorial Clean-up of NRPM Sections 2.4 and 2.5’ as an editorial draft policy."

The Chair called for comments. AD stated that the proposal text did not align with the policy style guide, which lists the term ‘IP address(es)’ as an acceptable use. Discussion ensued on the matter with SH noting that the layout of common use within that section of the NRPM should have said ‘IP address or IP addresses’. He stated that one does not need to follow the term ‘IP address(es)’ to the letter – it can mean one address or more than one address.

JP stated that to SH’s point, there have been zero hits for the parenthetical use of the word. AD suggested a revision. CT suggested moving it forward now and changing the text before it is circulated.

AD stated that he preferred everyone be clear about what is being changed. He would like to follow the Style Guide and then have a clean editorial update put forward.

It was suggested that SH clean the style guide and the shepherds will make an editorial cleanup that matches it.

KH and CT agreed and therefore withdrew the motion.

14.. ARIN-prop-312: Clean-up of NRPM Section 2.11.

AQ stated that this was submitted by NRPM WG and taken out of an editorial proposal. The text has substantive changes and should not be editorial.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-312: Clean-up of NRPM Section 2.11’ as a Draft Policy.”

The Chair called for comments. There were no comments.

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

15. ARIN-prop-313: Editorial Clean-up of NRPM Sections 2.12 and 2.14.

KH stated that this is another policy broken from a larger one that eliminates the capitalization of some words and makes the meaning of ‘intended’ clear.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-313: Editorial Clean-up of NRPM Sections 2.12 and 2.14’ as an editorial change.”

The Chair called for comments. There were no comments.

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

16. ARIN-prop-314: Clean-up of NRPM – Introduction of Section 2.17

AW stated that this section deals with defining ‘IANA’. During this meeting she received a definition from the IANA Operations Manager on how they would like the definition to read. AW stated she has forwarded it to the policy authors and is awaiting their feedback.

17. ARIN-prop-315: Editorial Clean-up of NRPM Section 2.16.

KH stated that this is the last editorial clean up from a larger proposal. The focus is to ensure that the meaning of text is clear and to clarify the word ‘utilize’ and other statements.

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

“The ARIN Advisory Council accepts ‘ARIN-prop-315: Editorial Clean-up of NRPM Section 2.16’ as an editorial change.”

The Chair called for comments. There were no comments.

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

18. ARIN-prop-316: Streamlining Section 11 Policy Language.

CT stated that this came from the Policy Experience WG. The problem statement is clear and within scope. He noted the problem statement is general, but it is within scope. The intent is to perform general cleanup for clarity and make it consistent with the experience of those who use the section.

It was moved by CT, and seconded by AD, that:

“The ARIN Advisory Council accepts ‘ARIN-prop-316: Streamlining Section 11 Policy Language’ as a Draft Policy.”

The Chair called for comments. There were no comments.

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

19. ARIN AC Working Groups

• Number Resource Policy Manual Working Group (NRPM WG) Update. JP stated that they received good feedback on several proposals and will update the ones that were not moved forward in today’s meeting. They will have a more detailed discussion on Sections 2.10 and 2.15.

• Policy Development Process Working Group (PDP WG) Update. AP thanked everyone who reviewed the last version of the PDP and provided feedback. She stated that the WG made revisions from the feedback and circulated a new version via email and a redline as well. She is hoping to have a vote on sending the revised PDP to the ARIN Board under any other business, if ready.

  For the record, the Chair stated that AQ had left the meeting. He noted there were now 11 on the call and noted the presence of quorum.

• Policy Experience Report Working Group (PER WG) Update. AW stated that the WG is reviewing the PER from ARIN 49 and getting items submitted shortly.

20. Any Other Business

• Changes in Employment and Affiliation. The Chair called for any changes. KR reported that she now works for a local World Bank project. AP reported that she is on the Board of Directors of her company. LS reported he is accepting a different position within his company in networking.

• ARIN Election Cycle. The Chair stated that the cycle closed on Friday, July 8th. Candidate eligibility for both the AC and Board are in progress and are due next Friday. He stated that we will know if there are enough candidates for both elections at that time.

• Vote on PDP Update. AP reiterated that she had sent a revised draft, noting that one change has been made since then in the beginning of section 2.12. This was in response to requests for clarity made by the Chair. She read the changes to the Council.

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

  “The ARIN Advisory Council moves to send the revised Policy Development Process to the ARIN Board of Trustees for adoption.”

  The Chair called for discussion. JP asked what level of community input is required. AP responded it was not formalized but, from discussions with the President, the AC recommends it to the Board, and it is sent to the Community for input before it is adopted.

  SH, in the absence of the President, explained and reiterated that it is sent to the Board with a sense of the AC that the Board can put it in place, but it is up to the Board if it goes further.

  AP stated she believed it would be good for the Community to provide input, but the motion is to send it as-is to the Board.

  CT thanked the working group for their diligent and thorough work. He stated it was a huge undertaking and a job well done.

  AD reiterated that the WG believes that the revised PDP is ready for the Board and if it can be implemented, it would be great. The Community should opine on it, but it is a completed document that the Board can implement.

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

21. Adjournment

The Chair entertained a motion to adjourn at 5:26 p.m. ET. AD moved to adjourn, seconded by KH. The meeting adjourned with no objections.