1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
|
<pre>Internet Engineering Task Force (IETF) A. Melnikov
Request for Comments: 6477 Isode Ltd
Category: Informational G. Lunt
ISSN: 2070-1721 SMHS Ltd
January 2012
<span class="h1">Registration of Military Message Handling System (MMHS)</span>
<span class="h1">Header Fields for Use in Internet Mail</span>
Abstract
A Military Message Handling System (MMHS) processes formal messages
ensuring release, distribution, security, and timely delivery across
national and international strategic and tactical networks. The MMHS
Elements of Service are defined as a set of extensions to the ITU-T
X.400 (1992) international standards and are specified in STANAG 4406
Edition 2 and ACP 123. This document specifies message header fields
and associated processing for <a href="./rfc5322">RFC 5322</a> (Internet Message Format) to
provide a comparable messaging service. In addition, this document
provides for a STANAG 4406 / Internet Email Gateway that supports
message conversion.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6477">http://www.rfc-editor.org/info/rfc6477</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
<span class="grey">Melnikov & Lunt Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Registration Templates ..........................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Header Field: MMHS-Exempted-Address ........................<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Header Field: MMHS-Extended-Authorisation-Info .............<a href="#page-5">5</a>
<a href="#section-3.3">3.3</a>. Header Field: MMHS-Subject-Indicator-Codes .................<a href="#page-6">6</a>
<a href="#section-3.4">3.4</a>. Header Field: MMHS-Handling-Instructions ...................<a href="#page-6">6</a>
<a href="#section-3.5">3.5</a>. Header Field: MMHS-Message-Instructions ....................<a href="#page-7">7</a>
<a href="#section-3.6">3.6</a>. Header Field: MMHS-Codress-Message-Indicator ...............<a href="#page-8">8</a>
<a href="#section-3.7">3.7</a>. Header Field: MMHS-Originator-Reference ....................<a href="#page-8">8</a>
<a href="#section-3.8">3.8</a>. Header Field: MMHS-Primary-Precedence ......................<a href="#page-9">9</a>
<a href="#section-3.9">3.9</a>. Header Field: MMHS-Copy-Precedence ........................<a href="#page-10">10</a>
<a href="#section-3.10">3.10</a>. Header Field: MMHS-Message-Type ..........................<a href="#page-10">10</a>
<a href="#section-3.11">3.11</a>. Header Field: MMHS-Other-Recipients-Indicator-To .........<a href="#page-11">11</a>
<a href="#section-3.12">3.12</a>. Header Field: MMHS-Other-Recipients-Indicator-CC .........<a href="#page-12">12</a>
<a href="#section-3.13">3.13</a>. Header Field: MMHS-Acp127-Message-Identifier .............<a href="#page-13">13</a>
<a href="#section-3.14">3.14</a>. Header Field: MMHS-Originator-PLAD .......................<a href="#page-13">13</a>
<a href="#section-4">4</a>. Formal Syntax ..................................................<a href="#page-14">14</a>
<a href="#section-5">5</a>. Service in Comparison to ACP 123 / STANAG 4406 .................<a href="#page-16">16</a>
<a href="#section-6">6</a>. Gatewaying with ACP 123 / STANAG 4406 ..........................<a href="#page-16">16</a>
<a href="#section-7">7</a>. Gatewaying with ACP 127 ........................................<a href="#page-18">18</a>
<a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-18">18</a>
<a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-18">18</a>
<a href="#section-10">10</a>. References ....................................................<a href="#page-19">19</a>
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-19">19</a>
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-19">19</a>
<a href="#appendix-A">Appendix A</a>. Acknowledgements ......................................<a href="#page-21">21</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC5322">RFC5322</a>] defines a protocol for the format of electronic messages
exchanged on the Internet. MMHS is a military specification defined
in ACP 123 [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>] (also specified in STANAG 4406 [<a href="#ref-STANAG-4406">STANAG-4406</a>]),
which defines a number of extensions to the basic X.400 (1992)
protocol for the services required by military messaging.
This document supports translating most of the Elements of Service
defined in ACP 123 [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>] to Internet message header fields (see
<a href="#section-5">Section 5</a> for more details). This specification is written to extend
the Mime Internet X.400 Enhanced Relay (MIXER) specification
<span class="grey">Melnikov & Lunt Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
[<a id="ref-RFC2156">RFC2156</a>] to enable inter-conversion in a MIXER gateway with the
X.400 Interpersonal Messaging System (IPMS) heading extensions
defined in ACP 123 / STANAG 4406, Annex A.
The document is aimed at the ability to represent MMHS messages as
<a href="./rfc5322">RFC 5322</a> messages. All <a href="./rfc5322">RFC 5322</a> header fields defined in this
document are prefixed with the string "MMHS-" to distinguish them
from any other header fields.
Unless stated otherwise, all header fields described in this document
are OPTIONAL in an Internet Message.
This document is structured as follows: <a href="#section-3">Section 3</a> and its subsections
formally define new Internet header fields and show some examples.
<a href="#section-4">Section 4</a> provides Augmented Backus-Naur Form (ABNF) syntax for them.
<a href="#section-5">Section 5</a> provides some background information about which features
of ACP 123 / STANAG 4406 were not implemented in this specification.
Subsequent sections talk about additional requirements for gatewaying
to/from ACP 123 / STANAG 4406 and ACP 127 [<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>] environments,
respectively.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
The formal syntax uses the ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] notation including the core
rules defined in <a href="./rfc5234#appendix-B">Appendix B of RFC 5234</a> [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Registration Templates</span>
Header field entries are summarized below in tabular form for
convenience of reference and presented in full in the following
subsections.
Any header field specified in this document MUST NOT appear more than
once in message headers.
<span class="grey">Melnikov & Lunt Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
+------------------------------------+----------+-------------------+
| Header name | Protocol | Reference |
+------------------------------------+----------+-------------------+
| MMHS-Exempted-Address | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.1 |
| | | and B.105 |
| MMHS-Extended-Authorisation-Info | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.2 |
| | | and B.106 |
| MMHS-Subject-Indicator-Codes | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.3 |
| | | and B.107 |
| MMHS-Handling-Instructions | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>][ACP123], |
| | | Appendices A1.4 |
| | | and B.108 |
| MMHS-Message-Instructions | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.5 |
| | | and B.109 |
| MMHS-Codress-Message-Indicator | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.6 |
| | | and B.110 |
| MMHS-Originator-Reference | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.7 |
| | | and B.111 |
| MMHS-Primary-Precedence | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.8 |
| | | and B.101 |
| MMHS-Copy-Precedence | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.9 |
| | | and B.102 |
| MMHS-Message-Type | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.10 |
| | | and B.103 |
| MMHS-Other-Recipients-Indicator-To | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.12 |
| | | and B.113 |
| MMHS-Other-Recipients-Indicator-CC | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.12 |
| | | and B.113 |
| MMHS-Acp127-Message-Identifier | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.14 |
| | | and B.116 |
| MMHS-Originator-PLAD | mail | [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], |
| | | Appendices A1.15 |
| | | and B.117 |
+------------------------------------+----------+-------------------+
<span class="grey">Melnikov & Lunt Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Header Field: MMHS-Exempted-Address</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Exempted-Address header field, by its presence, indicates
the addresses of members in an Address List (AL) that should not
receive the message. If this header field is absent from the
message, all members of an AL will be considered to be valid
recipients of the message.
Note: there is no guarantee that the exempted addresses will not
receive the message as the result of redirection, Distribution List
(DL) expansion, etc.
Example:
MMHS-Exempted-Address:
UK SHL CGT Samuals G <graham.samuals@shl.example.com>,
UK SHL Duty Officer <duty@shl.example.com>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Header Field: MMHS-Extended-Authorisation-Info</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]]
The MMHS-Extended-Authorisation-Info header field, by its presence,
indicates either the date and the time when the message was
officially released by the releasing officer or the date and time
when the message was initially submitted to a communication facility
for transmission.
This header field SHOULD always be present in an email message that
complies with this specification.
Example:
MMHS-Extended-Authorisation-Info:
Mon, 09 Aug 2010 15:27:40 +0100
The example above demonstrates use of folding white space (FWS
[<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]).
<span class="grey">Melnikov & Lunt Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Header Field: MMHS-Subject-Indicator-Codes</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
A Subject Indicator Code (SIC) is a mechanism for formally
identifying the topic of a message. SICs are nested codes that
provide information for message distribution after delivery to the
recipient organization. SICs are usually three letters or three
letters and digits, but may be up to eight characters long. Nations
and organizations using SICs usually maintain a central registry.
When present, an MMHS-Subject-Indicator-Codes header field contains
one or more SICs, which indicates distribution information to a
recipient or a recipient's User Agent. This information can be used
to perform automatic or manual local distribution of a message. If
the MMHS-Subject-Indicator-Codes header field is absent, then the
local distribution will be in accordance with the message handling
policy of the recipient's domain.
[<a id="ref-ACP123">ACP123</a>] specifies two optional components of the Distribution Code
Element of Service. The MMHS-Subject-Indicator-Codes header field
covers only the SIC code component of distribution codes.
Example:
MMHS-Subject-Indicator-Codes: SDM; KKZ ; BRL
The example above includes three SIC codes: "SDM" (GROUND/LAND
REQUIREMENTS), "KKZ" (HELICOPTER PUBLICATIONS/MANUALS), and "BRL"
(HILEX INCIDENTS).
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Header Field: MMHS-Handling-Instructions</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Handling-Instructions header field, by its presence,
indicates human-readable local handling instructions that require
some manual handling by a traffic operator. If this header field is
absent, the message will be considered as not requiring manual
handling by a traffic operator.
<span class="grey">Melnikov & Lunt Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
Handling instructions (also called "transmission instructions") are a
part of format line 4 as defined in ACP 127 [<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>] and concern the
sending of the message, e.g., that a particular system shall be used
for transfer of the message.
This header field is used to support interoperability with ACP 127
systems.
Example:
MMHS-Handling-Instructions: RXFPA ZOV MINDEF
The example above includes one ACP 131(F) handling instruction:
"RXFPA ZOV MINDEF". The "ZOV MINDEF" indicates that MINDEF rerouted
the message for some reason, and the correct routing is via RXFPA.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Header Field: MMHS-Message-Instructions</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Message-Instructions header field, by its presence,
indicates message instructions (also known as "remarks") accompanying
the message (e.g., similar to the operating signals specified in ACP
131 [<a href="#ref-ACP131" title=""Comms Instructions - Operating Signals"">ACP131</a>]). If this header field is absent, the message will be
considered received without message instructions.
The difference between handling instructions and message instructions
is that the former is only for manual handling by traffic operators,
while the latter also contains information of interest to the persons
reading the message.
Example:
MMHS-Message-Instructions: MINIMIZE CONSIDERED; NO DISTRIBUTION
The example above includes two message instructions defined by
ACP123(B) [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>]: "MINIMIZE CONSIDERED" indicating that the
originating user has considered the Minimize status of the recipients
and "NO DISTRIBUTION" indicating that the recipients should not
distribute the message further without the originating user's
approval.
<span class="grey">Melnikov & Lunt Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Header Field: MMHS-Codress-Message-Indicator</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Codress-Message-Indicator header field, by its presence,
indicates that the message is in Codress format. If this header
field is absent, the message will be considered received without the
Codress format.
A Codress message is one in which all addresses, i.e., the sender and
all recipients, are encrypted within the ACP 127 text (body)
[<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>]. The heading of any Codress message contains only the
minimum amount of information that will enable a receiving station to
deal properly and expeditiously with the particular transmission.
The general rules for the preparation and transmission of Codress
messages are given in ACP 121 [<a href="#ref-ACP121" title=""Comms Instructions - General"">ACP121</a>].
This header field is used only to support interoperability with ACP
127 systems.
Example:
MMHS-Codress-Message-Indicator: 23
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Header Field: MMHS-Originator-Reference</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Originator-Reference header field, by its presence,
indicates a user-defined reference called the "originator's number".
If this header field is absent, then the message will be considered
received without any user-defined reference.
The originator's number is used by the originating organizational
unit and is further qualified within national policy.
Note: trailing and leading spaces in an originator reference are not
allowed by syntax.
Example:
MMHS-Originator-Reference: IMSCOM-JIC-612-78
<span class="grey">Melnikov & Lunt Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Header Field: MMHS-Primary-Precedence</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Primary-Precedence header field, by its presence, indicates
the precedence level of the primary ("action") recipients. The
message originating domain MUST ensure that this header field is
always present if the message contains "To:" ("action") addresses.
The MMHS Primary Precedence Element of Service indicates the relative
order in which Military Messages are to be handled for primary
(action) recipients, i.e., a Military Message with a higher MMHS-
Primary-Precedence header field value SHOULD be handled before a
Military Message with a lower MMHS-Primary-Precedence header field
value.
The header field value is a non-negative integer, or one of the six
predefined case-insensitive labels: "deferred" (same as "0"),
"routine" (same as "1"), "priority" (same as "2"), "immediate" (same
as "3"), "flash" (same as "4"), or "override" (same as "5"),
optionally followed by a comment. Note that, according to ACP 123,
values in the range from 0 to 15 are reserved for NATO-defined
precedence levels, and values in the range from 16 to 31 are reserved
for national users.
Example 1:
MMHS-Primary-Precedence: 0 (Deferred)
Example 2:
MMHS-Primary-Precedence: FLASH
Example 3:
MMHS-Primary-Precedence: 7
<span class="grey">Melnikov & Lunt Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Header Field: MMHS-Copy-Precedence</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Copy-Precedence header field, by its presence, indicates the
precedence level of the copy ("information") recipients. The message
originating domain MUST ensure that this header field is always
present if the message contains "Cc:" or "Bcc:" ("information")
addresses.
The MMHS Copy Precedence Element of Service indicates the relative
order in which Military Messages are to be handled for copy
(information) recipients. i.e. a Military Message with higher MMHS-
Copy-Precedence header field value SHOULD be handled before a
Military Message with a lower MMHS-Copy-Precedence header field
value.
The header field value is a non-negative integer, or one of the 6
predefined case-insensitive labels: "deferred" (same as "0"),
"routine" (same as "1"), "priority" (same as "2"), "immediate" (same
as "3"), "flash" (same as "4"), or "override" (same as "5"),
optionally followed by a comment. Note that according to ACP 123,
values in the range from 0 to 15 are reserved for NATO-defined
precedence levels and values in the range from 16 to 31 are reserved
for national users.
Example 1:
MMHS-Copy-Precedence: 2 (priority)
Example 2:
MMHS-Copy-Precedence: Priority
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Header Field: MMHS-Message-Type</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Message-Type heading extension, by its presence, indicates
whether the message is to be considered as an exercise, an operation,
a project, or a drill. (Note that the list of types is extensible,
and other types can be specified using the numeric form, see below).
<span class="grey">Melnikov & Lunt Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
It may include an optional parameter specifying the name of the
exercise, operation, project, or drill. If this extension is absent,
the message will be considered to be of an undefined type.
The header field value is a non-negative integer, or one of the four
predefined case-insensitive labels: "exercise" (same as "0"),
"operation" (same as "1"), "project" (same as "2"), "drill" (same as
"3"). Note that according to ACP 123, values in the range from 0 to
127 are reserved for NATO-defined Message Type identifiers and values
in the range from 128 to 255 are not defined by NATO and may be used
nationally or bilaterally.
Example 1:
MMHS-Message-Type: 0(exercise); identifier="CANDLE FISH"
Example 2:
MMHS-Message-Type: 3
Example 3:
MMHS-Message-Type: 2 (projet)
Example 4:
MMHS-Message-Type: project
Note that some of the examples above demonstrate use of optional
comments. See <a href="#section-4">Section 4</a> for the exact syntax of this header field.
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. Header Field: MMHS-Other-Recipients-Indicator-To</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Other-Recipients-Indicator-To header field, by its presence,
indicates the names of primary ("action") recipients that are
intended to receive, or have received, the message via means other
than MMHS. Note that the absence of both this header field and the
MMHS-Other-Recipients-Indicator-CC header field (see <a href="#section-3.12">Section 3.12</a>)
does not guarantee that all recipients are within the MMHS.
This header field enables a recipient to determine all action
recipients of a Military Message. This header field is derived from
the Other Recipient Indicator Element of Service.
<span class="grey">Melnikov & Lunt Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
There are several reasons as to why a recipient of a Military Message
may be identified by this header:
1. The recipient is not part of the MMHS.
2. The path to the recipient through the MMHS may not be secure;
therefore, the originator has used alternative mechanisms to
distribute the Military Message.
3. The recipient was already in receipt of the Military Message
prior to the Military Message being inserted into the MMHS.
Example:
MMHS-Other-Recipients-Indicator-To: UK SHL COS; UK SHL IM
The example above includes names of two primary recipients that
received the message via means other than MMHS.
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. Header Field: MMHS-Other-Recipients-Indicator-CC</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Other-Recipients-Indicator-CC header field, by its presence,
indicates the names of copy ("information") recipients that are
intended to receive, or have received, the message via means other
than MMHS. Note that the absence of both this header field and the
MMHS-Other-Recipients-Indicator-To header field (see <a href="#section-3.11">Section 3.11</a>)
does not guarantee that all recipients are within the MMHS.
This header field enables a recipient to determine all copy
recipients of a Military Message. This header field is derived from
the Other Recipient Indicator Element of Service.
There are several reasons as to why a recipient of a Military Message
may be identified by this header:
1. The recipient is not part of the MMHS.
2. The path to the recipient through the MMHS may not be secure;
therefore, the originator has used alternative mechanisms to
distribute the Military Message.
3. The recipient was already in receipt of the Military Message
prior to it being inserted into the MMHS.
<span class="grey">Melnikov & Lunt Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
Example:
MMHS-Other-Recipients-Indicator-CC: UK SHL LEGAD
The example above includes 1 copy (information) recipient that
received the message via means other than MMHS.
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. Header Field: MMHS-Acp127-Message-Identifier</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Acp127-Message-Identifier header field, by its presence,
indicates an ACP 127 message identifier [<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>] for a message that
originated from an ACP 127 domain. If this extension is absent, then
the message did not encounter an ACP 127 domain.
The MMHS-Acp127-Message-Identifier contains the contents of ACP 127
format line 3, which consists of three space-separated fields: the
Calling Station (DERI), Station Serial Number (SSN), and Filing Time
(JFT) [<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>].
This header field is used only to support interoperability with ACP
127 systems, it should be treated as opaque by a pure MMHS system.
Example:
MMHS-Acp127-Message-Identifier: RPDLE 1234 0341215
<span class="h3"><a class="selflink" id="section-3.14" href="#section-3.14">3.14</a>. Header Field: MMHS-Originator-PLAD</span>
Applicable protocol: mail [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
Status: informational
Author/change controller: IESG (iesg@ietf.org) on behalf of the IETF
Specification document(s): [<a href="./rfc6477">RFC6477</a>]
The MMHS-Originator-PLAD (PLAD: Plain Language Address Designator)
header field, by its presence, indicates the plain language address
associated with an originator for cross-referencing purposes. If
this header field is absent, then the message will be considered not
to have an originator PLAD cross-reference between the MMHS and ACP
127 domains.
This header field is used only to support interoperability with ACP
127 systems.
<span class="grey">Melnikov & Lunt Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
This header field and the MMHS-Extended-Authorisation-Info header
field provide a cross-reference for message identification in both
ACP 127 and MMHS domains.
Example:
MMHS-Originator-PLAD: SACLANT
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Formal Syntax</span>
The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) as described in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]. Terms not defined here are
taken from [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>], [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>], and [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>].
NZ-DIGIT = %x31-39
; "1".."9"
nonneg-integer = "0" / (NZ-DIGIT *DIGIT)
military-string = 1*69( ps-char )
quoted-military-string = DQUOTE military-string DQUOTE
military-string-sequence = military-string
*( [FWS] ";" [FWS] military-string )
Exempted-Address = "MMHS-Exempted-Address:"
[FWS] address-list [FWS] CRLF
Extended-Authorisation-Info = "MMHS-Extended-Authorisation-Info:"
[FWS] date-time CRLF
Subject-Indicator-Codes = "MMHS-Subject-Indicator-Codes:"
[FWS] sic-sequence [FWS] CRLF
sic-sequence = sic *( [FWS] ";" [FWS] sic )
; ACP 123 specifies that the maximum number of
; SICs is 8. Use of more than 8 SICs is
; permitted, but additional SICs might not
; be transferred to ACP 123 system.
sic = 3*8( ps-char )
Handling-Instructions = "MMHS-Handling-Instructions:"
[FWS] military-string-sequence [FWS] CRLF
Message-Instructions = "MMHS-Message-Instructions:"
[FWS] military-string-sequence [FWS] CRLF
<span class="grey">Melnikov & Lunt Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
Codress-Message-Indicator = "MMHS-Codress-Message-Indicator:"
[FWS] nonneg-integer [FWS] CRLF
Originator-Reference = "MMHS-Originator-Reference:"
[FWS] military-string [FWS] CRLF
PrimaryPrecedence = "MMHS-Primary-Precedence:" [FWS] precedence CRLF
CopyPrecedence = "MMHS-Copy-Precedence:" [FWS] precedence CRLF
precedence = (nonneg-integer / std-precedence) [CFWS]
std-precedence = "deferred" / "routine" / "priority" /
"immediate" / "flash" / "override"
; deferred == 0
; routine == 1
; priority == 2
; immediate == 3
; flash == 4
; override == 5
MessageType = "MMHS-Message-Type:" [FWS] message-type [CFWS]
[";" [FWS] MessageTypeParam [FWS] ] CRLF
message-type = nonneg-integer / std-message-type
std-message-type = "exercise" / "operation" / "project" / "drill"
; exercise == 0
; operation == 1
; project == 2
; drill == 3
MessageTypeParam = "identifier" [FWS] "=" [FWS]
quoted-military-string
Designator = military-string
OtherRecipIndicatorPrimary = "MMHS-Other-Recipients-Indicator-To:"
[FWS] Designator *([FWS] ";" [FWS] Designator)
[FWS] CRLF
OtherRecipIndicatorCopy = "MMHS-Other-Recipients-Indicator-CC:"
[FWS] Designator *([FWS] ";" [FWS] Designator)
[FWS] CRLF
Acp127MessageIdentifier = "MMHS-Acp127-Message-Identifier:"
[FWS] military-string [FWS] CRLF
<span class="grey">Melnikov & Lunt Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
OriginatorPLAD = "MMHS-Originator-PLAD:" [FWS] military-string [FWS]
CRLF
address-list = <Defined in <a href="./rfc5322">RFC 5322</a>>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Service in Comparison to ACP 123 / STANAG 4406</span>
The service specified in this document is a subset of the
functionality set out in Annex A1 "Military Heading Extensions" of
[<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>]. The majority of this functionality is supported in this
document. A few capabilities have been left out, which would have
significantly increased the complexity of this specification.
For Distribution Codes (A.1.3) only Subject Indicator Codes are
supported and Distribution Extensions are omitted. Authors of this
document believe that distribution extensions are not widely used.
Address List Indication (A.1.11) is not supported. This complex
extension is deprecated in [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>].
Pilot Forwarding Information (A.1.13) is not supported.
Security Information Labels (A.1.16) is not supported. This
extension is deprecated in favor of Annex A of [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>], which uses
Enhanced Security Services (ESS) Labels [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>] that can be
supported in a directly compatible manner in S/MIME [<a href="./rfc5751" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification"">RFC5751</a>].
ACP 127 Notification Requests (see Annex A.2.1 of [ACP123) and
Responses (see Annex A.3.1 of [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>]) are not supported. These
extensions are used to request and return notifications from ACP 127
gateways, and are not relevant to an SMTP gateway.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Gatewaying with ACP 123 / STANAG 4406</span>
The header fields defined in this specification are designed to be
mapped with ACP 123 Annex A1 heading extensions as part of a MIXER
mapping according to [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>]. The syntax of these headings is
defined such that mapping is mechanical. OR Names SHOULD be mapped
with Internet Email addresses according to [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>].
This section summarizes how a gateway between [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>] and [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]
conformant to this specification operates.
If an incoming X.400 message is encoded as P772, [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>] header
fields MUST be generated according to this specification for all ACP
123 heading extensions where an equivalent header is defined in this
specification. For the three heading extensions where no mapping is
defined, the heading extension MAY be discarded or mapped in a
<span class="grey">Melnikov & Lunt Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
proprietary manner. If a Distribution Extension is encoded, this MAY
be discarded or represented as a comment (<CFWS>). The whole message
MAY be signed according to [<a href="./rfc5652" title=""Cryptographic Message Syntax (CMS)"">RFC5652</a>]. These rules also apply to
heading extensions in forwarded messages. MM-Message MUST be treated
as a forwarded message for the purposes of MIXER mapping. If an ACP
127 Notification Request is present, this MAY be discarded or
represented as a comment (<CFWS>).
Incoming X.400 notifications are encoded according to [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>]. If
an ACP 127 Notification Response is present, this MAY be discarded or
mapped in a proprietary manner.
If an incoming SMTP message contains any of the header fields defined
in this specification, the outgoing X.400 message MUST be encoded as
P772. The outgoing message MAY be encoded as P772 for other reasons,
for instance, policy or characteristics such as the message
containing a military body part. The X.400 message might be signed
according to ACP 123 Annex B [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>] or STANAG 4406 Annex G
[<a href="#ref-STANAG-4406">STANAG-4406</a>]. message/rfc822 body parts included in the message
SHOULD be mapped to MM-Message and the heading mapping rules applied.
Generated P772 messages SHOULD follow the following rules, generating
heading extensions if needed.
a. Extended Authorization is required. If the MMHS-Extended-
Authorization-Info header field is absent, then the default value
is taken from the Date header field.
b. Primary Precedence is required if the To header field is present.
If the MMHS-Primary-Precedence header field is absent, the
message need not be considered a Military Message and can be
handled according to a local policy.
c. Copy Precedence is required if the Cc header field is present and
there is an MMHS-Copy-Precedence header field that is different
from the MMHS-Primary-Precedence header field.
d. For Message-ID fields, ACP 123 applies additional constraints
over X.400, leading to the following rules in addition to
[<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>], which SHOULD be followed by a gateway following this
specification.
1. The local identifier MUST be at least 15 characters long. If
the [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>] generated value is shorter than this, then it
is padded with spaces to 15 characters. This value will
correctly reverse map.
<span class="grey">Melnikov & Lunt Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
2. The OR Address part is required, and it is not usually
generated by an [<a href="./rfc2156" title=""MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME"">RFC2156</a>] mapping. It is mandatory in ACP
123. The gateway SHOULD generate an OR Address in a manner
that can be reverse mapped. It MAY use the OR Address to
encode long message ids that cannot be encoded in the local
identifier.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Gatewaying with ACP 127</span>
The header fields defined in this specification include fields to
carry Elements of Service specific to ACP 127 [<a href="#ref-ACP127" title=""Communication Instructions - Tape Relay Procedures"">ACP127</a>]. This
specification does not define a mapping of these header fields to ACP
127. In the absence of this mapping, it is recommended that these
headings be mapped to ACP 123 and hence into ACP 127 following the
Annex D (Gateway Translation) of [<a href="#ref-STANAG-4406">STANAG-4406</a>].
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
IANA has added the list of header fields specified in subsections of
<a href="#section-3">Section 3</a> to the "Permanent Message Header Field Names" registry
defined by "Registration Procedures for Message Header Fields"
[<a href="./rfc3864" title=""Registration Procedures for Message Header Fields"">RFC3864</a>].
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
Annex B of [<a href="#ref-ACP123" title=""Common Messaging Strategy and Procedures"">ACP123</a>] describes how MMHS messages can be protected in
an X.400 environment. Similar protection can be provided using
S/MIME [<a href="./rfc5751" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification"">RFC5751</a>] and/or DKIM [<a href="./rfc6376" title=""DomainKeys Identified Mail (DKIM) Signatures"">RFC6376</a>]. In particular, DKIM can be
used to protect against alteration, deletion, or insertion of header
fields specified in this document that can affect disposition and
quality of service applied to processing of the protected Internet
message by receiving gateways/endpoints that support this
specification. (Note that most of the header fields defined in this
document might affect processing of the message by the receiving
gateway/end system, MMHS-Subject-Indicator-Codes and MMHS-Primary-
Precedence/MMHS-Copy-Precedence header fields being the most
important examples. For example, alteration of the MMHS-Primary-
Precedence header field value might affect processing speed of the
message by the recipient Message Transfer Agent (MTA).)
When the original message header fields are digitally signed, the act
of gatewaying messages with such header fields to/from an Internet
environment from/to an ACP 123 environment breaks digital signatures.
The gateway can sign the translated message itself (e.g., with DKIM),
but a message recipient would be unable to verify that the message
was generated by the original sender.
<span class="grey">Melnikov & Lunt Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-ACP123">ACP123</a>] CCEB, "Common Messaging Strategy and Procedures", ACP 123
(B), May 2009, <a href="http://jcs.dtic.mil/j6/cceb/acps/acp123/">http://jcs.dtic.mil/j6/cceb/acps/acp123/</a>.
[<a id="ref-ACP127">ACP127</a>] CCEB, "Communication Instructions - Tape Relay
Procedures", ACP 127 (G), November 1988,
<a href="http://jcs.dtic.mil/j6/cceb/acps/acp127/">http://jcs.dtic.mil/j6/cceb/acps/acp127/</a>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2156">RFC2156</a>] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay):
Mapping between X.400 and <a href="./rfc822">RFC 822</a>/MIME", <a href="./rfc2156">RFC 2156</a>,
January 1998.
[<a id="ref-RFC3864">RFC3864</a>] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Procedures for Message Header Fields", <a href="https://www.rfc-editor.org/bcp/bcp90">BCP 90</a>, <a href="./rfc3864">RFC 3864</a>,
September 2004.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January
2008.
[<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
October 2008.
[<a id="ref-RFC5652">RFC5652</a>] Housley, R., "Cryptographic Message Syntax (CMS)", STD
70, <a href="./rfc5652">RFC 5652</a>, September 2009.
[<a id="ref-RFC6376">RFC6376</a>] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed.,
"DomainKeys Identified Mail (DKIM) Signatures", <a href="./rfc6376">RFC 6376</a>,
September 2011.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-ACP121">ACP121</a>] CCEB, "Comms Instructions - General", ACP 121 (I),
October 2010, <a href="http://jcs.dtic.mil/j6/cceb/acps/acp121/">http://jcs.dtic.mil/j6/cceb/acps/acp121/</a>.
[<a id="ref-ACP131">ACP131</a>] CCEB, "Comms Instructions - Operating Signals", ACP 131
(F), April 2009,
<a href="http://jcs.dtic.mil/j6/cceb/acps/acp131/">http://jcs.dtic.mil/j6/cceb/acps/acp131/</a>.
[<a id="ref-RFC2634">RFC2634</a>] Hoffman, P., Ed., "Enhanced Security Services for
S/MIME", <a href="./rfc2634">RFC 2634</a>, June 1999.
<span class="grey">Melnikov & Lunt Informational [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
[<a id="ref-RFC5751">RFC5751</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
Mail Extensions (S/MIME) Version 3.2 Message
Specification", <a href="./rfc5751">RFC 5751</a>, January 2010.
[<a id="ref-STANAG-4406">STANAG-4406</a>]
NATO, "STANAG 4406 Edition 2: Military Message Handling
System", STANAG 4406, March 2005.
<span class="grey">Melnikov & Lunt Informational [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc6477">RFC 6477</a> MMHS Header Fields January 2012</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgements</span>
This document copies a lot of text from the "Mapping between X.400
P772 and <a href="./rfc822">RFC-822</a>" by Julian Onions and Graeme Lunt and STANAG 4406
(2nd Edition). So the authors of this document would like to
acknowledge contributions made by the authors of these documents.
Many thanks for reviews and text provided by Steve Kille, Alan Ross,
David Wilson, James Usmar, Kathy Nuckles, Andy Trayler, Ken Carlberg,
Chris Bonatti, Oeyvind Jonsson, Mykyta Yevstifeyev, Sean Turner,
Stephen Farrell, Adrian Farrel, and Peter Saint-Andre.
Authors' Addresses
Alexey Melnikov
Isode Ltd
5 Castle Business Village
36 Station Road
Hampton, Middlesex, TW12 2BX
UK
EMail: Alexey.Melnikov@isode.com
Graeme Lunt
SMHS Ltd
Bescar Moss Farm
Bescar Lane
Ormskirk L40 9QN
UK
EMail: graeme.lunt@smhs.co.uk
Melnikov & Lunt Informational [Page 21]
</pre>
|
