MIL STD 3011

MIL STD 3011
How can we make it better?
Mr. Brian Bass
Allied Training Manager
Joint Interoperability Division
Fort McPherson, GA, USA
[email protected]
404-464-4649
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
2
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
3
Early BLOS Link 16 Efforts
Service Unique
Non-standardized Protocols
STJ
UHF SATCOM
Navy UHF DAMA
Serial J
Interface to ADSI
Point-to-Point
SHF SATCOM
• Limited
Interoperability
• Work-around was
required
• Funding did not tie
improvements in one
system to the other
Legacy
Point-to-Point
Socket J
Legacy IP Interfaces
UNCLASSIFIED
4
1996
CVBG
F14/F15
E-2 HAWKEYE
ATDL-1
RJ
Link 11B
TACC
TAOC
Link 11
Link 16
(FJUA/B)
CRE
CRC
ATDL-1
(FPU)
E-3 AWACS
(NCS)
Backup
JSTARS
AMDPCS
(AAMDC)
AMDPCS
AOC
(JFACC)
ICC
Link 11 B
ICC
PATRIOT
PATRIOT
PATRIOT
PATRIOT
UNCLASSIFIED
PATRIOT
Link 11
Link 11B
Link 16
ATDL-1
PADIL
5
1999
CRE
CRC
E-3
CRE
RJ
JSTARS
ABCCC
E-3
Aegis CG/DD
TF HAWK
CRE
Leyte Gulf
E-3
Link 11
Link 11B
Link 16
CRC
Serial J
CVBG
UNCLASSIFIED
E-2
6
2000
SAG
Link 11
Link 11B
Link 16
Serial J
BG Alpha
BG Bravo
UNCLASSIFIED
7
2001
JRE
JRE
CRC
ADA
AOC
CBG
UNCLASSIFIED
Satellite-A
Satellite-J
RF Link16
Land Lines
HF Link 11
8
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
9
Transition to a Standard
Service Unique
Non-standardized Protocols
Joint Range Extension
Application Protocol (JREAP)
MIL-STD 3011
STJ
UHF SATCOM
Navy UHF DAMA
Appendix A – Token
Passing
(UHF SATCOM)
Serial J
Interface to ADSI
Point-to-Point
Appendix B – Point To Point
SHF SATCOM
(Phone Lines/SHF SATCOM)
Legacy
Point-to-Point
Appendix C – IP / UDP
Socket J
SIPRNET/ EHF
Legacy IP Interfaces
UNCLASSIFIED
10
UNCLASSIFIED
11
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
12
MIL-STD 3011 Organization
•
•
•
•
•
•
Applicable Documents
Definitions, Terms, and Acronyms
General Requirements
Detailed Requirements
Notes
Appendices A, B, and C
UNCLASSIFIED
13
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
14
JREAP Design
JTIDS Zone
JTIDS Zone
JRE
Processor
TCP/IP
JRE
Processor
UNCLASSIFIED
15
Open System Interconnect (OSI)
•
•
•
•
•
•
•
Application
Presentation
Session
Transport
Network
Data Link
Physical
UNCLASSIFIED
16
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-1881582)
– 5- and 25-kHz UHF non-DAMA SATCOM (MIL-STD-188-181)
UNCLASSIFIED
17
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
18
Appendix B
• Full Duplex Synchronous or Asynchronous Point-toPoint Connection
Media
JRE
Processor
Crypto
Media
Interface
Media
Interface
UNCLASSIFIED
Crypto
JRE
Processor
19
Appendix B Planning
Considerations
•
•
•
•
•
•
Connection Type
Crypto Device drive crypto used
Throughput
Circuit Planning
Backup Links
Data Loops
UNCLASSIFIED
20
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
21
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
22
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
23
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
24
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
UNCLASSIFIED
25