Title
FMN Spiral 3 - Standards Profile

Reference document

Org
FMN
Pubnum
Date
2018-10-26
Version
3
Title
FMN Spiral 3 Standards Profile

Subprofiles

Status

URI

History

Flag Date RFC Version
added 2018-10-30 11-57 12.0
UUID
8e1dd177-8022-481c-a26b-06040e1d3b6a

FMN Spiral 3 - Standards Profile

FMN Spiral 3 Communications and Networking Profile

FMN Spiral 3 Communications Profile

Service Standard Implementation Guidance

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.

Mandatory

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

Mandatory

Standards for IP version 4 (IPv4) over Ethernet

Mandatory

Mandatory

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

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.

Mandatory

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

Optional

Mandatory

The following standards shall apply for all IP interconnections.

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.

Mandatory

The following standard applies for unicast routing.

Mandatory

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

Conditional

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

Recommended

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

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.

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

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.

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

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).

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.

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 Networking Profile

Service Standard Implementation Guidance

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

Optional

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

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.

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

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.

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

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

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 Communities of Interest Profile

FMN Spiral 3 Intelligence Profile

Service Standard Implementation Guidance

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.

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.)

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.

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.
Service provider must identify which interfaces/patterns they support as a part of the federation process.

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)

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.

    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)

    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)

    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)

    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)

    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)

      FMN Spiral 3 Situational Awareness Profile

      Service Standard Implementation Guidance

      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.

      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

        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

        Mandatory

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

        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

        Mandatory

        The implementation of the following message types is mandatory

        • Contact Report (CTC)
        • Enhanced Contact Report (XCTC),
        • Overlay Message (OVLY2, OVLY3),
        The implementation of the following message types is optional
        • Area of Interest Filter (AOI),
        • FOTC Situation Report,
        • Group Track Message (GROUP),
        • Operator Note (OPNOTE),
        • PIM Track (PIMTRACK).
        These messages can be used for other C2 functions.For interconnecting C2 Systems and their RMP Services, the implementation of the following transport protocol to share OTH-T GOLD messages is mandatory
        • TCP (connect, send, disconnect) - default port 2020
        End-users that do not have RMP Applications MAY generate OTH-T GOLD messages manually and transmit them via eMail/SMTP (see also Message Text Format messaging).

        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)

        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"

        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.
        The suite of guidance documents includes the MIP Operating Procedures (MOP), which provides technical procedures for configuration/operation of MIP 3.1 interfaces in a Coalition environment.The Land C2 Information Exchange profile should be used primarily for the exchange of Battlespace Objects; this profile is not intended to support high volume, high frequency updates such as Friendly Force Tracking (FFT).Likewise, the Land C2 Information Exchange profile is not designed to support the exchange of data over tactical bearers (limited capacity and intermittent availability) across network boundaries - STANAG 4677 would be more appropriate.

        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.

        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

        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 SMC Profile

        Service Standard Implementation Guidance

        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.

        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.

          Mandatory

          FMN Spiral 3 Procedural Instructions for Service Management and Control

            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.

            Mandatory

            FMN Spiral 3 Service Interface Profile for Service Management and Control

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

              FMN Spiral 3 Human-to-Human Communications Profile

              FMN Spiral 3 Unified Collaboration Profile

              FMN Spiral 3 Audio-based Collaboration Profile

              Service Standard Implementation Guidance

              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.

              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 Basis Text-based Collaboration Profile

              Service Standard Implementation Guidance

              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.

              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.

              FMN Spiral 3 Numbering Plans Profile

              Service Standard Implementation Guidance

              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

              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).

              FMN Spiral 3 Call Signaling Profile

              Service Standard Implementation Guidance

              FMN Spiral 3.0 Standalone Voice Services Call Signaling Profile

              Audio-based Communication Services

              Mandatory

              FMN Spiral 3.0 Standalone VTC Services Call Signaling Profile

              Video-based Communication Services

              Mandatory

              FMN Spiral 3.0 Unified Voice and VTC Services Call Signaling Profile

              Audio-based Communication Services,

              Video-based Communication Services

              Mandatory

              FMN Spiral 3 Unified Audio and Video Profile

              Service Standard Implementation Guidance

              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.

              Mandatory

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

              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

              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

              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

              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.

              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

              FMN Spiral 3 Calendaring Exchange Profile

              Service Standard Implementation Guidance

              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

              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 Formatted Messages Profile

              Service Standard Implementation Guidance

              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)

              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)

              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)

              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.

                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)

                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)

                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)

                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)

                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 Video-based Collaboration Profile

                  Service Standard Implementation Guidance

                  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.

                  Mandatory

                  The following standards are required for video coding in VTC.

                  Conditional

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

                  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 Secure Voice Profile

                  Service Standard Implementation Guidance

                  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

                  Mandatory

                  SCIP Secure Applications

                  Mandatory

                  SCIP Signaling Plan and Negotiation

                  Mandatory

                  SCIP Network Standards for operation over VoIP RTP

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

                  FMN Spiral 3 Informal Messaging Profile

                  Service Standard Implementation Guidance

                  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.

                  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 Content Encapsulation Profile

                  Service Standard Implementation Guidance

                  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

                  Mandatory

                  Media and Content Types:

                  FMN Spiral 3 Information Management Profile

                  Service Standard Implementation Guidance

                  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.

                  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.

                  Mandatory

                  For still image coding.

                  Mandatory

                  For document exchange, storage and long-term preservation.

                  Recommended

                  For document exchange

                  Mandatory

                  For word processing documents, spreadsheets and presentations.

                  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

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

                  FMN Spiral 3 Geospatial Profile

                  Service Standard Implementation Guidance

                  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".

                  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.

                  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

                  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

                  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

                  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:

                  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.

                  Recommended

                  File exchange of xdigital raster data:

                  Mandatory

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

                  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
                  Or proprietary compression image formats such as
                  • 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 Web Hosting Profile

                  Service Standard Implementation Guidance

                  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.

                  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).

                  Mandatory

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

                  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

                  Conditional

                  Mandatory

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

                  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.

                  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

                  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.

                  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.

                  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 Web Authentication Profile

                  Service Standard Implementation Guidance

                  FMN Spiral 3.0 Federated Web Authentication Profile

                  Authentication Services

                  Mandatory

                  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.