If this was actually drafted, I would too.

Doesn't seem like a bad thing.

On 5/1/2014 午後 03:19, Owen DeLong wrote:
I would support.

Owen

On Apr 30, 2014, at 7:49 AM, Jeffrey Lyon <[email protected]> wrote:

Friends, Colleagues,

A couple of years ago I brought up an issue I had run into where the
utilization requirement for new requests is being calculated on a per
allocation basis rather than in aggregate. For example, if an
organization has 4 x /22 and 3 of them are utilized 100% and the
fourth utilized at 75%, that request would be denied. This is a bit
out of balance as an organization with a single /20 utilized at 80%
would have less efficient utilization but would be eligible to request
additional space.

The last time this was discussed it sounded as if the community would
support a policy proposal to change this calculation to be considered
in aggregate vs. per assignment. Does this remain the case?

Thanks,
--
Jeffrey A. Lyon, CISSP-ISSMP
Fellow, Black Lotus Communications
mobile: (757) 304-0668 | gtalk: [email protected] | skype: blacklotus.net
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to