[arin-ppml] Draft Policy ARIN-2014-3 Remove 8.2 and 8.3 and 8.4 Minimum IPv4 Block Size Requirements

Alvarado, Jose Jose.Alvarado at allstream.com
Tue Apr 15 10:58:42 EDT 2014


As an ISP planner and operator, the concern is with tying to accommodate exceptions as most of our Transit providers have rules that deny >/24 on their route filters. Yes, exceptions can be made but the administration of those exceptions are somewhat cumbersome to keep track of. Agree that ARIN may not be is a position to block or otherwise stipulate the prefix limit, but will be more of a consensus from the global carriers out there.


Regard,


Jose Alvarado
Sr Engineering Specialist, | Technology Operations, Internet & Security  |Customer Operations | * Tel: 416.642.4036 | *Cell: 416.315.4364| * email: jose.alvarado at allstream.com<mailto:jose.alvarado at allstream.com>
MTS Allstream Inc

[sig8]

From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Azinger, Marla
Sent: Tuesday, April 15, 2014 10:48 AM
To: ARIN PPML (ppml at arin.net)
Subject: [arin-ppml] Draft Policy ARIN-2014-3 Remove 8.2 and 8.3 and 8.4 Minimum IPv4 Block Size Requirements

No Support at this time.   I have concerns regarding route table growth.  However, it might be good to review if some exceptions where appropriate can be made.  Although, in the long run operators decide what to route.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140415/9a63517f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17613 bytes
Desc: image001.png
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140415/9a63517f/attachment-0001.png>


More information about the ARIN-PPML mailing list