Meeting of the ARIN Advisory Council - 31 October 2002 [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.

Eugene, Oregon

Attendees:

Council Members

  • Alec Peterson, Chairman (AP)
  • Bill Darte (BD)
  • Ron da Silva (RD)
  • Sanford H. George (SHG)
  • Mark Kosters (MK)
  • Lea Roberts (LR)
  • John Sweeting (JS)
  • Cathy Wittbrodt (CJW)

Guests

  • Bill Manning, ARIN Board of Trustees(BM)
  • Dennis Molloy, ARIN Counsel (DM)
  • Richard Jimmerson, ARIN Director of Operations (RJ)
  • Thérèse Colosi, ARIN Recording Secretary

Agenda

  1. 2002-1: Lame Delegations in IN-ADDR.ARPA
  2. 2002-2: Experimental Internet Resource Allocations
  3. 2002-3: Micro-Assignments for Multi-Homed Networks
  4. 2002-4: Bulk copies of ARIN’s WHOIS
  5. 2002-5: Amnesty Requests
  6. 2002-6: Aggregation Requests
  7. 2002-7: Micro-assignments for multi-homed organizations
  8. 2002-8: Privatizing POC Information
  9. 2002-9: To allow micro-assignments for end-user organizations
  10. Transfer of 6Bone address space administration
  11. Bulk in-addr.arpa data requests
  12. CLEW Charter language
  13. Any Other Business
  14. Adjournment

Advisory Council Chairman Alec Peterson called the meeting to order at 5:24 PM PST. Roll call was taken. The presence of a quorum was noted and the Chair thanked everyone for attending, and with their help with the proposals.

The Chair noted that AC Member John Brown raised an objection to the meeting being held at a time not announced per the ARIN bylaws. The meeting had sufficient members in attendance to create a quorum and according to the bylaws, participation of those members in attendance would not require written waiver notice to the meeting.

It is reflected here that it is the AC’s intent to provide the raw participant straw-polls that were taken during the ARIN Public Policy Meeting to the proposal authors as feedback on Policy Proposals 2002-3 and 2002-7.

1. 2002-1: Lame Delegations in IN-ADDR.ARPA

This discussion went through the steps to resolve the Lame Delegation issue. Minor adjustments were made to the text resulting from discussions at the ARIN Public Policy Meeting. The revised language is as follows:

ARIN will actively identify lame DNS name server(s) for in-addr.arpa delegations associated with address blocks allocated, assigned or administered by ARIN. Upon identification of a lame delegation, ARIN shall attempt to contact the POC for that resource. The process of contact shall follow at least the following sequence until the lame delegation is repaired:

  1. Email contact to POC information from ARIN database record(s) associated with the in-addr.arpa delegation
  2. Email contact to POC information from ARIN database record(s) associated with ASN(s) originating the route in the global routing table
  3. Telephone contact to any POC information obtained above
  4. Postal mail contact to any POC information obtained above requesting response within 30 days

After completing the contact procedures listed above, and the lame delegation persists, and waiting for a minimum of 30 days following the postal mail being sent, ARIN shall update the resource record with text indicating:

  1. That the delegation has been determined to be lame
  2. The evaluation date of the lame delegation
  3. That contact has been attempted unsuccessfully
  4. The date record was updated

The record shall be further updated by removing the name server delegation(s).

The Chair called for a motion to approve the revised language as a final proposal for consideration by the ARIN Board of Trustees. MK motioned to accept the revisions as written and BD seconded the motion. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

2. 2002-2: Experimental Internet Resource Allocations

It was noted discussion at the Public Policy Meeting contained some focus on commercial use language in this proposal.

CJW noted the overwhelming consensus at the Public Policy Meeting for moving this proposal forward as written and motioned to approve it as a final proposal for consideration by the ARIN Board of Trustees. LR seconded the motion. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

3. 2002-3: Micro-Assignments for Multi-Homed Networks

The Chair noted there was a call for a show of hands to determine consensus for this policy proposal at the Public Policy Meeting and asked the numbers be read aloud.

2 people wanted to accept the proposal as written
3 people wanted to reject the proposal outright
36 people would be willing to accept the proposal with clarification/revision by the authors

CJW stated that the AC needed to respond to the proposal authors with information about the meeting and what they need to do to make changes. It was restated that it is the AC’s intent to provide the raw participant straw-polls that were taken during the ARIN Public Policy Meeting to the proposal authors as feedback on Policy Proposals 2002-3 and 2002-7.

The Chair asked for a motion. CJW moved that due to lack of consensus, this proposal should not move forward and BD seconded. The Chair called for a vote and the motion passed unanimously.

4. 2002-4: Bulk copies of ARIN’s WHOIS

It was noted there was discussion at the Public Policy meeting that supported moving this policy proposal forward. Discussion at the meeting in regard to including point of contact information in bulk copies of WHOIS data obtained from ARIN to reflect the same policy as the other RIRs. It was also noted that any information marked as private should be excluded from bulk copies of WHOIS. This wording of the proposal was modified to:

ARIN will provide a bulk copy of WHOIS output, including point of contact information, on the ARIN site for download by any organization that wishes to obtain the data providing they agree to ARIN’s acceptable use policy. This point of contact information will not include data marked as private.

It is also proposed the existing ARIN Bulk WHOIS Acceptable Use Policy…

“The ARIN WHOIS data is for Internet operational or technical research purposes pertaining to Internet operations only. It may not be used for advertising, direct marketing, marketing research, or similar purposes. Use of the ARIN WHOIS data for these activities is explicitly forbidden. ARIN requests to be notified of any such activities or suspicions thereof.”

…be applied in the implementation of any policy that results from this policy proposal with the addition of the following text:

Redistributing bulk ARIN WHOIS data is explicitly forbidden. It is permissible to publish the data an individual query or small number of queries at a time, as long as reasonable precautions are taken to prevent automated querying by database harvesters.

The Chair called for a motion to approve the revised language as a final proposal for consideration by the ARIN Board of Trustees. LR moved to accept this language as revised, and MK seconded. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

5. 2002-5: Amnesty Requests

It was noted there was discussion at the Public Policy meeting that supported moving this policy proposal forward with minor changes to the language. The resulting language:

If an organization, whether a member or non-member, ISP or end-user, relinquishes a block of portable address space to ARIN, they shall be allowed to receive a block /24 or shorter, returning exchanged space within 12 months, and they shall not be required to justify their use of that space. That is, anyone should be able to decrease their use of address space at any time without fear of the effects of a utilization audit. ARIN staff shall, at their discretion, determine whether the smaller replacement block shall be a subnet of the returned block, or a block allocated from some different range. In the case of an organization name change for address resource records, ARIN’s normal transfer policies will apply. If the exchanged address block was maintained in the ARIN database without maintenance fees, the replacement space shall be as well, but if the returned block had associated maintenance fees, then the replacement block shall also be subject to maintenance fees.

The Chair called for a motion to approve the revised language as a final proposal for consideration by the ARIN Board of Trustees. JS moved to accept the proposal as now written, and SHG seconded. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

SHG volunteered to monitor the status of this policy proposal going forward.

6. 2002-6: Aggregation Requests

It was noted there was discussion at the Public Policy meeting that supported moving this policy proposal forward with minor changes to the language. The resulting language:

If an organization, whether a member or non-member, ISP or end-user, relinquishes a group of portable, nonaggregatable address blocks to ARIN, they shall be allowed to receive a block in exchange, /24 or shorter, but no more than the shortest block that could contain all of the returned blocks. Exchanged space shall be returned within 12 months. For example, if an organization relinquished three /24s, they should be allowed to take either a /24, a /23, or a /22 in exchange. If all of the previous address blocks were maintained in the ARIN database without maintenance fees, the replacement space shall be as well, but if any one of the returned blocks had associated maintenance fees, then the replacement block shall also be subject to maintenance fees.

The Chair called for a motion to approve the revised language as a final proposal for consideration by the ARIN Board of Trustees. RD moved to accept the proposal as now written, and LR seconded. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

7. 2002-7 Micro-assignments for multi-homed organizations

The Chair noted there was a call for a show of hands to determine consensus for this policy proposal at the Public Policy Meeting and asked the numbers be read aloud.

0 people wanted to accept the proposal as written
13 people wanted to reject the proposal outright
31 people would be willing to accept the proposal with clarification/revision by the authors

It was restated that the AC needed to respond to the proposal authors with information about the meeting and what they need to do to make changes. It was restated that it is the AC’s intent to provide the raw participant straw-polls that were taken during the ARIN Public Policy Meeting to the proposal authors as feedback on Policy Proposals 2002-3 and 2002-7.

The Chair asked for a motion. JS moved that due to lack of consensus, this proposal should not move forward and BD seconded. The Chair called for a vote and the motion passed unanimously.

8. 2002-8: Privatizing POC Information

It was noted there was discussion at the Public Policy meeting that supported moving this policy proposal forward with minor changes to the language. The resulting language:

ARIN’s new database allows an organization to designate several points of contact for their organization and resource records. Available types of POCs are Admin, Technical, Abuse, and NOC. If an organization designates several POCs for the management of their organization or resource records in the ARIN database, they are made available via ARIN WHOIS. In order for a point of contact to conduct resource administration for a given resource record in the ARIN database, that POC does have to be associated with the resource record in the ARIN database, and therefore is listed in ARIN WHOIS.

It is proposed organizations be able to designate certain points of contact as private from ARIN WHOIS, with the exception that, at the minimum, one point of contact must be viewable.

The Chair called for a motion to approve the revised language as a final proposal for consideration by the ARIN Board of Trustees. LR moved to accept the proposal as now written, and RD seconded. The Chair called for a vote and the motion passed unanimously. The Chair requested ARIN staff post a final call for comments to the mailing list, as described in the ARIN Internet Resource Policy Evaluation Process.

9. 2002-9: To Allow Micro-Assignments for End-User Organizations

Discussion ensued regarding the fact that consensus in favor of this policy proposal was not reached during the Public Policy Meeting.

The Chair asked for a motion. CJW moved that due to lack of consensus in favor of this proposal, it should not move forward. BD seconded the motion. The Chair called for a vote and the motion passed unanimously.

10. Transfer of 6Bone Address Space Administration

It was noted there is an open comments period on the ARIN Public Policy Mailing List and 6bone mailing list on this subject until December 31, 2002. It was decided that no AC action was required, at this time.

11. Bulk in-addr.arpa Data Requests

The AC discussed whether or not to make this information readily available as other RIRs have done. It was decided to post this issue to the mailing list for a policy discussion. MK volunteered to craft a document to be sent to the list by the next regularly scheduled call.

12. CLEW Charter Language

This agenda item was withdrawn by BD.

13. Any Other Business

There was no other business.

14. Adjournment

Chair called for a motion to adjourn at 6:40 PM PST. LR moved to adjourn and this was seconded by SHG. The motion passed 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.