Considerations for Policy Development

1
Considerations for Policy Development

• Presented by
• UEN
• Network Engineering

2
Timing is Critical

• Many Schools will begin implementation of
  One-to-One Computing grants by this summer
• Some school districts and regions are currently
  out of address space
• Many school districts and regions increasingly
  require 24 hour internet connectivity. Outages
  can currently cause significant problems

3
Technical vs. Political

• It is important that we create an addressing plan
  that is grounded in technical realities and not
  in political what ifs.
• It is truly impossible to accurately predict
  global address utilization over the next 10
  years. Thus, the address plan needs to be
  technically flexible enough to adapt to growth
  and possible infrastructure changes
• The political problems associated with address
  allocation can best be solved by proper
  distribution and use of current address space,
  keeping a watchful eye on total utilization, and
  ultimately applying for new space as current
  space is depleted
• IP addresses are an asset with quantifiable
  financial value. Current utilization reports and
  predictions need to become a part of Steering
  Committee oversight just like Internet Bandwidth,
  Fiber, and circuit utilization.
• With a plan in place based on technology,
  applying for new address space from ARIN will be
  easy

4
The Technical Questions

• Address Portability?
• What should the plan look like?
• Who should administer the plan?
• How can the plan be enforced?
• Does the plan need to completely overhaul all
  current addressing?
• Network Address Translation?

5
Address Portability

• Unlike telephone numbers, IP Addresses are not
  very portable. An IP address is a logical number
  that represents physical location. If you change
  locations you will most likely need to change
  assigned addresses
• UNI and the State of New Jersey vs. NAC June
  2004 proved that the technology for address
  portability just does not exist. The Federal
  Courts ruled that addresses are an asset like any
  other and cannot be surrendered in the event a
  customer wishes to move
• Most people ease this burden by using private
  addressing space to address internal needs.
  Network Address Translation (NAT) helps to keep
  these addresses connected to the Internet
• NAT has saved millions of addresses for ARIN and
  public consumption.
• Service Provider control of addresses, lack of
  portability, and NAT have made more addresses
  available for everyone on the Global Scale

6
Policy Suggestions

• Addresses should be assigned on as needed
  basis, with consideration for 6 months of growth.
  This would adopt ARINs policy for address
  assignment keeping our needs in check with global
  policy
• If an entity moves from one PoP to another
  re-addressing may be required
• Addresses should be assigned from aggregation
  blocks that are as large as possible. Assigning
  large blocks to each PoP will allow for growth
  with respect to districts and regions connected
  to the Pop. Large blocks can be carved up as
  necessary during assignment
• The smallest allowable block size assignable to a
  PoP should be a /22

7
Block Size

• Using pre-assigned large blocks to implement
  address assignment follows the same patterns that
  are used by ISPs and ARIN itself
• A /22 as the smallest block will allow addresses
  to be as portable as possible. If a school does
  change PoPs and falls within a movable /22 than
  the school will not have to be readdressed
• A full analysis of total unused and used address
  space will be required before the appropriate
  large block size can be determined
• Large blocks should be assigned to the PoP and
  broken down into smaller blocks as IPs are needed
• Aggregation of new address space at the district
  or school level is impossible. Aggregation can
  only happen at the ISP. Example ATT cannot
  assign contiguous address space when applying for
  addresses 3 years after the initial application.
  The contiguous space will already be assigned.

8
Address Administration

• UEN has invested in tools for IP address
  management to ease the burden of administering a
  Unified Addressing Plan
• IPControl can be used to allocate, track, and
  assign addresses based on location of assignment
• Large blocks can be pre-assigned to the PoPs for
  use by customers. Some control will be required
  to keep smaller blocks from becoming discontiguous

9
Policy Enforcement

• With the completion of GL3 phase 1 UEN has become
  a true service provider environment. All routing
  of new address space is under very strict control
  by design. Customers must contact UEN in order
  to have a block of addresses routed through the
  UEN network
• Any route added to, or sent to UEN must be
  explicitly stated in UENs router configurations.
  This design was implemented to keep routes
  organized and protected but has the secondary
  benefit of keeping route configuration management
  centralized.
• IPControl can be used to track enforcement of
  address policies. If it is not in IPControl, UEN
  is not routing the address

10
Do We Need a Complete Overhaul of Current Address
Deployments?

• The answer is NO!
• There are many blocks that were assigned under
  the old addressing plans that are very
  aggregatable.
• Of the addresses that have been assigned only
  routed addresses should be left allocated.
  Unrouted address space should be reclaimed for
  future distribution
• In order to spare District, Library, Charter
  School, and Regional techs time and overhead
  current aggregatable large blocks should be
  established and aggregated at the PoPs
• IPControl can be used to discover this
  information
• Some entities will have to change addressing.
  This is a way of life in this Internet era

11
Questions?