MIL STD 3011 - idlsoc.com

1 MIL STD 3011 How can we make it better?Mr. Brian BassAllied Training ManagerJoint Interoperability DivisionFort McPherson, GA, Historical development of Joint Range Extension Application Protocols ( jreap ) MIL-STD 3011 Organization Applicable Documents Definitions, Terms, and Acronyms General Requirements Detailed Requirements Notes Appendices A, B, and C Technical Review of Appendices A, B, and CUNCLASSIFIED3 The Beginnings of jreap The requirement: Exchange tactical data beyond line of sight in such a manner that the data can be used for situational awareness, planning, and limited decision makingUNCLASSIFIED4 Early BLOS Link 16 Efforts Limited Interoperability Work-around was required Funding did not tie improvements in one system to the otherService UniqueNon-standardized ProtocolsSTJUHF SATCOMNavy UHF DAMAS erial JInterface to ADSIP oint-to-PointSHF SATCOML egacyPoint-to-PointSocket JLegacy IP InterfacesUNCLASSIFIED51996 CVBGRJE-2 HAWKEYEJSTARSF14/F15 AOC(JFACC)TAOC(FJUA/B)E-3 AWACS(NCS)Link 16 Link 16 PATRIOTLink 11 BLink 11 BATDLATDL--11 CRECRC(FPU)TACCATDLATDL--11 AMDPCS(AAMDC)

2 Link 11 BLink 11 BLink 11 Link 11 PATRIOTPATRIOTPATRIOTPATRIOTICCICCAMDPCS Link 11 Link 11 BLink 16 ATDL-1 PADILB ackupUNCLASSIFIED61999 Link 11 Link 11 BSerial JLink 16 CRCTF HAWKCRECRCCRE CREA egis CG/DDLeyte GulfCVBGE-3E-3E-3 RJJSTARSABCCCE-2 UNCLASSIFIED72000 SAGBG AlphaBG BravoLink 11 Link 11 BSerial JLink 16 UNCLASSIFIED82001 Satellite-ASatellite-JRF Link16 Land LinesHF Link 11 CBGADAAOCCRCJREJREUNCLASSIFIED9 Refining the Requirement Increased need to exchange information across service and national boundaries Increased size of the operations area Increased number of BLOS Link 16 equipment available Dynamic targets, precise weapons, shorter reaction timeUNCLASSIFIED10 Transition to a StandardAppendix B Point To Point(Phone Lines/SHF SATCOM)Appendix A Token Passing(UHF SATCOM)Appendix C IP / UDPSIPRNET/ EHFS ervice UniqueNon-standardized ProtocolsSTJUHF SATCOMNavy UHF DAMAS erial JInterface to ADSIP oint-to-PointSHF SATCOML egacyPoint-to-PointSocket JLegacy IP InterfacesJoint Range ExtensionApplication Protocol ( jreap )MIL-STD 3011 UNCLASSIFIED11 UNCLASSIFIED12In accordance with DoD Instruction , it is DoD policy that all Joint and combined operations be supported by compatible, interoperable, and integrated Command, Control, Communications, and Intelligence (C3I)

3 3011 Organization Applicable Documents Definitions, Terms, and Acronyms General Requirements Detailed Requirements Notes Appendices A, B, and CUNCLASSIFIED14 Primary Capabilities of jreap Extending the range-limited tactical networks to beyond LOS while reducing their dependence upon relay platforms Reducing the loading on stressed networks Providing backup communications in the event of the loss of the normal link Providing a connection to a platform that may not be equipped with the specialized communications equipment for that TDLUNCLASSIFIED15 TCP/IPJREAP DesignJREP rocessorJREP rocessorJTIDS ZoneJTIDS ZoneUNCLASSIFIED16 Open System Interconnect (OSI)

4 Application Presentation Session Transport Network Data Link PhysicalUNCLASSIFIED17 Appendix A Half-Duplex Announced Token Passing Protocol This protocol may be used when several terminals share the same JRE media and take turns transmitting, or, in a broadcast situation, when one transmits and the rest receive. Data rates down to 2400 bits per second (bps) on a serial data interface encryption device used for data security Designed for use with media such as: 25-kHz UHF TDMA/DAMA SATCOM (MIL-STD-188-183), EHF LDR Forced Mode Network Operations (MIL-STD-188- 1582) 5- and 25-kHz UHF non-DAMA SATCOM (MIL-STD-188-181)UNCLASSIFIED18 jreap A Planning Considerations Satellite Access Satellite Access Request/Authorization Participation Data Rate Terminal Base Address Two Encryption Keys (orderwire & data)

5 Network Roles OPTASK LINK InputsUNCLASSIFIED19 Appendix B Full Duplex Synchronous or Asynchronous Point-to- Point ConnectionJREP rocessorJREP rocessorCryptoCryptoMediaInterfaceMediaI nterfaceMediaUNCLASSIFIED20 Appendix B Planning Considerations Connection Type Crypto Device drive crypto used Throughput Circuit Planning Backup Links Data LoopsUNCLASSIFIED21 Appendix C Encapsulation over Internet Protocol (IP) TCP: Transmission Control Protocol UDP: User Datagram Protocol Unicast: sent to a specific peer address Multicast: sent to a peer group and portUNCLASSIFIED22 Appendix C Planning Considerations Group Address: JGROUP Port Number.

6 JPORT Firewalls Server and client relationships TCP and UDP Differences Timeliness Throughput IP Network Admin CoordinationUNCLASSIFIED23 OPTASK LINK and jreap Newer USMTF Baselines include jreap sets Older baselines require GENTEXT sets to be added Vital to getting on the same page UNCLASSIFIED24 Improvements to jreap Network Time Standards DIS Compatibility Transition from IPv4 to IPv6 STD maintenance Original 3011 complete in 2002 No recent updates/revisions NATO StandardUNCLASSIFIED25 Summary Historical development of Joint Range Extension Application Protocols ( jreap ) MIL-STD 3011 Organization Applicable Documents Definitions, Terms, and Acronyms General Requirements Detailed Requirements Notes Appendices A, B, and C Technical Review of Appendices A, B, and C