[arin-ppml] Upcoming Public Policy Discussions

[Michael Peddemors]

I have one comment..

Having had recent discussions on the current policies, it is important 
that all policies have synergy..

In ARIN-2016-5, we speak of..

"Efficient utilization of at least 50% of cumulative IPv4
address blocks already assigned to them"

I believe this should be extended to also include that the current 
registrant MUST be compliant with existing policies regarding the proper 
use of SWIP or 'rwhois' for any IP space they currently operate, insofar 
as that space is relegated to other parties.

It should also require that all existing POC information is correct and 
up to date.  And if they have a reference to a 'rwhois' server, it 
should be operating, functional and accurate.

Even some of the largest provider(s) do not seem to conform to ARIN 
guidelines, and the transfer process should not be started, unless 
current networks are in compliance.. Not to pick on Time Warner, it was 
just recently reported to me, so fresh in my mind..

eg..

NetRange:       97.76.0.0 - 97.79.255.255
CIDR:           97.76.0.0/14
NetName:        RCSW
NetHandle:      NET-97-76-0-0-1
Parent:         NET97 (NET-97-0-0-0-0)
NetType:        Direct Allocation
OriginAS:
Organization:   Time Warner Cable Internet LLC (RCSW)
....
Comment:        Allocations for this OrgID serve Road Runner commercial 
customers out of the Austin, TX and Tampa Bay, FL RDCs.
....
Found a referral to rwhois.rr.com:4321.

connect: Connection refused

So, at it simplest, I would see that amended to read..

"Accurate record keeping, and efficient utilization of .."


On 16-10-15 08:16 PM, Alexander, Daniel wrote:
> Hello Everyone,
>
> We are going to discuss a number of policies next week at the Public
> Policy Meeting in Dallas. Four of these proposals are focused on
> transfers and needs assessment, each suggesting changes using a
> different approach. To try and help the discussions, the AC wanted to
> put a comparison chart together to compliment the discussion guide.
>
> The attached chart will be provided to people attending the discussions
> in person. We wanted to provide this chart to the mailing list as well,
> for those who cannot make it to the meeting. Please let the Shepherds
> know your thoughts about these suggested changes.
>
> Related proposals:
>
> ARIN 2015-7 Simplified Requirements for Demonstrated Need for IPv4 Transfers
> ARIN 2016-3 Alternative Simplified Criteria for Justifying Small IPv4
> Transfers
> ARIN 2016-4 Transfers for New Entrants
> ARIN 2016-5 Post IPv4 Free Pool Depletion Transfer Policy
>
> Needed feedback:
>
> - Is it useful to break the dependency between section 4 and section 8?
> - Is it useful to simplify the transfer requirements?
> - Are the needs requirements in any of the proposals too lax, or too
> restrictive?
> - Do people prefer one approach over another? Which ones?
>
> Please let the AC Shepherds know your thoughts on these topics.
>
> Thank you
> Dan Alexander
> AC Chair
>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>



-- 
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
------------------------------------------------------------------------
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.