archive.nisp.nw3.dk · nisp volume 2 adatp-34(h)-rev3 - iii - table of contents 1. introduction

NISP Volume 2 ADatP-34(H)-REV3

Allied Data Publication 34

(ADatP-34(H))

NATO InteroperabilityStandards and Profiles

Volume 2

Agreed Standards

22 August 2014

C3B Interoperability Profiles Capability Team


- iii -

Table of Contents

1. Introduction .......................................................................................................................... 11.1. Scope ......................................................................................................................... 1

2. Reference Models: Transition from Platform Centric to Service Oriented Models ............. 33. Standards .............................................................................................................................. 5

3.1. Introduction ............................................................................................................... 53.1.1. Releasability Statement .................................................................................. 7

3.2. Comparison to former NISP Versions ...................................................................... 73.3. Technical Services ..................................................................................................... 7

3.3.1. List of Core Enterprise Services .................................................................... 83.3.2. Community Of Interest (COI) Services ....................................................... 893.3.3. Communications Services .......................................................................... 126

4. Profiles .............................................................................................................................. 1634.1. Introduction ............................................................................................................ 163

4.1.1. Profiles derived from NATO Operations ................................................... 1634.1.2. Profiles derived from NATO member nations ........................................... 163

4.2. Profile Specifications ............................................................................................ 1634.2.1. NRF Generic Interface Profile ................................................................... 1644.2.2. Tactical ESB - Profile ................................................................................ 1644.2.3. AMN - Profile ............................................................................................ 1644.2.4. CES - Profile .............................................................................................. 1644.2.5. Service Interface Profile (SIP) Template Document .................................. 1644.2.6. FMN - Profile ............................................................................................. 164

Index ...................................................................................................................................... 165

ADatP-34(H)-REV3 NISP Volume 2

- iv -

This page is intentionally left blank


- v -

List of Figures

3.1. C3 Classification Taxonomy ............................................................................................. 6


- vi -



- 1 -

1. INTRODUCTION

001. Volume 2 of the NISP focuses on agreed interoperability standards and profiles. This isthe short-term step describing the state-of-the-art of NATO systems today and the frameworkfor new systems actually under procurement or specification.

002. The NISP references Standards from different standardization bodies. In the case ofa ratified STANAG, NATO Standardization procedures apply. The NISP only referencesthese STANAG’s without displaying the country-specific reservations. The country-specificreservations can be found in the NATO Standardization Agency Standards database.

003. The Combined Communications Electronics Board (CCEB) nations will use NISP Volume2 Chapter 3 and Section 3.3 tables to publish the interoperability standards for the CCEB underthe provisions of the NATO-CCEB List of Understandings (LoU)1. For the CCEB Chapter 4 isonly applicable to the CCEB Nations when taking part in NATO lead operations.

1.1. SCOPE

004. The scope of this volume includes:

• Identifying the standards, profiles and technologies that are relevant to a service orientedenvironment,

• Describing the standards, profiles, and technologies to support federation.

1References:NATO Letter AC/322(SC/5)L/144 of 18 October 2000, CCEB Letter D/CCEB/WS/1/16 of 9 November2000, NATO Letter AC/322(SC/5)L/157 of 13 February 2001


- 2 -



- 3 -

2. REFERENCE MODELS: TRANSITION FROM PLATFORMCENTRIC TO SERVICE ORIENTED MODELS

005. Information technology has undergone a fundamental shift from platform-orientedcomputing to network-oriented computing. Platform-oriented computing emerged with thewidespread proliferation of personal computers and the global business environment. Thesefactors and related technologies have created the conditions for the emergence of network-oriented computing. This shift from platform to network is what enables the more flexible andmore dynamic network-oriented operation. The shift from viewing NATO and partner Nationsas independent to viewing them as part of a continuously adapting network ecosystem fostersa rich information sharing environment.

006. This shift is most obvious in the explosive growth of the Internet, intranets, andextranets. Internet users no doubt will recognize transmission control protocol/internet protocol(TCP/IP), hypertext transfer protocol (HTTP), hypertext markup language (HTML), Webbrowsers, search engines, and Java1 Computing. These technologies, combined with high-volume, high-speed data access (enabled by the low-cost laser) and technologies for high-speed data networking (hubs and routers) have led to the emergence of network-orientedcomputing. Information “content” now can be created, distributed, and easily exploited acrossthe extremely heterogeneous global computing environment. The “power” or “payoff” ofnetwork-enabled computing comes from information-intensive interactions between very largenumbers of heterogeneous computational nodes in the network, where the network becomesthe dynamic information grid established by interconnecting participants in a collaborative,coalition environment. At the structural level, network-enabled warfare requires an operationalarchitecture to enable common processes to be shared.

007. One of the major drivers for supporting net-enabled operations is Service-OrientedArchitectures (SOA). SOA is an architectural style that leverages heterogeneity, and thusinherently platform-neutral. It is focused on the composition of Services into flexible processesand is more concerned with the Service interface and above (including composition metadata,security policy, and dynamic binding information), more so than what sits beneath theabstraction of the Service interface. SOA requires a different kind of platform, because runtimeexecution has different meanings within SOA. SOA enables users and process architects tocompose Services into processes, and then manage and evolve those processes, in a declarativefashion. Runtime execution of such processes is therefore a metadata-centric operation of adifferent kind of platform -- a Service-oriented composite application platform.

008. Network-enabled operations are characterized by new concepts of speed of command andself-synchronization.

009. The most important SOA within an enterprise is the one that links all its systems. Existingplatforms can be wrapped or extended in order to participate in a wider SOA environment.NATO use of the NISP will provide a template for new systems development, as well as assistin defining the path for existing systems to migrate towards net-enabled operations.

1Registered Trademark of SUN Microsystems, INC.


- 4 -



- 5 -

3. STANDARDS

3.1. INTRODUCTION

010. This purpose of this chapter is to specify the NISP standards. The document organizes thesestandards into five service areas, following NATO's C3B Classification Taxonomy, as publishedon June 15, 2012. A graphical representation of this taxonomy is given in the followingfigure and a description of it can be obtained at: http://tide.act.nato.int/tidepedia/index.php?title=NATO_C3_Classification_Taxonomy


- 6 -

C3 Classification Taxonomy

Operational Context

Missions and Operations

Policy andGuidance

Strategic Concept Political Guidance Military Guidance Allied Publications C3 Policies

MissionTypes

Collective Defence (CD)

Consequence Management (CM)

Conflict Prevention (CP)

Counter Terrorism (Failed State) (CT(FS))

Counter Terrorism (State Sponsored Covert) (CT(SSC))

Support to Disaster Relief (DR) Extraction Operation (EOP)

Enforcement of Sanctions and Embargoes (ESE)

Peace Enforcement (PE)

Peacekeeping (PK)

Support to Humanitarian Assistance (SHA)

Anti-Terrorism (AT)

Peacemaking (PM)

Peacebuilding (PB)

Support of Non-Combatant Evacuation Operations (NEO)

Military Aid/Support to Civil Authorities (SCA)

Permanent Tasks

TasksCD Tasks CM Tasks CT (FS) Tasks CT (SSC) Tasks PK Tasks PE Tasks CP Tasks SHA Tasks DR Tasks EOP Tasks ESE Tasks

Operational Capabilities

Capability Hierarchy,Codes and Statements

Prepare Project Engage Sustain Protect Inform C3

BusinessProcesses

IA Processes SMC Processes Governance Processes Management Processes Consultation Processes Cooperation Processes Mission Threads Support Processes

InformationProducts

IA Information SMC Information Intent & Guidance Rules & Measures Plans Tasking & Orders Situational Awareness Resource Status Requests & Responses

Communication and Information Systems (CIS) Capabilities

User-Facing Capabilities

UserAppliances

UserApplications

IA Applications SMC Applications

Joint COI Applications

Air COI Applications

Land COI Applications

Maritime COIApplications

Space COI Applications

Special Operations COIApplications

JISR COI Applications

Logistics COIApplications

EW COI Applications

Environmental COIApplications

Missile Defence COIApplications

CIMIC COI Applications

CBRN COI Applications

ETEE COI Applications

CIS COI Applications

Modeling and SimulationCOI Applications

Generic Applications

Technical Services

InformationSystems

Equipment

CommunicationsEquipment

Community Of Interest (COI) Services

COI-SpecificServices

COI-Specific IAServices

COI-Specific SMCServices

Joint COI Services

Air COI Services

Land COI Services

Maritime COI Services

Space COI Services

Special Operations COIServices

JISR COI Services

Logistics COI Services

EW COI Services

Environmental COIServices

Missile Defence COIServices

CIMIC COI Services

CBRN COI Services

ETEE COI Services

Modeling and SimulationCOI Services

CIS COI Services

COI-EnablingServices

COI-Enabling IAServices

COI-Enabling SMCServices

Operational PlanningServices

Tasking and OrderServices

Situational AwarenessServices

Business SupportServices

Modeling and SimulationServices

Core Enterprise Services

Enterprise SupportServices

Enterprise Support IAServices

Enterprise SupportSMC Services

Unified Communication and Collaboration Services Information Management Services Geospatial Services

SOA PlatformServices

SOA Platform IAServices

SOA Platform SMCServices

Message-orientedMiddleware Services

Web Platform ServicesInformation Platform

ServicesComposition Services Mediation Services

InfrastructureServices

Infrastructure IAServices

Infrastructure SMCServices

Infrastructure Processing Services Infrastructure Storage Services Infrastructure Networking Services

Communications Services

CommunicationsAccess Services

CommunicationsAccess IA Services

CommunicationsAccess SMC Services

Analogue Access Services

Digital (Link) Access Services

Message-based Access Services

Circuit-based Access Services

Frame-based Access Services

Packet-based Access Services

Multimedia Access Services

TransportServices

Transport IA ServicesTransport SMC

ServicesEdge Transport Services Core Network Services Aggregation Services Broadcast Services Distribution Services

TransmissionServices

Transmission IAServices

Transmission SMCServices

Wired Local Area TransmissionServices

Wired Metropolitan Area TransmissionServices

Wired Wide Area TransmissionServices

Wireless LOS Static TransmissionServices

Wireless LOS Mobile TransmissionServices

Wireless BLOS Static TransmissionServices

Wireless BLOS Mobile TransmissionServices

IA SMC Groupings Baseline 1.0 - Friday, 15 June 2012

Figure 3.1. C3 Classification Taxonomy

011. This section describes the role and requirements of each service area, and presents allassociated standards in tabular form. The tables refine each service area into one or more service


- 7 -

categories, with service components mapping to one or more mandatory, emerging or fadingcategories (see NISP vol.1). A remarks column provides optional supplementary informationon each standard plus CCEB-specific information.

3.1.1. Releasability Statement

012. In principle, NISP includes only standards/STANAGs/documents, which are generallyavailable for NATO/NATO member nations/CCEB.

013. However, a subset of documents are only available for those nations/ organisations, whichare joining a specific mission or are member of a special working group (I-ICWG). Themembership in these activities is outside the scope of NISP.

3.2. COMPARISON TO FORMER NISP VERSIONS

014. In comparison to the former version, this NISP is structured following the C3 ClassificationTaxonomy, as published by the C3B in June 2012. To allow a transformation from the old tothis new structure, automatic tools were used. Nevertheless, not all entries (neither in the old,nor in the new structure) are well placed, as they are artificially assigned to the structure. A pureservice oriented approach will lead to the result that these old entries will disapear in the future,when the relevant systems, where these standards were used, become obsolete.

3.3. TECHNICAL SERVICES

015. Technical services provide fundamental support to service based frameworks both inthe form of information integration and communication services, and in the form of COIindependent general service building blocks.

016. COI services provide more specialized services in order to give the business more specificbusiness benefits within a “domain” or “area of interest”.

017. A COI is a collaborative group of users who have shared goals, interests, missions orbusiness processes that result in information exchange and shared vocabulary.

018. Information services include services that are either made available to all users by theinfrastructure, or are mandatory to be provided by all users, by all providers or by all consumers.Information services also include specification of services of general interest that may bevoluntarily exchanged by any parties on the network. Currently, information services are basedonly on Core Enterprise Services (CES), but may be extended in the future.

019. Any service based framework, such as the Business Process Infrastructure Framework(BPIF), needs to provide a basic set of services that support and facilitate implementation anddeployment of actual business services and processes. Such basic services are usually referredto as Core Enterpise Services.

020. Here we will provide an overview of such CESs in a BPIF context in terms of the waysuch services are categorized. A few examples of CESs in each category is also provided, but a


- 8 -

complete set of well defined core services cannot be provided as it to a large extent will dependon the actual implementation of the BPIF.

021. Core services in a BPIF context are divided into two main categories according to theirprimary role in the implementation of business services and processes.

3.3.1. List of Core Enterprise Services

SUBAREA /SERVICECATEGORY

CAT-EGORY /SUBCAT-EGORY

MANDAT-ORYSTAND-ARDS

EMERGING FADING Remarks

CommunitySecurity Re-quirementsStatement ab-stract, v1.1(NATO:2010)

Used in profile:AMN

Common Cri-teria (ISO/IEC15408-1:2009,-2 to-3:2008)

Procedural doc-ument dealingwith the evalu-ation criteria forIT security.

Guidance on theuse of Com-mon Criteriawithin NATOis providedwith AC/322-D(2010)0043.

Physical char-acteristics(ISO/IEC7810:2003)

Integrated cir-cuit(s) withelectrical con-tacts (ISO/IEC7816:2006)

Base profile,consisting ofparts 1-5)

Interfacebetween thecard aware ap-plications and


- 9 -





cards, PC/SC Specs.v.2.0.1.9:2005

Card-resistance al-lications, JA-VACARDkitv.2.2.2:2006

Contactlesscards (ISO/IEC14443:2008)

Base profile,consisting ofparts 1 - 3.

Java Enter-prise Edi-tion Specific-ation (JAVAEE v.7:2012),(JCP:2012)

Java Stand-ard Edition6 (JAVASE v.6:2006),(JCP:2002)

Java RemoteMethod Invoc-ation (JRMI),(JCP)ed.1.5.0:2004

Java API forXML Pro-cessing(JAXP) v.1.3,(JCP:2004)

Java Namingand Direct-ory Interface(JNDI) ed. 1.2,(SUN:1999)


- 10 -





JNLPv6.0:2011,JCP

JAVA Serv-er Pages JSPv2.1:2009,JCP

JAVA Servletsv3.0:2009,JCP

EnterpriseSupport Ser-vices

Semantics ofBusinessVocabularyand BusinessRules, Vers.1.0 (SBVR);OMG 2008

Unified Com-munication andCollaborationServices

Media Gate-way Con-trol Protocolv3(ITU-TH.248.1:2005)

Protocol formanaging themulti-mediagatewaysbetween circuitswitched andpacket switchednetworks.

SynchronizedMultimedia In-tegration Lan-guage (SMIL3.0):2008(W3C)

Language formultimediaproducts basedon XML.


- 11 -





Advanced Dis-tributed Learn-ing (ADL)(STANAG2591:2013)

Audio-basedCollaborationServices

Packet-basedMultimediaComms Sys-tem (ITU-TH.323:2009)

Used in Pro-files: AMN,FMN

G.722.1C14kHz audiocodec (ITU-TG.722.1 An-nex C:2012)


Rich TextFormat (RTF)v.1.9.1:2007(MS)

Basic docu-ment inter-change format

ASCII Text,ISO 646:1991

For constrainedenvironments

UTF-8 (IETFRFC3629:2003)

Universal TextFormat

Document Ob-ject Model(DOM) Level3:2004 (MS)

DocumentObjectModel(DOM)Level 2(MS)

Basic Docu-ment ObjectModel .

Office XPformats:2003(MS)

Office2000formats:Office XP

Office 2000-formats not tobe used for newsystems.


- 12 -





Pertains tothe interchangeformats of MSWord, Exceland Power-Point, irrespect-ive of the ac-tual MS Officeversion or gen-eral office auto-mation packagebeing used.

OpenDocu-ment (ODF)ISO/IEC26300:2006

Formerly pub-lished as OAS-IS standard.

Used in Profile:FMN

Office OpenXML, ed.1(ECMA-376)


Office OpenXML, ISO/IEC29500:2012

XML variant ofMicrosoft Of-fice.


HTML 4.01(ISO/IEC15445:2000)

HTML 5.0(W3C EDhtml5:2012)

Used in Pro-files: AMN,FMN, tactESB

HTML 4.01(RFC2854:2000)


Text-basedCollaborationServices


- 13 -





Data Form(XMPP Stand-ards Founda-tion,XEP-0004:2007)


Data Form(Service Dis-covery,XEP-0030:2007)


XMPP (IETFRFC6120:2011 -6121:2011)

Three differ-ent, non-over-lapping profilesfor AMN andFMN - Details:see NISP Vol 3.

Used in Pro-files: AMN,CES, FMN

Video-basedCollaborationServices

MultinationalVideoconfer-encing Ser-vices (ACP220:2008)

Narrow-bandvisual tele-phone sys-tems and ter-minal equipm-ment (ITU-TH.320:2004)

Calendaringand Schedul-ing Services


- 14 -





Formal Mes-saging Ser-vices

Military Mes-saging(STANAG4406Ed.2:2006)

ACP120replacedbyACP145

This includesPCT (protectedcontent type).PCT may beused for protec-tion of data ob-jects in systems.

For CCEB in-teroperabilitythe mandat-ory standard isACP145 (Gate-way-to-Gateway Mes-saging Proto-cols)

ADatP-3(A),CONFOR-METS(STANAG5500, ed.7:2010)


APP-11(C)Change 1,NATO Mes-sage Catalogue(STANAG7149ed.5:2010)

APP-11(D) APP-11(STANAG7149) as thesingle sourcefor NATO Mil-itary Messagesfor commandand control ofNATO forces atall levels of theChain of Com-mand down to


- 15 -





and includingindividual units.

For CCEB in-teroperabilitythe standard isMIL-STD 6040 and OTH-TGOLD stand-ards

Used in Pro-files: AMN,FMN (ed.4)

Variable Mes-sage Format(DoD Mil-Std6017B:2009)

Interoperabil-ity of Low-Level Ground-based Air De-fence Surveil-lance, Com-mand and Con-trol Systems(STANAG4312 Part I,ed.2:2009)

S/MIME withEncrypted Se-curity Ser-vice (ESS)(IETF RFCs3850:2004,3851:2004)

ACP120replacedbyACP145

Messaging Sys-tem independ-ent encapsula-tion syntax sup-porting signa-ture and confid-entiality func-tions based onDSA.


- 16 -





For CCEB in-teroperabilitythe standard isS/MIME Ver-sion 3 ESS, ap-plication layerdata confiden-tiality or linklevel encryption

ITU-TX.411:1999

SCIP KeyManagementPlan,SCIP-120rev.1.0:2010(IICWG)

SCIP X.509Key Manage-ment Plan,SCIP-121rev.0.8:2012(IICWG)

SCIP Sig-nalling Plan,SCIP-210rev.3.5:2012(IICWG)

For CCEB in-teroperabilitythe SCIP stand-ard is mandat-ory

Used in Profile:FMN

SCIP Muli-timedia Op-tion-SpecificMERs forSCIP Devices,SCIP-213rev.1.0:2012(IICWG)


- 17 -





Generic Pack-et Data Option,SCIP-213.1rev.1.0:2010(IICWG)

Used in Profile:FMN

Network Spe-cific MERs forSCIP Devices,SCIP-214rev.1.2:2011(IICWG)

Used in Profile:FMN


SCIP overthe PSTN,SCIP-214.1rev.1.0:2008(IICWG)


SCIP overRTP,SCIP-214.2rev.1.0:2010(IICWG)


U.S. SCIP/IP Implement-ation Standardand MER Pub-lication,SCIP-215rev.2.2:2011(IICWG)

Used in Profile:FMN


Minimum Es-sential Re-quirements(MER) forV.150.1 Gate-ways Publica-tion, SCIP-216


Used in Profile:FMN


- 18 -





rev.2.2:2011(IICWG)

RequirementDocument,SCIP-220:2006(IICWG)

Used in Profile:FMN


Mimimum Im-plementationProfile (MIP),SCIP-221rev.3.0:2011(IICWG)


Used in Profile:FMN

CryptographySpecificationfor SCIP,SCIP-231rev.1.3:2008(IICWG)


SCIP Crypto-graphy Spe-cification -Main Mod-ule, SCIP-233rev.1.1:2012(IICWG)


Used in Profile:FMN

Universal CallSetup Encryp-tion (CSE)Key Materi-al Format andFill Specifica-tion,



- 19 -





SCIP-233.106rev.1.1:2012(IICWG)

MERCATORCall Setup En-cryption (CSE)Key Materi-al Format andFill Specifica-tion,SCIP-233.110rev.1.0:2012(IICWG)


MERCATORCall Setup En-cryption (CSE)Specification,SCIP-233.202rev.1.0:2012(IICWG)


ECDH KeyAgreementand TEK De-rivation,SCIP-233rev.1.1:2011(IICWG)


MERCATORECDH KeyAgreementand TEK De-rivation Spe-cification,SCIP-233.308rev.1.0:2012(IICWG)


InteroperableTerminal Pri-ority (TP)

For CCEB in-teroperabilitythe SCIP stand-


- 20 -





Community ofInterest (COI)Specification,SCIP-233.350rev.1.0:2010(IICWG)

ard is mandat-ory

ApplicationState Vec-tor ProcessingSpecification,SCIP-233.401rev.1.2:2012(IICWG)


Point-to-PointCryptographicVerification w/Signature,SCIP-233.444rev.1.0:2011(IICWG)


MERCATORPoint-to-PointCryptographicVerification w/Signature Spe-cification,SCIP-233.445rev.1.0:2012(IICWG)


SecureMELP(e)Voice,SCIP-233.501rev.1.1:2012(IICWG)


Secure AlmostFull Band-width (AFB)Data,

For CCEB in-teroperabilitythe SCIP stand-


- 21 -





SCIP-233.518rev.1.0:2010(IICWG)

ard is mandat-ory

Secure FullBandwidth(FB) Data,SCIP-233.519rev.1.0:2010(IICWG)


Secure PacketData,SCIP-233.531rev.1.0:2010(IICWG)


Secure Mes-saging Pro-cessing Spe-cification,SCIP-233.547rev.1.0:2012(IICWG)


Galois/Counter Mode(GCM) DataIntegrity Spe-cification,SCIP-233.562rev.0.1:2012(IICWG)


MERCATOREncryption Al-gorithm Spe-cification,SCIP-233.604rev.1.0:2012(IICWG)


UsernameToken Pro-

Used in Profile:CES


- 22 -





file, v1.1:2004(OASIS)

X.509 Certific-ate Token Pro-file, v1.1:2004(OASIS)

Used in Pro-files: CES, tact-ESB

KerberosToken Pro-file 1.1:2006(OASIS)

Used in Profile:CES

SAML TokenProfile1.1:2006(OASIS)

Used in Pro-files: CES,FMN, tactESB

SOAP Mes-sages with At-tachments(SwA) Pro-file 1.1:2006(OASIS)

Used in Profile:CES

WS-SecurityUtility1.0:2001(OASIS)

Used in Profile:CES

WS-Trust1.4:2007(OASIS)

Changed tomandatory withApproved Er-rata, dated 25April 2012.

Used in Pro-files: AMN,CES, FMN,tactESB

Basic Secur-ity Profile Ver-sion 1.1:2010(WS-I)



- 23 -





Military Mes-saging(STANAG4406Ed.2:2006)

Use ofPCT with-inSTANAG4406 isfading

Used for Form-al Messaging.STANAG 4406contains the up-per layer pro-tocol profiledown to the re-quested Trans-port Service.

For CCEB in-teroperabilitythe mandat-ory standard isACP123A .

X.400:1993deleted forinformalmessaging,as no con-crete re-quirementfrom MM-HSWG

MMHS Head-er Fields foruse in SMTP(IETF RFC6477:2012)

Used in Profile:FMN

Nato Sec-ondary Im-agery Format(NSIF),STANAG4545ed.2:2013

NSIF estab-lishes theformat for ex-change of elec-tronic second-ary imagery.



- 24 -





InformalMessagingServices

SMTP (IETFRFCs1870:1995,1985:1996,2034:1996,2821:2001,2920:2000,3207:2002,3461:2003 up-dated by3798:2004,3885:2004,4954:2007,5321:2008,5322:2008)

eSMTP (IETFRFC3030:2000)

Used for inter-personal mes-saging (email)


POP3 (IETFRFC1939:1996 up-dated by1957:1996,2449:1998)

For CCEB in-teroperabilitythis standard isnot applicable

IMAP4 (IETFRFC3501:2003 up-dated by4466:2006,4469:2006,4551:2006,5032:2007,5182:2008,5738:2010)


ApplicationSharing Ser-vices


- 25 -





Data Proto-cols for Multi-media Confer-encing (ITU-T T.120:2007,T.128:2008)

Fax Services

Fax G.3, ITU-T T.4:2003

Fax Transmis-sion, ITU-TT.30:2005

Fax Relayfor IP Net-works, ITU-TT.38:2010

TDF(STANAG5000ed.3:2006)


Unified Mes-saging Ser-vices

Whiteboard-ing Services

Presence Ser-vices

DocumentSharing Ser-vices

ITU Multi-point still im-age and An-notation Con-ference Pro-tocol Spec(ITU-TT.120:2007),T.126:2007


- 26 -





(Reference toT.122 - T.125)

HTTP Ex-tensions forWeb Distrib-uted Author-ing and Ver-sioning (Web-DAV) (IETFRFC4918:2007)

Enterprise Sup-port IA Services

EnterpriseSupportGuard Ser-vices

XML Confid-entiality LabelSyntax (FFI00961:2010)


Binding ofMetadata toData objects(FFI00962:2010)


NATO XMLLabelling ver-sion 1.0 (Ref:-NC3A Tech-nical Note1455 "NATOProfile forthe 'Bindingof Metadatato Data Ob-jects' - ver-sion 1.0"; and



- 27 -





- NC3A Tech-nical Note1456, "NATOProfile for the'XML Confid-entiality LabelSyntax' - ver-sion 1.0".)

ACP 145(A) -Interim Imple-mentationGuide forACP 123/STANAG4406 Mes-saging Ser-vices BetweenNations -dated Septem-ber 2008

Provides gate-way betweenACP 123Amessaging ser-vices.

For CCEB in-teroperabilitythis standard ismandatory.

Binding ofMetadata toData Objects(NC3A TN1455)

Used in Pro-files: AMN,CES

Text-basedCollaborationGuard Ser-vices

Audio-basedCollaborationGuard Ser-vices

Informal Mes-saging GuardServices

Video-basedCollaboration


- 28 -





Guard Ser-vices

Formal Mes-saging GuardServices

Geospatial Ser-vices

Additionalmilitary Lay-ers for digit-al geospatialdata products(AML),STANAG7170ed.2:2010

STANAG 7170is the referenceto the NATOMaritime Con-cepts standardand describesthe product Ad-ditional Milit-ary Layers. Thisstandard in-cludes the Fea-tures, Attributesand enumera-tions specifiedby AML, butnot covered bythe IHO S-57version 3.1.2(June 2009) Ob-ject Catalogue.Once all re-quired mari-time definitionsare includedin DFDD/NG-FCD, referenceto STANAG7170 may beunnecessary.

DIGEST V2.0and DIGESTV2.1,

IGEOWG isin the pro-cess of imple-


- 29 -





STANAG7074ed.2:1998,AgeoP-3(VMaps, US-RP, ASRP)

menting DFDDas a STANAGcalled the NG-FCD (NATOGeospatial Fea-ture ConceptDictionary).The IGEOWGwill regulateany proposalsthat DGIWGmay put for-ward with re-spect to DI-GEST replace-ments.

For CCEB in-teroperabilitythe mandat-ory standard isDGIWG Fea-ture Data Dir-ectory (DFDD)2006 and DI-GEST v2.1 isfading

DTED(STANAG3809ed.4:2006)

Digital TerrainElevation Ex-change FormatSTANAG 3809is based on USMIL-PRF-89020B,Digital Ter-rain ElevationData (DTED),dated 23 May2000. The USA,custodians of


- 30 -





DTED, areworking withthe DGIWG todefine and de-velop appropri-ate replacementstandards forthe exchangeformat in or-der to addressnew and emer-ging elevationrequirements.


SpatialSchema ISO19107:2003,DGI-WG/TSMADprofiles of ISO19107

ISO 19107provides con-ceptual schem-as for describ-ing and manip-ulating the spa-tial characterist-ics of geograph-ic features.

The DGI-WG/TSMADprofiles are in-tended to definesub-schemas ofISO 19107 to beused for defin-ing data inter-change formats.

For CCEB in-teroperability


- 31 -





this standard isemerging

Methodologyfor featurecataloguingISO19110:2005

ISO 19110defines themethodologyfor cataloguingfeature typesand specifieshow the classi-fication of fea-ture types isorganized in-to a featurecatalogue andpresented to theuser of a setof geographicdata.

For CCEB in-teroperabilitythis standard isemerging

Spatial Refer-encing by geo-graphic iden-tifiers ISO19112:2003

ISO 19112defines the con-ceptual schemafor spatial ref-erences basedon geographicidentifiers. Thisstandard en-ables gazetteersto be construc-ted in a consist-ent manner.



- 32 -





Simple FeatureAccess, ISO19125-1:2004and ISO19125-2:2004

ISO 19125-1establishes acommon archi-tecture for geo-graphic inform-ation (simplefeature pro-file of ISO19107) anddefines termsto use withinthe architecture.It also stand-ardizes namesand geometricdefinitions forTypes for Geo-metry.

ISO 19125-2specifies andSQL schemathat supportstorage, re-trieval, queryand update ofsimple geospa-tial feature col-lections via theSQL Call LevelInterface (SQL/CLI) and estab-lishes and ar-chitecture forthe implement-ation of featuretables.



- 33 -





this standard isemerging

GeographicalTagged Im-age Format(GeoTIFF)v.1.8.2 (OS-GEO:2000)


CompressedARC DigitizedRaster Graph-ics (CADRG),STANAG7098ed.2:2004)


GML 3.2.1(OGC:2007)

GML v3.1(ISO19136:2007)

This Open-GIS Consor-tium recom-mendationstandard maybe used asthe transferformat betweenthe FA provid-ing the pub-lished opera-tional data (e.g.COP) and theCore Map Ap-plication Serv-er.

For CCEB in-teroperabilityGML 3.1 isemerging


- 34 -






GML SimpleFeature Pro-file v2.0 (OGC10-100r2:2010)


OpenGIS CityGeographyMarkup Lan-guage(CityGML)v1.0(OGC:2008)

Added in NISPv.6 throughRFCP 5-46.

Filter Encod-ing v2.0 (OGC09-026r1:2010)

Used in Pro-files: AMN(v1.1), FMN(v1.1)

GeospatialData Abstrac-tion Library(GDAL:2013)

ESRIShapefileSpecifica-tion(ESRI:2008)


Open EsriGeoServicesREST spe-cification,v.1.0:2010

Used in Profile:FMN

OpenGIS WebProcessingService(WPS),v.1.0.0:2007(OGC)

Used in Profile:FMN

DLMS/DFAD1, Mil-PRF-89005:1994(NGA)

DLMS/DFAD1must be useduntil DI-GEST/VMAP 1


- 35 -





covers thewhole world.


World Geo-detic System(WGS) 84(NIMA TR8350.2:2004)

WGS specifiesthe set ofparameters thatdefine math-ematically theshape of theearth


Geographic In-formation -Metadata - ISO19115:2003

This providesthe most com-prehensivemetadata spe-cification for di-gital geographicdata. This shallbe used for thegeo metadatawhich forms thefoundation ofthe Core GeoCatalogue. It islikely that aNATO profileof this standardwill have to beproduced basedon the DGIWGprofile.


- 36 -







NATO Geo-spatialMetadata Pro-file (STANAG2586ed.1:2013)

Used in profile:FMN

WECDIS(STANAG4564ed.2:2007)

Standard forWarship Elec-tronic ChartDisplay and In-formation Sys-tems.

SEDRIS (ISO/IEC18023-1:2006)

Environmentaldata represent-ation and in-terchange spe-cification

EDCS (ISO/IEC18025:2005)

Environmentaldata coding spe-cification

SRM (ISO/IEC18026:2009)

Spatial refer-ence model

Geodetic Pro-jections,STANAG2211ed.6:2001


- 37 -





Keyhole-Markup Lan-guage (KML)v.2.2:2008(OGC07-147r2)


Geospatial In-formationProvision Ser-vices

OpenGIS WebMap Tile Ser-vice Imple-mentationStandard(WMTS 1.0.0)(OGC07-057r7)


GeospatialWeb Map Ser-vices

GeospatialWeb FeatureServices

GeospatialWeb CoverageServices

GeospatialWeb Map TileServices

GeospatialCatalog Ser-vices

GeospatialData Manage-ment Services


- 38 -





GeospatialVector DataServices

GeospatialRaster DataServices

GeospatialData Syn-chronizationServices

GeospatialProcessingServices

Terrain Ana-lysis Services

Geospatial Co-ordinate Ser-vices

CoordinateTransforma-tion Services(OGC01-009:2001)

Used in Profile:FMN

GeospatialNetwork Ana-lysis Services

GeospatialRoute Services

Enterprise Sup-port SMC Ser-vices

ApplicationStore Services

Configura-tion Manage-


- 39 -





ment Data-base Services

InformationManagementServices

AVDL

EDXL-DE

DocumentManagementServices

WorkflowServices

Content Man-agement Ser-vices

EnterpriseSearch Ser-vices

Dublin CoreMetadata Ele-ment Set(DCES) (ISO15836:2009)


NATO TIDEInformationDiscovery(Request-Re-sponse),v.2.3.0:2009(ACT)

Part of TIDEspecification atACT. ForCCEB interop-erability thisstandard is notapplicable.


InfrastructureServices


- 40 -





X WindowX11R7.5:2009,(X.Org) (seeUI Svc)

DCE DFSv1.1:1997(The OpenGroup)

RMI-IIOP1.5.0:2005(SUN)

MS-DCOMv.12.0:2010(MS)

As part ofMS Windows2000 Interfaces;DCOM only inlocal environ-ment, not foroutside.

FTP (IETFSTD9:1985,IETFRFC0959:1985 up-dated by RFC2228:1997,2640:1999,2773:2000,3659:2007)

RTP (IETFRFC3550:2003)

SRTP (IETFRFC3711:2004)

RTCP Attrib-utes in SDP(I-ETF RFC3605:2003)

Telnet (IETFSTD 8:1983,IETF RFC

Used in Profile:FMN (RTP)


- 41 -





0854:1983 up-dated by RFC5198:2008,0855:1983)

Network NewsTransfer Pro-tocol NNTP(IETF RFC3977:2006)

Network TimeProtocol(NTP)(RFC5905:2010)


Simple Net-work TimeProtocol(SNTP)(RFC2030:1996)

MPEG-1(ISO/IEC11172:1996)

MPEG-2 (ISO/IEC13818:2000)

MPEG-4 (ISO/IEC14496:2004)

Encodingstandard forvideo conferen-cing

UDF 1.0.1(ISO/IEC13346:1995)

UDF 2.0.1 UDF (UniversalDisk Format)

Pulse CodeModulation(PCM) (ISO/IEC11172-3:1993,

PCM used foraudio in ISDNSystems


- 42 -





ITU-TG.711:1988)

7 kbit au-dio-coding in64 kbit/s (ITU-T G.722:1993)

DifferentialPCM (ITU-TG.726:1990)

CS-ACELP(ITU-TG.729:2012)

Used in Profile:FMN

Internet LowBitrate Cod-ing (iLBC)(IETF RFC3951:2004)

Used in Profile:FMN (G.729)

H.263 (ITU-TH.263:2005)

ITU-T H.263(Video codingfor low bitrate communic-ation);


H.264 (ITU-TH.264:2012)

ITU-T H.264(The AdvancedVideo CodingStandard)

Delta-Modula-tion DM,EURO-COM D/0

GSM-Modulation(GSM 06.10,

Used for mobilephones


- 43 -





GSM 06.20v.8.1.1:1999)

Linear Pre-dictiveCoding-10(STANAG4198ed.1:1984)

Code ExcitedLinear Predic-tion coding(CELP) (FS1016:1991)

CELP is usedmilitary air-craft voice com-munications innarrow bandUHF networks.CELP has high-er throughputthan LPC-10,but a lowerrange.

Mixed Excit-ation LinearPredictive cod-ing (MELPe)(STANAG4591ed.1:2008)

MELPe isused for HFvoice commu-nications in nar-row band sys-tems.

STANAG4421 de-leted asit is can-celled byNATO

Parametersand CodingStandards for800 bps. Digit-al Speech En-coder/Decoder(STANAG



- 44 -





4479ed.1:2002)

BIIF (ISO12087-5:1998)

NSILI(STANAG4559ed.3:2010)

NSILI providesinteroperabilitybetween NATOnations recon-naissance data-bases andproduct librar-ies


NIIRS(STANAG7194ed.1:2009)

NIIRS -AIntP-7(STANAG7194 ed.2(Draft))

NIIRS providesevaluation ofimagery qual-ity and useof a con-sistent measurefor such evalu-ations

NADSI(STANAG4575ed.3:2009)

NADSI(STANAG4575 ed.4(RD))

NADSI definesan interface foradvanced digit-al storage sys-tems.

GMTIF(STANAG4607ed.3:2010)

GMTIF definesa ground mov-ing target indic-ator format.


DMIS(STANAG

DMIS defines adigital motion


- 45 -





4609ed.3:2009)

imagery stand-ard.

For CCEB in-teroperabilitythis standard isnot applicable.


NPIF(STANAG7023ed.4:2009)

NPIF estab-lishes a stand-ard data formatand a stand-ard transport ar-chitecture forthe transferof reconnais-sance and sur-veillance im-agery and asso-ciated auxiliary

AR-TRI(STANAG7024ed.2:2001)

AR-TRI estab-lishes the phys-ical format forthe exchange ofmagnetic tapecartridges

Exchange ofImagery(STANAG3764ed.6:2008)

ImplementingJPEG 2000 inNITFS/BIIF/NSIF (ISO

This profiledefines the lim-its of the inter-national stand-ard that can


- 46 -





10918-4:1999) be used withinNITF 2.1.

InfrastructureIA Services

Allied Nav-al and Mari-time Air Com-munication In-structions(ACP 176NATO Supp1:1967)

Contains con-figuration set-tings across dif-ferent cryptodevices.

Used in Profile:FMN

S/MIME(IETF RFC5751:2010)

Identity Man-agement Ser-vices

Common Bio-metric Ex-changeFormatsFramework(CBEFF)

NPKI Certi-ficate Policy(CertP),AC/322D(2004)0024REV2

Used in Profile:FMN

Machine read-able pass-port (ISO/IEC7501-1:2008)

Used in Profile:FMN

DOD EBTS8.1 (FBIIAFIS-DOC-01078-8.1:2008)

Used in Profile:AMN


- 47 -





CredentialManagementServices

AttributeManagementServices

PrivilegeManagementServices

Digital PolicyManagementServices

IA AuditManagementServices

Crypto KeyManagementServices

IA Configura-tion Manage-ment Services

IA MetadataManagementServices

Infrastruc-ture GuardServices

NC3 Re-pository

Common repos-itory for stand-ard data ele-ments and theirrelated tool forthe NATO Cor-porate DataModel forData Adminis-


- 48 -





tration. See alsoXML.

As this is cur-rently not aformal stand-ard, this entryis under fur-ther considera-tion within theC3B. CurrentSTANAG can-celled in 2013.

For CCEB in-teroperabilitythis standard ispartially applic-able

Used in Profile:AMN

DirectoryGuard Ser-vices

File Trans-fer Guard Ser-vices

Malware De-tection Ser-vices

Intrusion De-tection Ser-vices

Network Ac-cess ControlServices

InfrastructureSMC Services


- 49 -





Open Ser-vices Infra-structure(OpenSiS)v.1.9.5.6,OpenSIS

Infrastruc-ture Monitor-ing Services

Infrastruc-ture Provi-sioning Ser-vices

Infrastruc-ture MeteringServices

Infrastruc-ture LoggingServices

InfrastructureNetworkingServices

DistributedComputingEnvironment(DCE)v1.1:1997(OSF)

ONC RPC v.2(IETF RFC1831:1995)

DCE RPCv1.1:1997(The OpenGroup)


- 50 -





Remote Pro-cedure Call(MS-RPC:2003)(MS)

As part of MSWindows 2000Interfaces

X/Open Net-work File Sys-tem (XNFS)v.3W:1998(The OpenGroup)

Includes RFC1094:1989(NFS 89) andRFC 1813:1995(NFS95)

Server Mes-sage Block(MS-SMB)v20100711:2010(MS)

As part of MSWindows 2000

Default Ad-dress Selec-tion for In-ternet Pro-tocol Version6 (IPv6) (RFC6724:2012)

used in Profile:FMN

VDSL2 VDSL2 is thenext genera-tion of Su-per BroadbandDSL. Ericssonhas demon-strated 500-Mbits/s trans-mission ratesover coppercabling byusing newcrosstalk can-cellation or vec-torized VDSL2based modems.


- 51 -





The data rate isover 20 timesfaster than thefastest ADSL2services cur-rently on offerin most coun-tries.

DistributedTime Services

DCE DTSv1.1:1995(The OpenGroup)

DCE DTS usesTPI (Time Pro-vider Interface)to access otherdistributed timeservices (suchas NTP asmentioned un-der Comms Ser-vice).

Working withTime Zones(W3C Note-timezone:2005)

Used in Profile:FMN

Remote Ac-cess Services

DomainName Ser-vices

End-to-EndNetwork – In-ternet Pro-tocol Frame-work (NETIP),STANAG4731 (Draft)


- 52 -





DNS (IETFSTD 13:1987,RFC1034:1987 andRFC1035:1987 up-dated by RFC1101:1989,1183:1990, up-dated by5395:2008;1706:1994,1876:1996,1982:1996,1995:1996,1996:1996,2136:1997,2181:1997, up-dated by5452:2009;2308:1998,2845:2000,2931:2000,3007:2000,3226:2004,3425:2002,3597:2004,3645:2003,4033:2005,4034:2005,4035:2005,4343:2006,4470:2006,4592:2006)

DNSSEC(IETF RFC4025 -4033:2005)

Bind version 9or later shouldbe used.

Used in Pro-files: AMN,FMN, tactESB.

In tactESBonly used, ifenough band-width available

mDNS (IETFRFC 6762)

Part of TIDEspecification atACT. ForCCEB interop-erability this


- 53 -





standard is notapplicable.

IPSec Materialin DNS (RFC4025:2005)

DNS Config-uration Op-tions for DH-CPv6 (RFC3646:2003)

NIS-Optionsfor DHCPv6(RFC3898:2004)

Dynamic HostConfigurationProtocol, DH-CP (RFC2131:1997 up-dated by RFC3396:2002,4361:2006,5494:2009)

Host Config-uration Ser-vices

DHCP forIPv6 (RFC3315:2003 up-dated by4361:2006,5494:2009)

DHCP Op-tions andBOOTPVendorExtensionsnot to beused innew sys-tems

IPv6 Pre-fix Optionsfor DHCPv6


- 54 -





(RFC3633:2003)

Data TransferServices

FTP Exten-sions for IPv6and NATs(IETF RFC2428:1998)

NetworkLoad Balan-cing Services

Printing andScanning Ser-vices

InfrastructureProcessing Ser-vices

Open Visual-isation Format(OVF) v1.1.0(ISO/IEC17203:2011)

Open Visual-isation Format(OVF) v.2.0.1(DMTFDSP0243:2013)

Used in Profile:FMN

X WindowSystem 11R7.5:2009

X WindowSystem 11R5

The R6.6 re-lease addressesa portion of thebacklog of bugreports sinceRelease 6.5.1patch 1, alongwith additionalfixes from theXfree86 com-munity.

R5 should notbe used for fu-ture systems.


- 55 -






US DoDHCI StyleGuide Ver-sion 4.0Dec 2000not for usein new sys-tems


UK ArmyCIS StyleGuide V2.0 not foruse in newsystems


VirtualizedProcessingServices

OperatingSystem Ser-vices

Win 32APIs

As part of MSWindows 2000Interfaces


CDE 2.1:1997 CDE 1.0 CommonDesktop En-vironment isthe UNIX Win-dows Desktopequivalent.


- 56 -






Motif/CDEStyle GuideRev 2.1:1997

Motif StyleGuide Rev1.2

Toolkit specificstyle guides


MS Win-dows Inter-faceGuidelinesfor Soft-wareDesign

Toolkit specificstyle guides. Aspart of MS Win-dows 2000 In-terfaces.


Motif 2.1:1997 Motif 1.2 For CCEB in-teroperabilitythis standard isnot applicable

InfrastructureStorage Ser-vices

PDF/A-1 (ISO19005-1:2005)

Used in Profile:FMN

PDF/A-2 (ISO19005-2:2011)

Electronic doc-ument fileformat for long-term preserva-tion.

Used in Profile:FMN


- 57 -





PDF/A-3 (ISO19005-3:2012)

Portable docu-ment present-ation format,realised inAdobe productversion 7. Usedin Minerva sys-tem at NATOHQ

For CCEB in-teroperabilitythe primarystandard isAdobe Post-script (level Iand II) /Encap-sulated Post-script (EPS) ,and the second-ary standard isAdobe PDF


Block-LevelStorage Ser-vices

File SystemStorage Ser-vices

Compact DiscFile System(CDFS) (ISO9660:1988)

For physicalmedia distribu-tion (CD)

Blob StorageServices


- 58 -





RelationalDatabaseStorage Ser-vices

SQL 3 (ISO/IEC 9075(-1 to-14):2008)

Full Leveland ISO/IEC9075:1999canceled,new Ver-sion ISO/IEC9075(-1 to-14):2008,Parts 1,2 and11 encom-pass theminimumrequire-ments ofthe lan-guage.Other partsdefine ex-tensions.


ODMG3.0:2000(ODMG)

ODBC 3.8(MS)

JAVA DBCversion4.1:2006 (JD-BC)

JDBC sep-aratedfromODBC

DistributedRDA (DRDA),


- 59 -





v.5 (The OpenGroup)

SQL CLI(ISO/IEC9075-3:2008)

C2 Inform-ation Ex-changeData Mod-el(C2IEDM)and DataExchangeMechan-ism (DEM)


DEM DataReplicationMechanismfrom MIPbaseline3:2009

DEM DataReplicationMechanismfrom MIPbaseline 4


NATOCorporateData Mod-el v2 (AD-atP-32)

For CCEB in-teroperabilitythis standard ispartially applic-able

ASTERIX,ed.1 (AD-atP-35:2010)

This profileis based onADatP-35 anda correspond-ing series ofEUROCON-TROL specific-ations

For CCEB in-teroperabilitythis profile isonly applicable


- 60 -





for NATO leadoperations.

Rules for ap-plicationschema ISO19109:2005

ISO 19109defines rulesfor creatingand document-ing applica-tion schemas,including theprinciples forthe definitionof features. Re-quired for Geoto ensure con-sistency of usein the definitionand use of thegeographic fea-tures.


Joint C3 In-formation Ex-change DataModel (MIPBL 3.1.4:2012; MIPJC3IEDM3.1.4:2012)

MIP Baseline4

C2IEDMreplacedbyJC3IEDM

C2IEDM re-placed byJC3IEDM.

MIP BL 3.1.4used insteadof STANAG5525ed1 to re-flect the cur-rent versionapproved bythe MIP Com-munity.


- 61 -






MIP Inform-ation Mod-el, Stand-ard Data Ele-ments (SDE)(STANAG5526ed1(Study))


Non-relationalStructuredStorage Ser-vices

DirectoryStorage Ser-vices

Common Dir-ectory Ser-vices and Pro-cedures (ACP133D:2009)

ACP 133B Contains a com-mon directorys-chema.

Common Dir-ectory Ser-vices and Pro-cedures Sup-plement (ACP133 Sup-pl.1:2009)

LDAP v3(NATO LDAPProfile)

LDAP is anIETF protocoland close to afunctional sub-set of DAP.Many Web-browsers can


- 62 -





act as LDAPclients, whichis highly desir-able.


LDAP: StringRepresentationof Distin-guishedNames:2006(IETF)

Used in Profile:CES

LDIF (IETFRFC2849:2000)

LDIF definesa flexible andalmost univer-sally acceptedmeans of ex-changing dir-ectory inform-ation via flatfiles.

DSP (ITU-TX.500:2008)

DSP definesX.500 serverto server com-munication, in-cluding chain-ing.


DSIP(ITU-TX.500:2008)

DISP definesX.500 based in-formation shad-


- 63 -





owing/replica-tion.


DOP (ITU-TX.500:2008)

Contains opera-tional manage-ment.


DSMLv2.0:2002,OASIS

DSML providesa Dircetory Ac-cess via a Webinterface

SOA PlatformServices

ebRIMv3.0:2005(OASIS)

ebXML Re-gistry Informa-tion Model

Used in Profile:AMN, FMN

AtomPub(IETF RFC5023:2007)

Used in Profile:FMN

Web Ser-vices BusinessProcess Ex-ecution Lan-guage (WS-BPEL)v.2:2007,OASIS


- 64 -





Business Pro-cess Mod-el and Nota-tion (BPMN)v.2.0:2010

WS-I WebService Ba-sic Profile,v1.1:2nd ed.2006

WS-I WebService Ba-sic Profile,v1.2:3rd ed.2007

For CCEB in-teroperabilitythis profile ismandatory.

Used in Pro-files: AMN(v1.1), CES(v1.0), tactESB(v1.1)

WS-I WebService BasicProfile, v2.02010

Simple Ob-ject AccessProtocol v1.1(SOAP), W3C

Simple Ob-ject AccessProtocol v1.2(SOAP), W3C

Could be usedin support of theGeo Web Ser-vices.

Used in Pro-files: AMN(v1.1), CES(v1.1), FMN(v1.1), tactESB(v1.2)

WS-I SimpleSOAP Bind-ing Profilev1.0:2004


Used in Profile:tactESB

WS-I Attach-ments Profile



- 65 -





v1.0:2nd ed.2006

this profile ismandatory.

Used in Profile:CES

WS-Addressingv1.0 -Core:2010


WS-Addressing 1.0-Metadata:2007

Used in Profile:AMN

WS-Addressing 1.0- SOAP Bind-ings:2006

Used in Profile:AMN

WS-Notificationv1.3:2006


WS-BrokeredNoti-ficationv1.3:2006


WS-Topicsv1.3:2006


Representa-tional StateTransfer(REST):2002,(ACM)


Mediation Ser-vices

Services toForward

Used in Profile:FMN


- 66 -





Friendly ForceInformation toWeapon De-livery Assets(STANAG5528 ed.1(Study))

Enhanced Se-curity Ser-vices (ESS)for S/MIME,STANAG4631Ed.1:2008

STANAG 4631contains anadditional S/MIME profilefor MMMHS(in addition toPCT)

For CCEB in-teroperabilitythe mandat-ory standard isACP123A .

Interoper-ability oftelebrief-ing sys-tems(STANAG5059) de-leted

Interoper-abilitystandardsfor tele-briefingsystems(STANAG4339) de-leted

XML 1.0 5thed:2008, W3C

XML 1.1 2nded:2006, W3C

Where semant-ic tags are


- 67 -





required, theNC3 Reposit-ory serves asan XML re-gistry (see DataManagement).


XLink1.0:2001,W3C

XLink1.1:2012,W3C

XLink is usedto point toresources fromXML docu-ments.

XPointer1.0:2001,W3C

XPointer isused to identifyXML fragmentinside any giv-en XML docu-ments.

Relax NG(ISO/IEC19757-2:2008)

Relax NG maybe a replace-ment for XMLschema lan-guages.

Used in Profile:CES

XMLBase:2001,W3C

XMIed.1:2001(ISO/IEC19503:2005)

XMI can beused for anymetadata whosemetamodel canbe expressedin Meta-ObjectFacility (MOF).


- 68 -





XML In-foset:2001,W3C

XSL Associ-ation:1999,W3C

Namespaces inXML (xml-names-19990114:1999)W3C

Used in Pro-files: AMN,CES, tactESB

ExtensibleStylesheetLanguageTransforma-tion (XSLT)Version 2.0(W3C:2007)


ExtensibleStylesheetLanguage(XSL)1.0:2001

ExtensibleStylesheetLanguage(XSL)1.1:2006

XML Schema,Part 1-2:2004


Efficient XMLInterchangeFormat (EXI)v1.0

Efficient imple-mentations ofXML in thetactical envir-onment

Data FormatTransforma-tion Services

XQuery1.0:2003,W3C

Used in Profile:CES


- 69 -





XML PathLanguage(XPath)v2.0:2003,W3C


Used in Profile:CES

ProtocolTransforma-tion Services

CompositionServices

Unified Mod-eling Lan-guage (UML)v2.2:2009(OMG)


TransactionServices

Choreo-graphy Ser-vices

Web Ser-vice Choreo-graphy Inter-face (WSCI)v.1:2002

OrchestrationServices

Message-ori-ented Middle-ware Services

SOAP Mes-sage Secur-ity 1.1:2004(OASIS)

SOAP Mes-sage Secur-ity 1.2:2001(W3C)



- 70 -





WS-ReliableMes-sagingv1.2:2009(OASIS)


WS-ReliableMessaging 1.2

Web PlatformServices

HTTP v. 1.1(IETF RFC2616:1999 up-dated by TLS(RFC2817:2000),URL (RFC4248:2005,4266:2005),URI (RFC3986:2005)


Content-IDand Mes-sage-ID URLs(IETF RFC2392:1998)

Used in Profile:CES

HTTP StateChange Mg-mt. (IETF RFC2965:2000)

Used in Pro-files: CES, tact-ESB

HTTPS (IETFRFC2818:2000)

Used in Profile:CES

CascadingStyle Sheets(CSS) 2.1(W3C css-lev2:2001)

CascadingStyle Sheets(CSS) level 3



- 71 -





WirelessMarkup Lan-guage (WML)2.0:2001

WML to beused with Wire-less Applica-tion Protocol(WAP) for con-strained envir-onments

Web HostingServices

Web-ServicesSecurity Pro-file (WSS),v1.0 (OASIS)

Used in Pro-files: AMN,FMN (v1.1),tactESB

WS-SecurityPolicy,v1.3:2009(OASIS)

Changed tomandatory withApproved Er-rata 01, dated 25April 2012.


Security As-sertionMarkup Lan-guage, SAMLv2.0 (OASIS)

For CCEB in-teroperabilitythe Secur-ity AscertionMarkup Lan-guage (SAML)v1.1 is mandat-ory and SAML2.0 is emerging

Used in Pro-files: CES(v2.0), FMN,tactESB

XKMS 2.0(W3C):2005

Used in Pro-files: AMN,tactESB


- 72 -





Public-key andattribute cer-tificate frame-works, X.509v3:2008 (ITU-T)


Portlet Ser-vices

Java Port-let Specific-ation v.1.0,JSR 168:2003(JCP)

Java Port-let Specific-ation v.2.0,JSR 286:2008(JCP)

Used in Profile:FMN

Remote Port-let Specifica-tion v1.0, WS-RP1.0:2003(OAS-IS)

Remote Port-let Specifica-tion v2.0, WS-RP2.0:2008(OAS-IS)

Used in Profile:FMN

Web Applica-tion Accelera-tion Services

Web CachingServices

SOA PlatformSMC Services

WS-Managementv1.0 (DMTF)

Used in Pro-files: CES,FMN

WS-ManagementCIM Bind-ing Specific-ation, v1.0.0(DMTF)

Used in Profile:FMN


- 73 -





CIM Schemav2.30.0(DMTF)

Used in Profile:FMN

CMDB Feder-ation Specific-ation v1.0.1(DMTF)

Used in Profile:FMN

ITIL (ISO/IEC20000:2012)


COBIT 5:A BusinessFramework forthe Gov-ernance andManagementof EnterpriseIT (ISACA:2012)


enhancedTelecom Op-erations Map(eTOM, rel.13:2012 (TM-Forum))

Used in Profile:FMN

ConfigurationManagementDatabase(CMDB) Fed-eration Spe-cification(DMTFDSP0252:2009)

Used in Profile:AMN

SNMPv3 Ap-plications(IETF RFC3413:2002)

SNMPv1(IETF Std15) not for

SNMPv3 isconsideredemerging be-cause of current


- 74 -





new sys-tems

lack of agree-ment on theconcept of op-erations for dis-tributed man-agement



Message Pro-cessing andDispatchingfor the SN-MP (RFC3412:2002 up-dated by5590:2009)


User-based Se-curity Model(USM) for SN-MPv3 (RFC3414:2002 up-dated by5590:2009)


View-basedAccess Con-trol Mod-el (VACM)for the SN-MP (RFC3415:2002)


Structure ofMgt Info



- 75 -





(IETF Std16:1990, IETFRFC1155:1990 and1212:1991)

this standard isnot applicable

Architecturefor SNMPMgt Frame-works (RFC3411:2002 up-dated by5343:2008,5590:2009)


MIB II (IETFStd 17:1991,RFC1213:1991 up-dated by4293:2006,4022:2005,4113:2005)


IPv6 MIB(IETF RFC4293:2006)


ICMPv6 MIB(IETF RFC4293:2006)


MulticastGroup Mem-bership Dis-covery MIB(IETF RFC5519:2009)


IPv6 MIB forTCP (IETF



- 76 -





RFC4022:2005)

this standard isnot applicable

IPv6 MIB forUDP (IETFRFC4113:2005)


Host Re-sources MIB(IETF RFC2790:2000)


Defs of MgtObjects forthe Ether-net-like In-terface types(IETF RFC2666:1999,3635:2003,3638:2003)


RMON MIBv. 1 (RFC2819:2000)

RMON 2MIB (RFC4502:2006)


OSPF MIBv.2 (RFC4750:1996)


RIP-2 MIB(RFC1724:1994)


802.1p(IEEE:2004)

IEEE 802.1p(Quality of Ser-vice)

Performanceobjectives andprocedures forprovisioning

Used in Profile:FMN


- 77 -





and mainten-ance of IP-based net-works (ITU-TM.2301:2002)

Common In-formationModel (CIM)(DMTF:1999)

CMIS(ISO9595:1998)deleted inNISP v.1


CMIP(ISO/IEC9596-1:1998)deleted inNISP v.1

Primarily usedfor TelecomManagement

CMIPPICS (ISO/IEC9596-2:1993)deleted inNISP v.1

GDMO(ISO/IEC10165-4:1996)deleted inNISP v.1

Service Dis-covery Ser-vices

Universal De-scription, Dis-covery and In-tegration(UDDI) 3.0,W3C

UDDI 3.0provides a plat-form-independ-ent way ofdescribing- anddiscovering ser-vice.


- 78 -





Used in Pro-files: AMN,CES, FMN,tactESB (v2.03)

UDDI APISpec v.2,OASIS:2002


ElectronicBusiness Ex-tensibleMarkup Lan-guage(ebXML) ISO/TS15000-1:2004,-2:2004,-3:2004,-4:2004,-5:2005

ebXML is asuite of spe-cifications forstandardizingXML basedbusiness mes-sages to fa-cilitate tradingbetween organ-isation.

Used in Pro-files: AMN(v3.0), CES(v3.0), FMN

ebXML Mes-saging Servicev. 2.0:2002(OASIS)

ebXML Re-gistry Servicesand Protocols,v.3.0:2005(OASIS)


WS-Discoveryv.1.1:2009,OASIS


TIDE Ser-vice Discov-ery,



- 79 -





v.2.2.0:2008(ACT)

DNS-BasedService Dis-covery (DNS-SD):2013(IETF)


NATO TIDEService Dis-covery (Sub-scribe-Pub-lish),v.2.2.0:2008(ACT)


Used in Pro-files: FMN,tactESB

WSDLv1.1:2001,W3C

WSDLv2.0:2007 Part1: Core Lan-guage, W3C


SOA PlatformIA Services

Key Wrap Ad-vanced En-cryptionStandard 128(AES 128,NIST FIPS197)

Key Wrap Ad-vanced En-cryptionStandard 256(AES 256,NIST FIPS197)

PKI compon-ents and applic-ations shouldutilise AES forkey wrap func-tions.

AES 256 shouldbe utilized post2008 for RootCA and Sub CAPKI compon-ents together


- 80 -





with SHA-384and 512. Endentities can stillutilize AES 128together withSHA-256.

For CCEB in-teroperabilityAES 128 isemerging.

IP ESP (RFC4303:2005)

EncapsulatingSecurity Pay-load (ESP) maysupport integ-rity and authen-tication depend-ing on the use ofalgorithms


NINE IS-pec v1.0.3(NATO)

Digital Sig-nature Al-gorithm 1024(DSA-1024,NIST FIPS186-2 withChange Notice1, Oct 2001)

Elliptic CurveDigital Signa-ture Algorithm(ECDSA 384,NIST FIPS186-2 withChange Notice1, Oct 2001)

DigitalSignatureAlgorithm(originalversion)not for newsystems

Authenticationand integrityalgorithm forEnd Entities asmandated bythe interoper-ability protocolPCT for imple-menting digit-al signatures fora NATO PublicKey Infrastruc-ture (PKI) inthe NATO mes-


- 81 -





saging system.ECDSA 384 isplanned for post2008. Guid-ance is providedin AC/322-D(2004)0035.

For CCEB in-teroperabilitythe DigitalSignature Al-gorithm (DSA)NIST FIPS186-2 is man-datory. DSAFIPS 186-2 canbe used inNATO for veri-fication pur-poses only.

RSA 2048(PKCS#1 v2.1RSA Crypto-graphy Stand-ard, RSALaboratories,June 2002)

Elliptic CurveDigital Signa-ture Algorithm(ECDSA 384,NIST FIPS186-2 withChange Notice1, Oct 2001)

Authenticationand integrity al-gorithm for SubCA and oth-er PKI com-ponents (suchas Key Re-covery Agents)as mandated bythe interoper-ability protocolPCT for imple-menting digit-al signatures fora NATO PublicKey Infrastruc-ture (PKI) inthe NATO mes-saging system.


- 82 -





ECDSA 384 isplanned for post2008. Guid-ance is providedin AC/322-D(2004)0035.

For CCEB in-teroperabilitythe DigitalSignature Al-gorithm (DSA)NIST FIPS186-2 is man-datory.

Secure HashAlgorithm 256(SHA-256,NIST FIPS180-2 withChange Notice1, Feb 2004)

Secure HashAlgorithm 384(SHA-384,NIST FIPS180-2 withChange Notice1, Feb 2004)

SecureHash Al-gorithm(SHA-1),NIST FIPS180-1 re-placed bySHA-256

Hash algorithmto accom-pany the DSAand RSA foruse in NMS.SHA-384 isplanned for post2008. Guid-ance is providedin AC/322-D(2004)0035.

For CCEB in-teroperabilitythe standard isSHA-1, NISTFIPS 180-1is mandatory.SHA-1 can beused in NATOfor verificationpurposes only.

XML En-cryption Syn-tax and Pro-



- 83 -





cessing,W3C:2002

XML Signa-ture(W3C):2008


Release Ser-vices

SOA Plat-form GuardServices

TLS v1.2(IETF RFC5246:2008)

SSL ex-cluded inNCSP v.6

Used as a trans-port layer secur-ity protocol.

Used in Pro-files: AMN(v1.1), CES,FMN, tactESB

SSH v.2 (IETFRFC4250-4256:2006)

XML GuardServices

Web GuardServices

SecurityToken Ser-vices

WS-Policyv1.5:2007(OASIS)


WS-Policy 1.5- Guidelines(OASIS:2007)



- 84 -





WS Policy1.5 - Primer(OAWS-IS:2007)


WS-Federationv1.2 (OASIS)

Used in Pro-files: AMN(v.1.1), CES,FMN, tactESB

Radius, IETFRFC2865:2006 up-dated by RFC2868:2000,3575:2003,5080:2007

Radius andIPv6, IETFRFC3162:2001

Kerberos v.5,IETF RFC1510:1993


The Kerberosv5 Simple Au-thenticationand Secur-ity Layer(SASL) Mech-anism, IETFRFC4752:2006

Used in Profile:CES

Single signon (SSO, theOpen Group)

X.509 Pub-lic Key Infra-structure Cer-tificate andCRL Profile(IETF RFC5280:2008)


- 85 -





Identificationof Issuers (ISO7812:2007)

Base profileconsisting ofparts 1 - 2.

SOA Plat-form Priv-ilege Manage-ment Services

Policy De-cision Point(PDP) Ser-vices

NPKI Certi-ficate Policy(CertP),AC/322D(2004)0024REV2

Used in Profile:AMN, FMN

XACMLv2.0:2008(OASIS)

XACMLv3.0:2010(OASIS)

Used in Pro-files: AMN,CES, tactESB

DOD EBTS1.2 (DoD:2000)

Used in Profile:AMN

DOD EBTS2.0 (DoD:2000)

Used in Profile:AMN

BiometricsData, Inter-change,Watchlistungand Report-ing (STANAG4715ed.1:2013)

Data Formatfor the Inter-change of Fin-gerprint, Fa-cial, and ScanMark and Tat-too (SMT) In-formation(ANSI ITL-1:2000)

Used in Pro-files: AMN(ITL-1), FMN(STANAG4715)

Biometric datainterchangeformats --

Used in Profile:AMN


- 86 -





Part 2 (ISO19794-2:2007)

Biometric datainterchangeformats -- Part5: Face Im-age Data (ISO19794-5)

Used in Profile:AMN

Biometric datainterchangeformats -- Part6: Iris Im-age Data (ISO19794-6)

Used in Profile:AMN

Policy En-forcementPoint (PEP)Services

InformationPlatform Ser-vices

InformationDiscoveryServices

SPARQL 1.1Query Lan-guage:2012(W3C)

Part of TIDEspecification atACT.



Web Onto-logy Language

Part of TIDEspecification at


- 87 -





(OWL):2009,W3C

ACT. ForCCEB interop-erability thisstandard is notapplicable.


OpenSearch1.1,OpenSearch

Used in Profile:FMN

ISAF Minim-um MetadataImplementa-tion Policy(NATO:2010)

Used in profile:AMN

OWL-S

InformationAnnotationServices

Metadata Re-pository Ser-vices

NATOMetadata Re-gistry and Re-pository(NMRR)(NC3ATN-1313:2008)


WS-MetadataEx-change:2010,W3C

Used in Profile:CES

XML Encryp-tion(W3C):2008



- 88 -





InformationAccess Ser-vices

Resource De-scriptionFramework(RDF):2004(W3C)


Real SimpleSyndication(RSS 2.0)(WS-I:2010)


GeoRSS(GeoRSS1.0):2007(OGC)


Atom Syndic-ation Format(IETF RFC4287)


XHTML1.0:2002(W3C)

XForms1.0:2003(W3C)

XHTML is spe-cified in XML


SGML (ISO8879:1986)

For high valuecomplex docu-ments


- 89 -

3.3.2. Community Of Interest (COI) Services





COI-EnablingServices

CDIF (EIA/IS-106 to118:1994)

CDIF (CASE(ComputerAided Soft-ware Engineer-ing) Data Inter-changeFormat). AnEIA (Elec-tronic Industryof America )standard for ex-changing databetween CASETools.

Unified Profilefor DoDAFand MODAF(UPDMv.2):2008(OMG)


Codes forthe represent-ation of Cur-rencies andFunds (ISO4217:2008)

ECMA ScriptLanguage Spe-cification(ECMA 262)ed.3:2009

Scripting re-quired for en-hanced Webpages



- 90 -





ECMA ScriptXML Specific-ation (ECMA357) ed.3:2009

This sstand-ard adds nativeXML datatypesto the ECMAScript language.

Zip Implementa-tions of zip(e.g. Winzip)also includesgzip (RFC1952:1996) andtar/compress

7-bitCodedCharac-ter-set forInfo Ex-change(ASCII)(ISO/IEC646:1991)

8-bitSingle-ByteCodedGraphicChar Sets(ISO/IEC8859-1-6,8-10:1999;7:2003)

UniversalMultiple Oct-et Coded CharSet (UCS) -Part 1 (ISO/IEC10646:2003)


- 91 -





NATO Stand-ard Bar CodeSymbology(STANAG4329ed.4:2010)

STANAG 4329is a coverSTANAG ofISO16388:1999 -Bar code sym-bology specific-ations - Code39.

Bar code sym-bology spe-cification -Code 128(ISO/IEC15417:2007),Bar code printquality testspecification -Linear sym-bols (ISO/IEC15416:2000)

Representationof Dates andTimes (ISO8601:2004)


Date andTime Formats(W3C NOTE-date-time:1998)


MIME (IETFRFC2045:1996 up-dated by2184:1997,2231:1997,5335:2008;2046:1996 up-dated by

S/MIME ESS(IETF RFC3850:2004,3851:2004)

Base64 is in-cluded in RFC2045:1996

Used in Pro-files: CES,FMN


- 92 -





3676:2004,3798:2004,5147:2008;2047:1996 up-dated by2184:1997,2231:1997,5338:2008;2049:1996;4288:2005;4289:2005)

MIME Encap-sulation of Ag-gregate Doc-uments, suchas HTML(MHTML):1999(IETF)

Used in Profile:CES

SituationalAwareness Ser-vices

SymbologyServices

Vector ProductFormat (VPF)(DoD, Mil-Std.2407:1996)

Vector Map(VMap) Level1 (STANAG7163ed.1:2003)

NetCDF v1.0OGC 10-090r3(OGC:2011)


- 93 -





GeoPDF OGC08-139r3(OGC:2011)

GeospatialSymbols forDigital Dis-plays (Geo-Sym)(NIMA:2000)

WebCGM(Web Com-puter Graph-ics Metafile),W3C REC20011217,2001

CGM(ISO/IEC8632:1999)not for newsystems

Primarily inten-ded for vec-tor-based im-ages.

SVG 1.2:2005(W3C)

The preferredformat to visu-alize mapsin the Webbrowser.

Mobile SVGProfiles: SVGTiny andSVG Basic,W3C REC20030114,2003

SVG profilesfor cellphonesand PDAs

Tagged ImageFile Format forimage techno-logy (TIFF)(ISO12639:1998)

VectorMarkup Lan-guage (VML),W3C Note


- 94 -





19980513,1998 (W3C)

TIDE Trans-formationalBaseline3.0:2009(ACT)


NVG - NATOVector Graph-ics Protocolv.1.5:2010(ACT)

NVG - NATOVector Graph-ics Protocolv.2.0:2012(ACT)


Used in Profles:AMN, FMN,tactESB

Controlled Im-agery Base(CIB,STANAG7099ed.2:2004),

JPEG 2000(ISO/IEC15444-1:2004,ISO/IEC15444-2:2004,ISO/IEC15444-3:2007,including Amd2:2003, ISO/IEC15444-4:2004,ISO/IEC15444-5:2003,ISO/IEC

JPEG 2000 isthe standardused to storeraster data (im-agery, scannedmaps, mat-rix data) andprovides theability to in-clude spatialreferencing in-formation with-in the standard.


- 95 -





15444-6:2003,) For CCEB in-teroperabilityISO/IEC15444-2 Cor. 3is not applic-able.

JPEG LS (ISO/IEC14495:2003)

Loss-less andnear loss-lesscompression ofcontinuous tonestill images.

Multiresolu-tion seamlessImage Data-base (MrSidRes. 2)


EnhancedCompressedWavelet(ECW 3.3)

Used in Profile:AMN

Raster productformat (RPF)(NIMA):2010

Used in Profile:AMN

GIF (ver-sion 89a)not for newsystems

Graphics Inter-change Formatis intendedfor the on-line trans-mis-sion and inter-change of rastergraphic data.

PNG 1.0 (RFC2083:1997)

Portable Net-work GraphicsPNG is inten-ded for the com-pressed stor-age of rasterimages. PNG


- 96 -





provides a pat-ent-free re-placement forGIF.

CommonWarfightingSymbology(Mil-Std2525B)

CommonWarfightingSymbology(Mil-Std2525C)

For CCEB in-teroperabilitythe mandat-ory standardis MIL-STD2525B COM-MONWARFIGHT-ING SYM-BOLOGY andthe emergingstandard isMIL-STD2525C


Joint Sym-bology (AP-P-6(C)/STANAG2019ed.6:2011)



Telecommu-nications Sym-bology(STANAG5042ed1:1978)

Portrayal ISO/DIS19117:2005

Currently inDraft. Interna-tional Standard


- 97 -





specifies the in-terface to stand-ard symbol sets,not the symbolsthemselves.

Symbolson LandMaps,Aeronaut-ical Chartsand spe-cial Nav-al Charts(STANAG3675ed.2:2000)

For CCEB in-teroperabilitythis standard isapplicable andfading.

IHO S-100,2000

IHO S-57

Web Map Ser-vice (WMS)Implementa-tion Specifica-tion v.1.3:2006(OGC 06-042)

Used as ameans of dis-tributing com-piled mappingdata betweenapplications.


OpenGISStyled Lay-er DescriptorProfile of theWeb Map Ser-vice (SLD1.1.0) (OGC05-078r4)


Web FeatureService (WFS)

Web FeatureService (WFS)v.2.0:2009

Used as ameans of dis-tributing geo


- 98 -





v.1.1.0:2005(OGC 04-094)

(OGC09-025r1)

feature (vector)data betweenapplications.



Web CoverageService (WCS)v.2.0.1:2012(OGC09-110r4)

Used as a meansof distributinggeo coverages(raster) databetween applic-ations.



WCS Imple-mentation Spe-cificationv1.1.2 (OGC07-067r5:2007)

WCS Im-plementa-tion Spe-cificationv1.0 (OGC03-065r6:2003)

OGC 03-065r6is declared asdeprecated byOpenGIS.

Used in Pro-files: AMN(v1.1.1), FMN(v1.1.1)

GML in JPEG2000 for Geo-graphic Im-agery

This evolvingOGC standarddescribes min-imally required


- 99 -





(GMLJP2)v.1.0.0 (OGC05-047r3:2006)

GML definitionfor georeferen-cing images andgives guidelinesfor augment-ing that defini-tion to addressthe addition-al encoding ofmetadata, fea-tures, annota-tions, styles, co-ordinate refer-ence systems,and units ofmeasure fordata encoded inJP2K

Used in Profile:FMN

OGC GISWeb TerrainService RFCv.05:2004

Used as a meansto perform WebService basedTerrain analysisand communic-ate terrain datato clients

Catalogue Ser-vice for theWeb (CSW)v.2.0.2 (OGC)

Used as a meansof discoveringgeo metadata.


CSW-ebRIMRegistry Ser-vice, Part 1:ebRIM pro-



- 100 -





file for CSWv.1.0.1 (OGC07-110r4:2009)

OGC - ISO19115:2003/ISO19119:2005ApplicationProfile forCSW 2.0

Describes theorganisationand implement-ation of Cata-logue Servicesbased on theISO 19115 /ISO 19119 Ap-plication Profile

Web Re-gistry Servicev.0.0.2:2001(OGC Ref.01-024r1)

Used as a meansof publishingand finding geoservices.

As this stand-ard is declareddeprecated byOGC, the fur-ther inclusion ofit in NISP isunder consider-ation within theC3B.

ComputerGraphicsInterface(CGI ISO/IEC9636:1991)


OpenGLv4.0:2010


Track Man-agement Ser-vices


- 101 -





JREAP,STANAG5518 (RD)

ISO/IEC8802-3:2000(CSMA/CD)

ACP 190 (D)

ACP 190 (B)NATO Suppl1A

Spectrum Sup-portability Re-quest/Commentis a two-way commit-ment betweenthe (host)nationowing the sys-tem and eachnation hostingthe system:

- it is a pre-requisite for theprocuring na-tion/agency toperate SDEs ina host nation.

- host nationsgranting sup-port to a SDEis expected toassign frequen-cies when re-quested.

Failure to fol-low this processwill have verynegative long-term impacts:


- 102 -





- an evergrowing riskof interferencebetween ownsystems.

- the ever-in-creasing pres-sure from thecommercialsector: hav-ing an accurateview of militaryuse of spectrumis an essentialprecondition tobe able to de-fend it againstcivil encroach-ment.


ACP 190 (B)NATO Suppl 2


SMADEFXML Rel.3.0.0

For CCEB in-teroperabilityRel.1.2.3 ismandatory

SIMPLE(STANAG5602ed.3:2010)

SIMPLEprovides spe-cifications to in-terconnectground rigs ofall types for


- 103 -





TDL interoper-ability testing

Link-11(STANAG5511ed.7:2008, M-Series)

For furtherguidance referto the Bi-SCData Link Mi-grationStrategy,November2000.

For CCEB in-teroperabilitythe standardis MIL-STD6011C

Link-16(STANAG5516ed.4:2008, J-Series)

Link-16(STANAG5516ed.5:2009 RD,J-Series)

For CCEB in-teroperabilitythe mandat-ory standardis MIL-STD6016C Change1 and theemerging stand-ard is MIL-STD6016D


Link-22(STANAG5522ed.2:2008, J-Series)

Link-22(STANAG5522ed.3:2009 RD,J-Series)

Used in Profile:AMN

Technicalcharacteristicsof the Link 22TDL system


- 104 -





(STANAG4610 ed.1(Draft))

Link-14(STANAG5514ed.2:2002)

The Link-14 isa legacy sys-tem that mostNATO nationshave no inten-tion to imple-ment in newplatforms otherthan interfacingdata link buffersand have ceasedto use or main-tain. Thereforeconsidered fad-ing

NFFI,STANAG5527 (study)

Until the de-veloment ofSTANAG 5527is more stable,documentAC/322(SC/5)N(2006)0025should be used.



Track Data-base Services

Track Correla-tion Services


- 105 -





Track Interop-erability Ser-vices

Track Dissem-ination Ser-vices

Track Mes-saging Service

Track Stream-ing Service

Track Broad-casting Service

Track Aug-mentation Ser-vices

Track LoggingServices

Common Op-erational Pic-ture Services

BattlespaceObject Ser-vices

BattlespaceObject Discov-ery Services

BattlespaceObject IdentityServices

BattlespaceObject Inform-ation Services

Ordnance In-formation Ser-vices


- 106 -





Order of BattleServices

Weapon Sys-tem Informa-tion Services

BattlespaceObject Com-puting Ser-vices

BattlespaceObject PatternAnalysis Ser-vices

BattlespaceObject Rela-tionship Valid-ation Services

BattlespaceEvents Ser-vices

ReportingServices

Alerting Ser-vices

Incident Re-porting Ser-vices

Position Re-porting Ser-vices

Mission Re-porting Ser-vices

Situation Re-porting Ser-vices


- 107 -





Status Report-ing Services

Overlay Man-agement Ser-vices

OperationalPlanning Ser-vices

TargetingServices

TargetingComputingServices

Target ListValidationServices

Targeting In-formation Ser-vices

Target Materi-al Services

Target ListsServices

Target StatusServices

ADL andAFL Manage-ment Services

Courses ofAction (COA)Services

DeploymentPlan Services

CampaignSynchronisa-


- 108 -





tion MatrixServices

Tasking and Or-der Services

OperationsOrder Ser-vices

Resource Al-location Ser-vices

Resource Re-quest Man-agement Ser-vices

Tasking Ser-vices

ROE Man-agement Ser-vices

COI-EnablingSMC Services

Data Ex-change Mon-itoring Ser-vices

Business Sup-port Services

Business Pro-cess Integra-tion Services

Business DataManagementServices

Business In-telligence Ser-vices


- 109 -





EnterpriseProject Plan-ning Services

Business Ob-ject SearchServices

COI-EnablingIA Services

Modeling andSimulation Ser-vices

OMG SystemsModeling Lan-guage (OMGSysML) Ver-sion 1.1,November2008. SysMLis a Sys-tems Engineer-ing standard.

CoalitionBattle Man-agement Ser-vices

COI-SpecificServices

Air COI Ser-vices

Air Informa-tion Services

Joint BrevityWords Pub-lication (AP-P-7(E) Change1, STANAG


- 110 -





1401ed.14:2011)

RecognisedAir Picture(RAP) Ser-vices

Air TaskingOrder (ATO)Services

Air SpaceManagementServices

Asset List Ser-vices

Air Coordin-ation Order(ACO) Ser-vices

Air Opera-tions Directive(AOD) Ser-vices

Airlift Ser-vices

AeronauticalInformationServices

Air Comput-ing Services

Air SpaceStructure Man-agement Ser-vices

RecognisedAir Picture


- 111 -





(RAP) Analys-is Services

WeaponMatching Ser-vice

ATO AnalysisService

Air ThreatAnalysis Ser-vices

Air MobilityAnalysis Ser-vices

Land COI Ser-vices

Land Inform-ation Services

RecognisedGround Pic-ture (RGP)Services

Land Com-puting Ser-vices

RecognisedGround Pic-ture (RGP)Analysis Ser-vices

Maritime COIServices

Maritime In-formationServices

Vessel Posi-tion Services


- 112 -





AutomaticIdentificationSystem (AIS)Services

Long RangeIdentificationand Tracking(LRIT) Ser-vices

Over-the-Horizon-Gold(OTH-Gold)Messages Ser-vices

Technologyfor Informa-tion, Decisionand Execu-tion superi-ority (TIDE)Sensor Ser-vices

Format AlfaServices

ShippingRoutes Net-work Services

Water SpaceManagement(WSM) Ser-vices

MaritimeComputingServices

Maritime An-omaly Detec-tion Services


- 113 -





Maritime His-torical Analys-is Services

Maritime Kin-ematic Analys-is Services

DestinationResolutionServices

RendezvousDetection Ser-vices

EstimatedTime of Ar-rival (ETA)VerificationServices

GeographicalProximity De-tection Ser-vices

Maritime Cor-relation andFusion Ser-vices

Mine War-fare Calcula-tion Services

SONAR Pre-diction Ser-vices

AmphibiousWarfare Cal-culation Ser-vices

Space COI Ser-vices


- 114 -





Space In-formationServices

Satellite RadarServices

Satellite Im-agery Services

EnvironmentalCOI Services

GeographyServices

Oceano-graphy Ser-vices

HydrographyServices

Space Weath-er Services

MeteorologyServices

Specificationsfor Naval MineWarfare In-formation andfor Data Trans-fer - AMP11 (STANAG1116ed.9:2010)


NATO Hand-book of Mil-itary Ocean-ographic In-formation andSer-vices(STANAG

For CCEB in-teroperabilitythis standard isonly applicablefor NATO leadoperations


- 115 -





1171ed.9:2008)

NATOOceano-graphicData Ex-changeFormat(STANAG1317ed.3:2008)


Interoperabil-ity betweenNaval MineWarfare DataCentres(STANAG1456ed.2:2010)


Warning andReporting andHazard Predic-tion of Chem-ical, Biologic-al, Radiologic-al and Nuc-lear Incidents(STANAG2103ed.10:2010)


Adoption of aStandard Bal-listic Meteor-ological Mes-sage(STANAG4061ed.4:2000)



- 116 -





Adoption of aStandard Ar-tillery Com-puter Meteor-ological Mes-sage(STANAG4082ed.3:2012)


Format of Re-quests for Met-eorologicalMessages forBallistic andSpecial Pur-poses(STANAG4103ed.4:2001)


Adoption of aStandard Tar-get Acquisi-tion Meteoro-logical Mes-sage(STANAG4140ed.2:2001)


NATO Met-eorologicalCodes Manu-al (STANAG6015ed.4:2005)


Adoption of aStandard Grid-ded Data Met-eorologicalMessage

For CCEB in-teroperabilitythis standard isonly applicable


- 117 -





(STANAG6022ed.2:2010)

for NATO leadoperations

Binary Univer-sal Form forthe Represent-ation of met-eorologicaldata (BUFR)(WMO FM94:2002)

Gidded Bin-ary (GRIB)(WMO:1994)

Gridded Bin-ary - WMO -Standard formatfor grid fields;WMO ManualCode Nr. 306

Simple Know-ledge Organ-ization Sys-tem Refer-ence (SKOS)(W3C:2002)

For the descrip-tion of vocabu-laries and TermConcept Mapsof sematic webservices.

Meteorologic-al ProductsServices

Logistics COIServices

EDIFACT(ISO9735:2002)

EDIFACT canbe used totransfer busi-ness documentssuch as pur-chase orders,invoices, andelectronic fundstransfer inform-


- 118 -





ation. ebXML isa UN standard

RFID Ap-plication In-terface, ISO15961:2004

RFID Data En-coding Rules,ISO15962:2004

RFID - Freightcontainers,ISO17363:2007

RFID - Re-turnable trans-port items, ISO17364:2009

RFID - Trans-port units, ISO17365:2009

RFID -Product pack-aging, ISO17366:2009

RFID -Product tag-ging, ISO17367:2009

OAGIS9.4.1:2009,OAGi

PLCS, ISO10303-239:2005

S1000D issue4:2008, ASD-AIA-ATA


- 119 -





S2000M issue4:2005, ASD-AIA-ATA

NATO Policyfor SystemsLife CycleMgmt(SLCM), C-M(2005)0108

SLCM isprimarily basedon AAP 48 andISO/IEC 15288

Force Sup-port Engin-eering Ser-vices

Financial Ser-vices

Maintenanceand RepairServices

Movementand Trans-portation Ser-vices

Logistics C2Services

Human Re-sources Ser-vices

Medical Ser-vices

Medical Sup-port Services

LogisticsStatus Ser-vices


- 120 -





EvacuationManagementServices

LogisticsComputingServices

Casualty RateEstimationServices

Stockpile Ana-lysis Services

Logistics In-formationServices

Supply Ser-vices

Asset TrackingServices

CasualtyStatus Services

ConsignmentServices

Patient Track-ing Services

JISR COI Ser-vices

JISR Inform-ation Services

Video Services

Imagery Ser-vices

Sensor Ser-vices


- 121 -





Request for In-formation(RFI) Services

IntelligenceSituation Ser-vices

ExploitationReport Ser-vices

Collection andExploitationPlans Services

Sensor Plan-ning Services

Sensor Plan-ning Service(SPS) (OGC09-000:2011)

Used in Profile:FMN

CommercialSurveillanceRadar Services

Military Sur-veillanceRadar Services

IntelligenceRequirementServices

Battle Dam-age Effects As-sessment Ser-vices

ISR Synchron-isation MatrixServices


- 122 -





Decision Sup-port Informa-tion Services

Imagery Ma-nipulation Ser-vices

JISR Annota-tion Services

IntelligenceReport Ser-vices

Video Manip-ulation Ser-vices

JISR Com-putation Ser-vices

Effects ListValidationServices

Collection andExploitationPlan AnalysisServices

IntelligenceRequirementValidationServices

ExploitationReport Valida-tion Services

Multi-spectralPixel Data Fu-sion Services


- 123 -





Imagery Pat-tern Recogni-tion Services

CIMIC COIServices

CIMIC In-formationServices

InternationalCriminal Po-lice Organiza-tion (INTER-POL) Services

National LawEnforcementServices

World Cus-toms Organiz-ation (WCO)Services

European Uni-on (EU) Mari-time Surveil-lance (MAR-SUR) Services

Special Opera-tions COI Ser-vices

EW COI Ser-vices

EW Informa-tion Services

Restricted Fre-quency ListServices


- 124 -





NEDB Ser-vices

EW Comput-ing Services

Emitter Ana-lysis Services

CBRN COIServices

ETEE COI Ser-vices

Missile De-fence COI Ser-vices

Missile De-fence Inform-ation Services

TBMD De-fence DesignServices

Missile De-fence Com-puting Ser-vices

TBMD Re-source Ser-vices

TBMD De-fence DesignAnalysis Ser-vices

TBMD Re-source Analys-is Services

COI-SpecificIA Services


- 125 -





VulnerabilityManagementServices

On-Site Vul-nerability As-sessment Ser-vices

PenetrationTesting Ser-vices

COMPUSECBulletin Ser-vice

Web-Site Test-ing Services

On-Line Vul-nerability As-sessment Man-agement Ser-vice

COI-SpecificSMC Services

Joint COI Ser-vices

Surface AreaManagementServices

CIS COI Ser-vices

SpectrumManagementServices

Spectrum Us-age Informa-tion Services


- 126 -





Modeling andSimulation COIServices

CORBA/IIOP2.2:2009(OMG)

DistributedInteractiveSimulation(DIS)(IEEE1278.1a:1998)

Modeling andSimulationHigh Level Ar-chitecture(HLA) (IEEE1516:2000)

For CCEB in-teroperabilitythis standard ismandatory

Modeling andSimulationInfrastruc-ture Services

Modeling andSimulationIntegrationServices

3.3.3. Communications Services





ZigBee 1.0

WiBree

W-USB

6LoWPAN


- 127 -





5G

MobileWiMax

Mobile-Fi

WiBro

HIPERMAN

Flash-OFDM

AODV

DSR

UWB

OGSA

OSGi

SCTP

CAP

Media Ac-cess Con-trol (MAC)Bridges (IEEE802.1D:2004)

Rapid Recon-figuration ofSpanning Tree(IEEE802.1W:2004)

Multiple Span-ning Trees(IEEE802.1S:2004)

VirtualBridged LocalArea Networks(VLAN)(IEEE802.1q:2005)


- 128 -





Link LayerDiscovery Pro-tocol (IEEE802.1AB:2009)

Gigabit Ether-net,1000BASE-LX10 (IEEE802.3-2013)

Used in Profile:FMN

Genericcabling forcustomerpremises (ISO/IEC11801:2002)

Used in Profile:FMN

Optical FibreCables (ITU--T G.652:2009)

Used in Profile:FMN

LC connect-ors with pro-tective hous-ings (ISO/IEC61754-20:2012)

Used in Profile:FMN

FDDI, ISO9314:1989


Characteristicsof 1200/2400/3600 bpssingle tonemodulat-ors/demodu-lators for HFRadio links(STANAG4285ed.1:1989)

For CCEB in-teroperabilitythe mandat-ory stand-ard is MIL-STD-188-110A


- 129 -





Non-HoppingSerial TONEHF Radio,STANAG4415ed.1:1999

MinimumStandards forNaval Shore-to-Ship Broad-cast Systems,STANAG4481 ed.1

Characteristicsof single tonemodulat-ors/demodu-lators formaritime HFradio linkswith 1240Hz bandwidth,STANAG4529 ed.1

Automatic Ra-dio ControlSystem forHF LinksSTANAG4538ed.1:2009

Automatic Ra-dio ControlSystem forHF LinksSTANAG4538 ed.2(Draft)

Non-hoppingHF Commu-nicationsWaveformsSTANAG4539ed.1:2006


- 130 -





MinimumStandards forNaval low Fre-quency (LF)Shore-to-ShipSurface Broad-cast Systems(STANAG5065ed.1:1999)

Profile forHF radiodata commu-nications(STANAG5066ed.3:2010)

Communica-tion betweenSingle Chan-nel and Fre-quency Hop-ping Radi-os in VHF,STANAG4292ed.2:1987

Non-secureVoice In-teroperab-ility forVHF Radi-os,STANAG4448ed.1:2006

SecureVoice and


- 131 -





Data In-terface forVHF Radi-os,STANAG4449ed.1:2006

Have QuickSTANAG4246ed.3:2009


STANAG4372ed.3:2008(Saturn)

UHF standardfor Link-22, butcan also carryLink-11 andLink-16 mes-sages.

Multi-Hop IPNetworkingwith legacyUHF radios:Mobile ad-hocRelay Lineof Sight Net-working(MARLIN),STANAG4691 ed.1(RD)

Digital Inter-operabilitybetween UHFSatellite Com-municationsTerminals - In-tegratedWaveform(IWF),STANAG


- 132 -





4681 ed.1(RD)

Super HighFrequency(SHF) Mil-itary Satel-lite (MILSAT-COM) jam-resistant mo-dem(STANAG4376ed.1:1998)


Interoperabil-ity Stand-ard for Satel-lite SHF De-ployable Ter-minals Con-trol and Com-mand Services(STANAG4706:2013)


MIDS termin-als STANAG4175 ed.4:2009

MIDS termin-als STANAG4175 ed. 5(RD)

Single seri-al line in-terface(TIA-232-E:1991)

Multi-point seri-al line


- 133 -





(TIA-422-B:2005)

Serial bin-ary data ex-change atDTE and DCE(TIA-530-A)

Generic spe-cification foroptical wave-guide fibers(EIA 4920000:1997)

VLF andLF BroadcastOOK Systems,STANAG5030ed.4:1995

Extendedrange singleand multi-channel VLFsystem,STANAG4724 /Draft)

Conditionsfor interop-erability of2400 BPS /HF(STANAG4197ed.1:1984)

(QSTAG 1108)

TransmissionIA Services

TransmissionSMC Services

Wired WideArea Transmis-sion Services

Wired Metro-politan Area


- 134 -






Wireless LOSMobile Trans-mission Ser-vices

Wireless LOSMobile Nar-rowbandTransmissionServices

STANAG4444ed.1:1999 RD(Slow hop EC-CM)

STANAG4444ed.2:2010 RD(Slow hop EC-CM)

HF standard forLink-22.

For CCEB in-teroperabilitythis STANAGis mandatory

Technicalstandards forsingle chan-nel HF ra-dio equipment,STANAG4203ed.3:2007

For CCEB in-teroperabilitythe mandatorystandard is MILSTD 188-141A

Technicalstandards forsingle chan-nel VHF ra-dio equipmentSTANAG4204ed.3:2008

For CCEB in-teroperabilitythe mandatorystandard is MILSTD 188-242

Technicalstandards forsingle chan-nel UHF ra-

For CCEB in-teroperabilitythe mandatory


- 135 -





dio equipmentSTANAG4205ed.3:2005

standard is MILSTD 188-243

Interoperabil-ity Standardfor 25 kHzUHF/ TDMA/DAMA ter-minal Wave-formSTANAG4231ed.5:2011

STANAG 4231ed.5 is identic-al with MIL-STD-188-183C.

For CCEB in-teroperabilitythe mandat-ory stand-ard is MIL-STD-188-183D

Overall Su-per High Fre-quency (SHF)Military Satel-lite COMmu-nications(MILSAT-COM) interop-erability stand-ards(STANAG4484ed.2:2003)

Overall Su-per High Fre-quency (SHF)Military Satel-lite COMmu-nications(MILSAT-COM) interop-erability stand-ards(STANAG4484 ed.3(RD))


Wireless LOSMobile Wide-band Trans-mission Ser-vices

Wireless LOSStatic Trans-mission Ser-vices


- 136 -





Wireless LOSStatic Nar-rowbandTransmissionServices

Wireless LOSStatic Wide-band Trans-mission Ser-vice

Wireless BLOSStatic Trans-mission Ser-vices

WirelessBLOS Stat-ic Narrow-band Trans-mission Ser-vices

WirelessBLOS Stat-ic Wide-band Trans-mission Ser-vices

Super HighFrequency(SHF) Medi-um Data Rate(MDR) Mil-itary Satel-lite COMmu-nications(MILSAT-COM) jam-resistant mo-dem interoper-

Super HighFrequency(SHF) Medi-um Data Rate(MDR) Mil-itary Satel-lite COMmu-nications(MILSAT-COM) jam-resistant mo-dem interoper-



- 137 -





ability stand-ards(STANAG4606ed.1:2009)

ability stand-ards(STANAG4606 ed.3(RD))

Interoperabil-ity stand-ard for Satel-lite Broad-cast Services(SBS) (Draft)(STANAG4622 ed.1RD2)


Wireless BLOSMobile Trans-mission Ser-vices

SHFMILSATCOMNon-EPM mo-dem for ser-vices conform-ing to class-A of STANAG4484(STANAG4485ed.1:2002)

SHFMILSATCOMNon-EPM mo-dem for ser-vices conform-ing to class-A of STANAG4484(STANAG4485 ed.2(RD))


Super HighFrequency(SHF) Mil-itary Satel-lite COMmu-nications(MILSAT-COM) Fre-quency Di-vision Mul-

Super HighFrequency(SHF) Mil-itary Satel-lite COMmu-nications(MILSAT-COM) Fre-quency Di-vision Mul-



- 138 -





tiple Access(FDMA) Non-EPM modemfor servicesconforming toclass-B ofSTANAG4484(STANAG4486ed.2:2002)

tiple Access(FDMA) Non-EPM modemfor servicesconforming toclass-B ofSTANAG4484(STANAG4486ed.3:2008)

Digital inter-operabilitybetween EHFTactical Satel-lite Commu-nications Ter-minals(STANAG4233ed.1:1998)

For CCEB in-teroperabilitythe mandat-ory stand-ard is MIL-STD-1582D

EHF MILSATCOM in-teroperabilitystandards formedium datarate servicesSTANAG4522ed.1:2006

For CCEB in-teroperabilitythe mandat-ory stand-ard is MIL-STD-188-136

WirelessBLOS Mo-bile Narrow-band Trans-mission Ser-vices

WirelessBLOS Mo-bile Wide-


- 139 -





band Trans-mission Ser-vices

Wired LocalArea Transmis-sion Services

Communica-tions AccessServices

X.25(1996,Cor.1:1998)

MPLS (IETFRFC 3031:2001,3032:2001)

Tactical Com-munications,STANAGs4637ed1:2009,STANAG4638ed1:2009,4639ed1:2009,4640ed1:2009,4643ed1:20094644ed1:2009,4646ed1:2009,4647ed1:2009


ISDN: ITU-TG, I Series

ISDN Tele-phony

Physical/elec-trical char-acteristics ofhierarchical di-gital inter-faces, ITU-TG.703(11/2001)

Used in Profile:FMN


- 140 -





Synchronousframe struc-tures used at1544, 6312,2048, 8448and 44 736kbit/s hier-archical levels,ITU-T G.704(10/1998)

Used in Profile:FMN

UMTS (3GPP)

GPRS (3GPP)

ITU-T E,P, Q, VSeries

Digital VideoBroadcasting(DVB) (ET-SI:2009)

ITU-TV.90:1998

ITU-TV.42:2002Corri-gendum1:2003

User Net-work Inter-face - UNIv4.0 (af-sig-0061.000)

PrivateNetwork -NetworkInterface -PNNI v1


- 141 -





(af-pnni-0055.000)

LAN Emu-lation overATM -LANEv2.0 (af-lane-0084.000,af-lane-0112.000)


Standards forData Forward-ing betweenTactical DataSystems em-ployingLink-11/11Band Link-16(STANAG5616ed.5:2011)

Standards forData Forward-ing betweenTactical DataSystems em-ployingLink-11/11Band Link-16(STANAG5616 ed.6(RD))

GatewaybetweenLink-11 andLink-16.

For CCEB in-teroperabilitythe mandat-ory standard isMIL-STD 6020

Link 1STANAG5501ed.5:2011

Link 1STANAG5501 ed.6 RD

Link 11STANAG5511ed.7:2008

Communica-tions part forLink-11

For CCEB in-teroperabilitythe standardis MIL-STD6011C



- 142 -





STANAG4175ed.4:2009

STANAG4175 ed.5(RD)

Communica-tions part forLink-16

Used in Profile:AMN

MIDS SSS-M-10001

MultifunctionalInformationDistributionSystem - Sys-tem SegmentSpecification

STANAG7085ed.3:2009(IDL for Ima-ging Systems)

STANAG 7085provides the in-teroperabilitystandards for 3classes of im-agery DL usedfor primaryimagery datatransmission.

STANAG4586ed.3:2012

STANAG4586 ed.4

STANAG 4586facilitates com-municationbetween a UCSand differentUAVs and theirpayloads aswell as multipleC4I users.

Analogue Ac-cess Services

Digital (Link)Access Services

Message-basedAccess Services


- 143 -





Short Mes-saging AccessServices

Tactical Mes-saging AccessServices

Maritime Tac-tical WideArea Network-ing (ACP 200)

For CCEB in-teroperabilitythe mandatorystandard is ACP200 :MaritimeTactical WideArea Network-ing

Routing andDirectory fortactical Sys-tems,STANAG4214ed.2:2005

InternationalNetwork Num-bering forCommunica-tions Sys-tems in Usein NATO,STANAG4705 ed.1(RD)

Used in Profile:FMN

Gateway Mul-tichannelCable Link(Optical),STANAG4290 ed.1(RD)


- 144 -





Enhanced Di-gital StrategicTactical Gate-way (EDSTG)(STANAG4578 ed.2:2009)

STANAG4249 re-placed bythe morefunda-mentalSTANAG4206.STANAG4206 not tobe used fornew sys-tems.

STANAG iscurrently underreview for anew edition.


NATO Multi-channel tac-tical digit-al Gateway(STANAG4206:Ed.3:1999)


NATO Multi-channel tac-tical Gate-way-MultiplexGroup Fram-ing Standards(STANAG4207:Ed.3:2000)

The NATOMilitary Com-municationsDirectory Sys-tem, STANAG5046 ed.3

The NATOMilitary Com-municationsDirectory Sys-tem, STANAG5046 ed.4(RD)

Circuit-basedAccess Services


- 145 -





Native Cir-cuit-basedAccess Ser-vices

EmulatedCircuit-basedAccess Ser-vices

Frame-basedAccess Services

NativeFrame-basedAccess Ser-vices

EmulatedFrame-basedAccess Ser-vices

Packet-basedAccess Services

IP packettransfer andavailabilityperformanceparameters(ITU-TY.1540:2011)

Used in Profile:FMN

Network per-formance ob-jectives forIP-based ser-vices (ITU-TY.1541:2011)

Used in Profile:FMN

Framework forachieving end-to-end IP per-formance ob-

Used in Profile:FMN


- 146 -





jectives (ITU-TY.1542:2006)

Quality of ser-vice rankingand measure-ment meth-ods for digit-al video ser-vices deliveredover broad-band IP net-works (ITU-TJ.241:2005)

Used in Profile:FMN

IPv4 RoutedAccess Ser-vices

IPv6 RoutedAccess Ser-vices

VirtualPrivate Net-work (VPN)Services

Multimedia Ac-cess Services

Voice AccessServices

Video AccessServices

VTC AccessServices

Communica-tions Access IAServices

Network Fire-wall Services


- 147 -





Communica-tions AccessSMC Services

Call Manage-ment Services

Session Ini-tialisation Pro-tocol (SIP)(IETF RFC3261:2002, up-dated by3265:2002,3853:2004,4320:2006,4916:2007,5393:2008,5621:2009,5626:2009,5630:2009,5922:2010)

Used in Profile:FMN

VTC Man-agement Ser-vices

Demand As-signed Mul-tiple Ac-cess (DAMA)Control Ser-vices

Resource Dis-covery Ser-vices

ResourceConfigura-tion and Ac-tivation Ser-vices


- 148 -





ResourceTesting Ser-vices

Collect, Up-date andReport Re-source Con-figurationServices

Survey andAnalyse Re-sourceTrouble Ser-vices

Localise Re-sourceTrouble Ser-vices

Correct andRecover Re-sourceTrouble Ser-vices

Track andManage Re-sourceTrouble Ser-vices

Monitor Re-source Per-formance Ser-vices

Control Re-source Per-formance Ser-vices


- 149 -





Collect Re-source DataServices

Transport Ser-vices

Internet Pro-tocol Qual-ity of Ser-vice (IP QoS),STANAG4711 (Draft)

IP QoS forthe NII, NC3ATN-1417

Used in Profile:FMN

DifferentiatedServices Field(IETF RFC2474:1998 up-dated by3168:2001,3260:2002)

DiffServ re-defines use offormer TOSfield; first, butnot sufficientRFC to dif-ferentiate trafficclasses. RFC forDiffServ stillmissing. Ap-plicable to bothIPv4 and IPv6.

Included in Pro-file: FMN

ConfigurationGuidelines forDiffServ Ser-vice Classes(RFC4594:2006)

Included in Pro-file: FMN

Resource Re-SerVation Pro-tocol (RSVP)


- 150 -





(IETF RFC2205:1997)

Requirementsfor IPv4routers (RFC1812:1995 up-dated by2644:1999)

Used in Profile:FMN

Open ShortestPath First (OS-PFv2) RFC2328:1998)

OSPF forIPv6 (RFC5340:2008)

Suitable forLANs as wellas WANs (in-cluding tacticalnetworks) withsufficient band-width

IS to IS in-tra-domainrouteing in-formation ex-change pro-tocol (ISO/IEC10589:2002)

Router Inter-net Protocol(RIP v2) (IETFSTD 56/RFC2453:1998 up-dated by4822:2007)

RIPng forIPv6 (RFC2080:1997)

Border Gate-way Protocol(BGP4) (RFC4271:2006)

MultiprotocolExtensions forBGP-4 (RFC4760:2007)

Use of BGP-4MultiprotocolExtensions forIPv6 Inter-Do-main Rout-



- 151 -





ing (RFC2545:1999)

BGP Com-munities At-tribute (RFC1997:1996)

BGP Exten-ded Com-munities At-tribute (RFC4360:2006)


CapabilitiesAdvertisementwith BGP-4(RFC5492:2009)

Used in Profile:FMN

BGP Supportfor Four-Oct-et Autonom-ous System(AS) NumberSpace (RFC6793:2012)


4-Octet ASSpecific BGPExtendedCommunity(RFC5668:2009)


BGMP (RFC3913:2004)

Application ofBGP-4 (RFC1772:1995)

Protocol Inde-pendent Mul-ticast SparseMod-e(PIM-SM)(RFC4601:2006, up-

PIM-SM is im-plemented bythe router mar-ket leaders.



- 152 -





dated by5059:2008)

SimplifiedMulticast For-warding(SMF) (RFC6621:2012)


Protocol Inde-pendent Mul-ticastingDense Mod-e(PIM-DM)(RFC3973:2005)

PIM-DM is in-cluded as asecond conceptfor tactical net-works

MulticastSource Dis-covery Pro-tocol (MS-DP) (RFC3618:2003)


Generic Rout-ing Encapsu-lation (GRE)(RFC4023:2005, up-dated by5332:2008)

GRE is in-cluded as ageneral rout-ing encapsula-tion mechanism

Traditional IPNetwork Ad-dress Trans-lator (RFC3022:2001)

Stateless IP/ICMP Transla-tion Algorithm(SIIT) (RFC2765:2000


- 153 -





Generic Pack-et Tunnelingin IPv6 (RFC2473:1998)

This RFC isa generic tun-nel mechanism,which can beapplied for sev-eral protocols.

Router InternetProtocol (RIPv2) MIB ex-tension (RFC1724:1994)

To be used instatic networks.See also SystemManagement.

Classless InterDomain Rout-ing (CIDR)(RFC4632:2006)

CIDR is onlyvalid for IPv4


Mobile IPv4(RFC3344:2002 up-dated by4721:2007)

Mobile IPv6(RFC3775:2004)

Mobile IPv6Fast Han-dovers (RFC5568:2009)

IPSec and Mo-bile IPv6 (RFC3776:2004 up-dated by4877:2007)

Policy-basedNetwork Man-agement -General (RFC1104:1989,2753:2000,


- 154 -





3198:2001,3334:2002)

Policy-basedNetwork Man-agement -DiffServ (RFC2963:2000,2998:2000,3086:2001,3260:2002,3287:2002,3289:2002,3290:2002,3308:2002,3496:2003)

Policy-basedNetwork Man-agement - Int-Serv (RFC2205:1997 up-dated by2750:2000,3936:2004,4495:2006,2206 -2210:1997,2380:1998,2382:1998,2430:1998,2490:1999,2745 -2746:2000,2747:2000 up-dated by3097:2001,2749:2000,2750:2000,2755:2000,2814:2000,


- 155 -





2872:2000,2961:2001, up-dated by5063:2007;2996:2000,3097:2001,3175:2001, up-dated by5350:2008;3181:2001,3182:2001,3209:2001 up-dated by3936:2004,4874:2007;3210:2001,3468:2003,3473:2003 up-dated by4003:2005;3474:2003,3476:2003,3477:20034201:2005,4783:2006,4873:2007,4874:2007,5250:2008,5420:2009

Point to PointProtocol (PPP)Internet Pro-tocol Con-trol Protocol(IPCP) (RFC1332:1992 up-dated by3241:2002,4815:2007)

To allow pack-et switched ser-vices over cir-cuit switchedinterconnec-tions.


- 156 -





Layer 2 Tun-neling Pro-tocol (L2TP)(RFC3308:2002)

Link Con-trol Protocol(LCP) exten-sions (RFC1570:1994 up-dated by2484:1999)

Addition toLLC1 (see LinkLayer).

Point to PointProtocol (PPP)(STD 51, RFC1661:1994 up-dated by2153:1997;1662:1994, up-dated by5342:2008)

IPv6 overPPP (RFC5072:2007)


PPP Chal-lenge Hand-shake Authen-tication Pro-tocol (CHAP)(RFC1994:1996 up-dated by2484:1999)

Used in routers.

Used in Profile:FMN

PPP Multilink(MP) (RFC1990:1996)

Allows for ag-gregation ofbandwidth viamultiple sim-ultaneous datalink connec-tions


- 157 -





Virtual RouterRedundancyProtocol(VRRP), IETFRFC3768:2004

Winsock 2(Revision 2.2)

TransportService(ISO8072:1996)de-leted inNCSP v.6

TCP (IETFSTD 7:1981,RFC 793:1981updated byRFC1122:1989,3168:2001)

Used in Pro-files: AM-N,FMN, tact-ESB

UDP (IETFSTD 6:1980,RFC0768:1980)


OSI trans-port svc overTCP/IP (RFC2126:1997)

Includes theISO TransportProtocol

Space commu-nications pro-tocol specific-ation (SCPS) -Transport pro-tocol (SCPS-TP) (ISO15893:2010)


- 158 -





Edge TransportServices

Link Emula-tion Trans-port Services

Time Divi-sion Multi-plexed-basedTransportServices

Frame-basedTransportServices

IP-basedTransportServices

AssignedNumbers(RFC3232:2002)

IPv4 (STD 5,RFC791:1981,792:1981,826:1982,894:1984,919:1984,922:1984,950:1985 up-dated by RFC1112:1989,2365:1998,2474:1998,2507:1999,2508:1999,2908:2000,3168:2001,3171:2001,



- 159 -





3260:2002,3376:2002,4604:2006,4884:2007)

IPv6 (RFC1981:1996,2375:1998,2460:1998,2464:1998,2467:1998,2470:1998,2491:1999,2492:1999,2497:1999,2526:1999,2529:1999,2590:1999,2710:1999 up-dated by3590:2003,2711:1999,2894:2000,3056:2001,3111:2001,3122:2001,3146:2001,3306:2002,3307:2002,3483:2003,3510:2003,3544:2003,3587:2003,3595:2003,3697:2004,3736:2004,3810:2004,3879:2004,3956:2004,4001:2005,4007:2005,

Note: Cat-egory of RFC2375:1998 is´Informal´



- 160 -





4213:2005,4291:2006,4311:2005,4338:2006,4443:2006,4489:2006,4604:2006,4861:2007,4862:2007,4884:2007,4941:2007,5095:2007,5172:2007,5494:2009)

IGMP v.3(RFC3376:2002 up-dated by4604:2006)

RFC 3367:2002obsoleted2236:1997 up-dates RFC1112:1989 andis widely imple-mented, RFC3376:2002 ob-soleted RFC2236:1997

Host require-ments (STD3, IETF RFC1122:1989 up-dated by2474:1998,2181:1997,3168:2001,3260:2002,4033:2005,4034:2005,4035:2005,4343:2006,4379:2006,4470:2009,


- 161 -





5452:2009,5462:2009)

BootstrapProtocol,BOOTP(RFC951:1985updated byRFC1542:1993,2132:1997,3442:2002,3942:2004,4361:2006,4833:2007,5494:2009)

Will be over-taken by thericher DHCP.BOOTP is stillavailable inolder imple-mentations andis expected tophase out.

IP Encapsu-lation (RFC2003:1996)

Clarifica-tions andExtensionsfor theBootstrapProtocol(RFC1542:1993)

Dual StackIPv6 mobilitysupport (RFC5555:2009)

Core NetworkServices

Packet Rout-ing Services

Interconnec-tion of IPv4Networks at

Interconnec-tion of IPv4Networks at

Used in Profile:FMN


- 162 -





Mission Secretand Unclas-sified Secur-ity Levels,STANAG5067ed.1:2007(RD)

Mission Secretand Unclas-sified Secur-ity Levels,STANAG5067 ed.2(Draft)

FrameSwitchingServices

CircuitSwitchingServices

AggregationServices

Packet-basedAggregationTransportServices

Frame-basedAggregationTransportServices

Circuit-basedAggregationTransportServices

Broadcast Ser-vices

Transport IAServices

Transport SMCServices

DistributionServices


- 163 -

4. PROFILES

4.1. INTRODUCTION

022. The purpose of this chapter is to specify the NISP near term profiles. The documentorganizes these profiles under the following considerations:

• Profiles derived from NATO Reference Architectures

• Profiles derived from NATO Operations

• Profiles derived from NATO member nations

023. The above list will be enhanced dynamically, based on updated profile definitions beingdeveloped in relevant NATO bodies.

024. The standards being used in these profiles may differ in version from those being listed inchapter 3. This is based on the time for the development of these standards and may be modifiedin newer versions of these profiles.

025. Standards, which are listed in NISP Vol. 2 and are belonging to one or more profiles, aslisted in chap. 4 of this document or in NISP Vol. 3, are marked in the Remarks column asfollows:

026. Used in Profile(s): standard1 (, standard2, ...)

027. Standards, which are not included by a valid RFCP in NISP, Vol.2, but are only includedin a profile, are marked in the Remarks column in italics as follows:

028. Used in Profile(s):standard1 (, standard2, ...)

4.1.1. Profiles derived from NATO Operations

029. This chapter contains profiles from current or future planned NATO operations. Currently,the following operations are recognised:

• Afghan Mission Network (AMN)

4.1.2. Profiles derived from NATO member nations

030. This chapter contains profiles from member nations being proposed for interoperabilitypurposes in NATO and between NATO nations.

4.2. PROFILE SPECIFICATIONS

031. This section summarizes the profiles, listed in volume 3:


- 164 -

4.2.1. NRF Generic Interface Profile

032. The purpose of this profile is to support NRF rotation specific profile development.

4.2.2. Tactical ESB - Profile

033. The aim of this specification is to describe a profile for a tactical Enterprise ServiceBus (tact ESB) to be used in a coalition, highly mobile and distributed environment. Theprofile focuses specifically on requirements from military usage and goes beyond the ESBspecification, available in civil implementations/products.

034. The profile is a generic specification; following the principle construction elements,it allows for national implementations a derivation from the proposed one, not losing theinteroperability aspects.

035. Details of this profile are contained in: IT-AmtBw_A5_RuDi-High_Level_Concept_400.pdf (DEU)

4.2.3. AMN - Profile

036. The purpose of this specification is to define an Interoperability Standards Profile to supportthe Afghanistan Mission Network (AMN) in order to enhance the exchange of informationwithin and across the AMN. These are the extant and NATO agreed list of practical standardsto achieve immediately usable interoperability between the national network extensions of theNATO nations, coalition nations and NATO provided capabilities.

037. Nations participating in the AMN have agreed to comply with the AMN joininginstructions, of which these standards form an integral part.

4.2.4. CES - Profile

038. The Core Enterprise Services Framework ([NC3A CESF, 2009]) describes a set of CoreEnterprise Services (CES) – sometimes referred to as the “what” of the NNEC CES. This sectionaddresses the “how” by detailing the profile of functionality and mandated standards for eachof the Spiral 1 CES.

4.2.5. Service Interface Profile (SIP) Template Document

039. The aim of this profile is to define a template based on the NCIA and IABG proposal for astandard profiling document, which from now on will be called Service Interface Profile (SIP).

4.2.6. FMN - Profile

040. The FMN Profile is included for notation by NATO Nations in ADatP-34(H) and providesimplementation guidance for NATO common funded capabilities used in NATO exercises suchas CWIX, Steadfast Cobalt, and Trident Juncture, until formally approved.


- 165 -

IndexSymbols3rd Generation Partnership Project, 140, 140

AACM

2002-REST-TOIT, 65Adobe Systems Incorporated

EPS, 57PDF v. 1.4, 57Postscript (level I and II), 57

AeroSpace and Defence IndustriesAssociation of Europe

S1000D-I9005-01000-00, 118s2000m, 119

ANSIincits-398, 46

ANSI/NISTITL 1-2000, 85

BBluetooth SIG

Core Version 4.0, 126

CChairman of the Joint Chiefs of Staff

SSS-M-10001, 142Combined Communications and ElectronicBoard

ACP 123A, 23, 66ACP 133, 61ACP 133 Suppl.1, 61ACP 145(A), 27ACP 176 NATO SUPPL-1, 46ACP 190(D), 101ACP 200, 143, 143ACP 220(A), 13ACP145, 14

DDMTF

cim_schema_v2300, 73DSP0004, 77

DSP0226, 72DSP0227, 72DSP0243, 54DSP0252, 73, 73

DoDDIN: DOD_BTF_TS_EBTS_Mar09_02.00.00, 85DIN: DOD_BTF_TS_EBTS_Nov06_01.02.00, 85MIL-STD 188-110A, 128MIL-STD 188-136, 138MIL-STD 188-141A, 134MIL-STD 188-1582D, 138MIL-STD 188-183D, 135MIL-STD 188-242, 134MIL-STD 188-243, 135MIL-STD 2525B, 96, 96MIL-STD 2525C, 96MIL-STD 6011C, 103, 141MIL-STD 6016C, 103MIL-STD 6016D, 103mil-std 6017B, 15MIL-STD 6040, 15mil-std-2407, 92MIL-STD-2525C, 96OTH-T, 15

EEBXML

ebTA, 78ECMA

368, 127ECMA-262, 89ECMA-357, 90ECMA-376, 12

Electronic Industries AssociationIS-106, 89RS-530, 133TIA/EIA-492000-A, 133

ERDASecw, 95

ESRIREST, 34

European Telecommunication StandardisationInstitute


- 166 -

TS 102 624-1, 127

FFederal Bureau of Investigation

IAFIS-DOC-01078-8.1, 46

GGeospatial Data Abstraction Library

gdal, 34Global Grid Forum

draft-ggf-ogsa-spec-1.5-011, 127

IIEEE

802.15.4, 126802.16e, 127, 127802.1AB, 128802.1D, 127802.1p, 76802.1Q, 127802.1S, 127, 127802.20, 127802.3-2012, 128P1516, 126

IETFdraft-ietf-manet-dsr-09, 127RFC 1212, 75RFC 1213, 75RFC 1332, 155RFC 1510, 84RFC 1519, 153RFC 1570, 156RFC 1643, 76RFC 1661, 156RFC 1724, 76, 153RFC 1772, 151RFC 1812, 150RFC 1831, 49RFC 1939, 24RFC 1990, 156RFC 1994, 156RFC 1997, 151RFC 2003, 161RFC 2021, 76RFC 2030, 41

RFC 2058, 84RFC 2080, 150RFC 2083, 95RFC 2126, 157RFC 2205, 150RFC 2236, 160RFC 2328, 150RFC 2392, 70RFC 2428, 54RFC 2452, 76RFC 2453, 150RFC 2454, 76RFC 2460, 160RFC 2465, 75RFC 2466, 75RFC 2472, 156RFC 2473, 153RFC 2474, 149RFC 2545, 151RFC 2557, 92RFC 2616, 70RFC 2740, 150RFC 2765, 152RFC 2790, 76RFC 2818, 70RFC 2819, 76RFC 2849, 62RFC 2965, 70RFC 3022, 152RFC 3030, 24RFC 3162, 84RFC 3232, 158RFC 3261, 147RFC 3308, 156RFC 3315, 53RFC 3344, 153RFC 3501, 24RFC 3550, 40RFC 3561, 127RFC 3605, 40RFC 3618, 152RFC 3633, 54RFC 3646, 53RFC 3711, 40


- 167 -

RFC 3768, 157RFC 3775, 153RFC 3776, 153RFC 3898, 53RFC 3913, 151RFC 3973, 152RFC 3977, 41RFC 4023, 152RFC 4025, 53RFC 4250, 83RFC 4271, 150RFC 4287, 88RFC 4360, 151RFC 4514, 62RFC 4594, 149RFC 4601, 152RFC 4750, 76RFC 4752, 84RFC 4760, 150RFC 4918, 26RFC 4919, 126RFC 5023, 63RFC 5246, 83RFC 5280, 84RFC 5492, 151RFC 5519, 75RFC 5555, 161RFC 5568, 153RFC 5668, 151RFC 5905, 41RFC 6477, 23RFC 6621, 152RFC 6724, 50RFC 6762, 52RFC 6763, 79RFC 6793, 151RFC 768, 157RFC 791, 159RFC 959, 40STD 89, 161

Information Systems Audit and ControlAssociation

Cobit 5, 73International Hydrographic Organisation

S-100, 97International Interface Control WorkingGroup

SCIP-120, 16SCIP-121, 16SCIP-210, 16SCIP-213, 16SCIP-213.1, 17SCIP-214, 17SCIP-214.1, 17SCIP-214.2, 17SCIP-215, 17SCIP-216, 18SCIP-220, 18SCIP-221, 18SCIP-231, 18SCIP-233, 18SCIP-233.106, 19SCIP-233.110, 19SCIP-233.202, 19SCIP-233.307, 19SCIP-233.308, 19SCIP-233.350, 20SCIP-233.401, 20SCIP-233.444, 20SCIP-233.445, 20SCIP-233.501, 20SCIP-233.518, 21SCIP-233.519, 21SCIP-233.531, 21SCIP-233.547, 21SCIP-233.562, 21SCIP-233.604, 21

ISO10303-239, 11812639, 9315836, 3915893, 15719005-1, 5619005-2, 5619107, 3019109, 6019110, 3119112, 31


- 168 -

19115, 3519117, 9619503, 674217, 898601, 918879, 889735, 117ISO 19005-3, 57ISO/IEC 19794-2:2011, 86ISO/IEC 19794-5:2005, 86ISO/IEC 19794-6:2011, 86

ISO/IEC10589, 15010646, 9010918-4, 4611172-3, 4211801, 12812087-5, 4413818, 4114443, 914495-1, 9514496, 4115408, 815444, 9515961, 11815962, 11817203, 5417363, 11817364, 11817365, 11817366, 11817367, 11818026, 3626300, 1261754-20, 128646, 117501-1, 467810, 87812, 857816, 88802-3, 1019075, 58, 599594-8, 72DIS 9660, 57

FCD 18023-1, 36FCD 18025, 36ISO/IEC 15445, 12

ITU StandardG. 993-2, 50G.652, 128G.703, 139G.704, 140G.722, 42G.722.1c, 11G.726, 42G.729, 42GI, 139H.248.1, 10H.263, 42H.264, 42H.320, 13H.323, 11J.241, 146M.2301, 77T.120, 25, 26T.30, 25T.38, 25X.411, 16Y.1540, 145Y.1541, 145Y.1542, 146

JJava Community Process

JSR 168, 72JSR 206, 9JSR 245, 10JSR 270, 9JSR 286, 72JSR 315, 10JSR 342, 9JSR 56, 10JSR 66, 9

LLizard Tech

MG2, 95


- 169 -

MMicrosoft, 157

Application Note GC0165, 11MS Office XP, 11MS-SMB - 20130118, 50MSDN-ODBCPR, 58

Multilateral Interoperability ProgramJC3IEDM, 60MIP BL 4, 60MTIDP-SEAWG-ed3.0.10-annex-b, 59, 59

NNATO

AC/322(SC/3)D(2007)0003-Rev5, 102AC/322-D(2004)0024REV2, 46, 85ACP 190(B) NATO Supp 1A, 101ACP 190(B) NATO Supp 2, 102APP-11, 14APP-11(D), 14C-M(2005)0108, 119com-sec-req, 8draft, 87MIL-STD 6020, 141NC3A-RD-2977, 27RTO-MP-IST-091, 27STANAG 1116, 114STANAG 1171, 115STANAG 1401, 110STANAG 1456, 115STANAG 2019, 96STANAG 2103, 115STANAG 2211, ed. 6, 36STANAG 2586, 36STANAG 2591, 11STANAG 3764, 45STANAG 3809, 29STANAG 4061, 115STANAG 4082, 116STANAG 4103, 116STANAG 4140, 116STANAG 4175 ed.4, 132, 142STANAG 4175 ed.5(RD), 132, 142STANAG 4203 ed.3, 134STANAG 4204 ed.3, 134

STANAG 4205, 135STANAG 4206 ed.3, 144STANAG 4207 ed.3, 144STANAG 4214 ed.2, 143STANAG 4231 ed.4, 135STANAG 4233, 138STANAG 4246 ed.3, 131STANAG 4285, 128STANAG 4290 RD, 143STANAG 4292, 130STANAG 4312 ed.2, 15STANAG 4329, 91STANAG 4372 ed.3, 131STANAG 4376 ed.1, 132STANAG 4406, 14, 23STANAG 4415, 129STANAG 4444 ed.1 (Draft), 134STANAG 4444 ed.2 (Draft), 134STANAG 4479 ed.1, 44STANAG 4481 ed.1, 129STANAG 4484 ed.2, 135STANAG 4484 ed.3 (RD), 135STANAG 4485 ed.1, 137STANAG 4485 ed.2, 137STANAG 4486 ed.2, 138STANAG 4486 ed.3, 138STANAG 4522 ed.1, 138STANAG 4529 ed.1, 129STANAG 4538 ed.1, 129STANAG 4538 ed.2, 129STANAG 4539, 129STANAG 4545 ed.2, 23STANAG 4559 ed. 3, 44STANAG 4564 ed.2, 36STANAG 4575 ed. 3, 44STANAG 4575 ed. 4, 44STANAG 4578 ed.2, 144STANAG 4586, 142, 142STANAG 4591, 43STANAG 4606 ed.1, 137STANAG 4606 ed.3, 137STANAG 4607 ed.3, 44STANAG 4609 ed.3, 45STANAG 4610, 104


- 170 -

STANAG 4622, 137STANAG 4631, 66STANAG 4681, 132STANAG 4691 ed.1, 131STANAG 4705 RD, 143STANAG 4706, 132STANAG 4711, 149STANAG 4715, 85STANAG 4724, 133STANAG 4731, 51STANAG 5000, 25STANAG 5030 ed.4, 133STANAG 5042, 96STANAG 5046 ed.3, 144STANAG 5046 ed.4, 144STANAG 5065 ed.1, 130STANAG 5066 ed.3, 130STANAG 5067 ed.1 (RD), 162STANAG 5067 ed.2 (RD), 162STANAG 5500, 14STANAG 5501 Ed.5, 141STANAG 5501 Ed.6, 141STANAG 5511 Ed.7, 103, 141STANAG 5516 Ed.4, 103STANAG 5516 Ed.5, 103STANAG 5518ed1, 101STANAG 5522 Ed.2, J-Series, 103STANAG 5522 Ed.3, J-Series, 103STANAG 5526, 61STANAG 5527, 104STANAG 5528 ed.1, 66STANAG 5602 ed.3, 102STANAG 5616 ed.5, 141STANAG 5616 ed.6, 141STANAG 6015, 116STANAG 6022, 117STANAG 7023 ed.4, 45STANAG 7024 ed.2, 45STANAG 7074, 29STANAG 7085 ed.3, 142STANAG 7098, 33STANAG 7099, 94STANAG 7163, 92STANAG 7170 ed.2, 28

STANAG 7194 ed.1, 44STANAG 7194 ed.2, 44TIDE/NVG, 94TIDE/NVG20, 94TIDE/TIDE-ID-RR, 39TIDE/TIDE-ID-SP, 79, 79TIDE/TTB, 94TN-1313, 87TN-1417, 149

NIMAMIL-PRF 89005, 34MIL-PRF-89045, 93MIL-STD-2411, 95TR 8350.2, 35

NISTFS 1016, 43

Norwegian Defence Research Establishment2010-00961, 262010-00962, 26

OOASIS

AVDL Specification - 01, 39CAP-V1.1, 127dsml, 63ebms2, 78EDXL-DE-V1.0, 39ProgrammersAPI_v2, 78regrep-rim-3.0-os, 63regrep-rs-3.0-os, 78relmes, 70, 70SAML 1.1, 71uddi-v3.00-published-20020719, 77ws-bpel, 63ws-notif, 65wsdd-discovery-1.1-spec, 78wsfed, 84wsn-ws_brokered_notification-1.3-spec-os,65wsn-ws_topics-1.3-spec-os, 65wsrp-specification-1.0, 72wsrp-specification-2.0, 72wss-username-token-profile-1.0, 22wss-v1.1-errata-os-SAMLTokenProfile, 22


- 171 -

wss-v1.1-spec-os-KerberosTokenProfile,22wss-v1.1-spec-os-SOAPMessageSecurity,69wss-v1.1-spec-os-SwAProfile, 22wss-x509-token-profile-1.0, 22wsspol-1.3, 71wssutil, 22wstrust-1.4, 22xacml-3.0-core-spec-os, 85

ODMGISBN 1-55860-647-5, 58

OMGformal-2012-06-01, 109formal/08-01-02, 10formal/2002-12-06, 126formal/2011-01-03, 64formal/2011-08-05, 69formal/2012-01-03, 89

Open Applications GroupOAGIS, 118

Open GIS Consortium01-009, 3801-024r1, 10004-038r1, 10004-094, 9805-007r7, 3405-047r3, 9905-078r4, 9706-042, 9706-050r3, 8807-006r1, 9907-036, 3307-057r7, 3707-067r5, 9807-110r4, 10007-147r2, 3708-007r1, 3408-139r3, 9309-000, 12109-025r1, 9809-026r1, 3409-110r4, 9810-090r3, 92

10-100r2, 34OGC 03-081r2, 99

Open Services Infra-Structure Initiative, 49Open Source Geospatial Foundation

1.8.2, 33OpenGL

glspec40.Core.20100311, 100OpenSearch.org

OpenSearch 1.1 Draft 4, 87OSF

F201, 49

PPS/SC Working Group

pc-sc-spec, 9

RRSA

PKCS#1 v2.1, 81RSS Advisory Board

2.0, 88

SSUN Microsystems

java_card_kit-2_2_1-fr-spec, 9JNDI, 9JSR 221, 58rmi-over-iiop, 40

TThe Open Group

C 112, 59C310, 51C702, 50C706, 49F209a, 40P702, 84T525, 55, 56, 56

tm-forumeTOM Rel.13, 73

UUSB.org

wusb, 126


- 172 -

WW3C

datetime, 91draft, 87NOTE-SOAP-20000508, 64NOTE-VML-19980513, 94NOTE-ws-policy-guidelines-20071112, 83NOTE-ws-policy-primer-20071112, 84NOTE-wsci-20020808, 69NOTE-wsdl-20010315, 79PR-sparql11-query-20121108, 86REC-CSS2-2011067, 70REC-html401-19991224, 12rec-skos-reference-20090818, 117REC-SMIL3-20081201, 10REC-SVGMobile-20030114, 93REC-WebCGM-20011217, 93REC-ws-addr-core-20060509, 65REC-ws-addr-metadata-20070904, 65REC-ws-addr-soap-20060509, 65REC-ws-policy-20070904, 83REC-wsdl20-20070626, 79REC-xforms-20031014, 88REC-xhtml1-20020801, 88REC-xlink-20010627, 67REC-xlink11-20100506, 67REC-xml-20081126, 66REC-xml-infoset-20011024, 68REC-xml-names-19990114, 68REC-xml-stylesheet-19990629, 68REC-xml11-20060816, 66REC-xmlbase-20010627, 67REC-xpath-19991119, 69REC-xsl-20061205, 68REC-xsl11-20061205, 68REC-xslt20-20070123, 68SOAP Version 1.2, 69SUBM-OWL-S-20041122, 87timezone, 51WD-exi-20070716, 68WD-html5-20121025, 12WD-SVG12-20050413, 93WD-xquery-20030502, 68xkms2, 71

xmldsig-core, 87xmlenc-core, 83, 83

WAP ForumWAP-238-WML-20010911-a, 71

Web Services Interoperability OrganisationAttachmentsProfile-1.0-2006-04-20, 65BasicSecurityProfile-1.1-2010-01-24.html ,22BP11, 64BP12, 64SimpleSoapBindingProfile-1.0-2004-08-24,64wsbp, 64

Wolrd Meteorological OrganisationFM 92-IX Ext. GRIB, 117fm94, 117

XX Consortium

X11R7.5, 40, 54XMPP Standards Foundation

XEP-0004, 13XEP-0030, 13

archive.nisp.nw3.dk · nisp volume 2 adatp-34(h)-rev3 - iii - table of contents 1. introduction

Documents