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

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 4502 ARLINGTON, VIRGINIA IN REPLY REFER TO: Battlespace Communications Portfolio (JTE) 08Aug 08 MEMORANDUM FOR DISTRIBUTION SUBJECT: Special Interoperability Test Certification of the Quantum Scalar i2000, Firmware 571.GS00101 with the Datatek Internet Protocol (IP) Version 4/IP Version 6 (IPv6) Translator Version 2.1.4, Disk , Build for IPv6 Capability References: (a) DoDD , "Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS)," 5 May 2004 (b) CJCSI D, "Interoperability and Supportability of Information Technology and National Security Systems," 8 March 2006 (c) through (i), 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 Quantum Scalar i2000, Firmware (FW) 571.GS00101 with the Datatek Internet Protocol (IP) Version 4 (IPv4)/IP Version 6 (IPv6) Translator Version (V) 2.1.4, Disk , Build has met the IPv6 Capable interoperability requirements of a Simple Server as described in the Department of Defense (DoD) Information Technology Standards Registry, DoD IPv6 Standard Profiles for IPv6 Capable Products Version 2.0, 1 August 2007, reference (c). The Quantum Scalar i2000, FW 571.GS00101 with the Datatek IPv4/IPv6 Translator V 2.1.4, Disk , Build device has successfully completed the related IPv6 Interoperability portions of the DoD IPv6 Generic Test Plan (GTP) Version 3, August 2007 reference (d), and is certified for listing on the Unified Capabilities (UC) Approved Products List (APL) as IPv6 Capable. This certification expires upon changes that could affect interoperability, but no later than 3 years from the date of this memorandum. 3. This special certification is based on IPv6 Capable Interoperability testing conducted by JITC at Fort Huachuca, Arizona, and the vendor s Letter of Conformance (LoC) dated 9 May Interoperability testing was conducted from 2 through 6 June 2008 at JITC s Advanced IP Technology Capability. Conformance testing was confirmed by Quantum and was verified in the LoC provided. Enclosure 2 documents the summary test results and describes the devices. Users should verify interoperability before deploying the devices in an environment that varies significantly from that described. 4. The device s interoperability status summary is in table 1, and table 2 contains the equipment listing.

2 JITC Memo, JTE, Special Interoperability Test Certification of the Quantum Scalar i2000, Firmware 571.GS00101 with the Datatek Internet Protocol (IP) Version 4/IP Version 6 (IPv6) Translator Version 2.1.4, Disk , Build for IPv6 Capability Table 1. Interoperability Status Summary Quantum Scalar i2000 Functional Category Requirement Verified Base IPv6 M Yes IPSec S+ No Transition Mechanisms S Yes Quality of Service O No Mobility CS No Bandwidth Limited Networks O No Server O No Host S No LEGEND: CS Conditional Should O Optional IPSec Internet Protocol Security S Should IPv6 Internet Protocol Version 6 S+ Should+ M Must NOTE: The terms Conditional Should, Must, Should, Should+, and Optional are used to reference specific required Request for Comments from the Internet Engineering Task Force, the Department of Defense Information Technology Standards Registry, and the Department of Defense Internet Protocol Version 6 Generic Test Plan. Table 2. Equipment Listing Quantum Scalar i2000 Component Firmware/Software Interface Quantum Scalar i2000 FW 571.GS00101 RJ45 Datatek IPv4/IPv6 Translator V , Disk , Build RJ45 LEGEND: FW Firmware RJ Registered Jack IPv4 Internet Protocol Version 4 V Version IPv6 Internet Protocol Version 6 5. No detailed test report was written in accordance with the DoD IPv6 Transition Office. JITC distributes interoperability information via the JITC Electronic Report Distribution (ERD) system, which uses Unclassified-But-Sensitive Internet Protocol Router Network (NIPRNet) e- mail. More comprehensive interoperability status information is available via the JITC System Tracking Program (STP). The STP is accessible by.mil/gov users on the NIPRNet at Test reports, lessons learned, and related testing documents and references are on the JITC Joint Interoperability Tool (JIT) at (NIPRNet), or (SIPRNet). Information related to IPv6 Capable testing is on the UC APL at 2

3 JITC Memo, JTE, Special Interoperability Test Certification of the Quantum Scalar i2000, Firmware 571.GS00101 with the Datatek Internet Protocol (IP) Version 4/IP Version 6 (IPv6) Translator Version 2.1.4, Disk , Build for IPv6 Capability 6. The JITC point of contact is Donald L. Hann, DSN , commercial (520) , or don.hann@disa.mil. FOR THE COMMANDER: 2 Enclosures a/s RICHARD A. MEADOR Chief Battlespace Communications Portfolio Distribution: Joint Staff J6I, Room 1E596, Pentagon, Washington, DC Joint Interoperability Test Command, Liaison, ATTN: TED/JT1, 2W24-8C, P.O. Box 4502, Falls Church, VA Defense Information Systems Agency, Net-Centricity Requirements and Assessment Branch, ATTN: GE333, Room 244, P.O. Box 4502, Falls Church, VA Office of Chief of Naval Operations (N71CC2), CNO N6/N7, 2000 Navy Pentagon, Washington, DC Headquarters U.S. Air Force, AF/XICF, 1800 Pentagon, Washington, DC Department of the Army, Office of the Secretary of the Army, CIO/G6, ATTN: SAIS-IOQ, 107 Army Pentagon, Washington, DC U.S. Marine Corps (C4ISR), MARCORSYSCOM, 2200 Lester St., Quantico, VA DOT&E, Net-Centric Systems and Naval Warfare, 1700 Defense Pentagon, Washington, DC U.S. Coast Guard, CG-64, nd St. SW, Washington, DC Defense Intelligence Agency, 2000 MacDill Blvd., Bldg 6000, Bolling AFB, Washington, DC National Security Agency, ATTN: DT, Suite 6496, 9800 Savage Road, Fort Meade, MD Director, Defense Information Systems Agency, ATTN: GS235, Room 5W24-8A, P.O. Box 4502, Falls Church, VA Office of Assistant Secretary of Defense (NII)/DOD CIO, Crystal Mall 3, 7th Floor, Suite 7000, 1851 S. Bell St., Arlington, VA Office of Under Secretary of Defense, AT&L, Room 3E144, 3070 Defense Pentagon, Washington, DC U.S. Joint Forces Command, J68, Net-Centric Integration, Communications, and Capabilities Division, 1562 Mitscher Ave., Norfolk, VA DITO, Defense Information Systems Agency (DISA), Attn: GE36, P.O. Box 4502, Arlington, VA Quantum Corporation, Attn: Gary Zellner, 8560 Upland Drive, Englewood, CO

4 ADDITIONAL REFERENCES (c) Department of Defense (DoD) Information Technology Standards Registry (DISR), DoD Internet Protocol Version 6 (IPv6) Standard Profiles for IPv6 Capable Products Version 2.0, 1 August 2007 (d) Defense Information Systems Agency, Joint Interoperability Test Command, DoD IPv6 Generic Test Plan Version 3, August 2007 (e) JITC, Special Interoperability Test Certification of the Datatek Applications, Inc., Internet Protocol Version 4/Internet Protocol Version 6 (IPv6) Transformer Running Software Version for IPv6 Capability, May 2008 (f) DoD Chief Information Officer (CIO) Memorandum, IPv6, 9 June 2003 (g) DoD CIO Memorandum, IPv6 Interim Transition Guidance, 29 September 2003 (h) DoD IPv6 Transition Office, DoD IPv6 Master Test Plan, Version 2, September 2006 (i) DoD, DISR Global Information Grid (GIG) Convergence Master Plan (GCMP), Version 5.25, 29 March 2006 Enclosure 1

5 INTERNET PROTOCOL VERSION 6 CAPABLE TESTING SUMMARY 1. SYSTEM TITLE. Quantum Scalar i2000, Firmware (FW) 571.GS00101 with Datatek Internet Protocol (IP) Version 4 (IPv4)/IP Version 6 (IPv6) Translator Version (V) 2.1.4, Disk , Build , hereafter referred to as the device under test (DUT). 2. PROPONENT. Department of Defense (DoD) IPv6 Transition Office (DITO). 3. PROGRAM MANAGER/USER POC. DITO, Defense Information Systems Agency (DISA), Attn: GE36 Sam Assi, P.O. Box 4502, Arlington, VA , (703) , sam.assi@disa.mil. 4. TESTER. Donald L. Hann, Joint Interoperability Test Command (JITC), P.O. Box 12798, Fort Huachuca, AZ , DSN: , commercial: (520) , don.hann@disa.mil. 5. DEVICE UNDER TEST DESCRIPTION. The DUT was an Intelligent Enterprise Scalable Tape Library designed for disk-based backup solutions. 6. OPERATIONAL ARCHITECTURE. The operational architecture was the JITC simulated Defense Information Systems Network (DISN) IP Core Network as depicted in figure REQUIRED DEVICE INTERFACES. All IPv6-capable products to be included on the Unified Capabilities Approved Product List must meet the requirements of the DoD Information Technology Standards Registry (DISR), DoD IPv6 Standard Profiles for IPv6 Capable Products Version 2.0, 1 August Product testing conducted against these requirements is in accordance with the DoD IPv6 Generic Test Plan (GTP) Version 3, August The IPv6 Simple Server profile requirements for conformance and interoperability are in table 2-1. Enclosure 2

6 LEGEND: CE Customer Edge LAN Local Area Network DISN Defense Information Systems Network P Provider IP Internet Protocol PE Provider Edge JITC Joint Interoperability Test Command VLAN Virtual LAN Figure 2-1. JITC Simulated DISN IP Core Network 2-2

7 Table 2-1. IPv6 Capability Requirements and Status RFC RFC Title Quantum Scalar i2000 Testing Completed Simple Server Conformance Interoperability Requirement Met/Not Met IPv6 Base Implemented 2460 Internet Protocol version 6 (IPv6) Specification Stated in LoC Yes M Met Yes Internet Control Message Protocol 4443 (ICMPv6) for the Internet Protocol Stated in LoC Yes M Met Yes Version 6 (IPv6) Specification 2461 Neighbor Discovery for IP version 6 (IPv6) Stated in LoC Yes M Met Yes 1981 Path Maximum Transmission Unit Discovery for IPv6 Stated in LoC Yes S Met Yes IPv6 Stateless Address Auto 2462 Stated in LoC Yes M Met Yes configuration 3315 DHCPv6 (Client) Not Stated Not Tested M Not Tested No 4291 IPv6 Addressing Architecture Stated in LoC Yes M Met Yes 4007 IPv6 Scoped Address Architecture Stated in LoC Yes M Met Yes 4193 Unique Local IPv6 Unicast Addresses Stated in LoC Yes M Met Yes 2710 Multicast Listener Discovery (MLD) Stated in LoC Yes M Met Yes 3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6 Not Stated Yes S Met Yes 2464 Transmission of IPv6 Packets over Ethernet Networks Stated in LoC Yes CM Met Yes 4301 Security Architecture for the Internet Protocol IPSec Not Stated Not Tested S+ Not Tested No Comments 4302 IP Authentication Header Not Stated Not Tested S Not Tested No 4303 IP Encapsulating Security Payload (ESP) Not Stated Not Tested S+ Not Tested No Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP) Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) Not Stated Not Tested S Not Tested No Not Stated Not Tested S+ Not Tested No 4869 Suite B Cryptographic Suites for IPsec Not Stated Not Tested S+ Not Tested No 2-3

8 Table 2-1. IPv6 Capability Requirements and Status (continued) RFC RFC Title Quantum Scalar i2000 Testing Completed Simple Server Conformance Interoperability Requirement Met/Not Met Implemente d Using Advanced Encryption Standard 4309 (AES) CCM Mode with IPsec Not Stated Not Tested CS Not Tested No Encapsulating Security Payload (ESP) 3971 Secure Neighbor Discovery Not Stated Not Tested S Not Tested No 3972 Cryptographically Generated Addresses Not Stated Not Tested S Not Tested No Privacy Extensions for Stateless Address 3041 Not Stated Not Tested S Not Tested No Auto configuration in IPv Internet Key Exchange (IKEv2) Protocol Not Stated Not Tested S+ Not Tested No Cryptographic Algorithms for Internet Key 4307 Not Stated Not Tested S+ Not Tested No Exchange Version 2 (IKEv2) Transition Mechanisms Transition Mechanisms for IPv6 Host and 4213 Stated in LoC Yes S Met Yes Routers Network Address Translation Protocol 2766 Not Stated Not Tested SN Not Tested No Translation (NAT-PT) 3053 IPv6 Tunnel Broker Not Stated Not Tested CS Not Tested No Definition of the Differentiated Services 2474 Field (DS Field) in the IPv4 and IPv6 Headers Resource ReSerVation Protocol (RSVP) 2205 Version 1 Functional Specification 2207 RSVP Extensions for IPSEC Data Flows The Use of RSVP with IETF Integrated 2210 Services 2750 RSVP Extensions for Policy Control 3175 Aggregation of RSVP for IPv4 and IPv6 Reservations Mobility 3775 Mobility Support in IPv6 (section 9) Not Stated Not Tested CS Not Tested No Bandwidth Limited Networks 3095 Robust Header Compression (RoHC) Not Stated Not Tested O 3241 RoHC over PPP Not Stated Not Tested O Not Tested Not Tested No No 3843 RoHC: A Compression Profile for IP RoHC: A Link-Layer Assisted Profile for 4362 IP/UDP/RTP 2507 IP Header Compression Compressing IP/UDP/RTP Headers for 2508 Low-Speed Serial Links QoS Comments 2-4

9 RFC RFC Title Table 2-1. IPv6 Capability Requirements and Status (continued) Quantum Scalar i2000 Testing Completed Simple Server Conformance Interoperability Requirement Met/Not Met Implemented Server 959 File Transfer Protocol 2428 FTP Extensions for IPv6 and NAT 2821 Simple Mail Transfer Protocol (SMTP) 2911 Internet Printing Protocol RADIUS (Remote Authentication dial-in 3162 User Service) and IPv Simple Network Time Protocol (SNTP) DNS Security and IPv6 A6 Aware 3226 Server/Resolver Message Size Requirements 3261 Session Initiation Protocol (SIP) 3596 DNS Extensions to Support IPv6 Host 3484 Default Address Selection for IPv6 Not Stated Not Tested S Not Tested No 3596 DNS Extensions to Support IPv6 Not Stated Not Tested S Not Tested No Uniform Resource Identifier (URI): Generic 3986 Not Stated Not Tested S Not Tested No Syntax LEGEND: CBC Cipher Block Chaining M Must CCM CBC MAC Mode MAC Message Authentication Code CM Conditional Must O Optional CS Conditional Should PPP Point-to-Point Protocol DHCPv6 Dynamic Host Configuration Protocol Version 6 QoS Quality of Service DNS Domain Name Service RFC Request for Comment DoD Department of Defense RoHC Robust Header Compression FTP File Transfer Protocol RSVP Resource ReSerVation Protocol IETF Internet Engineering Task Force RTP Real-Time Transport Protocol IP Internet Protocol S Should IPSec Internet Protocol Security S+ Should Plus ISAKMP Internet Security Association and Key Management Protocol SN Should Not LoC Letter of Conformance UDP User Datagram Protocol NOTES: 1. The terms Must, Conditional Must, Should, Should+, Conditional Should, Should Not, and Optional are used to reference specific required RFCs from the IETF, the DoD Information Technology Standards Registry, and the DoD IPv6 Generic Test Plan. Comments 2-5

10 8. TEST NETWORK DESCRIPTION. The DUT was tested as part of the JITC simulated DISN IP Core Network managed by the Advanced IP Technology Capability, and configured as shown in figure 2-2. LEGEND: CE Customer Edge LAN Local Area Network DISN Defense Information Systems Network P Provider IP Internet Protocol PE Provider Edge IPv4 Internet Protocol Version 4 VLAN Virtual LAN IPv6 Internet Protocol Version 6 Figure 2-2. Test Network 9. DEVICE CONFIGURATIONS. Table 2-2 provides hardware and software components used in the test network. 2-6

11 Table 2-2. Test Configuration Hardware and Software Equipment Name Model Number IOS/OS/Version(s) Hardware Quantum Scalar - DUT Scalar i2000 FW 571.GS00101 Datatek IPv4/IPv6 Translator Disk , Build Cisco Router Cisco (11)T Cisco Router Cisco (11)T Juniper Router Juniper M40e V 7.6R3.6 Juniper Router Juniper M40e V 7.6R3.6 Juniper Router Juniper T320 V 7.5R4.4 Juniper Router Juniper T320 V 7.5R4.4 Juniper Router Juniper T640 V 7.5R4.4 3 Dell Power Edge Servers 2850 MS 2003 Server 1 Dell Power Edge Server 1950 MS 2008 Server 1 Gateway Notebook 450ROG Windows XP Professional Software Windows XP Professional N/A Build SP2 Windows Server 2003 N/A Build SP1 Windows Server 2008 N/A Build Wireshark N/A V (SVN Rev 18752) LEGEND: DUT Device Under Test R Release FW Firmware Rev Revision IOS Internetworking Operating System SP Service Pack MS Microsoft SVN Software Version Number N/A Not Applicable T New Technology OS Operating System V Version 10. TEST LIMITATIONS. None. 11. TEST RESULTS. a. IPv6 Base. Test Case C.1.1. The Request for Comments (RFC) 1981 Path Maximum Transmission Unit Discovery for IPv6 is necessary for proper IPv6 implementations. It acts as a mechanism to determine the maximum size of packets to traverse the network without fragmentation. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C.1.2. The RFC 2460 IPv6 Specification is the base specification of the IPv6 protocol. It specifies a number of parameters that enable successful completion of IPv6 traffic addressing and control. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. 2-7

12 Test Case C.1.3. The RFC 2461 Neighbor Discovery for IPv6 specifies the neighbor discovery function that is similar to address resolution protocol in IPv4. It is necessary for implementing neighbor solicitations and neighbor advertisements within IPv6. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C.1.4. The RFC 2462 IPv6 Stateless Address Auto-configuration specifies how a host auto-configures its interfaces in IPv6. These steps include determining whether the source addressing should be stateless or stateful, whether the information obtained should be solely the address or include other information, and Duplicate Address Detection. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C.1.5. The RFC 2464 Transmission of IPv6 Packets over Ethernet Networks specifies the frame format for transmission of IPv6 link-local addresses and statelessly auto-configured addresses on Ethernet networks. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C.1.8. The RFC 2710 Multicast Listener Discovery for IPv6 specifies the protocol used by an IPv6 router to discover the presence of multicast listeners (i.e., nodes wishing to receive multicast packets) on its directly attached links, and to discover specifically which multicast addresses are of interest to those neighboring nodes. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C The RFC 4007 IPv6 Scoped Address Architecture defines the nature and characteristics for the usage of IPv6 addresses of different scopes. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C The RFC 4193 Unique Local IPv6 Unicast Addresses defines globally unique local addresses. Local IPv6 unicast addressing is intended to be used for local communications and is not expected to be routed to the Internet. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C The RFC 4291 IPv6 Addressing Architecture defines the specifications for the addressing architecture of the IPv6 protocol. The definitions cover unicast addresses, anycast addresses, and multicast addresses. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. Test Case C The RFC 4443 identifies Internet Control Message Protocol messages for the IPv6 protocol. It includes message format and identifies two types of messages: error and informational. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. 2-8

13 b. Transition Mechanisms. Test Case C The RFC 4213 Transition Mechanisms for IPv6 Host and Routers specifies IPv4 co-existence mechanisms that can be implemented by IPv6 devices. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met the test requirement. c. Conclusion. The Quantum Scalar i2000 with the Datatek IPv4/IPv6 Translator met all the required RFCs. 12. TEST AND ANALYSIS REPORT. No detailed test report was written in accordance with the DITO. All test data is maintained in the Advanced IP Technology Capability and is available upon request. This certification is available on the Joint Interoperability Tool (JIT). The JIT homepage is (NIPRNet), or (SIPRNet). The JIT has links to JITC interoperability documents to provide the DoD community, including the warfighter in the field, easy access to the latest interoperability information. System interoperability status information is available via the JITC System Tracking Program (STP). The STP is accessible by.mil/.gov users on the NIPRNet at: 2-9