Cdls washington dc cdr usafricom stuttgart ge cdr uspacom honolulu hi

ZNR UUUUU

R 091456Z APR 15

FM CNO WASHINGTON DC

TO ADFWC

ADMIRALDANFLEET

ASWCEN JMSDF JA

BWOPSCMD

CDR USAFRICOM STUTTGART GE

CDR USPACOM HONOLULU HI

CDR USSOUTHCOM MIAMI FL

CDR USSTRATCOM OFFUTT AFB NE

NDHQ C NAVY OTTAWA

NDHQ SJS OTTAWA

MARLANTHQ HALIFAX

MARPACHQ ESQUIMALT

CFMCC CENT

CHIEF OF NAVAL STAFF ROME IT

CINCGERFLEET NCS

CINCROKFLT ROKN BUSAN KOR

COMAUSFLT

COMAUSFLT AFLOAT

COMDATG

COMFLTCYBERCOM FT GEORGE G MEADE MD

COMFOURTHFLT

COMNAVAIRFORES SAN DIEGO CA

COGARD LO COMNAVFORKOREA SEOUL KOR

COMNAVSURFOR SAN DIEGO CA

COMPACFLT PEARL HARBOR HI

COMRNLN

COMSIXTHFLT

COMSPAWARSYSCOM SAN DIEGO CA

COMSUBFOR NORFOLK VA

COMTENTHFLT

COMTHIRDFLT

COMUSFLTFORCOM NORFOLK VA

COMUSNAVCENT

COMUSNAVEUR COMUSNAVAF NAPLES IT

DAASC DAYTON WRIGHT PATTERSON AFB OH

DDIS DNK

DEFCAMSAUS

DGNCIW

DIRECT USNORTHCOM

DISA PAC WHEELER AAF HI

DISA FT GEORGE G MEADE MD

DSD CANBERRA

CDR USEUCOM VAIHINGEN GE

FHQAUST

GENAVO ROSTOCK

HQ JFNZ

HQ ROKN TAEJON KOR

NATO COMMCEN SHAPE

HQ USAFRICOM STUTTGART GE

HQ USSOUTHCOM MIAMI FL

HQJOC

HQNZDF

MARINE PARIS

MARISTAT

MOD NL

COMLOG WESTPAC

COMNECC LITTLE CREEK VA

MSO DGC4I JMSDF JA

NATO BRUSSELS

COMNAVFORJAPAN YOKOSUKA JA

CMS AA FAR EAST YOKOSUKA JA

NAVCOMTELSTA NAPLES IT

NCTAMS LANT DET HAMPTON ROADS NORFOLK VA

NDHQ CMP OTTAWA

JOINT STAFF NORAD-USNORTHCOM LNO WASHINGTON DC

NSACSS FT GEORGE G MEADE MD

PEO C4I SAN DIEGO CA

SACT

SPAWARSYSCEN NORFOLK DET WESTPAC YOKOSUKA JA

USCENTCOM CCJ6 MACDILL AFB FL

USCENTCOM JSO FWD MACDILL AFB FL

COMNAVSURFLANT NORFOLK VA

COMSUBPAC PEARL HARBOR HI

COMOPSNAV

ABNL

COMEUROMARFOR

INFO CNO WASHINGTON DC

BT

UNCLAS

POC/PURIFOY/CDR/OPNAV N2N6F34/-/TEL: 703-695-7876/EMAIL: RODNEY.PURIFOY(AT)NAVY.MIL//

POC/ZATT/CTR/OPNAV N2N6F34/-/TEL: 703-695-7882/EMAIL: DAVID.ZATT.CTR(AT)NAVY.MIL//

RMKS/1. This message highlights specific issues, action items, and priorities addressed during the semi-annual Multi-National Maritime Information Services Interoperability (M2I2) Board 15-01 meeting, which occurred February 16 * 21, 2015 in Victoria, Canada. The M2I2 Board is the single coalition maritime information systems forum focused on improving maritime coalition network interoperability. Its current focus is to improve Combined Enterprise Regional Information Exchange System-Maritime (CENTRIXS-M) environments and collaboration at sea, while supporting the development of Mission Partner Environment (MPE), North Atlantic Treaty Organization (NATO) Federated Mission Networking (FMN), and other similar configurable secret mission capabilities.

2. The M2I2 Board 15-01 meeting was hosted by the U.S. and attended by representatives from the following nations and organizations: Australia, Belgium, Canada, Chile, Denmark, Finland, France, Germany, Italy, Japan, Mexico, Netherlands, New Zealand, Norway, Peru, Sweden, the United Kingdom, and NATO*s Allied Command Operations and Combined Joint Operations from the Sea Centre of Excellence. Representation from the U.S. included: Office of the Chief of Naval Operations; U.S. Central Command; U.S. Cyber Command; U.S. European Command; U.S. Northern Command; U.S. Pacific Command; U.S. Southern Command; U.S. Fleet Forces Command; U.S. Pacific Fleet; U.S. Navy Information Dominance Forces; U.S.THIRD Fleet; U.S. FOURTH Fleet; U.S. FIFTH Fleet; U.S. SIXTH Fleet; U.S. Naval Forces Japan; Program Executive Office Command, Control, Communications, Computers, and Intelligence; U.S. Space and Naval Warfare Systems Facility Pacific; Naval Computer and Telecommunications Area Master Station Pacific/Pacific Regional Network Operations Center; Tactical Training Group Pacific; Office of the Under Secretary of Defense for Intelligence; Defense Information Systems Agency (DISA); Space and Naval Warfare Systems (SPAWAR) Center Atlantic; SPAWAR Center Pacific; Joint Interoperability and Test Command; and the U.S. Coast Guard. First time attendees to the meeting included: Chile, Mexico, Peru, U.S. Central Command, and U.S. Cyber Command.

3. The M2I2 Board addressed coalition operational and technical capabilities related to the effective employment of coalition networks in the maritime environment. Specific highlights include:

a. Policy and Doctrine. The M2I2 working groups advanced the following governance and organizational items:

(1) Current MPE/NATO FMN are land centric. Developed a plan of action and milestones to review and update the joining, membership, and exit instructions to ensure the maritime environment is properly incorporated. Scheduled a MPE/FMN *Deep-dive* as part of the M2I2 Board 15-02 agenda.

(2) Agreed to the updated CENTRIXS-M quick reference guide and included the services checklist as an annex, to ensure that new coalition members (or potential members) have the basic information and guidance regarding CENTRIXS-M in one document.

(3) Reviewed the common mission network transport (CMNT) implementation requirements for nations that are interested in connecting to the CMNT. DISA will investigate and provide feedback at the M2I2 Board 15-02.

(4) Approved a new M2I2 Board battle rhythm to improve coordination and completion of actions between meetings.

b. Command and Control (C2). The M2I2 Board worked to establish a future vision for maritime common operational picture, also known as recognized maritime picture. Operation and security of C2 systems in a C2 denied or degraded environment continues to concern the board. The board made progress on the following C2 issues:

(1) Common operating picture (COP) tool synchronization and interoperability. M2I2 initiated a COP tool data call that will be used to determine COP version/variants for all M2I2 members and establish a baseline of interoperability capabilities and limitations.

(2) Reviewed the increased demands on communications and information sharing in the Arctic. National polar updates are programmed for future M2I2 Board meetings to share improvements and challenges in the Arctic and Antarctic.

(3) Shared voice over internet protocol call manager information including connection to the Combined Maritime Forces Central (CMFC) gatekeepers and requirements for nations to connect their national assets.

(4) Provided an update on the status of the Global Counter Terrorism Force (GCTF) Network. U.S. Joint Staff and DISA are determining whether GCTF application services should be terminated. GCTF transport capabilities will be maintained for the foreseeable future while alternative methods of transport are developed to ensure members maintain connectivity associated with subordinate enclaves. No changes will occur to GCTF applications services or transport capabilities without coordination between U.S. combatant commands, services, and agencies. A communications tasking order will be issued prior to DISA shutting down application services.

(5) Planned multi-lateral enduring contingency domino configuration. Implementation of CENTRIXS-M baseline toolsets should reduce operator training requirements and improve information sharing.

(6) Discussed command and control personal computer (C2PC) version differences and possible impacts to coalition maritime units.

c. Information Security and Survivability of Maritime Networks. The M2I2 Board made progress towards increasing network security and resilience. The challenge of aligning national standards for security and information sharing is of particular importance to the member nations. The M2I2 Board:

(1) Shared Windows XP to Windows 7 migration lessons identified/learned, and future U.S. Navy plans for migration to Windows 8/Windows 10.

(2) Discussed commercial solutions for classified (CSfC) implementation in the U.S. Southern Command area of responsibility (AOR) and provided technical details of CSfC functionality. CSfC implementation policies and procedures standardization across AORs must be developed and will be a priority in future meetings.

(3) Shared the information assurance (IA) lessons learned from TRIDENT WARRIOR 2014. The test highlighted the need to revise and standardize the M2I2 IA standard organization procedures. This work will be completed at the next M2I2.

(4) Updated the IA four-phase work plan. The M2I2 IA focus group will develop an IA roadmap and execution timelines, to include the establishment of IA situational awareness and virtualization tools.

d. Operational Support. Representation from international partners, U.S. combatant commanders/fleets, and other U.S. Department of Defense organizations at the M2I2 Board remains critical to addressing the challenges of operating in the coalition maritime environment and the development of standardized MPE solutions. The M2I2 Board:

(1) Held myriad geographic combatant commander/component and partner nation sidebars to discuss current and future operational requirements covering a variety of topics such as: Network Operation Center support for Consolidated Afloat Networks and Enterprise Services; C2PC interoperability; trusted network environment implementation across the geographic combatant commanders and interaction with CENTRIXS-M; CMFC transport options; U.S. Battlefield Information, Collection, and Exploitation System implementation implications for partners; and virtualization support in deployed AORs.

(2) Established an experimentation and interoperability focus group. This group will plan tests to verify network and application interoperability. The tests will use the coalition test and evaluation environment, which was recently extended to Pearl City, Hawaii.

4. The ad hoc nature of coalitions requires continued improvement in interoperability. The M2I2 Board continues to be the principal organization for the development of these capabilities within the maritime community. As Vice Admiral Mark Norman, Commander of the Royal Canadian Navy noted, *The standards and practices laid down and governed by this board provide the underpinning for successful maritime coalition operations.*

5. All briefings and detailed action items (including status and tracking) are available on the APAN SharePoint M2I2 web site and can be view upon request to the points of contact.

6. The next M2I2 Board will be held in Hamburg, Germany from 7-11 September 2015.

7. Released by Vice Admiral Ted N. Branch, OPNAV N2N6.//