Meeting of the ARIN Advisory Council - 15 November 2018 [Archived]

Teleconference

Advisory Council Attendees:

• Tina Morris, Chair (TM)
• Leif Sawyer, Vice Chair (LS)
• Andrew Dul (AD)
• David Farmer (DF)
• Amy Potter (AP)
• Joe Provo (JP)
• Kerrie Richards (KR)
• John Springer (JS)
• Chris Tacit (CT)
• Alicia Trotman (AT)
• Alison Wood (AW)
• Chris Woodfield (CW)

Scribe:

• Therese Simcox

ARIN Staff:

• Michael Abejuela (MA), Assoc. General Counsel
• John Curran, President & CEO
• Nate Davis, COO (ND)
• Sean Hopkins (SHo), Policy Analyst
• Richard Jimmerson (RJ), CIO
• John Sweeting, (JSw) Sr. Director, Registration Services

ARIN General Counsel

• Stephen Ryan, Esq.

Observers

• Kat Hunter – 2019 AC member-elect

Regrets

• Alyssa Moore

• Rob Seastrom

Absent

• Owen DeLong

1. Welcome

The Chair called the meeting to order at 4:0 p.m. EST. The presence of a quorum was noted. The Chair welcomed Kat Hunter, 2019 AC member-elect, as an observer to the meeting.

2. Agenda Review

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

3. Approval of the Minutes

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

“The ARIN Advisory Council approves the Minutes of 05 October 2018, as written.”

The Chair called for comments. No comments were made.

The motion carried with no objections.

4. Recommended Draft Policy ARIN-2017-12: Require New POC Validation Upon Reassignment

CT stated that following the discussions at the AC’s last meeting, AD made suggestions of significance to the policy text. CT noted that there has only been one noted clarification from DF. CT further stated that the Public Policy Mailing List (PPML) was quiet and those that commented had supported the policy. Before formally making any edits, CT wanted to meet with the AC to see if there was any further feedback from them, or to find if the text is it acceptable as proposed.

AP stated that 2017-3 has implementation instructions based upon the implementation of 2017-12. She stated that she will need to change the implementation instruction in 2017-3 if 2017-12 is accepted as proposed, or should she make a new proposal? AD advised that she keep the same proposal number (2017-3) and edit it to tie into the updates in 2017-12.

CT stated that he and DF will get together and edit it 2017-12 accordingly.

5. Recommended Draft Policy ARIN-2018-1: Allow Inter-Regional ASN Transfers

AW stated it this policy was ready to move forward for Board adoption. She noted positive feedback at ARIN 42, and no comments on the PPML.

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

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2018-1: Allow Inter-Regional ASN Transfers’, 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.

6. Draft Policy ARIN-2018-2: Clarification to ISP Initial Allocation and Permit Renumbering

KR stated that after the October meeting, a staff and legal review was completed on 26 October and there were five staff comments. She noted there were two comments having edits. KR reviewed the edits with the Council and stated that they have been included in the text. She noted that one edit that was updated today, was to change the title to “ARIN-2018-2: Clarification to ISP Initial Allocation”.

It was moved by KR, and seconded by DF, that:

“The ARIN Advisory Council recommends ‘Draft Policy ARIN-2018-2: Clarification to ISP Initial Allocation’ for adoption to Recommended Draft Policy.”

The Chair called for discussion. The Chair noted that, once adopted, the policy needed to be presented at the ARIN 44 Public Policy Meeting in April 2019.

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

7. Recommended Draft Policy ARIN-2018-3: Remove Reallocation Requirements for Residential Market Assignments

JP stated that there were no comments on the PPML during the last call period. He noted that positive feedback was received at the ARIN 42 Public Policy meeting in October.

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

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2018-3: Remove Reallocation Requirements for Residential Market Assignments’, 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.

8. Recommended Draft Policy ARIN-2018-4: Clarification on IPv6 Sub-Assignments

CW stated that the last call period expired on 24 October with no objections seen during that period. He noted one “off the record” conversation about expecting push back on the word ’temporary’. However, he stated that after changing the word to ’transient’, no further comments have been heard.

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

“The ARIN Advisory Council, having completed a successful policy development process for ‘Recommended Draft Policy ARIN-2018-4: Clarification on Temporary Sub-Assignments’, 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.

9. Proposed Editorial Change to Number Resource Policy Manual (Formerly ARIN-Prop-255: NRPM Cleanup)

CT stated that the policy has been through a 30-day consultation period with no comments made.

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

“The ARIN Advisory Council advances the proposed editorial change to the Number Resource Policy Manual, formerly titled ‘ARIN-Prop-255: NRPM Cleanup’, 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.

10. Proposed Editorial Change to Number Resource Policy Manual (Formerly ARIN-Prop-256: Modify 8.3 and 8.4 for Clarity)

AT stated that the last call period ended on 25 October with no comments made.

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

“The ARIN Advisory Council advances the proposed editorial change to the Number Resource Policy Manual, formerly titled ‘ARIN-Prop-256: Modify 8.3 and 8.4 for Clarity’, 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.

11. ARIN-Prop-257: Disallow Third-Party Organization Record Creation

AD stated explained the problem statement is that the creation of POCs by 3rd parties causes problems and should be disallowed. He noted the proposal to be in scope and has a clear problem statement.

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

“The ARIN Advisory Council accepts ‘ARIN-Prop-257: Disallow Third-Party Organization Record Creation’ as a Draft Policy.”

The Chair called for discussion. DF stated this is complimentary to language for revisions for 2017-12 as well. The Chair agreed.

AP cited parts of the Number Resource Policy Manual (NRPM) and asked if this language would conflict with them. AD stated that she cited a valid critique and as the proposal gets published as a draft others in the Community may have similar thoughts about it. AD believed that at this point in time the ideas in the text need to be discussed and the text should be published as-is even with gray areas in the scope. Then the Community can discuss the text and the AC can edit it from feedback received.

JS asked, for clarity, if the AC was about to act on a motion to advance the proposal to Draft Policy inspite of the fact that it may not be in scope? AD explained that the proposal was in scope, but that there are elements in the text that may fall out of scope. He did not believe it was such that it needed to be sent back to the author.

JS stated the criteria of the Policy Development Process (PDP) is that a proposal has a clear problem statement and that the proposal is in scope, not that the problem statement is in scope.

The President clarified that per the PDP, a proposal is in scope if it has a clear statement of a valid, existing problem and it applies to the ARIN region. The policy text may need work, but if the problem statement meets the real problem and in-region criteria, then the proposal is in scope.

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

12. ARIN-Prop-258: Clarify Reassignment Requirements in 4.2.3.7.1

AW stated that the intention of this proposal is to simplify the reassignment requirement. She and AM, as the proposal shepherds, clarified the language with AD, who is the author.

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

“The ARIN Advisory Council accepts ‘ARIN-Prop-258: Clarify Reassignment Requirements in 4.2.3.7.1’ as a Draft Policy.”

The Chair called for discussion. AW read the edits she had made, after having discussions with AD, to the AC for their reference. She noted that any ambiguity will be worked on during the policy process.

CW noted the mention of ’exempted by policy’ and asked if there is any current language that would apply to that or is it theoretical for future policies? AW stated that she and AM had also discussed that issue. AD asked if there are examples of language that would override the requirements in the policy statement. CW clarified that the policy statement language may be overridden by residential privacy policies elsewhere and in the future. AD acknowleged that that was a helpful clarification and thanked CW for noting it.

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

13. Any Other Business

The Chair called for any other business items. The Chair reminded the AC to send in their expenses, if they have not already done so. The Chair also stated that the AC’s travel options have been posted to the AC’s mailing list, and that she was awaiting approximately half of the AC’s input. She noted that she could not assign travel for 2019 without all of the AC’s input.

14. Adjournment

The Chair entertained a motion to adjourn at 4: 47 p.m. EST. JP moved to adjourn, seconded by CW. The meeting adjourned with no objections.