MIL STD 3011 How can we make it better?

Mr. Brian BassAllied Training Manager

Joint Interoperability DivisionFort McPherson, GA, USAbrian.bass1@us.army.mil

404-464-4649

UNCLASSIFIED 2

Overview

• 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

UNCLASSIFIED 3

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 making

UNCLASSIFIED 4

Early BLOS Link 16 Efforts

• Limited Interoperability

• Work-around was required

• Funding did not tie improvements in one system to the other

Service UniqueNon-standardized Protocols

STJUHF SATCOM

Navy UHF DAMA

Serial JInterface to ADSI

Point-to-Point

SHF SATCOMLegacy

Point-to-Point

Socket JLegacy IP Interfaces

UNCLASSIFIED 5

1996CVBG

RJ

E-2 HAWKEYE

JSTARS

F14/F15

AOC(JFACC)

TAOC(FJUA/B)

E-3 AWACS(NCS)

Link 16Link 16

PATRIOT

Link 11BLink 11B

ATDLATDL--11

CRE

CRC(FPU)

TACC

ATDLATDL--11

AMDPCS(AAMDC)

Link 11 BLink 11 B

Link 11Link 11

PATRIOT PATRIOTPATRIOT

PATRIOT

ICCICC

AMDPCS

Link 11Link 11BLink 16ATDL-1PADIL

Backup

UNCLASSIFIED 6

1999

Link 11Link 11B

Serial JLink 16

CRC

TF HAWK

CRE

CRC

CRE

CRE

Aegis CG/DD

Leyte Gulf

CVBG

E-3

E-3

E-3

RJJSTARSABCCC

E-2

UNCLASSIFIED 7

2000

SAG

BG AlphaBG Bravo

Link 11Link 11B

Serial JLink 16

UNCLASSIFIED 8

2001

Satellite-ASatellite-JRF Link16Land LinesHF Link 11

CBG

ADA

AOC

CRC

JRE

JRE

UNCLASSIFIED 9

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 time

UNCLASSIFIED 10

Transition to a Standard

Appendix B – Point To Point(Phone Lines/SHF SATCOM)

Appendix A – Token Passing

(UHF SATCOM)

Appendix C – IP / UDPSIPRNET/ EHF

Service UniqueNon-standardized Protocols

STJUHF SATCOM

Navy UHF DAMA

Serial JInterface to ADSI

Point-to-Point

SHF SATCOMLegacy

Point-to-Point

Socket JLegacy IP Interfaces

Joint Range ExtensionApplication Protocol (JREAP)

MIL-STD 3011

UNCLASSIFIED 11

UNCLASSIFIED 12

In accordance with DoD Instruction 4630.8, it is DoD policy that all Joint and combined operations be supported by compatible, interoperable, and integrated Command, Control, Communications, and Intelligence (C3I) systems.

UNCLASSIFIED 13

MIL-STD 3011 Organization

• Applicable Documents• Definitions, Terms, and Acronyms• General Requirements• Detailed Requirements• Notes• Appendices A, B, and C

UNCLASSIFIED 14

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 TDL

UNCLASSIFIED 15

TCP/IP

JREAP Design

JREProcessor

JREProcessor

JTIDS Zone

JTIDS Zone

UNCLASSIFIED 16

Open System Interconnect (OSI)

• Application• Presentation• Session• Transport• Network• Data Link• Physical

UNCLASSIFIED 17

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)

UNCLASSIFIED 18

JREAP A Planning Considerations

• Satellite Access– Satellite Access Request/Authorization

• Participation• Data Rate• Terminal Base Address• Two Encryption Keys (orderwire & data)• Network Roles• OPTASK LINK Inputs

UNCLASSIFIED 19

Appendix B

• Full Duplex Synchronous or Asynchronous Point-to- Point Connection

JREProcessor

JREProcessorCrypto CryptoMedia

InterfaceMedia

Interface

Media

UNCLASSIFIED 20

Appendix B Planning Considerations

• Connection Type• Crypto Device drive crypto used• Throughput• Circuit Planning• Backup Links• Data Loops

UNCLASSIFIED 21

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 port

UNCLASSIFIED 22

Appendix C Planning Considerations

• Group Address: JGROUP• Port Number: JPORT• Firewalls• Server and client relationships• TCP and UDP Differences• Timeliness• Throughput• IP Network Admin Coordination

UNCLASSIFIED 23

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”

UNCLASSIFIED 24

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 Standard

UNCLASSIFIED 25

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