nato unclassified - Ham-pages ... No indexes at this level

More documents

Recommendations

Info

NATO UNCLASSIFIED STANAG 5066: PROFILE FOR MARITIME HF DATA COMMUNICATION V1.0.2 The only field of this S_PDU is “TYPE”. A value of 7 identifies that the S_PDU is of type HARD LINK TERMINATE CONFIRM. Bit-Maps of the S_PDUs types are shown in Figs. A-4 (a) and (b). MSB LSB 7 6 5 4 3 2 1 0 0 TYPE * PRIORTY * TYPE = 0 (DATA S_PDU) 1 2 3 SOURCE SAP ID DESTINATION SAP ID DLVRY VALID CONFN NOT USED TTD TTD ** RQRD TTD *** S_PCI **These bits are “dont care” if VALID TTD flag is not set . ***These bytes do not exist i f VALID TTD flag is not set 4 TTD *** U_PDU Figure A-4 (a): Bit Maps of S_PDUs MSB LSB 7 6 5 4 3 2 1 0 0 1 TYPE * SOURCE SAP ID NOT USED DESTINATION SAP ID S_PCI * TYPE = 1 (DATA DELIVERY CONFIRMS_PDU) U_PDU (OR PART OF IT) MSB LSB 7 6 5 4 3 2 1 0 0 1 TYPE * SOURCE SAP ID REASON DESTINATION SAP ID S_PCI * TYPE = 2 (DATA DELIVERY FAIL S_PDU) U_PDU (OR PART OF IT) NATO UNCLASSIFIED 32
NATO UNCLASSIFIED STANAG 5066: PROFILE FOR MARITIME HF DATA COMMUNICATION V1.0.2 0 MSB LSB 7 6 5 4 3 2 1 0 TYPE * LINK TYPE LINK PRIORITY * TYPE = 3 (HARD LINK ESTABLISHMENT REQUEST S_PDU) 1 REQUESTING SAP ID REMOTE SAP ID** ** VALID ONLY IF LINK TYPE = 3 0 MSB LSB 7 6 5 4 3 2 1 0 TYPE * NOT USED * TYPE = 4 (HARD LINK ESTABLISHMENT CONFIRM S_PDU) 0 MSB LSB 7 6 5 4 3 2 1 0 TYPE * REASON * TYPE = 5 (HARD LINK ESTABLISHMENT REJECTED S_PDU) 0 MSB LSB 7 6 5 4 3 2 1 0 TYPE * REASON * TYPE = 6 (HARD LINK TERMINATE S_PDU) 0 MSB LSB 7 6 5 4 3 2 1 0 TYPE * NOT USED * TYPE = 7 (HARD LINK TERMINATE CONFIRM S_PDU) Figure A-4 (b): Bit Maps of S_PDUs The TTD field shall be filled with the GMT in 1/8 seconds after which time the S_PDU must be discarded by the receiving peer if it has not yet been delivered to the client. The TTD field shall be filled with the Julian date 4 modulo 16, and the GMT in seconds after which time the S_PDU must be discarded if it has not yet been delivered to the client. The Julian date mod 16 part of the TTD shall be mapped into bits 0-3 of byte 2 of the S_PDU. The 16 high bits of the GMT part of the TTD shall be mapped into the 2 remaining bytes of the TTD field; the LSB of the GMT shall be discarded. If the “VALID TTD” flag bit of a DATA S_PDU is set (=1) then the complete TTD 20-bit field is present and its value must be used. If this flag bit is not set (=0), the last two bytes of the TTD field are not present (to conserve overhead) and the TTD must not be used. The “VALID TTD” flag bit allows the transmitting peer to specify whether the S_PDU should be discarded by the receiving peer based on TTD or it should be delivered to the client without consideration of the TTD. The bit-maps of the remaining fields of the S_PDUs do not require additional explanation as there is a one-to-one association with the corresponding fields shown in the generic encoding of Figure A-3. A.3.2 Peer-to-Peer Communication Protocol 4 The simple Julian date system, which numbers the days of the year consecutively starting with 001 on 1 January and ending with 365 on 31 December (or 364 on leap years). NATO UNCLASSIFIED 33
Page 1 and 2: NATO UNCLASSIFIED NATO Standardizat
Page 3 and 4: NATO UNCLASSIFIED STANAG 5066: PROF
Page 39: NATO UNCLASSIFIED STANAG 5066: PROF
Page 91 and 92:
NATO UNCLASSIFIED STANAG 5066: PROF
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155:
show all

nato unclassified - Ham-pages ... No indexes at this level

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?