This protocol specifies a mechanism for optimized transfer of IPv4 or IPv6 over STANAG 5066.   Overhead can be reduced significantly relative to IP Client specified in Annex F of STANAG 5066 in situations where IP addressing can be determined from STANAG 5066 addressing and most other IP header fields defaulted.

This is specifically intended for black side STANAG 5066 used with IP Crypto, where it is anticipated that this protocol can be used for all IP packets.

This document is part of the STANAG 5066 Application Protocol (S5066-APP) series. The complete set of documents in the series are:

  1. STANAG 5066 Application Protocol Index (S5066-APP1)
  2. HF Discovery, Ping and Traffic Load (S5066-APP2)
  3. SIS Layer Extension Protocol (SLEP) (S5066-APP3)
  4. Providing STANAG 5066 services over UDP/IP (S5066-APP4)
  5. Implicit IP Client over STANAG 5066 (S5066-APP5)
  6. Providing Control Parameters for STANAG 5066 over UDP/IP through IP Crypto (S5066-APP6)
  7. XML Control Messages for STANAG 5066 over UDP/IP through a Data Diode (S5066-APP7)
  8. HF File Transfer Protocol (HFFTP) (S5066-APP8)

STANAG 5066 Encoding

An IP packet is encoded as STANAG 5066 User Data as follows:

  MSB
7
6 5 4 3 2 1 LSB
0
0
Not Used
IPv4
Version=0
1







n
IP Data








The version is set to 0. If IPv4 bit is set to1, the protocol is IPv4. Otherwise it is IPv6. This allows both IPv4 and IPv6 to be used.
IP Source and Destination addresses (IPv4 or IPv6) are inferred from the STANAG 5066 source and destination addresses. This protocol can only be used where there is a clear system wide mapping between these addresses.

On reception, an IP header will be generated with default values.   So this protocol can only be used if special IP services (e.g., Fragmentation) are not used and there is no information in the incoming header which is essential to include in the generated header.  

Recommended SAP ID

Prior to an official assignment, it is recommended to run this protocol over SAP ID 13.