Policy Proposal 2008-1 - Staff Assessment

Member Services info at arin.net
Fri Mar 21 14:46:27 EDT 2008


Policy Proposal 2008-1
Title:  SWIP Support for smaller than /29 Assignments
Proposal Submitted: Feb 26, 2008
Date of Assessment: Mar 21, 2008


ARIN Staff Assessment

The assessment of this proposal includes comments from ARIN staff and
the ARIN General Counsel. It contains analysis of procedural, legal, and
resource concerns regarding the implementation of this policy proposal
as it is currently stated. Any changes to the language of the proposal
may necessitate further analysis by staff and Counsel.

I.      Proposal

Policy Proposal is available as Annex A below and at:
http://www.arin.net/policy/proposals/2008_1.html


II.     Understanding of the proposal

Staff understands that this policy will allow upstream ISPs to report
utilization to ARIN by submitting their customer and/or internal
assignments of /29 or smaller via SWIP and RWHOIS server in addition to
the current accepted method which is a flat file in the form of an excel
spreadsheet of similar.  This will allow customers to use SWIP or RWHOIS
server as a single source for reporting their utilization data back to
ARIN.


III.    Issues and concerns

A.	ARIN Staff Comments

Staff foresees no problems with the implementation of this policy and no
conflicts with current policy.


B.	ARIN General Counsel

Counsel sees no significant legal or litigation issues related to this
policy.


IV. Resource Impact – Minimal

The resource impact of implementing this policy is minimal. Barring any
unforeseen resource requirements, this policy could be implemented
within 90 days from the date of the ratification of the policy by the
ARIN Board of Trustees.  It will require the following:

• Changes to the registration software to accept the submission of /29s
and smaller via the various reassignment templates.
• Changes to Guidelines
• Minor template changes
• May increase RSD’s workload if an overwhelming number of people choose
to swip allocations smaller than /29
• Staff  anticipates no major issues with Whois (performance, storage,
gen, etc.)

Respectfully submitted,

Member Services
American Registry for Internet Numbers (ARIN)




##*##


Annex A

Policy Proposal 2008-1
SWIP Support for smaller than /29 Assignments

Author: Joe Maimon

Proposal Version: 1

Submission Date: 26 February 2008

Proposal type: modify

Policy term: permanent

Policy statement:

4.2.2.1.2.)

"
ISPs must provide reassignment information on the entire previously
allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks.
For blocks smaller than /29 and for internal space, ISPs should provide
utilization data using the table format described in Section 4.2.3.7.5.
"

Replace with

"
ISPs must provide reassignment information on the entire previously
allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks.
For blocks smaller than /29 and for internal space, ISPs should provide
utilization data either via SWIP or RWHOIS server or by using the table
format described in Section 4.2.3.7.5.
"

4.2.2.2.1.)

"
Utilization for blocks smaller than /29 can be documented using the
format described in Section 4.2.3.7.5.
"

Replace with

"
Utilization for blocks smaller than /29 can be documented via SWIP or
RWHOIS server or by using the format described in Section 4.2.3.7.5.
"

4.2.3.7.2.)

"
For blocks smaller than /29 and for internal space, ISPs should provide
utilization data using the format described in Section 4.2.3.7.5.
"

Replace with

"
For blocks smaller than /29 and for internal space, ISPs should provide
utilization data via SWIP or RWHOIS server or by using the format
described in Section 4.2.3.7.5.
"

4.2.3.7.5.) Accounting for additional utilization

"
The following format should be used to provide the required information
for utilization of blocks smaller than /29 and for describing internal
networks:
"

Replace with

"
The following format should be used to provide the required information
for utilization of blocks smaller than /29 and for describing internal
networks when either SWIP or RWHOIS server is not used:
"

Rationale:

With increasing frequency of smaller than /29 assignements to customers,
the ability for ISP's to utilize SWIP or RWHOIS as a single
comprehensive source of their utilization data should be supported. To
implement this policy change, ARIN SWIP would need to no longer reject
SWIP templates smaller then /29.

Timetable for implementation: Immediate





More information about the Info mailing list