09.02.2015 Views

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

SHOW MORE
SHOW LESS

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 />

Changes from Version 1.0 to Version 1.0.2 (<strong>this</strong> should be deleted from the final version):<br />

• Main body, page 5 - added List of Annexes<br />

• In List of Annexes and in each Annex, indic<strong>at</strong>ed whether Annex is mand<strong>at</strong>ory or<br />

inform<strong>at</strong>ion only<br />

Annex A:<br />

• Corrections to Table A-1<br />

• S_BIND_ACCEPTED: specified th<strong>at</strong> maximum MTU of 4096 for broadcast-only nodes<br />

• S_UNBIND_INDICATION: added reasons<br />

• S_EXPEDITED_UNIDATA_REQUEST: added guidance on use<br />

• S_HARD_LINK_REJECTED: added reasons<br />

• S_HARD_LINK_TERMINATED: added reasons<br />

• Section A.2.1: Added version and size fields to all S_primitives (Figure A-1(a))<br />

• Figure A-1(f): changed wording of TTL to m<strong>at</strong>ch (new) resolution of TTD<br />

• Figure A-1(g): changed _INDICATION primitives to allow indic<strong>at</strong>ion of missing as well<br />

as blocks with errors<br />

• Figure A-1(i): changed text following to indic<strong>at</strong>e th<strong>at</strong> “deliver in order” applies only to<br />

ARQ service.<br />

Section A.3.1<br />

• DATA S_PDU: changed text to m<strong>at</strong>ch figure here and to m<strong>at</strong>ch Figure A-4(a)<br />

• DATA DELIVERY FAIL S_PDU: Added reasons<br />

• HARD LINK ESTABLISHMENT REJECTED S_PDU: Added reasons<br />

• HARD LINK TERMINATE S_PDU: Added reasons<br />

• Text following Figure A-4(b): changed definition of TTD<br />

• Section A.3.2.2.1: changed wording and rules<br />

Annex B<br />

• Figure B-3(a): modified logic to allow multiple connections<br />

• Figure B-3(b): expanded<br />

Annex C<br />

• Section C.1: editorial changes. Also th<strong>at</strong> in the “non-reliable” mode, delivery of<br />

complete C_PDUs is not guaranteed.<br />

Section C.3<br />

• Previously advertised EOT shall not be viol<strong>at</strong>ed<br />

• Each D_PDU description placed in its own subsection (C.3.2 - C.3.11)<br />

• Section C.3.1: change “first 3 bytes” → “first 4 bytes”<br />

• Section C.3.1.2, Figure C-2: added figure C-2(d), EOW Message Type 3 (version<br />

number): The Type 3 EOW message shall be placed in all non-ARQ D_PDUs<br />

• Section C.3.1.3: EOT clarific<strong>at</strong>ions; all zeros reserved for full duplex or broadcast<br />

oper<strong>at</strong>ion<br />

• Section C.3.1.4: clarified address encoding<br />

• Section C.3.1.5: added example CRC calcul<strong>at</strong>ion<br />

• New section C.3.3: deleted sentence “If the bit representing … it will always be zero).”<br />

Changed Figure C-6 to m<strong>at</strong>ch.<br />

• New section C.3.3: Changed Table C-4 and text so th<strong>at</strong> repetitions are not mand<strong>at</strong>ory.<br />

• New section C.3.5: added reference to C.4.4 for detailed FULL RESET procedure;<br />

changed Table C-5 and text so th<strong>at</strong> repetitions are not mand<strong>at</strong>ory.<br />

• New section C.3.8: changed table C-6 to reserve message types 5 and 6 for ALM.<br />

Changed Figure C-12(a) to apply to Message types 0 and 4.<br />

• New section C.3.9: Added reference to new type 4 EOW message and specified th<strong>at</strong> it<br />

shall be sent when non-ARQ D_PDUs are transmitted.<br />

NATO UNCLASSIFIED<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!