Meeting of the ARIN Advisory Council - 17 August 2017 [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
Teleconference
Advisory Council Attendees
- Dan Alexander, Chair (DA)
- Tina Morris, Vice Chair (TM)
- Owen DeLong (OD)
- Andrew Dul (AD)
- David Farmer (DF)
- David Huberman (DH)
- Alyssa Moore (AM)
- Amy Potter (AP)
- Joe Provo (JP)
- Leif Sawyer (LS)
- John Springer (JS)
- Chris Tacit (CT)
- Alison Wood (AW)
- Chris Woodfield (CW)
Scribe
- Thérèse Simcox
ARIN Staff
- Michael Abejuela (MA), Assoc. General Counsel
- John Curran, President & CEO
- Nate Davis (ND), COO
- Sean Hopkins (SHo), Policy Analyst
- John Sweeting (JSw), Senior Director, Registration Services
ARIN General Counsel
- Stephen M. Ryan, Esq.
Regrets
- Rob Seastrom
1. Welcome
The Chair called the meeting to order at 4:02 p.m. EDT. The presence of a quorum was noted.
2. Agenda Review
The Chair reviewed the agenda with the Council and called for comments. The Chair added a reminder, for ARIN 40, of timelines for policy text and dates to Any Other Business. OD requested item 10 be discussed before item 4 on the agenda. The Chair agreed to do so.
3. Approval of the Minutes
It was moved by OD, and seconded by CT, that:
“The ARIN Advisory Council approves the Minutes of 20 July 2017, as written.”
The Chair called for discussion. There were no comments.
The motion carried with no objections.
The Chair stated that item 10 would be discussed at this time, per OD’s request.
10. ARIN-Prop-243: Amend the Definition of Community Network
AD stated that this proposal would create a different definition of ‘Community Networks’. AD stated that he reviewed the text with author; and, then submitted an update of the text and posted it to AC’s Wiki and to their mailing list. He believed the policy was clear and in scope.
It was moved by AD, and seconded by OD, that:
“The ARIN Advisory Council accepts ‘ARIN-Prop-243: Amend the Definition of Community Network’ as a Draft Policy.”
The Chair called for discussion. The Chair stated this proposal was the outcome of work produced by AP and AM.
DF joined at this time (4:10 p.m. EDT). The Chair let him know what discussion was taking place.
The motion carried with all in favor, via roll call vote.
The Chair resumed the agenda in order.
4. Draft Policy ARIN-2017-2: Removal of Community Networks
It was moved by AM, and seconded by OD, that:
“The ARIN Advisory Council abandons “Draft Policy ARIN-2017-2: Removal of Community Networks”.
The Chair called for discussion. The Chair stated this action was mainly due to the replacement text submission of ARIN-Prop-243. AM stated that there had been little support for ARIN-2017-2, and that the replacement proposal may garner more support. CW queried if proposal 243 failed as well, what was the likelihood that there would be a revival of 2017-2, or any other work developed taking a different approach?
AM stated that she had not expected 2017-2 to happen in the first place, and that it was unexpected to a lot of folks. She stated we can only wait and see how proposal 243 fares.
OD stated that he hoped any further work was not a resurrection of 2017-2, as it had no support. He believed that the few people who wanted it on the AC’s docket was because there was no alternative. Now that we have an alternative, if it is rejected, then the community may be satisfied with what is already in place. OD did not see the definition being removed any time soon. He noted that it just may need to be modified in a different way.
The motion carried with all in favor, via roll call vote.
5. Draft Policy ARIN-2017-3: Update to NRPM 3.6: Annual Whois POC Validation
AP stated that she had requested feedback from staff before solidifying the draft text. She noted an editorial change to reallocation and reassignment to clear up confusion.
The Chair asked that, in its current state, did AP intend the text be presented as a draft policy at ARIN 40 in October. AP stated that after feedback is received, she intended to make any needed revisions and present it as edited, as a draft policy.
6. Draft Policy ARIN-2017-4: Remove Reciprocity Requirement for Inter-RIR Transfers
JP stated that there was no change, and updated text had not been posted to the Public Policy Mailing List (PPML). He stated that the policy shepherds are going to revise the text, and post it on Monday in order to receive feedback prior to ARIN 40. It will be presented as a draft at that time.
The Chair stated that he was trying to ascertain which policies would be presented as recommended draft policies.
JP stated that if the shepherds received positive feedback, the policy could be advanced to recommended draft state, and be presented as such, but at this point in time he could not say.
OD stated that he would like to see it stay as a draft policy, in good conscience. If it was ready, via community feedback, his understanding was that the AC should advance it to recommended draft policy status in order to move it to last call after ARIN 40. Otherwise, it will wait until ARIN 41 before the AC could advance it to last call.
Chair stated that he was not suggesting it be advanced, rather he was assessing status from a timeline basis, and the shepherd’s point of view.
JS stated that the draft policy needed a staff and legal review before moving it to recommended draft status. If we’d like to advance it in September, at the AC’s next teleconference, then it needs to be requested. The Chair agreed and clarified that it needed to be requested prior to the September AC teleconference.
JP stated that the staff and legal review as done on an earlier iteration of the text and that it was already updated per that review. The Chair clarified that a staff and legal refresh review was only required if the text was substantially changed. If the changes were minor, the AC could request a review as an update.
JP stated that the changes were made specifically from the staff and legal review already in place.
JSw asked the Chair asked if he wanted ARIN staff re-review the text. The Chair stated that he did not see the need.
Counsel stated that he did not recall if the changes made satisfied the review conducted, noting a re-review could be turned quite promptly. The Chair agreed.
JP asked if discussing the changes with the RS, the other policy shepherd, and posting it to the PPML would that satisfy the matter. Counsel stated that it would not, and to send it back to staff and legal for a final review. All agreed.
The Chair stated that prior to JP posting the revised text, send a note to the Chair and the Chair will request an updated staff and legal review. JP agreed to do so.
AD asked if the draft policy could be advanced at the AC’s September call, to recommended draft status. The Chair stated that the timelines would allow it. He noted that the ideal situation would be that the policy was not being edited up to the time of the AC’s September call, but that it would be ready for advancement prior to the call. AD understood.
7. Draft Policy ARIN-2017-5: Equalization of Assignment Registration Requirements between IPv4 and IPv6
LS stated that he was going to request a staff and legal review, but due to a miscommunication it was posted to the PPML prior to any final edits. He noted that this turned out well, as community feedback was received that clarified the language. He stated that further cleanup needed to be done, and a title name change request would be requested. He intended to post it one more time, and then request a staff and legal review. He intended move to advance this draft policy to recommended draft status on the AC’s September call.
The Chair requested that LS send a note to the Chair to request the staff and legal review at any time. LS agreed to do so.
OD stated that he hoped this draft policy was advanced to recommended draft in time for ARIN 40. LS agreed and hoped the same.
8. Draft Policy ARIN-2017-6: Improve Reciprocity Requirement for Inter-RIR Transfers
AW stated that there was no update at this time. She intended to submit the text to the PPML for comment today, to foster discussion prior to the AC’s September call. She noted the text would be presented at ARIN 40 as a draft policy, for discussion. The Chair agreed that she post it to the PPML to foster as much discussion as possible. AW agreed.
9. Draft Policy ARIN-2017-7: Retire Obsolete Section 4 from the NRPM
CW stated that the initial request for feedback was received as universally negative. After the last AC meeting, he sent one more post to the PPML with an alternative approach to solve issue, noting no support received and very few posts at that.
It was moved by CW, and seconded by JS, that:
“The ARIN Advisory Council abandons “Draft Policy ARIN-2017-7: Retire Obsolete Section 4 from the NRPM”.
The Chair called for discussion. There were no comments.
The motion carried with all in favor, via roll call vote.
The Chair asked the policy shepherds to craft statements of abandonment, by early next week, for both of the draft policies that had been abandoned at this meeting.
10. ARIN-Prop-243: Amend the Definition of Community Network
Previously discussed.
11. Any Other Business
Timeline for Text Edits prior to ARIN 40
The Chair reviewed the timelines to have text edits completed and policy text ready for ARIN 40 with the Council.
ARIN 40 Fellowship Mentors
The Chair stated that ARIN is in need of 9 more volunteers. He stated that if anyone would like to volunteer, to please let staff know as AC participation is instrumental and makes a large, positive difference in a Fellow’s experience at the meeting.
CW volunteered to serve as Mentor. The Chair noted it, and thanked him.
The Chair called for any further business. DF asked if staff had received AM’s updated text for Prop-243. SHo stated that AM’s text had been received.
12. Adjournment
The Chair entertained a motion to adjourn at 4:40 p.m. EDT. OD moved to adjourn, seconded by JS. The meeting adjourned with no objections.
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.