3.4. Technical Services

< Prev		Next >

3.4. Technical Services

16. Technical services provide fundamental support to service based frameworks both in the form of information integration and communication services, and in the form of COI independent general service building blocks.

17. COI services provide more specialized services in order to give the business more specific business benefits within a "domain" or "area of interest".

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

19. Information services include services that are either made available to all users by the infrastructure, 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 be voluntarily exchanged by any parties on the network.

20. Actually information services are based only on core enterprise services (CES), but may be extended in the future.

21. 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 and deployment of actual business services and processes. Such basic services are usually referred to as Core Enterpise Services.

22. Here we will provide an overview of such CESs in a BPIF context in terms of the way such services are categorized. A few examples of CESs in each category is also provided, but a complete set of well defined core services cannot be provided as it to a large extent will depend on the actual implementation of the BPIF.

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

3.4.1. Basic Infrastructure Services

24. The first main category of core services, here referred to as Basic Infrastructure Services (BIS), are used to support the infrastructure (BPIF) that support deployment, operation and management of business processes. BIS is further divided into three subcategories according to three of the main aspects of a BPIF.

Service Selection BIS are concerned with the basic mechanisms for discovery and visibility of services. Typically this encompasses basic service directories with support for syntactic description and lookup of services.
Management and operation BIS are concerned with various types of management and operation of services and infrastructure. There are at least four subcategories.
- BIS handling policies, including required security level, conditions for service delivery, availability, quality of service undertakings etc.
- Security BIS include basic functions for managing information security, and a typical example is a service that keeps track of role and person oriented authorization, distribution of keys, handling of certificates etc.
- Service Management BIS handle life cycle management of other services, including for example monitoring and configuration.
- Resource Management BIS are used to manage infrastructure resources and will be highly dependent on infrastructure implementation. A typical example is resource management in a Grid.
- Network Management BIS are concerned with networking and communication aspects of the infrastructure, and involve for example router configuration.
Process Composition BIS are concerned with support for business processes.

3.4.2. Business Service Enablers

25. The second of the main core service categories is Business Service Enablers (BSE). While BIS services are concerned with the BPIF infrastructure per se, they are not used a foundation for implementation of business services. This is instead the role of BSE, which provide basic functionality that is shared by many business services independently of Community of Interest (COI).

26. BSE are divided into three main subcategories based on the types of functionality they offer.

Collaboration BSE support basic exchange of data between services. Examples include message passing (uni- and multicast, email, etc.), distributed file sharing, publication (web pages etc.), and data format conversion.
Synchronization BSE support synchronization of service and process interaction, and includes for example time services, and event notification.
Common Information Services (CIS) is the third and last subcategory of BSE. CIS provide COI-independent support for access to general information like maps, glossaries, standards, and document registries.

27. Note: Not all functions in this category are necessarily service oriented in a SOA sense. They are nevertheless important for a network-oriented capability.

28. The third area of the technical services is the communication services. These services provide a transparent, seamless information exchange capability to allow a communication between the various information entities above.

3.4.3. List of COI Standards

SERVICECATEGORY / CATEGORY / SUBCATEGORY	MANDATORY STANDARDS	EMERGING NEAR TERM	Remarks
Generic COI Services
Meteo
Map View
Map Mgmt
Spatial Geography Visualisation
Specific COI Services
Communicate and Inform
Battlespace Mgmt
Orbat Mgmt
Overlay Mgmt
Symbol Mgmt
Tracking
		NFFI, STANAG 5527 (study)	Until the develoment of STANAG 5527 is more stable, document AC/322(SC/5)N(2006)0025 should be used. For CCEB interoperability this standard is not applicable.
Synchronisation
Distribution
Notification
Aggregation
Collaborate and Plan
Plan Workspace
Plan Analysis
Plan Briefing
Plan Replay
Plan Synchronisation
Plan Collaboration
Simulation
Collaboration analysis
Sense and Respond
Tasking
Plan Deviation Monitor
JCOP
Logistics Svcs
Supply Chain Svcs
		OAGIS 9.0, OAGi
		PLCS, ISO 10303-239:2005
		S1000D issue 4, ASD
	NATO Policy for Systems Life Cycle Mgmt (SLCM), C-M(2005)0108		SLCM is primarily based on AAP 48 and ISO/IEC 15288

3.4.4. List of Information Integration Standards

SERVICECATEGORY / CATEGORY / SUBCATEGORY	MANDATORY STANDARDS	EMERGING NEAR TERM	FADING	Remarks
Core Enterprise Services
Discovery
Service Discovery Services
	Universal Description, Discovery and Integration (UDDI) v2.0, W3C	UDDI v3.0, W3C		UDDI 2.0 provides a platform-independent way of describing- and disovering service. For CCEB interoperability UDDI 3.0 is mandatory
		Electronic Business Extensible Markup Language (ebXML) ISO/TS 15000-1:2004, -2:2004, -3:2004, -4:2004, -5:2005		ebXML is a suite of specifications for standardizing XML based business messages to facilitate trading between organisation.
		ebXML Messaging Service v. 2:2002 (OASIS)
		Resource Description Framework (RDF) (W3C)		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
		Protocol and RDF Query Language (SPARQL) (W3C)		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
		DNS Service Disvovery (DNS-SD) (ACT TIDE)		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
Information Discovery Services
		Web Ontology Language (OWL), W3C		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
Repository
	NC3 Repository			Common repository for standard data elements and their related tool for the NATO Corporate Data Model for Data Administration. See also XML. For CCEB interoperability this standard is partially applicable
Metadata Registry Services
		NATO Metadata Registry and Repository (NMRR)		For CCEB interoperability this standard is not applicable.
Enterprise Directory Services
		Common Directory Services and Procedures (ACP 133C)	ACP 133B	Contains schema.ACP 133B contains the upper layer protocol profile down to the requested Transport Service
	LDAP v3 (IETF RFC 4510:2006, 4511:2006,4512:2006, 4513:2006)			LDAP is an IETF protocol and close to a functional subset of DAP. Many Web-browsers can act as LDAP clients, which is highly desirable.
	LDIF (IETF RFC 2849:2000)			LDIF defines a flexible and almost universally accepted means of exchanging directory information via flat files.
			DSP (ITU-T X.500:2005)	DSP defines X.500 server to server communication, including chaining. For CCEB interoperability this standard is not applicable
			DSIP (ITU-T X.500:2005)	DISP defines X.500 based information shadowing/replication. For CCEB interoperability this standard is not applicable
			DOP (ITU-T X.500:2005)	Contains operational management. For CCEB interoperability this standard is not applicable
Mediation
	SQL 3 (ISO/IEC 9075(-1 to -14):2008)		Full Level and ISO/IEC 9075:1999 canceled, new Version ISO/IEC 9075(-1 to -14):2008, Parts 1, 2 and 11 encompass the minimum requirements of the language. Other parts define extensions.
	ODMG 3.0:2000 (ODMG)
	ODBC 3.8 (MS)
	JAVA DBC (JDBC)		JDBC separated from ODBC
	SQL CLI (ISO/IEC 9075-3:2008)
	DEM Data Replication Mechanism from STANAG 5525 ed. 1:2007
			NATO Corporate Data Model v2 (ADatP-32)	For CCEB interoperability this standard is partially applicable
	Spatial Schema ISO 19107:2003, DGIWG/TSMAD profiles of ISO 19107			ISO 19107 provides conceptual schemas for describing and manipulating the spatial characteristics of geographic features. The DGIWG/TSMAD profiles are intended to define sub-schemas of ISO 19107 to be used for defining data interchange formats. For CCEB interoperability this standard is emerging
	Rules for application schema ISO 19109:2005			ISO 19109 defines rules for creating and documenting application schemas, including the principles for the definition of features. Required for Geo to ensure consistency of use in the definition and use of the geographic features. For CCEB interoperability this standard is emerging
	Methodology for feature cataloguing ISO 19110:2005			ISO 19110 defines the methodology for cataloguing feature types and specifies how the classification of feature types is organized into a feature catalogue and presented to the user of a set of geographic data. For CCEB interoperability this standard is emerging
	Spatial Referencing by geographic identifiers ISO 19112:2003			ISO 19112 defines the conceptual schema for spatial references based on geographic identifiers. This standard enables gazetteers to be constructed in a consistent manner. For CCEB interoperability this standard is emerging
	Simple Feature Access, ISO 19125-1:2004 and ISO 19125-2:2004			ISO 19125-1 establishes a common architecture for geographic information (simple feature profile of ISO 19107) and defines terms to use within the architecture. It also standardizes names and geometric definitions for Types for Geometry. ISO 19125-2 specifies and SQL schema that support storage, retrieval, query and update of simple geospatial feature collections via the SQL Call Level Interface (SQL/CLI) and establishes and architecture for the implementation of feature tables. For CCEB interoperability this standard is emerging
	Joint C3 Information Exchange Data Model (JC3IEDM, STANAG 5525 ed.1:2007) for the Land environment	Joint C3 Information Exchange Data Model (JC3IEDM, STANAG 5525 ed.1:2007) for the Joint, Maritime and Air environments	C2IEDM replaced by JC3IEDM	C2IEDM replaced by JC3IEDM. For CCEB JC3IEDM is mandatory for all environments.
	WebCGM (Web Computer Graphics Metafile), W3C REC 20011217, 2001		CGM (ISO/IEC 8632:1999) not for new systems	Primarily intended for vector-based images.
	SVG 1.2:2005 (W3C)			The preferred format to visualize maps in the Web browser.
	Mobile SVG Profiles: SVG Tiny and SVG Basic, W3C REC 20030114, 2003			SVG profiles for cellphones and PDAs
		NVG - NATO Vector Graphics Protocol, ACT		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
	JPEG 2000 (ISO/IEC 15444-1:2004, ISO/IEC 15444-2:2004, ISO/IEC 15444-3:2007, including Amd 2:2003, ISO/IEC 15444-4:2004, ISO/IEC 15444-5:2003, ISO/IEC 15444-6:2003,)			JPEG 2000 is the standard used to store raster data (imagery, scanned maps, matrix data) and provides the ability to include spatial referencing information within the standard. For CCEB interoperability ISO/IEC 15444-2 Cor. 3 is not applicable.
		JPEG LS (ISO/IEC 14495:2003)		Loss-less and near loss-less compression of continuous tone still images.
			GIF (version 89a) not for new systems	Graphics Interchange Format is intended for the on-line trans-mission and inter-change of raster graphic data.
	PNG 1.0 (RFC 2083:1997)			Portable Network Graphics PNG is in-tended for the com-pressed storage of raster images. PNG provides a patent-free replacement for GIF.
	Fax G.3, ITU-T T.4:2003
	Fax Transmission, ITU-T T.30:2005
	TDF (STANAG 5000 ed.3:2006)			For CCEB interoperability Secure Telephone Equipment (STE) is used for secure fax. The emerging standard is Secure Communication Interoperability Protocol (SCIP).
	ADatP-3, CONFORMETS/Change 4 (STANAG 5500, ed.6:2007), Database Baseline 13.			For CCEB interoperability the standard is MIL-STD 6040 and OTH-T GOLD standards baseline 14 is actually under construction
	APP-11(B)/ STANAG 7149 ed.3:2008 NATO Message Catalogue	APP-11(C)/ STANAG 7149 ed.4		APP-11 (STANAG 7149) as the single source for NATO Military Messages for command and control of NATO forces at all levels of the Chain of Command down to and including individual units. For CCEB interoperability this standard is not applicable
	EDIFACT (ISO 9735:2002)			EDIFACT can be used to transfer business documents such as purchase orders, invoices, and electronic funds transfer information. ebXML is a UN standard
	DIGEST V2.0 and DIGEST V2.1, STANAG 7074 ed.2:1998, AgeoP-3 (VMaps, USRP, ASRP)			Source data may be provided in this format for conversion to the neutral database format by the CWS. Note: DGIWG is in the process of restructuring DIGEST based on the ISO 19*** standards. They are generating military specific profiles of the ISO standards. Of particular interest to the Core GIS project are profiles of: Spatial Schema (19107), General Feature Model (19109), Metadata (19115), Portrayal (19117), and FACC Data Dictionary (19126). For CCEB interoperability the mandatory standard is DGIWG Feature Data Directory 2006 and DIGEST v2.1 is fading.
			GML v3.2 (ISO 19136:2007)	This OpenGIS Consortium recommendation standard may be used as the transfer format between the FA providing the published operational data (e.g. COP) and the Core Map Application Server. For CCEB interoperability GML 3.1 is emerging
	DLMS/DTED (STANAG 3809 ed.4:2006)			Digital Terrain Elevation Exchange Format
	DLMS/DFAD1			DLMS/DFAD1 must be used until DIGEST/VMAP 1 covers the whole world. For CCEB interoperability this standard is not applicable
	World Geodetic System (WGS) 84			WGS specifies the set of parameters that define mathematically the shape of the earth
	Geographic Information - Metadata - ISO 19115:2003			This provides the most comprehensive metadata specification for digital geographic data. This shall be used for the geo metadata which forms the foundation of the Core Geo Catalogue. It is likely that a NATO profile of this standard will have to be produced based on the DGIWG profile. For CCEB interoperability this standard is emerging.
	WECDIS (STANAG 4564 ed.2:2007)			Standard for Warship Electronic Chart Display and Information Systems.
	SEDRIS (ISO/IEC 18023-1:2006)			Environmental data representation and interchange specification
	EDCS (ISO/IEC 18025:2005)			Environmental data coding specification
	SRM (ISO/IEC 18026:2009)			Spatial reference model
	Geodetic Projections, STANAG 2211 ed.6:2001
	Additional military Layers for digital geospatial data products (AML), STANAG 7170 ed.1:2003
				For CCEB interoperability the mandatory standard is MIL-STD 2525B COMMON WARFIGHTING SYMBOLOGY and the emerging standard is MIL-STD 2525C
	Joint Symbology (APP-6(B)/STANAG 2019 ed.5:2008)			For CCEB interoperability this standard is not applicable.
		Portrayal ISO/DIS 19117:2005		Currently in Draft. International Standard specifies the interface to standard symbol sets, not the symbols themselves.
	Symbols on Land Maps, Aeronautical Charts and special Naval Charts (STANAG 3675 ed.2:2000)
	IHO S-57, Version 3.1, 2000	IHO S-57, Version 4.0		Standard defined by IHO for digital maritime information. Currently in harmonisation with DIGEST. Access to S-57 data may be required by maritime users. S-57, Version 4.0 should support a greater variety of hydrographic-related digital data sources, products and customers. For CCEB interoperability IHO S-52, S-57, S-61 and S-63 standards are mandatory.
	Web Map Service v.1.3 (OGC 04-024)	ISO 19128:2005 Web Map Service		Used as a means of distributing compiled mapping data between applications.
	Web Feature Service v.1.1 (OGC 04-094)			Used as a means of distributing geo feature (vector) data between applications. For CCEB interoperability this standard is emerging
	Web Coverage Service v.1.0 (OGC 03-065r6)			Used as a means of distributing geo coverages (raster) data between applications. For CCEB interoperability this standard is emerging
		GML in JPEG 2000 for Geographic Imagery (GMLJP2) (OGC 05-047r)		This evolving OGC standard describes minimally required GML definition for georeferencing images and gives guidelines for augmenting that definition to address the additional encoding of metadata, features, annotations, styles, coordinate reference systems, and units of measure for data encoded in JP2K
		OGC Web Terrain Service and OGC Web3DService		Used as a means to perform Web Service based Terrain analysis and communicate terrain data to clients
		OGC - ISO 19115:2003/ ISO 19119:2005 Application Profile for CSW 2.0		Describes the organisation and implementation of Catalogue Services based on the ISO 19115 / ISO 19119 Application Profile
		Web Registry Service v.0.0.2 (OGC Ref. 01-024r1)		Used as a means of publishing and finding geo services.
		Catalog Interface v.1.1.1 (OGC Ref. 02-087r3 )		Used as a means of discovering geo metadata.
			Computer Graphics Interface (CGI ISO/IEC 9636:1991)	For CCEB interoperability this standard is not applicable
	OpenGL v2.0:2004		OpenGL v1.5:2003	For CCEB interoperability this standard is not applicable
	Unified Modeling Language (UML) v2.0:2003 (OMG)			For CCEB interoperability this standard is not applicable
	Codes for the representation of Currencies and Funds (ISO 4217:2008)
	Letters for Geographic Entities, STANAG 1059, ed.8:2004	Letters for Geographic Entities, STANAG 1059, ed.9		For CCEB interoperability the country codes standard is ISO 3166 trigraphs except for military messaging - see CCEB COMAG Policy On Security Labelling
	ECMA Script Language Specification (ECMA 262)			Scripting required for enhanced Web pages For CCEB interoperability this standard is not applicable
	Zip			Implementations of zip (e.g. Winzip) also includes gzip (RFC 1952:1996) and tar/compress
			7-bit Coded Character-set for Info Exchange (ASCII) (ISO/IEC 646:1991)
			8-bit Single-Byte Coded Graphic Char Sets (ISO/IEC 8859-1-6,8-10:1999; 7:2003)
	Universal Multiple Octet Coded Char Set (UCS) - Part 1 (ISO/IEC 10646:2003)
	NATO Standard Bar Code Symbology (STANAG 4329 ed.2:2004)	NATO Standard Bar Code Symbology (STANAG 4329 ed.3)		STANAG 4329 is a cover STANAG of ISO 16388:1999 - Bar code symbology specifications - Code 39.
	Bar code symbology specification - Code 128 (ISO/IEC 15417:2007), Bar code print quality test specification -Linear symbols (ISO/IEC 15416:2000)
	Representation of Dates and Times (ISO 8601:2004)
	UUENCODE (UNIX 98), MIME (IETF RFC 2045:1996 updated by 2184:1997, 2231:1997, 5335:2008; 2046:1996 updated by 3676:2004, 3798:2004, 5147:2008; 2047:1996 updated by 2184:1997, 2231:1997, 5338:2008; 4288:2005, 4289:2005; 2049:1996)	S/MIME ESS (IETF RFC 3850:2004, 3851:2004)		Base64 is included in RFC 2045:1996
Composition Services
Translation Services
Interaction
Messaging Services
	Military Messaging (STANAG 4406 Ed.2)		Use of PCT within STANAG 4406 is fading	Used for Formal Messaging. STANAG 4406 contains the upper layer protocol profile down to the requested Transport Service. For CCEB interoperability the mandatory standard is ACP123A.
	Enhanced Security Services (ESS) for S/MIME, STANAG 4631 Ed.1			STANAG 4631 contains an additional S/MIME profile for MMMHS (in addition to PCT) For CCEB interoperability the mandatory standard is ACP123A.
			X.400:1993 deleted for informal messaging, as no concrete requirement from MMHSWG
			Interoperability of telebriefing systems (STANAG 5059) deleted
			Interoperability standards for telebriefing systems (STANAG 4339) deleted
	SMTP (IETF RFCs 1870:1995, 1985:1996, 2034:1996, 2920:2000, 3207:2002, 3461:2003 updated by 3798:2004, 3885:2004, 4954:2007, 5321:2008)			Used for interpersonal messaging (email)
	POP3 (IETF RFC 1939:1996 updated by 1957:1996, 2449:1998)			For CCEB interoperability this standard is not applicable
	IMAP4 (IETF RFC 3501:2003 updated by 4466:2006, 4469:2006, 4551:2006, 5032:2007, 5182:2008)			For CCEB interoperability this standard is not applicable
		Interim Implementation Guide for ACP 123/STANAG 4406 Messaging Services between Nations (ACP 145)		Provides gateway between ACP 123A messaging services. For CCEB interoperability this standard is mandatory
Publish/Subscribe Services
Transaction Services
Collaboration Services
		XMPP (IETF RFC 3920:2004 - 3923:2004)		For CCEB interoperability this standard is mandatory
	Packet-based Multimedia Comms System (ITU-T H.323:2006)
		Session Initialisation Protocol (SIP) (IETF RFC 3261:2002)
	Multinational Videoconferencing Services (ACP 220:2003)
	Narrow-band visual telephone systems and terminal equipmment (ITU-T H.320:2004)
	Media Gateway Control Protocol v3(ITU-T H.248.1:2005)			Protocol for managing the multi-media gateways between circuit switched and packet switched networks.
	ITU Multi-point still image and Annotation Conference Protocol Spec (ITU-T T.120:2007), T.126:2007 (Reference to T.122 - T.125)
	Data Protocols for Multimedia Conferencing (ITU-T T.120:2007, T.128:2008)
Infrastructure
		Distributed Computing Environment (DCE) v1.1:1997 (OSF)
		Open Network Computing (ONC) 1.1 (The Open Group)
		DCE RPC v1.1 (The Open Group)
		Remote Procedure Call (MS-RPC) (MS)		As part of MS Windows 2000 Interfaces
	X Window (see UI Svc)
		DCE DFS v1.1
		X/Open Network File System (XNFS) 3W (The Open Group)		Includes RFC 1094:1989 (NFS 89) and RFC 1813:1995 (NFS95)
		Server Message Block (MS-SMB) (MS)		As part of MS Windows 2000
		DCE DTS v1.1		DCE DTS uses TPI (Time Provider Interface) to access other distributed time services (such as NTP as mentioned under Comms Service).
		CORBA/IIOP 2.2
			MS-DCOM	As part of MS Windows 2000 Interfaces; DCOM only in local environment, not for outside.
	Standardised Information technology Protocols for Distributed Interactive Simulation (DIS)(STANAG 4482 ed.1:1995)		STANAG 4482 should be migrated to IEEE Std 1278:1998	For CCEB interoperability the mandatory standard is IEEE Std 1278.1a:1998 STANAG 4482 should also be migrated to IEEE Std 1278:1998
		Modeling and Simulation High Level Architecture (HLA) (IEEE 1516:2000)		For CCEB interoperability this standard is mandatory
Application Services
	FTP (IETF STD 9:1985,IETF RFC 0959:1985 updated by RFC 2228:1997, 2640:1999, 2773:2000, 3659:2007)
		FTP Extensions for IPv6 and NATs (IETF RFC 2428:1998)
	Telnet (IETF STD 8:1983, IETF RFC 0854:1983 updated by RFC 5198:2008, 0855:1983)
	Network News Transfer Protocol NNTP (IETF RFC 3977:2006)
	Network Time Protocol (NTP)(RFC 1305:1992)
			MPEG-1 (ISO/IEC 11172:1993)
	MPEG-2 (ISO/IEC 13818:2000)
	MPEG-4 (ISO/IEC 14496:2004)			Encoding standard for video conferencing
	Compact Disc File System (CDFS) (ISO 9660:1988)			For physical media distribution (CD)
	Pulse Code Modulation (PCM) (ISO/IEC 11172-3:1993, ITU-T G.711:1988)			PCM used for audio in ISDN Systems
	Differential PCM (ITU-T G.726:1990)
			Delta-Modulation DM, EUROCOM D/0
	GSM-Modulation (GSM 06.10, GSM 06.20)			Used for mobile phones
		Voice Coding Algorithm (STANAG 4444 ed.1).		Used for HF voice communications as defined in STANAG 4444.
			Linear Predictive Coding-10 (STANAG 4198 ed.1:1984)
	Code Excited Linear Prediction coding (CELP) (FS 1016:1991)			CELP is used military aircraft voice communications in narrow band UHF networks. CELP has higher throughput than LPC-10, but a lower range.
	Mixed Excitation Linear Predictive coding (MELPe) (STANAG 4591 Ed.1)			MELPe is used for HF voice communications in narrow band systems.
			STANAG 4421 deleted as it is cancelled by NATO
	Parameters and Coding Standards for 800 bps. Digital Speech Encoder/Decoder (STANAG 4479 ed.1:2002)			For CCEB interoperability this standard is not applicable
	SIMPLE (STANAG 5602 ed.2)	SIMPLE (STANAG 5602 ed.3)		SIMPLE provides specifications to interconnect ground rigs of all types for TDL interoperability testing
	Nato Secondary Imagery Format (NSIF), STANAG 4545 ed 1.:1998			NSIF establishes the format for exchange of electronic secondary imagery
	BIIF (ISO 12087-5:1998)
	NSILI (STANAG 4559 ed.2:2007)			NSILI provides interoperability between NATO nations reconnaissance databases and product libraries
	NADS (STANAG 4575 ed.3:2009)			NADS defines an interface for advanced digital storage systems.
	GMTIF (STANAG 4607 ed.2:2007)			GMTIF defines a ground moving target indicator format.
	DMIS (STANAG 4609 ed.2:2007)			DMIS defines a digital motion imagery standard. For CCEB interoperability this standard is not applicable.
	NPIF (STANAG 7023 ed.3:2004)	NPIF (STANAG 7023 ed.4)		NPIF establishes a standard data format and a standard transport architecture for the transfer of reconnaissance and surveillance imagery and associated auxiliary
	AR-TRI (STANAG 7024 ed.2:2001)			AR-TRI establishes the physical format for the exchange of magnetic tape cartridges
	Exchange of Imagery (STANAG 3764 ed.6:2008)
	Implementing JPEG 2000 in NITFS/BIIF/NSIF (SC24 ISO Registered Profile)			This profile defines the limits of the international standard that can be used within NITF 2.1.
	Link-11 (STANAG 5511 ed.6:2008, M-Series)	Link-11 (STANAG 5511 ed.7, M-Series)		For further guidance refer to the Bi-SC Data Link Migration Strategy, November 2000. For CCEB interoperability the standard is MIL-STD 6011C
	Link-16 (STANAG 5516 ed.4:2008, J-Series)	Link-16 (STANAG 5516 ed.5, J-Series)		For CCEB interoperability the mandatory standard is MIL-STD 6016C Change 1 and the emerging standard is MIL-STD 6016D
	Link-22 (STANAG 5522 ed.2:2008, J-Series)	Link-22 (STANAG 5522 ed.3, J-Series)
			Link-14 (STANAG 5514 ed.2:2002)	The Link-14 is a legacy system that most NATO nations have no intention to implement in new platforms other than interfacing data link buffers and have ceased to use or maintain. Therefore considered fading
	PDF-Format 1.4		Formets deleted in NCSP v.6	Portable document presentation format, realised in Adobe product versions 5 and 6. Used in Minerva system at NATO HQ For CCEB interoperability the primary standard is Adobe Postscript (level I and II)/Encapsulated Postscript (EPS), and the secondary standard is Adobe PDF
	Rich Text Format (RTF)			Basic document interchange format
	ASCII Text, ISO 646:1991			For constrained environments
	UTF-8 (IETF RFC 3629:2003)			Universal Text Format
	Document Object Model (DOM) Level 3		Document Object Model (DOM) Level 2	Basic Document Object Model .
	Office XP formats		Office 2000 formats: Office XP	Office200-formats Not to be used for new systems. Pertains to the interchange formats of MS Word, Excel and PowerPoint, irrespective of the actual MS Office version or general office automation package being used.
	OpenDocument ISO/IEC 26300:2006			Formerly published as OASIS standard.
	HTML 4.01 (RFC 2854:2000)
	XHTML 1.0:2002 (W3C)			XHTML is specified in XML
	SGML (ISO 8879:1986)			For high value complex documents
Storage Services
Web Services
	HTTP v. 1.1 (IETF RFC 2616:1999 updated by RFC 2817:2000), URL (RFC 4248:2005, 4266:2005), URI (RFC 3986:2005)
	HTTPS (IETF RFC 2818:2000)
		Web Services Business Process Execution Language (WSBPEL) v.2:2007, OASIS
		Web Service Choreography Interface (WSCI) v.1:2002
		Business Process Management Language (BPML) v.0.4
		Open Services Infrastructure (OpenSiS) v.1.9.5.6, OpenSIS
		Java Enterprise Edition 1.4 Specification (J2EE 1.4), (JCP:2002)
		Java Remote Method Invocation (JRMI), (JCP)
		DSML v2.0:2001, OASIS		DSML provides a Dircetory Access via a Web interface
		NATO TIDE Information Discovery (Request-Response), ACT		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
		NATO TIDE Information Discovery (Subscribe-Publish), ACT		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
		WSDL v1.1:2001, W3C		For CCEB interoperability WSDL v1.1 is mandatory
	XML 1.0 2nd ed:2003, W3C	XML 1.0 3rd ed:2004, W3C		Where semantic tags are required, the NC3 Repository serves as an XML registry (see Data Management).
		XLink 1.0:2001, W3C		XLink is used to point to resources from XML documents.
		XPointer 1.0:2001, W3C		XPointer is used to identify XML fragment inside any given XML documents.
		Relax NG (ISO/IEC 19757-2:2008)		Relax NG may be a replacement for XML schema languages.
	XML Base:2001, W3C
	XML Infoset:2001, W3C
	XSL Association:1999, W3C
	Namespaces in XML (xml-names-19990114:1999)
	Extensible Stylesheet Language Transformation (XSLT) 1.0:1999
	Extensible Stylesheet Language (XSL) 1.0:2001
	XML Schema, Part 0-2:2001
	Wireless Markup Language (WML) 2.0:2001			WML to be used with Wireless Application Protocol (WAP) for constrained environments
		Efficient XML Interchange Format (EXI) v1.0		Efficient implementations of XML in the tactical environment
		XML Path Language (XPath) v2.0:2003, W3C		For CCEB interoperability this standard is mandatory
	WS-I Web Service Basic Profile, v1.1:2nd ed. 2006	WS-I Web Service Basic Profile, v1.2:3rd ed. 2007		For CCEB interoperability this profile is mandatory
	Simple Object Access Protocol v1.1 (SOAP), W3C	Simple Object Access Protocol v1.2 (SOAP), W3C		Could be used in support of the Geo Web Services.
		WS-I Simple SOAP Binding Profile v1.0:2004		For CCEB interoperability this profile is mandatory
		WS-I Attachments Profile v1.0:2nd ed. 2006		For CCEB interoperability this profile is mandatory
Device Independent Console
	X Window System 11 R6.6		X Window System 11 R5	The R6.6 release addresses a portion of the backlog of bug reports since Release 6.5.1 patch 1, along with additional fixes from the Xfree86 community. R5 should not be used for future systems. For CCEB interoperability this standard is not applicable
	Win 32 APIs			As part of MS Windows 2000 Interfaces For CCEB interoperability this standard is not applicable
	CDE 2.1		CDE 1.0	Common Desktop Environment is the UNIX Windows Desktop equivalent. For CCEB interoperability this standard is not applicable
	Motif/CDE Style Guide Rev 2.1		Motif Style Guide Rev 1.2	Toolkit specific style guides For CCEB interoperability this standard is not applicable
	MS Windows Interface Guidelines for Software Design			Toolkit specific style guides. As part of MS Windows 2000 Interfaces. For CCEB interoperability this standard is not applicable
	Motif 2.1		Motif 1.2	For CCEB interoperability this standard is not applicable
			US DoD HCI Style Guide Version 4.0 Dec 2000 not for use in new systems	For CCEB interoperability this standard is not applicable
			UK Army CIS Style Guide V 2.0 not for use in new systems	For CCEB interoperability this standard is not applicable
Content Mgmt
		Semantics of Business Vocabulary and Business Rules, Vers. 1.0 (SBVR); OMG 2008

3.4.5. List of Communications Standards

SERVICECATEGORY / CATEGORY / SUBCATEGORY	MANDATORY STANDARDS	EMERGING NEAR TERM	FADING	Remarks
Network and Transport Services
	DNS (IETF STD 13:1987, RFC 1034:1987 and RFC 1035:1987 updated by RFC 1101:1989, 1183:1990, updated by 5395:2008; 1706:1994, 1876:1996, 1982:1996, 1995:1996, 1996:1996, 2136:1997, 2181:1997, updated by 5452: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)			Bind version 9 or later should be used.
		mDNS (IETF Draft draft-cheshire-dnsext-multicastdns-06.txt)		Part of TIDE specification at ACT. For CCEB interoperability this standard is not applicable.
		IPSec Material in DNS (RFC 4025:2005)
				NACOSA Operating Instructions A-03-06 deals with the TCP/IP environment and A-03-07 deals with the OSI environment. Both are due for re-write.
	Assigned Numbers (RFC 3232:2002)
	IPv4 (STD 5, RFC 791:1981, 792:1981, 894:1984, 919:1984, 922:1984, 950:1985 updated by RFC 1112:1989, 2474:1998, 2507:1999, 2508:1999, 3168:2001, 3260:2002, 3376:2002, 4604:2006, 4884:2007)	IPv6 (RFC 1981: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 updated by 3590: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, 4213:2005, 4291:2006, 4311:2005, 4338:2006, 4489:2006, 4443:2006, 4489:2006, 4604:2006, 4861:2007, 4862:2007, 4884:2007, 4941:2007, 5095:2007, 5494:2009)		Note: Category of RFC 2375:1998 is ´Informal´
		IGMP v.3 (RFC 3376:2002 updated by 4604:2006)		RFC 3367:2002 obsoleted 2236:1997 updates RFC 1112:1989 and is widely implemented, RFC 3376:2002 obsoleted RFC 2236:1997
	Host requirements (STD 3, IETF RFC 1122:1989 updated by 2474:1998, 2181:1997, 3168:2001, 3260:2002, 4033:2005, 4034:2005, 4035:2005, 4343:2006, 4379:2006, 4470:2009, 5452:2009, 5462:2009)
			Bootstrap Protocol, BOOTP (RFC 951:1985 updated by RFC 1542:1993, 2132:1997, 3442:2002, 3942:2004, 4361:2006, 4833:2007, 5494:2009)	Will be overtaken by the richer DHCP. BOOTP is still available in older implementations and is expected to phase out.
			Clarifications and Extensions for the Bootstrap Protocol (RFC 1542:1993)
		DHCP for IPv6 (RFC 3315:2003 updated by 4361:2006, 5494:2009)	DHCP Options and BOOTP Vendor Extensions not to be used in new systems
		Dual Stack IPv6 mobility support (RFC 5555:2009)
		IPv6 Prefix Options for DHCPv6 (RFC 3633:2003)
		DNS Configuration Options for DHCPv6 (RFC 3646:2003)
		NIS-Options for DHCPv6 (RFC 3898:2004)
	Dynamic Host Configuration Protocol, DHCP (RFC 2131:1997 updated by RFC 3396:2002, 4361:2006, 5494:2009)
	Differentiated Services Field (RFC 2474:1998 updated by 3168:2001, 3260:2002)			DiffServ redefines use of former TOS field; first, but not sufficient RFC to differentiate traffic classes. RFC for DiffServ still missing. Applicable to both IPv4 and IPv6
	Requirements for IPv4 routers (RFC 1812:1995 updated by 2644:1999)
	Open Shortest Path First (OSPFv2) (RFC 2328:1998)	OSPF for IPv6 (RFC 5340:2008)		Suitable for LANs as well as WANs (including tactical networks) with sufficient bandwidth
	Router Internet Protocol (RIP v2) (IETF STD 56/RFC 2453:1998 updated by 4822:2007)	RIPng for IPv6 (RFC 2080:1997)
	Border Gateway Protocol (BGP4) (RFC 4271:2006)	Multiprotocol Extensions for BGP-4 (RFC 4760:2007); Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing (RFC 2545:1999)
		BGMP (RFC 3913:2004)
	Application of BGP-4 (RFC 1772:1995)
	Protocol Independent Multicast Sparse Mode(PIM-SM) (RFC 4601:2006, updated by 5059:2008)			PIM-SM is implemented by the router market leaders.
		Protocol Independent Multicasting Dense Mode(PIM-DM) (RFC 3973:2005)		PIM-DM is included as a second concept for tactical networks
		Generic Routing Encapsulation (GRE) (RFC 4023:2005, updated by 5332:2008)		GRE is included as a general routing encapsulation mechanism
	Traditional IP Network Address Translator (RFC 3022:2001)
		Stateless IP/ICMP Translation Algorithm (SIIT) (RFC 2765:2000
		Generic Packet Tunneling in IPv6 (RFC 2473:1998)		This RFC is a generic tunnel mechanism, which can be applied for several protocols.
	Router Internet Protocol (RIP v2) MIB extension (RFC 1724:1994)		To be used only in static networks.	To be used in static networks. See also System Management.
	Classless Inter Domain Routing (CIDR) (RFC 4632:2006)			CIDR is only valid for IPv4
	Mobile IPv4 (RFC 3344:2002 updated by 4721:2007)	Mobile IPv6 (RFC 3775:2004)
		Mobile IPv6 Fast Handovers (RFC 5568:2009)
		IPSec and Mobile IPv6 (RFC 3776:2004 updated by 4877:2007)
		Policy-based Network Management - General (RFC 1104:1989, 2753:2000, 3198:2001, 3334:2002)
		Policy-based Network Management - DiffServ (RFC 2963:2000, 2998:2000, 3086:2001, 3260:2002, 3287:2002, 3289:2002, 3290:2002, 3308:2002, 3496:2003)
		Policy-based Network Management - IntServ (RFC 2205:1997 updated by 2750:2000, 3936:2004, 4495:2006, 2206 - 2210:1997, 2380:1998, 2382:1998, 2430:1998, 2490:1999, 2745 - 2746:2000, 2747:2000 updated by 3097:2001, 2749:2000, 2750:2000, 2755:2000, 2814:2000, 2872:2000, 2961:2001, updated by 5063:2007; 2996:2000, 3097:2001, 3175:2001, updated by 5350:2008; 3181:2001, 3182:2001, 3209:2001 updated by 3936:2004, 4874:2007; 3210:2001, 3468:2003, 3473:2003 updated by 4003:2005; 3474:2003, 3476:2003, 3477:2003 4201:2005, 4783:2006, 4873:2007, 4874:2007, 5250:2008, 5420:2009
	Point to Point Protocol (PPP) Internet Protocol Control Protocol (IPCP) (RFC 1332:1992 updated by 3241:2002, 4815:2007)			To allow packet switched services over circuit switched interconnections.
	Link Control Protocol (LCP) extensions (RFC 1570:1994 updated by 2484:1999)			Addition to LLC1 (see Link Layer).
	Point to Point Protocol (PPP) (STD 51, RFC 1661:1994 updated by 2153:1997; 1662:1994, updated by 5342:2008)	IPv6 over PPP (RFC 5072:2007, 5172:2008)
	PPP Challenge Handshake Authentication Protocol (CHAP) (RFC 1994:1996 updated by 2484:1999)			Used in routers
	PPP Multilink (MP) (RFC 1990:1996)			Allows for aggregation of bandwidth via multiple simultaneous data link connections
	Virtual Router Redundancy Protocol (VRRP), IETF RFC 3768:2004
	Winsock 2 (Revision 2.2)
			Transport Service (ISO 8072:1996)deleted in NCSP v.6
	TCP (IETF STD 7:1981, RFC 0793:1981 updated by RFC 1122:1989, 3168:2001)
	UDP (IETF STD 6:1980, RFC 0768:1980)
	OSI transport svc over TCP/IP (RFC 2126:1997)			Includes the ISO Transport Protocol
Mixed DISA standards
Data Link and Connection Service
External Networks
			X.25 (1996, Cor.1:1998)
		Tactical Communications Post 2000, Draft STANAGs 4637ed1:2009, 4639ed1:2009, 4640ed1:2009, 4643ed1:2009 4644ed1:2009, 4645ed1:2009, 4646ed1:2009, 4647ed1:2009
	ISDN: ITU-T G, I Series			ISDN Telephony
			ITU-T E, P, Q, V Series
			ITU-T V.90:1998
			ITU-T V.42:2002 Corrigendum 1:2003
			User Network Interface - UNI v4.0 (af-sig-0061.000)
			Private Network - Network Interface - PNNI v1 (af-pnni-0055.000)
			LAN Emulation over ATM - LANE v2.0 (af-lane-0084.000, af-lane-0112.000)	For CCEB interoperability this standard is not applicable.
	Standards for Data Forwarding between Tactical Data Systems employing Link-11/11B and Link-16 (STANAG 5616 ed.4:2008)	Standards for Data Forwarding between Tactical Data Systems employing Link-11/11B and Link-16 (STANAG 5616 ed.5)		Gateway between Link-11 and Link-16. For CCEB interoperability the mandatory standard is MIL-STD 6020
	Link 11 STANAG 5511 ed.6:2008	Link 11 STANAG 5511 ed.7		Communications part for Link-11 For CCEB interoperability the standard is MIL-STD 6011C
	STANAG 4175 ed.3:2001	STANAG 4175 ed.4		Communications part for Link-16
	STANAG 7085 ed.2:2004 (IDL for Imaging Systems)			STANAG 7085 provides the interoperability standards for 3 classes of imagery DL used for primary imagery data transmission.
	STANAG 4586 ed.2:2007			STANAG 4586 facilitates communication between a UCS and different UAVs and their payloads as well as multiple C4I users.
Tactical Area Comms
		Maritime Tactical Wide Area Networking		For CCEB interoperability the mandatory standard is ACP 200: Maritime Tactical Wide Area Networking
	Routing and Directory for tactical Systems, STANAG 4214 ed.2:2005
		Gateway Multichannel Cable Link (Optical), STANAG 4290 ed.1 (RD)
	Enhanced Digital Strategic Tactical Gateway (EDSTG) (STANAG 4578 ed. 2:2009)		STANAG 4249 replaced by the more fundamental STANAG 4206. STANAG 4206 not to be used for new systems.	STANAG is currently under review for a new edition. For CCEB interoperability this standard is not applicable.
	NATO Multi-channel tactical digital Gateway (STANAG 4206: Ed.3:1999)			The overlapping area between STANAG 4206 and STANAG 4578 has to be resolved by SC/6. For CCEB interoperability this standard is not applicable
	The NATO Military Communications Directory System, STANAG 5046 ed.3
		Interconnection of IPv4 Networks at Mission Secret and Unclassified Security Levels, STANAG 5067 ed.1 (RD)
Transmission
	FDDI, ISO 9314:1989			For CCEB interoperability this standard is not applicable.
		STANAG 4444 ed.1 (Slow hop ECCM)		HF standard for Link-22. For CCEB interoperability this STANAG is mandatory.
		JREAP, MIL-STD 3011
	ISO/IEC 8802-3:2000 (CSMA/CD)
				For CCEB interoperability the mandatory standard is Interoperability and Performance Standard for SATCOM (MIL-STD 188-164).
				For CCEB interoperability the mandatory standard is MIL-STD-188-181B
				For CCEB interoperability the mandatory standard is Interoperability Standard for 5-Khz UHF DAMA Terminal Waveform MIL-STD-188-182A
				For CCEB interoperability the mandatory standard is DoD Interface Standard, Interoperability of UHF MILSATCOM DAMA Control System MIL-STD-188-185
				For CCEB interoperability the mandatory standard is Interoperability and Performance Standards for C-Band, X-Band, and Ku-Band SHF Satellite Communications Earth Terminals, 13 Jan 1995 MIL-STD-188-164
				For CCEB interoperability the mandatory standard is Interoperability and Performance Standards for SHF Satellite Communications PSK Modems (Frequency Division Multiple Access (FDMA) Operations), 13 January 1995, with Notice of Change 1, 9 September 1998, MIL-STD-188-165
		ECM-resistant digital traffic exchange between tactical satellite communications terminals (STANAG 4271 ed.1)		For CCEB interoperability this standard is not applicable
	ACP 190 (B)
	ACP 190 (B) NATO Suppl 1A			Spectrum Supportability Request/Comment is a two-way commitment between the (host)nation owing the system and each nation hosting the system: - it is a prerequisite for the procuring nation/agency to perate SDEs in a host nation. - host nations granting support to a SDE is expected to assign frequencies when requested. Failure to follow this process will have very negative long-term impacts: - an ever growing risk of interference between own systems. - the ever-increasing pressure from the commercial sector: having an accurate view of military use of spectrum is an essential precondition to be able to defend it against civil encroachment. For CCEB interoperability this standard is not applicable.
	ACP 190 (B) NATO Suppl 2			For CCEB interoperability this standard is not applicable
	SMADEF XML Rel.1.2.2	SMADEF XML Rel.1.2.3		For CCEB interoperability Rel.1.2.3 is mandatory
				For CCEB interoperability the mandatory standard is Equipment Technical Design Standards for Common Long Haul/Tactical Radio Communications in the LF Band and Lower Frequency Bands MIL STD 188-140A
				For CCEB interoperability the mandatory standard is Digital Line-of-Sight (LOS) Microwave Radio Equipment, 7 May 1987 MIL STD 188-145
	MIDS terminals STANAG 4175 ed. 3:2001	MIDS terminals STANAG 4175 ed. 4
			Single serial line interface (RS-232)
			Multi-point serial line (RS-422/RS-423)
	Serial binary data exchange at DTE and DCE (RS-530)
	Generic specification for optical wave-guide fibers (EIA 4920000: 1997)
VLF
	VLF and LF Broadcast OOK Systems, STANAG 5030ed.4
HF
	Conditions for interoperability of 2400 BPS / HF (STANAG 4197 ed.1:1984)			(QSTAG 1108)
	Technical standards for single channel HF radio equipment, STANAG 4203 ed.3:2007			For CCEB interoperability the mandatory standard is MIL STD 188-141A
	Characteristics of 1200/2400/ 3600 bps single tone modulators/demodulators for HF Radio links (STANAG 4285 ed.1:1989)			For CCEB interoperability the mandatory standard is MIL-STD-188-110A
	Non-Hopping Serial TONE HF Radio, STANAG 4415 ed.1:1999
		HF Radios STANAG 4444 ed.1
	Minimum Standards for Naval Shore-to-Ship Broadcast Systems, STANAG 4481 ed.1
	Automatic Radio Control System for HF Links STANAG 4538 ed.1:2009
	Non-hopping HF Communications Waveforms STANAG 4539 ed.1:2006
	Profile for HF radio data communications (STANAG 5066 ed.2:2008)
VHF
	Technical standards for single channel VHF radio equipment STANAG 4204 ed.3:2008			For CCEB interoperability the mandatory standard is MIL STD 188-242
	Communication between Single Channel and Frequency Hopping Radios in VHF, STANAG 4292 ed.2:1987
	Non-secure Voice Interoperability for VHF Radios, STANAG 4448 ed.1:2006
	Secure Voice and Data Interface for VHF Radios, STANAG 4449 ed.1:2006
UHF
	Technical standards for single channel UHF radio equipment STANAG 4205 ed.3:2005			For CCEB interoperability the mandatory standard is MIL STD 188-243
			UHF Radios STANAG 4246 ed.2:1987	For CCEB interoperability this standard is not applicable
	STANAG 4372 ed.3:2008 (Saturn)			UHF standard for Link-22, but can also carry Link-11 and Link-16 messages.
UHF SATCOM
	Interoperability Standard for 25 kHz UHF/ TDMA/DAMA terminal Waveform STANAG 4231 ed.4:2004			STANAG 4231 ed.4 is identical with MILSTD-188-183B. For CCEB interoperability the mandatory standard is MIL-STD-188-183D
				For CCEB interoperability the mandatory standard is Interoperability and Performance Standard for the Data Control Waveform MIL-STD-188-184
		UHF MILSATCOM interoperability standards for paging receiver (Draft) (STANAG 4492 ed. 1)		For CCEB interoperability this standard is not applicable
SHF SATCOM
	Super High Frequency (SHF) Military Satellite (MILSATCOM) jam- resistant modem (STANAG 4376 ed.1:1998)			For CCEB interoperability this standard is not applicable
	Overall Super High Frequency (SHF) Military Satellite COMmunications (MILSATCOM) interoperability standards (STANAG 4484 ed.2:2003)			For CCEB interoperability this standard is not applicable
	SHF MILSATCOM Non-EPM modem for services conforming to class-A of STANAG 4484 (STANAG 4485 ed.1:2002)			For CCEB interoperability this standard is not applicable
	Super High Frequency (SHF) Military Satellite COMmunications (MILSATCOM) Frequency Division Multiple Access (FDMA) Non-EPM modem for services conforming to class-B of STANAG 4484 (STANAG 4486 ed.2:2002)			For CCEB interoperability this standard is not applicable
	Super High Frequency (SHF) Medium Data Rate (MDR) Military Satellite COMmunications (MILSATCOM) jam-resistant modem interoperability standards (STANAG 4606 ed.1:2009)	Super High Frequency (SHF) Medium Data Rate (MDR) Military Satellite COMmunications (MILSATCOM) jam-resistant modem interoperability standards (STANAG 4606 ed.2)		For CCEB interoperability this standard is not applicable
		Interoperability standard for Satellite Broadcast Services (SBS) (Draft) (STANAG 4622 ed.1 RD2)		For CCEB interoperability this standard is not applicable
EHF SATCOM
	Digital interoperability between EHF Tactical Satellite Communications Terminals (STANAG 4233 ed.1:1998)			For CCEB interoperability the mandatory standard is MIL-STD-1582D
	EHF MIL SATCOM interoperability standards for medium data rate services STANAG 4522 ed.1:2006			For CCEB interoperability the mandatory standard is MIL-STD-188-136
QoS
			DoD Guide to selecting computerbased multi-media standards, technologies, products and practices deleted in NCSP v.6

< Prev	Up	Next >
	Home