ARMY MIL-STD-2045-47001 D CHANGE 1-2008 CONNECTIONLESS DATA TRANSFER APPLICATION LAYER STANDARD《无连接数据传送应用层标准》.pdf

1、 NOT MEASUREMENT SENSITIVE MIL-STD-2045-47001D w/CHANGE 1 23 June 2008 SUPERSEDING MIL-STD-2045-47001D 29 September 2005 DEPARTMENT OF DEFENSE INTERFACE STANDARD CONNECTIONLESS DATA TRANSFER APPLICATION LAYER STANDARD AMSC N/A AREA DCPS DISTRIBUTION STATEMENT A. Approved for public release; distribu

2、tion is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 ii FOREWORD This military standard is approved for use by all Departments and Agencies of the Department of Defense (DoD). This military standard is pro

3、duced by the Radio Information Transfer Technical Working Group (RITTWG). The MIL-STD-2045 document series was established within the Data Communication Protocol Standards (DCPS) Standardization Area to allow for the enhancement of commercial standards or the development of standards that are unique

4、 to DoD. Specific details and instructions for establishing a MIL-STD-2045 document, as well as profile development guidelines, are documented in the RITTWG Management Plan. RITTWG Working Groups (WGs) are responsible for standard development, formal service and agency coordination, and approval. Th

5、is military standard does not supersede the scope of Allied Communication Publication (ACP) 123 with US SUPP-1. ACP 123 with US SUPP-1 addresses message handling communications protocol and procedures for the exchange of military messages. The Preparing Activity (PA) for this standard is USA CECOM L

6、CMC, ATTN: AMSEL-SE-CD (Chairman, Combat Net Radio Working Group (CNRWG), Fort Monmouth, NJ 07703. The custodians for the document are identified in the Defense Standardization Program, “Standardization Directory (SD1)” under Standardization Area DCPS. Beneficial comments (recommendations, additions

7、, deletions) and any pertinent data that may be of use in improving this military standard should be addressed to the PA at the above address by letter. Comments, suggestions, or questions on this document should be addressed to CDR, USA CECOM LCMC, ATTN: AMSEL-SE-CD Chairman, (CNRWG), Building 1209

8、, Fort Monmouth, NJ 07703 or emailed to CNRWGconus.army.mil. Since contact information can change, you may want to verify the currency of this address information using the ASSIST Online database at http:/assist.daps.dla.mil. Provided by IHSNot for ResaleNo reproduction or networking permitted witho

9、ut license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 iii CONTENTS PARAGRAPH PAGE FOREWORD.ii 1 SCOPE . 1 1.1 Purpose. 1 1.2 Scope. . 1 1.3 Application guidance. . 1 2 APPLICABLE DOCUMENTS 2 2.1 General. 2 2.2 Government documents. . 2 2.3 Specifications, standards, and handbooks. . 2 2.3.1 Other G

10、overnment documents, drawings, and publications. 3 2.3.2 North Atlantic Treaty Organization (NATO) Standardization Agreements (STANAG) documents, drawings, and publications. 3 2.4 Non-Government publications. . 3 2.5 Order of precedence. . 4 3 DEFINITIONS . 5 3.1 Definitions of terms. . 5 3.2 Abbrev

11、iations and acronyms. 8 4 GENERAL REQUIREMENTS . 13 4.1 Application layer users. 13 4.2 Interoperability. 13 4.3 Application layer services provided. 13 4.4 System standards and design. 13 5 SPECIFIC REQUIREMENTS 15 5.1 Application layer. . 15 5.2 Application Protocol Data Unit (PDU). . 15 5.3 Appli

12、cation header. 15 5.4 Application header formatting. . 22 5.5 Syntax. . 22 5.5.1 Field Presence Indicator (FPI). 22 5.5.2 Field Recurrence Indicator (FRI). . 22 5.5.3 Group Presence Indicator (GPI). . 22 5.5.4 Group Recurrence Indicator (GRI). . 22 5.5.5 End-of-literal field marker. . 23 5.5.6 Data-

13、field construction procedures. . 23 5.6 Application header fields. . 26 5.6.1 Version. 26 5.6.2 Data compression type. . 26 5.6.3 Originator, recipient, and information addressee fields. 27 5.6.4 User Message Format (UMF) field. . 27 5.6.5 Functional Area Designator (FAD) field. 31 5.6.6 Message Num

14、ber field. . 31 5.6.7 Message Subtype field. 31 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 iv 5.6.8 File Name. 31 CONTENTS PARAGRAPH PAGE 5.6.9 Message Size field. . 31 5.6.10 Operation Indicator field. 31 5.6.11 R

15、etransmit Indicator field. 32 5.6.12 Message Precedence field. . 32 5.6.13 Security Classification field. . 33 5.6.14 Control and Release Marking field. . 33 5.6.15 Originator Date-Time Group (DTG). 34 5.6.16 DTG Extension field. 35 5.6.17 Time Perishability DTG. . 35 5.6.18 Machine Acknowledge Requ

16、est Indicator field. . 35 5.6.19 Operator Acknowledge Request Indicator field. 35 5.6.20 Operator Reply Request Indicator field. 35 5.6.21 Message Acknowledgment DTG. 35 5.6.22 Receipt/Compliance (R/C) field. . 36 5.6.23 Cannot Comply (CANTCO) Reason field. 36 5.6.24 Cannot Process (CANTPRO) Reason

17、field. . 36 5.6.25 Reply Amplification field. . 36 5.6.26 Reference Message Data group. 37 5.6.27 Header Size field. . 37 5.6.28 Security Parameter Information (SPI). 37 5.6.29 Keying Material ID Length. 38 5.6.30 Keying Material ID. 38 5.6.31 Cryptographic Initialization Length. . 38 5.6.32 Cryptog

18、raphic Initialization. . 38 5.6.33 Key Token Length. . 38 5.6.34 Key Token. . 38 5.6.35 Authentication Data (A) Length. 38 5.6.36 Authentication Data (A). 38 5.6.37 Authentication Data (B) Length. . 38 5.6.38 Authentication Data (B). . 39 5.6.39 Signed acknowledge request indicator. 39 5.6.40 Messag

19、e Security Padding Length. 39 5.6.41 Message Security Padding. . 39 5.6.42 Group Size field. . 39 5.7 Application header formatting rules and construction procedures. . 39 5.7.1 Case and conditionality statement syntax. . 39 5.7.2 Cases and conditions for the application header. . 41 5.7.3 User data

20、. . 52 5.7.4 Message acknowledgments. 52 5.8 Processing factors. 53 5.8.1 Application process. . 53 5.8.2 Message formats. 53 5.8.3 Lower layer interactions. . 53 5.8.4 Application header padding. . 55 6 NOTES . 56 Provided by IHSNot for ResaleNo reproduction or networking permitted without license

21、from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 v 6.1 Subject term (key word) listing. 56 6.2 Issue of the DoD index of specifications and standards (DODISS). . 56 CONTENTS PARAGRAPH PAGE 6.3 Management of TCP connections. . 56 6.4 Application header initial settings. 57 6.5 Changes from previous issue.

22、 62 APPENDIX A APPLICATION HEADER FIELDS AND CODES FOR VMF 63 A.1 General. 63 A.1.1 Scope. . 63 A.1.2 Application. 63 A.2 Applicable documents. 63 A.3 Codeword tables. 63 A.3.1 Unit reference number codewords. 63 A.3.2 FAD codewords. . 63 A.3.3 Message Number codewords. 64 A.3.4 Message Subtype code

23、words. 64 A.3.4.1 MIL-STD-6017 message cases as message subtypes. . 64 A.3.5 CANTCO Reason codewords. . 65 A.3.6 CANTPRO Reason codewords. . 65 A.3.7 Data field construction procedures for VMF messages/user data. 67 APPENDIX B EXAMPLE OF APPLICATION LAYER PDU AND VMF MESSAGE CONSTRUCTION 68 B.1 Gene

24、ral. 68 B.1.1 Scope. . 68 B.1.2 Application. 68 B.2 Example application layer PDU construction. . 68 B.2.1 Application layer data exchange. 68 B.2.2 Example. 70 B.3 Example VMF message construction. . 76 B.3.1 VMF message data exchange. . 76 B.3.2 Example. 77 B.3.3 Example. 79 APPENDIX C SEGMENTATIO

25、N/REASSEMBLY PROTOCOL . 82 C.1 General. 82 C.1.1 Scope. . 82 C.1.2 Application. 82 C.1.3 Definitions. . 82 C.1.3.1 Definitions of terms. . 82 C.1.3.2 Summary of S/R acronyms, terms, explanations, and applications. . 83 C.1.4 Summary of S/R procedures. . 89 C.2 Applicable documents. 90 C.3 Overall op

26、eration. . 90 C.3.1 Maximum segment size (MSS). 91 C.3.1.1 MSS for IP datagram exchanges. 91 C.3.1.2 MSS for n-layer pass through exchanges. 91 C.3.1.3 MSS for Packet Mode exchanges. . 92 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-4

27、7001D w/CHANGE 1 vi C.3.2 Interface with peer-to-peer layers. . 92 C.3.2.1 UDP/IP Datagram exchanges. . 95 C.3.2.2 MIL-STD-188-220 n-layer pass through (NLP) exchanges. 95 CONTENTS PARAGRAPH PAGE C.3.3 S/R PDU format. . 96 C.3.3.1 Common S/R header. 96 C.3.3.2 Data segment. . 97 C.3.3.3 Partial Ackn

28、owledgment PDU. . 98 C.3.3.4 Complete Acknowledgment PDU. . 99 C.3.3.5 Abort Request PDU. . 99 C.3.3.6 Abort Confirm PDU. . 100 C.3.3.7 Acknowledgment Request. 100 C.3.4 Data segment acknowledgment schemes. 101 C.3.4.1 End of Data Transfer (EDT) Acknowledgment Required scheme. . 101 C.3.4.2 End of D

29、ata Transfer Acknowledgment Not Required scheme. . 101 C.3.5 S/R Basic procedures. . 102 C.3.5.1 S/R Basic Overview. . 102 C.3.5.2 S/R Basic Flow Control. . 104 C.3.5.3 S/R Basic timing parameters and variables. 105 C.3.5.4 Detailed S/R Basic Procedures 107 C.3.5.5 S/R Basic timers. 116 C.3.5.6 Basi

30、c Timer equations. . 118 C.3.5.7 Basic Initialization equations. . 119 C.3.6 S/R Enhanced procedures. 120 C.3.6.1 S/R Enhanced Overview. 120 C.3.6.2 Enhanced Flow Control. . 123 C.3.6.3 S/R Enhanced timing parameters and variables. . 125 C.3.6.4 Detailed S/R Enhanced Procedures . 131 C.3.6.5 S/R Enh

31、anced timers. . 137 C.3.6.6 Enhanced Timer equations. 147 C.3.6.7 Enhanced Initialization equations. 148 C.3.7 S/R Basic / S/R Enhanced Interoperability Notes and Considerations 150 C.3.8 Examples. . 150 APPENDIX D SECURITY EXTENSION PROTOCOL 179 D.1 General. 179 D.1.1 Scope. . 179 D.1.2 Application

32、. 179 D.2 Applicable documents. 179 D.3 Definitions. . 179 D.4 General requirements. . 179 D.4.1 SPI 0 authentication using SHA-1 and DSA/no encryption. 179 D.4.1.1 Message Security Group. 179 APPENDIX E DoD STANDARDIZED PROFILE IMPLEMENTATION CONFORMANCE STATEMENTS (DSPICS) REQUIREMENTS LIST (DPRL)

33、 FOR MIL-STD-2045-47001D 186 E.1 General. 186 E.1.1 Scope. . 188 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 vii E.1.2 Application. 188 E.2 Applicable documents. 188 E.3 Notation. 188 E.4 Implementation requirements

34、. 189 CONTENTS PARAGRAPH PAGE E.5 Detailed requirements. 190 APPENDIX F COMBAT NET RADIO PLATFORM - SYSTEM IMPLEMENTATION 282 F.1 General. 282 F.1.1 Scope. . 282 F.1.2 Application. 282 F.2 Applicable documents. 282 F.3 Definitions. . 282 F.4 General requirements. . 282 F.4.1 Reason for table. . 282

35、F.4.1.1 Process explanation. . 282 F.4.2 Table construction. . 282 F.4.2.1 Platform/System and version implementation codes (column 5). . 284 F.4.3 MIL-STD-2045-47001 Platform system implementation (example). 303 F.4.4 CNRWG website MIL-STD-2045-47001 platform system implementation spreadsheet examp

36、le. 306 TABLE . PAGE TABLE I. Application header 15 TABLE II. Version codes 26 TABLE III. Data compression type codes . 27 TABLE IV. UMF codes 28 TABLE V. Message Standard Version based on UMF codes 30 TABLE VI. Operation Indicator codes 31 TABLE VII. Message Precedence codes. 32 TABLE VIII. Securit

37、y Classification codes 34 TABLE IX. DTG codes 34 TABLE X. R/C codes 36 TABLE XI. Security Parameter Information type codes 37 TABLE XII. SPI typical field sizes. 37 TABLE XIII. Logical operator definitions. 40 TABLE XIV Case level minimum implementation. 51 TABLE XV Expected response minimum impleme

38、ntation 51 TABLE XVI Special consideration minimum implementation. 51 TABLE XVII. Port Numbers for PDUs related to the exchange of 47001 ALP 54 TABLE XVIII. Application header initial settings . 57 TABLE A-I. FAD codewords. 63 TABLE A-II MIL-STD-6017 message subtypes . 64 TABLE A-III. CANTCO Reason

39、codewords. 65 TABLE A-IV. CANTPRO Reason codes 65 TABLE B-I. Example construction of application layer PDU. 70 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 viii TABLE B-II. Example construction of fictitious VMF mess

40、age data . 78 TABLE B-III. Example of Future Use Groups 79 TABLE C-I. Summary of S/R acronyms, terms, explanations, and applications . 84 TABLE C-II. S/R and UDP Destination/Source Port field values for S/R PDUs sent via UDP/IP 95 CONTENTS TABLE . PAGE TABLE C-III. S/R Destination/Source Port and MI

41、L-STD-188-220 Intranet Message Type field values for S/R PDUs sent via MIL-STD-188-220 NLP in support of MIL-STD-2045-47001 ALP exchanges. . 96 TABLE C-IV. Types of S/R PDUs 97 TABLE C-V. Programmable S/R flow control parameters. 104 TABLE C-VI. Programmable S/R parameters 105 TABLE C-VII. Programma

42、ble S/R flow control parameters. 125 TABLE C-VIII. Programmable S/R parameters 127 TABLE C-IX. Example of construction of S/R PDU (Acknowledgment Request) . 151 TABLE D-I. Example construction of the SEP. 180 TABLE E-I. Pre-Application header requirements. 190 TABLE E-II. Application header requirem

43、ents . 198 TABLE E-III. Post application header receipt requirements . 220 TABLE E-IV. Cases. 220 TABLE E-V. Conditions. 225 TABLE E-VI. Expected response requirement 227 TABLE E-VII. Special considerations . 229 TABLE E-VIII. Segmentation/Reassembly Protocol requirements. 234 TABLE E-IX. Security E

44、xtension Protocol requirements 281 TABLE F-I. MIL-STD-2045-47001 PLATFORM SYSTEM IMPLEMENTATION (TEMPLATE) 285 TABLE F-II. MIL-STD-2045-47001 PLATFORM SYSTEM IMPLEMENTATION (EXAMPLE) 303 TABLE F-III. MIL-STD-2045-47001 PLATFORM SYSTEM IMPLEMENTATION . 306 FIGURE. PAGE FIGURE 1. Application PDU struc

45、ture. 15 FIGURE 2. Application protocol data field bit order (example) 24 FIGURE 3. System compatibility relationship examples. 26 FIGURE B-1. Application layer interaction with other communications layers 69 FIGURE B-2. Exchange of application layer PDU between communications layers 69 FIGURE B-3.

46、VMF message services interaction with other communications layers 77 FIGURE B-4. Exchange of message data between communications layers . 77 FIGURE C-1. Segmentation/Reassembly header 96 FIGURE C-2. Data segment. 98 FIGURE C-3. Partial acknowledgment 98 FIGURE C-4. Complete acknowledgment 99 FIGURE

47、C-5. Abort Request 100 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 ix FIGURE C-6. Abort Confirm. 100 FIGURE C-7. Acknowledgment Request PDU. 100 FIGURE C-8. S/R Example Scenario Symbol Key . 152 FIGURE C-9. S/R Exam

48、ple Scenario, Nominal . 154 FIGURE C-10. S/R Example Scenario, Missed Segments 158 FIGURE C-11. S/R Example Scenario, Multicast 166 CONTENTS FIGURE. PAGE FIGURE C-12, S/R Example Scenario, Temporarily Out of Range 168 FIGURE C-13, S/R Example Scenario, Permanently Out of Range 174 PARAGRAPH PAGE CONCLUDING MATERIAL 310 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2045-47001D w/CHANGE 1 1 1 SCOPE 1.1 Purpose. This military standard presents the minimum essential technical parameters in the form of a mandatory system