[media-types] application/nits+xml registration request
Ryen Krusinga <[email protected]> Thu, 16 Jul 2026 20:02:38 +0000
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <PH0PR04MB74789321451F2AA9D286C1E2ECC72@PH0PR04MB7478.namprd04.prod.outlook.com> |
--===============6558399740936411847== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_PH0PR04MB74789321451F2AA9D286C1E2ECC72PH0PR04MB7478namp_" --_000_PH0PR04MB74789321451F2AA9D286C1E2ECC72PH0PR04MB7478namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello, I intend to register the standards media type application/nits+xml on behal= f of the NATO STANAG 4676 Custodial Support Team (CST). STANAG 4676 is the = NATO Intelligence, Surveillance, and Reconnaissance (ISR) Track Standard (N= ITS). This is a public standard that specifies a format for representing an= d transmitting ISR track data - sequences of points indicating object traje= ctories. Application form for preliminary review: ---- Name: Ryen Krusinga (submitting on behalf of Rob Downs, STANAG 4676 Custodi= an) Email: [email protected] Type name: application Subtype Name: nits+xml (standards tree, no prefix) Required Parameters: N/A Optional Parameters: "charset" This parameter has identical semantics to the charset parameter= of the "application/xml" media type as specified in RFC 7303. "sv" or "schemaversion" This parameter=92s value indicates the edition of= NITS (NATO ISR Track Standard) to which the data is conformant. Legal valu= es are: "B" Data is conformant to NITS Edition B, defined in AEDP-12 Edition B "C" Data is conformant to NITS Edition C, defined in AEDP-4676 Edition= C If the "sv" and "schemaversion" parameters are absent, then the data consum= er determines the version by examining file content. Edition C is largely b= ackwards compatible with Edition B, so consumers should not reject data whe= n the version is not included within the media type. "profile" This parameter=92s value is a comma-separated list of named pro= files of NITS to which the data is conformant. The file includes values of = the parameter as values of the "profile" attribute within the "nitsRoot" ro= ot element of the XML data. Encoding Considerations: "Binary" =96 based on the recommendation in the application: "If the format is based on JSON or XML, "binary" should generally be select= ed due to the possibility that lines could be longer than 998 octets." Same as encoding considerations of application/xml as specified in RFC 7303= . Security Considerations: Same as general security considerations for application/xml as specified in= section 10 of RFC 3023. While AEDP-4676.2 Ed. C will be the published schema that defines the XML e= ncoding of NITS for STANAG 4676 Ed. 3, the schema supports the XSD 1.1 open= content model and allows additional content to be inserted anywhere in the= file. While the standard content defined by NITS itself includes no execut= able content, it is possible for a data provider to insert additional XML e= ntities into the file that do contain executable content. In addition to en= suring the data is valid and well-formed XML, data consumers MUST take care= to not blindly process any unexpected data found in the file and should on= ly parse or display content using mechanisms that prevent malformed or mali= cious data attacking the consumer. In many applications, access to the NITS data is restricted for privacy and= control issues. NITS itself defines no mechanisms to restrict access to th= e data. As such, data providers MUST implement their own access methods to = prevent unauthorized access to the data, and the transmission of the NITS d= ata MUST be protected using standard encryption methods such as SSL/TLS. NI= TS files may include elements specifying confidentiality and how access to = the data is restricted or permitted, encoded in the XML using ADatP-4774, t= he NATO Confidentiality Metadata Label Syntax. Consumers that discover ADat= P-4774 markings within NITS data MUST not provide further access to the dat= a beyond what is permitted by those markings. Consumers who discover ADatP-= 4774 markings but do not recognize the specific markings MUST not provide a= ny further access to the received data until permission to access the data = can be authoritatively confirmed. Interoperability Considerations: Same as the interoperability considerations specified in RFC 7303. If both "sv" and "schemaversion" are specified, then the value of "schemave= rsion" MUST be ignored. Structuring and validating the NITS data requires the XML schema files for = the corresponding STANAG edition, Ed. 2 or Ed. 3. For Ed. 3, the schema fil= es will be published as AEDP-4676.2 Ed. C in late 2026/early 2027 and are c= urrently available upon request from the STANAG 4676 custodial support team= (CST); for Ed. 2, they are only available by contacting the CST. Published Specification: STANAG 4676 Ed. 2 AEDP-12 Ed. B: "NATO ISR Tracking Standard, Edition B" Available via the NSO NSDD<https://nso.nato.int/nso/nsdd/main/standards> a= t https://nso.nato.int/nso/nsdd/main/standards STANAG 4676 Ed. 3 AEDP-4676 Ed. C: "NATO ISR Track Standard, Edition C" AEDP-4676.1 Ed. C: "NATO ISR Track Standard Implementation Guide, Edition= C" AEDP-4676.2 Ed. C: "NATO ISR Track Standard XML Schema Definition, Editio= n C" Available by contacting the STANAG 4676 Custodian; currently under review a= nd expected to be published in late 2026/early 2027 via the NSO NSDD<https:= //nso.nato.int/nso/nsdd/main/standards> Application Usage: The NATO Intelligence, Surveillance and Reconnaissance (ISR) Track Standard= (NITS) defines a standard format for object track data (data on the trajec= tories of real-world moving objects, such as boats, trucks or airplanes). N= ITS files are intended for use by applications that generate, analyze, and = synthesize object track data for intelligence, surveillance, and reconnaiss= ance purposes. The typical use case is for intelligence or defense systems = communicating target information for the purposes of intelligence, analysis= , and battlefield responsiveness. However, this is not an exhaustive list o= f possible uses, and there is nothing in the standard that prevents use in = other environments (e.g., commercial truck fleet tracking, parents tracking= the movement of their children=92s electronic devices, tracking checked ba= ggage through an airport baggage handling system, etc.) Fragment Identifier Considerations Same as fragment identifier considerations as specified in RFC 7303. In addition, identifiers can be assigned to many of the elements in NITS, e= ither using UUIDs (the "uid" element) or simple integers with local scope (= the "lid" element). The uid values can be used to refer to a fragment of on= e NITS file from another file; this mechanism is heavily relied on to avoid= repeating static data across a large sequence of NITS files. While the lid= values alone cannot be used to refer to an element from outside the file, = a local scope identifier (a UUID) can be assigned within each file, allowin= g the combination of local scope identifier and the simple local integer id= entifier to be used to refer to fragments of a NITS file from external reso= urces. Restrictions on Usage: N/A Provisional Registrations: No Additional Information: * Deprecated alias names: N/A * Magic Numbers: Same as magic numbers specified by RFC 7303 * File extensions: .nits * Macintosh File Type Codes: N/A * Object Identifiers or OIDs: N/A Intended Usage: COMMON Other info and comments: N/A Contact Person: * Name: Rob Downs * Email: [email protected] * Author/Change Controller: NATO STANAG 4676 CST Ryen Krusinga Imagery Standards Developer | Compass, Inc. STANAG 4676 Technical Editor [email protected] --_000_PH0PR04MB74789321451F2AA9D286C1E2ECC72PH0PR04MB7478namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Hello,</p> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> I intend to register the standards media type application/nits+xml on behal= f of the NATO STANAG 4676 Custodial Support Team (CST). STANAG 4676 is the = NATO Intelligence, Surveillance, and Reconnaissance (ISR) Track Standa= rd (NITS). This is a public standard that specifies a format for representing and transmitting ISR track data -= sequences of points indicating object trajectories.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Application form for preliminary review:</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> ----</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <b><br> </b></div> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Name:</b> Ryen Krusinga (submitting on behalf of Rob Downs, STANAG 4676 = Custodian)</p> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Email: </b>[email protected]</p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Type name:</b> application</p> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Subtype Name:</b> nits+xml (standards tree, no prefix)</p> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Required Parameters:</b> N/A</p> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Optional Parameters:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "charset" This parameter has identical semantics to t= he charset parameter of the "application/xml" media type as speci= fied in RFC 7303.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "sv" or "schemaversion" This parameter=92s = value indicates the edition of NITS (NATO ISR Track Standard) to which the = data is conformant. Legal values are:</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "B" Data is conformant to NITS Edition B= , defined in AEDP-12 Edition B</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "C" Data is conformant to NITS Edition C= , defined in AEDP-4676 Edition C</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> If the "sv" and "schemaversion" parameters are absent, = then the data consumer determines the version by examining file content. Ed= ition C is largely backwards compatible with Edition B, so consumers should= not reject data when the version is not included within the media type.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "profile" This parameter=92s value is a comma-separated li= st of named profiles of NITS to which the data is conformant. The file incl= udes values of the parameter as values of the "profile" attribute= within the "nitsRoot" root element of the XML data.</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Encoding Considerations:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "Binary" =96 based on the recommendation in the application:</p> <p class=3D"elementToProof" style=3D"text-align: center; line-height: 1.38;= margin: 8pt 0in 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontS= ervice, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0= );"> <i>"If the format is based on JSON or XML, "binary" should g= enerally be selected due to the possibility that lines could be longer than= 998 octets."</i></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Same as encoding considerations of application/xml as specified in RFC 7303= .</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Security Considerations:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Same as general security considerations for application/xml as specified in= section 10 of RFC 3023.</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0= px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, H= elvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> While AEDP-4676.2 Ed. C will be the published schema that defines the XML e= ncoding of NITS for STANAG 4676 Ed. 3, the schema supports the XSD 1.1 open= content model and allows additional content to be inserted anywhere in the= file. While the standard content defined by NITS itself includes no executable content, it is possible for = a data provider to insert additional XML entities into the file that do con= tain executable content. In addition to ensuring the data is valid and well= -formed XML, data consumers MUST take care to not blindly process any unexpected data found in the file and= should only parse or display content using mechanisms that prevent malform= ed or malicious data attacking the consumer.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0= px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, H= elvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> In many applications, access to the NITS data is restricted for privacy and= control issues. NITS itself defines no mechanisms to restrict access to th= e data. As such, data providers MUST implement their own access methods to = prevent unauthorized access to the data, and the transmission of the NITS data MUST be protected using standa= rd encryption methods such as SSL/TLS. NITS files may include elements spec= ifying confidentiality and how access to the data is restricted or permitte= d, encoded in the XML using ADatP-4774, the NATO Confidentiality Metadata Label Syntax. Consumers that discover AD= atP-4774 markings within NITS data MUST not provide further access to the d= ata beyond what is permitted by those markings. Consumers who discover ADat= P-4774 markings but do not recognize the specific markings MUST not provide any further access to the received = data until permission to access the data can be authoritatively confirmed.<= /div> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Interoperability Considerations:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Same as the interoperability considerations specified in RFC 7303.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> If both "sv" and "schemaversion" are specified, then th= e value of "schemaversion" MUST be ignored.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Structuring and validating the NITS data requires the XML schema files for = the corresponding STANAG edition, Ed. 2 or Ed. 3. For Ed. 3, the schema fil= es will be published as AEDP-4676.2 Ed. C in late 2026/early 2027 and are c= urrently available upon request from the STANAG 4676 custodial support team (CST); for Ed. 2, they are onl= y available by contacting the CST.</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Published Specification:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> STANAG 4676 Ed. 2</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> AEDP-12 Ed. B: "NATO ISR Tracking Standard, Edition B"</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt;"> <span style=3D"color: rgb(0, 0, 0);">Available via the </span><span style= =3D"color: rgb(70, 120, 134);"><a href=3D"https://nso.nato.int/nso/nsdd/mai= n/standards" id=3D"OWA62401377-b663-f672-d7b8-e6a1d9b8d305" class=3D"OWAAut= oLink" title=3D"https://nso.nato.int/nso/nsdd/main/standards" style=3D"marg= in-top: 0px; margin-bottom: 0px;"><u>NSO NSDD</u></a></span><span style=3D"color: rgb(0, 0, 0);"> at <a href= =3D"https://nso.nato.int/nso/nsdd/main/standards" id=3D"OWA283d26ae-69c4-62= 38-3b81-4a4ac92134c4" class=3D"OWAAutoLink" style=3D"margin-top: 0px; margi= n-bottom: 0px;"> https://nso.nato.int/nso/nsdd/main/standards</a></span></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> STANAG 4676 Ed. 3</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> AEDP-4676 Ed. C: "NATO ISR Track Standard, Edition C"= ;</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> AEDP-4676.1 Ed. C: "NATO ISR Track Standard Implementation Guid= e, Edition C"</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> AEDP-4676.2 Ed. C: "NATO ISR Track Standard XML Schema Definiti= on, Edition C"</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt;"> <span style=3D"color: rgb(0, 0, 0);">Available by contacting the STANAG 467= 6 Custodian; currently under review and expected to be published in late 20= 26/early 2027 via the </span><span style=3D"color: rgb(70, 120, 134);"><a href=3D"https://nso.nat= o.int/nso/nsdd/main/standards" id=3D"OWAd540fb55-f4e6-32af-e49d-7e7afe7651a= a" class=3D"OWAAutoLink" style=3D"color: rgb(70, 120, 134); margin-top: 0px= ; margin-bottom: 0px;"><u>NSO NSDD</u></a></span></p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(70, 120, 134);"> <u><br> </u></div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Application Usage:</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> The NATO Intelligence, Surveillance and Reconnaissance (ISR) Track Standard= (NITS) defines a standard format for object track data (data on the trajec= tories of real-world moving objects, such as boats, trucks or airplanes). N= ITS files are intended for use by applications that generate, analyze, and synthesize object track data for = intelligence, surveillance, and reconnaissance purposes. The typical use ca= se is for intelligence or defense systems communicating target information = for the purposes of intelligence, analysis, and battlefield responsiveness. However, this is not an exhausti= ve list of possible uses, and there is nothing in the standard that prevent= s use in other environments (e.g., commercial truck fleet tracking, parents= tracking the movement of their children=92s electronic devices, tracking checked baggage through an airpo= rt baggage handling system, etc.)</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Fragment Identifier Considerations</b></p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Same as fragment identifier considerations as specified in RFC 7303.</p> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> In addition, identifiers can be assigned to many of the elements in NITS, e= ither using UUIDs (the "uid" element) or simple integers with loc= al scope (the "lid" element). The uid values can be used to refer= to a fragment of one NITS file from another file; this mechanism is heavily relied on to avoid repeating static data across a lar= ge sequence of NITS files. While the lid values alone cannot be used to ref= er to an element from outside the file, a local scope identifier (a UUID) c= an be assigned within each file, allowing the combination of local scope identifier and the simple local in= teger identifier to be used to refer to fragments of a NITS file from exter= nal resources.</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Restrictions on Usage:</b> N/A</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Provisional Registrations: </b>No</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Additional Information:</b></p> <ul data-editing-info=3D"{"applyListStyleFromLevel":false,"u= norderedStyleType":2}" style=3D"margin-top: 0px; margin-bottom: 0px;"> <li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C= alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin= : 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Deprecated alias names:</b> N/A</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Magic Numbers:</b> Same as magic numbers specified by RFC 7303</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>File extensions:</b> .nits</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Macintosh File Type Codes:</b> N/A</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Object Identifiers or OIDs:</b> N/A</p> </li></ul> <div style=3D"line-height: 1.38; margin: 0in 0in 8pt; font-family: Aptos, A= ptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; fon= t-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Intended Usage: </b>COMMON</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Other info and comments: </b>N/A</p> <div class=3D"elementToProof" style=3D"line-height: 1.38; margin-top: 0in; = margin-right: 0in; margin-left: 0in; font-family: Aptos, Aptos_EmbeddedFont= , Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <p class=3D"elementToProof" style=3D"line-height: 1.38; margin: 0in 0in 0px= ; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Hel= vetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <b>Contact Person:</b></p> <ul data-editing-info=3D"{"applyListStyleFromLevel":false,"u= norderedStyleType":2}" style=3D"margin-top: 0px; margin-bottom: 0px;"> <li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C= alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin= : 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Name: </b>Rob Downs</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Email:</b> [email protected]</p> </li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi= ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m= argin: 0in 0in 8pt; list-style-type: "- ";"> <p class=3D"elementToProof" role=3D"presentation" style=3D"line-height: 1.3= 8; margin-top: 0in; margin-bottom: 0px;"> <b>Author/Change Controller:</b> NATO STANAG 4676 CST</p> </li></ul> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </p> <div id=3D"Signature" class=3D"elementToProof"> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> Ryen Krusinga</p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> Imagery Standards Developer | Compass, Inc.</p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> STANAG 4676 Technical Editor</p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> [email protected]</p> <p class=3D"elementToProof" style=3D"margin-top: 0px; margin-bottom: 0px; f= ont-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvet= ica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </p> </div> </body> </html> --_000_PH0PR04MB74789321451F2AA9D286C1E2ECC72PH0PR04MB7478namp_-- --===============6558399740936411847== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWVkaWEtdHlw ZXMgbWFpbGluZyBsaXN0IC0tIG1lZGlhLXR5cGVzQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNl bmQgYW4gZW1haWwgdG8gbWVkaWEtdHlwZXMtbGVhdmVAaWV0Zi5vcmcK --===============6558399740936411847==--