[ppml] Policy Proposal: SWIP support for smaller than /29assignments

Hello,

I agree with the proposal to get ARIN's whois to no longer reject SWIPs with
/30's or smaller blocks.  

However, I would like the changed wording regarding tightened up a little.
I would like this use of SWIP or RWHOIS over submitting in table form to be
completely optional, not recommended as 'should' implies.  For example: 

"For blocks smaller than /29 and for internal space, ISPs must provide
utilization data
via one of the following methods: SWIP, RWHOIS server, or by using the table
format 
described in Section 4.2.3.7.5."

$0.02.

Chris

> -----Original Message-----
> From: ppml-bounces at arin.net [mailto:ppml-bounces at arin.net] On 
> Behalf Of Member Services
> Sent: Friday, January 18, 2008 12:20 PM
> To: ppml at arin.net; rss feed
> Subject: [ppml] Policy Proposal: SWIP support for smaller 
> than /29assignments
> 
> ARIN received the following policy proposal. In accordance 
> with the ARIN
> Internet Resource Policy Evaluation Process, the proposal is being
> posted to the ARIN Public Policy Mailing List (PPML) and 
> being placed on
> ARIN's website.
> 
> The ARIN Advisory Council (AC) will review this proposal at their next
> regularly scheduled meeting. The AC may decide to:
> 
>      1. Accept the proposal as written. If the AC accepts the 
> proposal,
> it will be posted as a formal policy proposal to PPML and it will be
> presented at a Public Policy Meeting.
> 
>      2. Postpone their decision regarding the proposal until the next
> regularly scheduled AC meeting in order to work with the 
> author. The AC
> will work with the author to clarify, combine or divide the 
> proposal. At
> their following meeting the AC will accept or not accept the proposal.
> 
>      3. Not accept the proposal. If the AC does not accept 
> the proposal,
> the AC will explain their decision via the PPML. If a proposal is not
> accepted, then the author may elect to use the petition process to
> advance their proposal. If the author elects not to petition or the
> petition fails, then the proposal will be closed.
> 
> The AC will assign shepherds in the near future. ARIN will provide the
> names of the shepherds to the community via the PPML.
> 
> In the meantime, the AC invites everyone to comment on this 
> proposal on
> the PPML, particularly their support or non-support and the reasoning
> behind their opinion. Such participation contributes to a thorough
> vetting and provides important guidance to the AC in their 
> deliberations.
> 
> The ARIN Internet Resource Policy Evaluation Process can be found at:
> http://www.arin.net/policy/irpep.html
> 
> Mailing list subscription information can be found at:
> http://www.arin.net/mailing_lists/
> 
> Regards,
> 
> Member Services
> American Registry for Internet Numbers (ARIN)
> 
> 
> ## * ##
> 
> 
> Policy Proposal Name: SWIP support for smaller than /29 assignments
> 
> Author: Joe Maimon
> 
> Proposal Version: 1
> 
> Submission Date: Jan 16, 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
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to 
> the ARIN Public Policy
> Mailing List (PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml
> Please contact the ARIN Member Services Help Desk at 
> info at arin.net if you experience any issues.
>