ORGANIZATIONAL MESSAGING POLICY - UPDATED:

1 NAVADMINs are known that refer back to this one:
NAVADMIN ID Title
NAVADMIN 068/11 TRANSITION TO OFFICIAL INFORMATION EXCHANGE TO SATISFY MESSAGING REQUIREMENTS OF BUPERS AND NAVPERSCOM DIRECTIVES AND PUBLICATIONS
UNCLASSIFIED//

ROUTINE

R 161850Z DEC 10

FM CNO WASHINGTON DC

TO AL NAVADMIN
NAVADMIN

INFO CJCS
CMC WASHINGTON DC
COMDT COGARD WASHINGTON DC
DIA WASHINGTON DC
DISA WASHINGTON DC
COGARD TISCOM ALEXANDRIA VA
RDA CHIEF ENGINEER WASHINGTON DC
CNO WASHINGTON DC
COMMARCORSYSCOM QUANTICO VA
DISA JITC WASH OPS

BT
UNCLAS
FM CNO WASHINGTON DC
TO AL NAVADMIN
NAVADMIN
INFO
CJCS WASHINGTON DC
CMC WASHINGTON DC
COMDT COGARD WASHINGTON DC
DIA WASHINGTON DC
DISA WASHINGTON DC
COMMARCORSYSCOM QUANTICO VA
DISA JITC WASH OPS
COGARD TISCOM ALEXANDRIA VA
RDA CHIEF ENGINEER WASHINGTON DC
UNCLAS //N02310//

NAVADMIN 404/10

MSGID/GENADMIN/CNO WASHINGTON DC/N2N6/DEC//

SUBJ/ORGANIZATIONAL MESSAGING POLICY - UPDATED//

REF/A/MSG/NAVADMIN 373/10/24NOV2010//

REF/B/MEMO/ASD NII/16MAY2005/NOTAL//

REF/C/MEMO/DOD CIO/16DEC2009/NOTAL//

REF/D/MEMO/VCJCS/26NOV2008/NOTAL//

REF/E/MEMO/COMNAVNETWARCOM/27FEB2009/NOTAL//

REF/F/MSGID/COMNAVCYBERFOR/251735ZMAR10/-//

REF/G/MEMO/JOINT STAFF/30APR2009/NOTAL//

REF/H/MEMO/DON CIO/20OCT2008/NOTAL//

NARR/REF A IS NAVADMIN 373/10 PROMULGATING ORGANIZATIONAL MESSAGING POLICY.  
REF B IS ASSISTANT SECRETARY OF DEFENSE FOR NETWORKS AND INFORMATION 
INTEGRATION (NII) MEMO PLACING DEFENSE MESSAGE SYSTEM
(DMS) IN SUSTAINMENT.  REF C IS DEPARTMENT OF DEFENSE CHIEF INFORMATION 
OFFICER (DOD CIO) MEMO PROVIDING GUIDANCE REGARDING THE SUSTAINMENT OF DMS.  
REF D IS VICE CHAIRMAN OF THE JOINT CHIEFS OF STAFF (VCJCS) MEMO INTENDING TO 
ELIMINATE DMS.  REF E IS COMNAVNETWARCOM COMMAND AND CONTROL OFFICIAL 
INFORMATION (OI) REQUIREMENTS MEMO.  REF F IS COMNAVCYBERFOR ANNOUNCMENT OF 
COMMAND EMAIL IMPLEMENTATION.  REF G IS JOINT STAFF MEMO TO COALITION PARTNERS 
REGARDING THE FUTURE OF ORGANIZATIONAL MESSAGING (OM).  REF H IS DEPARTMENT OF 
THE NAVY CHIEF INFORMATION OFFICER (DON CIO) MEMO ENDORSING THE USE OF WEB 2.0 
TOOLS FOR INFORMATION EXCHANGE.//
POC/NAME: ONEAL CHARLES/LCDR/UNIT: CNO/WASHINGTON DC/
TEL: 703-604-7716/EMAIL: CHARLES.ONEAL1@NAVY.MIL/
POC/NAME: NANCY RANTANEN/CIV/UNIT: NAVCYBERFOR/NORFOLK VA/
TEL: 757-417-6713 EXT. 7/EMAIL: NANCY.RANTANEN@NAVY.MIL//

RMKS/1.  THIS MESSAGE SUPERSEDES REF A AND PROVIDES UPDATED GUIDANCE.  THIS IS 
A CNO/DON CIO/FLTCYBERCOM/COMNAVCYBERFOR/PEO C4I COORDINATED MESSAGE PROVIDING 
GUIDANCE AND DIRECTION ON THE NAVY'S ROADMAP TO TRANSITION FROM LEGACY DMS 
ARCHITECTURE TO ALTERNATIVE METHODS OF CONVEYING OFFICIAL INFORMATION (OI).

2.  BACKGROUND.  PER REF B, DMS WAS PLACED IN SUSTAINMENT
THROUGH    FY-12. RECENT DOD CIO AND VCJCS GUIDANCE IDENTIFIED IN
REFS C AND D DIRECTS THE SERVICES TO FIND ALTERNATE MEANS AND TECHNOLOGIES TO 
PROCESS ORGANIZATIONAL MESSAGES WHILE A POST-DMS ROADMAP IS DEFINED.  THE NAVY 
INTENDS TO CONSOLIDATE AND ELIMINATE DMS FOR ORGANIZATIONAL MESSAGING USING A 
PHASED APPROACH WHILE ENSURING CRITICAL MISSION REQUIREMENTS (IDENTIFIED IN 
REF E) ARE MAINTAINED.

3.  OPNAV ENDORSES COMMAND EMAIL EFFORTS CITED IN REF F.  THIS EFFORT HAS 
ALREADY RESULTED IN A REDUCTION OF 84 BILLETS IN FY-11 AND $97 .1M IN COST 
SAVINGS ACROSS THE FYDP.  ACCORDINGLY, THE NAVY WILL NO LONGER SUPPORT ITS 
UNCLASSIFIED MESSAGING DOMAIN AFTER 30 APR 2011.  ALL UNCLASSIFIED NON-COMMAND 
AND CONTROL (C2) RELATED OI THAT HISTORICALLY WAS TRANSMITTED VIA MESSAGE 
TRAFFIC SHALL BE DISSIMENATED VIA COMMAND EMAIL OR OTHER TRANSPORT MECHANISMS 
SUCH AS PORTALS, WIKIS, BLOGS, ETC.  C2 OI WILL CONTINUE TO BE SUPPORTED VIA 
SECRET NAVY REGIONAL ENTERPRISE MESSAGING SYSTEM, AS WELL AS LEGACY SYSTEMS 
SUCH AS FLEET SIPRNET MESSAGING.  PER REF G, THE NAVY WILL CONTINUE TO 
EXCHANGE OI WITH OUR COALITION PARTNERS THROUGH ACP-145 STANDARD GATEWAYS AND 
EXISTING CLASSIFIED MESSAGING SYSTEMS UNTIL A COMBINED COMMUNICATIONS-
ELECTRONICS BOARD TRANSITIONAL CAPABILITY THAT FULLY SUPPORTS INTEROPERABILITY 
IS DEVELOPED.  NAVCYBERFOR IS TASKED WITH THE IMPLEMENTATION OF COMMAND EMAIL 
AND ASSOCIATED GATEWAY SERVICES TO ENSURE INTEROPERABILITY WITH OTHER ALLIES, 
COALITION, JOINT, AND AGENCY PARTNERS.

4.  THE COMMAND EMAIL SYSTEM BEING IMPLEMENTED BY NAVCYBERFOR UTILIZES A 
COMMAND GLOBAL ADDRESS LIST (CGAL).  THIS CGAL INCORPORATES ORGANIZATIONAL 
EMAIL ADDRESSES THAT CORRELATE TO COMMAND PLAIN LANGUAGE ADDRESSES CURRENTLY 
USED IN LEGACY/DMS.  THE CGAL, WITH NAVY-APPROVED EMAIL SYSTEMS (NMCI, ONE-
NET, IT-21 AND LEGACY NETWORKS) WILL BE USED FOR TRANSPORT OF OI.  COMMAND 
EMAIL FINAL OPERATIONAL CAPABILITY (FOC) IS SCHEDULED FOR 1 APR 11.  ALL 
CURRENT INSTRUCTIONS AND PUBLICATIONS THAT DIRECT THE USE OF NAVAL MESSAGES 
FOR NON-C2 INFORMATION MUST BE CHANGED TO REFLECT COMMAND EMAIL OR OTHER 
ALTERNATIVE MECHANISM FOR DELIVERY.  REFERENCES AND ADDITIONAL INFORMATION ARE 
PUBLISHED ON THE NAVY OIX WEBSITE AT 
HTTPS://WWW.PORTAL.NAVY.MIL/OIX/DEFAULT.ASPX.

5. ROADMAP.
A.  THE NAVY HAS ALREADY BEGUN CONSOLIDATING AND ELIMINATING LEGACY /DMS 
ARCHITECTURE.  CRITICAL DMS COMPONENTS SUCH AS NOVA AND SUPPORTING SYSTEMS 
WILL BE SUSTAINED THROUGH FY-17 AND FY-18 TIMEFRAME TO SUPPORT CRITICAL 
NUCLEAR COMMAND, CONTROL AND COMMUNICATIONS REQUIREMENTS AND ALLIED 
COMMUNICATIONS.
B.  BEGINNING IN FY-12, THE NAVY WILL BEGIN TRANSITIONING ITS SHORE AND AFLOAT 
COMPONENTS TO AN IP-BASED INTERIM SOLUTION CALLED COMMAND AND CONTROL OFFICIAL 
INFORMATION EXCHANGE (C2OIX).  C2OIX IS THE NAVY'S TRANSITIONAL OFFICIAL 
INFORMATION EXCHANGE SYSTEM THAT CONSOLIDATES AND ELIMINATES SHORE AND AFLOAT 
SUPPORT SYSTEMS WHILE STILL FACILITATING MESSAGE TRANSFER VIA IP AS THE 
PRIMARY, PLUS FAILOVER TO ALTERNATIVE MECHANISMS. C2OIX IS DESIGNED TO SUPPORT 
A NUMBER OF MODERN MESSAGING PROTOCOLS SUCH AS OUTLOOK WEB ACCESS INTERFACES 
AND EXTENSIBLE MARKUP LANGUAGE DATA EXCHANGES THAT CAN BE VIEWED AS PORTLETS, 
AND SIMPLE MAIL TRANSFER PROTOCOL. MESSAGE COMMUNICATIONS WITH ALLIED, 
COALITION AND OTHER DOD SERVICES AND AGENCIES WILL CONTINUE TO BE SUPPORTED BY 
EXISTING CLASSIFIED MESSAGING SYSTEMS.  WITH IP CONNECTIVITY BEING PROBLEMATIC 
FOR AFLOAT COMPONENTS AT TIMES, COMMON USER DIGITAL EXCHANGE SYSTEM WILL 
REMAIN AS AN ALTERNATIVE PATH FOR MESSAGE TRAFFIC DELIVERY.
C.  FLEET BROADCAST IS IN SUSTAINMENT AND WILL NO LONGER BE FUNDED UPON C2OIX 
REACHING FOC DURING THE FY-17 AND FY-18 TIMEFRAME.  THE NAVY WILL CONTINUE TO 
EXPLORE OTHER COMMUNICATION MEANS TO FULLY REPLACE FLEET BROADCAST 
CAPABILITIES AND REDUNDANCIES.

6.  ACTION.
A.  ALL COMMANDERS ARE DIRECTED TO IMPLEMENT ALTERNATIVE METHODS DESCRIBED IN 
REF H FOR THE EXCHANGE OF NON-C2 RELATED UNCLASSIFIED OI.  ALL COMMANDS WILL 
REGISTER FOR AND ACTIVATE COMMAND EMAIL ACCOUNTS AND REQUEST ALTERNATE TOKENS 
PER GUIDANCE POSTED AT HTTPS://WWW.PORTAL.NAVY.MIL/OIX/DEFAULT.ASPX.
B.  ALL COMMANDERS SHALL IDENTIFY ANY INSTRUCTIONS, PUBLICATIONS, NOTICES, AND 
DIRECTIVES THAT REQUIRE SENDING AND RECEIVING ORGANIZATIONAL MESSAGES, AND 
MAKE CHANGES AS REQUIRED TO REMOVE MESSAGING REQUIREMENTS, WHILE PROMULGATING 
GUIDANCE THAT FULLY IMPLEMENTS ALTERNATIVE METHODS FOR UNCLASSIFIED OFFICIAL 
INFORMATION EXCHANGE NLT 1 FEB 11.
C.  ORGANIZATIONS THAT CANNOT TRANSITION UNCLASSIFIED MESSAGING TO ALTERNATE 
METHODS BY 31 MAR 11 MUST REPORT TO THEIR ISIC WITH A PLAN OF ACTION AND 
MILESTONES (POA&M) NLT 1 FEB 11, SPECIFYING OPERATIONAL FUNCTIONS THAT CANNOT 
TRANSITION.  THE POA&M SHOULD ADDRESS RESOURCE AND/OR TECHNOLOGY SHORTFALLS 
THAT PRECLUDE THE TRANSITION.  ECHELON II COMMANDS WILL CONSOLIDATE ISIC 
REPORTS AND FORWARD TO USFF (N6).  NAVCYBERFOR, IN THEIR DUAL ROLE AS USFF 
(N6), WILL OFFER OPTIONS TO ORGANIZATIONS HAVING OPERATIONAL FUNCTIONS THAT 
CANNOT BE TRANSITIONED.

7.  RELEASED BY VADM DAVID J. DORSETT, DCNO FOR INFORMATION DOMINANCE 
(N2N6).//

BT
#0001
NNNN