Joint Interoperability Test Command (JTE) 13 Aug 12

Size: px
Start display at page:

Download "Joint Interoperability Test Command (JTE) 13 Aug 12"

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 13 Aug 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability Test Certification of the Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Passive Optical Network (PON) with Software Release FP25.7 References: (a) Department of Defense Directive , Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS), 5 May 2004 (b) Department of Defense Instruction , DoD Unified Capabilities (UC), 9 December 2010 (c) through (e), see Enclosure 1 1. References (a) and (b) establish the Joint Interoperability Test Command (JITC) as the responsible organization for interoperability test certification. 2. The Tellabs Gigabit Passive Optical Network (GPON) solution consists of a MSAP OLT and an ONT. The Tellabs 1134 and 1150 MSAP OLTs, combined with an OLT (Tellabs 704 Gigabit (G), 709 Gigabit and Power over Ethernet (GP), 714G, 728GP, 729, and 729GP) with Software Release FP25.7, are hereinafter referred to as the System Under Test (SUT). The SUT meets all its critical interoperability requirements, and JITC certifies the SUT for joint use in the Defense Information System Network (DISN) as a PON. The JITC evaluated and certified the SUT for PON interfaces detailed in Table 1. The operational status of the SUT will be verified during deployment. Any new discrepancies that are discovered in the operational environment will be evaluated for impact and adjudicated to the satisfaction of the Defense Information Systems Agency (DISA) in a vendor Plan of Action and Milestones to address the concern(s) within 120 days of identification. JITC conducted testing using PON requirements within the Unified Capabilities Requirements (UCR) 2008, Change 3, Reference (c). JITC tested the SUT using PON test procedures, Reference (d). JITC does not certify any other configurations, features, or functions, except those cited within this memorandum. This certification expires upon changes that affect interoperability, but no later than 3 years from the date of this memorandum. 3. This finding is based on interoperability testing conducted by JITC, review of the Vendor s Letters of Compliance, and Information Assurance (IA) Certification Authority (CA) approval of the IA configuration. JITC conducted Interoperability testing at its facility in Indian Head Maryland, from 21 February through 30 March JITC published the IA findings in a 6

2 JITC Memo, JTE, Special Interoperability Test Certification of the Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Passive Optical Network (PON) with Software Release FP25.7 separate report, Reference (e). The DISA IA CA reviewed the JITC published IA Assessment Report for the SUT and provided a positive recommendation on the IA configuration on 5 June The acquiring agency or site will be responsible for the Department of Defense IA Certification and Accreditation Process (DIACAP) accreditation. Enclosure 2 documents the test results and describes the tested network and system configurations. Enclosure 3 lists the PON Capability Requirements (CR) and Functional Requirements (FR). 4. Section 5.3 of the UCR establishes the interfaces and threshold CRs/FRs used to evaluate the interoperability of the SUT as a GPON. Tables 1 and 2 list the GPON, sponsor-requested interfaces, CRs, FRs, and component status of the SUT. Interface Critical Table 1. SUT Interface Interoperability Status Reference (UCR 2008, Change 3) CR/FR Requirements Tellabs 1134 MSAP OLT Tellabs 1150 MSAP OLT Specified Tellabs 700 Series ONTs (See note 1.) Remarks NNI-NNI 100 Mbps No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, NA NA NA See note 2. 22, 23, 24, 25, 26, 27 GbE No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 19, Certified Certified NA See note 2. 20, 22, 23, 24, 25, 26, GbE No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 19, NA Certified NA See note 2. 20, 22, 23, 24, 25, 26, 27 PON GPON Yes , 17, 18 Certified Certified Certified NM 10Base-X Yes , 6, 23, 24, 26, 27 Certified Certified 100Base-X Yes , 6, 23, 24, 26, 27 Certified Certified NA NA See note 3. See note 3. UNI 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 10 Mbps No , 13, 14, 15, 16, 19, 20, NA NA Certified See note 4. 21, 22, 24, 25, 26, Mbps No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, NA NA Certified See note 4. 21, 22, 24, 25, 26, 27 GbE No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, NA NA Certified See note 4. 21, 22, 24, 25, 26, 27 OTHER VoIP No NA 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, NA NA Not Tested See note 5. 21, 22, 24, 25, 26, 27 POTS No NA 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 NA NA Not Tested See note 6. 2

3 JITC Memo, JTE, Special Interoperability Test Certification of the Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Passive Optical Network (PON) with Software Release FP25.7 NOTES: 1. Specified Tellabs 700 Series ONTs consisted of Tellabs 704G, 709GP, 714G, 728GP, 729, and 729GP. 2. The OLT NNI-NNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). 3. The NM interfaces were available only on 1134 and 1150 OLTs and all the configuration, alarm, other event management for 700 series ONTs were performed via OLTs. 4. The ONT UNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). 5. The Tellabs 700 Series ONTs provide a VoIP interface that converts POTS analog voice to SIP. This interface was not tested and is not certified for use. 6. The Tellabs 700 Series ONTs provides a 2-wire analog POTS voice interface. The ONT POTS Voice interface ports are not tested and not certified. LEGEND: 10Base-X 10 Mbps Ethernet generic designation 100Base-X 100 Mbps Ethernet generic designation CR Capability Requirement FR Functional Requirement G Gigabit GbE Gigabits Ethernet GP Gigabit Power Over Ethernet GPON Gigabit Passive Optical Network IEEE Institute of Electrical and Electronic Engineers Mbps Megabits per second MSAP Multi-Services Access Platform NA Not Applicable NM NNI OLT ONT PON POTS SIP SUT UCR UNI VoIP Network Management Network-to-Network Interface Optical Line Terminal Optical Network Terminal Passive Optical Network Plain Old Telephone Service Session Initiation Protocol System Under Test Unified Capabilities Requirements User Network Interface Voice over Internet Protocol CR/FR ID Capability/Function Table 2. SUT CRs and FRs Status Applicability (See note 1.) Reference (UCR 2008 Change 3) Status Remarks GPON Requirements 1 Interfaces Required Met See notes 2 and 3. 2 Class of Service Markings Required Met See notes 2 and 3. 3 Virtual LAN Capabilities Required Met See notes 2 and 3. 4 Protocols Conditional Met See notes 2 and 3. 5 Quality of Service Features Required Met See notes 2 and 3. 6 Network Monitoring Required Met See notes 2 and 3. 7 Voice Services Required Met See note 2. 8 Video Services Required Met See note 2. 9 Data Services Required Met See note Information Assurance Requirements Required Met See note PON Network Management Requirements Required Met See notes 2 and Configuration Control Required Met See notes 2 and Operational Changes Required Met See notes 2 and Performance Monitoring Required Met See notes 2 and Alarms Required Met See notes 2 and Reporting Required Met See notes 2 and Fiber Media Required Met See notes 2 and RF-over-Glass Conditional Met See notes 2 and Traffic Engineering Required Met See notes 2 and VLAN Design and Configuration Required Met See notes 2 and Power Backup Required Met See notes 2 and Availability Conditional Met See notes 2 and Redundancy Required Met See notes 2 and 3. 3

4 JITC Memo, JTE, Special Interoperability Test Certification of the Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Passive Optical Network (PON) with Software Release FP25.7 CR/FR ID Table 2. SUT CRs and FRs Status (continued) Capability/Function Applicability (See note 1.) Reference (UCR 2008 Change 3) Status Remarks GPON Requirements 24 Survivability Required Met See notes 2 and Summary of LAN Requirements by Subscriber Mission Required Met See notes 2 and IPv6 Required Met See notes 2, 3, and Network Management Required Met See note 5. NOTES: 1. Annotation of required refers to high-level requirement category. Applicability of each sub-requirement is provided in Enclosure Any Tellabs 704G, 709GP, 714G, 728GP, 729, and 729GP ONT combined with a Tellabs 1134 or 1150 OLT creates a GPON solution that meets the CRs and FRs set forth by UCR 2008, Change The SUT met the requirement via interoperability testing and review of vendor LoC. 4. This requirement was met via dual stack IPv4/IPv6 testing and review of vendor LoC. 5. The NM interface was available only on 1134 and 1150 OLTs, and all the configuration, alarm, other event management for 700 series ONTs were performed via OLT. LEGEND: CR Capabilities Requirement FR Functional Requirement G Gigabit GP Gigabit Power Over Ethernet GPON Gigabit Passive Optical Network ID Identification IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 LAN Local Area Network LoC NM OLT ONT PON RF SUT UCR VLAN Letter of Compliance Network Management Optical Line Terminal Optical Network Terminal Passive Optical Network Radio Frequency System Under Test Unified Capabilities Requirements Virtual Local Area Network 5. In accordance with the Program Manager s request, JITC did not develop a detailed test report. JITC distributes interoperability information via the JITC Electronic Report Distribution system, which uses Unclassified-But-Sensitive Internet Protocol Router Network (NIPRNet) . More comprehensive interoperability status information is available via the JITC System Tracking Program, which.mil/.gov users can access on the NIPRNet at Test reports, lessons learned, and related testing documents and references are on the JITC Joint Interoperability Tool at (NIPRNet). Information related to DISN testing is on the Telecommunications Switched Services Interoperability website at All associated data is available on the DISA Unified Capabilities Certification Office (UCCO) website located at 4

5 JITC Memo, JTE, Special Interoperability Test Certification of the Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Passive Optical Network (PON) with Software Release FP JITC testing point of contact is Mr. Son Pham, commercial (301) His address is mailing address: 3341 Strauss Avenue, Suite 236, Indian Head, Maryland The UCCO Tracking Number is FOR THE COMMANDER: 3 Enclosures a/s for RICHARD A. MEADOR Chief Battlespace Communications Portfolio Distribution (electronic mail): Joint Staff J-6 Joint Interoperability Test Command, Liaison, TE3/JT1 Office of Chief of Naval Operations, CNO N6F2 Headquarters U.S. Air Force, Office of Warfighting Integration & CIO, AF/XCIN (A6N) Department of the Army, Office of the Secretary of the Army, DA-OSA CIO/G-6 ASA (ALT), SAIS-IOQ U.S. Marine Corps MARCORSYSCOM, SIAT, MJI Division I DOT&E, Net-Centric Systems, and Naval Warfare U.S. Coast Guard, CG-64 Defense Intelligence Agency National Security Agency, DT Defense Information Systems Agency, TEMC Office of Assistant Secretary of Defense (NII)/DoD CIO U.S. Joint Forces Command, Net-Centric Integration, Communication, and Capabilities Division, J68 HQUSAISEC, AMSEL-IE-IS 5

6 (This page left intentionally blank.) 6

7 ADDITIONAL REFERENCES (c) Office of the Assistant Secretary of Defense, Department of Defense Unified Capabilities Requirements 2008, Change 3, September 2011 (d) Joint Interoperability Test Command, Passive Optical Network Test Procedures, 20 February 2012 (e) Joint Interoperability Test Command, Information Assurance (IA) Assessment of Tellabs 1150 Multiservice Access Platform and Tellabs 1134 Multiservice Access Platform Gigabit Passive Optical Network (GPON), with Software Release FP25.7 (TN ), 23 March 2012 Enclosure 1

8 (This page intentionally left blank.)

9 CERTIFICATION TESTING SUMMARY 1. SYSTEM TITLE. The Tellabs 1134 and 1150 Multiservice Access Platform (MSAP) Optical Line Terminals (OLT) with Specified Tellabs 700 Series Optical Network Terminals (ONT) Gigabit Passive Optical Network (GPON) with Software Release FP25.7. The system is hereinafter referred to as the System Under Test (SUT). 2. SPONSOR. Mr. Jordan Silk, Program Manager, HQUSAISEC, AMSEL-IE-IS, Building 53302, Fort Huachuca, AZ 85613, 3. SYSTEM POC. Mr. Russell Kulpins, Staff Product Manager, Tellabs, 1415 West Diehl Road, Naperville, IL TESTER. Joint Interoperability Test Command (JITC), Indian Head, Maryland. 5. SYSTEM DESCRIPTION. There are three main components in a GPON, other than the fiber itself. The GPON OLT is the network concentrator, the splitter (or splitters) allows a single fiber to be shared among a number of subscribers, and the ONT serves a local site. The Tellabs 1134 MSAP offers a medium-density, full-service option ideal for smaller "deep-fiber" (i.e., fiber-to-the desktop) applications. Tellabs designed the system to meet growing demands of high-bandwidth services, including voice, video, and data. The Tellabs 1150 MSAP is a native end-to-end Internet Protocol (IP)/Ethernet delivery platform that offers the packet-based, high-bandwidth technology required for current telecommunications services. The Tellabs 1150 MSAP is a high-density access platform focused on optimized, scalable, deep-fiber service delivery of voice, video, and data. The Tellabs 1134 and 1150 perform the function of the GPON OLT. Tellabs designed the 700 series ONT to deliver narrowband and broadband subscriber services. The Tellabs 704 Gigabit (G), 709 Gigabit and Power Over Ethernet (GP), 714G, 728GP, 729, and 729GP ONTs are GPON access devices that provide service termination for the subscriber ports of the 1134/1150 MSAP platforms. The ONTs were tested peripherals to the 1134/1150 MSAP platforms. The Tellabs-1134/1150 MSAPs and 704G, 709GP, 714G, 728GP, 729, and 729GP ONTs are components of the GPON system International Telecommunication Union-Telecommunication (ITU-T) Standardization Sector G.984 standard. The Oracle Database User Licensed Standard Edition and Tellabs Panorama are used for provisioning the SUT; and they were not part of the SUT. 6. OPERATIONAL ARCHITECTURE. Under the direction of the Unified Capabilities (UC) Certification Office, the SUT is being tested and evaluated as a GPON. Figure 2-1 shows the role of the SUT in a Defense Information System Network (DISN) architecture. Enclosure 2

10 DISN Backbone OTS-P (OLA, Transponder, Muxponder, ROADM) OTS-P (OLA, Transponder, Muxponder, ROADM) DISN Router P OTS (OLA, Transponder, Muxponder, ROADM) TSF-P (ODXC) F-NE(s) AGF-P (MSPP) F-NE(s) BITS AGF-P (MSPP) HAIPE/ LEF AGF-P (MSPP) HAIPE/ LEF DISN Router S-PE DISN Router U-PE DISN Router S-AR DISN Router U-AR DISN Router S-AR DISN Router U-AR AAF-P (TDM MUX) F-NE(s) HAIPE/ LEF DISN Router S-CE DISN Router U-CE DISN Router S-CE DISN Router U-CE F-NE(s) DISN Router S-CE DISN Router U-CE GPON GPON GPON C/P/S Edge C/P/S C/P/S Edge C/P/S C/P/S Edge C/P/S LEGEND: AAF-P Access Aggregation Function Product AGF-P Access Grooming Function Product BITS Building Integrated Timing Supply C/P/S Camp, Post, or Station DISN Defense Information System Network F-NE Fixed Network Element GPON Gigabit Passive Optical Network HAIPE High Assurance Internet Protocol Encryptor LEF Link Encryption Family MSPP Multi-Service Provisioning Platform MUX Multiplexer ODXC Optical Digital Cross Connect OLA Optical Line Amplifier OTS-P Optical Transport System Product P Provider Router ROADM Reconfigurable Optical Add and Drop Multiplexer S-AR Secret Aggregation Router S-CE Secret Customer Edge Router S-PE Secret Provider Edge Router TDM Time Division Multiplexing TSF-P Transport Switch Function Product U-AR Unclassified Aggregation Router U-CE Unclassified Customer Edge Router U-PE Unclassified Provider Edge Router Figure 2-1. DISN Architecture 2-2

11 7. INTEROPERABILITY REQUIREMENTS. The interface, Capability Requirements (CR), Functional Requirements (FR), Information Assurance (IA), and other requirements for GPON products are established by the Department of Defense (DoD) Unified Capabilities Requirements (UCR) 2008, Change 3, Section Interfaces. The GPON products use their interfaces to connect to a Local Area Network (LAN) or DISN Wide Area Network infrastructure. The threshold requirements for interfaces specific to the GPON products are listed in Table 2-1. Table 2-1. GPON Interface Requirements Interface Critical Reference (UCR 2008 Change 3) 100 Mbps No GbE No GbE No CR/FR Requirements Criteria NNI-NNI 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 22, 23, 24, 25, 26, 27 Meet minimum 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, CR/FRs and 16, 17, 19, 20, 22, 23, 24, 25, 26, 27 interface standards 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 19, 20, 22, 23, 24, 25, 26, 27 PON GPON Yes , 17, 18 10Base-X Yes , 6, 23, 24, 26, Base-X Yes , 6, 23, 24, 26, Mbps No Mbps No GbE No VoIP No NA POTS No NA NM Meet minimum CR/FRs and interface standards Meet minimum CR/FRs and interface standards UNI 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 Meet minimum 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, CR/FRs and 16, 19, 20, 21, 22, 24, 25, 26, 27 interface standards 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 OTHER 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 Meet minimum CR/FRs and interface standards Meet minimum CR/FRs and interface standards Remarks See note 1. See note

12 Table 2-1. GPON Interface Requirements (continued) NOTES: 1. The OLT NNI-NNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). 2. The ONT UNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). LEGEND: 10Base-X 10 Mbps Ethernet generic designation 100Base-X 100 Mbps Ethernet generic designation CR Capability Requirement FR Functional Requirement GbE Gigabits Ethernet GPON Gigabit Passive Optical Network IEEE Institute of Electrical and Electronic Engineers Mbps Megabits per second NM NNI OLT ONT PON UCR UNI Network Management Network-to-Network Interface Optical line Terminal Optical Network Terminal Passive Optical Network Unified Capabilities Requirements User Network Interface 7.2 CRs and FRs. The GPON products have required and conditional features and capabilities that are established by UCR 2008, Change 3, Section The SUT does not need to provide non-critical (conditional) features and capabilities. If they are present, however, they must function according to the specified requirements. Table 2-2 lists the features and capabilities and their associated requirements for the SUT products. Table 3-1 of Enclosure 3 provides detailed CR/FR requirements. CR/FR ID Capability/Function Table 2-2. SUT CRs and FRs Applicability (See note.) Reference (UCR 2008 Change 3) Criteria GPON Requirements 1 Interfaces Required Meet UCR Requirements 2 Class of Service Markings Required Meet UCR Requirements 3 Virtual LAN Capabilities Required Meet UCR Requirements 4 Protocols Conditional Meet UCR Requirements 5 Quality of Service Features Required Meet UCR Requirements 6 Network Monitoring Required Meet UCR Requirements 7 Voice Services Required Meet UCR Requirements 8 Video Services Required Meet UCR Requirements 9 Data Services Required Meet UCR Requirements 10 Information Assurance Requirements Required Meet UCR Requirements 11 PON Network Management Requirements Required Meet UCR Requirements 12 Configuration Control Required Meet UCR Requirements 13 Operational Changes Required Meet UCR Requirements 14 Performance Monitoring Required Meet UCR Requirements 15 Alarms Required Meet UCR Requirements 16 Reporting Required Meet UCR Requirements 17 Fiber Media Required Meet UCR Requirements 18 RF-over-Glass Conditional Meet UCR Requirements 19 Traffic Engineering Required Meet UCR Requirements 20 VLAN Design and Configuration Required Meet UCR Requirements 21 Power Backup Required Meet UCR Requirements 22 Availability Conditional Meet UCR Requirements 23 Redundancy Required Meet UCR Requirements 24 Survivability Required Meet UCR Requirements 25 Summary of LAN Requirements by Subscriber Mission Required Meet UCR Requirements 2-4

13 CR/FR ID Table 2-2. SUT CRs and FRs (continued) Capability/Function Applicability (See note.) Reference (UCR 2008 Change 3) Criteria 26 IPv6 Required Meet UCR Requirements 27 Network Management Required Meet UCR Requirements NOTE: Annotation of required refers to high-level requirement category. Applicability of each sub-requirement is provided in Enclosure 3. LEGEND: CR Capabilities Requirement FR Functional Requirement ID Identification IPv6 Internet Protocol version 6 GPON Gigabit Passive Optical Network LAN Local Area Network PON RF SUT UCR VLAN Passive Optical Network Radio Frequency System Under Test Unified Capabilities Requirements Virtual Local Area Network 7.3 Other. None. 8. TEST NETWORK DESCRIPTION. JITC tested the SUT at its facility in Indian Head, Maryland. Figure 2-2 shows the SUT s Test Configuration. 2-5

14 704G ONT 10/100/1000 Ethernet 709GP ONT 714G ONT GPON CONNECTION TMDE 10/100/1000 Ethernet 10/100/1000 Ethernet 709GP ONT 729 ONT 729GP 704G ONT 709GP ONT 714G ONT 709GP ONT GPON CONNECTION GPON CONNECTION Optical Splitter Combiner Optical Splitter Combiner GPON CONNECTION GPON CONNECTION 1150 OLT 1134 OLT 10 GbE LAG 1 GbE LAG Golden Master ASLAN Distribution Router 1 GbE 10/100/1000 Ethernet 729 ONT 729GP GPON CONNECTION LEGEND: G GbE GP GPON LAG Gigabit Gigabit Ethernet Gigabit and Power Over Ethernet Gigabit Passive Optical Network Link Aggregation Group OLT ONT SUT TMDE Optical Line Terminal Optical Network Terminal System Under Test Test, Measurement, and Diagnostic Equipment Figure 2-2. SUT s Test Configuration 2-6

15 9. SYSTEM CONFIGURATION. Table 2-3 lists the Hardware/Software Tested SUT Equipment shown in Figure 2-2, Table 2-4 lists the Non-SUT Equipment, and Table 2-5 lists the test equipment used to generate voice, video, and IP data traffic. Table 2-3. Hardware/Software Tested SUT Equipment Platform Software Release UC Product Type 704G ONT FP25.7 PON 709GP ONT FP25.7 PON 714G ONT FP25.7 PON 728GP ONT FP25.7 PON 729 ONT FP25.7 PON 729GP ONT FP25.7 PON Tellabs 1134 MSAP OLT FP25.7 PON Tellabs 1150 MSAP OLT FP25.7 PON Oracle Database 5 Named User License SE Version 10 - Oracle Standard Edition NM Tellabs Panorama Release NM SUT-Equipment List Quantity Description Part Number 1 MDS5 Chassis, 16 I/O Slot ESU2- ESU- 2 x 10 GbE and 4 x 1 Gbps; 2 for redundancy ESU11 - MSAP - Ethernet Switching Unit - 4 x 1 Gbps QOIU7 QUAD GPON Card (4 SFPs included) XFP, TDM, 10 Gbps, 1310 nm, industrial temp 5/3.3/1.8V - 10 km Chassis Fan Tray Assembly ESU30 ESU GbE SFP Wideband 850 nm (1000 base SX) 550 m ONT701, 1D, GPON TL - Includes encl and power supply. (Note this unit doesn't support a battery) 3 ONT709, 4 GbE Indoor ONT729, MDU NID 24P, 24FE ONT704G, 2P (ANSI), 4 GbE - Indoor desktop unit (A power cord) 81.16G-704G00PA-R6 2 ONT709GP, 4 GbE, PoE, No POTS, No-Plug 81.16G-709GP00X-R6 2 ONT714, 4 GbE, 2P, No-Plug TL NID 81.16G-714G00PX-R6 2 ONT728GP 24 GbE with PoE; MDU; 1 RU 19-inch Rack. 100 to 81.16G-728GP00B-R6 240V AC powered (B power cord) 2 ONT729GP - 24P, 24 GbE with PoE; MDU; 1 RU 19-inch Rack G-729GP0PB-R6 to 240V AC powered (B power cord) 1 Sun T2000 Sever MDS5 Chassis, 16 I/O Slot ESU2- ESU - 2 x 10 GbE and 4 x 1 Gbps; 2 for redundancy ESU11 - MSAP - Ethernet Switching Unit - 4 x 1 Gbps QOIU7 QUAD GPON Card (4 SFPs included) XFP, TDM, 10 Gbps, 1310 nm, industrial temp 5/3.3/1.8V - 10 Km

16 Table 2-3. Hardware/Software Tested SUT Equipment (continued) LEGEND: AC Alternating Current ANSI American National Standards Institute ESU Ethernet Switch Unit FE Fast Ethernet FP Feature Package G Gigabit GbE Gigabit Ethernet Gbps Gigabits per second GP Gigabit Power Over Ethernet GPON Gigabit Passive Optical Network I/O Input/Output km kilometer m meters MDS Multipoint Distribution Service MDU Multiplexer Decoder Unit MSAP Multi-Services Access Platform NID Network Interface Device NM Network Manager nm nanometer OLT ONT P PoE PON POTS QOIU7 QUAD RU SE SFP SUT SX TDM TL UC V XFP Optical Line Terminal Optical Network Terminal Port Power over Ethernet Passive Optical Network Plain Old Telephone Service 4-port GPON module Quadruple Rack Unit Standard Edition Small Form-Factor System Under Test Short Haul Fiber Time Division Multiplexing Transport Layer Unified Capabilities volt X-Form Factor Pluggable Table 2-4. Non-SUT Equipment Component Software Version Function Subcomponent Cisco 6509 Version 12.2 Router 1 GbE, 10 GbE LAG LEGEND: GbE LAG Gigabit Ethernet Ling Aggregation Group SUT System Under Test Table 2-5. Test, Measurement, and Diagnostic Equipment Agilent Ixia Manufacture Type Port Type Optical Tester Router Tester 900 Traffic generator Agilent Rack Mounted Router Tester nm 1310 nm OC-3/OC-12 /POS OC-48 Multilayer 1000Base-X 10 G LM1000STX 10 G LAN/WAN 10/100/1000Base-T 1000Base-X OC-48c POS OC-3/12/POS A Software Version LEGEND: 10/100/1000 Base-T 10/100/1000 Mbps (Baseband Operation, Twisted Pair) Ethernet 1000Base-X 1000 Mbps Ethernet Generic Designation G Gigabit LAN Local Area Network LM Light Manager Mbps nm OC POS STX WAN Megabits per second Nanometer Optical Carrier Packet Over Synchronous Optical Network Ixia Product Name Wide Area Network 2-8

17 10. TEST LIMITATIONS. The JITC Indian Head testers noted the following test limitations during testing of the system: a. There were no real users connected to the GPON-ONTs so JITC test team simulated all the functionality of the real users using test equipments. b. There were no real Local Session Controller and IP-enabled Voice switch connected to the GPON-OLTs so JITC test team simulated all the functionality of the Local Session Controller and the IP-enabled Voice switch using test equipments. c. GPON systems acts as the Access-Layer of the ASLAN and connects directly to the Distribution-Layer of ASLAN and JITC-IHD ATT Lab does not have a fully function ASLAN, so JITC test team simulated the Distribution-Layer of the ASLAN using single Cisco 4507R layer-3 switch. 11. INTEROPERABILITY EVALUATION RESULTS. The SUT meets the critical interoperability requirements for PON, and JITC certifies its joint use within the DISN. Additional discussion regarding specific testing results is contained in subsequent paragraphs Interfaces. The SUT s GPON interface status is provided in Table 2-6. Table 2-6. SUT GPON Interface Requirements Status Interface Critical Reference (UCR 2008, Change 3) CR/FR Requirements Tellabs 1134 MSAP OLT Tellabs 1150 MSAP OLT Specified Tellabs 700 Series ONTs (See note 1.) NNI-NNI 100 Mbps No , 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 22, 23, 24, 25, 26, 27 NA NA NA 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, GbE No , 13, 14, 15, 16, 17, 19, Certified Certified NA 20, 22, 23, 24, 25, 26, 27 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 10 GbE No , 13, 14, 15, 16, 17, 19, NA Certified NA 20, 22, 23, 24, 25, 26, 27 PON GPON Yes , 17, 18 Certified Certified Certified NM 10Base-X Yes , 6, 23, 24, 26, 27 Certified Certified NA 100Base-X Yes , 6, 23, 24, 26, 27 Certified Certified NA 10 Mbps No Mbps No GbE No UNI 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 NA NA Certified NA NA Certified NA NA Certified Remarks See note 2. See note 2. See note 2. See note 3. See note 3. See note 4. See note 4. See note

18 Table 2-6. SUT GPON Interface Requirements Status (continued) Interface Critical Reference (UCR 2008, Change 3) VoIP No NA POTS No NA CR/FR Requirements OTHER 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 19, 20, 21, 22, 24, 25, 26, 27 Tellabs 1134 MSAP OLT Tellabs 1150 MSAP OLT Specified Tellabs 700 Series ONTs (See note 1.) NA NA Not Tested NA NA Not Tested Remarks See note 5. See note 6. NOTES: 1. Specified Tellabs 700 Series ONTs consisted of Tellabs 704G, 709GP, 714G, 728GP, 729, and 729GP. 2. The OLT NNI-NNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). 3. The NM interfaces were available only on 1134 and 1150 OLTs and all the configuration, alarm, other event management for 700 series ONTs were performed via OLTs. 4. The ONT UNI port shall support at least one of the required interface rates (other rates and IEEE standards may be provided as conditional interfaces). 5. The Tellabs 700 Series ONTs provide a VoIP interface that converts POTS analog voice to SIP. This interface was not tested and is not certified for use. 6. The Tellabs 700 Series ONTs provides a 2-wire analog POTS voice interface. The ONT POTS Voice interface ports are not tested and not certified. LEGEND: 10Base-X 10 Mbps Ethernet generic designation 100Base-X 100 Mbps Ethernet generic designation CR Capability Requirement FR Functional Requirement G Gigabit GbE Gigabits Ethernet GP Gigabit Power Over Ethernet GPON Gigabit Passive Optical Network IEEE Institute of Electrical and Electronic Engineers Mbps Megabits per second MSAP NA NM NNI OLT ONT PON SUT UCR UNI Multi-Services Access Platform Not Applicable Network Management Network-to-Network Interface Optical Line Terminal Optical Network Terminal Passive Optical Network System Under Test Unified Capabilities Requirements User Network Interface 11.2 CRs and FRs. Table 2-7 lists the SUT s CR/FR statuses. The detailed CR/FR requirements are provided in Table 3-1 of the System Functional and Capability Requirements (Enclosure 3). CR/FR ID Capability/Function Table 2-7. SUT CRs and FRs Status Applicability (See note 1.) Reference (UCR 2008 Change 3) Status Remarks GPON Requirements 1 Interfaces Required Met See notes 2 and 3. 2 Class of Service Markings Required Met See notes 2 and 3. 3 Virtual LAN Capabilities Required Met See notes 2 and 3. 4 Protocols Conditional Met See notes 2 and 3. 5 Quality of Service Features Required Met See notes 2 and 3. 6 Network Monitoring Required Met See notes 2 and 3. 7 Voice Services Required Met See note 2. 8 Video Services Required Met See note 2. 9 Data Services Required Met See note

19 CR/FR ID Table 2-7. SUT CRs and FRs Status (continued) Capability/Function Applicability (See note 1.) Reference (UCR 2008 Change 3) Status Remarks 10 Information Assurance Requirements Required Met See note PON Network Management Requirements Required Met See notes 2 and Configuration Control Required Met See notes 2 and Operational Changes Required Met See notes 2 and Performance Monitoring Required Met See notes 2 and Alarms Required Met See notes 2 and Reporting Required Met See notes 2 and Fiber Media Required Met See notes 2 and RF-over-Glass Conditional Met See notes 2 and Traffic Engineering Required Met See notes 2 and VLAN Design and Configuration Required Met See notes 2 and Power Backup Required Met See notes 2 and Availability Conditional Met See notes 2 and Redundancy Required Met See notes 2 and Survivability Required Met See notes 2 and Summary of LAN Requirements by Subscriber Mission Required Met See notes 2 and IPv6 Required Met See notes 2, 3, and Network Management Required Met See note 5. NOTES: 1. Annotation of required refers to high-level requirement category. Applicability of each sub-requirement is provided in Enclosure Any Tellabs 704G, 709GP, 714G, 728GP, 729, and 729GP ONT, combined with Tellabs 1134 or 1150 OLT creates a GPON solution that meets the CRs and FRs set forth by UCR 2008, Change This requirement was met via interoperability testing and review of vendor LoC. 4. This requirement was met via dual stack IPv4/IPv6 testing and review of vendor LoC. 5. The NM interface was available only on 1134 and 1150 OLTs, and all the configuration, alarm, other event management for 700 series ONTs were performed via OLT. LEGEND: CR Capabilities Requirement FR Functional Requirement G Gigabit GP Gigabit Power Over Ethernet GPON Gigabit Passive Optical Network ID Identification IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 LAN Local Area Network LoC NM OLT ONT PON RF SUT UCR VLAN Letter of Compliance Network Management Optical Line Terminal Optical Network Terminal Passive Optical Network Radio Frequency System Under Test Unified Capabilities Requirements Virtual Local Area Network a. Interfaces: Overall Interfaces Requirements. In Accordance With (IAW) UCR 2008, Change 3, paragraph , Passive Optical Networks (PON) can be composed of Broadband PON, Ethernet PON, and GPON, and the requirements do not delineate between the different types. The UCR defines four types of interfaces in a typical PON: the Network to Network Interface (NNI); the interface from network to OLT; the interface from OLT to ONT Network Management (NMI) interface; and the User to Network Interface (UNI) interface. (1) NNI-NNI Interface. 2-11

20 (a) The NNI-NNI interface is composed of the uplink between the OLT and the Core network. This interface is composed of Institute of Electrical and Electronics Engineers (IEEE) interfaces and may provide a Fiber channel interface IAW American National Standard Institute (ANSI) International Committee for Information Technology Standards T11.2 and T11.3 (previously known as X3T9.3). At this time, no minimum rate or type of IEEE interface is specified and commercial-off-the-shelf interfaces are accepted. If the Fiber Channel Interface is provided the interface must meet the following requirements: Request For Comment (RFC) 4338 Transmission of IP version (v)6, IPv4, and Address Resolution Protocol; Packets over Fiber channel; and RFC 4044 Fiber Channel Management. The SUT met the requirement via IA testing, Letter of Complaince (LoC), and interoperability testing using test equipment and simulated information exchanges. (b) The OLT NNI-NNI port shall support at least one of the following interface rates (other rates and IEEE standards may be provided as conditional interfaces): 100 Megabits per second (Mbps) IAW IEEE 802.3u, 1 Gigabit per second (Gbps) IAW IEEE 802.3z, and 10 Gbps IAW IEEE 802.3ae. The NNI ports shall provide the following parameters on a per port basis as specified: Auto-negotiation IAW IEEE 802.3, Force mode IAW IEEE 802.3; Flow control IAW IEEE 802.3x, Filtering IAW RFC 1812; Link Aggregation IAW IEEE 802.1AX (formerly 802.3ad); Spanning Tree Protocol IAW IEEE 802.1D; and Multiple Spanning Tree IAW IEEE 802.1s, Rapid Configuration of Spanning Tree IAW IEEE The SUT met the requirement via IA testing, LoC, and interoperability testing using test equipment and simulated information exchanges. (2) OLT to ONT PON Interface. The GPON OLT to ONT interface is defined by the ONT Management Control Interface protocol and was standardized and defined by the ITU-T standard G This interface is composed of the PON port on the OLT and the Fiber port on the ONT. Between these ports are a single strand of Single Mode Fiber and one or more optical splitters. Bi-directional transmission is accomplished by use of separate wavelengths (1310 nanometer (nm) and 1490 nm) for transmission. The number of splitters is driven by local requirements and does not exceed the ITU-T G.984 specification for fiber loss per PON port between the OLT and ONT. There may be 1 to 64 (some vendors support more) ONTs on a single PON port. The number of ONTs is driven by the required bandwidth for each user and IAW the traffic engineering guidelines in paragraph , Traffic Engineering. The SUT met the requirement via IA testing and vendor LoC. (3) Network Monitoring. The GPON products shall support the following network monitoring features: Simple Network Management Protocol (SNMP) IAW RFCs 1157, 3410, 3411, 3412, 3413, and 3414; SNMP Traps IAW RFC 1215, Remote Monitoring IAW RFC 2819; Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework IAW RFC 3584; and The Advanced Encryption 2-12

21 Standard Cipher Algorithm in the SNMP User-based Security Model IAW RFC The SUT met the requirement via IA testing, vendor LoC, and interoperability testing using test equipment and simulated information exchanges. (4) UNI Interface. (a) PON products shall provide at least one of the following interface rates: 10 Mbps IAW IEEE 802.3i, 100 Mbps IAW IEEE 802.3u, 1000 Mbps IAW IEEE 802.3z, and 1000 Mbps IAW IEEE 802.3ab. The PON must also support traffic conditioning, which will ensure that the required bandwidth is available for all network users. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (b) UNI Ports. The UNI ports shall provide the following parameters on a per port basis as specified: Auto-negotiation IAW IEEE 802.3, Force mode IAW IEEE 802.3, Flow control IAW IEEE 802.3x, Filtering IAW RFC 1812, Port-Base Access Control IAW 802.1x, and Link Layer Discover Media Endpoint Discovery IAW ANSI- Telecommunications Industry Association (TIA) The SUT met the requirement via IA testing, vendor LoC, and interoperability testing using test equipment and simulated information exchanges. (c) Link Aggregation. IAW IEEE 802.1AX (formerly 802.3ad). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (d) Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI). The UNI ports may provide the following feature parameter on a per port basis as specified: DTE Power via MDI. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (e) Power-over-Ethernet (PoE) Plus. PoE Plus or DTE Power via MDI for Conditional Interfaces IEEE 802.3af. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. b. Class of Service Markings. The PON network shall comply with access product requirements, paragraph , #1 and #3. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. c. Virtual LAN (VLAN) Capabilities. The NNI and UNI PON ports shall comply with paragraph , VLAN Capabilities. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. d. Protocols. The PON network shall support bridging at Layer-2 of the Open Systems Interconnection model. Bridging will provide for higher survivability and will 2-13

22 reduce traffic congestion on the uplinks to the Distribution or Core Layers of the network. Bridging at Layer-2 will be supported for packets that do not require Layer-3 handling. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. e. Quality of Service Features (QoS). The PON shall comply with the Access product requirements listed in paragraph , QoS Features. PON products targeted for non-assured services are not subject to the Layer-3 queuing requirements in this section and the conditions of fielding will state whether the PON can support Assured Services or not. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. f. Network Monitoring. The PON shall comply with the product requirements listed in paragraph , Network Monitoring. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. g. Voice Services. GPON product shall comply with the following: (1) Latency. The PON shall have the capability to transport voice IP packets, media, and signing with no more than 6 milliseconds (ms) latency end-to-end across the PON SUT as measured under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent IP video, 25 percent preferred data, and 25 percent best effort traffic). The latency shall be achievable over any 5-minute measured period under congested conditions. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (2) Jitter. The PON shall have the capability to transport voice IP packets across the PON SUT with no more than 3 ms of jitter. The jitter shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent IP video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (3) Packet Loss. The PON shall have the capability to transport voice IP packets across the PON SUT with packet loss not to exceed configured traffic engineered (queuing) parameters. Actual measured packet loss across the PON shall not exceed percent within the defined queuing parameters. The packet loss shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. 2-14

23 h. Video Services. GPON product shall comply with the following: (1) Latency. The PON shall have the capability to transport video IP packets with no more than 30 ms latency across the PON SUT. Latency is increased over voice IP packets because of the increased size of the packets (230 bytes for voice packets and up to 1518 bytes for video). The latency shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering (25 percent voice/ signaling, 25 percent video, 25 percent-preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (2) Jitter. The LAN shall have the capability to transport video IP packets across the PON SUT with no more than 30 ms of jitter. The jitter shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering (25 percent voice/signaling, 25 percent video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (3) Packet Loss. The PON shall have the capability to transport video IP packets across the PON SUT with packet loss not to exceed configured traffic engineered (queuing) parameters. Actual measured packet loss across the PON shall not exceed 0.15 percent within the defined queuing parameters. The packet loss shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. i. Data Services. GPON product shall comply with the following: (1) Latency. The PON shall have the capability to transport prioritized data IP packets with no more than 45 ms latency across the PON SUT. Latency is increased over voice IP packets because of the increased size of the packets (230 bytes for voice packets and up to 1518 bytes for data). The latency shall be achievable over any 5-minute measured period under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. 2-15

24 (2) Jitter. There are no jitter requirements for preferred data IP packets. JITC tested this IAW the video service jitter requirement, and the SUT met the requirement via interoperability testing using test equipment and simulated information exchanges. (3) Packet Loss. The PON shall have the capability to transport prioritized data IP packets across the PON SUT with packet loss not to exceed configured traffic engineered (queuing) parameters. Actual measured packet loss across the LAN shall not exceed 0.15 percent within the defined queuing parameters. The packet loss shall be achievable over any 5-minute period measured under congested conditions. Congested conditions are defined as 100 percent of link capacities (as defined by baseline traffic engineering 25 percent voice/signaling, 25 percent video, 25 percent preferred data, and 25 percent best effort traffic). The SUT met the requirement via vendor LoC and interoperability testing using test equipments and simulated information exchanges. j. Information Assurance Requirements. All systems must comply with the applicable Security Technical Implementation Guides (STIGs). The SUT met the requirement via IA testing, vendor LoC, and all IA Requirement testing done by the JITC IA test team. All IA related requirements status was reported separately. k. PON Network Management Requirements. Network managers must be able to monitor, configure, and control all aspects of the network and observe changes in network status. (1) Secure Shell version 2 (SSHv2). The PON products shall support RFC 4251 through RFC 4254 inclusive. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (2) Telnet. The PON product shall be configured by default not to accept Telnet. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (3) Hypertext Transfer Protocol, Secure (HTTPS). HTTPS shall be used instead of Hypertext Transfer Protocol due to its increased security as described in RFC The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (4) RFC The LAN products shall support RFC 3414 for SNMP. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. (5) LAN Interface. If other methods are used for interfacing between LAN products and the NM System (NMS), they shall be implemented in a secure manner. The SUT met the requirement via vendor LoC and interoperability testing using test equipment and simulated information exchanges. 2-16

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of the Special

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Apr 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Apr 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 Apr 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 Jan 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 Fort Meade, Maryland

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 Fort Meade, Maryland DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 Fort Meade, Maryland 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 Sep 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 23 Oct 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 23 Oct 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 23 Oct 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 14 Apr 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 14 Apr 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 14 Apr 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 Jan 14

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 Jan 14 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 21 Jan 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 5 Oct 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 26 Mar 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 26 Mar 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 26 Mar 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 Jul 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 16 Oct 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 16 Oct 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 16 Oct 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 12 Dec 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 12 Dec 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 12 Dec 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Oct 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Oct 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 Oct 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Aug 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Aug 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Aug 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 27 May 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 27 May 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 27 May 11 SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 11 Sep 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 11 Sep 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 11 Sep 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 11 Oct 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 11 Oct 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 11 Oct 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 2 Nov 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 22 Feb 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 22 Feb 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 22 Feb 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 2 Feb 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 2 Nov 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

Joint Interoperability Test Command (JTE) 8 May 13

Joint Interoperability Test Command (JTE) 8 May 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 May 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 18 Oct 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 19 Oct 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 19 Oct 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 19 Oct 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 19 Oct 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 19 Oct 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 19 Oct 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of the Joint

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 30 Oct 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 30 Oct 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 30 Oct 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 Thanks IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 22 Jan 16 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 Thanks IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 23 Oct 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTD) 15 Aug 14

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTD) 15 Aug 14 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTD) 15 Aug 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 Sep 15 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 20 May 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 20 May 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 20 May 11 SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 3 May 2012

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 3 May 2012 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 3 May 2012 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Thanks DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 Thanks IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 18 Dec 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Nov 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Nov 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Nov 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 6 Dec 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 22 Dec 08 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE)

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION Ser JT4/1225 18 February 2010 SUBJECT:

More information

SUBJECT: Special Interoperability Test Certification of RedSky Technologies, Inc., Cielo Enhanced 911 (E911) Manager with Software Release 5.5.

SUBJECT: Special Interoperability Test Certification of RedSky Technologies, Inc., Cielo Enhanced 911 (E911) Manager with Software Release 5.5. DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 26 Oct 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 28 Dec 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 28 Dec 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 28 Dec 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Jul 14

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 Jul 14 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Jul 14 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 15 Aug 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 15 Aug 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 15 Aug 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 25 July 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 25 July 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 25 July 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 7 Oct 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 1 Jun 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 1 Jun 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 1 Jun 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 Oct 08 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 12 Jan 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 15 Jun 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 15 Jun 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 15 Jun 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE)

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION Ser JT4/1224 18 February 2010 SUBJECT:

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Feb 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA MEMORANDUM FOR DISTRIBUTION 10 Jun 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA MEMORANDUM FOR DISTRIBUTION 10 Jun 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 10 Jun 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 13 June 2018

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 13 June 2018 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 13 June 2018 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 5 Jan 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 5 Jan 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 5 Jan 11 MEMORANDUM FOR DISTRIBUTION Subject: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 14 Apr 16

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 14 Apr 16 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 14 Apr 16 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 22 Jan 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 22 Jan 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 22 Jan 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 30 April 2012

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 30 April 2012 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 30 April 2012 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 27 Mar 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 30 Sep 10

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 30 Sep 10 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 30 Sep 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Sep 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 Feb 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 Feb 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 21 Feb 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 16 Apr 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 22 Jul 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 9 Feb 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 20 Aug 08 MEMORANDUM FOR DISTRIBUTION Subject: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 27 Apr 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 27 Apr 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 27 Apr 11 SUBJECT: Special Interoperability

More information

MEMORANDUM FOR DISTRIBUTION 18 Mar 11

MEMORANDUM FOR DISTRIBUTION 18 Mar 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BO 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 18 Mar 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND F. Joint Interoperability Test Command (JTE) 15 Oct 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND F. Joint Interoperability Test Command (JTE) 15 Oct 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 F IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 15 Oct 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 26 May 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 26 May 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 26 May 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Jan 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 24 Jan 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 Jan 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 16 Jul 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 29 Nov 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 29 Nov 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BO 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 29 Nov 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 25 Mar 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 25 Mar 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 25 Mar 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 24 June 2008

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 24 June 2008 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 June 2008 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 8 Dec 10

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA Joint Interoperability Test Command (JTE) 8 Dec 10 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BO 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 Dec 10 MEMORANDUM FOR SEE DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 17 Jan 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 17 Jan 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 17 Jan 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 24 Mar 09 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 16 Jun 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 16 Jun 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 16 Jun 11 SUBJECT: References:

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 25 Mar 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 25 Mar 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 25 Mar 11 SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 3 Dec 08 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 23 Jan 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 23 Jan 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYAND 0755-0549 IN REPY REFER TO: Joint Interoperability Test Command (JTE) 3 Jan 5 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 October 2012

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 10 October 2012 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 October 2012 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 18 Oct 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA

DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA 85613-7051 IN REPLY REFER TO: Networks, Transmission and Integration Division (JTE) MEMORANDUM

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 13 May 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 10 Feb 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 2 Sep 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 2 Sep 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 2 Sep 11 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 13 Mar 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTD) 1 March 2018

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTD) 1 March 2018 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTD) 1 March 2018 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND F

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND F DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 F IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 30 Mar 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 6 Sept 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 6 Sept 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 6 Sept 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Battlespace Communications Portfolio (JTE) 08Aug 08 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 15 Jun 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 15 Jun 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYAND 0755-0549 IN REPY REFER TO: Joint Interoperability Test Command (JTE) 5 Jun 5 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 29 Jul 14

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 29 Jul 14 ol DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYAND 0755-0549 IN REPY REFER TO: Joint Interoperability Test Command (JTE) 9 Jul 4 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 8 August 2017

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 8 August 2017 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 8 August 2017 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 13 Jan 15

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 13 Jan 15 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYAND 0755-0549 IN REPY REFER TO: Joint Interoperability Test Command (JTE) 3 Jan 5 MEMORANDUM FOR DISTRIBUTION SUBJECT: Joint Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 27 July 12

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 27 July 12 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 27 July 12 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA 22204-4502 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 5 Oct 10 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability

More information

DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA

DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA DEFENSE INFORMATION SYSTEMS AGENCY JOINT INTEROPERABILITY TEST COMMAND 2001 BRAINARD ROAD FORT HUACHUCA, ARIZONA 85613-7051 IN REPLY REFER TO: Networks, Transmission and Integration Division (JTE) 21 January

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 May 13

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 21 May 13 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 21 May 13 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of

More information

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 6 Jul 11

DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND MEMORANDUM FOR DISTRIBUTION 6 Jul 11 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND 20755-0549 IN REPLY REFER TO: Joint Interoperability Test Command (JTE) MEMORANDUM FOR DISTRIBUTION 6 Jul 11 SUBJECT: Special Interoperability

More information