Direct Peering Policy

Policy Number: Operations (ITP) 15-01

Effective Date: 01/01/2015

1. Purpose

The State of Indiana operates a core network hub at a co-located data facility through which the State has the ability to peer directly to non-State entities for a variety of reasons. This policy lays out the terms under which the State would consider a direct peering in order to maximize the efficient use of State resources while providing the best connectivity to connected peers as possible.

2. Revision History

3. Persons, Groups, Systems Affected

All agencies within the Executive Branch of Indiana State Government and those connected to the State backbone.

4. Policy

4.1 A direct peering connection shall be defined as a direct physical network connection between State and non-State entities over Ethernet.

4.2 Direct peering connections will be considered under the following circumstances:

• The non-State entity will be providing connectivity to the State backbone for State offices.
• The non-State entity will be providing connectivity to an application or service in use by State government agencies under contract.
• The non-State entity will be providing development or ongoing support of applications or systems in use by State government agencies under contract.
• There is no other means by which the non-State entity can access the resources.

4.3 Should a peering request be granted, the following guidelines will be followed. The refusal or inability to follow these guidelines may result in the cancellation of a peering request approved under circumstances described above.

• Traffic sourced from the non-State entity destined for the State network shall be filtered by the State to allow only the access needed to perform the duties required.
• Traffic sourced from the State network destined for the non-State network will NOT be filtered by the State. The State strongly encourages any entity peering with the State to provide their own traffic filtering for traffic sourced from the State destined for the non-State network. The State assumes no responsibility for damages to the non-State entity should it decline to provide that filtering.
• The State is not required to accept traffic from or route traffic to any IP subnets listed under RFC 5735.
• The physical peering connection can be completed using a variety of connection technologies at the discretion of the State in negotiation with its peering partner.

5. Responsibilities

5.1 Agency—Adhere to requirements established by IOT

5.2 Indiana Office of Technology—IOT will establish guidelines, provide for necessary infrastructure, hardware and software and provide support for direct peering connections.

6. Definitions/References

Statutory Authority:  IC 4-13.1