FMN Spiral 3.0 Inter-Autonomous Systems IP Transport Service Profile

The Inter-Autonomous Systems IP Transport Profile provides standards and guidance for Edge Transport Services between autonomous systems, using Internet Protocol (IP) over point-to-point Ethernet links on optical fibre.

Packet-based Transport Services

Conditional

If the interconnection point is outside a shelter in a harsh environment, the interconnection shall follow STANAG 4290 or MIL-DTL-83526 connector specifications.

• US DoD MIL-DTL-83526D - Connectors, fiber optic, circular, environmental resistant, hermaphroditic, general specification for
• NATO AComP-4290 Ed A Ver 2 - Standard for optical connector medium-rate and high-rate military tactical link

Mandatory

The use of LC-connectors is required for network interconnections inside shelters (or inside other conditioned infrastructure).

• ITU-T G.652 - Characteristics of a single-mode optical fibre and cable
• IEC 61754-20-100 - Interface standard for LC connectors with protective housings related to IEC 61076-3-106

Mandatory

Standards for IP version 4 (IPv4) over Ethernet

• IETF RFC 826 - Ethernet Address Resolution Protocol

Mandatory

• ISO/IEC 11801-1 - Information technology -- Generic cabling for customer premises -- Part 1: General requirements

Mandatory

Section 3 - Clause 38 - 1000BASE-LX, nominal transmit wavelength 1310nm.

• IEEE 803.3 - IEEE Standard for Ethernet

Use 1 Gb/s Ethernet over single-mode optical fibre (SMF).

FMN Spiral 3.0 Inter-Autonomous Systems Multicast Routing Profile

The Inter-Autonomous Systems Routing Profile provides standards and guidance for routing between inter-autonomous systems.

Packet Routing Services,

IPv4 Routed Access Services

Mandatory

The following standards shall apply to multicast routing.

• IETF RFC 6308 - Overview of the Internet Multicast Addressing Architecture
• IETF RFC 5771 - IANA Guidelines for IPv4 Multicast Address Assignments
• IETF RFC 2365 - Administratively Scoped IP Multicast

Mandatory

Service providers with their own multicast capability shall provide a Rendezvous Point (RP) supporting the following IP multicast protocol standards.

• IETF RFC 3618 - Multicast Source Discovery Protocol (MSDP)
• IETF RFC 4760 - Multiprotocol Extensions for BGP-4

Optional

• IETF RFC 4607 - Source-Specific Multicast for IP
• IETF RFC 4608 - Source-Specific Protocol Independent Multicast in 232/8

Mandatory

The following standards shall apply for all IP interconnections.

• IETF RFC 7761 - Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
• IETF RFC 1112 - Host Extensions for IP Multicasting
• IETF RFC 3376 - Internet Group Management Protocol, Version 3

FMN Spiral 3.0 Inter-Autonomous Systems Routing Profile

The Inter-Autonomous Systems Routing Profile provides standards and guidance for routing between inter-autonomous systems.

Packet Routing Services,

IPv4 Routed Access Services

Mandatory

The following standards apply for all IP interconnections.

• IETF RFC 1997 - Border Gateway Protocol (BGP) Communities Attribute
• IETF RFC 4360 - BGP Extended Communities Attribute
• IETF RFC 5492 - Capabilities Advertisement with BGP-4
• IETF RFC 4271 - A Border Gateway Protocol 4 (BGP-4)
• IETF RFC 4760 - Multiprotocol Extensions for BGP-4
• IETF RFC 7606 - Revised Error Handling for BGP UPDATE Messages
• IETF RFC 6793 - BGP Support for Four-Octet Autonomous System (AS) Number Space
• IETF RFC 6286 - Autonomous-System-Wide Unique BGP Identifier for BGP-4
• IETF RFC 7153 - IANA Registries for BGP Extended Communities

Mandatory

The following standard applies for unicast routing.

• IETF RFC 4632 - Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

Mandatory

The following standard is added to improve MD5-based BGP-authentication

• IETF RFC 5082 - The Generalized TTL Security Mechanism (GTSM)

Conditional

The following standard can be added to improve MD5-based BGP-authentication, depending on bilateral agreement.

• IETF RFC 7454 - BGP Operations and Security

Recommended

Additionally, the following standard applies for 32-bit autonomous system numbers (ASN).

• IETF RFC 5668 - 4-Octet AS Specific BGP Extended Community

Border Gateway Protocol (BGP) deployment guidance in IETF RFC 1772 1995, Application of the Border Gateway Protocol in the Internet.BGP sessions must be authenticated, through a TCP message authentication code (MAC) using a one-way hash function (MD5), as described in IETF RFC 4271.

FMN Spiral 3.0 Inter-Autonomous Systems IP Communications Security Profile

The Inter-Autonomous Systems IP Communications Security Profile provides standards and guidance for communications security for transporting IP packets between federated mission network interconnections and in general over the whole Mission Network.

Transport CIS Security Services

Recommended

In Missions, where NATO information products are not carried over the mission network, MISSION SECRET (MS) communications infrastructure is protected with technical structures by mutual agreement made during the mission planning phase.

• DPC AC/322-D(2015)0031 - CIS Security Technical and Implementation Directive on Cryptographic Security and Mechanisms for the Protection of NATO Information within NNN & IO CIS
• NSA CSfC MSC CP Ver 1.0 - CSfC Multi-Site Connectivity Capability Package Ver 1.1

Conditional

In Missions, where NATO information products are carried over the mission network, the MISSION SECRET (MS) communications infrastructure is protected at minimum with Type-B crypto devices

• DPC AC/322-D(2015)0031 - CIS Security Technical and Implementation Directive on Cryptographic Security and Mechanisms for the Protection of NATO Information within NNN & IO CIS

In Missions, where the mission network classification is MISSION RESTRICTED (MR) or lower, communication infrastructure is protected at the minimum with technical structures that are within Service Instruction section Security and in Routing Encapsulation Profile.

FMN Spiral 3.0 Interface Auto-Configuration Profile

The Interface Auto-Configuration Profile provides standards and guidance for support of the Routing Information Protocol (RIPv2 and RIPng) to expand the amount of useful information carried in RIP messages for the exploitation of auto-configurations over NIP-G and PCN-compliant interfaces and to add a measure of control.

Packet-based Transport Services

Mandatory

The Interface Auto-Configuration Profile provides standards and guidance for support of the Routing Information Protocol (RIPv2 and RIPng) to expand the amount of useful information carried in RIP messages for the exploitation of auto-configurations over NIP-G and PCN-compliant interfaces and to add a measure of control.

• IETF RFC 2453 - Routing Information Protocol (RIP) Version 2
• IETF RFC 2080 - Routing Information Protocol next generation for IPv6 (RIPng)

The auto-configuration is a highly recommended feature for the desired flexibility, maintainability and survivability in communications systems configuration. Nevertheless, there is always an option to follow a manual configuration process. This implies that auto-configuration in itself is not mandatory; when applied, the listed standards are mandatory.

FMN Spiral 3.0 Routing Encapsulation Service Profile

The Routing Encapsulation Profile provides standards and guidance for generic routing encapsulation functions between network interconnection points (NIPs).

Packet-based Transport Services

Mandatory

• IETF RFC 4303 - IP Encapsulating Security Payload (ESP)
• IETF RFC 2784 - Generic Routing Encapsulation (GRE)
• IETF RFC 4754 - IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA)
• IETF RFC 5903 - Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2
• IETF RFC 7670 - Generic Raw Public-Key Support for IKEv2
• IETF RFC 7296 - Internet Key Exchange Protocol Version 2 (IKEv2)
• IETF RFC 7427 - Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)

Protected Core Communications does not support the use of pre-shared keys as an authentication method. While Classified Information Domains in Coloured Clouds may use pre-shared keys in their NIP-G interfaces.IKEv2 is used for authentication both using Digital Certificates and pre-shared keys.

FMN Spiral 3.0 IP Quality of Service Profile

The IP Quality of Service Profile provides standards and guidance to establish and control an agreed level of performance for IP services in federated networks.

IPv4 Routed Access Services,

Packet-based Transport Services

Mandatory

Utilize Quality of Service capabilities of the network (Diffserve, no military precedence on IP).

• IETF RFC 2474 - Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
• IETF RFC 4594 - Configuration Guidelines for DiffServ Service Classes
• ITU-T Y.1540 - IP packet transfer and availability performance parameters
• ITU-T Y.1541 - Network performance objectives for IP-based services
• ITU-T Y.1542 - Framework for achieving end-to-end IP performance objectives
• ITU-T M.2301 - Performance objectives and procedures for provisioning and maintenance of IP-based networks
• ITU-T J.241 - Quality of service ranking and measurement methods for digital video services delivered over broadband IP networks

Mandatory

The following normative standards shall apply for IP Quality of Service (QoS). The condition is that this STANAG, although widely used and referenced, is currently a draft version in process by approval authorities.

• NATO AComP-4711 Ed A Ver 1 - Interoperability Point Quality of Service (IP QoS)

For NATO-led Mission Network deployments, the following governing policies apply

• AC/322(SC/6)WP(2009)0002-REV2 - NC3B Policy on the Federation of Networks and Provision of Communications Services within the Networking Information Infrastructure
• NATO Policy for Standardization

FMN Spiral 3.0 Digital Certificate Service Profile

The Digital Certificate Profile provides standards and guidance in support of a Public Key Infrastructure (PKI) on federated mission networks.

Digital Certificate Services

Mandatory

• ITU-T X.509 - Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks

Optional

The Online Certificate Status Protocol (OCSP) capability is optional for PKI Service providers and consumers.

• IETF RFC 6960 - X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP

Mandatory

CRLs may be provided at multiple endpoints. The addresses of these endpoints shall be provided in digital certificates through X.509 certificate extensions such as Authority Information Access (AIA) and CRL distribution point (CDP). Each CA shall provide CRLs using at least one of the endpoint types (HTTP or LDAP). Clients must support both types.

• IETF RFC 5280 - Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
• IETF RFC 4523 - Lightweight Directory Access Protocol (LDAP) - X.509 Certificate Schema

The version of the encoded public key certificate shall be version 3. The version of the encoded certificate revocation list (CRL) shall be version 2.Additional Implementation Guidance

• AC/322-D(2004)0024-REV2-ADD2 - NATO Public Key Infrastructure (NPKI) Certificate Policy
• AC/322-D(2010)0036 - NATO Cryptographic Interoperability Strategy

FMN Spiral 3.0 Domain Naming Service Profile

The Domain Naming Profile provides standards and guidance to support the hierarchical distributed naming system for computers, services, or any resource connected to a federated mission network.

Domain Name Services

Mandatory

• IETF RFC 1034 - Domain names - concepts and facilities
• IETF RFC 1035 - Domain names - implementation and specification
• IETF RFC 2181 - Clarifications to the DNS Specification
• IETF RFC 2782 - A DNS RR for specifying the location of services (DNS SRV)
• IETF RFC 3258 - Distributing Authoritative Name Servers via Shared Unicast Addresses
• IETF RFC 4786 - Operation of Anycast Services
• IETF RFC 5936 - DNS Zone Transfer Protocol (AXFR)
• IETF RFC 5966 - DNS Transport over TCP - Implementation Requirements
• IETF RFC 6382 - Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services
• IETF RFC 6891 - Extension Mechanisms for DNS (EDNS(0))
• IETF RFC 7094 - Architectural Considerations of IP Anycast

FMN Spiral 3.0 Time Synchronization Service Profile

The Time Synchronization Profile provides standards and guidance to support the synchronization of clients and servers across a network or a federation of networks and the safeguard of the accurate use of timestamps.

Distributed Time Services

Mandatory

Service providers must synchronize their network segment with a stratum 1 time server directly connected to a stratum 0 device, or over a reliable network path to a stratum 1 time server of another service provider. All other entities in the federation must use the time service of their host service provider.

• IETF RFC 5905 - Network Time Protocol (NTP) Version 4: Protocol and Algorithms Specification
• ITU-R TF.460-6 - Standard-frequency and time-signal emissions. Annex 1: Coordinated universal time (UTC)

Stratum 1 devices must implement IPv4 so that they can be used as time servers for IPv4-based Mission Networks.

FMN Spiral 3.0 Directory Data Structure Service Profile

The Directory Data Structure Profile provides standards and guidance in support of the definition of the namespace of a federated mission network on the basis of the Lightweight Directory Access Protocol (LDAP).

Directory Services

Mandatory

• IETF RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
• IETF RFC 4519 - Lightweight Directory Access Protocol (LDAP) - Schema for User Applications

The Federated Directory Services shall be able to exchange inetOrgPerson object class with mandatory Common Name (cn) and Surname (sn) attributes. Based on the specific MN requirements, the list of exchanged attributes for particular MN might be extended by SMA during MN planning process.

FMN Spiral 3.0 Cryptographic Algorithms Profile

The Cryptographic Algorithms Profile specifies the use of public standards for cryptographic algorithm interoperability to protect IT systems.

Digital Certificate Services

Mandatory

• NIST FIPS PUB 197 - Advanced Encryption Standard (AES)
• NIST SP 800-56A Rev 3 - Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography
• NIST FIPS PUB 186-4 - Digital Signature Standard (DSS)
• NIST FIPS PUB 180-4 - Secure Hash Standard (SHS)
• IETF RFC 3526 - More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)
• NIST SP 800-56B Rev 1 - Recommendation for Pair-Wise KeyEstablishment Schemes Using Integer Factorization Cryptography

The following algorithms and parameters are to be used to support specific functions

• Root CA Certificates
  • Digest Algorithm SHA-256, or SHA-384 (Root CA certificates, which were signed using SHA-1 before 1 January 2016, may be used until 1 January 2025)
  • RSA modulus size (bits) 2048, 3072 and 4096
  • ECC Curve NIST P-256, and P-384
• Subordinate CA Certificates
  • Digest Algorithm SHA-256, and SHA-384
  • RSA modulus size (bits) 2048, 3072 and 4096
  • ECC Curve NIST P-256, and P-384
• Subscriber Certificates
  • Digest Algorithm SHA-256, and SHA-384
  • RSA modulus size (bits) 2048, 3072 and 4096
  • ECC Curve NIST P-256, and P-384

FMN Spiral 3.0 ISR Library Interface Profile

The ISR Library Interface is the standard interface for querying and accessing heterogeneous product libraries maintained by various nations.

Disseminate JISR Products

Mandatory

The following international standards are mandated for interoperability of ISR libraries.

• ISO 639-2 - Representation of Names of Languages Part 2: Alpha-3
• ISO/IEC 11179-3 - Information technology -- Metadata registries (MDR) -- Part 3: Registry metamodel and basic attributes
• ISO/IEC 12087-5 - Image Processing and Interchange (IPI) - Functional Specification - Part 5: Basic Image Interchange Format (BIIF)
• ISO/IEC 14750 - Information technology -- Open Distributed Processing -- Interface Definition Language

Mandatory

The following NATO standards are mandated for interoperability of ISR libraries. (For STANAG 4559 Ed 4: Only Standard AEDP-17 Ed. A Ver. 1 NATO Standard ISR Library Interface.)

• NATO AEDP-04 Ed 2 Ver 1 - NATO Secondary Imagery Format (NSIF) STANAG 4545 Implementation Guide
• NATO AEDP-07 Ed 2 Ver 1 - NATO Ground Moving Target Indicator (GMTI) Format STANAG 4607 Implementation Guide
• NATO AEDP-17 Ed A Ver 1 - NATO Standard ISR Library Interface
• NATO AEDP-18 Ed A Ver 1 - NATO Standard ISR Streaming Services
• NATO AEDP-19 Ed A Ver 1 - NATO Standard ISR Workflow Architecture
• NATO MISP-2015.1 - US Motion Imagery Standards Board (MISB) - Motion Imagimary Standards Profile-2015.1

Mandatory

Note: implementation of STANAG 5525 in the context of the ISR Library Interface Profile is limited to the definition of unique keys that could be used to unambiguously refer to an external information object that is modelled in accordance with STANAG 5525.

• NATO STANAG 5525 Ed 1 - Joint C3 Information Exchange Data Model (JC3IEDM)

To ensure optimization of network resources the CSD services work best with a unicast address space.AEDP-17 Ed. A Vers. 1 defines two interfaces

• the first one is a federated service provider interface (see ISR Library Federation Pattern) based on CORBA's Internet Inter-ORB Protocol,
• the second one is in support of the provider-consumer interface (see ISR Library Access Pattern) based on web services.

FMN Spiral 3.0 Formatted Messages for ISR Profile

The Formatted Messages Profile provides standard for formatted messages that are typically used to exchange Intelligence, Surveillance, and Reconnaissance (ISR) products in military operations. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or for publication as files on websites. In addition, some of these formatted messages are also supported by federated ISR Libraries.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services,

Web Hosting Services,

Disseminate JISR Products

Mandatory

To support the exchange of information needed to govern and facilitate the collection of Intelligence, Surveillance and Reconnaissance (ISR) information and production of intelligence the following message formats defined in APP-11 MUST be supported (MTF Identifier, MTF Index Ref Number): Intelligence Request (INTREQ, J021)Information Requirement Management & Collection Management Exchange (ICE, J033)Information Requirement Management & Collection Management Exchange (ICE, J033)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Recommended

The following XML Schema defined by MAJIIC 2 SHOULD be supported: ISR Spot Report (ISRSPOTREP) This report is to be used for quick reporting allowing a free-text description of the results. MAJIIC 2 Bravo.1

Mandatory

To support the sharing of JISR Products the following message formats defined in various AEDPs MUST be supported: ISR TrackMeasurement and Signature Intelligence Report (MASINTREP)ImageryGround Moving Target Indicator (GMTI)Motion Imagery Corrigendum to FMN Spiral 3 Standard Profile: AEDP-08 Ed. 3 has been replaced by NNSTD MISP-2015.1 with STANAG 4609 Ed 4.

• NATO AEDP-12 Ed A Ver 1 - NATO Intelligence, Surveillance And Reconnaissance Tracking Standard
• NATO AEDP-16 (Study) - NATO standardization of measurement and signature intelligence (MASINT) Reporting
• NATO AEDP-04 Ed 2 Ver 1 - NATO Secondary Imagery Format (NSIF) STANAG 4545 Implementation Guide
• NATO AEDP-07 Ed 2 Ver 1 - NATO Ground Moving Target Indicator (GMTI) Format STANAG 4607 Implementation Guide
• NATO MISP-2015.1 - US Motion Imagery Standards Board (MISB) - Motion Imagimary Standards Profile-2015.1

Mandatory

To support the sharing of JISR Products the following message formats defined in APP-11 and STANAG 3377 MUST be supported (MTF Identifier, MTF Index Ref Number): Target Track Report (TRACKREP, J071)Mission Report (MISREP, F031)Inflight Report (INFLIGHTREP, J009)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue
• NATO STANAG 3377 Ed 6 - Air Reconnaissance Intelligence Report Forms

FMN Spiral 3.0 Formatted Messages for Intelligence Profile

The Formatted Messages Profile provides standard for formatted messages that are typically used to exchange Intelligence Products in military operations. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or for publication as files on websites.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services,

Web Hosting Services

Mandatory

To support exploitation the following APP-11 message formats MUST be supported (MTF Identifier, MTF Index Ref Number): Air Intelligence Report (AIRINTREP, F001)Counter-Intelligence and Security Report (CIINTREP, J112)Counter-Intelligence and Security Summary (CIINTSUM, J113)Counter-Intelligence and Security Supplementary Report (CISUPINTREP, J115)Detailed Document Report (DEDOCREP, J089)First Hostile Act Report (First Hostile Act)Intelligence Report (INTREP, J110)Intelligence Summary (INTSUM, J111)Maritime Intelligence Report (MARINTREP, J016)Maritime Intelligence Summary (MARINTSUM, J015)Supplementary Intelligence Report (SUPINTREP, J114)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Mandatory

To support the exchange of Intelligence Products the following AJP-2.5 message formats MUST be supported (MTF Identifier): Human Intelligence Report (HUMINTREP)Human Intelligence Summary (HUMINTSUM)Interrogation Report (INTGREP)

• NATO AJP-2.5 Ed A - Captured Persons, Materiel And Documents

Mandatory

To support the exchange of information needed to govern and facilitate the collection of Intelligence, Surveillance and Reconnaissance (ISR) information and production of intelligence the following message formats defined in APP-11 MUST be supported (MTF Identifier, MTF Index Ref Number): Intelligence Request (INTREQ, J021)Information Requirement Management & Collection Management Exchange (ICE, J033)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Recommended

To support exploitation the following MAJIIC 2 message formats SHOULD be supported Electronic Order of Battle (EOB)Pentagram Report (PentagramREP)MAJIIC 2 Bravo.1

FMN Spiral 3.0 Formatted Messages for ISR Exploitation Profile

The Formatted Messages Profile provides standard for formatted messages that are used to exploit Intelligence, Surveillance, and Reconnaissance (ISR) information in military operations. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or for publication as files on websites. In addition, some of these formatted messages are also supported by federated ISR Libraries.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services,

Web Hosting Services,

Disseminate JISR Products

Mandatory

To support exploitation the following APP-11 message formats MUST be supported (MTF Identifier, MTF Index Ref Number): Preliminary Technical Report (PRETECHREP, J085)Complementary Technical Report (COMTECHREP COMTECHREP - TYPE A (J086)COMTECHREP - TYPE B (J087)COMTECHREP - TYPE C (J088) Reconnaissance Exploitation Report (RECCEXREP, J103) To support exploitation the following STANAG 3377 message formats MUST be supported: Motion Intel Exploitation Report (MIEXREP)Radar Exploitation Report (RADAREXREP)Radar Exploitation Report - Abbreviated (RADAREXREP-A)Supplemental Programmed Interpretation Report (SUPIR)Initial Programmed Interpretation Report (IPIR) General Version of Initial Programmed Interpretation Report/Supplemental Programmed Interpretation Report (IPIR/SUPIR) To support exploitation the following STANAG 4607 message formats MUST be supported: Moving Target Indicator Exploitation Report (MTIEXREP)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue
• NATO STANAG 3377 Ed 6 - Air Reconnaissance Intelligence Report Forms
• NATO AEDP-07 Ed 2 Ver 1 - NATO Ground Moving Target Indicator (GMTI) Format STANAG 4607 Implementation Guide

FMN Spiral 3.0 Battlespace Event Federation Profile

The Battlespace Event Federation Profile provides standards and guidance to support the exchange of information on significant incidents, important events, trends and activities within a coalition network or a federation of networks.

Battlespace Event Services

Mandatory

To support exploitation the following APP-11 message formats MUST be supported (MTF Identifier, MTF Index Ref Number): Incident Report (INCREP, A078)Incident Spot Report (INCSPOTREP, J006)Troops in Contact SALTA format (SALTATIC, A073)Events Report (EVENTREP, J092)Improvised Explosive Device Report (IEDREP, A075) The INCREP is used to report any significant incident caused by terrorism, civil unrest, natural disaster, or media activity. The INCSPOTREP is used to provide time critical information on important events that have an immediate impact on operations. The SALTATIC is used to report troops in contact, the report should be made as soon as possible by the unit that has come under some form of attack. It uses the following basic format: Size of enemy, Action of enemy, Location, Time and Action taken. The EVENTREP is used to provide the chain of command information about important Events, trends and activities that do not have an element of extreme urgency, but do influence on-going operations The IEDREP is sent when an IED has been encountered. It identifies the hazard area, tactical situation, operational priorities and the unit affected. This initial report should be followed by normal EOD/Engineer reporting requirements.

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

FMN Spiral 3.0 Friendly Force Tracking Profile

The Friendly Force Tracking Profile provides standards and guidance to support the exchange of Friendly Force Tracking information within a coalition network or a federation of networks.

Track Management Services

Conditional

VMF may only be used when messages are converted to FFI before the publication on the FFT network, using the exchange mechanism described in the MIL-STD-6017B. NISP Standard - VMF - "Variable Message Format (VMF)"

Mandatory

• NATO ADatP-36 Ed A Ver 1 - Friendly Force Tracking Systems (FFTS) Interoperability
• NATO APP-11 Ed D Ver 1 - NATO Message Catalogue

Messages exchanged according to the exchange mechanisms described in ADatP-36(A) shall comply with the Message Text Format (FFI MTF) schema incorporated in APP-11(D)(1).IP1 is the preferred protocol for Spiral 3.Caveat where needed the other ADatP-36(A) protocols (IP2 an SIP3) may be used if the situation requires this, and this MUST be determined on instantiation.Caveat VMF uses the concept of the Unit Reference Number (URN) as unique identifier on the tracked unit and this is not in line with the FFI unique identifier. VMF URN can be used as FFI unique identifier but the viceversa is not true, so specific rules shall be defined for the unique identifier allignments.

FMN Spiral 3.0 Symbology Federation Profile

Symbology Services

Mandatory

Implementation of NATO Vector Graphics MUST use Symbology Standard APP-6(D). Remark: It should be noted that as of July 2018 ADatP-4733 Version A Edition 1 does not include a binding to APP-6(D). At this time this binding is is being developed by ACT with the intent of including this update into the final ratified STANAG, but is not clear if it will result in a new Edition

• NATO APP-06 Ed D Ver 1 - NATO Joint Military Symbology

Mandatory

Implementation of NATO Vector Graphics MUST be conformant to NVG Conformance Level: B2Q

• NATO NVG 1.5 - NATO Vector Graphics (NVG) Protocol version 1.5:2010 (ACT)

All presentation services shall render tracks, tactical graphics, and MOOTW objects using these standards except in the case where the object being rendered is not covered in the standard. In these exceptional cases, additional symbols shall be defined as extensions of existing symbol standards and must be backwards compatible. These extensions shall be submitted as a request for change within the configuration management process to be considered for inclusion in the next version of the specification.

FMN Spiral 3.0 Maritime Information Exchange Profile

The Maritime Information Exchange Profile provides standards and guidance to support the exchange of Maritime Recognized Picture information within a coalition network or a federation of networks

Recognized Maritime Picture Services

Mandatory

For the RMP Services for building the Operational RMP it is mandatory to implement NVG to provide an interface for Cross COI Shared Situational Awareness where OTH-T GOLD cannot be processed

• NATO NVG 1.5 - NATO Vector Graphics (NVG) Protocol version 1.5:2010 (ACT)

Mandatory

• US DoN OTH-T Gold Baseline 2000 - Operational Specification for Over-The-Horizon Targeting Gold Revision D, OS-OTG (Rev. D)

The implementation of the following message types is mandatory

• Contact Report (CTC)
• Enhanced Contact Report (XCTC),
• Overlay Message (OVLY2, OVLY3),

• Area of Interest Filter (AOI),
• FOTC Situation Report,
• Group Track Message (GROUP),
• Operator Note (OPNOTE),
• PIM Track (PIMTRACK).

• TCP (connect, send, disconnect) - default port 2020

FMN Spiral 3.0 Formatted Messages for SA Profile

The Formatted Messages Profile for Situational Awareness provides standard for formatted messages that are typically used in military operations in support of Situational Awareness. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or in standardized voice procedures, e.g. MEDEVAC Requests.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services

Mandatory

Procedures for Situational Awareness require the following messages: Events: Incident Report (INCREP – A078)Incident Spot Report (INCSPOTREP – J006)Troops in Contact SALTA Format (SALTATIC – A073)Search and Rescue Incident Report (SARIR)EOD Incident Report (EODINCREP - J069) / EO Incident Report (EOINCREP)Events Report (EVENTREP - J092) Tasks and Orders: Airspace Control Order (ACO - F011)Air Tasking Order (ATO - F058) Features: Killbox Message (KILLBOX - F083)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

FMN Spiral 3.0 Land C2 Information Exchange Profile

The Land C2 Information Exchange Profile provides standards and guidance to support the exchange of Command and Control information within a coalition network or a federation of networks.

Battlespace Object Services

Mandatory

MIP 3.1 Interoperability Specification - "MIP 3.1 Interoperability Specification"

• NATO STANAG 5525 Ed 1 - Joint C3 Information Exchange Data Model (JC3IEDM)

The MIP3.1 Interoperability Specification comprises both a mandatory technical interface specification as well as implementation guidance documents, and is available on the MIP website (https //www.mip-interop.org). The interface specification consists of

• MIP Technical Interface Design Plan (MTIDP) v3.1.2 - defining the MIP3.1 Data Exchange Mechanism (DEM)
• Joint C3 Information Exchange Data Model (JC3IEDM) v3.1.4 - defining the MIP3.1 data model (also available as STANAG 5525); and
• MIP Implementation Rules (MIR) v3.1.5 - defining implementation rules for mapping the JC3IEDM to C2 systems.

FMN Spiral 3.0 Tactical Message Distribution Profile

The Air Information Exchange Profile provides standards and guidance to support the exchange of Recognized Air Picture (RAP) information within a coalition network or a federation of networks.

Recognized Air Picture Services,

Track Management Services,

Situational Awareness Services

Mandatory

The Standard for Joint Range Extension Application Protocol (JREAP) - ATDLP-5.18 Edition B enables TDL data to be transmitted over digital media and networks not originally designed for tactical data exchange. JREAP consists of three different protocols: A, B and C. For implementation in FMN only JREAP, Appendix C 'Encapsulation over Internet Protocol (IP)' which enables TDL data to be transmitted over an IP network must be used. As per the common time reference within JREAP, UTC must be supported as the common time reference. If no common time reference is available, round-trip shall be used.

• NATO ATDLP-5.18 Ed B Ver 2 - Interoperability Standard for Joint Range Extension Application Protocol (JREAP)

Mandatory

The "Minimum Link-16 Message Profile", as described in the FMN Spiral 3 Service Interface Profile for RAP Data, defines the minimum set of data elements that are required to be available for operational or technical reasons so that correctly formatted technical message can be generated to establish a Recognized Air Picture in a federated environment. The implementation of the following message types of STANAG 5516 is MANDATORY: Precise Participant Location and Identification (PPLI) Messages J2.0 Indirect Interface Unit PPLIJ2.2 Air PPLIJ2.3 Surface (Maritime) PPLIJ2.4 Subsurface (Maritime) PPLIJ2.5 Land (Ground) Point PPLIJ2.6 Land (Ground) Track PPLI Surveillance Messages J3.0 Reference PointJ3.1 Emergency PointJ3.2 Air Track messageJ3.3 Surface (Maritime) TrackJ3.4 Subsurface (Maritime) TrackJ3.5 Land (Ground) Point/TrackJ3.7 Electronic Warfare Product Information To maximize the ability to share tactical data in support of Situational Awareness, the following message types must also be supported: J7 Information ManagementJ8 Information ManagementJ9 Weapons Coordination and ManagementJ10 Weapons Coordination and ManagementJ12 ControlJ13 Platform and System StatusJ15 Threat WarningJ17 Miscellaneous

• NATO STANAG 5516 Ed 4 - Tactical Data Exchange - Link 16

With regards to JREAP JREAP is designed to support operations using Link 16 over most communication media (JRE media) including forwarding TDL data over SATCOM links (JREAP-A), Serial links (JREAP-B), and over IP networks (JREAP-C). Each JRE medium has unique characteristics. It supports UDP Unicast, UDP multicast, and TCP. For implementation in FMN only JREAP, Appendix C Encapsulation over Internet Protocol (IP) is to be used.

FMN Spiral 3.0 SMC Process Choreography Profile

Service Management and Control Process Choreography Profile is the capability to bring together individual services to accomplish a larger piece of work. It provides standards and guidance to support the choreography of SMC processes and ITSM systems in a multi-service provider environment.

Platform SMC Services

Recommended

For the implementation of SMC Federation Level 1 or 2, the following TM Forum REST specifications are strongly recommended.

• TM Forum TMF630 - TMF630 API Design Guidelines 3.0 R17.5.0
• TM Forum TR250 - API REST Conformance Guidelines R15.5.1 Standard

Recommended

Compliance with the Service Implementation Profiles for REST Messaging/REST Security Services that the implementations meet a set of non-functional requirements aligned with emerging message labelling and security standards.

The Service Management and Control Process Choreography Profile will expand over time and new APIs are expected to be added as they mature as commercial standards.

FMN Spiral 3.0 SMC Process Implementation Profile

The SMC Process Implementation Profile enables the handover of federated Service Management records between the sending Service Providers and the receiving Service Provider. Details about the handover point and supported use cases is described per process in the Service Interface Profile. The profiles provide the implementation guidance for the TM Forum API REST Specification.

C3 Taxonomy

Recommended

Note: Some of the TM Forum standards mentioned below refer to a newer version than documented in the official FMN Spiral 3 Profile.

• TM Forum TMF621 - Trouble Ticket REST API Specification R14.5.1 Interface
• TM Forum TMF638 - TMF638 Service Inventory API REST Specification R16.5
• TM Forum TMF641 - TMF641 Service Ordering API REST Specification R16.5.1
• TM Forum TMF622 - Product Ordering API REST Specification R14.5.1 Interface
• TM Forum TMF000 - TMF000 Event API REST Specification R17.5
• TM Forum TR250 - API REST Conformance Guidelines R15.5.1 Standard
• TM Forum TMF661 - TMF661 Trouble Ticket API Conformance Profile R16.5.1
• NATO ADatP-4774 Ed A Ver 1 - Confidentiality Metadata Label Syntax
• NATO ADatP-4778 Ed A Ver 1 - Metadata Binding Mechanism

FMN specific implementation details are specified within each of the Service Interface Profiles for Service Management and Control.

FMN Spiral 3.0 Audio-based Collaboration Service Profile

The Audio-based Collaboration Profile provides standards and guidance for the implementation of an interoperable voice system (telephony) on federated mission networks.

Audio-based Communication Services

Mandatory

The following standards are used for audio protocols.

• ITU-T G.729 - Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)
• ITU-T G.722.1 (2005) Corrigendum 1 (06/08) - Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss
• ITU-T G.711 - Pulse code modulation (PCM) of voice frequencies

Voice over IP (VoIP) refers to unprotected voice communication services running on unclassified IP networks e.g. conventional IP telephony. Voice over Secure IP (VoSIP) refers to non-protected voice service running on a classified IP networks. Depending on the security classification of a FMN instance, VoIP or VoSIP is mandatory.If a member choses to use network agnostic Secure Voice services in addition to VoSIP, then SCIP specifications as defined for audio-based collaboration services (end-to-end protected voice) should be used.The voice sampling interval is 40ms.

FMN Spiral 3.0 Basic Text-based Collaboration Service Profile

The Basic Text-based Collaboration Profile provides standards and guidance to establish a basic near-real time text-based group collaboration capability (chat) for time critical reporting and decision making in military operations.

Presence Services,

Text-based Communication Services

Mandatory

The following standards are the base IETF protocols for interoperability of chat services.

• IETF RFC 6120 - Extensible Messaging and Presence Protocol (XMPP): Core
• IETF RFC 6121 - Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
• IETF RFC 6122 - Extensible Messaging and Presence Protocol (XMPP): Address Format

Mandatory

The following standards are required to achieve compliance for an XMPP Server and an XMPP Client dependent upon the categorisation of presenting a core or advanced instant messaging service interface.

• XSF XEP-0004 - XEP-0004: Data Forms (2007/08)
• XSF XEP-0012 - XEP-0012: Last Activity
• XSF XEP-0030 - XEP-0030: Service Discovery (2008/06)
• XSF XEP-0045 - XEP-0045: Multi-User Chat (2012/02)
• XSF XEP-0047 - XEP-0047: In-Band Bytestreams
• XSF XEP-0049 - XEP-0049: Private XML Storage
• XSF XEP-0054 - XEP-0054: vcard-temp
• XSF XEP-0055 - XEP-0055: Jabber Search
• XSF XEP-0060 - XEP-0060: Publish-Subscribe (2010/07)
• XSF XEP-0065 - XEP-0065: SOCKS5 Bytestreams
• XSF XEP-0092 - XEP-0092: Software Version
• XSF XEP-0114 - XEP-0114: Jabber Component Protocol
• XSF XEP-0115 - XEP-0115: Entity Capabilities (2008/02)
• XSF XEP-0160 Ver 1.0 - XEP-0160: Best Practices for Handling Offline Messages (2016/01)
• XSF XEP-0198 - XEP-0198: Stream Management
• XSF XEP-0199 - XEP-0199: XMPP Ping (2009/06)
• XSF XEP-0202 - XEP-0202: Entity Time
• XSF XEP-0203 - XEP-0203: Delayed Delivery
• XSF XEP-0220 - XEP-0220: Server Dialback (2014/08)
• XSF XEP-0258 - XEP-0258: Security Labels in XMPP

FMN Spiral 3.0 Numbering Plans Service Profile

The Numbering Plans Profile provides standards and guidance for the facilitation of numbering plans of telecommunications, audio and video networks.

Audio-based Communication Services,

Video-based Communication Services

Optional

The following standards are optionally used for numbering

• NATO STANAG 5046 Ed 4 - The NATO Military Communications Directory System

Mandatory

The following standards are used for numbering. Network planners and engineers are reminded that in case Canada and United States are both participating in a mission network, there is a necessity to de-conflict the country code a.k.a. Country Identified (CI).

• NATO STANAG 4705 Ed 1 - International Network Numbering for Communications Systems in use in NATO
• ITU-T E.123 - Notation for national and international telephone numbers, e-mail addresses and web addresses
• ITU-T E.164 - The international public telecommunication numbering plan

FMN Spiral 3.0 Standalone Voice Services Call Signaling Profile

Audio-based Communication Services

Mandatory

• ITU-T G.729 - Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)
• ITU-T G.711 - Pulse code modulation (PCM) of voice frequencies
• ITU-T G.722.1 (2005) Corrigendum 1 (06/08) - Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss

FMN Spiral 3.0 Standalone VTC Services Call Signaling Profile

Video-based Communication Services

Mandatory

• ITU-T G.711 - Pulse code modulation (PCM) of voice frequencies
• ITU-T G.722.1 (2005) Corrigendum 1 (06/08) - Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss
• ITU-T H.264 - Advanced video coding for generic audiovisual services

FMN Spiral 3.0 Unified Voice and VTC Services Call Signaling Profile

Audio-based Communication Services,

Video-based Communication Services

Mandatory

• ITU-T G.711 - Pulse code modulation (PCM) of voice frequencies
• ITU-T G.722.1 (2005) Corrigendum 1 (06/08) - Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss
• ITU-T H.264 - Advanced video coding for generic audiovisual services

FMN Spiral 3.0 Session Initiation and Control Profile

The Session Initiation and Control Profile provides standards used for session initiation and control.

Video-based Communication Services

Mandatory

The following standards are used for regular session initiation and control.

• IETF RFC 3261 - Session Initiation Protocol (SIP)
• IETF RFC 3262 - Reliability of Provisional Responses in the Session Initiation Protocol (SIP)
• IETF RFC 3264 - An Offer/Answer Model with the Session Description Protocol (SDP)
• IETF RFC 3311 - The Session Initiation Protocol (SIP) UPDATE Method
• IETF RFC 4028 - Session Timers in the Session Initiation Protocol (SIP)
• IETF RFC 4566 - SDP: Session Description Protocol
• IETF RFC 6665 - SIP-Specific Event Notification

Mandatory

The following standards define the SIP and RTP support for conferencing.

• IETF RFC 4353 - A Framework for Conferencing with the Session Initiation Protocol (SIP)
• IETF RFC 4579 - Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents
• IETF RFC 5366 - Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)
• IETF RFC 7667 - RTP Topologies

FMN Spiral 3.0 Priority and Pre-emption Profile

The Priority and Pre-emption Profile provides standards are used to execute priority and pre-emption service with SIP.

Audio-based Communication Services,

Video-based Communication Services

Mandatory

• IETF RFC 4411 - Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events
• IETF RFC 4412 - Communications Resource Priority for the Session Initiation Protocol (SIP)

FMN Spiral 3.0 Media Streaming Profile

The Media Streaming Profile provides standards used to stream media across the mission network.

Audio-based Communication Services

Mandatory

• IETF RFC 3550 - RTP: A Transport Protocol for Real-Time Applications
• IETF RFC 4733 - RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals

FMN Spiral 3.0 SRTP-based Media Infrastructure Security Profile

The SRTP-based Media Infrastructure Security Profile provides security standards that are used for security of media infrastructure based on Transport Layer Security (TLS) and Secure Real-time Transport Protocol (SRTP).

Transport CIS Security Services

Conditional

Securing the MN Media infrastructure can be done in several ways and that the selection of the appropriate method is to be done during the mission planning. For this specific method, the following standard apply

• IETF RFC 3711 - The Secure Real-time Transport Protocol (SRTP)
• IETF RFC 4568 - Session Description Protocol (SDP) Security Descriptions for Media Streams
• IETF RFC 5246 - Transport Layer Security (TLS)The Transport Layer Security (TLS) Protocol Version 1.2
• IETF RFC 7919 - Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)

Note that securing the MN Media infrastructure can be done in several ways and that the selection of the appropriate method is to be done during the mission planning.

FMN Spiral 3.0 IPSec-based Media Infrastructure Security Profile

The IPSec-based Media Infrastructure Security Profile provides security standards that are used for security of media infrastructure based on Internet Protocol Security (IPSec).

Network Access Control Services,

Infrastructure CIS Security Services

Conditional

Securing the MN Media infrastructure can be done in several ways and that the selection of the appropriate method is to be done during the mission planning. For this specific method, the following standard apply.

• IETF RFC 7296 - Internet Key Exchange Protocol Version 2 (IKEv2)
• IETF RFC 4303 - IP Encapsulating Security Payload (ESP)
• IETF RFC 4754 - IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA)
• IETF RFC 5903 - Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2
• IETF RFC 7427 - Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)
• IETF RFC 7670 - Generic Raw Public-Key Support for IKEv2

FMN Spiral 3.0 Media Infrastructure Taxonomy Profile

The Media Infrastructure Taxonomy Profile provides guidance and taxonomy for media infrastructures.

Audio-based Communication Services,

Video-based Communication Services

Optional

• IETF RFC 5853 - Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
• IETF RFC 7092 - A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents
• IETF RFC 7656 - A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources

FMN Spiral 3.0 Calendaring Exchange Profile

The calendaring exchange profile provides standards and guidance for the exchange Meeting Requests, Free/Busy information as well as Calendar sharing implemented by CUA software. The focus of this standard is on the exchange of the aforementioned information items and does not cover other typical features found in collaboration software, e.g. chat or workflows.

Calendaring and Scheduling Services

Mandatory

• IETF RFC 5545 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
• IETF RFC 5546 - iCalendar Transport-Independent Interoperability Protocol (iTIP)
• IETF RFC 6047 - iCalendar Message-Based Interoperability Protocol (iMIP)

RFC 5545 is required in order to allow a vendor independent representation and exchange of calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.RFC 5546 defines the scheduling methods that permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling.

FMN Spiral 3.0 Formatted Messages for SA Profile

The Formatted Messages Profile for Situational Awareness provides standard for formatted messages that are typically used in military operations in support of Situational Awareness. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or in standardized voice procedures, e.g. MEDEVAC Requests.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services

Mandatory

Procedures for Situational Awareness require the following messages: Events: Incident Report (INCREP – A078)Incident Spot Report (INCSPOTREP – J006)Troops in Contact SALTA Format (SALTATIC – A073)Search and Rescue Incident Report (SARIR)EOD Incident Report (EODINCREP - J069) / EO Incident Report (EOINCREP)Events Report (EVENTREP - J092) Tasks and Orders: Airspace Control Order (ACO - F011)Air Tasking Order (ATO - F058) Features: Killbox Message (KILLBOX - F083)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

FMN Spiral 3.0 Formatted Messages for MEDEVAC Profile

The Formatted Messages Profile provides standard for formatted messages that are typically used for C2 of Medical Evacuation missions. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or in standardized voice procedures.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services

Mandatory

C2 of MEDEVAC Missions requires the following messages: Situational Awareness: Incident Report (INCREP – A078)Incident Spot Report (INCSPOTREP – J006)Troops in Contact SALTA Format (SALTATIC A073) Requests: Medical Evacuation Request (MEDEVAC – A012)Mechanism Injury Symptoms Treatment (MIST AT, supplement to A012)Diving Accident (DIVEACC – N019)Evacuation Request (EVACREQ – N096)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue
• NATO AJMedP-2 Ed A Ver 1 - Allied Joint Medical Doctrine For Medical Evacuation
• NATO ATP-97 Ed A Ver 1 - NATO Land Urgent Voice Messages (LUVM) Pocket Book

The following set of APP-11 messages should be supported

• Presence Report (PRESENCE)
• Enemy Contact Report (ENEMY CONTACT REP)
• Search and Rescue Incident Report (SARIR)
• Events Report (EVENTREP)
• Situation Report (SITREP)
• Friendly Force Information (FFI)

FMN Spiral 3.0 Formatted Messages for ISR Profile

The Formatted Messages Profile provides standard for formatted messages that are typically used to exchange Intelligence, Surveillance, and Reconnaissance (ISR) products in military operations. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or for publication as files on websites. In addition, some of these formatted messages are also supported by federated ISR Libraries.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services,

Web Hosting Services,

Disseminate JISR Products

Mandatory

To support the exchange of information needed to govern and facilitate the collection of Intelligence, Surveillance and Reconnaissance (ISR) information and production of intelligence the following message formats defined in APP-11 MUST be supported (MTF Identifier, MTF Index Ref Number): Intelligence Request (INTREQ, J021)Information Requirement Management & Collection Management Exchange (ICE, J033)Information Requirement Management & Collection Management Exchange (ICE, J033)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Recommended

The following XML Schema defined by MAJIIC 2 SHOULD be supported: ISR Spot Report (ISRSPOTREP) This report is to be used for quick reporting allowing a free-text description of the results. MAJIIC 2 Bravo.1

Mandatory

To support the sharing of JISR Products the following message formats defined in various AEDPs MUST be supported: ISR TrackMeasurement and Signature Intelligence Report (MASINTREP)ImageryGround Moving Target Indicator (GMTI)Motion Imagery Corrigendum to FMN Spiral 3 Standard Profile: AEDP-08 Ed. 3 has been replaced by NNSTD MISP-2015.1 with STANAG 4609 Ed 4.

• NATO AEDP-12 Ed A Ver 1 - NATO Intelligence, Surveillance And Reconnaissance Tracking Standard
• NATO AEDP-16 (Study) - NATO standardization of measurement and signature intelligence (MASINT) Reporting
• NATO AEDP-04 Ed 2 Ver 1 - NATO Secondary Imagery Format (NSIF) STANAG 4545 Implementation Guide
• NATO AEDP-07 Ed 2 Ver 1 - NATO Ground Moving Target Indicator (GMTI) Format STANAG 4607 Implementation Guide
• NATO MISP-2015.1 - US Motion Imagery Standards Board (MISB) - Motion Imagimary Standards Profile-2015.1

Mandatory

To support the sharing of JISR Products the following message formats defined in APP-11 and STANAG 3377 MUST be supported (MTF Identifier, MTF Index Ref Number): Target Track Report (TRACKREP, J071)Mission Report (MISREP, F031)Inflight Report (INFLIGHTREP, J009)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue
• NATO STANAG 3377 Ed 6 - Air Reconnaissance Intelligence Report Forms

FMN Spiral 3.0 Formatted Messages for Intelligence Profile

The Formatted Messages Profile provides standard for formatted messages that are typically used to exchange Intelligence Products in military operations. These formatted messages may be used as payload/attachment in combination with various transport mechanisms such as informal messaging (e-mail), text collaboration (chat) or for publication as files on websites.

Informal Messaging Services,

Audio-based Communication Services,

Text-based Communication Services,

Web Hosting Services

Mandatory

To support exploitation the following APP-11 message formats MUST be supported (MTF Identifier, MTF Index Ref Number): Air Intelligence Report (AIRINTREP, F001)Counter-Intelligence and Security Report (CIINTREP, J112)Counter-Intelligence and Security Summary (CIINTSUM, J113)Counter-Intelligence and Security Supplementary Report (CISUPINTREP, J115)Detailed Document Report (DEDOCREP, J089)First Hostile Act Report (First Hostile Act)Intelligence Report (INTREP, J110)Intelligence Summary (INTSUM, J111)Maritime Intelligence Report (MARINTREP, J016)Maritime Intelligence Summary (MARINTSUM, J015)Supplementary Intelligence Report (SUPINTREP, J114)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Mandatory

To support the exchange of Intelligence Products the following AJP-2.5 message formats MUST be supported (MTF Identifier): Human Intelligence Report (HUMINTREP)Human Intelligence Summary (HUMINTSUM)Interrogation Report (INTGREP)

• NATO AJP-2.5 Ed A - Captured Persons, Materiel And Documents

Mandatory

To support the exchange of information needed to govern and facilitate the collection of Intelligence, Surveillance and Reconnaissance (ISR) information and production of intelligence the following message formats defined in APP-11 MUST be supported (MTF Identifier, MTF Index Ref Number): Intelligence Request (INTREQ, J021)Information Requirement Management & Collection Management Exchange (ICE, J033)

• NATO APP-11 (Study) Ed D Ver 2 - NATO Message Catalogue

Recommended

To support exploitation the following MAJIIC 2 message formats SHOULD be supported Electronic Order of Battle (EOB)Pentagram Report (PentagramREP)MAJIIC 2 Bravo.1

FMN Spiral 3.0 Video-based Collaboration Service Profile

The Video-based Collaboration Profile provides standards and guidance for the implementation and configuration of Video Tele Conferencing (VTC) systems and services in a federated mission network.

Video-based Communication Services

Mandatory

The following standards are required for audio coding in VTC.

• ITU-T G.722.1 (2005) Corrigendum 1 (06/08) - Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss
• ITU-T G.711 - Pulse code modulation (PCM) of voice frequencies

Mandatory

The following standards are required for video coding in VTC.

• ITU-T H.264 - Advanced video coding for generic audiovisual services
• IETF RFC 6184 - RTP Payload Format for H.264 Video

Conditional

Not required at this time, but when available it can be implemented between dedicated network segments after approval from the MN administrative authority.

• IETF RFC 4582 - The Binary Floor Control Protocol (BFCP)

It Is recommended that dynamic port ranges are constrained to a limited and agreed number. This is an activity that needs to be performed at the mission planning stage. Different vendors have different limitations on fixed ports. However common ground can always be found.As a Minimum G.722.1 is to be used. Others are exceptions and need to be agreed by the MN administrative authority for video calls.

FMN Spiral 3.0 Secure Voice Service Profile

The Secure Voice Profile provides standards and guidance for the facilitation of secure telephony and other protected audio-based collaboration on federated mission networks.

Audio-based Communication Services

Optional

SCIP Network Standards for operation over other network types

• CIS3 C&IP SCIP-214 - Network-Specific Minimum Essential Requirements (MERs) for SCIP Devices, rev.1.2
• CIS3 C&IP SCIP-215 - U.S. SCIP/IP Implementation Standard and MER Publication rev.2.2
• CIS3 C&IP SCIP-216 - Minimum Essential Requirements (MER) for V.150.1 Gateways Publication rev.2.2

Mandatory

SCIP Secure Applications

• CIS3 C&IP SCIP-233.501 - Secure MELP(e) Voice rev.1.1
• CIS3 C&IP SCIP-233.502 - Secure G.729D Voice Specification Rev. 1.1.

Mandatory

SCIP Signaling Plan and Negotiation

• CIS3 C&IP SCIP-210 - SCIP Signalling Plan rev.3.3
• CIS3 C&IP SCIP-233.350 - Interoperable Terminal Priority (TP) Community of Interest (COI) Specification rev.1.0

Mandatory

SCIP Network Standards for operation over VoIP RTP

• CIS3 C&IP SCIP-214.2 - SCIP over RTP rev.1.0
• CIS3 C&IP SCIP-214.3 - Securing SIP Signaling - Use of TLS with SCIP

AComP-5068 Secure Communications Interoperability Protocol (SCIP) Edition A Version 1 provides further guidance for the implementation of SCIP specifications.

FMN Spiral 3.0 Informal Messaging Profile

The Informal Messaging Profile provides standards and guidance for SMTP settings and the marking of informal messages.

Informal Messaging Services

Mandatory

Regarding Simple Mail Transfer Protocol (SMTP), the following standards are mandated for interoperability of e-mail services within the Mission Network.

• IETF RFC 5321 - Simple Mail Transfer Protocol
• IETF RFC 1870 - SMTP Service Extension for Message Size Declaration
• IETF RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes
• IETF RFC 2920 - SMTP Service Extension for Command Pipelining
• IETF RFC 3207 - MTP Service Extension for Secure SMTP over Transport Layer Security (TLS)
• IETF RFC 3461 - Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
• IETF RFC 4954 - SMTP Service Extension for Authentication

Informal messages must be marked in the message header field Keywords (IETF RFC 2822) and firstline-of-text in the message body in accordance with the markings defined in the Security Policy in effect.TLS with mutual authentication is mandatory for all SMTP communications. Detailed TLS protocol requirements are specified in the 'Service Interface Profile for Transport Layer Security'.

FMN Spiral 3.0 Content Encapsulation

The Content Encapsulation Profile provides standards and guidance for content encapsulation within bodies of internet messages, following the Multipurpose Internet Mail Extensions (MIME) specification.

Informal Messaging Services

Mandatory

MIME Encapsulation

• IETF RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
• IETF RFC 2046 - Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
• IETF RFC 2047 - Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text
• IETF RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Example
• IETF RFC 4288 - Media Type Specifications and Registration Procedures
• IETF RFC 6152 - SMTP Service Extension for 8-bit MIME Transport

Mandatory

Media and Content Types:

• IETF RFC 1896 - The text/enriched MIME Content-type
• IETF RFC 1866 - Hypertext Markup Language - 2.0

FMN Spiral 3.0 Character Encoding Service Profile

The Character Encoding Profile provides standards and guidance for the encoding of character sets.

Web Hosting Services,

Informal Messaging Services,

Text-based Communication Services,

Content Management Services

Mandatory

Use of UTF-8 for complete Unicode support, including fully internationalized addresses is mandatory.

• IETF RFC 3629 - UTF-8, a transformation format of ISO/IEC 10646

FMN Spiral 3.0 File Format Service Profile

The File Format Profile provides standards and guidance for the collaborative generation of spreadsheets, charts, presentations and word processing documents.

Web Hosting Services,

Informal Messaging Services

Recommended

For word processing documents, spreadsheets and presentations.

• ISO/IEC 26300 - Open Document Format (ODF) for Office Applications (OpenDocument) v1.0
• ISO/IEC 26300-1 - Open Document Format for Office Applications (OpenDocument) v1.2 -- Part 1: OpenDocument Schema

Mandatory

For still image coding.

• ISO/IEC 10918-1 - Digital compression and coding of continuous-tone still images: Requirements and guidelines
• ISO/IEC 10918-3 - Digital compression and coding of continuous-tone still images: Extensions

Mandatory

For document exchange, storage and long-term preservation.

• ISO 19005-1 - Electronic document file format for long-term preservation -- Part 1: Use of PDF 1.4 (PDF/A-1)
• ISO 19005-2 - Electronic document file format for long-term preservation -- Part 2: Use of ISO 32000-1 (PDF/A-2)
• ISO 32000-1 - Document management — Portable document format — Part 1: PDF 1.7

Recommended

For document exchange

• ISO 32000-2 - Document management — Portable document format — Part 2: PDF 2.0

Mandatory

For word processing documents, spreadsheets and presentations.

• ISO/IEC 29500-1 - Office Open XML File Formats -- Part 1: Fundamentals and Markup Language Reference

ISO/IEC 29500 and ISO/IEC 26300 are both open document formats for XML-based saving and exchanging word processing documents, spreadsheets and presentations. They differ in design and scope.

FMN Spiral 3.0 Internationalization Service Profile

The Internationalization Profile provides standards and guidance for the design and development of content and (web) applications, in a way that ensures it will work well for, or can be easily adapted for, users from any culture, region, or language.

Web Hosting Services

Recommended

• W3C Character Model for the WWW 1.0 - Character Model for the World Wide Web 1.0: Fundamentals
• W3C ITS 1.0 - Internationalization Tag Set (ITS) Version 1.0
• W3C ITS 2.0 - Internationalization Tag Set (ITS) Version 2.0
• W3C Ruby Annotation - Ruby Annotation

Best practices and tutorials on internationalization can be found at http //www.w3.org/International/articlelist.

FMN Spiral 3.0 Geospatial Web Feeds Service Profile

The Geospatial Web Feeds Profile provides standards and guidance for the delivery of geospatial content to web sites and to user agents, including the encoding of location as part of web feeds. Feed processing software is required to either read or ignore these extensions and shall not fail if these extensions are present, so there is no danger of breaking someone's feed reader (or publisher) by including this element in a feed.

Web Hosting Services

Mandatory

GeoRSS Simple encoding for "georss:point", "georss:line", "georss:polygon", "georss:box".

• OGC 11-044 - Geography Markup Language (GML) simple features profile Technical Note v 2.0

Recommended

GeoRSS GML Profile 1.0 a GML subset for point "gml:Point", line "gml:LineString", polygon "gml:Polygon", and box "gml:Envelope". In Atom feeds, location shall be specified using Atom 1.0's official extension mechanism in combination with the GeoRSS GML Profile 1.0 whereby a "georss:where" element is added as a child of the element.

• OGC 06-050r3 - An Introduction to GeoRSS: A Standards Based Approach for Geo-enabling RSS feeds, v1.0.0

Geography Markup Language (GML) allows to specify a coordinate reference system (CRS) other than WGS84 decimal degrees (lat/long). If there is a need to express geography in a CRS other than WGS84, it is recommended to specify the geographic object multiple times, one in WGS84 and the others in your other desired CRSs.For backwards compatibility it is recommended to also implement RSS 2.0.

FMN Spiral 3.0 Web Map Tile Service Profile

The Web Map Tile Service standard and guidance provides a standardized protocol for serving pre-rendered georeferenced map tiles over the Internet.

Geospatial Web Map Tile Services

Mandatory

version 1.0

• OGC 11-044 - Geography Markup Language (GML) simple features profile Technical Note v 2.0

Additional implementation guidance

• STANAG 6523 Edition 1
• NCIA Technical Instruction AI TECH 06.02.14 Service Interface Profile for Geospatial Services - Map Rendering Service

FMN Spiral 3.0 Web Feature Service Profile

The Web Feature Service standard and guidance provides a standardized interface for geodata provision in a defined format over a network connection.

Geospatial Web Feature Services

Mandatory

With Corrigendum – version 2.0.2, 07/10/2014

• OGC 09-025r2 - OGC Web Feature Service (WFS) 2.0 Interface Standard With Corrigendum

Additional Implementation Guidance

• STANAG 6523 Edition 1
• DGIWG – 122, DGIWG - Web Feature Service 2.0

FMN Spiral 3.0 Web Map Service Profile

The Web Map Service standard and guidance provides a standardized interface for geodata provision in a defined format over a network connection.

Geospatial Web Map Services

Mandatory

• OGC 06-042 - OpenGIS Web Map Service (WMS) Implementation Specification

Additional Implementation Guidance

• STANAG 6523 Edition 1
• NCIA Technical Instruction AI TECH 06.02.14 Service Interface Profile for Geospatial Services - Map Rendering Service

FMN Spiral 3.0 Geospatial Data Exchange Service Profile

Geospatial data are being produced by different organisations and need to be exchanged between different participants using standardized exchange formats. These datasets would then be loaded into specialised geospatial information systems (GIS) and published via standardized Web Services (e.g. WMS or WMTS for raster data/maps).

Geospatial Services

Mandatory

File based storage and exchange of digital geospatial vector data:

• OGC 07-147r2 - OGC KML 2.2.0

Recommended

File geodatabases store geospatial datasets and can hold any number of these large, individual datasets. File geodatabases can be used across multiple platforms. Users are rapidly adopting file geodatabases in place of using legacy shapefiles.

• OGC 12-128r12 - OGC GeoPackage Encoding Standard Version 1.1

Recommended

File exchange of xdigital raster data:

• US DoD MIL-PRF-89038 - Compressed ARC Digitized Raster Graphics (ADRG)
• NGA MIL-STD-2411 - Raster Product Format
• ISO/IEC 15444-1 - JPEG 2000 image coding system — Part 1: Core coding system

Mandatory

File based storage and exchange of digital geospatial mapping (raster) data.

• OSGEO GeoTIFF Format Specification Revision 1.0 - Geographical Tagged Image File Format (GeoTIFF) Specification Revision 1.0
• OGC 05-047r3 - GML in JPEG 2000 for Geographic Imagery (GMLJP2)

The direct exchange of data (via automated or manual file transfer) is to be considered only in case of limited connectivity (no regular access to the network).Often the exchange of large geospatial (raster) data sets between Geo organizations of different Mission Participants is conducted in proprietary formats such as

• Shapefile (ESRI), technical description athttps //www.esri.com/library/whitepapers/pdfs/shapefile.pdf

• Multi-resolution seamless image database format (MrSID Generation 3), technical description athttps //www.loc.gov/preservation/digital/formats/fdd/fdd000184.shtml. Data in MrSID format could be transformed to GeoTIFF. The JPEG 2000 image compression standard offers many of the same advantages as MrSID, plus the added benefits of being an international standard (ISO/IEC 15444).
• Erdas Compression Wavelet (ECW) which is optimized for aerial and satellite imagery.

FMN Spiral 3.0 Structured Data Service Profile

The Structured Data Profile provides standards and guidance for the structuring of web content on federated mission networks.

Web Hosting Services

Mandatory

General formatting of information for sharing or exchange.

• W3C XML 1.0 (Fith Edition) - eXtensible Markup Language (XML) 1.0 (Fifth Edition)
• IETF RFC 4627 - The application/json Media Type for JavaScript Object Notation (JSON)
• W3C XML Schema Part 1: Structures Ed 2 - XML Schema Part 1: Structures Second Edition
• W3C XML Schema Part 1: Datatypes Ed 2 - XML Schema Part 2: Datatypes Second Edition
• W3C XHTML 1.0 in XML Schema - XHTML™ 1.0 in XML Schema

XML shall be used for data exchange to satisfy those Information Exchange Requirements within a FMN instance that are not addressed by a specific information exchange standard. XML Schemas and namespaces are required for all XML documents.

FMN Spiral 3.0 Web Feeds Service Profile

The Web Feeds Profile provides standards and guidance for the delivery of content to feed aggregators (web sites as well as directly to user agents).

Web Hosting Services

Mandatory

Web content providers must support at least one of the two standards (RSS and/or Atom).

• IETF RFC 4287 - Atom Syndication Format, v1.0
• IETF RFC 5023 - Atom Publishing Protocol
• RSS RSS 2.0 Specification - RSS 2.0 Specification

Mandatory

Receivers of web content such as news aggregators or user agents must support both the RSS and the ATOM standard.

• IETF RFC 4287 - Atom Syndication Format, v1.0
• IETF RFC 5023 - Atom Publishing Protocol
• RSS RSS 2.0 Specification - RSS 2.0 Specification

RSS and Atom documents should reference related OpenSearch description documents via the Atom 1.0 link element, as specified in Section 4.2.7 of RFC 4287.The rel attribute of the link element should contain the value search when referring to OpenSearch description documents. This relationship value is pending IANA registration. The reuse of the Atom link element is recommended in the context of other syndication formats that do natively support comparable functionality.The following restrictions apply

• The type attribute must contain the value application/opensearchdescription+xml.
• The rel attribute must contain the value search.
• The href attribute must contain a URI that resolves to an OpenSearch description document.
• The title attribute may contain a human-readable plain text string describing the search engine.

FMN Spiral 3.0 Web Services Profile

The Web Services Profile provides standards and guidance for transport-neutral mechanisms to address structured exchange of information in a decentralized, distributed environment via web services.

Web Hosting Services

Mandatory

• W3C SOAP 1.1 - Simple Object Access Protocol (SOAP) 1.1
• W3C WSDL 1.1 - Web Service Description Language (WSDL) 1.1
• W3C WSDL 2.0 SOAP 1.1 binding - Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding
• W3C WS-Addressing 1.0 - Core - Web Services Addressing 1.0 - Core

Conditional

• ACM 2002-REST-TOIT - Representational State Transfer (REST)

Mandatory

Provide the elements a web service needs to deliver a suitable UI service, such as remote portlet functionality.

• W3C Cross-Origin Resource Sharing - Cross-Origin Resource Sharing

Recommended

Reliable messaging for web services, describes a protocol that allows messages to be transferred reliably between nodes implementing this protocol in the presence of software component, system, or network failures.

• OASIS WS-ReliableMessaging Ver 1.2 - Web Services Reliable Messaging (WS-ReliableMessaging) Ver 1.2

The preferred method for implementing web-services are SOAP, however, there are many use cases (mashups etc.) where a REST based interface is easier to implement and sufficient to meet the IERs.Restful services support HTTP caching, if the data the Web service returns is not altered frequently and not dynamic in nature. REST is particularly useful for restricted-profile devices such as mobile phones and tablets for which the overhead of additional parameters like headers and other SOAP elements are less.

FMN Spiral 3.0 Web Platform Service Profile

The Web Platform Profile provides standards and guidance to enable web technology on federated mission networks.

Web Hosting Services

Mandatory

• IETF RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
• IETF RFC 7231 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
• IETF RFC 7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
• IETF RFC 7233 - Hypertext Transfer Protocol (HTTP/1.1): Range Requests
• IETF RFC 7234 - Hypertext Transfer Protocol (HTTP/1.1): Caching
• IETF RFC 7235 - Hypertext Transfer Protocol (HTTP/1.1): Authentication
• IETF RFC 2817 - Upgrading to TLS Within HTTP/1.1
• IETF RFC 3986 - Uniform Resource Identifiers (URI): Generic Syntax
• IETF RFC 1738 - Uniform Resource Locators (URL)

HTTP MAY (only) be used as the transport protocol for CRL and AIA exchange between all service providers and consumers (unsecured HTTP traffic). HTTPS MUST be used as the transport protocol between all service providers and consumers to ensure confidentiality requirements (secured HTTP traffic). HTTP traffic shall use port 80 by default. HTTPS traffic shall use port 443 by default

FMN Spiral 3.0 Web Content Service Profile

The Web Content Profile provides standards and guidance for the processing, sharing and presentation of web content on federated mission networks. Web presentation services must be based on a fundamental set of basic and widely understood protocols, such as those listed below. Recommendations in the FMN Spiral 2 Service Interface Profile for Web Applications are intended to improve the experience of Web applications and to make information and services available to users irrespective of their device and Web browser. However, it does not mean that exactly the same information is available in an identical representation across all devices: the context of mobile use, device capability variations, bandwidth issues and mobile network capabilities all affect the representation. Some services and information are more suitable for and targeted at particular user contexts. While services may be most appropriately experienced in one context or another, it is considered best practice to provide as reasonable experience as is possible given device limitations and not to exclude access from any particular class of device, except where this is necessary because of device limitations.

Web Hosting Services

Mandatory

Publishing information including text, multi-media, hyperlink features, scripting languages and style sheets on the network.

• IETF RFC 2854 - The 'text/html' Media Type
• W3C APIs for HTML5 and XHTML - HTML5 - A vocabulary and associated APIs for HTML and XHTML (2014)
• IETF RFC 4329 - Scripting Media Types
• W3C CSS Media Queries - CSS Media Queries
• W3C CSS Selectors Level 3 - CSS Selectors Level 4

Mandatory

Providing a common style sheet language for describing presentation semantics (that is, the look and formatting) of documents written in markup languages like HTML.

• W3C REC-CSS2 - Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
• W3C CSS Style Attributes - CSS Style Attributes
• W3C CSS Namespaces Module Level 3 - CSS Namespaces Module Level 3
• W3C CSS Color Module Level 3 - CSS Color Module Level 3

To enable the use of web applications by the widest possible audience, web applications shall be device independent and shall be based on HTML5 standards and criteria for the development, delivery and consumption of Web applications and dynamic Web sites. HTML5 is a new version of the mark-up language HTML, with new elements, attributes, and behaviours (data format) and it contains a larger set of associated technologies such as CSS 3 and JavaScript that allows more diverse and powerful Web sites and applications.Web applications will not require any browser plug-ins on the client side as some organizations or end user devices do not allow the use of Java Applets or proprietary extensions such as Silverlight (Microsoft), Flash (Adobe) or Quick Time (Apple). Implementers shall use open standard based solutions (HTML5 / CSS3) instead.The requirements defined in the FMN Spiral 2 Service Interface Profile for Web Applications are mandatory for all web content consumers (browsers) and are optional for web content providers. It is expected that in the future FMN Spiral Specifications they will become mandatory also for the web content providers.

FMN Spiral 3.0 Federated Web Authentication Profile

Authentication Services

Mandatory

• OASIS saml - OASIS Security Services (SAML)
• IETF RFC 5322 - Internet Message Format
• IETF RFC 3986 - Uniform Resource Identifiers (URI): Generic Syntax
• IETF RFC 2256 - A summary of the X.500(96) User Schema for Use with LDAPv3
• IETF RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
• IETF RFC 4519 - Lightweight Directory Access Protocol (LDAP) - Schema for User Applications

The Identity Providers must support the following components of the SAML 2.0 specification

• Profiles
  • Web Browser SSO Profile
  • Single Logout Profile
• Bindings
  • HTTP Redirect Binding
  • HTTP POST Binding.