Static Routing Policy

This document outlines Frontier policy when performing customer static routing. The policies herein are designed to maintain Frontier as a good internet citizen, reduce possible routing problems internet-wide, and reduce the possibility of legal implications of originating IP prefixes foreign to Frontier's network.

Frontier will only static route Frontier owned net-blocks if the following criteria are met:

  1. Frontier's IP Admin has assigned a netblock from a Frontier CIDR block, and the netblock has a valid SWIP record reflecting its proper sub-delegation.

    Note: Netblocks delegated and routed to Frontier customers within Frontier CIDR blocks will be advertised to Frontier peers as aggregate CIDR blocks only and will not be advertised individually.

Frontier will only static route a maximum of 10 netblocks foreign to Frontier's network per customer if their prefix length is between /24 and /21 (Ex,/24, /23, /22, /21), Frontier is the only internet provider for the customer, and one of the following criteria are met:

  1. The netblock has been delegated to the customer directly by ARIN (or similar registry), and the customer has provided LOA to Frontier, indicating that it is acceptable for Frontier to route the netblock.
  2. The netblock has been sub-delegated by another upstream of the customer; the sub-delegation has been SWIP'd to that customer, and the customer has provided LOA to Frontier, indicating that it is acceptable for Frontier to route the netblock.
  3. The netblock has been directly delegated by ARIN (or a similar registry) to another organization. That organization has provided an LOA to Frontier indicating that it is acceptable for Frontier to route the netblock and that the netblock has a valid RPKI ROA signed for origination from the Frontier network.

If a customer does not meet the above requirements, it is recommended that BGP routing be deployed following Frontier's Customer BGP Policy.