KPBSD seeks proposals for basic internet access (including bundled transport) with no value-add services. This circuit provides internet connectivity. Responses to this section (Part 2) will be evaluated as described in Section R, subparts 3a-3g in the RFP Instructions to Bidders. KPBSD maintains our own IP address space (Autonomous System Number and /22 CIDR block) registered through ARIN. Provider must be able to accept BGP advertisement of this ASN/CIDR block from our equipment. We presently advertise the entire /22 in one advertisement, but reserve the right to carve that space into multiple advertisements as necessary (for instance, to accommodate an alternate regional ISP connection). We expect that service (e.g. the demarcation handoff) is provided using public, non-KPBSD, IPv4 space. In other words, we require the provider-facing interface(s) on our edge equipment be addressed in your IPv4 space to allow for the potential for multi-homed configurations. Although we are not currently multi-homed, we require flexibility to seamlessly migrate providers if changing from one internet service provider to another. Presently, this handoff to us is accomplished via a /30 public IPv4 netblock. KPBSD desires a defined level of support and service that is exclusively directed to the corporate/mission critical user. Furthermore, we require full measurement of service – no oversubscribing bandwidth. Services proposed must include a Service Level Agreement (SLA). SLA should outline items such as network availability/uptime metric, trouble reporting, response time, escalation and resolution procedures, as well as include remedies available to customer if service performance falls below established SLA benchmarks...
