[ppml] Proposal for SWIP/RWHOIS extension beyond /29

Yes, that was the intent behind the proposal.

Thanks,

Joe

Owen DeLong wrote:
> Yes... That is my understanding of it as well.
> 
> Owen
> 
> On Feb 6, 2008, at 12:05 PM, Divins, David wrote:
> 
>> Can I please get a clarification, is the following an accurate statement:
>>  
>> This policy simply allows SWIP longer than /29 but does not manadate 
>> such reporting.
>>  
>> Thanks,
>> dsd
>>
>> David Divins
>> Principal Engineer
>> ServerVault Corp.
>> (703) 652-5955
>>
>> ------------------------------------------------------------------------
>> *From:* ppml-bounces at arin.net [mailto:ppml-bounces at arin.net] *On 
>> Behalf Of *Owen DeLong
>> *Sent:* Wednesday, February 06, 2008 2:58 PM
>> *To:* Public Policy Mailing List
>> *Subject:* ***POSSIBLE SPAM*** [ppml] Proposal for SWIP/RWHOIS 
>> extension beyond /29
>>
>> The ARIN AC is about to consider the next steps for the proposal at 
>> the end of this
>> message.
>>
>> In light of that, we would like to get any feedback from the community 
>> on this
>> proposal and especially whether it has support or not from members of the
>> community.
>>
>> In your messages, please indicate if you support the proposal and make
>> any comments you wish as to why/why not.
>>
>> Thanks,
>>
>> Owen DeLong
>> ARIN AC
>>
>>> ## * ##
>>
>>>
>>>
>>> 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 <mailto: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.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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.