| 1 |
<pre>Network Working Group E. Levinson |
| 2 |
Request for Comments: 1895 Accurate Info. Sys., Inc. |
| 3 |
Category: Informational February 1996 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">The Application/CALS-1840 Content-type</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This memorandum provides guidelines for using the United States |
| 17 |
Department of Defense Military Standard MIL-STD-1840, "Automated |
| 18 |
Interchange of Technical Information," with the Internet electronic |
| 19 |
mail standards, <a href="./rfc822">RFC 822</a> and <a href="./rfc1521">RFC 1521</a>. Electronic mail provides a |
| 20 |
more convenient mechanism that delivery via physical media for |
| 21 |
certain types and quantities of data. Software already exists to |
| 22 |
support data exchanges based on MIL-STD-1840 and it can continue to |
| 23 |
be used in conjunction with electronic mail exchanges defined in this |
| 24 |
document. This document defines a new media type and a MIME message |
| 25 |
structure for exchanging data in conformance with MIL-STD-1840. |
| 26 |
|
| 27 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 28 |
|
| 29 |
The United States Department of Defense (DOD) has defined a standard, |
| 30 |
MIL-STD-1840 [<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>], for the exchange of digital data. Most |
| 31 |
applications of that standard use 9-track tape as the transport |
| 32 |
medium. The Application/CALS-1840 media-type is proposed to |
| 33 |
facilitate such exchanges using the Multipurpose Internet Mail |
| 34 |
Extensions [<a href="#ref-MIME" title=""MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies"">MIME</a>] and network based transport media, i.e. electronic |
| 35 |
mail [<a href="#ref-822" title=""Standard for the Format of ARPA Internet Text Messages"">822</a>]. |
| 36 |
|
| 37 |
This memo has been reviewed and authorized by the Continuous |
| 38 |
Acquistion and Life-cycle Support (CALS) Industry Steering Group |
| 39 |
(ISG). CALS is a US DOD initiative for the use and exchange of |
| 40 |
digital data. The Industry Steering Group, which consists of members |
| 41 |
drawn from government and industry, guides the development of CALS |
| 42 |
standards such as [<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>]. |
| 43 |
|
| 44 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definition</span> |
| 45 |
|
| 46 |
An [<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>] exchange consists of a set of files with well defined file |
| 47 |
names (see below). Each set consists of a declaration file and one |
| 48 |
or more data files. The data files, in turn, consist of header |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Levinson Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1895">RFC 1895</a> CALS-1840 February 1996</span> |
| 55 |
|
| 56 |
|
| 57 |
records immediately followed by the data. The data itself may be |
| 58 |
formatted in accordance with a published specification or a |
| 59 |
contractual agreement. |
| 60 |
|
| 61 |
MIL-STD-1840 encodes the file's data type in the file name. |
| 62 |
|
| 63 |
It might seem appropriate to transform the 1840 headers into MIME |
| 64 |
headers and use the appropriate media type, essentially transforming |
| 65 |
the 1840 files into MIME body parts. There are three reasons for not |
| 66 |
doing that. First, not all of the "types" used in [<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>] are |
| 67 |
registered MIME types. Second, there exists an installed base of |
| 68 |
software capable of reading the 1840 formatted files and processing |
| 69 |
the data appropriately. Finally the three existing revisions to the |
| 70 |
standard have maintained the same file structure. Consequently, a |
| 71 |
processor for the data may be able to handle any one of the |
| 72 |
standard's revisions. Thus, a single Application/CALS-1840 is being |
| 73 |
proposed and its body part body contains headers and data in the |
| 74 |
[<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>] format. |
| 75 |
|
| 76 |
A set of related files constitutes a "transfer unit" in 1840 and each |
| 77 |
transfer unit shall correspond to a Multipart/Mixed MIME entity. |
| 78 |
Included in each transfer unit is a declaration file which shall be |
| 79 |
the first body part in the Multipart/Mixed entity. Several transfer |
| 80 |
units may be included in a single MIME message. |
| 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 |
<span class="grey">Levinson Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1895">RFC 1895</a> CALS-1840 February 1996</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Registration Information</span> |
| 114 |
|
| 115 |
The following form is copied from <a href="./rfc1590#appendix-A">RFC 1590, Appendix A</a> for the |
| 116 |
purpose of registering this media-type. |
| 117 |
|
| 118 |
To: [email protected] |
| 119 |
Subject: Registration of new Media Type content-type/subtype |
| 120 |
|
| 121 |
Media Type name: Application |
| 122 |
Media subtype name: CALS-1840 |
| 123 |
Required parameters: filename, version |
| 124 |
Optional parameters: None |
| 125 |
Encoding considerations: Any valid MIME encodings my be used |
| 126 |
Security considerations: Depends solely on the referenced type |
| 127 |
Published specification: This document |
| 128 |
Person & email address |
| 129 |
to contact for further |
| 130 |
information: Alan Peltzman <[email protected]> |
| 131 |
+1 (703) 735-3568 |
| 132 |
Defense Information Systems Agency |
| 133 |
Center for Standards |
| 134 |
Code JIEO/JEBEB |
| 135 |
10701 Parkridge Blvd |
| 136 |
Reston, VA 22091-4398 |
| 137 |
|
| 138 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. The Filename Parameter</span> |
| 139 |
|
| 140 |
The filename parameter gives the transfer unit filename as defined by |
| 141 |
[<a href="#ref-1840" title=""Automated Interchange of Technical Information"">1840</a>]. The parameter's value, called <1840-name>, has the syntax |
| 142 |
given by the grammer below. |
| 143 |
|
| 144 |
1840-name := "D" 1840-tuseq [ 1840-type 1840-dfseq ] |
| 145 |
1840-type := letter ; limited to the set defined in |
| 146 |
; the appropriate version of |
| 147 |
; [1840, Table III] |
| 148 |
1840-tuseq := 1840-seq |
| 149 |
1840-dfseq := 1840-seq |
| 150 |
1840-seq := alphnum alphnum alphnum |
| 151 |
alphanum := letter / digit |
| 152 |
letter := "A" / "B" / "C" / "D" / "E" / "F" / "G" / |
| 153 |
"H" / "I" / "J" / "K" / "L" / "M" / "N" / |
| 154 |
"O" / "P" / "Q" / "R" / "S" / "T" / "U" / |
| 155 |
"V" / "W" / "X" / "Y" / "Z" |
| 156 |
digit := "0" / "1" / "2" / "3" / "4" / "5" / |
| 157 |
"6" / "7" / "8" / "9" / |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Levinson Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1895">RFC 1895</a> CALS-1840 February 1996</span> |
| 167 |
|
| 168 |
|
| 169 |
All Application/CALS-1840 body parts in a single Multipart/Mixed MIME |
| 170 |
entity shall have the same <1840-tuseq>. Within a single message all |
| 171 |
filename values shall be unique. |
| 172 |
|
| 173 |
Notes: 1) Tuseq and dfseq correspond to transfer unit sequence number |
| 174 |
and data file sequence number respectively. 2) The filename for a |
| 175 |
declaration file has the form "D" 1840-tuseq and for data files, the |
| 176 |
form "D" 1840-tuseq <letter> 1840-dfseq. |
| 177 |
|
| 178 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. The Version Parameter</span> |
| 179 |
|
| 180 |
The specversion parameter's value shall indicate the particular |
| 181 |
version of MIL-STD-1840 to which the data conforms. Valid values |
| 182 |
are: |
| 183 |
|
| 184 |
MIL-STD-1840C, 0, 199XXXXX |
| 185 |
MIL-STD-1840B, 0, 19921103 |
| 186 |
MIL-STD-1840A, 0, 19871222 |
| 187 |
|
| 188 |
Notes: (1) The value "199XXXXX" is to be replaced with the actual |
| 189 |
issue date for MIL-STD-1840C. (2) The embedded blanks in the above |
| 190 |
strings are required, hence the value must be enclosed in quote marks |
| 191 |
("). |
| 192 |
|
| 193 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Example</span> |
| 194 |
|
| 195 |
In the example below a single transfer unit is provided. It consists |
| 196 |
of three data files, the declaration, a contract defined file and an |
| 197 |
IGES file. The headers and data are in accordance with MIL-STD- |
| 198 |
1840B. The content-transfer-encoding perserves the data file's fixed |
| 199 |
record length. |
| 200 |
|
| 201 |
To: [email protected] |
| 202 |
From: [email protected] |
| 203 |
Date: Fri, 03 Nov 1995 18:23:10 -0500 |
| 204 |
MIME-Version: 1.0 |
| 205 |
Content-Type: Multipart/Mixed; |
| 206 |
Boundary="DISA CFS - SFC ASID" |
| 207 |
|
| 208 |
--DISA CFS - SFC ASID |
| 209 |
Content-Type: Application/CALS-1840; filename=D001; |
| 210 |
version="MIL-STD-1840B, 0, 19921103" |
| 211 |
Content-Transfer-Encoding: Base64 |
| 212 |
|
| 213 |
[Declaration File] |
| 214 |
--DISA CFS - SFC ASID |
| 215 |
Content-Type: Application/CALS-1840; filename=D001A001; |
| 216 |
version="MIL-STD-1840B, 0, 19921103" |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Levinson Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1895">RFC 1895</a> CALS-1840 February 1996</span> |
| 223 |
|
| 224 |
|
| 225 |
Content-Transfer-Encoding: Base64 |
| 226 |
|
| 227 |
[Data File -- Contract Defined including headers] |
| 228 |
--DISA CFS - SFC ASID |
| 229 |
Content-Type: Application/CALS-1840; filename=D001Q001; |
| 230 |
version="MIL-STD-1840B, 0, 19921103" |
| 231 |
Content-Transfer-Encoding: Base64 |
| 232 |
|
| 233 |
[Data File -- Raster including 1840 headers] |
| 234 |
--DISA CFS - SFC ASID-- |
| 235 |
|
| 236 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 237 |
|
| 238 |
None of the body parts, as constitued, represent executable data. |
| 239 |
When the 1840 file format is processed the resultant data may be |
| 240 |
executable. Processing will be under the control of the process |
| 241 |
associated with Application/CALS-1840. |
| 242 |
|
| 243 |
Classified information or other information that cannot be disclosed |
| 244 |
except to authorized personnel should not be sent via the Internet |
| 245 |
without using appropriate privacy enhancements, [<a href="#ref-PEM" title=""Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures"">PEM</a>], [<a href="#ref-MOSS" title=""MIME Object Security Services"">MOSS</a>], or |
| 246 |
other privacy mechanism. |
| 247 |
|
| 248 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span> |
| 249 |
|
| 250 |
The author acknowledges the encouragement of Alan Peltzman, US DOD, |
| 251 |
DISA, and the suggestions of Richard Klobuchar, SAIC. |
| 252 |
|
| 253 |
This work was supported under U.S. Dept. of the Army, Contract |
| 254 |
DAAB07-93-D-T001 and prepared under the direction of the MIL-STD-1840 |
| 255 |
Revision C Review Team. |
| 256 |
|
| 257 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span> |
| 258 |
|
| 259 |
[<a id="ref-1840">1840</a>] MIL-STD-1840B, "Automated Interchange of Technical |
| 260 |
Information", US Department of Defense, 3 November 1992. |
| 261 |
|
| 262 |
[<a id="ref-822">822</a>] Crocker, D., "Standard for the Format of ARPA Internet |
| 263 |
Text Messages", STD 11, <a href="./rfc822">RFC 822</a>, UDEL, August 1982. |
| 264 |
|
| 265 |
[<a id="ref-MIME">MIME</a>] Borenstein, N. and N. Freed, "MIME (Multipurpose Internet |
| 266 |
Mail Extensions): Mechanisms for Specifying and |
| 267 |
Describing the Format of Internet Message Bodies", <a href="./rfc1521">RFC</a> |
| 268 |
<a href="./rfc1521">1521</a>, Bellcore and Innosoft, September 1993. |
| 269 |
|
| 270 |
[<a id="ref-MOSS">MOSS</a>] Crocker, S., Freed, N., Galvin, J., and S. Murphy, "MIME |
| 271 |
Object Security Services", <a href="./rfc1848">RFC 1848</a>, Cybercash, Innosoft, |
| 272 |
TIS, October 1995. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Levinson Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1895">RFC 1895</a> CALS-1840 February 1996</span> |
| 279 |
|
| 280 |
|
| 281 |
[<a id="ref-PEM">PEM</a>] Linn, J., "Privacy Enhancement for Internet Electronic Mail: |
| 282 |
Part I: Message Encryption and Authentication Procedures", |
| 283 |
<a href="./rfc1421">RFC 1421</a>, IAB IRTF PSRG, IETF PEM WG, February 1993. |
| 284 |
|
| 285 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span> |
| 286 |
|
| 287 |
Edward Levinson |
| 288 |
Accurate Information Systems, Inc. |
| 289 |
2 Industrial Way |
| 290 |
Eatontown, NJ 07724-2265 |
| 291 |
USA |
| 292 |
|
| 293 |
Phone: +1 908 389 5550 |
| 294 |
EMail: [email protected] |
| 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 |
Levinson Informational [Page 6] |
| 333 |
</pre> |