1. CENTRIXS-ISAF: Phase 1 Overview
Jesse Scott
NC3A CAT 7: Core Enterprise Services
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

2. NATO UNCLASSIFIED Releasable to ISAF
Agenda
1. Transformation of Afghanistan Coalition Networks
2. CENTRIXS-ISAF Interconnection Overview
3. A Common Mission Network
4. Operational Use
5. Mission Applications & Interoperability
6. The Way Ahead (Phase 2, HoA, Additional Nations)
NATO UNCLASSIFIED Releasable to ISAF

3. Coalition Network Transformation
CENTRIXS-GCTF Cross-Domain Gateway (2006)
Procured by US and NATO
Allowing bi-directional and tracks through guards
UK Overtask Extension (2007)
Extension of NATO CIS to the UK bases in the south
Procured and deployed by the UK
Managed by NATO and UK
CENTRIXS-ISAF Interconnection (2009)
Procured by US and NATO (interconnection only)
Direct connection of the two networks with no guards
Connection managed by US and NATO
NATO networks get extended by NATO nations. The MISSION SECRET – COALITION SECRET connection using IEG fails.
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

4. Overview of the ISAF Networks
FOC+ ISAF
NATO ISAF
NATO
FOC+
KAF
KABUL
FOC+ primary connection
IOC connection
FOC+ SATCOM
Anchor connection
FOC+ secondary connection
IOC infrastructure
location
FOC+ infrastructure
SATCOM anchor
Gateway connection
CENTRIXS-ISAF
UK Overtask
infrastructure
CENTRIXS-ISAF
infrastructure
UK Overtask
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

5. Pre-CENTRIXS-ISAF IERs
NATO NS
SIPR
COP
CHAT
FILE (R)
COP
WEB
FILE (G)
FMV
COP
FMV
FILE (R)
CIDNE
CHAT
NITB
VOIP
GCTF
VoIP
ISAF MS
CHAT
OVERTASK UK
IER
OPERATIONAL
IN PROGRESS
REQUIRED
IER
IER
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

6. Creation of new CENTRIXS-ISAF network
National expansion of ISAF Secret network (e.g. Overtask Model) was not feasible for U.S. (funding and support structures)
Implementation Approach
Establish a new baseline (STIG = SIPRnet standards) and upgrade the CENTRIXS network in order to stand up CENTRIXS-ISAF within Afghanistan.
Remove ~5% non-ISAF TCN users to a separate network
Move CDG between CENTRIX-ISAF and CENTRIXS-GCTF
Establish two interconnection points (Kabul and KAF) between CENTRIXS-ISAF and ISAF Secret
NATO UNCLASSIFIED Releasable to ISAF

7. ISAF Current networks and Information Exchange Requirement
NATO NS
US SIPR
CHAT
FMV
FILE
COP
FMV
FILE (R)
COP
CIDNE
COP
WEB
NITB
VOIP
CHAT
VoIP
CENTRIXS
ISAF
NATO
ISAF
VOIP
CENTRIXS
GCTF
CHAT
FILE
CHAT
FMV
COP
OVERTASK UK
41 TCN Coalition Zone
IER
OPERATIONAL
IN PROGRESS
REQUIRED
IER
IER
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

8. Post-Phase 1 CXI Connectivity
N ATO SECRET
Service Provision Authority: U.S. ARCENT
, one-way http
one-way http
ISAF Coalition Information Domain
ISAF SECRET
(41 TCN)
CENTRIXS -ISAF
(41 TCN)
CENTRIXS -GCTF
(existing) Cross Domain Gateways ( , Chat, VoIP)
Service Provision Authority: NATO CIS Services Agency
NATO UNCLASSIFIED Releasable to ISAF

9. Common Mission Network
Command C2 Network
Strategic (JFC-B, ISAF HQ) NS / IS
Operational (IJC, RC, APOD) NS / IS
CX-I, National (CJOC)
Tactical (TF) CX-I, UK Overtask, National networks
The funding of NATO CIS into the operational level is more then traditionally expected from NATO (Balkans, Bi-SC AIS)
CX-I may very well disappear out of the Operational Layer since it is now transparently connected to ISAF Secret
NS may very well disappear from the operational level. NS will be pruned as far as possible while IS is the centre of gravity (and requires all available bandwidth.
NATO extending into operational / divisional (2*) level at the RCs makes the common application question relevant, after all it has been typically the task of the nations to provide these applications, especially on the Land C2 apps. More reason for Common and integrated Apps (hence the success of JADOCS, which support JOINT fires)
Also on the operational level there are more JOINT operations then expected from a doctrinal perspective. More reason to
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

10. Common Mission Network
There is NO Common Mission Network for Afghanistan
NATO still has two (classified) networks (NS + IS)
National networks still used on tactical level
Germany
Canada
The Netherlands
However:
ISAF Secret (+Overtask + CXI) is the largest network throughout Afghanistan (with potentially more sites then the NATO static network)
NATO UNCLASSIFIED Releasable to ISAF

11. NATO UNCLASSIFIED Releasable to ISAF
Application Sources
NATO Applications
Free of charge and available to all nations
JOC Watch, JChat
NATO Application with COTS elements
NATO application free of charge but component needs investment from nation
JOIIS (MapInfo), iGeoSIT, BOM/COPLM (Maria)
COTS Applications
Requires significant investment from nation for procurement, maintenance and development (!)
JADOCS, WEBTAS, CIDNE
National Applications
Release and support issues (FMS, ITAR etc.)
NATO UNCLASSIFIED Releasable to ISAF

12. Application Interoperability
As part of the CXI Phase 2 discussions NATO and the US have agreed to:
NOT select a common set of applications but work on application/data operability
NATO (selected) applications will be used at HQ ISAF, IJC HQ and RC level.
National trusted/funded applications can be used at Tactical level
Individual connections between applications should be prevented as they are hard to manage. Interoperability servers should be used instead
NATO UNCLASSIFIED Releasable to ISAF

13. Interoperability Points
Interoperability points will be setup to exchange information.
NATO will use COPLM/BOM server (MIPDEM compliant)
US will use the PAS Servers (Publish and Subscribe)
UK will use ....
One of the key applications that we need as “Common Mission Application” is XMPP based Chat in support of C2.
All nations have to agree on the protocol extensions so that we remain interoperable (e.g. security labels for x-domain chat, geo-whiteboarding extensions for map based collaboration).
XMPP is the protocol of choice between US, UK and NATO. Need to agree on CONOPS to become one large XMPP (Jchat) community. GCTF can only be included using x-domain chat gateway.
NATO UNCLASSIFIED Releasable to ISAF
NATO UNCLASSIFIED

14. Proposed CXI Architecture with C2 Interoperability Bus
CIDNE
JADOCS
ISRIS
Intel FS
JOCWatchB
NIRIS
C2PC
CPOF
FBCB2
GCCS
BOM
JOIIS
COP
ICC
US Integration Solutions
Based on PASS / DDS Server
C2 Interoperability Bus (CUR 355)
JC3IEDM / NIIA Canonical Form
By installing an ISAF interoperability bus on the ISAF Secret network, we can significantly simplify our connection to the US systems. This will enable us to significantly reduce the scope of work required of the CENTRIXS ISAF Phase II project and will result in a solution that is both more flexible and is also easier to maintain.
The ISAF interoperability bus will be based on existing NATO standards, including the JC3IEDM standard that has arisen from the MIP community, and also the NIIA standards for ISR interoperability that have been developed by the MAJIIC community.
EVE
CIED
IFTS
JISR 1
Others
CORSOM
GEO ü
JADOCS
NATO UNCLASSIFIED Releasable to ISAF 14

15. NATO UNCLASSIFIED Releasable to ISAF
Way Ahead
Expansion of the Common Mission Network
More NATO/ISAF nations to extend the mission secret network
Achieve Data / Application Interoperability
CENTRIXS-ISAF Phase 2
Define & implement interoperability points
Increase the use of web based access
Provide ISAF C2
Interoperability Bus and ISAF COP (CUR 355 and 264)
NATO UNCLASSIFIED Releasable to ISAF