Meeting of the ARIN Advisory Council - 15 February 2007 [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

Attendees:

  • Marla Azinger (MA) Chair
  • Ron da Silva, (RD) Vice Chair
  • Dan Alexander (DA)
  • Paul Andersen (PA)
  • Cathy Aronson (CA)
  • Leo Bicknell (LB)
  • Bill Darte (BD)
  • Alec Peterson, (AP)
  • Matt Pounsett (MP)
  • Alex Rubenstein (AR)
  • Robert Seastrom (RS)
  • Heather Skanks (HS)
  • Suzanne Woolf (SW)

ARIN Staff:

  • Einar Bohlin, (EB) Policy Analyst & Scribe
  • Thérèse Colosi, Call Operator
  • Nate Davis, (ND) Director of Operations
  • Susan Hamlin, (SH) Director of Member Services
  • Richard Jimmerson, (RJ)Director of External Relations
  • Leslie Nobile, (LN) Director of Registration Services
  • Ray Plzak, President & CEO

ARIN Counsel:

  • Stephen M. Ryan

Apologies:

  • Lea Roberts
  • Stacy Taylor

1. Welcome

The Chair called the meeting to order at 4:06 p.m. EST. The presence of a quorum was noted via roll call.

2. Agenda Bashing

The Chair called for any comments. Counsel noted his email request to provide an update at the end of the meeting. The Chair added this to the agenda as a new Item 8.

3. Policy Proposal 2006-7: Changes to IPv6 Initial Allocation Criteria

Proposal shepherd MA reported that she has been working with the author. The author will decide between two versions one post one before the deadline.

4. Policy Proposals

Shepherds for A, B & C below are MP, LB, BD and PA.

A. Reinstatement of PGP Authentication Method.

MP moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Reinstatement of PGP Authentication Method’, accepts the text, as submitted by the author, as a formal policy proposal; and, requests the President assign it a formal policy proposal number.”

This was seconded by SW. The Chair called for any comments. LB clarified the AC is discussing version 3, which was sent directly by the author to the AC. HS questioned the appropriateness for this policy proposal in the IRPEP, and suggested that the ARIN Consultation and Suggestion Process may be a better place for this policy proposal. MP and others thought that it was appropriate for the IRPEP.

RP noted that ‘non-policy’ text needs to be removed from the policy section. He stated an example of having template instructions in a policy and therefore having to use the policy process to change a template. DA agreed with RP. LB stated that the author wants the basic requirements openly discussed.

RD joined the call at this time (4:15 p.m. EDT).

BD stated that at this time the issue should be brought to the floor for discussion. AP argued that non-policy matters should not be part of policy process.

DA questioned the word “reinstatement” in the proposal name. MP suggested amending the motion. BD accepted this friendly amendment. The new motion reads:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Reinstatement of PGP Authentication Method’, accepts the text, as submitted by the author, as a formal policy proposal; will continue to work with the author; and, requests the President assign it a formal policy proposal number.”

The Chair called for any other comments. There were no other comments.

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

B. Documentation of the X.509 Authentication Method.

MP moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Documentation of the X.509 Authentication Method’, accepts the text, as submitted by the author, as a formal policy proposal; will continue to work with the authors; and, requests the President assign it a formal policy proposal number.”

This was seconded by BD. The Chair called for discussion. BD suggested merging the policy proposals on this agenda under Item 4: A, B & C, into one proposal. RP agreed. The Chair called for any other comments. It was noted that the discussion of 4A above also applied to this proposal. There were no other comments.

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

C. Documentation of the Mail-From Authentication Method.

MP moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Documentation of the Mail-From Authentication Method’, accepts the text, as submitted by the author, as a formal policy proposal; will continue to work with the authors; and, requests the President assign it a formal policy proposal number.”

This was seconded by CA. The Chair called for discussion. It was noted that the discussion of 4A above also applied to this proposal. There were no other comments.

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

D. Changes to IPv6 Policy: Removal of “Interim” Consideration.

DA moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Changes to IPv6 Policy: Removal of “Interim” Consideration’, accepts the text, as submitted by the author, as a formal policy proposal; and, requests the President assign it a formal policy proposal number.

This was seconded by BD. The Chair called for discussion. There were no comments.

The motion carried unanimously via roll call.

E. Changes to IPv6 Policy: Removal of “Multiple /48” Justification.

BD moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Changes to IPv6 Policy: Removal of “Multiple /48” Justification’, accepts the text, as submitted by the author, as a formal policy proposal; and, requests the President assign it a formal policy proposal number.”

This was seconded by MP. The Chair called for discussion. HS pointed out that this would remove important guidelines, not replacing them with anything, and felt that this should not be done. BD and CA noted that this is the very beginning of the process for this policy proposal’s discussion. HS felt that the AC should work with the author. AP argued that working with the author would not make sense. The Chair called for any further discussion. There were no other comments.

The motion carried unanimously via roll call.

F. Changes to IPv6 Policy: Removal of IPv6 Operational Information from NRPM.

CA moved that:

“The ARIN Advisory Council, having reviewed the proposed policy entitled, ‘Changes to IPv6 Policy: Removal of IPv6 Operational Information from NRPM’, accepts the text, as submitted by the author, as a formal policy proposal; and, requests the President assign it a formal policy proposal number.”

This was seconded by BD. The Chair called for discussion. LN stated that the guidelines are useful, and that ARIN needs the guidelines. BD suggested a review of terminology and that the AC work with ARIN staff to make explicit distinctions with terms such as ‘policy’, ‘guidelines’, ‘procedures’, ‘recommendations’, ‘operations’, etc.

RP suggested the outcome could be an annex to IRPEP. MA offered that the information in the NRPM has value, and it should not simply disappear. CA withdrew the motion and, as the author, withdrew the proposal.

DA supported the proposal, and suggested that the clarification should be in regards to the utilization, the policy should be part of that section of the NRPM. BD asked DA to be part of the AC committee to review the terms.

CA made an offer to take this discussion back to the PPML since she is removing her proposal. She suggested that instead of a policy, possibly a Number Policy Operational Guideline (NPOG) document should be created. The Chair acknowledged CA’s offer, and recognized her as the lead on this new project.

The Chair noted that the motion had been withdrawn. CA stated she would post an announcement to the PPML.

5. ARIN Staff Policy Evaluation and Feedback Report

A. Item 1: Initial Needs Policy. RS joined the call at this time (5:02 p.m. EDT). He reported that he and ST will complete their work, and post something by the 22 February deadline for both Item 1 and Item 2.

B. Item 2: Initial Allocations to ISP Policy. Discussed above.

C. Item 3: Subsequent Assignment to End Users Policy. AR stated he would revise the text and submit a proposal.

BD stated that he had wanted to include discussion of the new proposal, IPv4 PI Minimum Size Change, during Item 2, Agenda Bashing, but had gotten disconnected from the Via teleconference. RP stated that the AC will have to meet again, and seeing that the proposal was posted today to PPML, suggested to let it get a few days of discussion on the list first.

D. Item 4, Transfer Policy. PA stated he would have something to submit by the 22 February deadline.

6. RIR Trip Report

A. AFRINIC 5 (December) report. PA noted that he had sent a report to the AC’s list. RP stated he would be happy to pass comments from the AC to AFRINIC.

B. ARIN Subregional Carribbean Workshop Findings. BD provided the AC a report regarding the workshop held in St. Thomas. He noted some of the constraints placed on the development of the Internet infrastructure in the Caribbean. DA noted that many of those constraints could not be solved by the policy process.

RP noted that this portion of the ARIN region had different needs than the developed portion of the ARIN region; and, that the AC should explore the possibility of special policies similar to that created for the former African portion of the ARIN region. He also stated that ARIN would continue its efforts to encourage participation in the various ARIN processes, particularly the policy process.

7. AC Projects

A. Number Resource Policy Manual (NRPM) IPv6 Editing. The Chair noted that this was discussed above during Item 4F.

B. PPML Polling. RP stated that ARIN will test the polling system with the AC next week.

8. ARIN Counsel Update

Counsel provided a brief update of ARIN litigation matters to the AC.

9. Any Other Business

There was no other business.

10. Adjournment

The Chair entertained a motion to adjourn at 5:35 p.m. EDT. BD moved to adjourn, and this was seconded by CA. The motion carried unanimously.

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.