CENTRIXS-ISAF

Report
CENTRIXS-ISAF:
Phase 1 Overview
Jesse Scott
NC3A CAT 7: Core Enterprise Services
NATO UNCLASSIFIED Releasable to ISAF
Agenda






1.
2.
3.
4.
5.
6.
Transformation of Afghanistan Coalition Networks
CENTRIXS-ISAF Interconnection Overview
A Common Mission Network
Operational Use
Mission Applications & Interoperability
The Way Ahead (Phase 2, HoA, Additional Nations)
NATO UNCLASSIFIED Releasable to ISAF
2
Coalition Network Transformation
 CENTRIXS-GCTF Cross-Domain Gateway (2006)
 Procured by US and NATO
 Allowing bi-directional e-mail 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 UNCLASSIFIED Releasable to ISAF
3
Overview of the ISAF Networks
FOC+ primary connection
FOC+ secondary connection
IOC connection
FOC+ SATCOM
Anchor connection
CENTRIXS-ISAF
Gateway connection
NATO ISAF
IOC infrastructure
location
FOC+ infrastructure
location
NATO
FOC+
UK Overtask
infrastructure
KABUL
SATCOM anchor
location
CENTRIXS-ISAF
infrastructure
NATO
FOC+
UK Overtask
KAF
FOC+ ISAF
NATO UNCLASSIFIED Releasable to ISAF
4
Pre-CENTRIXS-ISAF IERs
NATO NS
VOIP
REQUIRED
NITB
IN PROGRESS
CHAT
OPERATIONAL
EMAIL
WEB
GCTF
COP
SIPR
VoIP
EMAIL
CHAT
ISAF MS
OVERTASK
UK
IER
IER
IER
NATO UNCLASSIFIED Releasable to ISAF
5
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 CENTRIXSGCTF
 Establish two interconnection points (Kabul and KAF)
between CENTRIXS-ISAF and ISAF Secret
NATO UNCLASSIFIED Releasable to ISAF
6
ISAF Current networks and
Information Exchange Requirement
NATO NS
US SIPR
VOIP
NITB
CHAT
EMAIL
WEB
COP
VoIP
VOIP
EMAIL
CENTRIXS
GCTF
CHAT
CENTRIXS
ISAF
EMAIL
CHAT
FILE
FMV
NATO
ISAF
COP
41 TCN Coalition
Zone
OPERATIONAL
IN PROGRESS
REQUIRED
OVERTASK
UK
IER
IER
IER
NATO UNCLASSIFIED Releasable to ISAF
7
Post-Phase 1 CXI Connectivity
N ATO SECRET
eMail,
one-way http
Service Provision Authority:
U.S. ARCENT
one-way http
ISAF Coalition Information Domain
ISAF SECRET
(41 TCN)
CENTRIXS
-ISAF
(41 TCN)
(existing) Cross
Domain
Gateways
(eMail, Chat, VoIP)
Service Provision Authority:
NATO CIS Services Agency
NATO UNCLASSIFIED Releasable to ISAF
CENTRIXS
-GCTF
8
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)
NATO UNCLASSIFIED Releasable to ISAF
9
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
10
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
11
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
12
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).
NATO UNCLASSIFIED Releasable to ISAF
13
Proposed CXI Architecture
with C2 Interoperability Bus
CIDNE
C2PC
JADOCS
CPOF
ISRIS
FBCB2
GCCS
Intel FS
BOM
JOCWatchB
JOIIS
NIRIS
COP
ICC
US Integration Solutions
C2 Interoperability Bus (CUR 355)
Based on PASS / DDS Server
JC3IEDM / NIIA Canonical Form
EVE
Others
CORSOM
NATO UNCLASSIFIED Releasable to ISAF
CIED
GEO
IFTS

JISR 1
JADOCS
14
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
15

similar documents