- TESTING REQUIREMENTS.pdf

TESTING REQUIREMENT

The vendor will perform a 72 hour test prior to transferring service to U.S. Control. Vendor will notify DITCO and the points of contract at each terminating location at least 10 days in advance of the scheduled test date and allow the site the witness testing. Vendor must coordinate site visits with site POCs a minimum of 72hrs before requiring access to facilities at either user location. The test will be end-to-end/head-to-head using separate calibrated test equipment at each location. Acceptance testing utilizing hardware or software loops is not acceptable.

Test will be conducted from each contractual demarcation point. The U.S. controlled termination panel (located within the U.S. Government commercial demarcation shelter) will be the contractual demarcation point at each site. Test results shall not be reset due to slips, sync losses, or anomalous performance conditions during the formal testing period. Testing will be performed in accordance with Standard RFC 2544 and other standards called out in the document. The testing arrangement shall collect capture all testing performance information for the full 72hrs duration of the test. Vendor will provide the following date in printed hard copy and verifiable digital media format such as Adobe. (.pdf) file format. Vendor will performance acceptance testing in accordance with RFC 2544. Tests covered in sections 9.1, 10, 11.1, 14, 20, 21, 26.1, 26.2, and 26.3 of RFC 2544 must be performed and results reported in the format specified by the RFC. Specifically, frame sizes of 64, 128, 256, 512, 1024, 1280, and 1518 bytes must be used. The test must verify length of received frames, indicated number of frames dropped, number of frames received out of order and duplicate frames.

Tests must be bi-directional using the same data rate in each direction. Burst tests must be run to determine minimum interval between frames that can be processed without frame loss. A throughput test is required indicating the fastest rate at which test frames can be transmitted without frame loss.

A separate throughput test must be run with frames addressed to the hardware broadcast address constituting at least 1% of the tet stream and be evenly distributed throughout the test. A latency test must be run for a period of no less than 120 seconds, and repeated no less than 20 times. The test stream for the latency test should be run at the throughput rate for corresponding frame sizes from the throughput test. End to end latency will be calculated as the average over the 20 test runs.

Frame OSS rate tests should be run at the frame rate corresponding to the maximum frame rate, and reduced by 10% intervals until there are at least two consecutive runs in which no frames are lost.

Throughput Test Result: passing rate 100% for all frame bytes sizes exercised.

Frame Loss Rate (%) Results: Frame loss rate less than 0.01% for all frame bytes sizes exercised.

Latency, Measured Round-Trip, will be according to the following guidelines:

Within country, less than 25MS;

Within the Middle East, less than 75MS;

Outside the Middle East, less than 150MS.

The vendor must provide the Government with a copy of the test criteria and results and shall allow local communication (circuit actions/designated rep) to witness testing. Test result will be maintained in the circuit history folder at serving tech controls.

Service Level requirements (SLR) requirements are as follows (calculated monthly):

One way latency less than 10MS.

Packet loss less than 1%.

Jitter less than 2MS.

Uptime greater than 99.95%.

Availability of the end-to-end provided service shall be 99.95% or greater.

The Government reserves the capability to accept 24hr live traffic test against SLRS in lieu of above test to maintain continuity of service or fulfill mission need. The Government will provide written instructions when testing criteria is revised.