Networx Unit Pricer

Technical Summary

A content delivery network is a system of computers containing copies of data placed at various points in a network so as to maximize bandwidth for access to the data from clients throughout the network. The Networx contractor provides CDNS which efficiently and rapidly delivers an Agency's content to Web browsers worldwide by reducing the infrastructure required to provide a domestic or global Web presence. CDNS providers guarantee that Agency content and applications will be available to constituents at all times, even in the event of periods of unexpected high usage, network outages, security incidents, and large-scale natural disasters.

The CDNS provider will incorporate equipment and algorithms to cache content on geographically dispersed servers on the Internet. When a request is made from a particular location for specific content, the server that can most rapidly and efficiently provide the content is dynamically identified.

CDNS consists of a collection of surrogate servers that attempt to offload work from origin servers (where content originates) by delivering content on their behalf. The servers belonging to a CDNS may be located at the same site as the origin server, or at different locations around the network, with some or all of the origin server's content cached or replicated amongst the CDNS servers. For each request, the CDNS attempts to locate a CDNS server close to the client Agency to serve the request, where the notion of "close" could include geographical, topological, or latency considerations.

The picture below shows a typical CDNS server site connected to the Internet.

Typical CDNS Server Site

CDNS addresses the following technical and operational issues:

• Latency - the delay in delivering Web content to the end-user.
• Scalability - Web services automatically scale-up while the end-user requests increase.
• Reliability - content is always available and its integrity is assured (i.e. not been altered by third parties including "hackers").
• Flash crowd control - i.e., effectively meeting demand during periods of unexpected high usage.

CDNS is an application-layer service and therefore requires a connectionless data service, such as the Networx Internet Protocol Service (IPS), for the data transfer from the origin server to the CDNS servers.

CDNS supports the full range of technical capabilities that are available in commercial offerings. It is similar to Content Delivery Network Service on the FTS2001 contracts. These capabilities include:

Content Distribution

• Static Content Download Service
  1. This capability provides fast, secure, and reliable download of content including text, video, music, etc. Such content will likely be stored on CDNS servers deployed globally at the edge of the Internet for faster access.
• Real-time Streaming (Webcasting).
  1. The CDNS provider will deliver streams in real-time. Real-time streaming content will include (but not be limited to) RealNetworks Real Media, Microsoft Windows Media, and Apple QuickTime.
• On-demand Streaming
  1. The CDNS provider will host (i.e., provide storage) and deliver streams on demand when requested by end-users. On-demand streaming content will include (but not be limited to) RealNetworks Real Media, Microsoft Windows Media, and Apple QuickTime.

Site Monitoring/ Server Performance Measurements

CDNS will provide a continuous monitoring to ensure performance and quality of service. Measurements will include:

• Availability.
• Latency.
• File Transfer Protocol (FTP) Load.
• Central Processing Unit (CPU) Load.
• Memory Usage.
• Secure Sockets Layer (SSL) Service Load.
• HyperText Transfer Protocol (HTTP) Port Service Load.
• HTTP Connections Queue Statistics.

The contractor will provide statistics via a performance dashboard - a secure, Web-based portal accessible by Agency clients on a 24x7 basis. The performance dashboard will be consistent with commercial best practices.

These and other service capabilities are detailed in Section C.2.4.6.1.4 Technical Capabilities of the Networx contracts.

CDNS also offers features that complement the basic service. These features are described in Section C.2.4.6.2 Features of the Networx contracts.

• Failover Service.
• Redirection and Distribution Service (Global Load Balancing - Optional to Offer).

Each Networx contractor may provide variations or alternatives to the offering and pricing for CDNS. The specific details can be found within each contractor's Networx contract and pricing notes for CDNS.

For more information on the general CDNS specifications and requirements, please refer to Section C.2.4.6 of the Networx contract for technical specifications and Section B.2.4.6 for pricing.

CDNS Price Basics

CDNS efficiently and rapidly delivers Agency's content to Web browsers worldwide. CDNS basic service consists of two main service types:

• Domestic CDNS where CDNS servers are located only in domestic regions.
• Global CDNS where CDNS servers located in either domestic or non-domestic regions.

CDNS is ordered by specifying a monthly bandwidth commitment level and storage commitment level.

• Committed Bandwidth: Users specify a monthly bandwidth commitment level. Contractor unit prices per Mbps vary by bandwidth commitment level. In general, the larger the bandwidth commitment level, the lower the unit price per Mbps. The MRC is calculated by multiplying the bandwidth commitment level by the unit price per Mbps. This calculation is done automatically in the unit pricer. This MRC is the minimum level charged.
• Bandwidth Overage: If the actual bandwidth used exceeds the bandwidth commitment level, then a separate overage MRC may be applied. The actual bandwidth used is measured at the 95th percentile per month and rounded up to the next highest Mbps bandwidth. The overage MRC applies only to the excess bandwidth (defined as the actual bandwidth used minus the bandwidth commitment level). The overage MRC is calculated by multiplying the excess bandwidth by the unit price per Mbps corresponding to the original committed bandwidth level.
• Committed Storage: Users specify a monthly storage commitment level. Contractor unit prices per GB vary by storage commitment level. In general, the higher the storage commitment level, the lower the unit price per GB. The MRC is calculated by multiplying the storage commitment level by the unit price per GB. This calculation is done automatically in the unit pricer. This MRC is the minimum level charged.
• Storage Overage: If the actual storage used exceeds the storage commitment level, then a separate overage MRC may be applied. The overage MRC applies only to the excess storage (defined as the actual storage used minus the storage commitment level). The overage MRC is calculated by multiplying the excess storage by the unit price per GB corresponding to the original committed storage level.

The CDNS NRC CLINs apply only to the initial service order. Therefore, when only upgrading or changing committed bandwidth levels, the NRC does not apply. Charges for underlying transport services from the origin server to CDNS servers are in addition to the CDNS charges. CDNS is similar to Content Delivery Network Service on the FTS2001 contracts.

Price components required for Domestic and Global CDNS:

• Underlying transport services, such as IPS, to provide connectivity
• Basic service (NRC per service)
• Committed Bandwidth (MRC per Mbps)
• Bandwidth Overage (Overage charges (MRC per Mbps) are incurred when the actual bandwidth used exceeds the monthly committed level)
• Committed Storage (MRC per GB)
• Storage Overage (Overage charges (MRC per GB) are incurred when the actual storage used exceeds the monthly committed level)
• Features ordered as needed by the Agency:
• Failover Service
• Service Enabling Devices (SEDs) may be required to implement CDNS. [Please note that SEDs under Networx replace the FTS2001 User-to-Network Interfaces and Access Adaptation Functions (UNIs/AAFs). SEDs may differ between Networx providers. The pricing structure for SEDs provides for either a one-time payment or monthly term payments for purchase, plus a NRC for installation and a MRC for maintenance.]