1. WJTSC ACGU Working Group ACGU … Way Ahead March 2012 Mr. John Vinett

2. Topics – Background – Proposal – Discussion

3. Background 2003 Australia (AUS)/US Interoperability Study Conducted 2005 AUS MINDEF and US SECDEF established Joint Combined Training Capability (JCTC) to enhance bilateral training 2006 Began the effort to connect National training networks 2007 - JTEN Connects to Australian DTEN – Talisman Sabre 07 Connections to UK and Canada working – 2008 UK Use cases – 2009 … 12 May Great Britain CONOPS approved 2009 … December -Nations begin ACGU effort 2010 … June - ACGU Briefed to DSAWG for TS 2011 2011 … ACGU OPT re-defines and re-designs ACGU – Multi-National MOU work Begins 2012 … Canada CONOPS Approved – 24x7x365 connectivity approved for Australia – Updated Ports, Protocols and Services list (55) approved

4. Facts ACGU is owned and operated by US JCW ACGU has been approved as the Enclave between US and Trusted Mission Partners Connectivity to Partners for training and test validated – In order to meet US security requirements, US must maintain an Enclave/DMZ such as ACGU. CONOPS exist that govern connectivity via ACGU – CONOPS are all very similar but country specific MOUs exist (not all executed yet) that cover ACGU connectivity Australia and Great Britain are connected into ACGU Canada will connect into ACGU in near future

5. Facts Continued ACGU is aligning with SIPR Rel DMZ requirements – Very well documented and understood – 80 % aligned – JCW will expand ACGU capabilities this year $500K to be invested Australia has an FMS case initiated for JCW support Multi-National funding and management has been difficult to define All of the pieces are in place to rapidly make this a Multi-National capability!

6. Proposal for Discussion Proposal: – Similar to the AMN Model – Australia has proposed that the four Countries jointly fund the ACGU US manages the core services and the ACGU for the benefit of the four nations. Australia has an FMS case pending – MOUs can quickly and easily be made standard – CONOPS can quickly be combined into one ACGU aligned with SIPR Rel DMZ requirements A Configuration/Capabilities Management Board will need to be formed – DSAWG model – Regularly scheduled meetings – One nation, one vote – Rotating Chair manages the group but does not vote – Subject Matter Experts petition the board for changes

7. Proposal for Discussion Proposal Continued: – Countries maintain and operate their own network Countries may locate sharable assets into their DMZs Countries manage their respective users Countries will establish and manage some ACGU services (AD, DNS, etc) – Could go to Five Eyes if Management Board agrees and a requirement exists – Cost: We have very good maintenance cost estimates Based upon actual costs to operate and maintain CX-I TF – $1.2 to $1.4 M per year Core services investment about $2M. – Initial cost is already sunk. Refresh begins about 2015 If Agreed, this capability could be signed and online by 1 July

8. Discussion