[arin-ppml] ARIN Multiple Discrete Networks Policy

[Jimmy Hess]

On Sat, Oct 1, 2011 at 10:29 AM, Richard A Steenbergen <ras at e-gerbil.net> wrote:
> On Sat, Oct 01, 2011 at 01:11:52PM +0000, John Curran wrote:
> specifically defined list of example compelling reasons is not a
> compelling reason, because of an exclusionary rule which doesn't exist
> anywhere in the policy (namely that you can't possibly solve the problem

Something needs to determine if there is a compelling reason.
The most obvious would be a business need for discrete networks
created by a technical
requirement.

I don't think it's necessarily reasonable/possible to codify every
feasible situation
in which multiple discrete networks are called for.

This is an engineering decision which should be handled based on sound
technical merits.
Since ARIN staffs'  job is to examine the application, not to review
technical decisions,

Perhaps what ARIN should do is provide an option for an "independent
technical review"
of the merits for an organization operating discrete networks, instead
of one network;
where the applicant would be required to find a "reviewer"  mutually
agreed upon by
ARIN and the applicant,   who would then be required to perform a
review, and submit their
findings directly to ARIN,  keeping them confidential from the applicant.

Then instead of staff making an arbitrary judgement call;  they would
be relying on the integrity
of the reviewer.      "Independent"  would imply  the reviewer has no
relationship with the applicant.

--
-JH