nato unclassified - Ham-pages ... No indexes at this level
nato unclassified - Ham-pages ... No indexes at this level
nato unclassified - Ham-pages ... No indexes at this level
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
NATO UNCLASSIFIED<br />
STANAG 5066: PROFILE FOR MARITIME HF DATA COMMUNICATION<br />
V1.0.2<br />
Type :<br />
“3” = HARD LINK ESTABLISHMENT REQUEST<br />
Encoding :<br />
TYPE<br />
(=3)<br />
LINK<br />
TYPE<br />
LINK<br />
PRIORITY<br />
REQUESTING<br />
SAP ID<br />
REMOTE<br />
SAP ID<br />
Description :<br />
This S_PDU is transmitted by a Peer in response to a Client’s request for a Hard<br />
Link. Since the establishment of a Hard Link overrides the normal procedures of<br />
making Links based on the destin<strong>at</strong>ions of the queued U_PDUs (Soft Links), it is<br />
important th<strong>at</strong> both Peers use a handshake procedure in order to confirm the<br />
successful Hard Link establishment The first field of the S_PDU is “TYPE”. It is<br />
equal to 3 and identifies the S_PDU as being of type HARD LINK<br />
ESTABLISHMENT REQUEST. The “LINK TYPE” and “LINK PRIORITY” fields<br />
are direct copies of the corresponding arguments of the<br />
S_HARD_LINK_ESTABLISH Primitive submitted by the Client. The<br />
“REQUESTING SAP ID” field is the SAP ID of the Client which requested the Hard<br />
Link Establishment. The “REMOTE SAP ID” field identifies the single Client<br />
connected to the remote <strong>No</strong>de, to and from which traffic is allowed. This argument is<br />
only valid if the “LINK TYPE” field has a value of 2 (see discussion <strong>at</strong> the end of<br />
<strong>this</strong> section for clarific<strong>at</strong>ion). For other values of “LINK TYPE” the “REMOTE SAP<br />
ID” is “don’t care”.<br />
Type :<br />
“4” = HARD LINK ESTABLISHMENT CONFIRM<br />
Encoding :<br />
TYPE<br />
(=4)<br />
Description :<br />
This S_PDU is transmitted as a positive response to the reception of a HARD LINK<br />
ESTABLISHMENT REQUEST S_PDU. Its only field is “TYPE”, which is equal to<br />
4 and identifies the S_PDU as being of type HARD LINK ESTABLISHMENT<br />
CONFIRM. The peer which receives <strong>this</strong> S_PDU should inform its appropri<strong>at</strong>e<br />
Client accordingly with a S_HARD_LINK_ESTABLISHED Primitive.<br />
Type :<br />
“5” = HARD LINK ESTABLISHMENT REJECTED<br />
Encoding :<br />
TYPE<br />
(=5)<br />
REASON<br />
Description :<br />
This S_PDU is transmitted as a neg<strong>at</strong>ive response to the reception of a HARD LINK<br />
ESTABLISHMENT REQUEST S_PDU. The first field is “TYPE” and contains a<br />
value of 5 to identify the S_PDU as being of type HARD LINK ESTABLISHMENT<br />
REJECTED. The second field is “REASON” and explains why the Hard Link<br />
NATO UNCLASSIFIED<br />
30
Change language