[ppml] Proposed policy - Connective Private Network Allocations

[Member Services]

ARIN received the following policy proposal.  In accordance
with the ARIN Internet Resource Policy Evaluation Process the
proposal is being posted to the ARIN Public Policy Mailing List
and being placed on ARIN's website.

The ARIN Advisory Council will review the proposal and within
ten working days may decide to: 
1)  support the proposal as is, 
2)  work with the author to clarify, divide or combine one or more
    policy proposals, or 
3)  not support the policy proposal. 
 
If this proposal is accepted by the Advisory Council or successfully
petitioned it will be posted as a formal policy proposal to the Public
Policy Mailing List and it will be presented at the Public Policy
Meeting.  If the proposal is not supported by the AC and the author
elects not to petition or the petition fails, then the policy proposal
will be considered closed.

The ARIN Internet Resource Policy Evaluation Process is available at:
http://www.arin.net/policy/ipep.html

Mailing list subscription information is available at:
http://www.arin.net/mailing_lists/index.html

Member Services 
American Registry for Internet Numbers (ARIN) 


### * ### 


Policy Proposal Name: Connective Private Network Allocations

Author: Marla Azinger

Author's Organization: Electric Lightwave

Policy term: Permanent 

Policy statement: Provide separate private networks a means of
privately networking with each other when the use of private IPs have
been deemed inappropriate for this connectivity.

Rationale: 
There are currently a couple different situations in which it seems
public IPs are needed to support a widely used private network.  For
simplicity the E-911 situation is used as the primary example in this
policy proposal discussion.  The E-911 networks are comprised of all
the confidential communication among Police Stations, Fire Stations,
Sheriff Stations, State Troop Stations and various other Emergency
Response Programs.

Background:  Every city and state deploys E-911 services separately.
This has created multiple private networks within every County in the
United States.  There is now an increasing effort to make these separate
entities communicate with each other.  This is achieved by putting these 
individual E-911 networks onto one larger connected private network
while at the same time leaving each individual network with its own
autonomy to do as it will.  Since every separate private network is
maintaining it's very own private network and utilizing the private
IP blocks within it's own network...there are no private IPs easily
identified for use in this connected private network.  

Also, due to the delicate nature of this E-911 network it is imperative
that no IP range "accidentally" gets utilized more than once.  This
leaves us with only one option.  This option is to use public IPs on
the E-911 Connective Networks.

How this has been handled for the past few years:  Either knowingly or
not by the upstream provider, public IPs are already being used for
these private networks.  There is currently one specific company
working with ELI for creating several of these "E-911 connected private
networks."  This company has already attained several different blocks
from multiple large telecom companies.  

Why bring this above the table now:  Several reasons.  One, to make the
entire community aware of this situation.  Two, to provide them with a
clearly documented answer that is supported by ARIN and the internet
community.

9. Timetable for implementation: 
Apr 2004 1st Day of Conference:  Vote on yes or no to implement use of
Public IPs for Private use when requirements are met.

Apr 2004 2nd Day of Conference:  Vote on requirements and supporting
questions detailed below in *proposal step 2.

*Policy proposal step 2
Supporting questions in need of answers and votes after this proposal
has been voted in to new ARIN Policy.  These questions exist in order
to clarify what public IPs should be used, who should be assigning them,
and state what the qualifying requirements should be.

1.  Should a special block of IPs be set aside for this type of use?
	a. Pro: 
	b. Con:  There are already networks using IPs for this purpose
	and they will not want to renumber.  A grandfather clause would
	be needed to protect those that are already using IPs in this 
	manner.

2.  Who should assign these IPs?  Upstream or ARIN?
	a. Upstream Pro:
	b. Upstream Con:
	c. ARIN Pro:
	d. ARIN Con:

3.  What are the qualifying requirements for someone to be allocated IPs
for this type of use?
	a. Emergency Use (Police enforcement organizations, Fire
	departments, 911 dispatch units)
	b. Life support line (ie. suicide hot lines, hospitals)
	c. 

4.  What are the qualifying factors that deem the use of Private IP
blocks for connectivity inappropriate?
	a.  When the quantity of private networks being combined makes
	it numerically unsupportable.